Core: No color temp support with Tradfri RGB via hue hub

[FezVrasta]

Home Assistant release with the issue:

Last working Home Assistant release (if known):
N/A

Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian

Component/platform:
https://www.home-assistant.io/components/hue

Description of problem:
The IKEA Tradfri RGB bulbs don't seem to support to set their color using kelvins. I can only provide color using the color wheel.

1. Link a IKEA Tradfri RGB bulb to a Hue bridge 2.0
2. Link the Hue bridge to Home Assistant (using auto discovery is fine)
3. Click on the bulb in the Home Assistant UI
4. Notice only the color wheel is available, no temperature bar is visible

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
I'm not sure if it's a bug or if this kind of bulb doesn't really support colors expressed in temperatures. But even if it doesn't, couldn't Hass convert the kelvin to an RGB value?

[Phontana]

This is related to https://github.com/home-assistant/home-assistant/issues/14525.

[FezVrasta]

@pvizeli I can still reproduce this issue with 0.72.1

[FezVrasta]

This issue shouldn't be related to #14887 at all, since in my case the bulb is being controlled by the Hue bridge rather than the Ikea Gateway.

It must be something in the Hue bridge component or in the way the bulb is handled in Home Assistant, since I can control the bulb temperature just fine using the Hue app or API.

@pvizeli may you re-open this?

[MartinHjelmare]

Please provide a step by step instruction to reproduce the issue. Also fill in your relevant config section. Eg the automation that is used. Then we can reopen.

[FezVrasta]

I added the steps. There's no relevant configuration, everything can be reproduced by simply using the auto discovery tool.

[MartinHjelmare]

This was limited in pytradfri:
https://github.com/ggravlingen/pytradfri/pull/162

We base the supported features in the tradfri home assistant light platform on what pytradfri reports.

Please take the discussion with the pytradfri team in that repo. They probably have a good reason to limit this?

[FezVrasta]

I already did open an issue on that repo:
https://github.com/ggravlingen/pytradfri/issues/177

He said that pytradfri only communicates with Ikea gateway, so my problem must be related to some other code.

[MartinHjelmare]

If you aren't using the tradfri gateway you can't use the tradfri component in home assistant. How are you integrating the lights?

[FezVrasta]

I'm not using the Tradfri component I guess, I'm using the Hue component. I'll update the issue, sorry for the confusion.

[FezVrasta]

Here's a picture of the RGB bulb interface:

[FezVrasta]

And these are the info from the entities list page, if they can be useful:

[MartinHjelmare]

This was last changed in the hue light platform in this big light refactor PR:
https://github.com/home-assistant/home-assistant/pull/11288

Maybe @armills knows about the background?

[emlove]

Can you add some logging to determine what type is being reported for this light?
https://github.com/home-assistant/home-assistant/blob/2ff5b4ce9547e1d0b15904ee1eb74906eb8f7608/homeassistant/components/light/hue.py#L281

Also, can you please provide the full model number for this bulb? Not all RGB bulbs support setting color temperature.

[FezVrasta]

Sorry I'm not so used to Python, what's the right way to log it?

Regarding the support, the bulb does support it because I can control its color temperature from the Hue app just fine.

[FezVrasta]

The Hue app says the bulb is a "TRADFRI bulb E27 CWS opal 6... (something)" the full model is cut off 😓

[Imbuzi]

I have exactly the same problem as you have, but I'm not connecting my bulbs through the Ikea TRADFRI gw, I'm using the ZHA component. Is this issue also linked to a pytradfri limitation, or not ?

[FezVrasta]

No it's not related to pytradfri, pytradfri only handles the Ikea gateway to Hass communication. In our case we use different bridges.

[Imbuzi]

Ok so I have to open a new issue.
Thanks :smile:

[FezVrasta]

This issue is for non Ikea gateway issue

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[FezVrasta]

The issue is still there

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[FezVrasta]

The issue is still there. As I told on my previous reply

[ltpitt]

I can confirm the same issue on my end but I am using Ikea Hub, no color temperature is shown but I can see colors.

Tradfri hub is enabled in my config and everything works 100% fine with non-RGB bulbs (I can change white temperature).

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[FezVrasta]

Not stale

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[FezVrasta]

Why is this issue labeled with waiting-for-reply? Reply from who? About what?

Also, please shut the fucking bot up, it's useless and rude on people that are trying to participate to this open source project.

[frenck]

please shut the fucking bot up, it's useless and rude on people that are trying to participate to this open-source project.

The waiting-for-reply is an older label, let me just remove that. Easy.
Please mind your words. Thanks 👍

[FezVrasta]

It's since October that this bot is constantly trying to close this issue, and nobody from the project members did anything to address this problem.

I'm sure this is not the only issue that has been almost closed (or closed all together) because of this useless and rude bot, what's the purpose of it?

