Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Color_temp in Scenes #134639

Open
ruttromp opened this issue Jan 4, 2025 · 7 comments
Open

Color_temp in Scenes #134639

ruttromp opened this issue Jan 4, 2025 · 7 comments

Comments

@ruttromp
Copy link

ruttromp commented Jan 4, 2025

The problem

Log message:

Got color_temp argument in turn_on service, which is deprecated and will break in Home Assistant 2026.1, please use color_temp_kelvin argument

How to reproduce:

  • Create a new Scene
  • Add light bulb with color temp support and turn it on
  • activate created Scene

Looks like some part of HA still use the deprecated color_temp

What version of Home Assistant Core has the issue?

2025.1.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Scenes

Link to integration documentation on our website

https://developers.home-assistant.io/blog/2024/12/14/kelvin-preferred-color-temperature-unit/

Diagnostics information

No response

Example YAML snippet

supported_color_modes:
  - color_temp
color_mode: color_temp

Anything in the logs that might be useful for us?

No response

Additional information

No response

@rrooggiieerr
Copy link
Contributor

Which integration is your light entity from? I think that one needs to be updated.

@home-assistant
Copy link

home-assistant bot commented Jan 4, 2025

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

Code owner commands

Code owners of scene 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 scene 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)


scene documentation
scene source
(message by IssueLinks)

@ruttromp
Copy link
Author

ruttromp commented Jan 4, 2025

@rrooggiieerr I'm using Z2M and Tradfri bulbs

@Mayhem-SWE
Copy link

Mayhem-SWE commented Jan 4, 2025

Last I checked, it seemed scenes would only accept whichever color temperature parameter that was native to a light. I have a mix of Philips Hue bulbs connected through a Hue Bridge and IKEA Trådfri bulbs connected through ZHA with SkyConnect, which all say only supported_color_modes: color_temp (well Hue color bulbs also support xy).

I just manually edited a scene to only use color_temp_kelvin and to my surprise this did work now, for lights connected through either of the above integrations. Unfortunately still was not possible to specify brightness_pct in a scene rather than brightness though…

@popy2k14
Copy link

popy2k14 commented Jan 5, 2025

Exact same issue (log entries) since 2025.1

@DenverOps
Copy link

This also happened to me with Hue lights connected directly to Z2M. I unselected the Color Temp setting and saved my automation.

@OnkelBuTscH
Copy link

I have also received this message since the 2025 update.

“WARNING (MainThread) [homeassistant.components.light] Got kelvin argument in turn_on service, which is deprecated and will break in Home Assistant 2026.1, please use color_temp_kelvin argument”

I simply replaced “kelvin” with “color_temp_kelvin” in the yaml view for the automations in question. And so far everything is working again without this message appearing again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants