Closed ianmtaylor1 closed 1 month ago
@Koenkk will this affect all versions of the LED2005R5/LED2106R3? I have no issues with the transition settings on the original version of these bulbs, it's broken on the newer revision. Original model: new version:
@Koenkk sorry to bump this but I want to make sure these changes won't break all the transition settings I've got on the older version of the bulb (I have a lot of them!) in the next release.
@tungmeister thanks for bringing this up. The off transition will now only be suppressed with firmware > 1.0.012
Changes will be available in the dev branch in a few hours from now.
Hello @Koenkk please also add https://www.zigbee2mqtt.io/devices/LED2003G10.html#ikea-led2003g10
On another note, maybe this helps with the issue: it happens MUCH more with ember (multiple times a day) than it did with ezsp (a couple times per week)
@supaeasy the fix is applied to all TRADFRI bulb with softwareBuildID > 1.0.012
. I think this issue can be closed now.
What happened?
Sorry for the grammatically confusing title, hopefully it will be clear below.
Sometimes I will send an "off" command to my bulb when the bulb is already off. This happens, for example, in home assistant scripts that turn off all the lights in a room when some lights are on but others are off, or if I press a smart button twice that turns off the light.
What did you expect to happen?
If the IKEA bulb is off, and I publish
{"state": "OFF"}
tozigbee2mqtt/My-Bulb-Name/set
, the light will remain off.How to reproduce it (minimal and precise)
{"state": "OFF"}
tozigbee2mqtt/My-Bulb-Name/set
. Bulb turns off as expected.Zigbee2MQTT version
1.36.0 commit: 86ed71c
Adapter firmware version
20210708
Adapter
SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P
Setup
Official docker image on Raspberry Pi 3B+
Debug log
No response