"extra keys not allowed @ data['color_temp']"

Third party integrations Node-RED
1

I sat up an automation years ago in the HA Addon Node-Red.
It has worked fine. But after the upgrade to Home Assistant 2026.3, I get an error when trying to turn on my light.

name: “HomeAssistantError”

message: “extra keys not allowed @ data[‘color_temp’]”

The setting looks like this:

image
image498×389 6.81 KB

As far as I can see, the color_temp attribute still exists in the target:

{"entity_id":"light.tv_krok","state{
  "entity_id": "light.tv_krok",
  "state": "off",
  "attributes": {
    "min_color_temp_kelvin": 2202,
    "max_color_temp_kelvin": 6535,
    "supported_color_modes": [
      "color_temp",
      "xy"
    ],
    "color_mode": null,
    "brightness": null,
    "color_temp_kelvin": null,
    "hs_color": null,
    "rgb_color": null,
    "xy_color": null,
    "is_hue_group": true,
    "hue_scenes": [
      "Les",
      "Slapp av",
      "Lad batteriene",
      "Lyst",
      "Konsentrer deg"
    ],
    "hue_type": "zone",
    "lights": [
      "TV-krok - Spot 1",
      "TV-krok - Spot 2",
      "TV-krok - Spot 3",
      "TV-krok - Spot 4",
      "TV-krok - Spot 5"
    ],
    "entity_id": [
      "light.tv_krok_spot_1",
      "light.tv_krok_spot_2",
      "light.tv_krok_spot_3",
      "light.tv_krok_spot_4,
      "light.tv_krok_spot_5"
    ],
    "dynamics": false,
    "icon": "mdi:lightbulb-group",
    "friendly_name": "TV-krok",
    "supported_features": 40
  },
  "context": {
    "id": "01KK1045HQVE4KE6XX1T9Q99R0",
    "parent_id": null,
    "user_id": null
  },
  "last_changed": "2026-03-06T07:17:22.615Z",
  "last_updated": "2026-03-06T07:17:22.615Z",
  "timeSinceChangedMs": 939985
}

It is entirely possible that some changes that has occured in Node-RED or Home Assistant that I have missed.
Or is it a bug?

Thanks

2

From the release notes:

Lights

Using color_temp (in mireds) to set a light’s color temperature is no longer supported. Use color_temp_kelvin instead.

Additionally, the color_temp, kelvin, min_mireds, and max_mireds light entity state attributes have been removed. Use color_temp_kelvin, min_color_temp_kelvin, and max_color_temp_kelvin instead.

(@emontnemery - #161777) (light documentation)

9 Likes
3

Works like a charm. Thank you!

4

Good that it is solved!

Also: please take the time to mark the post that holds the solution.
You do that by selecting the three dots under the post:

image

Then select the check box:

image
By doing so:

  • this thread can be useful to other users as well (this thread comes up as solution when starting a thread which is similar to yours).
  • this prevents that someone else steps in trying to help

Thanks for giving back to the community! :+1:

5

I’m glad you mention this, because I was looking for just that when I read the post earlier.
But I could not find the Solution tick box, and I still can’t:

image
image775×172 3.68 KB

6

There is no solution box in the node red forum

1 Like
7

Thanks for this… really frustrating though. Suddenly all my motion lights don’t work and I have to go through dozens of automations to change dozens of individual keys? Good thing I’m off work today and that I noticed before dark… What problem was the deprication supposed to be solving? :expressionless:

2 Likes
8

grumble

Why was this breaking change required? Was it not feasible to leave them for backwards compat?

3 Likes
9

Same here.

To avoid redoing everything manually, you can use the File editor to update the keys directly in the /homeassistant/automations.yaml file. Just use search and replace to change all the old keys to the new ones. It’s much faster.

10

Oh you had me excited for a minute, but that only works if you’re doing automations directly in HA, and not via NodeRED, sadly.

11

you can export the flow, then open with notepad, search and replace, save and import modified flow

12

You should really use a program made for code editing to avoid introducing problems.