What it does
The screen shows the view you pick for it in the Fluxplan admin, and keeps running without anyone touching it.
What you need
- A Raspberry Pi 4 or 5 with 1 GB of memory or more
- Its official power supply: an underpowered Pi restarts at random
- A microSD card of 8 GB or more; the system takes about 4 GB
- A screen with HDMI, such as a TV or monitor, and a micro-HDMI cable for the Pi
- A network: Wi-Fi or a network cable
- A Fluxplan instance (such as demo.fluxplan.nl) where you are an admin
SignageOS is built on Raspberry Pi OS Lite (64-bit): no desktop, only the browser that shows your Fluxplan. That is why it runs well on the smallest Pi 4.
Downloads
There are two kinds of release. You only ever download the image: screens that are running fetch the player by themselves.
Raspberry Pi OS with the player, ready to write to a card.
Download image The newest image, with a SHA-256 checksumRunning screens update to it at night, or right away with Update player in the admin.
What’s new The newest player, as a.deb
Raspberry Pi Imager can list the image too: rpi-imager --repo https://enjoytheshow-nl.github.io/fluxplan-signageos-releases/imager.json
Installing a screen
About ten minutes, most of it writing the card.
- Write the image to a card Use Raspberry Pi Imager, on Windows, macOS or Linux: Choose OS → Use custom, and pick the image. Leave its OS customisation off: the screen sets itself up. Get Raspberry Pi Imager
- Start the Pi Put the card in the Pi, connect the screen and a network cable if you use one, and then the power.
- Set it up with your phone Join the Wi-Fi network on the screen, SignageOS-XXXX, with the 8-digit password, or scan the QR code. Choose Wi-Fi or cable, enter your Fluxplan address and country, and save.
- Pair it in Fluxplan The screen shows a pairing code. In the admin, go to Operations › Narrowcasting › SignageOS screens, choose Pair screen, enter the code and choose what the screen shows.
On the setup network, the setup page usually opens by itself. If it doesn’t, open http://10.42.0.1 in your phone’s browser. If something goes wrong while connecting, the screen and the phone say which step failed, and the setup network comes back so you can try again.
Setting up in advance: fluxplan.json
Preparing several screens, or installing one where nobody can use a phone? Put the Fluxplan address and network on the card beforehand, and the screen skips the setup step. It goes straight to its pairing code.
{
"server": "demo.fluxplan.nl",
"country": "NL",
"wifi": {
"ssid": "Office",
"password": "secret-password",
"hidden": false
}
}
- Write the image to the card, then take the card out and put it back in your computer.
- Open the drive called bootfs. It holds many files, such as
config.txt,cmdline.txtandFLUXPLAN-README.txt. - Put
fluxplan.jsonin it, next to those files, not in a folder. Eject the card, and put it in the Pi.
What goes in the file
| Key | Needed | What it is |
|---|---|---|
server | Yes | Your Fluxplan address, such as demo.fluxplan.nl. A full address with https:// works too. |
country | Advised | Two-letter country code, such as NL, BE or DE. Decides which Wi-Fi channels the screen may use. Without it, the screen uses NL. |
wifi | For Wi-Fi | The Wi-Fi network. Leave it out completely when the screen uses a network cable. |
wifi.ssid | With wifi | The network’s name, exactly as it shows on a phone, capitals included. |
wifi.password | With wifi | The network’s password, 8 to 63 characters. Empty, or left out, for an open network. |
wifi.hidden | No | true for a network that does not show in lists. false when left out. |
What the screen does with it
- On its next start, it reads the file and deletes it right away, because it holds your Wi-Fi password. A file it cannot read is deleted too.
- It sets the country, saves the Fluxplan address and the Wi-Fi network, and connects.
- The screen shows a pairing code. Pair it in the admin as usual.
- If the network cannot be reached for five minutes, the setup network opens after all, so you can fix it with your phone.
If it does not work
- Windows hides extensions. A file saved as
fluxplan.jsonin Notepad can end up asfluxplan.json.txt. Use the download button above, or choose “All files” when saving. - Straight quotes only. Word and TextEdit turn
"into curly quotes, which break the file. In TextEdit, choose Format → Make Plain Text first. - Commas between items, none after the last. Every text goes between double quotes.
- Still the setup screen? Then the file was missing or could not be read. Put an empty
fluxplan-debugfile on the card to see why (below).
Other files on the card
The card’s bootfs drive also takes two instructions. Make an empty file with the name below (.txt at the end is fine too), put the card back, and start the Pi.
fluxplan-reset
Factory reset
The screen forgets its pairing, its Fluxplan address and its Wi-Fi network, deletes the file, and opens setup again. For a screen that is offline; otherwise use Factory reset in the admin.
fluxplan-debug
Troubleshooting report
While it is there, the screen writes fluxplan-debug.log next to it every 30 seconds: what it did, its network and the system logs since it started. No passwords. Unplug the Pi, read the file on your computer, and delete fluxplan-debug when you are done.
Messages on the screen
When something is wrong, the screen says so in plain words, in Dutch and English, with a short code bottom left. Most of them sort themselves out: the screen keeps trying.
| Code | The screen says | What to do |
|---|---|---|
NET-01 | Er is nog geen internet · There is no internet connection yet | Nothing, at first. If it lasts: check the cable or the Wi-Fi, or unplug the screen for a moment. |
NET-02 | Fluxplan reageert niet · Fluxplan is not responding | If it lasts, check whether your Fluxplan opens in a browser. |
DNS-01 | Dit Fluxplan-adres bestaat niet · This Fluxplan address does not exist | The address has a typo. Reset the screen and set it up again. |
API-429 | Even geduld · Just a moment | Nothing: Fluxplan asked the screen to wait, and it carries on by itself. |
API-5XX | Fluxplan is even niet beschikbaar · Fluxplan is briefly unavailable | If it lasts, contact whoever manages your Fluxplan. |
TLS-01 | De klok van het scherm wordt gelijkgezet · Setting the screen’s clock | Nothing: the Pi has no clock battery and sets its clock over the internet first. |
TLS-02 | De beveiligde verbinding lukt niet · The secure connection fails | A filter or proxy on the network blocks Fluxplan. Ask for it to be allowed. |
SET-01 | Verbonden, maar Fluxplan niet gevonden · Connected, but Fluxplan was not found | Check the Fluxplan address on the setup page. |
WIFI-01 | Het wachtwoord klopt niet · The password is not right | Enter the Wi-Fi password again, minding the capitals. |
NET-03 | Er is geen netwerkkabel aangesloten · No network cable is connected | Plug in the cable, or choose Wi-Fi. |
Updates and the night
Screens keep themselves up to date, at times when nobody looks.
- 03:00
- Debian, Raspberry Pi and player updates are installed.
- 03:30
- The browser restarts, for a fresh start each day.
- 04:00
- The Pi restarts, only when an update needs it.
- Sun 04:30
- A weekly restart.
A new screen installs the newest player as soon as it reaches Fluxplan.
From the admin
Under Operations › Narrowcasting › SignageOS screens, each screen has a Player menu:
- Update player: install the newest version now instead of tonight.
- Reload: start the browser afresh.
- Restart: restart the Pi.
- Shut down: turn the Pi off, for example before you move it. Unplug and replug the power to start it again.
- Factory reset: forget the Fluxplan, the pairing and the Wi-Fi, and go back to setup.
Security
apt/. Key fluxplan-signageos-archive-keyring.asc, fingerprint C57F 858F A9B2 7EE9 8EA3 13EF 5A39 CD8F 9F30 CF35.