New integration: Watts Home (Tekmar) Wi-Fi Thermostats for Radiant Heat

bhamilton · April 27, 2026, 1:46am

I put together a new integration which directly integrates Watts Home / Tekmar radiant heat (HVAC and hot water) thermostats into Home Assistant. This integration currently supports Watts Home / Tekmar 561, 562, 563, and 564 models, but others might work (your mileage may vary).

This is based on the wonderful MQTT gateway by AlbinoDrought (but it doesn’t require setting up a Docker instance or integrate MQTT into Home Assistant).

It works in my home, but I’d love feedback to see if it works for others!

To install, if you haven’t already:

Install HACS
Go to HACS > 3 dots menu > Custom Repositories, add https://github.com/bhamiltoncx/ha-watts-home/, select Integration
Install the Watts Home (Tekmar) integration

Screenshots:

haNube · June 6, 2026, 7:45pm

Just installed it for Tekmar 561 - works well, thank you !
Of course, still would be great to add a mode change feature and (can't even dream about it) a local control without using a Tekmar account

Bolt693 · June 15, 2026, 6:09pm

Works! Thank you so much for making this. I also have the Tekmar561's and seems to work.

Bolt693 · June 15, 2026, 6:13pm

Any way to get the floor temp sensor into this as well on the Tekmar 561's?

bhamilton · June 16, 2026, 8:27pm

Yes, I believe Tekmar requires a tekmarNet 486 gateway for this:

https://www.watts.com/products/hvac-hot-water-solutions/controls/control-accessories/486

The individual thermostats just don't have any (documented) interface for local control.

bhamilton · June 16, 2026, 8:28pm

I got a pull request to add this and other functionality:

github.com/bhamiltoncx/ha-watts-home

feat: extended entity support for Tekmar 5xx thermostats

main ← salanki:feat/extended-entities

opened 07:07PM - 25 May 26 UTC

salanki

+2765 -190

## Summary Adds support for the full range of Tekmar 5xx thermostat capabilitie…s exposed by the Watts Home cloud API — binary sensors, humidifier control, radiant floor heating, energy monitoring, away mode, and emergency heat — along with two correctness fixes for the existing climate entity. Based on reverse-engineering the Watts Home API and live integration testing against real Tekmar 563 hardware with 14 zones. All write operations are verified with round-trip tests (write → /Refresh → re-read → assert → restore). ## Bug fixes ### Always send both Heat and Cool in temperature writes The Watts API silently corrupts the omitted setpoint when only one field is sent. For example, sending `{"Settings": {"Heat": 66}}` in Heat mode resets Cool to `Schedule.CoolMax` (e.g. 95°F). The fix always includes both `Heat` and `Cool` (or `HeatHold`/`CoolHold` when schedule is active), echoing the current value for the unchanged field. ### Fix setpoint property mode check `target_temperature` / `target_temperature_high` / `target_temperature_low` previously checked whether the device *supports* `heat_cool` mode, not whether it's *currently in* that mode. A 562/563 in Heat mode would hide the single `target_temperature` and show the dual high/low controls instead. Fixed to check `self.hvac_mode == HVACMode.HEAT_COOL`. ### Fix `_patch()` empty response body Some PATCH endpoints return an empty body on success. The previous code unconditionally called `resp.json()`, which would fail. Now tolerates empty responses. ### Fix `async_unload_entry` session leak Only closes the HTTP session after a successful platform unload. ## New features ### Expanded Pydantic models Models for API fields not previously captured: `State.Sub`, `Fan.Active`/`Relay`, `Hum` (humidifier), `Schedule` (floor heating), `Energy` (daily/monthly kWh), `Location` (away state). All fields have defaults so existing devices parse without changes. ### Optimistic state updates `coordinator.optimistic_update()` immediately reflects write operations in entity state via `async_set_updated_data()`, preventing UI snap-back while waiting for the cloud to propagate. ### Post-write `/Device/{id}/Refresh` After every write, calls the `/Refresh` endpoint to force the thermostat to sync with the cloud before the next poll. Reduces state reflection time from up to 40s to ~5s. ### Binary sensor platform - **Fan Running** — `Fan.Relay` state (standalone G-terminal circulation, not the HVAC blower) - **Radiant Heating** — floor temp below occupied setpoint - **Humidifier Running** — fan relay on with no heat/cool call (heuristic) - **Cold Weather Shutdown** — `State.Sub == "CWSD"` (diagnostic) ### Humidifier platform For devices with `Hum.Active == 1`: target humidity, current humidity from RH sensor, action state. Always-on (Watts API has no humidifier on/off toggle). ### Floor Min number entity Writable occupied floor minimum (`Schedule.Floor.W`) for devices with radiant floor sensors. ### Switch platform - **Away** — per-location toggle via `PATCH /Location/{id}/State` - **Emergency Heat** — per-device, sets mode to `Emer`; restores previous mode on turn-off ### Additional sensors - **Floor Temperature** / **Floor Max** (diagnostic) - **Heat Today** / **Cool Today** — daily energy kWh (`total_increasing`) ### Other - Emergency heat mode mapping (`Emer` → switch entity since `HVACMode` has no `EMERGENCY_HEAT`) - Default poll interval changed to 40s (matches Watts Home app cadence) - Rename test env vars from `WAHA_*` to `WATTS_*` ## Testing All integration tests make real API changes, verify via `/Refresh` + re-read, then restore original values: - Temperature round-trip (both-field write, no corruption of unchanged setpoint) - Mode switching (Heat → Cool → Auto with setpoint verification) - Humidity, floor min, away state round-trips - Verification that all new model fields are present in real API responses ## Test plan - [ ] Install via HACS, configure with Watts credentials - [ ] Verify climate entities show correct mode, setpoints, current temp - [ ] Change a setpoint in HA → verify it reflects in the Watts Home app - [ ] Verify binary sensors show correct state - [ ] Verify humidifier entity shows target/current humidity - [ ] Toggle away switch → verify in Watts Home app - [ ] Check energy sensors show kWh values - [ ] Run for 24h, verify no token refresh errors

I asked for a few fixes, but if the author doesn't implement them, I'll go ahead and do it myself.

haNube · June 22, 2026, 1:29am

Possibly I wasn't clear enough about the mode change - I was talking about a possibility to change between Home and Away modes...

bhamilton · July 19, 2026, 4:31pm

Got it. This is now implemented in release 1.0.1 thanks to salanki’s work which I adapted. The integration now exposes a single switch switch.{name}_away which enables the Away mode on all thermostats in the home when toggled on.

haNube · July 29, 2026, 11:39pm

Thanks for letting me know !

bhamilton · August 23, 2026, 4:22pm

I just released version 1.1.1 to add support for Tekmar Wi-Fi Setpoint Control 170 devices.

1.1.1 (2026-08-23)

Bug Fixes

keep the floor entity’s upper setpoint bound usable (#17) (412f70d)
support Tekmar devices which are missing low/high setpoint (#15) (cfae065)
support the Tekmar 170 Wi-Fi Setpoint Control (#21) (c67c39c)

GMD999 · September 14, 2026, 11:13am

Hi Ben,

Thanks for creating this integration. I’m using Watts Home (Tekmar) v1.1.1 with Tekmar 561 thermostats and have run into what appears to be a multi-location limitation.

My Watts Home account contains two locations:

Home — 3 × Tekmar 561 thermostats
Cottage — 1 × Tekmar 561 thermostat

Normally Home is set as the Primary location in the Watts Home app. With Home Primary, the integration imports and updates the three Home thermostats, but the Cottage thermostat is not active.

I tested changing the Watts Home Primary location:

Changed Primary from Home to Cottage.
Reloaded the Watts Home integration in Home Assistant.
The Cottage Tekmar 561 immediately appeared and worked correctly, including room temperature, floor temperature, outdoor temperature, setpoint and other entities.
Changed the Watts Home Primary location back to Home without reloading the integration.
Within about two minutes, every entity belonging to the Cottage thermostat became Unavailable.

The Cottage device remains registered in Home Assistant, but its data stops updating whenever Home is Primary.

This seems to indicate that the integration is polling only whichever Watts location is currently marked Primary/default, rather than all locations returned by the account.

Would it be possible for the integration to support all Watts locations associated with an account simultaneously?

I’m happy to provide diagnostics, logs, screenshots or perform additional testing if useful.

Thanks again for the integration.

bhamilton · September 14, 2026, 11:30am

Welcome! Debug logs would be great. You can send them to me in a private message.

GMD999 · September 15, 2026, 3:33am

Thanks Ben. I’m a new member of the forum and I don’t seem to have the option to initiate a private message yet. Could you send me a PM and I’ll reply with the sanitized debug log?

bhamilton · September 15, 2026, 12:25pm

Sure, sent.

bhamilton · September 15, 2026, 4:43pm

Thanks for the report! I filed Only the default Watts Home location is polled · Issue #24 · bhamiltoncx/ha-watts-home · GitHub and landed a fix in fix: poll devices from every Watts Home location by bhamiltoncx · Pull Request #25 · bhamiltoncx/ha-watts-home · GitHub .

I released the fix in v1.1.2. Enjoy!

GMD999 · September 17, 2026, 10:23pm

Thanks for the revision. It worked well. Very helpful

posterChild · September 21, 2026, 1:33pm

Just wanted to say I appreciate you! This dropped in easily and now I can work my radiant heat into my workflows.