A module that is online but cut off from the control box keeps serving and
publishing a full document of blank and default values. Read literally that
is an idle spa: no temperatures, salt level 0, lights and jets off, and
controls that accept a value and snap back.
- The spa counts as reporting only while telemetry is fresh (something
arrived in the last five minutes) and carries control-box data. Otherwise
every entity is unavailable, and the reason is logged once per change.
- The entry still loads in that state, so entities return on their own when
the spa reports again.
- A watchdog catches silence between updates, and reloads the entry when the
broker connection stays down for three minutes. The broker is the only
control path and its credentials rotate; paho reconnects with the old ones,
so only a fresh sign-in recovers it.
- Version 0.2.0.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The dongle has no DNS name and takes its address from DHCP, so a configured
local /status URL goes stale when the lease changes. Setup treated that as
fatal: every entity went unavailable and control (which never used the local
path) went down with it.
- A local URL that does not answer at setup no longer fails the entry; the
coordinator subscribes to the cloud broker for telemetry instead and logs a
warning.
- After four consecutive failed local polls the coordinator switches to the
cloud the same way, instead of holding the last local values forever.
- When the local URL answers again it takes over: the cloud subscription is
dropped along with what it delivered, so a stale cloud value cannot shadow a
fresh local one.
- New reconfigure step changes the local URL without signing in again.
- Version 0.1.1.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>