You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
The relay notices when the heater has stopped talking to Ayla, within
minutes.
The problem: after a relay outage of a few minutes (a reboot of the
Home Assistant host), the heater's Wi-Fi module stops connecting to
the cloud. It still looks up the cloud's name but opens no connection,
until its network connection drops. Seen live for 8.5 hours, while health
said unknown: too few dials observed yet and no repair appeared.
The probe: a healthy heater passes a local reporting-mask write on to
the cloud about 100 ms before it confirms it locally; a broken one
confirms it with nothing sent to the cloud. The relay sends the mask
when the cloud has been quiet (5 minutes after start, then every 30), and
every routine renewal counts too.
Result: health degraded with code cloud_down, and the repair Water heater isn't reaching Ayla. /state has cloud_probe, and the Relay health sensor shows it as an attribute. CLOUD_PROBE=0 turns it
off; CLOUD_PROBE_AFTER sets the interval.
Optional automatic fix: a network switch (the integration's Configure).
What it does: when the cloud side is down, Home Assistant turns the
switch off for 90 seconds, then on, so the heater rejoins the network and
reconnects, as after a power cycle. At most once every 6 hours; turning it
back on is retried, and a Home Assistant restart mid-way turns it back on
at the next start.
Which switch: anything that cuts the heater's network access while
it's off. With UniFi, add the heater to the UniFi integration's block
client list and pick that switch. A quick Wi-Fi "reconnect" doesn't
work: the heater rejoins in seconds without resetting.
Measured: a 90-second block, then unblock, brought the cloud side
back at once (connection, config fetch, Local Connect re-registered).
With several heaters, the switch is used for the first heater only.
Docs
"Open in Home Assistant" buttons in the install steps: one adds the
repository and opens the add-on, one opens the integration in HACS, one
starts the integration's setup.
A much shorter README (437 → about 150 lines): what you get, what you
need, four install steps, good-to-know and uninstall. The rest moved,
unchanged, to new pages:
docs/USING.md: every entity, writes, the dashboard, outages, uninstalling in detail;
DNS_STEERING.md opens with a 3-step quick start: turn on dns_server, point the router's DHCP DNS at Home Assistant and check it,
then power-cycle the heater. The README links straight to it.
STEERING.md gains Before you start (find and reserve the heater's IP)
and the log lines that show Local Connect is armed.
Dropped: the README's old release steps, superseded by docs/RELEASING.md.