DerOetzi
commented
4 months ago Can confirm this issue with all of my bulbs on firmware version 1.1.20 affected by this.
The behavior for me is
Without transition or tranisition:0 in device.yaml:
- Send brightness 100 -> Bulb goes 100%
- Send brightness 0 -> Bulb goes 0%
- Send brightness 0 -> Bulb goes 1% in reality, z2m shows 0%
- Send brightness 0 -> Bulb goes 0% in reality, z2m shows 0%
- Send brightness 0 -> Bulb goes 1% in reality, z2m shows 0%
- Send brightness 0 -> Bulb goes 0% in reality, z2m shows 0%
- ...
With transition: 1 in device.yaml:
- Send brightness 100 -> Bulb goes 100%
- Send brightness 0 -> Bulb goes 0%
- Send brightness 0 -> Bulb goes 1% in reality, z2m shows 0%
- Send brightness 0 -> Bulb goes 0% in reality, z2m shows 0%
- Send brightness 0 -> Bulb stay 0% in reality, z2m shows 0%
- Send brightness 0 -> Bulb stay 0% in reality, z2m shows 0%
If any logs can help please tell me! But this looks like an Firmware problem to me. For me the z2m debug logs look the same like sending the same sequences to other tradfri bulbs with other versions.
Koenkk
ggtimtom
aseeus
LookedPath
KizzyCode
GoodnessJSON
monks600
marazmarci
What happened?
Some of our IKEA bulbs are switching on to the lowest brightness setting when toggled. Across all the UIs (HK, HA, Z2M) the brightness value still shows as the brightness that the bulb is supposed to be at, but the bulb itself will be very dim. This happened suddenly after Z2M autoupdated to 1.33.1, and it has never happened before. No OTA was done on the bulbs either, so there was no other change.
I first encountered this issue with the ICPSHC24-10EU-IL-1 bulb. I found that setting the transition option to a numerical value instead of leaving it blank solves the issue. I have since set transitions for all bulbs to 1.
However, the above solution does not work for bulbs in groups. Certain bulbs in groups still power on to to a very dim setting on toggle. The odd thing is, (EDIT: when transition is set) toggling the bulb directly will bring the bulb back to its intended brightness, but toggling the entire group would cause the certain bulb to power on dimly. Not all bulbs are affected, only some are, and they all happen to be LED1537R6/LED1739R5 bulbs.
What did you expect to happen?
The bulb should turn on to the last brightness setting when toggling from off to on
How to reproduce it (minimal and precise)
Zigbee2MQTT version
1.33.1
Adapter firmware version
20230507
Adapter
tubeszb-cc2652-eth
Debug log
I'm running HAOS and can't SSH into the host so I'm trying my best here to copy and paste from the addon's logs tab.
Setting
Common Toilet Lightsto 100% causes all bulbs in the group to be at 100%:Toggling
Common Toilet Lightsgroup OFF:Toggling
Common Toilet Lightsgroup ON causesCommon Toilet Ceilingto be dim:Toggling
Common Toilet CeilingOFF directly:Toggling
Common Toilet CeilingON directly withtransitionvalue indevices.yamldeleted, bulb turns on but is dim:Setting
transitionto1and togglingCommon Toilet CeilingON directly causes bulb to turn on to the correct previous brightness:It seems that when the
transitionoption is set, togglingCommon Toilet CeilingON directly will causegenLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":10}to be sent andCommon Toilet Ceilingwill turn on to the correct previous value. With thetransitionoption cleared,genOnOff.onis sent instead, causingCommon Toilet Ceilingto be dim.Regardless, toggling the group ON always always causes
genOnOff.onto be sent, causingCommon Toilet Ceilingto be dim. Only if I turn on the group by swiping to the brightness in the UI willgenLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0})be sent.