-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TRADFRI bulb E26 WS opal 980lm reports color mode as "xy" #1861
Comments
I can confirm this. When I query my bulbs state (httpI got this in return: { but not always...sometimes it seems to be correct: { |
@manup can we get a comment on this? |
I think since these are are plain color temperature lights we can fix the color mode to Looking forward to get this fixed for 2.05.70. |
Great! It would be nice if we could separate what "hascolor": true, means to actually color and add something like a haswhitespectrum or similar while we're at it :) |
Same issue with the IKEA/TRADFRI "LEPTITER Recessed spot light" (which isn't officially listed as supported but working well besides):
|
Does anyone have a workaround until 2.05.70 comes out? My home automation's principal investor is getting upset that the closest I can come with the color slider has a green tint XD |
@manup I also would very much appreciate at least a commit to fix this. I am stuck in a project and can't write anything more until I can reliably pull ct from the light. I understand that you guys are busy, but for many people this is a major issue. Danke. |
@Flurkmark I think the fix is in for 2.05.70, we just have to wait for the build. I think this weekend I will try a manual build from the source and report back on if it works or not. Is there a nightly available @manup ? |
@YAMLcase Have you tried a build? Version is bumped to 2.05.70, no release. I can't find anything in the commits that seems to fix this, then again I might have missed it. |
This is not fixed as of now, version 2.05.70, tried a build. Pretty bad bug for me, since I can't change color temp, kind of the reason for buying color temp lights.. |
The same thing happens for all sizes of IKEA Floalt panels, I'm already on deCONZ 2.05.70:
|
@manup |
I'm having the same issue |
I have the same issue |
Same issue here. |
Same issue here. |
Same issue here with IKEA Floalt 30x30 panels using deCONZ 2.05.72. In phoscon app, color temperature slider works as expected, but after connecting TRADFRI or Hue Dimming switches, setting color temperature to cooler on switches is unresponsive and results in mismatch of bulbs reporting back their current color temp and actual color state. EDIT: I think issue 2068 is related. |
Same issue with TRÅDFRI bulb E14 opal 400lm lamps... |
Same issue here with an Ikea Bulb. When Home Assistant is restarted the attribute "color_temp" is enabled. However, every time I use it in automation it disappears... |
Does this still fixes this issue? Or did you encounter some other issues with this change? |
It fixes it, I'm still on .69 since it's stable for me. It was supposed to be a fix for deconz build in scenes afaik. I don't use them, but I guess they will missbehave with IKEA light after the fix. |
@manup, any update? |
@Kane610 @manup any plans on fixing this? Just some feedback would be great to know is this being worked on, or we should start looking for alternatives (new bulbs etc)... home-assistant/core#14554 (comment) |
I have made a PR for this fix. Hopefully they will merge it. |
I didn’t do it initially, since I thought it would be fixed quickly after I found it. Hopefully it will get attention now. They should just back out the commit that introduced it and redo the scene fix in my opinion. Fingers crossed... |
Even with this fix I still don't get color_temp reported back.. |
I have this issue as well. Very annoying. If I VNC into deCONZ I can set the color temperature using the color control cluster of the light. It then also shows the correct value in Home Assistant/OpenHAB. But it seems the Phoscon interface as well as the connected Home Assistant do not set a color temperature value but a XY value instead... |
See #2507 |
Same issue with all my GU10 WS TRADFRI lamps. Investigated on this and found following behavior:
Hope this helps for finding a solution |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The REST api seems to be reporting this bulb as color mode "xy" even though it's only a color temperature bulb:
Setting the color temperature still works correctly, both via the REST api and the webapp, but it seems odd. Attempting to change the color mode over the REST api does not return anything, no errors or success:
The text was updated successfully, but these errors were encountered: