What's new in Kiosk Satellite 2026.8.89
One visual system for the device and the remote admin
The remote admin page now follows the device's settings screens to the pixel, and the device picks up the few things the remote did better. Same colors, same type sizes, same spacing, same controls, so a setting reads the same whether you are at the wall or at your desk.
- Colors and type. The remote's muted text, control fill and hairlines are the device's exact values, and its type is the device's ramp: page titles 22 semibold, row titles 17 medium over a 13 description, section headings 14, dialog titles 20. Cards sit 16 apart, the page is padded like the device's settings and the reading column caps at the same width.
- Buttons. The remote's buttons are the device's 44 high pills, every dialog's Cancel is a borderless text button on both surfaces, and the icon actions on list rows (play, import, download, delete, move) are 40 discs on the remote the way they are on the device.
- Phone width. Both surfaces reflow a settings row the same way under 640 wide: a short control (a switch, a number, one button) shares the first line with the name, a wide control stacks under the name across the row and the description goes beneath. The device's permission rows and list rows follow this rule now instead of squeezing their text beside the control, and a segmented pill that does not fit (the Logs source, the File Manager location) scrolls sideways under the edge fade on both surfaces instead of wrapping or spilling, down to a 320 wide phone.
- Fields. A time of day shows in a control box with a clock glyph and opens one time picker on both surfaces, hour and minute boxes with stepper chevrons that can also be typed into, in place of the Material dial on the device and the browser's own input on the remote. A color shows as a swatch on both and opens the same picker dialog on the remote as on the device. The ESPHome encryption key is a read-only copy box on both: tap it, the whole key is on the clipboard and a toast says Copied. The remote's switches, checkboxes, radios, fields, dropdowns and sliders are drawn at the device's Material 3 sizes, with sliders running the full row width under the name and value the way the device's do.
- Editors. Every editor field carries its label above the control on both surfaces. The device's dialogs drop the floating label that sat across the field's border, and the remote's editors keep the label's spacing when a field is shown again after its type changes. Fields stack 16 apart on both.
- Messages. One banner shape carries a state that makes a section inert (Bluetooth off) or a failure that blocks a page (the setup wizard's connection errors) on both surfaces. The remote admin has the device's toast now: a quick control that lands says so, a copied log or key says Copied, and the message box stays for answers that need a button. The remote's hint rows carry the device's info and warning icons.
- Lists. Orderable lists (the cameras in a view, the camera views a screensaver cycles, the At a Glance entities) carry Move up, Move down and Remove on the device now, the way the remote's do, so a tablet reorders without a drag. Tapping a glance entity's row edits it. The schedule and widgets editors end in an add row on both surfaces in place of a button. The remote's rail tiles take the device's size and radius.
- File Manager. The remote admin's File Manager no longer rebuilds the page on every click: the root tabs, the upload button and the path stay put, and the listing is a fixed pane that reaches the bottom of the window and scrolls inside, the way the Logs page works. Deleting a file asks in the app's own dialog, and upload or download failures say so in a toast.
Bug Fixes
- On a device whose Android build has no Bluetooth LE support (a Facebook Portal Gen 1 on Android 9, LineageOS ports that leave the feature declaration out), the Bluetooth proxy could be switched on but every scan failed the instant it started, forever, with "code=3 internal error" in the log. Enable Bluetooth proxy now stays off there and the switch says why, on the device and in the remote admin page. Everything else under ESPHome works as before.