Correction, November 2026: An earlier version of this post said that after every restart my KNX thermostats fell to standby and stopped heating, that I woke up to a cold flat with cold radiators, and that a startup automation has fixed it ever since. The house has floor heating, the room controllers kept their mode, and the startup automation has been switched off since January. In September I compared the mode display and the reported setpoints on both instances.
What Home Assistant showed
My 11 KNX room controllers appear in Home Assistant as climate entities with presets. After a restart of Home Assistant, all of them showed standby. I first took that at face value. On 2 January 2026 I added an automation that sets every thermostat to the right mode 30 seconds after Home Assistant starts, and committed it as a fix for the standby problem. The climate entity IDs below are placeholders; the example also needs an input_boolean.heizung_nachtmodus helper that is on during night mode.
- id: heating_startup_initialize
alias: 'Heating: set mode on start'
triggers:
- trigger: homeassistant
event: start
actions:
- delay:
seconds: 30
- choose:
- conditions:
- condition: state
entity_id: input_boolean.heizung_nachtmodus
state: 'on'
sequence:
- action: climate.set_preset_mode
data:
preset_mode: economy
target:
entity_id:
- climate.thermostat_example_1
- climate.thermostat_example_2
# ... 11 thermostats in total
default:
- action: climate.set_hvac_mode
data:
hvac_mode: heat
target:
entity_id:
- climate.thermostat_example_1
- climate.thermostat_example_2
- action: climate.set_preset_mode
data:
preset_mode: comfort
target:
entity_id:
- climate.thermostat_example_1
- climate.thermostat_example_2
mode: single
The 30 seconds give the KNX integration time to connect before the commands go out. Since January the automation has been switched off on my old instance.
The reported setpoint was 20.0 °C
In September, while I ran a new instance next to the old one, the two showed different modes one morning: the old one comfort, the new one standby. The new one had read the switch to comfort at 05:00 correctly, but after a restart at 07:19 it queried the operating mode and got standby back. The old instance only showed comfort because it had written that mode itself; after its own restart the evening before, it had also shown standby.
The reason is in the ETS project. My current ETS configuration has no readable feedback object for the operating mode. When Home Assistant reads the mode after a restart, it gets an answer that does not reflect the active mode. The setpoint the controllers report was more telling: on that morning it was 20.0 °C, my comfort setting, while Home Assistant showed standby; my night setting is 18.0 °C.
In the ETS export there is, next to each controller's mode switch, a second object with the data type for operating modes, and its name starts with Z. I almost entered it as the status address. The Z stands for forced operation and the object is not readable. My notes in the repository said that an earlier clean-up had already removed exactly these addresses from the feedback configuration, so I left them out.
What the startup automation actually does
The automation sets the mode again after the restart, although in my case the controller had kept it. It writes a mode, so that the controllers and the display in Home Assistant agree again. That only helps if the written mode is the one that should apply at that time. In my old version it was not consistent: at night it set economy, while my night automation set standby.
On my new instance the automation has been adjusted since 9 October: it skips rooms with an open window, and night mode is economy everywhere. Like all heating automations there, it is switched off, because the old instance still controls the heating.
What I changed on the old instance
On 6 November I switched off the night and day automations on the old instance and changed its heating dashboards to text. The night period from 21:00 to 05:00 lay entirely in the pause of the heating pump, which runs from 05:00 to 07:30 and from 17:00 to 20:00, and the history of 5 and 6 November showed that no room cooled down to its night setpoint. The dashboards now show current temperature, setpoint and preset as text. The window automations stay active.
What is still open
I still need to check whether these controllers offer a readable status object for the operating mode that I can put on its own group address in ETS. Until then I cannot rely on the mode shown after a restart on either instance; in the September comparison the reported setpoint matched my comfort setting.
Frequently asked questions
Why does my KNX thermostat show standby after a Home Assistant restart?
In my setup Home Assistant reads an object after a restart that does not report the active operating mode. The reported setpoint, 20.0 °C on that morning, matched my comfort setting.
Does a startup automation fix it?
It makes the display match again by writing a mode. It does not tell you which mode the controller was in, and it only helps if the mode it writes is the right one for that time.
How do I find a readable status object in ETS?
Look in the controller's documentation for an object that reports the active operating mode, then check its communication and read flags in ETS rather than going by its name. Abbreviations in ETS projects are manufacturer-specific; in mine, the Z in front of the mode object meant forced operation, not status.
Top comments (0)