Activating light scene doesn't change colour temperature in Hue bulbs

Ascathon commented 1 month ago

The problem

I yesterday noticed activating a GUI created light scene doesn't activate/change the colour temperature on my Hue bulbs. Triggering the scene does change brightness (or turn them on), but leaves the colour temperature on the previous setting

I restarted Home Assistant, I restarted the Hue bridge. Processed all available updates on either hass and Hue devices.

What does fix it for me is removing the "effect: None" from both the entities below.

Since it is summer having lots of daylight I'm not sure on which day exactly this issue has arisen but pretty sure it is very recent. Might be something changed on Hue's end but that I cannot verify. I wrote down it is an integration issue but it might as well be a general scene thing.

What version of Home Assistant Core has the issue?

core-2024.7.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Philips Hue

Link to integration documentation on our website

https://www.home-assistant.io/integrations/hue

Diagnostics information

No response

Example YAML snippet

- id: '1641320138684'
  name: Hal en overloop 10%
  entities:
    light.hal:
      min_color_temp_kelvin: 2202
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 454
      effect_list:
      - None
      - candle
      supported_color_modes:
      - color_temp
      color_mode: color_temp
      brightness: 26
      color_temp_kelvin: 2857
      color_temp: 350
      hs_color:
      - 28.077
      - 60.925
      rgb_color:
      - 255
      - 172
      - 99
      xy_color:
      - 0.51
      - 0.386
      effect: None
      mode: normal
      dynamics: none
      friendly_name: Hal
      supported_features: 44
      state: 'on'
    light.overloop:
      min_color_temp_kelvin: 2202
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 454
      effect_list:
      - None
      - candle
      supported_color_modes:
      - color_temp
      color_mode: color_temp
      brightness: 26
      color_temp_kelvin: 2857
      color_temp: 350
      hs_color:
      - 28.077
      - 60.925
      rgb_color:
      - 255
      - 172
      - 99
      xy_color:
      - 0.51
      - 0.386
      effect: None
      mode: normal
      dynamics: none
      friendly_name: Overloop
      supported_features: 44
      state: 'on'
  icon: mdi:lightbulb-group
  metadata: {}

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

Hey there @balloob, @marcelveldt, 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!

Code owner commands

