Boiler Short-Cycling: What Home Assistant Monitoring Can Reveal

Quick Summary (TL;DR)

Boiler short-cycling means the burner repeatedly fires and stops in relatively short intervals, often while there is still a demand for heat. Home Assistant can help establish whether this is happening, when it happens, and how it relates to thermostat demand, water temperature and system operating conditions. It cannot, by itself, prove the cause. A boiler that starts and stops frequently may be responding normally to a very small heating load, or it may be showing symptoms of poor control settings, restricted flow, unsuitable sizing or a fault requiring professional diagnosis.

The most useful measurements are burner state, central-heating demand, flow temperature, return temperature and timestamps. Start by monitoring rather than changing anything. Do not defeat minimum-off times, pump overrun, high-limit thermostats, pressure switches or other manufacturer protections. Any adjustment inside the boiler or to gas, flue or combustion components belongs to a suitably qualified heating professional.

What counts as boiler short-cycling?

A burner cycle starts when the appliance ignites and ends when the burner shuts off. The circulating pump may continue after flame-off, and the heating demand may remain active throughout. That distinction matters: the burner stopping is not the same as the heating system switching off. A modern modulating boiler may run continuously at low output on a cold day but cycle on a mild day when the building needs less heat than the burner’s minimum stable output.

There is no single universal “five-minute rule” that proves a fault. Acceptable cycle frequency depends on appliance model, minimum burner modulation, water volume, emitter design, weather compensation, demand and the manufacturer’s control strategy. A 90-second burst repeated continuously deserves investigation; a few cycles during a mild-weather hour may be expected. Compare against the manufacturer’s documentation and the behaviour of the same installation under similar conditions.

Observation	What it may indicate	What it does not prove
Burner repeatedly on for 1–3 minutes	Low water volume, high setpoint, minimum-output mismatch or control issue	A defective boiler
Burner stops while thermostat still calls	Internal temperature target or boiler control limit reached	Thermostat is broken
Many cycles only in mild weather	Heat demand below minimum burner output	Incorrect installation
Rapid flow-temperature rise	Heat not being transferred away quickly	Pump fault without flow testing
Short cycles after zones close	Insufficient open emitter capacity or hydraulic interaction	That TRVs should be removed

The five signals worth collecting first

1. Actual burner status

The best source is a supported boiler interface that reports burner operation, rather than inferring flame from power consumption or a room thermostat. Depending on model, OpenTherm, manufacturer telemetry or a documented Modbus register may expose burner state. Confirm the precise semantics: some integrations report heating mode, others report central-heating active, and only some expose the flame itself. Record when the entity becomes unavailable as well as when it changes state.

2. Thermostat heat demand

Track whether a thermostat, zone controller or heating schedule is actively requesting heat. An on/off thermostat provides a binary demand signal; a modulating thermostat may request a target water temperature or heat level. Do not treat a climate entity’s displayed “heat” mode as proof that it is currently calling for heat. The exact entity attributes and integration documentation matter.

3. Flow and return temperatures

Flow temperature is the water leaving the boiler towards the heating circuit; return temperature is the water coming back. A steep rise in flow temperature immediately after ignition can be informative. Sensor placement and thermal coupling are critical. Surface-mounted sensors respond differently from immersion probes, and poorly insulated probes may reflect cupboard air rather than pipe temperature. For sensor selection and placement, see flow and return temperature sensor accuracy; the measurement principles apply to hydronic boiler circuits too.

4. Zone and radiator demand

Log which heating zones are open, which TRVs are requesting heat, and whether the boiler has enough active radiator or underfloor heating area to absorb its minimum output. A room-by-room system can create an apparent control paradox: one small bedroom requests heat, the boiler fires at its minimum output, and the tiny active load warms rapidly. The result may be repeated starts despite a perfectly functional boiler.

5. Outdoor temperature and time of day

Outdoor conditions help separate genuine abnormal behaviour from low-load cycling in shoulder seasons. Mark hot-water production, setback recovery and scheduled heating periods. A combi boiler may fire for domestic hot water even when space heating is off; those events must be excluded from a space-heating cycling analysis.

