Issue on LIDL Livarno Lux light strip #4539
Labels
Comments
Mimiix
added
Device Improvement
|
I don't have the lightstrip to test, but the E27 colour bulb doesn't support Doing a PR not to expose the unsupported |
|
@ebaauw Took a test on my ledstrip
Ledstrip seems to not support it either. |
|
I would love to test it too but I don't know how to reach this windows. I logon in deconz app via VNC and then? |
|
Go to the Color Cluster (check the wiki on how to read/find clusters). Then scroll a bit down. |
|
I confirm that
|
|
Hi all, I noticed that my Model HG06104A has now only Color Temp and brightness in Phoscon. No more color control. Why I cannot change color anymore? @Mimiix maybe I changed some value in the color cluster without intention? Have you the same issue? |
|
@jokerigno I have no clue. Best to ask on the Phoscon repo. |
|
I will but I think there's more than this. The led strip model is know unknown (previous was HG06104A as reported in original post). |
|
@ebaauw Based on dresden-elektronik/phoscon-app-beta#362 it now broke the ledstrip. |
|
Another thing that I noticed in HA (don't know if can help, I share it because HA developer told me that integration just copy info from deconz ) is that every time brightness is and then change color brightness is changed automatically to 219. Moreover in HA UI the color is not reported correctly. |
Are you telling me that HA and even Phoscon are using If not, please post screenshot of Basic cluster and list the |
|
The Lidl Melinera Christmas Stripe from #3716 are also broken. The Device is broken since the latest stable release and cant be used anymore. basic cluster:
"27": {
"etag": "fed8c4c3652aa731b281608a962ea4da",
"hascolor": true,
"lastannounced": null,
"lastseen": "2021-04-06T18:45Z",
"manufacturername": "LIDL Livarno Lux",
"modelid": "HG06467",
"name": "Color dimmable light 27",
"state": {
"bri": 254,
"colormode": "hs",
"on": true,
"reachable": true
},
"swversion": null,
"type": "Color dimmable light",
"uniqueid": "bc:33:ac:ff:fe:73:3a:4a-01"
}, |
|
Any good news about this bug? |
|
Ha yes, some field are missing in the JSON Do you have the last version working ? BTW, this is the only part than can set hue field ? |
|
No, I stay on 2.10.4 |
|
So the 2.10.4 is still working or it s the first not working version ? |
|
2.10.4 doesn't work. |
|
Are you able to compile the code to test ? I realy don't see the problem from the new version, but I don't understand how the field "hue" and "sat" can be in the Json atm. In the file de_web_plugin.cpp around line 2815 can you add Edit: I think i have found the problem Can you try instead replacing this line in product match.cpp ,
by
|
|
This issue is about the regular lightstrip not supporting colorloop. Please open a new issue for the Xmas lightstrip. If you had done so in the first place, I would have seen it right away. |
|
Same bug as 2.10.4. |
|
@ebaauw why did you close this issue? |
|
Because the original problem for this issue has been addressed, see above. |
But the solution broke the component. Do you want me to open another ticket? |
|
Double-checking my LIDL RGB bulb. That's looking good, except I just set the colour using Checking with the sniffer, the light reports Current Hue and Current Saturation, even though it doesn't support setting these. The values are bogus, however; when I set |
|
F*ck me. deconz-rest-plugin/de_web_plugin.cpp Lines 3249 to 3253 in 59eee63 I'll add a check that the light also doesn't expose |
|
Thank you for working on it. Another thing that I noticed and reported in this post. By default brightness is 219. Everytime I change brightness color is changed to default value. Everytime i change brightness and then color brightness is changed again automatically to 219. What am I expecting ? That if I set brigthess to 255 and then change color brightness stays at 255. And when I change color and then adjust brightness color stays the same instead of default one. |
|
By "color brightness" do you mean colour temperature (the |
|
Sorry, a comma was required: |
In your opinion this can also cause the fact that entity icon color doesn't change based on entity light color? |
I'm not seeing that. Are you sure you don't have an automation running to reset the brightness. Do you mean brightness of the actual light or brightness as reported by the API?
Yes, the light changes colour alright, but the API reports the last colour temperature. This behaviour should be fixed by my commit above. |
|
No I had just setup default behaviour with light profile with brightness 255 and a specific color. In this case brightness was always reset to 255. Then I removed it and reboot HA. After that default color was warm white with brightness 219 and the issue was still there with value 219 against 255. |
|
Please try these changes when the next beta is released. If it still behaves weirdly, please capture a log of the API commands sent and the websocket notifications received. I’m sorry, I have no clue how to do that in HA. |
|
It seems to work again in HA. Now entity icons are in RGB according the lamp colour. |
|
Light status is correct. But the issue with brightness restored to default every time is still present. |
|
Brightness remains the same when switched off ; Even using physical switch. |
|
After 15 minutes without current, when I switch on, lamps keep their brightness but HA reports full brightness even if the correct value should be less. |
@ebaauw here is the log. Basically everytime as reported also by @LeoeLeoeL light is reset to default settings (brightness and color) |
|
Please, next time attach a log file instead of listing large amounts of text. The API seems to be working correctly; I don't see any discrepancies between the requested and reported brightness (except that 255 is not a valid value for Here HA is setting on, brightness, and colour: deCONZ accepts the command: Then it sends a websocket notification as a result of the command: Next, it sends a notification for Which is followed by the attribute report for deCONZ correctly reports |
|
OPS. Sorry. And sorry for 219. I changed default value to 255. I don't know what you see but what I see is not that correct. Basically I switched light on and then changed 1) color 2) brightness. As told in previous post every time light is reset to defaul values. |
|
From your log, deCONZ is reporting the brightness requested by HA. If that's not what you expect, you need to check the HA side. I do see HA sending requests to change the brightness to 255. |
|
After a power loss, Deconz and HA report a brightness of 255 even if the real brightness of the lamps is 1. |
|
@ebaauw don't know if is an attribute that can be implemented or not. I tried to change PowerOn OnOff behaviour but it reports unsupported attribute.
I avoided creating another issue because maybe it's just a lack of feature (like colorloop). Don't you agree? |
|
@jokerigno it's something the device needs to support. So unfortunately this can't be implemented by us 😢 |
|
For curiosity, I bought the Lidl bridge yesterday. |
I was afraid of it but I asked you just to be sure. Thank you for your feedback :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I just buyed a LIDL Livarno Lux (HG06104A) and I tried to switch on colorloop functionality in Home Assistant but nothing happens. I opened an issue #47287 but it seems that in not related to the integration but to HW and Deconz.
Steps to reproduce the behavior
Expected behavior
Light change color randomly
Screenshots
Environment
deCONZ Logs
I tried to add logs. I can see them in deConz but I'm unable to paste outside VNC.
Additional context
The text was updated successfully, but these errors were encountered: