search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.14k stars 29.81k forks source link

Hue lights groups don't update in a synchronised way #64015

Closed weelad closed 2 years ago

weelad commented 2 years ago

The problem

In each room, I have 6-8 hue spotlights in the ceiling. I'm specifically using light groups coming from the hue hub, not the light groups.

The problem I'm having is that if I adjust the light group, the spotlights each adjust at a slightly different pace. This is very noticeable. When I say adjust, I mean: turn on, turn off, adjust brightness, hue, etc.

It didn't happen with 2021.11 and only started happening with the December release.

The only other time I've experienced this is when I've used HA's light groups and not the ones defined directly in Hue. I presume the updates are sent to each spotlight sequentially, which causes this. Whereas with the Hue groups, a single event is sent to the hub, and it can adjust all the grouped lights at once.

What version of Home Assistant Core has the issue?

All 2021.12 patch releases. Currently, on 2021.12.8

What was the last working version of Home Assistant Core?

2021.11.x

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Phillips Hue

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

group documentation group source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

hue documentation hue source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (group) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

probot-home-assistant[bot] commented 2 years 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! (message by CodeOwnersMention)

marcelveldt commented 2 years ago

This is an issue with the Hue API atm. If you send a plain ON/OFF command, it will be send to the zigbee/Hue lightgroup directly. Once you add more changes, such as color, transition etc. the command can not be sent to the grouped light directly but each light will be addressed one by one.

Unfortunately it seems that recent bridge versions seem to limit the amount of parallel calls so we can only send a command every 250ms. So if you send a command to that group with 8 lights, it will take 2 seconds before all lights receive the command.

We'll have to wait for Signify to fix this issue. In the meanwhile I have one big recommendation and that is to use Hue scenes.

weelad commented 2 years ago

Thanks for getting back to me @marcelveldt.

So the reason I'm experiencing this now and not before, is because there's been an update to the bridge recently, reducing the number of allowed parallel calls - right?

Do you know if Signify have a customer facing bug tracker and if they've been made aware of this issue?

I do like your scene suggestion but unfortunately, I'm using the Circadian Lightening component, which wouldn't work with scenes.

marcelveldt commented 2 years ago

Yes, that seems to be the case. Either an update on the Hue bridge or some other component results in the fact we can no longer do parallel requests. The bug is reported to Signify on their developers forum.

Be aware that most circadian lightning components I've seen so far are changing the lights way too often, hammering requests every few seconds while there is no need. You can just as well adjust the color temperature every 5 minutes with a decent transition time of about 2 minutes and you will still have a very smooth effect without killing performance of your bridge.

Ehlz77 commented 2 years ago

Not true, Hue groups still working correct in HA 2021.9.7, only one command is send and lights turn on and off at exactly same time. . This must be an HA issue, not a Hue issue

marcelveldt commented 2 years ago

@Ehlz77 that version is still using the legacy API so that can't be compared. In the meanwhile we worked with Signify to fix the issue and the fix will be in the next 2022.2 release btw.

Ehlz77 commented 2 years ago

@marcelveldt i see, sorry, just wanted to make you aware. I will look forward to the updated version. Any news as to if the integration will again add effects to hue bulbs ? (Random and colorloop)

marcelveldt commented 2 years ago

@marcelveldt i see, sorry, just wanted to make you aware. I will look forward to the updated version. Any news as to if the integration will again add effects to hue bulbs ? (Random and colorloop)

For now it looks like random and colorloop effect will not be back any time soon as they're basically phased out in Hue and there's no replacement (yet) in the Hue V2 API. We've brought it to the attention of the Signify team and maybe they will reconsider and bring it back as some sort of script. For I suggest you to look for a alternative solution for these effects. On the forums there are a couple of solutions with scripts and templates.

jdiegmueller commented 2 years ago

@Ehlz77 that version is still using the legacy API so that can't be compared. In the meanwhile we worked with Signify to fix the issue and the fix will be in the next 2022.2 release btw.

