Color_temp to color_temp_kelvin migration tool

Share your Projects!
, ,
1

Home Assistant 2026.3 has removed color_temp (mireds), kelvin , min_mireds , and max_mireds in favor of color_temp_kelvin

Here’s a small tool to copy/paste your yaml into, and it’ll attempt to automatically replace the depreciated constants to their new versions along with the corresponding converted values.

11 Likes
2

Just made an account to say thank you. Worked well for me.

1 Like
3

Thanks, glad it was of help.

4

Thanks!
This really helped!

1 Like
5

Seriously, THANK YOU! This was one of the most annoying changes the HA folks have made in quite a while. This saved me tons of time and headaches!

2 Likes
6

This was great - for whatever reason the index.html did not work when I copy pasted it from the github GUI, but when I used git clone, everything worked as expected. Probably something goofy with my clipboard I suspect.

Great work!

7

I created an account just to post and say thank you for this!

8

Hi,

I’m surprised the HA team broke such a simple thing without considering how difficult it can be to update all different automations manually.
Usually we have a transition period, or a backward compatibility :frowning:

This tool looked like it was the solution, but there is a catch, if you have Yeelight lights, they still use “kelvin:” and this tool replaces it to “color_temp_kelvin:” which breaks all Yeelight automations.

Is there a way to make it smarter and avoid all the yeelight.set_color_temp_scene action ?

example:

Thanks for the good work :slight_smile:

9

Don’t challenge them…

10

This change was announced years ago, but somehow they didn’t actually deprecate it until this release.

This means it’s the opposite of what you wrote - it might be the longest transition period in the history of HA

11

Thanks for the feedback. Added skip logic for non-HA core kelvin occurrences. Should hopefully work for you now.

12

I find it strange as I used the GUI to do these now broken automations, and I didn’t force any YAML code to specifically force deprecated names… If it was planned to be deprecated, it was still offered and pushed when creating a new automation.

2 Likes