Balboa Spa Client
balboa
The Balboa Spa Client integration adds support for Balboa Spa WiFi Modules to be used within 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 | |
switch | Switch or outlet | |
climate | Thermostat | |
fan | Fan | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
select | Mode picker (as switches) |
What people report
Balboa spas work locally through the BWA Wi-Fi module. Wi-Fi range extenders and spa power cycles cause connection failures.
- Works2
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Balboa BP501G1 spa control | Works Local | Setup failed after 2025.1; issue closed completedSaved copyThe problem Balboa integration stopped working after updating to 2025 .1, shows failed to set up. ### What version of Home Assistant Core has the issue? core-2025.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Balboa ### Link to integration documentation on our website https://www.home-assistant.io/integrations/balboa ### Diagnostics information Logger: homeassistant.config_entries Source: config_entries.py:640 First occurred: 10:05:52 PM (1 occurrences) Last … Excerpt saved from GitHub on 2026-10-23. | Issue #135064 · 2025-01 | |
| Balboa spa hot tub | Works | 16-year-old spa still works in HA despite paid appSaved copy16 year old balboa spa hot tub, went paid app long ago but still works on HA! Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2026-07 | |
| Balboa BWA Wi-Fi Module | Partly works Local | Connection refused behind Wi-Fi extenders in MAC-proxy mode; module disconnects periodicallySaved copy… extender/MAC-proxy case (which sounds network-layer), but the "Connection Refused / spa becomes unavailable" symptom overlaps heavily with a firmware-side bug in the BWA Wi-Fi Module (part 50350) where the module accepts a TCP connection, streams status for ~30s, then goes silent without closing the socket. To the stock integration the connection still looks "up" and entity states freeze. I measured this over a 14.75h soak on excellent Wi-Fi (RSSI −44 dBm, 3m to AP): the module was silently unresponsive two-thirds of the time, 41 of 42 disconnects were the silent-socket pattern. Two artifacts … Excerpt saved from GitHub on 2026-10-23. | Issue #176961 · 2026-07 |
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 push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- DHCP
Details
| Installs (analytics) | 551 (0.08%) |
|---|---|
| Added in | Home Assistant 2021.12 |
| Set up in the UI | Yes |
| Maintainers | @garbled1, @natekspencer |
Limitations from the docs
- The WiFi Module is a direct connection to the control panel of the spa. Certain combinations of settings are not possible due to limitations of the spa.
- Turning on certain pumps, depending on the spa configuration, may cause other pumps to come online as well.
- The spa WiFi Module will need to be configured initially by the phone app to authenticate and get an IP on your network.
- The WiFi Module will automatically disconnect from Home Assistant periodically, and then be automatically reconnected. The disconnect is built-in to the hardware.
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.