I'm running 2022.2.6 (a handful of releases after the comment above) and seeing the "one light at a time" behavior when interacting with zones. Is that still expected? Do I need to get on newer Hue Bridge firmware, or enroll them in a beta program (saw this discussed in some other threads)? All 5 of mine are running 1.49.1949203030 currently.

Thanks!

conorlap commented 2 years ago

https://user-images.githubusercontent.com/57415184/154230443-7907bfea-7558-4538-9f3a-daf09a4bf9d6.mov

https://user-images.githubusercontent.com/57415184/154230455-8f4a71c1-b2c8-4570-885a-20a05c90b3d7.mov

Issue: Brightness slider isn't fluid / slow to respond to lights actual brightness state on hue light group.

Not sure if directly related to this (I think it is), but as you can see from attached clips, when I adjust the brightness with the slider; it initially pops back to the original value before eventually adjusting to the current set brightness value.

Adjusting the brightness for individual lights works fine, it's just light groups that are affected.

marcelveldt commented 2 years ago

Only a plain on/off command on a light group is sent as one command (so optimized) on the Zigbee stack. When you send another command (such as brightness, color change etc) this will result in unicast messages to each individual light of the group and a message back with the updates state. So, a non-fluid experience (especially in the UI) is the direct cause of that.

Signify is aware of this and is going to publish a new firmware update with a fix within 1 month from now. After that fix, we can send all commands to the group itself instead of addressing each light individually.

The original issue was that HA caused an additional delay in the light commands but that one is fixed. All commands/messages to/from Hue are now as fast as possible (only slowdown being the zigbee stack itself).

claytonjn commented 2 years ago

hue.brightness.1.mov light.popup.brightness.mov Issue: Brightness slider isn't fluid / slow to respond to lights actual brightness state on hue light group.

Not sure if directly related to this (I think it is), but as you can see from attached clips, when I adjust the brightness with the slider; it initially pops back to the original value before eventually adjusting to the current set brightness value.

Adjusting the brightness for individual lights works fine, it's just light groups that are affected.

I came here looking to see if anyone else has an issue where none of the Hue groups of lights (specifically rooms) can be controlled other than on/off - in my case brightness, color, etc aren't available in the frontend and trying to change those via service call doesn't seem to do anything, including no errors logged.

image

Is this working for others on HA core-2022.2.9? For reference, I have two Hue bridges - one is updated to 1.50.1950111000, the other is on 1.50.1950049000 but room entities from both are exhibiting the same behavior.

EDIT: Hue rooms/zones all seem to have attribute supported_color_modes: onoff, which based on the comment here seems to be related to them also having attribute lights: - no lights are listed under the lights attribute for any of the hue room/zone entities, which makes me think something is breaking here.

marcelveldt commented 2 years ago

@claytonjn please do not hijack a thread with something unrelated. Can you create a new issue ? Thanks!

Ehlz77 commented 2 years ago

Only a plain on/off command on a light group is sent as one command (so optimized) on the Zigbee stack. When you send another command (such as brightness, color change etc) this will result in unicast messages to each individual light of the group and a message back with the updates state. So, a non-fluid experience (especially in the UI) is the direct cause of that.

Signify is aware of this and is going to publish a new firmware update with a fix within 1 month from now. After that fix, we can send all commands to the group itself instead of addressing each light individually.

The original issue was that HA caused an additional delay in the light commands but that one is fixed. All commands/messages to/from Hue are now as fast as possible (only slowdown being the zigbee stack itself).

Hi Marcel, doing a light.turn_on and choosing a group in HA (zone from Hue through Hue integration) as destination still turns on lights one at the time. I have no customization in regards to brightness or other values. What am i doing wrong?

sc8696 commented 2 years ago

I see this has been all merged and closed. Does the 2022.4 beta resolve the issue @conorlap mentioned? Or are we still awaiting an update from Signify?

ThePatricide commented 2 years ago

For me this issue seems to be fixed for over a week or so, probably because of an update on the Hue Bridge, so it might have been included in the April 4 update (https://www.philips-hue.com/nl-nl/support/release-notes/bridge). However, release notes are meager so cannot tell for sure, but at least my lights are responding simultaneously again instead of light by light.