What's new in Kiosk Satellite 2026.8.36
Renameable At a Glance entities, and fixes for MQTT disconnects with the camera enabled, a camera CPU regression, and a stuck Charging entity.
New: At a Glance entities can be renamed (#206)
- Each chosen entity in the picker, in device settings and the remote admin alike, now has an Edit action opening a single dialog with the entity's name and its displayed value.
- A custom name replaces the Home Assistant name on the screensaver row, and clearing the field goes back to following Home Assistant. Handy where the registry name is a mouthful ("Garage Door Left Side") and the row only needs "Garage".
Fix: MQTT no longer drops repeatedly while the device camera is enabled (#207)
- Some brokers cap the size of an MQTT packet and answer an oversize publish by dropping the whole connection. A camera frame larger than the cap your broker advertises is now skipped with a log line instead of sent, so a high snapshot resolution can no longer cost you the connection.
- The fresh camera frame taken when the connection comes up is now throttled across reconnects, so a snapshot publish that kills the link can no longer re-kill every reconnect and keep the device offline for minutes.
- A connect attempt that fails or times out is now fully disarmed. Before, it could linger as a ghost session that fights the real connection over the client id, with the broker kicking whichever connected last, flapping availability every minute or two.
Fix: The camera pipeline no longer restarts into a faster frame rate than the one it is escaping (#164)
- On sensors whose only pinned frame rate is the full one, the exposure-hunt fallback meant restarting into the full-rate pipeline, the very cost the affected hardware cannot pay. A pinned rate is now used only when it is no faster than the slow range it replaces.
Fix: The Charging entity no longer sticks at "Charging" (#205)
- On devices whose kernel misreports the battery status, charging is now read from the charger's own plugged flag, in MQTT, the remote admin header and the health endpoint alike. A docked kiosk holding at 100% still reads as charging.