Signal	Preferred source	Common pitfall
Burner on/off	Supported boiler telemetry	Confusing CH demand with flame
CH call	Thermostat or zone-controller entity	Climate mode is not actual call
Flow temperature	Boiler sensor or fitted pipe probe	Slow surface-sensor response
Return temperature	Boiler telemetry or fitted probe	Unmatched probe placement
Zone status	Valve or manifold controller	Valve command is not proof of position
Outside temperature	Reliable weather sensor	Solar-exposed sensor
DHW demand	Boiler interface where available	Counting DHW cycles as CH cycles

Local data sources: OpenTherm, Modbus and simple relays

An OpenTherm-capable appliance may expose burner state, boiler water temperature, modulation and fault codes through a compatible interface, but available fields depend on the boiler and gateway. A Modbus-capable heating appliance may expose comparable data through a manufacturer-specific register map; a Modbus label alone guarantees none of those entities. A dry-contact thermostat generally reveals only a call for heat, not burner operation or modulation. Our ESP32 OpenTherm gateway guide covers the gateway concept; our ESP32 multi-zone heating controller explains how zone demand can be monitored and coordinated. Do not connect a hobby microcontroller directly to unknown boiler terminals: some thermostat connections carry mains voltage, and manufacturer interfaces may require galvanic isolation.

Interface	Can reveal demand?	Can reveal actual burner?	Key qualification
OpenTherm via compatible gateway	Often	Sometimes	Depends on supported message fields
Manufacturer local API	Often	Sometimes	Model and firmware specific
Modbus RTU/TCP	If mapped	If mapped	Register map and access rights required
Dry-contact thermostat	Yes, call state	No	A relay is not a flame sensor
Electrical power monitor	Indirectly	Sometimes inferred	Pump and fan loads complicate inference

Build a trustworthy Home Assistant timeline

First confirm the integration exposes stable entities, then record at least several representative heating periods. Use History or a dashboard with burner state and heating demand on the same time axis, with flow temperature underneath. Avoid creating automations that continually toggle the boiler while you are diagnosing it. Recording the raw signals before calculating derived statistics makes later verification much easier.

Give each entity a descriptive name, such as binary_sensor.boiler_burner or sensor.boiler_flow_temperature; substitute your real entity IDs.
Verify that burner state changes correspond to actual boiler operation, where safely observable.
Check that timestamps and time zones align and that recorder retention covers the intended observation window.
Exclude periods where telemetry is unavailable or the Home Assistant server has restarted.
Separate central-heating cycles from domestic hot-water events if the appliance serves both.

Count cycles without hiding missing data

A burner-start counter should increment only on a verified transition from off to on. If the sensor comes back from unavailable directly to on, that is not a verified ignition and should not be counted. The following illustrative Home Assistant automation uses an event-driven counter helper. Create a counter named boiler_burner_starts in Helpers first, and replace the example entity ID. Home Assistant YAML syntax and supported keys can change; validate it in your installed version before use.

alias: Count verified boiler burner starts
triggers:
  - trigger: state
    entity_id: binary_sensor.boiler_burner
    from: "off"
    to: "on"
actions:
  - action: counter.increment
    target:
      entity_id: counter.boiler_burner_starts
mode: single

A counter accumulates across the period for which it is maintained; it is not automatically “starts per hour”. To calculate frequency, compare two readings over a defined interval, or create a separately reset daily counter. Avoid resetting the only lifetime count unless that is intentional. A Home Assistant restart can interrupt measurements; mark gaps rather than estimating missing cycles.

Measure run time and off time, not just starts

Cycle count alone misses the most important information. Ten starts over a whole day are different from ten starts in half an hour. Record the duration of each verified burner-on interval and each verified off interval. Consider median rather than just mean run time, because one long morning recovery can obscure many very short cycles. Record the percentage of time with an active thermostat demand and the percentage of that time the burner actually fires.

Metric	How to calculate	Why it matters
Starts per hour	Verified off→on transitions / observed hours	Shows frequency
Median on-time	Median of complete burner-on intervals	Exposes repeated brief firings
Median off-time	Median of complete off intervals	Highlights rapid re-ignition
Demand duty	Minutes CH demand active / observation minutes	Context for cycling
Burner duty	Minutes burner on / observation minutes	Approximate runtime fraction
Flow overshoot	Peak flow minus active target	Can reveal temperature-control behaviour