[frenck]

Its purpose is explained by the bot itself, which is not a rude message IMHO. It is just asking if the issue still persists or not.

For more information about stalebot: https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea

[Adminiuga]

The bot is not the rude one here.

[noxhirsch]

Same problem here: No color temp for the RGB bulb.

[FunctionalHacker]

Just discovered a workaround to control the color temp of trådfri bulbs: use a light group, the color temp slider is visible there and the bulbs will follow suit.

I'm on deconz/conbee but I understand that this issue happens for all that do not use the trådfri gateway.

EDIT: using a service call directly to set a kelvin value on the bulb directly works too, so the only issue here is the actual popup in the web UI. I have no familiarity with the HASS codebase but I suspect that the way it checks for light capabilities is not working. We could just override that on all the affected bulbs (if there is a way to reliably detect them) and show the color temp slider.

It seems that the deconz webui has the same issue. I will have a look on their issue tracker later today if they have made any progress on this, so we can share our findings.

[ltpitt]

Hi @ReekyMarko !

I am using the Ikea Gateway but the problem is the same.

The same identical issue is shown in Alexa (without using HA).

[FunctionalHacker]

Aah okay so it's even worse. Can you try if you are able to control the temperature using a group, like I am?

[Flurkmark]

@ReekyMarko What I have found is this:
The light identify as 'color temperature lights' with a CT value on startup. If you touch the CT value it will change the color of the light, not update it and start reporting as a XY light.

If you change CT with ct_inc instead it not only works, but restores the CT value, until you change it again. Happens to all three types if IKEA lights that I have.

Groups sounds like a workaround for a while.

https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1861

[nic0dk]

Just discovered a workaround to control the color temp of trådfri bulbs: use a light group, the color temp slider is visible there and the bulbs will follow suit.

I'm on deconz/conbee but I understand that this issue happens for all that do not use the trådfri gateway.

EDIT: using a service call directly to set a kelvin value on the bulb directly works too, so the only issue here is the actual popup in the web UI. I have no familiarity with the HASS codebase but I suspect that the way it checks for light capabilities is not working. We could just override that on all the affected bulbs (if there is a way to reliably detect them) and show the color temp slider.

It seems that the deconz webui has the same issue. I will have a look on their issue tracker later today if they have made any progress on this, so we can share our findings.

any chance that i can see you config for that @ReekyMarko thanks for the workaround!

[Flurkmark]

I didn't write about it here, since I thought the fix was going to be in deconz already.
The bug is in deconz and I know where. I told the devs some weeks ago.
If you compile the plugin yourself you can just comment out one line. I can supply a library that is fixed for 2.0.69 if you have access to your filesystem. Best if you complile yourself as described in the README.

Comment out this line in : zcl_tasks.cpp (line 384)

useXy = useXy || task.lightNode->manufacturerCode() == VENDOR_IKEA;

That is make it look like:

//useXy = useXy || task.lightNode->manufacturerCode() == VENDOR_IKEA;

[nic0dk]

I didn't write about it here, since I thought the fix was going to be in deconz already.
The bug is in deconz and I know where. I told the devs some weeks ago.
If you compile the plugin yourself you can just comment out one line. I can supply a library that is fixed for 2.0.69 if you have access to your filesystem. Best if you complile yourself as described in the README.

Comment out this line in : zcl_tasks.cpp (line 384)

useXy = useXy || task.lightNode->manufacturerCode() == VENDOR_IKEA;

That is make it look like:

//useXy = useXy || task.lightNode->manufacturerCode() == VENDOR_IKEA;

thx for the reply @Flurkmark i can see that they haven't updated the zcl_tasks.cpp file in the lastest version, my second problem is that i'm using the docker version https://github.com/marthoc/docker-deconz and i have no luck to locate the file, and even if i do, i somehow need to update the dockerfile to get the new version of the file - my docker and linux knowledge might be a bit limited to figure it out :)

nice you found the reason for the problem, ill properly just wait for a new release with the fix :)

[sverleysen]

@Flurkmark I have created a PR for this change. Hopefully it will be merged.
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/2507

[llonca13]

@Flurkmark I compiled rest-plugin with your solution but Im having trouble figuring out which file I need to replace from my build folder to my marthoc/deconz docker. Any hint would be much appreciated :)
I tried finding zcl_tasks.o in my container but no luck

[Flurkmark]

@Flurkmark I compiled rest-plugin with your solution but Im having trouble figuring out which file I need to replace from my build folder to my marthoc/deconz docker. Any hint would be much appreciated :)
I tried finding zcl_tasks.o in my container but no luck

I don't use doicker, just a .deb install. The file:
/usr/share/deCONZ/plugins/libde_rest_plugin.so needs replacing.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[FezVrasta]

🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬

[johnekarlsson]

This is still very much an issue for me. :(