Homeassistant warnings invalid value for thermostat
Open
Nobody has claimed this yet.
problem
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
It looks like if a given thermostat is off zigbee2mqtt sends 0 values to home assistant causing a log spam
2026-08-11 09:19:42.372 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.kids_room_bob_west_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
2026-08-11 09:19:42.489 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.kids_room_alice_west_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
2026-08-11 09:19:42.493 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.kids_room_alice_west_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
2026-08-11 09:19:42.849 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.kids_room_alice_west_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
2026-08-11 09:19:42.921 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.office_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
2026-08-11 09:19:42.968 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.office_thermostat_timer_mode_target_temp: 0 (range 4.0 - 35.0)
What did you expect to happen?
Don't send invalid values.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.0
Adapter firmware version
20240710
Adapter
cc2625
Setup
home assistant with mqtt connected to zigbee2mqtt
Device database.db entry
No response
Debug log
No response
Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how thermostat target-temperature values are published when the device is off, using the reported Home Assistant MQTT errors and the Zigbee2MQTT setup as the reproduction context. Confirm the thermostat's off-state behavior and verify that no value outside the 4.0–35.0 range is sent; the issue is done when the repeated invalid-value warnings stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100