-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Presence of transition
parameter influences brightness in ON command
#2220
Comments
Should be fixed in latest zigbee2mqtt dev. |
Experiencing the same issue when switching lamps off with transition, brightness is set to 0 which makes some trouble in my installation. |
@pepp86 I guess it depends on the bulb, why dont you leave out the transition? |
@Koenkk Having this issue on all devices supporting transition. I want to use transition, so I can't leave it out!? |
@copystring @pepp86 your issue should be fixed in latest dev, please check and confirm. |
Seems to work. It remembers the brightness. |
Thanks, assuming this can be closed now. |
Bug Report
What happened
When a light is on and has e.g.
brightness: 50
, sending a command{"state": "ON", "transition": 1}
sets the brightness to maximum (255). Whereas if you send just{"state": "ON"}
, nothing happens (= the light stays on with brightness at level 50).It behaves the same way no matter what the actual value of
transition
is. Just its presence changes the behavior. The same situation is also if the defaulttransition
is set in the device-specific options.What did you expect to happen
I expect if sending an ON command to a light which is already on, nothing will happen. I definitely not expect that it should change the brightness and especially I don't expect that presence of
transition
parameter should change how it behaves.How to reproduce it (minimal and precise)
Given a Philips White Ambiance bulb (I only have Philips Hue bulbs, no other manufacturer to test) without default
transition
parameter in device-specific options, publishing one by one to its/set
topic:Debug Info
zigbee2mqtt version: commit
26ad2a
(version 1.6.0), was also present on927c4db
CC253X firmware version: I think this is a software issue, but I can provide if necessary
From the log, I'd guess it's connected to the fact that the
transition
parameter changes the Zigbee command from:Zigbee publish to device 'ambianceBulb3', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - 11
to:
Zigbee publish to device 'ambianceBulb3', genLevelCtrl - moveToLevelWithOnOff - {"level":255,"transtime":10} - {"manufSpec":0,"disDefaultRsp":0} - 11
The topic sounds similar to the #1260 but not the issue itself.
The text was updated successfully, but these errors were encountered: