Closed tumtumsback closed 2 years ago
Not sure why but the Template seems to be getting thrown off:
Describe the bug: Ledvance Flushmount TW fixture appearing to be an RGB light instead of a TW light
Steps to reproduce the behavior: When you open the entity within Home Assistant, it shows as an RGB light rather than Color Temperature / White Spectrum
Expected behavior: I expected a CT slider instead of an RBG wheel
Screenshots: See above
Environment: Host system: (Raspberry Pi / PC / NAS) Proxmox VM Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / Marthoc Docker container / Windows / Virtual Machine) Home Assistant deCONZ Add-on Firmware version: (26xxyy00) 26580700 deCONZ version: (2.xx.yy) 2.12.6 Device: (ConBee I / ConBee II / RaspBee I / RaspBee II) ConBee II Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II yes Is there any other USB or serial devices connected to the host system? If so: Which? No
deCONZ Logs: 2021-10-22 14:29:55 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"id":"47","lastannounced":"2021-10-04T15:47:46Z","lastseen":"2021-10-22T18:29Z","manufacturername":"LEDVANCE","modelid":"Flushmount TW","name":"Hallway","swversion":"Sep 19 2017","type":"Color dimmable light","uniqueid":"f0:d1:b8:00:00:02:a6:1f-01"},"e":"changed","id":"47","r":"lights","t":"event","uniqueid":"f0:d1:b8:00:00:02:a6:1f-01"}
Additional context: @Kane610 in the GitHub ~ Home Assistant ~ Addons section said the following:
"...Hello! This isn't the right repository to report the issue, it should be the ha core repo. But since your log clearly shows that this device doesn't properly report support color temp this issue can be closed.
Probably there is an issue with the device support in deCONZ. You should report this issue here https://github.com/dresden-elektronik/deconz-rest-plugin
The Integration looks for color temp value here: https://github.com/Kane610/deconz/blob/0b39827b8a88c15a3accba9d9d3bf376c9b7d589/pydeconz/light.py#L97
But as you can see there is no "state" "ct" value..."
'manufacturername': 'LEDVANCE', 'modelid': 'Flushmount TW', 'name': 'Hallway', 'state': {'alert': 'none', 'bri': 254, 'colormode': 'ct', 'effect': '0', 'hue': 0, 'on': False, 'reachable': True, 'sat': 254, 'xy': [0.3805, 0.3769]}, 'swversion': 'Sep 19 2017', 'type': 'Color dimmable light', 'uniqueid': 'f0:d1:b8:00:00:02:a6:1f-01'}, '48': {'etag': 'a4577a33675da4bb9fe5b456e72949ba', 'hascolor': False, 'lastannounced': None, 'lastseen': '2021-10-22T17:57Z'
That is what is seen in Home Assistant -- you can see what @Kane610 means by the "State"
Hello, I m seing 2 thing to try.
For the second one you just need the GUI and have a recent deconz version, then
Right clic on the node then "edit DDF" and here using drag an drop you can add remove field, So just add"state/ct" to start, then save the DDF and make a "hot reload" on the menu.
You can chnage the type too 'Color dimmable light'> 'Color temperature light'
Smanar can you send any screenshots? I am not able to find "Panels --> Control --> Normal mode" nor can I find anything about "DDF"
When I go into deCONZ VNC GUI, I can see the Color dimmable light setting, but I cannot "write" over that as it's only letting me interact with the "node" in a read-only sort of fashion
Smanar can you send any screenshots? I am not able to find "Panels --> Control --> Normal mode" nor can I find anything about "DDF"
When I go into deCONZ VNC GUI, I can see the Color dimmable light setting, but I cannot "write" over that as it's only letting me interact with the "node" in a read-only sort of fashion
Are you on the latest beta?
I am not on any beta version, Mimiix
Running method: Home Assistant deCONZ Add-on Firmware version: 26580700 deCONZ version: 2.12.6
If this could just be fixed so that deCONZ sees this light for what it really is (White Tunable), then it could report to Home Assistant (via REST) the correct value of "color temperature light" and then bob's my uncle.
Wondering how hard this would be for the deCONZ devs?
If this could just be fixed so that deCONZ sees this light for what it really is (White Tunable), then it could report to Home Assistant (via REST) the correct value of "color temperature light" and then bob's my uncle. Wondering how hard this would be for the deCONZ devs?
The DDF files are available since the last beta. Either way as you are on the ha addon you have to wait for a fix on next stable anyway.
The ddf are descriptor files and thus define how a device is presented in the api. Perfect for fixing this issue.
In your case, as you don't run betas, I won't expect a solution before the 15th of November ( if we even release a stable by than).
@Mimiix I totally get that -- I've been living this way for well over a year now, so, not in any rush. I think it would be great if it were fixed in a future version, and just wanted to make sure I've brought attention to this issue via the proper channel(s) in hopes that it could eventually be fixed naturally.
@Mimiix I totally get that -- I've been living this way for well over a year now, so, not in any rush. I think it would be great if it were fixed in a future version, and just wanted to make sure I've brought attention to this issue via the proper channel(s) in hopes that it could eventually be fixed naturally.
You did.
I'll try to get this in the next version but no promises :)
Fingers crossed :) thank you, Mimixx
@tumtumsback are you able to run 13.1 to test and help fix it ?
I'd be happy to help -- I can snapshot my hass proxmox VM quite easily so if I mess anything up, I can just revert to snapshot. Let me know whatever it is I can do to help.
You need to run native deconz or docker you can't do it on HA addon.
yikes -- I'm not sure that's in my skillset
Just install a vm with Ubuntu and install the deconz beta in there :)
that's not bad I guess -- I'd have to test by passing the conbee ii to that VM instead, which means all of my zigbee stuff would temporarily be down ... let me think on it -- thanks
Otherwise I'm afraid we have to wait until ddf are stable and then adjust the ddf for this device
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.
Describe the bug
Steps to reproduce the behavior
Expected behavior
Screenshots
Environment
deCONZ Logs
Additional context