What's new in Kiosk Satellite 2026.8.104
A Device name field in the setup wizard, so a kiosk arrives in Home Assistant (ESPhome) under that name instead of a generated id. Plus three fixes: video pushed over DLNA plays on MediaTek devices, a video that cannot play finally says why and a brightness knob moved under a screensaver applies at once again.
New Feature: Device name in the wizard
- A Device name field on the setup wizard's first page, on the device and in the remote admin alike, above Remote administration and filled in with the device model. It is the name Home Assistant, the remote admin and the network use for the kiosk.
- The ESPHome node name is built from it at the ESPHome server's first start, under a
ks-prefix so every kiosk sorts together: a Fire HD 10 left at its model name shows up asks-amazon-kftuwi, and a kiosk named Kitchen Tablet asks-kitchen-tabletwithesphome.ks_kitchen_tablet_notificationactions, instead of a generatedkiosk-satellite-<id>. A name typed in the ESPHome Node name setting itself is still taken as written. - It can be changed any time under Settings, Device.
Bug Fixes
- Video pushed over DLNA no longer fails with an error icon on MediaTek devices (#374), among them the Echo Show 8 and the Lenovo Smart Tab M10. The video surface Flutter draws into holds seven frames of its own, so the decoder was asked for fourteen buffers where it caps out around ten, and it refused to start: the file, the codec and the profile were never the problem, and the same video played fine in a dashboard card. Such a video is now retried once on a platform view, which asks for far fewer buffers, and it plays. Screensaver videos, local and Immich, take the same retry.
- A video that cannot play now says why. The error icon carried no wording at all, no line reached the App Logs and the transport stayed on PLAYING, so Home Assistant went on showing the media as playing on a kiosk that had given up on it. The card now names the reason, the full player error goes to the App Logs, and the media stops a few seconds later so the controller lets go.
- Moving Default brightness (or Maximum brightness, or the Screen light from Home Assistant) while a screensaver shows that leaves brightness alone, such as a clock with Screensaver brightness off, applies at once again. The write was being held back until the screensaver ended as if the screensaver owned the panel; it is now held back only while the screensaver has actually taken the panel with a Dim or Black mode, its own brightness, or a schedule entry's level.