Answers
How to manage and update dozens of Raspberry Pi kiosks remotely
Group the kiosks, run updates in waves that stop on failures, queue them for offline screens, and watch health so you know which ones need you.
Asked on Raspberry Pi Forums, August 2018: “Managing Kiosks on Large Network”
Short answer
Give each kiosk a way to be reached without a fixed address, group them by site, and push changes in waves: a few kiosks first, then the rest, stopping if something fails. Kiosks that are off get the change when they come back.
With Ansible
Ansible over SSH is the common free answer and works well when every kiosk is reachable on a stable network. Use serial: 2 then a larger batch so a bad change stops early, and max_fail_percentage to halt the run. It assumes the kiosks are reachable when you run it; a kiosk that's off or behind NAT is simply skipped, and an interrupted apt run can leave the package lock held.
With a managed OS
balena and Mender update the whole image atomically, which is the strongest guarantee, at the cost of reflashing every kiosk onto their OS. Worth it for a new product; heavy for kiosks already installed.
With Fieldhand, on the OS the kiosks already run
- Install the agent on each kiosk, or bake the install token into your image so new ones enroll themselves.
- Tag them, for example
site:austinandkiosk. - In Fleet commands, run a command, a service restart or a package upgrade on a tag, in waves, stopping on failures. Offline kiosks run it when they come back, and each kiosk's output is kept.
- Schedule it for the night, in your time zone.
- The fleet view shows which kiosks are offline, full or hot, and the screen of each one is a click away (see Device page).
sudo apt-get update && sudo apt-get -y upgrade && sudo systemctl restart kiosk
More in Fleet commands and Update a fleet.
By Abner Souza, who builds Fieldhand. Updated 2026-10-23. Something wrong or out of date? Write to support@fieldhand.dev.
Something wrong or missing on this page? Tell us.