Hot Spring
hotspring
The Hot Spring integration allows you to monitor and control your Hot Spring spa equipped with the HotSpring Connected Spa Kit 2 (part number 79994) module directly from Home Assistant.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature) | |
select | Mode picker (as switches) |
What people report
Hot Spring spas with the Connected Spa Kit 2 work over the local network. The Spa Network Adapter is rejected, and one 2024 HighLife spa had unknown entities.
- Works2
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Hot Spring Connected Spa Kit 2 | Works Local | Home Network Adapter spas supported; Celsius support added 2026Saved copySupported devices: Hot Spring spas equipped with the HotSpring Connected Spa Kit 2 (part number 79994) local network module.. Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Hot Spring HighLife Envoy NXT | Works Local | Fixed after report; HNA firmware ND25.1202E0 left entities unknownSaved copyThe problem I have a 2024 Hot Spring HighLife Envoy NXT using the new Connected Spa Kit V2 (Watkins 79994). The Connected Spa hardware is fully operational. The current Hot Spring Spas app communicates with the spa, displays the current and target temperature, and can successfully control the spa (for example, turning the jets on/off). Home Assistant automatically discovers the HNA and successfully adds the built-in Hot Spring integration. Home Assistant also reports Spa connected = Connected and correctly identifies the spa as a HotSpring HighLife. However, Current Temperature, Target … Excerpt saved from GitHub on 2026-10-23. | Issue #184167 · 2026-10 | |
| Hot Spring Spa Network Adapter (SNA) | Won’t be supported Local | Rejected in config flow; only the Home Network Adapter worksSaved copyProposed change Hotfix intended for the 2026.9.1 patch release (follow-up to #181256). Hot Spring Spas use two network adapters: the Home Network Adapter (HNA), which serves spa telemetry, and the Spa Network Adapter (SNA), which wirelessly links the spa motherboard to the HNA. Both adapters advertise the same mDNS service (`watkins_spa*._ws._tcp.local.`) and share the same `rootTopic`. Previously, discovering an SNA via Zeroconf would overwrite the config entry's host with the SNA's IP, which does not provide telemetry and caused entities to flap between available and unavailable. Using … Excerpt saved from GitHub on 2026-10-23. | PR #181261 · 2026-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 12 |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 2026.9 |
| Set up in the UI | Yes |
| Maintainers | @Moustachauve |
Devices listed in its documentation
- Hot Spring spas equipped with the HotSpring Connected Spa Kit 2 (part number 79994) local network module.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.