Philips hue ligths color_temp state gone

[evaliukonis]

The problem

Turn on light with color_temp and it visible in state for 1 or 2 seconds and gone. Problem only with "Extended color light". With Philips lights works fine.

What version of Home Assistant Core has the issue?

2021.12.1

What was the last working version of Home Assistant Core?

2021.11.5

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Philips Hue

Link to integration documentation on our website

No response

Example YAML snippet

service: light.turn_on
target:
  entity_id: light.my-light
data:
  color_temp: 155
  brightness: 255

Anything in the logs that might be useful for us?

State after call service:
min_mireds: 155
max_mireds: 495
supported_color_modes:
  - color_temp
  - xy
color_mode: color_temp
brightness: 255
color_temp: 155
hs_color:
  - 44.098
  - 2.43
rgb_color:
  - 255
  - 253
  - 248
xy_color:
  - 0.328
  - 0.334
mode: normal
dynamics: none
friendly_name: My Light
supported_features: 32


State after few seconds:
min_mireds: 155
max_mireds: 495
supported_color_modes:
  - color_temp
  - xy
color_mode: xy
brightness: 255
hs_color:
  - 256.174
  - 45.098
rgb_color:
  - 171
  - 140
  - 255
xy_color:
  - 0.2595
  - 0.1838
mode: normal
dynamics: none
friendly_name: My Light
supported_features: 32

Additional information

No response

[marcelveldt]

Let me guess, this happens only with a 3th party light (not Philips/Signify) ?
We've checked in a small fix for this today in the library which might fix your issue.
Please test again once the bugfix update 2021.12.2 is released and report back, thanks!

[probot-home-assistant]

Hey there @balloob, mind taking a look at this issue as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

hue documentation
hue source
_{^{(message by IssueLinks)}}

[marcelveldt]

@EddyK69 please not hijack another one's issue report.
Kelvin 1000 is invalid, Minimum will be around 2000 (mired 153).
Next HA bugfix release will fix the error, so it will default to the lower bound (153 mired) if you send in a value that's out of range

[evaliukonis]

No I send correct value. Ligth color and temp is correct just gone color_temp value from state and this issue only for 3th party lights. I use light template with color_temp and brightness and it wont work without color_temp state

[marcelveldt]

No I send correct value. Ligth color and temp is correct just gone color_temp value from state and this issue only for 3th party lights

Yea, please wait until the bugfix 2021.12.2 is released and report back, thanks

[evaliukonis]

Still same problem exists, but it looks like Philips hue bridge problem. On philips app state also wrong.

[marcelveldt]

OK, maybe a 3rd party light that needs some firmware update ?
Some lights are known to give strange issues when connected to Hue

[evaliukonis]

I have Conbee2 with zigbee2mqtt and moved one light on it. Light work like expected. There is no possibility upgrade firmware for this 3rd party lights.

[marcelveldt]

I think this is caused by the fact that the light doesn't properly report its capabilities to the Hue bridge, the mirek_schema will be empty.

There's also an attribute on the "ColorTemperatureFeature" in the api called "mirek_valid" and that's what determines if the light is in color temperature mode or color mode.
My guess is that with this light this one is always false.

https://developers.meethue.com/develop/hue-api-v2/api-reference/#resource_light_get

[achap01]

Hello,
Sorry i'm french...

I've the same problem with my HUE lamps since the last upgrade of HA 2021.12.2. I do it last day at 22h00.
Before, all my hue lamps were OK when i want to toogle.

Now, when the HUE lights are off, the toggle button return ON automatically after a few instant. After, i can't switch the lights. I must recharge the integration HUE and all is OK for the first operation.
I have no problem to command the light when i use directly the HUE application.

What's is the solution ? Do i must reload the latest version of HA or wait before a new release which fix this bug ?
Thank you for your answer...

Sincerely,

[marcelveldt]

@achap01 that is another issue, not related to this one.
See here: #61926
You can either revert to 2021.12.1 (which has the same issue but not as bad) or wait for 2021.12.3 (which fixes it)

[achap01]

Thank you for your answer ...

And excuse me for my bad english ....

I'll wait for the new release.

Sincerely