core: Automatically created scenes with light color will not work correctly as conflicting directives are added to scenes.yaml
The problem
Goal: To set bulb color temp as part of scene. Problem: When using the scene creator in the UI, and selecting lights with color temperature options, all of the available parameters are included in the scene.yaml, which seems to be problematic (RGB_COLOR and COLOR_TEMP should not be included together as example based on community feedback). Editing the scene.yaml to remove the additional directives resolves the problem - for example setting color_temp only. See example of working scene “reading” vs not functioning scene “test for bug report”
Environment
- Home Assistant Core release with the issue: Home Assistant 0.112.4
- Last working Home Assistant Core release (if known):
- Operating environment (OS/Container/Supervised/Core):
- Integration causing this issue:
- Link to integration documentation on our website:
Problem-relevant configuration.yaml
- id: '1594585192631'
name: reading
entities:
light.jons_bedside_lamp:
brightness: 254
color_temp: 420
friendly_name: Jons Bedside lamp
state: 'on'
transition: 3
light.stefs_bedside_lamp_level_light_color_on_off:
brightness: 254
color_temp: 420
friendly_name: Stefs Bedside lamp
state: 'on'
transition: 3
- id: '1594598925909'
name: test for bug report
entities:
light.jons_bedside_lamp:
brightness: 254
color_temp: 460
friendly_name: Jons Bedside lamp
hs_color:
- 0
- 0
max_mireds: 500
min_mireds: 154
off_brightness:
rgb_color:
- 255
- 255
- 255
state: 'on'
supported_features: 59
xy_color:
- 0.323
- 0.329
Traceback/Error logs
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 15 (3 by maintainers)
A similar situation seems to be happening with Yeelight bulbs. I’m trying to create scenes on the fly in a script but even if I set the light to have a temperature color before run it this will switch to RGB when I try to return to the initial values from the snapshot.