Open Airblader opened 6 days 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)
hue documentation hue source (message by IssueLinks)
Same problem here.
If you want to have different colors in a scene, you need the individual lights in the scene and not the group.
Is that a hard limitation, or just a feature request rather than a bug?
Here is my specific example which is facing the issue:
I have an automation where a light scene is being generated dynamically as soon as someone hits the main door ring bell.
This scene is taking a snapshot of the Hue light bulbs current state. After the scene is being created, the lights starts to blink using the “breathe” effect (which is done via mqtt.publish
action). After blinking the lights should get into their previous state at the moment when the snapshot was taken.
(Just for explanation: The idea behind this is that the Hue lights should singalize optically whenever someone is ringing the main door bell because there are some areas in our house where you just cannot hear the main door ring bell.)
As suggested by @marcelveldt, for taking the dynamic scene snapshot, I use the individual lights instead of the group, but this does not solve the issue I am facing. The automation works so far but the ugly limitation here is that when the scene is being activated at the last step of the automation, the color and brightness do not match the previous state.
Here's the code of the script which is being triggered by the automation after someone hits the main door ring bell:
alias: ScriptLightNotifications
sequence:
- action: scene.create
data:
scene_id: scene_scriptlightnotifications_lights_previous_state
snapshot_entities:
- light.huecolorlightstripplus02
- light.huecolorlightstripplus03
- delay:
hours: 0
minutes: 0
seconds: 2
milliseconds: 0
- action: mqtt.publish
data:
qos: 0
retain: false
topic: zigbee2mqtt/Z2MGroup_huecolorlightstripsplus/set
payload: "{\"scene_recall\": 1, \"effect\": \"breathe\"}"
- delay:
hours: 0
minutes: 0
seconds: 8
milliseconds: 0
- action: scene.turn_on
data: {}
target:
entity_id: scene.scene_scriptlightnotifications_lights_previous_state
mode: single
The problem
This is a follow-up for #122165 which has been fixed & closed, but I think something is still not working correctly.
I have an automation that creates a scene using a snapshot, dims the lights, and reactivates the scene later on (to dim the lights while the balcony door is open). In my specific case, they are all Hue lights.
When I create the scene as a snapshot of a light group (with each light having a different color), activating the scene turns on the lights, but sets them all to the same (white, for me) color instead of the correct individual settings.
If, however, I create the scene specifying the individual lights rather than a light group, everything works correctly.
I am attaching an automation that I can trigger manually to reliably reproduce the issue.
What version of Home Assistant Core has the issue?
core-2024.9.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
Anything in the logs that might be useful for us?
No response
Additional information
No response