-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS110E Dimmer has many issues with brightness #16804
Comments
Did you try it with the latest converter?
|
For me it seems, that brightness in that case is the 'normal' brightness setting AND the power_on_brightness at the same time. |
Does anybody know a way to limit the brightness slider? I set min- and max_brightness, but still can go below min/max treshold with the normal brightness slider. |
@Berlusconi13 I tried edge branch without success, but now I tried this converter and yeah, it's better (thank you!) but there are still some problems, and even new ones.
This is that I got by quick testing, maybe there are more errors too.
This is annoying for me too, but I tested other dimmers with min/max and it was never respected in Z2M and Home Assistant dashboard cards :/ Only in manual usage. I think it could be limited easy in converter, but I'm not sure about Z2M dashboard. It would be great if Z2M instead limiting brightness range, it could actually calculate correct range and send that to device. So If we have min_brightness set to 100 and max to 200, after setting in Z2M or HA brightness value to 1, it could send 100 to device, 255 would send 200, and 127 (50%) = 150 etc. I do not need max_brightness, but min_brightness is must for dimmable bulbs. Every dimmable led bulb has different level when it actually powers on. In my case I need brightness 65 to start, if I dim it lower it's just off and misleading. For now I'm fixing this somehow by nodered automations, but it's annoying and mess. Would be great if we could just use 1-255 range just like with led bulbs and led strips controllers. Is is maybe already option somewhere, implemented in some device? What do you think @Koenkk? |
@chojnicki Give it a friendly name and use it for all the stuff. That‘s how I solve it until now. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Same issue (I think) here with my TS110E_1gang_1 devices. Weirdly enough if I turn on or off a light from home assistant or Alexa (both are always as expected) the button works, it seems like it changes the brightness on its own after a while (dunno exactly how long it takes but often enough to make buttons unreliable). I tried changing power on behavior, disabling legacy home assistant actions, enabling state actions but nothing changes. Any ideas? |
What happened?
This device is supported by #15372, but for me it has many issues.
Probably other issues, it's hard do describe because it is chaos, everything related to brightness so maybe single fix would fix them all ;)
Some issues were fixed by @Koenkk already for similar device here #11853
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.30.1 tried also edge
Adapter firmware version
0x26680700
Adapter
ConBee2
Debug log
Refresh state:
Debug 2023-02-23 23:47:49Publishing get 'get' 'state' to 'living_room_ceiling_lamp'
Debug 2023-02-23 23:47:49Received Zigbee message from 'living_room_ceiling_lamp', type 'readResponse', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null
Info 2023-02-23 23:47:49MQTT publish: topic 'zigbee2mqtt/living_room_ceiling_lamp', payload '{"brightness":0,"last_seen":"2023-02-23T22:47:49.798Z","linkquality":119,"max_brightness":255,"min_brightness":1,"power_on_behavior":"previous","state":"ON","switch_type":"momentary"}'
Changing brightness:
Info 2023-02-23 23:49:43MQTT publish: topic 'zigbee2mqtt/living_room_ceiling_lamp', payload '{"brightness":185,"last_seen":"2023-02-23T22:49:43.590Z","linkquality":111,"max_brightness":255,"min_brightness":1,"power_on_behavior":"previous","state":"ON","switch_type":"momentary"}'
Debug 2023-02-23 23:49:44Received Zigbee message from 'living_room_ceiling_lamp', type 'attributeReport', cluster 'genLevelCtrl', data '{"61440":726,"currentLevel":185}' from endpoint 1 with groupID null
Info 2023-02-23 23:49:44MQTT publish: topic 'zigbee2mqtt/living_room_ceiling_lamp', payload '{"brightness":184,"last_seen":"2023-02-23T22:49:44.411Z","linkquality":119,"max_brightness":255,"min_brightness":1,"power_on_behavior":"previous","state":"ON","switch_type":"momentary"}'
The text was updated successfully, but these errors were encountered: