Survive a dead local status URL, and go unavailable when the spa is not reporting (#2)

This commit was merged in pull request #2.
This commit is contained in:
dfritz committed 2026-11-15 04:51:23 +00:00
1 parent 46a353071d
commit 5af5412248
13 files changed
+264 -15

No files matched your search

+27
View File
@@ -79,6 +79,33 @@ local HTTP endpoint instead of subscribed over the cloud broker, keeping
monitoring on-LAN and off the vendor cloud. Control still uses the cloud MQTT
connection. Leave it blank to use cloud MQTT for reads.
The module has no DNS name and takes its address from DHCP. While the URL does
not answer, telemetry is read from the cloud instead, and the local poll takes
over again when it answers. To change the URL without signing in again, use
**Reconfigure** on the integration entry.
A Connected Spa kit can have two modules on the LAN that both serve `/status`.
Only the one linked to the control box returns the spa's state; the other
returns the blank document described below. Use the one with temperatures in it.
## Health and availability
Every entity is **unavailable** unless telemetry arrived in the last five
minutes and carries control-box data. A module that is online but cut off from
the control box keeps serving, and publishing to the cloud, a full document of
blank and default values: empty `setWaterTemperature`,
`currentWaterTemperature` and `ControlBoxFirmwareVersion`, salt level 0,
lights and jets off. Commands sent in that state change nothing. Power-cycling
the module that is linked to the control box has recovered it; the entities
come back on their own once real data arrives.
The broker is the only control path and its credentials rotate. If the broker
connection stays down for three minutes the integration reloads itself, which
signs in again and fetches current credentials.
To be told when the spa stops reporting, trigger an automation on an entity
(for example the climate entity) being `unavailable` for a few minutes.
## License
MIT — see [LICENSE](LICENSE).