Koenkk
[BUG] Lidl lights (14156506L, 14158804L) flicker on, off, on when turning on
What happened?
When I turn on my lidl lights they flicker on, then off and on again. This only happens with the lidl lights and not with my other lights. Also when I set a transition value in z2m it takes a long time for them to turn on. Its regarding these lights: 14156506L 14158704L 14158804L
What did you expect to happen?
Turn on just as my other lights. WIthout flicker.
How to reproduce it (minimal and precise)
Buy a lidl lamp, pair it and turn them on. The will go:
- on
- off
- on
Within like 1 seconds does this happen. I am not using any transition and I am using adaptive lightning.
Zigbee2MQTT version
1.35.3-1
Adapter firmware version
20221226
Adapter
Sonoff 3.0
Debug log
Lights affected are:
- woonkamer_tv_lamp_links
- woonkamer_tv_lamp_rechts
- woonkamer_tafel_lamp
info 2023-03-31 07:34:12Succesfully changed options
info 2023-03-31 07:34:12MQTT publish: topic 'zigbee2mqtt/bridge/response/options', payload '{"data":{"restart_required":false},"status":"ok","transaction":"r2s7o-2"}'
debug 2023-03-31 07:34:14Received Zigbee message from 'tv_switch', type 'attributeReport', cluster 'aqaraOpple', data '{"247":{"data":[100,16,0,3,40,20,152,57,0,0,0,0,149,57,209,10,228,67,150,57,0,96,16,69,151,57,0,0,0,0,5,33,1,0,154,32,0,8,33,22,1,7,39,0,0,0,0,0,0,0,0,9,33,0,11,11,32,0,155,16,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
debug 2023-03-31 07:34:14lumi.plug.mmeu01: Processed buffer into data {"3":20,"5":1,"7":"0","8":278,"9":2816,"11":0,"100":0,"149":456.0845031738281,"150":2310,"151":0,"152":0,"154":0,"155":1}
debug 2023-03-31 07:34:14lumi.plug.mmeu01: unknown key 7 with value 0
debug 2023-03-31 07:34:14lumi.plug.mmeu01: unknown key 155 with value 1
debug 2023-03-31 07:34:14lumi.plug.mmeu01: Processed data into payload {"device_temperature":20,"power_outage_count":0,"state":"OFF","energy":456.08,"consumption":456.08,"voltage":231,"current":0,"power":0}
debug 2023-03-31 07:34:14lumi.plug.mmeu01: Processed data into payload {"device_temperature":20,"power_outage_count":0,"state":"OFF","energy":456.08,"consumption":456.08,"voltage":231,"current":0,"power":0}
info 2023-03-31 07:34:14MQTT publish: topic 'zigbee2mqtt/tv_switch', payload '{"auto_off":true,"consumer_connected":true,"consumption":456.08,"current":0,"device_temperature":20,"energy":456.08,"led_disabled_night":true,"linkquality":54,"overload_protection":2300,"power":0,"power_outage_count":0,"power_outage_memory":true,"state":"OFF","update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null,"voltage":231}'
debug 2023-03-31 07:34:16Received Zigbee message from 'afzuigkap', type 'readResponse', cluster 'haElectricalMeasurement', data '{"activePower":0,"rmsCurrent":0,"rmsVoltage":245}' from endpoint 1 with groupID 0
info 2023-03-31 07:34:16MQTT publish: topic 'zigbee2mqtt/afzuigkap', payload '{"child_lock":"UNLOCK","current":0,"energy":10.6,"indicator_mode":"off","linkquality":80,"power":0,"power_outage_memory":"restore","state":"OFF","update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null,"voltage":245}'
debug 2023-03-31 07:34:19Received MQTT message on 'zigbee2mqtt/woonkamer_lampen/set' with data '{"state":"ON"}'
debug 2023-03-31 07:34:19Publishing 'set' 'state' to 'woonkamer_lampen'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp1', payload '{"brightness":68,"color_mode":"color_temp","color_temp":454,"color_temp_startup":366,"linkquality":87,"power_on_behavior":"on","state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lampen', payload '{"brightness":68,"color":{"h":27,"hue":27,"s":92,"saturation":92,"x":0.5056,"y":0.4152},"color_mode":"color_temp","color_temp":454,"state":"ON"}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp2', payload '{"brightness":68,"color_mode":"color_temp","color_temp":454,"linkquality":94,"power_on_behavior":null,"state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp3', payload '{"brightness":68,"color_mode":"color_temp","color_temp":454,"color_temp_startup":370,"linkquality":98,"power_on_behavior":"previous","state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp4', payload '{"brightness":68,"color_mode":"color_temp","color_temp":454,"linkquality":87,"power_on_behavior":null,"state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_tafel_lamp', payload '{"brightness":68,"color":{"h":25,"hue":25,"s":95,"saturation":95,"x":0.5267,"y":0.4133},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":500,"do_not_disturb":null,"linkquality":87,"state":"ON"}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_tv_lamp_links', payload '{"brightness":68,"color":{"h":25,"hue":25,"s":95,"saturation":95,"x":0.5267,"y":0.4133},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":500,"do_not_disturb":null,"linkquality":83,"state":"ON"}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_tv_lamp_rechts', payload '{"brightness":68,"color":{"h":25,"hue":25,"s":95,"saturation":95,"x":0.5267,"y":0.4133},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":500,"do_not_disturb":null,"linkquality":69,"state":"ON"}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_spots', payload '{"brightness":68,"color":{"h":27,"hue":27,"s":92,"saturation":92,"x":0.5056,"y":0.4152},"color_mode":"color_temp","color_temp":454,"state":"ON"}'
debug 2023-03-31 07:34:19Received MQTT message on 'zigbee2mqtt/woonkamer_tafel_lamp/set' with data '{"state":"ON","transition":1.0,"brightness":152,"color_temp":232}'
debug 2023-03-31 07:34:19Publishing 'set' 'brightness' to 'woonkamer_tafel_lamp'
debug 2023-03-31 07:34:19Received MQTT message on 'zigbee2mqtt/woonkamer_tv_lamp_links/set' with data '{"state":"ON","transition":1.0,"brightness":152,"color_temp":232}'
debug 2023-03-31 07:34:19Publishing 'set' 'brightness' to 'woonkamer_tv_lamp_links'
debug 2023-03-31 07:34:19Received MQTT message on 'zigbee2mqtt/woonkamer_tv_lamp_rechts/set' with data '{"state":"ON","transition":1.0,"brightness":152,"color_temp":232}'
debug 2023-03-31 07:34:19Publishing 'set' 'brightness' to 'woonkamer_tv_lamp_rechts'
debug 2023-03-31 07:34:19Received MQTT message on 'zigbee2mqtt/woonkamer_spots/set' with data '{"state":"ON","transition":1.0,"brightness":152,"color_temp":232}'
debug 2023-03-31 07:34:19Publishing 'set' 'brightness' to 'woonkamer_spots'
debug 2023-03-31 07:34:19Publishing 'set' 'transition' to 'woonkamer_tafel_lamp'
debug 2023-03-31 07:34:19Publishing 'set' 'color_temp' to 'woonkamer_tafel_lamp'
debug 2023-03-31 07:34:19Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x04cd15fffe5d4886!
debug 2023-03-31 07:34:19Publishing 'set' 'transition' to 'woonkamer_tv_lamp_links'
debug 2023-03-31 07:34:19Publishing 'set' 'color_temp' to 'woonkamer_tv_lamp_links'
debug 2023-03-31 07:34:19Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x9035eafffe4e242a!
debug 2023-03-31 07:34:19Publishing 'set' 'transition' to 'woonkamer_tv_lamp_rechts'
debug 2023-03-31 07:34:19Publishing 'set' 'color_temp' to 'woonkamer_tv_lamp_rechts'
debug 2023-03-31 07:34:19Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x9035eafffe5aeb76!
debug 2023-03-31 07:34:19Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x04cd15fffe5d4886!
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_lampen', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_temp":232,"state":"ON"}'
info 2023-03-31 07:34:19MQTT publish: topic 'zigbee2mqtt/woonkamer_tafel_lamp', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":232,"do_not_disturb":null,"linkquality":69,"state":"ON"}'
debug 2023-03-31 07:34:20Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x9035eafffe4e242a!
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_tv_lamp_links', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":232,"do_not_disturb":null,"linkquality":40,"state":"ON"}'
debug 2023-03-31 07:34:20Missing colorTempPhysicalMin and/or colorTempPhysicalMax for endpoint 0x9035eafffe5aeb76!
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_tv_lamp_rechts', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_power_on_behavior":null,"color_temp":232,"do_not_disturb":null,"linkquality":94,"state":"ON"}'
debug 2023-03-31 07:34:20Publishing 'set' 'transition' to 'woonkamer_spots'
debug 2023-03-31 07:34:20Publishing 'set' 'color_temp' to 'woonkamer_spots'
debug 2023-03-31 07:34:20Received Zigbee message from 'afzuigkap', type 'attributeReport', cluster 'genBasic', data '{"65506":31,"65508":0,"appVersion":69}' from endpoint 1 with groupID 0
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp1', payload '{"brightness":152,"color_mode":"color_temp","color_temp":232,"color_temp_startup":366,"linkquality":87,"power_on_behavior":"on","state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_spots', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_temp":232,"state":"ON"}'
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp2', payload '{"brightness":152,"color_mode":"color_temp","color_temp":232,"linkquality":94,"power_on_behavior":null,"state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp3', payload '{"brightness":152,"color_mode":"color_temp","color_temp":232,"color_temp_startup":370,"linkquality":98,"power_on_behavior":"previous","state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_lamp4', payload '{"brightness":152,"color_mode":"color_temp","color_temp":232,"linkquality":87,"power_on_behavior":null,"state":"ON","update":{"installed_version":16784922,"latest_version":16784922,"state":"idle"},"update_available":null}'
info 2023-03-31 07:34:20MQTT publish: topic 'zigbee2mqtt/woonkamer_lampen', payload '{"brightness":152,"color":{"h":42,"hue":42,"s":41,"saturation":41,"x":0.3677,"y":0.3684},"color_mode":"color_temp","color_temp":232,"state":"ON"}'
ref https://github.com/Koenkk/zigbee2mqtt/issues/14714
@catduckgnaf thanks for checking, I do not believe so. There is also no firmware update. I do however have them paired in a group with philips hue lights.
It might be related. see if it goes away without hue lights in the group?
@catduckgnaf I tested it and it does not make any difference
Interesting, thank you
Hi, I've encountered the same issue with these light bulbs. Is there a fix or workaround available yet?
Happens here too, but only on very low brightnesses. Are we sure that this is not a firmware bug?
Probably not, as this behavior seems not to be observed using the Lidl/TuYa gateway or ZHA.
Okay, I've checked one of my Lidl lights for abnormal behaviors and found the following:
- Turn on with transition 0, brightness value: 1 Light will turn on normally
- Turn light off, with transition 0 or 1 Light will report back, that it's off, but stay on.
Sending a Turn_on command to this light in this state, will make it dim either immediately up (transition: 0) or slowly up (transition: >0), and then turn off.
The brightness value for this need to be 3 or higher.
So, looks like brightness 1 and 2 are broken, and you can't turn the light off with them.
Since brightness values 1 and 2 are below 2.55, I think it's safe to assume that the light can only handle percentage values, and as 2 is below 2.55, it “thinks” that it's at 0% brightness.
What I think is happening here, is that the lights are turned on with a brightness value of 1 or 2 and then get a command to dim up. This is causing the lights (sometimes) to flicker off again. I could not replicate this specific flickering behavior here, but I'm pretty sure that could be what's happening.
Otherwise, there's also the option that the light was commanded to turn off, while it was at brightness 1 or 2, but instead stayed on. The very low brightness state may make it non-obvious that the light stayed on, and the status showed it as off.
Turning it now on with anything above 2 will make it flicker off again.
So as @Koenkk suggested here this bug could be handled by putting an...
if user_requested_brightness > 0:
user_requested_brightness = max(user_requested_brightness, 3)
... somewhere in the converter code.
@Koenkk no, it doesn't.
So if you turn it on with brightness values 1-2 and turn it off, it will stay on.
This is also true if you turn it on with any brightness and just dim it down to 1-2 brightness values and then turn it off.
Lamp will report back "I'm off" and stay on.
If you now send a turn on with a higher brightness, 3-255 and transition 0, it will transition nearly instantly and turn off again (physically), but the status will remain "on".
If you send a longer transition, it will transition slower to this brightness and then turn off again (physically), but the status will remain "on".
Btw: I've inquired the Lidl support like a month ago regarding update URLs and described this problem, but not in so much detail, and asked if there's an update available for the firmware.
Their solution was to send me two new lamps, no questions asked, which have the same firmware bug.
So it's safe to say that we won't get any updates for the firmware anytime soon which would fix this.
Regarding reduced functionality: Yes, it will slightly reduce how much the lights can dim down, but it's not really worth discussing that.
If you're curious, there are power profiles for a lot of Lidl lamps available:
https://github.com/bramstroker/homeassistant-powercalc/tree/master/profile_library/lidl
@RubenKelevra try sending the off command twice in a row. The next time turning on the light will have it flicker on and off again. See https://github.com/Koenkk/zigbee2mqtt/issues/14714#issuecomment-1374600038 The brightness 0-2 bug is separate from this one IMO.
try sending the off command twice in a row. The next time turning on the light will have it flicker on and off again.
Ah thanks!
But it's more complicated, as both seems to be related: If the brightness 1-2 bug occours the lights will turn off again (physically), but if instructed to turn on again with a higher brightness setting, they will turn off (physically) but stay on. If instructed to turn off in this state and turn on again, they might flicker with a low chance.
So in commands:
turn_on brightness=1 or 2
turn_off
# light doesn't turn off physically, reports back: off
turn_on brightness >= 3
# light turns flickers / transitions on and turns back off (physically), reports back: on
turn_off # to clear the *on* status
turn_on brightness 1-255
# light will flicker with lower than 100% chance
The bug you described is:
# light is on normally with brightness 3-255
turn_off
# light turns off and reports back: off
turn_off
# light stays off and reports back: off
turn_on brightness 3-255
# light flickers, reports back: on
Main issue here is, that the light will report back: on, while it has flickered. Meaning once in this mode, it will basically stay there because:
# light is on normally with brightness 3-255
turn_off
# light turns off and reports back: off
turn_off
# light stays off and reports back: off
turn_on brightness 3-255
# light flickers, reports back: on
user switches the light, which is reportedly "on" in HA, off and on again:
# light flickers, reports back: on
user switches the light, which is reportedly "on" in HA, off and on again:
# light flickers, reports back: on
user switches the light, which is reportedly "on" in HA, off and on again:
# light flickers, reports back: on
user switches the light, which is reportedly "on" in HA, off and on again:
# light flickers, reports back: on
I tried contacting Lidl once again, this time via mail, asking for a contact for technical issues with their Zigbee firmware.
But I don't have high hopes. I think we should instead add workarounds here:
If light_status=off and command=turn_off:
skip command
and
if user_requested_brightness > 0:
user_requested_brightness = max(user_requested_brightness, 3)
Should hopefully fix both issues.
Update: Lidl responded today, and asked me if I want more broken lights as replacement 🥲
I've insisted that I want a technical contact to discuss the firmware issue instead.
Update: I got a technical support email address by Lidl and contacted them regarding both issues in their firmware. I've also asked for a URL for their firmware updates, as it is currently unknown where we could find those, if they are releasing them.
Thanks for the work @RubenKelevra ! I must say that when using ZHA there is no issue with the lights, so it is some what z2m related I guess? Looking forward to what lidl comesup with!
No, I think ZHA may keep track of the "off" status and won't send another "off" command to the light, if it already reported itself as off.
This can avoid sending duplicate commands to the lights, say if the light is in a HA group and some are off and some are on, and you send a turn-off to the group. I guess ZHA would skip the off lights, while Z2M sends an off command anyway.
Normally turning an off light off, should not cause any harm and has the advantage that if we missed an update by the light, and it is actually on, we can still turn it off.
However, the brightness=1 and brightness=2 bug should exist too, on ZHA. But you need dev tools or automations for it, as the normal GUI would just let you dim lights down to brightness=3, which is 1 %.
Would quickly test this, but last time I had some annoying bugs switching back and forth and had to reconnect a couple of Zigbee devices to my network. I would like to avoid that ;)
Ah gotcha, i am runnnig zha atm so I can test if you want me to test anything
@bruvv sure!
- Turn everything off which may control the light, like Adaptive Lighting or automations.
- Make sure to turn the Lidl light off normally in your GUI.
- Then go Development Tools -> "ACTIONS"
- Select light.turn_on, select a single Lidl light.
- Expand the view on the bottom, select "Brightness Value" and select
1, also add "Transition"0. - The light should turn on, but very faint.
- Then select light.turn_off from the action list, and run this against the light again. It should stay on.
- Go into your normal GUI, and the light should report, that it's "off" in the GUI.
- Go back to Development Tools -> "ACTIONS".
- Now select light.turn_on again from the action list, and run it against the same light, again with "Transition"
0but with "Brightness Value" and select3. - It should flicker on and then turn off again.
The "technical support" answered and asked random questions about which "App" I'm using and which "Mobile Phone".
Well, I've answered as best as I could, and pointed again to the fact that the lamps are:
- Reacting to Zigbee commands itself wrong
- The coordinator is not responsible, as this issue occurs with different coordinators
- My mobile phone doesn't matter, as it's not involved
- I'm using no app for this, as the Zigbee commands itself are interpreted wrongly.
Bet they've never heard of CC2652RB coordinator running zStack3x0 before ;)
I still doubt that this will lead to anything, but I mean it's worth a shot I guess.
@RubenKelevra when using zha and to this step: Then select light.turn_off from the action list, and run this against the light again. It should stay on. It turns off and also shows this in home assistant and the other steps i did too but perform normally and I have no flicker.
Alright, thanks!
I'll write a debug log later to see what's going on in Z2M.
I tried contacting Lidl once again, this time via mail, asking for a contact for technical issues with their Zigbee firmware.
But I don't have high hopes. I think we should instead add workarounds here:
If light_status=off and command=turn_off: skip commandand
if user_requested_brightness > 0: user_requested_brightness = max(user_requested_brightness, 3)Should hopefully fix both issues.
Is this something you can configure yourself in Z2M or is this something that needs to be added by the dev?
I have it working now by using an 'if' command in my automations in Home Assistant. But it would be more proofed when this would be baked in at the z2m level.
Info: I am experiencing this behavior with a cheap Tuya RGB led controller. but the issue is exactly the same and it is also fixed by not sending double off commands.
I have this issue with both HG07834B/HG08131B and 399629_2110. I'm using z2m with skyconnect, while waiting for my SMLIGHT SLZB-06.
Leaving this comment mostly to get an update on the question @Midifreakz posed.
If there is anything I can do on my end to test or maybe send emails to Lidl I'd be happy to. @RubenKelevra did you write to them in german or english?
Oh and happy new year! 🥳
@Adastreia
If there is anything I can do on my end to test or maybe send emails to Lidl I'd be happy to. @RubenKelevra did you write to them in german or english?
Hey!
I wrote them in German. However I doubt it would be an issue to write them in English.
I contacted Lidl, they gave me a contact mail address at Optimex, which is their partner for replacing lights if they are broken.
However, I eventually ran out of patients talking to Level 1 support. 🙄
In the meantime I found out, that neither Optimex nor Lidl actually imports these lights. So maybe there's an option to instead contact the company who does this instead?
That would be "OWIM GmbH & Co, Stiftbergstraße 1, 74167 Neckarsulm" according to the Datasheet provided for the lamps by Lidl.
I found this website Owim.com and I will send them an email this weekend.
Meanwhile, mostly for myself, I tested my lamps as instructed by @RubenKelevra
I fold this excursion as it might be out of scope for this issue, but I thought it might shed light on how inconsistent behavior these bulbs show, at least it did so to me.
Excursion
I wanted to see if it had something to do with color_mode and color_power_on_behavior.
If the bulb had previously been on in color_power_on_behavior": "previous" and had"color_mode": "color_temp" and I changed to a scene with xy-values it would turn on with color_temp and then go much slower than the others to xy. But more often than not, not responding at all and stay in color_temp. It also has a tendency to show in HA logs as "unknown" just as this happens. Lately it wont turn off either.
Turns out that one (1) of my 2 Livarno Home E14 candle RGB+CCT (HG07834B/HG08131B) was consistent. Even when failing at the last step, it did so consistently. No matter which combination of color_power_on_behavior and color_mode it was in.
| HG07834B/HG08131B | ||
|---|---|---|
| light.turn_on brightness 1 | ✅ | Just not very faint |
| light.turn_off | ✅ | |
| light.turn_on brightness 3 | ❌ | Turns itself off. GUI says "ON" |
The others were all over the place and I will put some tables below.
Livarno Home E27 bulb RGB+CCT
| initial/previous/customized | xy | xy | xy | color_temp | color_temp | color_temp |
|---|---|---|---|---|---|---|
| light.turn_on with brightness 1 | Blinks once then off | Blinks once then off | ✅ | ✅ | ✅ | ✅ |
| light.turn_off | Stays off GUI "OFF" | Stays off GUI "OFF" | ✅ | Turns itself off. | ✅ | ✅ |
| light.turn_on with brightness 3 | ✅ | ✅ | ✅ | Turns on, stays on | Turns off | ✅ |
Livarno Home E14 candle RGB+CCT (the one not as consistent)
| initial/previous/customized | xy | xy | xy | color_temp | color_temp | color_temp |
|---|---|---|---|---|---|---|
| light.turn_on with brightness 1 | Blinks once then off | ✅ | ✅ | ✅ | blinks and stays off | blinks and stays off |
| light.turn_off | Stays off GUI "OFF" | ✅ | Turns off | ✅ | Stays off | Stays off |
| light.turn_on with brightness 3 | ✅ | Turns off | Turns on, stays on | Turns off | ✅ | Turns off |
Livarno Lux Ceiling Panel RGB+CCT
399629_2110 - TS0505B
| initial/previous/customized | xy | xy | xy | color_temp | color_temp | color_temp |
|---|---|---|---|---|---|---|
| light.turn_on with brightness 1 | Turns off after 3s. Brightness 3 | ✅ (with brightness 3) | ✅ | ✅ | ✅ | Turns off |
| light.turn_off | Stays off, GUI "OFF" | Turns off | ✅ | ✅ | ✅ | ✅ |
| light.turn_on with brightness 3 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
I learnt a few things by this!
- They do not always take the right brightness-value. Sometimes it would be 8 when I sent 3. Sometimes 3 when I sent 1.
- Rather than flickering mine more often than not just turn off.
- Brightness in a lightcard on the dashboard doesn't always correspond to the brightness-value in z2m.
- The brightness-value on the "state"-tab in z2m does not update if you change device in the dropdown.
- If the lamp was still on after light.turn_off, light_turn_on will turn it off.
- When it was already off cause it failed light.turn_on with brightness 1, then it just blinks quickly and stays off.
- Switching to a tab in the z2m UI made one light actually take the command and start.