Worked example: two houses with the same cycle count

House A: the boiler records 12 burner starts over 12 hours of intermittent heating, with runs commonly lasting 20–35 minutes. That is roughly one start per observed hour, and the cycle pattern alone is not alarming. House B: the boiler records 12 starts within 40 minutes while a thermostat continuously requests heat, with runs lasting around 90 seconds. That is 18 starts per hour over that interval and is a much stronger reason to investigate. Neither dataset independently identifies the underlying cause.

For a numerical comparison, suppose a boiler runs for 2 minutes, then remains off for 3 minutes, repeating over an hour. The complete cycle is 5 minutes, implying about 12 starts per hour and 24 burner-on minutes per hour. If the same home instead has 20-minute runs and 10-minute off periods, the rate is approximately 2 starts per hour. These are illustrative patterns, not universal manufacturer acceptance limits.

Seven common causes and what the evidence looks like

1. Boiler minimum output exceeds the active heat load

A modulating boiler can reduce burner output only to its specified minimum. If the house needs 1.5 kW but the boiler’s minimum stable heating output is 4 kW, the extra energy raises water temperature and the burner eventually stops. This can happen even when every component is working. Compare the appliance’s minimum central-heating output from its exact datasheet with the estimated building load and the number of active emitters. Avoid assuming a boiler’s nominal maximum rating tells you its minimum.

2. Flow-temperature setpoint is too high for the current load

A high target water temperature can lead to rapid temperature rise, especially with a small radiator circuit or a single active zone. Weather compensation or a lower manufacturer-approved central-heating target may help in suitable installations, but changing control parameters without understanding emitter sizing, hot-water requirements and boiler commissioning can make performance worse. Distinguish space-heating water temperatures from domestic hot-water hygiene requirements.

3. Insufficient water circulation

A restricted filter, air in the system, inappropriate pump setting or closed valves can reduce heat transfer away from the heat exchanger. Monitoring may show fast flow-temperature rise and a pronounced flow/return difference, but those patterns are not conclusive. A qualified engineer may need to inspect pump operation, strainers, balancing and differential pressure. Do not remove covers or open pressurised components as part of a software troubleshooting exercise.

4. Too many TRVs or zones closing together

Smart TRVs improve room-by-room control but can reduce the active emitter area dramatically. If only one small radiator remains open, the boiler may be unable to shed its minimum output. Review the system’s approved bypass arrangement, minimum-flow requirements and zone-control logic with the installer. A bypass valve is not a universal substitute for adequate heat-emitting capacity.

5. Conflicting control layers

A smart thermostat, boiler-native schedule, zone controller and Home Assistant automation can issue competing demands. The resulting timeline may show rapid thermostat toggling rather than boiler-internal cycling. Pick a clear control authority, keep hysteresis or minimum run times within manufacturer-supported settings, and never use Home Assistant to bypass boiler safety limits.

6. Domestic hot water misclassified as heating

On a combination boiler, taps, showers or preheat functions can trigger short burner events unrelated to radiator heating. If the boiler exposes a domestic-hot-water active flag, exclude those intervals. Otherwise, inspect the timing carefully before making claims about space-heating performance.

7. Faults or commissioning problems

Temperature-sensor faults, circulation problems, burner control issues and installation defects may also produce abnormal patterns. Error codes, lockouts, unusual noises, pressure warnings, gas smell or signs of flue trouble are reasons to stop experimentation and obtain professional assessment. Home Assistant is a monitoring tool, not a substitute for appliance diagnostics.

Pattern in data	Plausible explanation	Next safe step
Short runs only with one zone open	Load too small for minimum modulation	Compare zone status and manufacturer minimum output
Flow rises quickly while demand persists	Poor heat transfer or high target	Log return temperature and ask installer to assess
Demand rapidly flips on/off	Thermostat automation or hysteresis	Review schedules and automation traces
Short bursts coincide with hot water use	DHW heating	Separate DHW and CH signals
Burner stops with error/lockout	Possible appliance fault	Record error and contact qualified service engineer
Cycling mainly in spring/autumn	Low heat demand	Compare colder-day operation

