Tasmota's OpenTherm driver fixed to keep talking after a lost link
A contributor fixed a six-second silence after lost connections that broke the OpenTherm timing rules, with Claude's help, and tested it on their own boiler.
Credits
Earliest dated source:
The full story
In Tasmota's OpenTherm driver, three timeouts in a row put the driver into a disconnected state and it then sent no frame for about six seconds while it cooled down and restarted the handshake. OpenTherm 2.2 requires the master to send a frame at least every second, and a boiler that sees no valid frame for five seconds treats the line as short-circuited, a heat demand, and runs on its own setpoints. So a brief hiccup turned into exactly that.
The pull request removes the silent cooldown in the driver's state machine so frames keep coming. The contributor says the code and description were written with Claude's help and tested on their own boiler with an ESP32-S3.
How it was done
Tools
Themes
Loading themes…
Sources
From the maker's own write-up or code. We summarise what they report; we haven't tested it ourselves.
- Tasmota Project: OpenTherm: no silent cooldown after a lost connectionSource byline: pebl-hankPublished
The Tasmota pull request with the analysis and the fix.
- The code: github.comRepository account: arendst
Tasmota's contributing guide, linked from the pull request's checklist.