Skip to content
Prompt & SolderHow to Ask Claude
All builds
SHNo photo
Worked Proof shown

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

  • Source byline pebl-hank Source ↗
  • Repository account arendst Source ↗

Earliest dated source: 17 Nov 2026

Code ↗

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 connectionCode or repositorygithub.com
    Source byline: pebl-hankPublished 17 Nov 2026

    The Tasmota pull request with the analysis and the fix.

  • The code: github.comCode or repositorygithub.com
    Repository account: arendst

    Tasmota's contributing guide, linked from the pull request's checklist.

Related builds

Finding related builds…

Prompt & Solder

An independent community project. Not affiliated with Anthropic.

What this is. Real projects where people used Claude to build, fix, port, revive or take apart something, from jailbroken Kindles to rebuilt DOS games, plus the times it went badly wrong. Every build links to where it was shared, and every source is listed here.

How far to trust it. We summarise what people reported and say what each build rests on: a full write-up with code, a short post, or a passing comment. We haven't tested them ourselves. Photos are shown from the original sources with credit. Only modify hardware you own, and back up first.

Privacy. No accounts. Analytics cookies (Google Analytics) only if you accept them; no ads or cross-site tracking. Searches are counted anonymously (just the words) to show what's popular, and so are clicks on Ask Claude (just the count). The Claude connector only receives the search words your Claude sends it.

How toAsk ClaudeEvery sourceStatsSubmit a buildPrivacyRSS