What's new in Kiosk Satellite v0.33.3-beta
Graceful recovery from WiFi network drops
Kiosk Satellite now watches Android's own network state and repairs everything the moment connectivity returns, instead of leaving each subsystem to its own timers. The dashboard is checked and fixed on the spot: a dead or half-open Home Assistant websocket is reconnected, Home Assistant's "Unable to connect, retrying in N seconds" screen is retried immediately instead of waiting out its growing countdown, and an error page is re-navigated back to the dashboard. MQTT no longer stays offline forever when the app starts before the network is up, so a device that boots ahead of the router now brings its Home Assistant entities back on its own, and a stuck broker connection is detected within a minute through ping timeouts. Sendspin, the At a Glance entity feed and the secure context proxy all reconnect immediately as well.
Web page failures heal themselves
Server errors now recover the way network errors always did: a 502 or 504 from a reverse proxy (or the secure context proxy) during an outage used to sit on screen until an app restart, because auto reload only watched network-level failures; the page now retries every few seconds until Home Assistant answers again. The Website screensaver and rotation overlay pages retry failed loads too, and a crashed page renderer in the screensaver or camera view rebuilds its own WebView instead of Android killing the whole app, which matters most on low-RAM devices.
Start the screensaver with a gesture
A new gesture action starts the screensaver, next to the other Kiosk Satellite actions in the gesture editor on the device and in the remote admin. Start only: any tap already dismisses a running screensaver.
Improvements
- Camera streams routed through the secure context proxy fail fast and reconnect when Home Assistant becomes unreachable mid stream, instead of hanging on a frozen frame.
- Retained MQTT payloads on command topics are now ignored when the broker replays them at reconnect, so a stale retained press (a reload, a restart, a volume set) no longer refires on every network hiccup. If you deliberately published retained commands for offline devices to pick up on their return, publish them unretained instead, as Home Assistant itself does.