Running without internet
Once installed, pikiosk works fully on a network with no internet access. Nothing it does at runtime contacts the internet, and nothing stops working when the internet is down or blocked.
What needs internet
| When | Why | Without it |
|---|---|---|
Installing with get.sh |
Downloads the release and the packages. | Install from the image instead. |
| First boot | Nothing: release images from v0.2.0 on come with every package installed. Older images, and installs onto your own Raspberry Pi OS card, download Chromium, sway, mpv, PipeWire, UxPlay and the rest from the Debian and Raspberry Pi package mirrors. | With a v0.2.0 or newer image, nothing: the first boot works offline. Otherwise the install waits and retries until the network is up. |
| System → Update | Downloads OS package updates from the same mirrors, and the latest pikiosk release from GitHub. | The update fails and nothing changes. Only runs when you press the button. |
| Release check | Twice a day, asks api.github.com whether a newer pikiosk release exists. On by default; turn it off under System → Releases. |
The check fails quietly and shows the error under System. Nothing else is affected. |
| YouTube cast button | Only while you cast: YouTube's TV app and the videos come from YouTube. | Nothing happens when you pick the kiosk in the YouTube app. |
That is all. With the release check off, the kiosk never contacts the internet on its own.
What works offline
Everything else stays on your local network:
- the web UI, the REST API and its docs page (
/api.html), served by the kiosk itself with no external fonts or scripts - MQTT and Home Assistant discovery, to a broker on your network
- web views and camera streams on your network
- sounds, the DLNA speaker and the AirPlay receiver
- screen power, brightness, sleep schedules, rotations and preloading
- the watchdogs (the network watchdog checks the local gateway, not the internet)
- single sign-on, when the provider (for example Authentik) runs on your network
Chromium runs with Google's background services turned off: no sync, metrics, Safe Browsing lookups, component updates, translation or search suggestions.
Views that point at internet sites need internet, of course.
Things to set up for an offline network
Clock. Without internet the Pi cannot reach the public NTP pool, and the Pi has no clock that survives power loss unless an RTC battery is fitted (the Pi 5 has a battery connector). A wrong clock breaks the daily sleep schedule and HTTPS certificate checks for your own sites. Either:
- point it at a local NTP server, over SSH: set
NTP=<your server>in/etc/systemd/timesyncd.confand runsudo systemctl restart systemd-timesyncd, or - fit a Pi 5 RTC battery, and set the time once.
Gateway. A network with no default gateway is fine: the network watchdog only acts when the kiosk has no address at all, or has a gateway that stops answering.
Updates. To update an offline kiosk, copy a release's pikiosk-arm64.tar.gz to it and run its install.sh (see Updating). OS packages need a local Debian mirror or a temporary internet connection.