Zigbee2MQTT publishes color_temp on Hue White bulbs causing MQTT Light warnings in HA

Configuration Zigbee
, ,
1

Dear friends,

I’m encountering an issue with MQTT flooding my Home Assistant Core raw logs with warning messages:

2026-01-22 09:01:41.944 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_droite
2026-01-22 09:01:51.942 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_droite
2026-01-22 09:03:54.969 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:04.945 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:14.945 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:24.945 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:34.944 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:44.946 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:04:54.946 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:05:04.997 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:05:14.990 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:05:24.940 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_gauche
2026-01-22 09:05:45.616 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'color_temp' received for entity light.salle_a_manger_suspension_entree

These three lights are Philips Hue White bulbs (brightness only), but it seems the payload is sending color temperature commands to them.

I use these lights in a Zigbee group controlled by Adaptive Lighting, but I don’t think it’s related since the warnings appear even when the add-on is disabled.

These bulbs were auto-configured by Zigbee2MQTT and expose only brightness in the GUI, but their States section shows:

{
    "brightness": 203,
    "color": {
        "x": 0.3608,
        "y": 0.3635
    },
    "color_mode": "color_temp",
    "color_temp": 222,
    "last_seen": "2026-01-19T14:52:49.372Z",
    "linkquality": 255,
    "power_on_behavior": "on",
    "state": "ON"
}

And payload :

[22/01/2026 09:36:27] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Salle a manger - Suspension gauche', payload '{"brightness":177,"color":{"x":0.3608,"y":0.3635},"color_mode":"color_temp","color_temp":222,"effect":null,"last_seen":"2026-01-22T08:36:27.556Z","linkquality":255,"power_on_behavior":"on","state":"ON","update":{"installed_version":16787202,"latest_version":16787202,"state":"idle"}}'

Is this where the problem comes from?
Any advice on how to fix or silence these warnings?

Thanks in advance!

2

I have this exact issue as well, using the same hardware, however my state is a little different.

{
    "brightness": 112,
    "color": {
        "x": 0.4986,
        "y": 0.4153
    },
    "color_mode": "color_temp",
    "color_temp": 440,
    "last_seen": "2026-02-16T09:02:47-07:00",
    "linkquality": 80,
    "power_on_behavior": "previous",
    "state": "ON",
    "update": {
        "installed_version": 16787202,
        "latest_release_notes": null,
        "latest_source": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Hue/100B-0114-01002702-ConfLightBLE-Lamps-EFR32MG21.zigbee",
        "latest_version": 16787202,
        "state": "idle"
    },
    "device": {
        "applicationVersion": 2,
        "dateCode": "20250213",
        "friendlyName": "Master 2",
        "hardwareVersion": 1,
        "ieeeAddr": "555-5555",
        "manufacturerID": 4107,
        "manufacturerName": "Signify Netherlands B.V.",
        "model": "9290024691A",
        "networkAddress": 5555555555,
        "powerSource": "Mains (single phase)",
        "softwareBuildID": "1.122.8",
        "stackVersion": 1,
        "type": "Router",
        "zclVersion": 8
    },
    "effect": null
}

Blockquote

3

I ended up finding out what happened. I had non color lights grouped with color lights and it appears that this caused the state.json file under the zigbee2mqtt directory to have color_temp defined. I also had adaptive lighting enabled targetting this group, the ultimate root cause is unknown to me so I removed the group and created two adaptive lighting instances for non color and colored bulbs.

To clear the states; First stop z2m, then remove every line referencing color from the state.json file under the correct keys for the problematic devices, you can find the json keys in z2m (the 0xblahblahblah number). Then restart z2m.

I also read somewhere that state.json can be removed all together as it is just a cache and will get filled back in as the devices report states back. However I did not try to do this.