Does short-cycling increase gas consumption?

Frequent starts can increase transient losses and may increase component wear, but the size of any efficiency penalty depends on the boiler design, cycling pattern and operating temperatures. It is not defensible to apply a blanket percentage penalty to every boiler. Modern condensing appliances can be efficient during long low-temperature operation; high return temperatures may reduce condensing opportunities. Use actual metered gas consumption, outdoor temperature and indoor comfort to assess whether a change helps.

If you have a pulse-output gas meter AliExpress price or utility data, compare similar weather periods using degree days or another temperature-normalised method. Do not assume that fewer burner starts necessarily means lower gas use: an adjustment could reduce cycling but also raise water temperature or overheat rooms. The relevant outcomes are fuel consumed, comfort, safe operation and stable control.

Can Home Assistant fix short-cycling?

Sometimes it can remove a software-created problem, such as two schedules fighting each other or a room controller calling for heat in tiny bursts. It cannot change a boiler’s physical minimum modulation, repair a restricted heat exchanger or guarantee minimum system flow. In many homes the most valuable Home Assistant action is to show the evidence clearly enough for an installer to diagnose the system. Keep the manufacturer’s own temperature and safety controls authoritative.

A sensible sequence is to observe the system unchanged, isolate the recurring pattern, check documented control settings, and then make one manufacturer-approved adjustment at a time with an installer where appropriate. Re-measure under comparable conditions. If changes increase lockouts, reduce hot-water safety or cause poor comfort, revert through the appropriate control interface and seek professional advice.

Troubleshooting checklist before calling an engineer

Record boiler model, firmware or controller model, heating type and approximate age.
Capture a representative timeline showing demand, burner status, flow temperature and zone state.
Note outdoor temperature, whether domestic hot water was used and whether the home was recovering from setback.
List the current user-accessible heating setpoint and whether weather compensation is enabled.
Check Home Assistant automations for repeated heat-demand commands or duplicated schedules.
Write down any fault codes or abnormal pressure readings without attempting internal repairs.
Give the engineer both the symptom and the evidence; ask about minimum output, flow, balancing and commissioning settings.

Frequently asked questions

How many boiler starts per hour are too many?

There is no universal number. Look at run duration, heat demand, appliance model and manufacturer guidance. Repeated very short starts during continuous demand deserve investigation.

Is short-cycling the same as a thermostat switching off?

No. A boiler burner can stop while the thermostat continues requesting heat. Log both signals separately.

Can I detect burner starts from a smart plug?

Only as an uncertain inference, and a boiler must not be powered through an unsuitable smart plug AliExpress price. Pump, fan and standby loads complicate identification.

Will an OpenTherm gateway show flame status?

Some combinations expose burner or flame-related status, but not all. Check the exact boiler, gateway and integration fields.

Can Modbus tell me why the boiler stopped?

Only if the appliance documents and exposes relevant operating states or fault registers. A Modbus connection alone does not guarantee this.

Does lowering flow temperature always solve cycling?

No. It may help in a suitable system, but minimum burner output, emitter area, flow and control logic still matter.

Do smart TRVs cause boiler short-cycling?

They can contribute when many valves close and the remaining heat load is very small. They are not inherently a fault.

Does a condensing boiler need long burner runs?

Long stable low-temperature runs can be beneficial, but the correct pattern depends on the appliance and heating demand.

Should I change anti-cycle settings?

Not without manufacturer instructions and competent commissioning advice. Anti-cycle protection should not be bypassed.

Can Home Assistant reset a boiler fault automatically?

Do not automate fault resets or bypass safety lockouts. Have the cause assessed by a qualified engineer.

Can I calculate boiler efficiency from flow and return temperatures?

Not from temperatures alone. You need reliable flow-rate and fuel measurements and must account for losses and measurement uncertainty.

What is the best first dashboard?

A time-aligned burner state, heating demand and flow-temperature history with zone state and outdoor temperature as context.