What's new in Kiosk Satellite 2026.8.3
Stand-alone motion sensor over MQTT
Motion detection is no longer tied to the screensaver: a new Motion Detection group in the Camera settings has a Motion sensor switch that exposes movement as its own Home Assistant binary sensor over MQTT. The sensor turns on when the camera sees motion and clears itself after a configurable quiet delay (Clear after), and unlike the screensaver's motion features the camera keeps watching even while the screen is off, so the automation everyone actually wants, turning the panel on when someone walks into the room, finally works.
The usual camera usage warning applies: the camera runs permanently while the sensor is on which increases CPU usage and adds heat to the device.
Motion detection got smarter about light
Camera motion detection no longer mistakes the device's own light for movement. The screensaver going dark could reflect off the room, read as motion and dismiss the screensaver the instant it started, an endless loop on dark clock faces, and a slideshow swapping between differently lit photos could do the same mid-session. Detection now discounts uniform lighting shifts, including the camera auto-exposure adjustment that follows them, and stands down for a couple of seconds around the app's own screen transitions: screensaver start and stop, screen power, brightness changes and slide changes. A moving person still reads as motion throughout, because a body changes the frame locally in both directions while light moves everything together.
Improvements
- Motion detection's tuning lives with the camera now: Motion frame rate and Motion sensitivity moved from the Screensaver section into the Camera settings' Motion Detection group, since they tune every motion feature, not just the screensaver's. Dismiss on motion and Postpone stay where they were, and the remote admin's Latest snapshot preview moved to its own group at the end of the Camera page so the new settings are not buried under the image.
- Motion-triggered camera snapshots publish once per motion arrival instead of every ten seconds for as long as movement continues: someone staying in front of the device updates the retained MQTT snapshot once, and the next update comes after the sensor has cleared and motion returns.
Bug Fixes
- Restoring a backup as a new device no longer copies the Sendspin player identity (#136). Both devices ended up connecting to Music Assistant as one player and kicked each other off in an endless connect/disconnect loop, with neither ever syncing; a new-device restore now keeps the restoring device's own identity, while a replacement-device restore still adopts the backup's so Music Assistant sees the same player it always had.
- The Filter dashboard updates optimization now catches entities referenced inside card templates (#139), such as a custom button-card's name, label and style templates: any entity id written in a template is included in the filter's allowlist, so those cards keep updating. Only entity ids computed dynamically inside a template remain invisible to it.
- CPU temperature now reports on devices whose thermal sensors do not name the CPU (#138), by also accepting the SoC sensor spellings MediaTek, Exynos and Qualcomm devices use. When no readable sensor exists at all, the app logs which sensors the device exposes, so a bug report's app logs carry the answer.