Code owners of `hue` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hue` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

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

Ascathon commented 1 month ago

This also happens when I trigger a scene created with the scene.create service and using the group entity for the lights in the snapshot parameter. Triggering that scene also turns the lights on in an instant, no fade as usual.

Also happens with the "broken" scenes from the opening post. They don't turn on with a half second fade but just a quick flash.

DulinDuskhawk commented 1 month ago

Same here. Only a few of the lights respond to the scene change.

Changing color directly works fine.

Ascathon commented 1 month ago

Same here. Only a few of the lights respond to the scene change.

Changing color directly works fine.

Could you also please try to remove the "effect: None" line form all scenes or one specific and see what it does after reloading.

DulinDuskhawk commented 1 month ago

Yep. Removing that line in all scenes fixed it. But gets added again after each edit from GUI....

Thx for now!

bcolyn commented 1 month ago

Also affected here, can confirm that the workaround does the trick until scenes.yaml is edited again from the GUI (and effect: None is added again).

Ascathon commented 1 month ago

I don't know if anyone has non Hue lights to try the same. If it is isolated to the Hue integration or if that label should be removed.

DulinDuskhawk commented 1 month ago

I got mixed brand lights in my scenes. The effect: None only gets added to the Hue lights. The other lights don't have any issue.

One thing stands out for me: I see that None is with capital N, all other effects are without capitals... does that have effect?

Kappade commented 1 month ago

Found this thread after my search of why my scenes with HUE lights is failing. Glad i am not the only one. What i want to add is that the issue seems combined with HA Scenes and Hue lights. I've got 2 scenes for the same room and based on weekdays or weekend different colors should go on with Hue lights and Nanoleaf. Since this month or so i noticed only brightness would change on the Hue lights while the Nanoleaf did switch to the other colors. Did not pay much attention to it but investigated further today. What i see is that my 2 differents scenes are all messed up and when i fix scene 1 , i would then see the config/color choices of scene 1 show up also in scene 2 , with HUE lights that is. Like its not saving my scene config correctly in HA. This has to be a HA Scene bug or something HA combined with HUE

My workaround for now is setting up a color scene in the Hue app. That syncs to HA and in my automation im using that one for now. I want to get back to HA when fixed because HA can do much more in a scene :)

ToasteyOstey commented 1 month ago

I have been having this issue for over a month now and this is the first that I seem to have found anyone else who finally shares my pain haha. Hopefully the permanent fix isn’t difficult!

DulinDuskhawk commented 1 month ago

Is there some way we can help with this issue? Did not see anything in the logs that hints to a cause yet.

Ascathon commented 1 month ago

@Kappade Exactly what I meant with "GUI created scenes". But yes, to be clear for this issue. My scenes are created in hass (/config/scene/dashboard) and my lights are all Hue lights connected via the Hue bridge

gldrenthe89 commented 1 month ago

Same issue where also the color is not changing. Have been messing around but even creating new scenes doesn't fix this issue. Only with Hue lights not with Govee, Ikea or zigbee directly zigbee controlled hue bulbs. looks like an issue with the Hue integration combined with these scenes that are created by the GUI.

WarpedObject commented 1 month ago

Chiming in too, I'm running HA 2022.9.4 core and haven't updated anything at all for a long time, restarted HA via GUI today and noticed my Philips Hue lights simply "snap" to the brightness level set in the scenes instead of gradually adjusting. Only devices that receive updates are the Philips Hue Hub/Lights so I assume somethings changed on Philips end.

Removing the "effect: None" line from scenes.yaml fixes it, luckily for me I don't really ever edit the scenes from the GUI so don't have to worry too much about it getting added back in hopefully.

EDIT: On a Raspberry Pi running "sudo sed -i '/effect: None/d' scenes.yaml" against the scenes.yaml file remove all instances in 1 go, reload SCENES from GUI > Developer Tools > YAML and all is now ok for the moment.

Ascathon commented 1 month ago

That an old version, but a very nice test. So yeah, definitely things changed at Hue. Maybe None is sent as a scene which isn't understood at the receiving end. Since those effects play with colours (and fading), the turn on fade and colour temperature are ignored. But I'm not a Home Assistant or Hue developer so just some thoughts.

itsjustjep commented 1 month ago

@WarpedObject Raspberry PI running 2024.7.3 - followed what worked for you with removing the "effect: none" and this worked as well!

gldrenthe89 commented 1 month ago

This is something that needs to be fixed in the integration itself. I dont work with .yaml files. Ik use GUI and this isn't possible for those scenes

jonas-brauer commented 1 month ago

I too got these symptoms yesterday. Changing scene does not fade hue bulbs (as they do as default) and they won't change color, just brightness. Selecting the bulb/entity manually let me change all properties as expected, but it won't work as part of a scene. There seem to be more delay than usual too.

Raspberry Pi 4 (32-bit) Core 2024.7.3 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240710.0

EDIT: Using the sed command as suggested above removing the effect does make it work.

davinkevin commented 1 month ago

+1 and I'm on the last version since its release. Same very annoying symptoms with Hue lights.

Everything is configured in the UI for me, so no escape hatch for the moment IIUC.

Container mode deployed in k8s, 2024.7.3

luuk58 commented 1 month ago

This doesn't only happen when creating a scene in the GUI, but also happens when a scene is created by an automation with values from snapshot_entities using the scene.create service.

DulinDuskhawk commented 1 month ago

Ah yes,

Thx @luuk58 ! That explains why Effect: None kept being added even though I did not use the GUI.

FabianKielkopf commented 1 month ago

+1 and similar symptoms with Hue lights.

This also happened with 2024.5.2. so i assume it is an issue with the Bridge or the bulbs itself. Because my non-Hue Lights are fine and They are also connected to the Same Bridge.

Container mode deployed in k3s, 2024.7.3

kylewilliams321 commented 1 month ago

Same issue here and also is hue bulbs

kylewilliams321 commented 1 month ago

I'll add that I'm creating "temporary " scenes so that I could revert the lights back to their prior state after an automation executes.

I do this with the snapshot entities option.

Just wanted to add this in as another detail to check.

mayrbenjamin92 commented 1 month ago

I have the same issue - I had quite some scenes created in home assistant to manage everything there (instead of in the hue app) and can confirm that colors are not working. I can configure scenes with multiple devices and set colors, but once I then try to trigger those scenes, the brightness settings work - but not the actual color.

Running 2024.7.3 (core) on a PI 4

cchaz003 commented 1 month ago

Same here 2024.7.2 (core). I was able to use the suggestions about removing the "effects" line in the scenes.yaml file to get the scenes to work again as a temporary fix. Thanks for the tip!

kylewilliams321 commented 1 month ago

Need to remove effect:none that is being written

Ascathon commented 1 month ago

Maybe. But I cannot tell if that same statement is relevant for other light integrations. The scene in general doesn't know which integration/light brand it will get applied to.

westerlind commented 1 month ago

I have tested this with a mix of Hue Bridge connected lights and ZHA connected lights.

If I create a scene in the GUI and add a Hue Bridge light and a ZHA light, I get this problem with both lights
If I then remove "effect: None" from the Hue Bridge light (it's not automatically put there for the ZHA light) and reload the YAML config, both lights seem to work properly
If I create a new scene with only a ZHA light, it works properly
ZHA lights do get just "effect:" by default, instead of "effect: None". Maybe Hue Bridge lights should get that instead too as a solution for this?
Adding a new scene that got this problem because it had "effect: None" in it does not (with what I have tested at least) seem to lead to any problems with other scenes. That might seem obvious, but is more strange together with the next point.
I also initially had problems making something like the code below fade the lights properly in the same way as with scenes, and it didn't matter if it was Hue Bridge lights or ZHA lights. It didn't work for any of them unless I removed all options except that the light should be turned on, and then the default fade worked. But when I have removed "effect: None" from all scenes, this actually now works too for some reason. Both for the Hue Bridge lights and the ZHA lights. So it's possible that "effect: None" in scenes can introduce problems in other places than those particular scenes too. I have not figured out the exact relation between these things though.
```
service: light.turn_on
target:
entity_id:
- light.test_light
data:
transition: 7
brightness_pct: 25
```

domibarton commented 1 month ago

Mine worked flawlessly for years.
However, since yesterday I experience the same issue: Calling scenes will no longer change the light temperature!

I'm sure this worked 2 days ago. I didn't change anything on home assistant, and I didn't change anything on the Hue bridge. HA was updated in June, no scene was updated in the last couple of weeks.

Home Assistant version: 2024.6.4
Hue bridge version: 1.65.1965111030

domibarton commented 1 month ago

Mine worked flawlessly for years. However, since yesterday I experience the same issue: Calling scenes will no longer change the light temperature!

I'm sure this worked 2 days ago. I didn't change anything on home assistant, and I didn't change anything on the Hue bridge. HA was updated in June, no scene was updated in the last couple of weeks.

Home Assistant version: 2024.6.4 Hue bridge version: 1.65.1965111030

UPDATE: Hue bridge was updated to 1965111030 (July 18, 2024).

stevenbrookslv commented 1 month ago

Chiming in that I am also having this issue. I only ever create scenes dynamically in an automation, and don’t have any contents in my scene.yaml (maybe I’m not looking in the right place?) so don’t really have anything to delete as a workaround

Andholmvej commented 1 month ago

Hi.. Same problem here... but it only sems to be bulbs with this software number 1.116.5 | 100b-114. The problem here only sems to affect color settings, if I change a scene on these bulbs the color will stay on that setting...

glain42 commented 1 month ago

Maybe a wild shot, but I've seen two firmware on my Hue bridge but no HA updates that might have triggered this. It suddendly affected all my Hue lights starting Jul, 23.

stevenbrookslv commented 1 month ago

I definitely don’t know about how the bridge and home assistant communicate but I would only expect the bridge to be the problem if triggering a scene that you have setup in the hue app. I would expect if the problem was the bridge you couldn’t even control the broken functionality of the lights at all via home assistant but it seems only scenes are messing up really and the direct control works fine

(again, this is all massively guessing I don’t really know anything lol)

mayrbenjamin92 commented 1 month ago

Hey all - I've tested this - it needs to be broken in the home-assistant hue integration due to an incompatibility with a newer hue update for our lamps! Check this: https://www.philips-hue.com/en-us/support/release-notes/lamps

With the May 14th update they have introduced two new effects Sparkel, Glisten and Opal - I guess with those they have changed the expected the default for effects!

westerlind commented 1 month ago

There is, at least for me, only problems if all of the following 3 points are true:

The "effect: None" option is still in the scenes (it doesn't matter which light in the scene that has this option, as the problem seem to effect all lights in the scene if it's there on one light, and when using automation actions it seems to not even matter which scene has this option as long as it's there in one scene)
The scene turns the lights on or off when it is triggered.
There is at least one more options triggered for a light than simply to turn it on or off.

If one of the points above is not true, everything seems to consistently work as expected for me.

Even when it doesn't work most of the time, it still does actually work occasionally for no apparent reason. The lights in one of my scenes had this issue for maybe 10-20 times in a row, which meant that it never changed to the intended light color and also didn't fade properly, but then it suddenly did work once, so that the color was correct the following times I used that scene.

It effects both Hue Bridge lights and other lights (ZHA in my case) when the "effect: None" is set for Hue lights, so it is probably not be a problem with the bridge, but it's hard to say for sure.

The problems can also occur even when using automation actions, not scenes, as long as "effect: None" is set in the scenes, so I guess it should not really be the scene functionality itself either that has the actual bug that causes this, but rather something else that can lead to problems even when not using scenes, but that still can change it's behaviour based on the scene configuration somehow.

But what would that be? I wish I knew.

jonas-brauer commented 1 month ago

~~I am not too comfortable with Python code to suggest changes, but it may be a clue to someone who is. Hue documentation suggest no_effect is to be used when setting effects. Searching the codebase here and and also in aiohue i can't find a reference of it. It seems we're sending None ? (Again, not Python dev) I may totally be lost in the woods, but if anyone actually comfortable with the codebase wants to verify, it's a clue at least.~~

Never mind, found that we do have correct attribute ...

2rym commented 1 month ago

Noticed this issue start around two weeks ago. All was fine then I noticed switching between the scenes, one of my bulbs continued to remain in the previous state. UPDATE: This is problem is effecting recently purchased bulbs only. My other HUE bulbs which are five or more years older still hold their colour temperatures.

jonas-brauer commented 1 month ago

I tried the Philips Hue API using Postman, connecting directly to the Philips Hue bridge. The documentation suggest effects is an optional attribute while sending no_effect is valid. However, testing this on a E27 bulb it won't let me change color while sending no_effect (I can force it by sending a significant change in brightness, and then it will flick state, not transition with fade as it used to). It DOES work as expected on Hue Play light bar though! My guess this is not necessarily caused by changes in Home assistant but rather a change in the firmware and/or the Philips Hue API. It will work not sending effects but then it also would likely alter behaviour (as a current effects wouldn't be disabled properly if something like fire or candle effect was activated). I'm not too comfortable making a PR, but I'll post these findings at least if it helps anyone.

Philips Hue Getting started PUT /light (You need to register which is free)

kylewilliams321 commented 1 month ago

There was a core patch 2024.7.4 released today which I was hoping addressed this issue but it didn't fix it. There were some hue related changes but nothing for this specific issue. Is anyone able to address this? I wish I had the know-how.

steffo007 commented 1 month ago

Hello. I'm having the same problem that everyone else seems to be having. The scene remembers what brightness it is set to, but seems to inherit the last color the light source was set to and use it, every time the scene is activated. Very annoying :)

jmendoza22 commented 1 month ago

I can confirm this is happening with my HA setup. Lots of my scenes are broken.

cjattard commented 1 month ago

+1 same issue - occurring over last 2-3 days. Homeassistant created scenes are no longer storing colour temperature value and instead are inheriting previous state.

davidlamd89 commented 1 month ago

I'm having the same problem, all scenes with hue lights not working since yesterday.

Landrin201 commented 1 month ago

I'm having the same problem. I have hue lights, set up like the following:

https://pastebin.com/wh1EpKxm

My lights have been working for years with this exact configuration, but last week stopped working. I will say that I'm not 100% sure this was something HomeAssistant broke. I don't remember exactly, but I'm pretty sure the lights broke before I applied the update from last week, and I applied the update hoping it would fix the problem, which it didn't.

When I try to activate my "day" scene, and my "night" scene is active, the red color from the night scene remains and only the brightness changes. Same in reverse. Color changing is altogether broken right now.

The update I got and installed today also didn't fix the problem.

I'm hoping this isn't something that Hue has changed on their end that breaks the HA integration, I'll be pissed if it is. It'll be expensive to replace these bulbs.

kylewilliams321 commented 1 month ago

Yes I’m hopeful it’ll be fixed soon as I believe an update with hue broke. What broke though is just the effect piece so should be able to be fixed rather easily (again I hope).

On Wed, Jul 31, 2024 at 11:21 PM Landrin201 @.***> wrote:

I'm having the same problem. I have hue lights, set up like the following:

https://pastebin.com/wh1EpKxm

My lights have been working for years with this exact configuration, but last week stopped working. I will say that I'm not 100% sure this was something HomeAssistant broke. I don't remember exactly, but I'm pretty sure the lights broke before I applied the update from last week, and I applied the update hoping it would fix the problem, which it didn't.

The update I got and installed today also didn't fix the problem.

I'm hoping this isn't something that Hue has changed on their end that breaks the HA integration, I'll be pissed if it is. It'll be expensive to replace these bulbs.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122165#issuecomment-2261978428, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQ3NWLCLE7G5MCXKJMNBNDZPGZVVAVCNFSM6AAAAABLEEO7LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRHE3TQNBSHA . You are receiving this because you commented.Message ID: @.***>

mayrbenjamin92 commented 1 month ago

Advise for anybody here in the thread: Disable automatic updates on your hue-bridge. Then connect an E27 light bulb in your "lab" and first always update this single light-bulbs firmware and test. This is what I will do from now on.

I have a huge smarthome system with nearly 100 hue lights and nearly all of my scenes broke because of this "bug" - super annyoing. I've now deactivated automatic hue upgrades in the hue-app and will do the updates selectively for the future. I am not using any of the "remote" features of hue directly, but fully rely on home assistant - hence being some firmware versions behind don't impose a huge risk for me (in my opinion).

gldrenthe89 commented 1 month ago

Hue being able to connect Home Assisant via Matter gets me to think this might be a solution. Any one using the Matter integration to integrate with Hue/HA

Andholmvej commented 1 month ago

Lab on hue is not working anymore... they stoped it...

home-assistant / core