Our new project, named infopi, aims to replace proprietary and expensive info screen solutions. Everything needed in order to get started is a Raspberry Pi.
Receiving several demands and requests for an open source alternative to pricy and proprietary information screens, we have decided to polish and publish our current info screen setup used at Semaphor.
Info screens are often located in receptions, foyers or meeting rooms. Occasionally larger facilities and workplaces even include them in hallways and bathrooms. At Semaphor, we have an info screen running in the background with statistical information such as hours worked, current jobs and an overview of warnings from our server room; should there be any. The setup is simple and hosted on a Raspberry Pi 3. The management of the Raspberry Pi is done through Ansible and allows us to update multiple of them with only one command. We actually never have to leave our desks once the Pi is configured and plugged into a screen. With the Pi powered with PoE (Power over Ethernet) and a small cable leading to the HDMI port of the screen, the cabling is neat and tidy and only exposes the information to the cabled internal network.
Why a Raspberry Pi?The Raspberry Pi is a compact and full functioning computer running on an ARM processor. The Raspberry Pi 4 has dual 4K monitor support and comes at just $35 for the cheapest model.
The Raspberry Pi' is also dead silent as the ARM processor and motherboard requires no fans to run. This means that it can be packed up and hidden away behind a monitor or TV. The "harddisk" of the Pi consists of a micro SD and can easily be removed and reformatted. If additional storage is required, an external drive could be mounted to one of the several USB ports. And if you decide to scrap the project of which you bought the Raspbery Pi for, just reuse it for something else. So why not use one?
The ProjectThe repository, infopi, can be found on our Github page and doesn't require anything but a Raspberry Pi to get started. The setup process may seem a bit tedious and could do with some more automation in the early phase of preparing each new Pi. But when managing just a few info screens like we do at Semaphor, I'd say it's endurable. It's our intention to further automate the proces at some point, we just need the spare time :-) If anyone else wants to fork and refine the project, feel free. It's released under the GPL-3 license.
Ideally, a dedicated info screen-image existed, flash-ready and accompanied by an install script, defining variables to suit the users infrastructure. But for now, the info screen Pi works impeccably at cycling through tabs in a Chromium browser. And apart from the vintage TV and a bit of dust, the solution, along with some Grafana-magic, is quite OK.
The repository includes a readme document to get you started managing your own info screens.
To get and try out the project for yourself, clone it with the following command or browse the files on Semaphor's Github page.
git clone https://github.com/semaphor-dk/infopi.git
The real beauty of using Ansible to manage the info screens comes with the option of creating seperate groups and still updating/configuring them with one command. Say for example a facility has six info screens in total. Two are located in the reception, two in the hallways and two in the cafeteria. The screens would then be managed by including them in the
hostsfile, usually referred to as the inventory. In the
hostsfile, each of the Pi's can be included under specific groups, declared in brackets. Remember, both domains and ip adresses can be used in the inventory file.
Given the example above, the
hostsfile could look something like this:
[reception] info-0.local info-1.local [hallway] info-2.local info-3.local [cafeteria] 192.168.1.10 192.168.1.11
With the Pi's defined in the
hostsfile, url's to browse can be set for each group by creating a
group_varsdirectory. By default, the project comes with an
all.ymlfile, which automatically applies to all Pi's included in the
If, for example, the Pi's were to display weekly menus on the ones located in the cafeteria, and the meeting scedule on the Pi's in the hallway, a file named
hallway.ymlcould be placed in the
group_varsdirectory with the following contents (with made up url's).
--- infopi_urls: - "hxxps://company.local/cafeteria/menu?vegan=true" - "hxxps://company.local/cafeteria/menu?vegan=false"
--- infopi_urls: - "hxxps://company.local/schedule/meetings?room=011" - "hxxps://company.local/schedule/meetings?room=012" - "hxxps://company.local/schedule/meetings?room=013"
To update and reboot the cafeteria Pi's with the new settings, simply run the following command from the root directory of the project:
ansible-playbook cafeteria infopi.yml
Or only the hallway Pi's:
ansible-playbook hallway infopi.yml
Or roll out changes to all Pi's with: