Urban Sandén

Custom Screens and Dashboards on My Raspberry Pi Art Frame

A while back I built an art frame powered by a Raspberry Pi. It shows art and family pictures with feh, and I still like it a lot.

But a screen on the wall can show more than pictures. I wanted a clock. Then the weather. Then what’s playing right now. So the frame got a second job: it runs dashboards.

The dashboards

Overhead is the only one that needed more than a static file. It has its own little server.js, because adsb.lol sends no CORS headers and the page can’t fetch it directly. Routes come from adsbdb.com and are crowd-sourced, so treat them as best effort.

How it works

The idea is almost embarrassingly simple.

My Mac is the web server. The Pi is just a screen.

A dashboard is a single index.html with inline <style> and <script>. No build step, no framework, no bundler. I open it directly in a browser while I work on it, and when it looks right I push it to the wall.

Nothing is installed on the Pi. It opens a URL on my Mac and renders it full-screen. If I stop the server, the screen goes blank — the Pi holds no copy of the page.

The whole trick is one SSH command, launching Chromium in kiosk mode:

Shell
ssh pi@192.168.XX.XX "DISPLAY=:0 XAUTHORITY=/home/pi/.Xauthority setsid nohup \
  chromium-browser --kiosk http://$LOCAL_IP:$PORT \
  --noerrdialogs --disable-infobars --incognito \
  --disable-translate --disable-features=TranslateUI \
  --disable-session-crashed-bubble --no-first-run \
  --user-data-dir=/tmp/chrome-kiosk \
  --simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT' \
  --disable-component-update > /tmp/kiosk.log 2>&1 < /dev/null &"
What all those flags are for
  • --kiosk is the one that counts. Full screen, no address bar, no tabs, no window chrome.
  • --noerrdialogs and --disable-infobars keep dialogs and bars off the wall.
  • --incognito starts clean every launch. Good for dashboards, annoying for anything you log into — more on that below.
  • --disable-translate and --disable-features=TranslateUI stop the translate bar. One of my dashboards is in Swedish, and Chromium kept offering to fix it.
  • --disable-session-crashed-bubble and --no-first-run stop the “Chrome didn’t shut down correctly” bubble after a power cut.
  • --simulate-outdated-no-au and --disable-component-update kill the update nag. The Pi runs Chromium 92, the last build in the Raspbian buster repo. It is never getting an update, so it should stop asking.

Serving the page

There is no web server to configure. It’s just an npm script per dashboard, running http-server on its own port:

JSON
"start:clock": "http-server src/dashboards/clock -p 8083 -a 0.0.0.0",
"clock": "concurrently \"npm run start:clock\" \"./deploy.sh 8083\""

Switching dashboards by asking

Running a dashboard means knowing which npm script it is and which port it sits on. I never remember either. So the repo carries three Claude Code skills in .claude/skills/, and now I just say what I want:

Text
/dash overhead

That starts the server if the port isn’t already listening, kills Chromium on the Pi, runs deploy.sh, and waits up to 30 seconds for the Pi to request the page. The kill matters: a running kiosk ignores a new URL, so switching dashboards without closing the old one looks exactly like nothing happening. And the wait is for the Pi’s own request, not for the command to exit — the script can succeed while the wall stays blank.

/dash-status says what’s on the wall right now, which servers are up, and whether something else has taken a port. /dash-stop blanks the screen and leaves the servers running; /dash-stop all stops everything.

The part worth copying is how little is in them. A skill is a markdown file, and most of it is a description of when to use it:

YAML
---
name: dash
description: Show a dashboard on the Raspberry Pi. Starts its local server if
    it isn't running, closes whatever the Pi is showing, launches the new one
    in kiosk mode and confirms the Pi loaded it.
argument-hint: <dashboard> (e.g. overhead, gallery, tiles, ember, clock)
allowed-tools: Bash(./dash.sh:*)
---

The logic stays in dash.sh, where I can read it, run it by hand and debug it with no agent involved. The skill adds the one thing a shell script can’t carry: a sentence saying when it’s the right script to run. allowed-tools keeps that honest — this skill can run ./dash.sh and nothing else.

Designing for an older Raspberry Pi

Mine is a Pi 2, and there are really only two constraints worth planning around.

Everything is designed 9:16 first. Pages size to vmin and rem so I can work on them in a browser window on my Mac and trust them on the wall.

Chromium 92 is the baseline. CSS variables, clamp(), flex and grid gap, optional chaining and ?? all work. Container queries and :has() do not. Worth checking before you reach for something.

Did you enjoy this post?