What's new in Kiosk Satellite 2026.8.56
Fixed: The Nearby devices permission row tells the truth on Android 11 and older
- Android versions before 12 grant the Bluetooth permissions at install but quietly gate scan results on location: without the Location permission and location services on, the scanner runs and hears nothing, which the row nevertheless reported as Granted. On a Fire tablet that meant a permanently empty Nearby list, nothing for Bermuda, and no clue anywhere (#240).
- On old devices the row now reads the location gate instead, and says which half of it is blocking scanning: "Location is off in the device settings" when the system-wide switch is the problem, the actual resolution of #240 and a setting nobody thinks to connect to Bluetooth, or that this Android version needs the Location permission when the grant is missing. This appears on the device page, the ESPHome page and both remote admin views.
- The Grant button asks for the right permission on those devices, and when the system switch is the blocker it opens the OS location settings screen, the only place that can flip it.
New: An invalid encryption key can no longer silently kill the ESPHome server
- The protocol's key must be the base64 form of 32 random bytes, and a hand-typed word used to stop the server without a trace, taking mDNS discovery down with it and leaving Home Assistant's generic "unable to connect" as the only symptom (#239).
- An invalid key now surfaces as a clear failure reason on the settings pages, with the recovery spelled out: clear the Encryption key field and a fresh valid key is generated automatically.
New: Scanner failures and the announced address land in the proxy log
- Bluetooth scanner failures now appear in the proxy log shown by the remote admin, named with their reason, instead of only Android's internal logcat. A scanner killed by a permission error or a Bluetooth stack failure used to look exactly like a healthy one from every surface a user could reach (#240).
- The log also states the server's bind scope and the IP address announced to Home Assistant over mDNS, logged again whenever it changes (#239). When discovery finds the device but Home Assistant cannot connect to it, which address Home Assistant was told to dial is the first question, and on multi-interface devices it was previously unanswerable.