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>
13 lines
373 B
JSON
13 lines
373 B
JSON
{
|
|
"domain": "hotspring",
|
|
"name": "Hot Spring Connected Spa",
|
|
"codeowners": ["@fritzlab"],
|
|
"config_flow": true,
|
|
"documentation": "https://code.fritzlab.net/homeassistant/hotspring",
|
|
"issue_tracker": "https://code.fritzlab.net/homeassistant/hotspring/issues",
|
|
"iot_class": "cloud_push",
|
|
"integration_type": "hub",
|
|
"requirements": [],
|
|
"version": "0.2.0"
|
|
}
|