Describe the bug
When using the "sync light off" followed immedietly by a light turn on command, the sync stops, the lights turn on and immedierly turn off again.
To Reproduce
Steps to reproduce the behavior:
- Tried sync option and as an entity, recreated standalone test of "sync off" then "turn on lights" with same problem.
Expected behavior
This sequence has worked for nearly a year and stopped working tonight. Expect sync to turn off, then change the colors of the lights.
Diagnostics
If possible add diagnostics data from HA. The "Download diagnostics" option can be found in the vertical 3 dots menu (⋮) of the integration.
Please add the file itself (drag-and-drop in this box). Do not, copy-paste the contents here as it will make the issue unreadable
actions:
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
enabled: false
- parallel:
- type: turn_off
device_id: f138c0c079de234b7da1782d66a134bd
entity_id: fc615648c50af0c43ca10b83f8bb665e
domain: switch
enabled: false
- action: switch.turn_off
metadata: {}
target:
entity_id: switch.hockey_synv_light_sync
data: {}
- choose:
- conditions:
- condition: template
value_template: "{{ range(0, 2) | random == 0 }}"
sequence:
- action: media_player.play_media
target:
entity_id:
- media_player.tv_1
- media_player.tv_2
data:
media:
media_content_id: media-source://media_source/local/score.mp4
media_content_type: video/mp4
metadata:
title: score.mp4
thumbnail: null
media_class: video
children_media_class: null
navigateIds:
- {}
- media_content_type: app
media_content_id: media-source://media_source
browse_entity_id: media_player.tv_1
- conditions: []
sequence:
- action: media_player.play_media
target:
entity_id:
- media_player.tv_1
- media_player.tv_2
data:
media:
media_content_id: media-source://media_source/local/Capitals 25 goal.mp4
media_content_type: video
metadata: {}
alias: TV 1 & 2 Media Play
- target:
entity_id:
- light.hue_bloom_1
- light.hue_bloom_2
- light.play_light_1
- light.undercabinet_lights
- light.undercabinet_lights_2
- light.play_light_2
- light.play_light_3
- light.play_light_4
- light.hue_lightstrip_1
- light.hue_play_gradient_lightstrip_1
- light.hue_lightstrip_1_2
- light.hue_lightstrip_1_3
- light.chair
- light.h7021
- light.hue_lightstrip_1_4
- light.nico_desk
data:
brightness: 255
rgb_color:
- 255
- 0
- 0
action: light.turn_on
- sequence:(edited by @mvdwetering to make the yaml more readable)
this is an example of the sync off to lights on. I have tried different actions to turn the sync off.
Logging
If there are errors in the Home Assistant logs please add them here.
Environment
Provide details about the versions you are using, which helps to reproduce and find the issue quicker.
Upgraded to 3.0, then downgraded to test. No change.
- Home Assistant Core version: 2025.12.5
- Home Assistant operating environment (OS/Container/Supervised/Core):
- Huesyncbox integration version:
- Last working version (if known):
Additional info
Add any other info about the problem here.
-I found adding in a 1 second delay allows it to pass. This has worked great for a long time and I never needed a delay, so the assumption is with the changes made the last 24 hours caused the issue.
Describe the bug
When using the "sync light off" followed immedietly by a light turn on command, the sync stops, the lights turn on and immedierly turn off again.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This sequence has worked for nearly a year and stopped working tonight. Expect sync to turn off, then change the colors of the lights.
Diagnostics
If possible add diagnostics data from HA. The "Download diagnostics" option can be found in the vertical 3 dots menu (⋮) of the integration.
Please add the file itself (drag-and-drop in this box). Do not, copy-paste the contents here as it will make the issue unreadable
(edited by @mvdwetering to make the yaml more readable)
this is an example of the sync off to lights on. I have tried different actions to turn the sync off.
Logging
If there are errors in the Home Assistant logs please add them here.
Environment
Provide details about the versions you are using, which helps to reproduce and find the issue quicker.
Upgraded to 3.0, then downgraded to test. No change.
Additional info
Add any other info about the problem here.
-I found adding in a 1 second delay allows it to pass. This has worked great for a long time and I never needed a delay, so the assumption is with the changes made the last 24 hours caused the issue.