
Once support and funding ended, an information kiosk was due to be retired. I took it on as my own project, mostly after hours, and rewrote all of its software from scratch: the app, the firmware for the Braille buttons, a Polish voice that runs locally and a sensor that greets people as they approach.
Technologies
- Astro
- Tailwind v4
- DaisyUI v5
- Directus
- Debian + cage + Chromium
- Python
- Piper TTS
- Arduino (ATmega32U4)
- Docker
This kiosk was about to be retired. It had stood in a lobby for years, but when support and funding for its commercial system ended, it stopped working. It would most likely have ended up somewhere in the depths of a storeroom.
I took it on as my own project. I did the diagnosis, the new software, the firmware for the button board, the Polish voice and the rollout myself, mostly after hours. Today the kiosk works again, and it is designed first and foremost for people with disabilities.
(enlarge)The starting point: a kiosk on its way to storage
The kiosk is a SAROS stand with a portrait touch screen, five buttons labelled in Braille and a presence sensor. Inside was a small computer running Android 7 from 2017 and an app from a commercial digital signage platform.
All of the software lived in the vendor’s cloud:
- content and configuration were not stored on the device but downloaded from a server,
- support for this installation had expired, so the kiosk only showed a waiting screen,
- leaving the app was blocked by a separate lock with a PIN nobody knew,
- the system had not received security updates for years.
In that state the kiosk had nothing left to show, so it was going to leave the lobby. Yet the cabinet, the screen and the buttons were in excellent condition. I thought it would be a waste to put them in storage when all it needed was new insides and new software.
(enlarge)Debugging step by step
I started by checking whether anything could be salvaged. A factory reset from the Android recovery menu removed the PIN lock and the old app. It turned out this unit had no USB debugging port, and putting Linux on its ARM processor risked ending up with no picture and no touch.
So I replaced only the computer. The cabinet now houses a small, quiet x86 machine running Linux. The rest of the hardware stayed as it was.
The button board
The buttons and the sensor are handled by a separate board with an ATmega32U4 microcontroller, the same chip as in the Arduino Leonardo. The original program was gone. All that was left was a test sketch that assumed the wrong pins and reported a distance of 0 cm.
- I wrote a diagnostic sketch to work out which pin belongs to which button,
- then new firmware with a simple text protocol: button presses and the distance of a person from the kiosk,
- firmware updates no longer require opening the cabinet.
(enlarge)A rotated screen and touch
The monitor sits upright in the cabinet, so the picture has to be rotated by 90 degrees. Touch does not rotate with it, so I built a five-point calibration page, calculated a calibration matrix from the measurements and set it in the system. Touch is now accurate to about a centimetre, which is plenty for large buttons.
(enlarge)The missing piece in the lobby
The lobby already has two information screens with a room directory, news and a map of the buildings. A screen shows everyone the same thing. What was missing was a place to ask your own question: where do I hand in my documents, where is the cash desk, what do I need to bring.
The kiosk completed the set:
- the room directory shows which department is in which building and on which floor,
- the slideshow screen shows news, events, the weather and a map of the buildings,
- a bus stop display shows the next departures,
- the kiosk answers a specific question and points you to the right room.
They all use the same data, the same typefaces and the same colour palette. Visitors see the same room number on the kiosk as on the screens and on the website. I wrote about the screens in Information screens in the lobby and A bus stop display with live departures.
What the kiosk can do
The start screen asks “How can we help?” and offers four routes:
- a service search with an on-screen keyboard that understands input without Polish diacritics (“slub” finds “ślub”, marriage),
- services grouped into categories,
- departments and offices with their location, phone number and opening hours,
- key places such as the cash desk or the point where letters are handed in.
(enlarge)A service card answers the questions people usually ask at the front desk:
- where: building, floor and room number, highlighted at the very top,
- how much it costs and how long it takes,
- which documents to bring,
- a “Take this information with you” QR code opens the service description with forms on your phone.
From a department card you can go to every service handled in the same place.
(enlarge)
(enlarge)Accessibility first
From the start I assumed the kiosk had to work for a blind person, someone with low vision, a wheelchair user and an older person who dislikes touch screens. That is why the kiosk can be used entirely without touching the screen.
Five buttons and a voice
- Next and Previous move between items, Select opens, Back goes back and Home returns to the start,
- the first press of any button turns on speech automatically, because people who reach for the buttons usually need the voice,
- the kiosk reads every selected item and the whole service card, including the room and the list of documents,
- volume has three levels and always starts at the quietest.
A Polish voice without the cloud
The browser on Linux has no decent Polish voice, and sending text to an external service was out of the question. Speech is synthesised by Piper, an engine running locally on the kiosk itself. Utterances are cached, so frequently read sentences play instantly.
Piper struggles with digits, so numbers are turned into words before synthesis. Phone numbers are read digit by digit, “II piętro” becomes “second floor” and amounts get the correct Polish grammatical forms of “złoty”.
The kiosk knows someone is there
An ultrasonic sensor measures the distance from the kiosk. When someone comes closer than about 1.2 m, the kiosk greets them by voice and mentions that the buttons are to the left of the screen. The greeting plays at most once a minute and never interrupts someone already using the kiosk.
Legibility and a clean slate after each visit
- the Larger text and Contrast buttons enlarge the text and switch on high contrast mode,
- the Atkinson Hyperlegible Next typeface was designed with low vision readers in mind,
- the accessibility switches are at the bottom of the screen, within reach of a wheelchair user,
- after 90 seconds of inactivity the kiosk returns to the start and turns off speech, contrast and enlargement, so the next person starts fresh.
(enlarge)The most important test was not a technical one. The kiosk has to guide someone who cannot see the screen from the entrance to the right room.
Aleksander Kowal
Data from the intranet and the portal CMS
The kiosk has no content database of its own, and nobody has to maintain it separately. Services, departments and places come from the same CMS that powers the website. Room locations came from the intranet.
- a member of staff edits a service description in the portal admin, and the change reaches the kiosk within fifteen minutes,
- the kiosk shows public information only: the service, department, room and general phone number, with no staff details,
- the kiosk keeps the last good copy of the data, so a CMS outage does not take it down,
- the screen never refreshes content while someone is using it, only when it is idle on the start page.
Runs unattended
The kiosk stands in the lobby with nobody looking after it, so it has to take care of itself and report problems before a visitor notices them.
- the system boots straight into the app, showing a logo instead of boot messages,
- the browser runs in kiosk mode, with no desktop and no way out of the app,
- a hardware watchdog restarts the computer if the system stops responding,
- monitoring checks that the kiosk is working properly and reports failures,
- communication with internal systems is encrypted and permissions are kept to the bare minimum.
Statistics without cookies
The kiosk collects anonymous statistics, with no cookies and no personal data. They show which services people look for most, how often they use the buttons and the voice, and how many people walk up to the kiosk. That tells us which service descriptions to improve first.
An after-hours project
I did most of the work on the kiosk after hours. The most time went into things you cannot see on the screen: diagnosing the old system, the button board, touch calibration and a Polish voice that reads numbers correctly.
The result: instead of putting working hardware into storage, there is a kiosk that does more than it ever did and does not depend on an outside vendor.
What’s next
The next step is a floor plan with the route to the room marked on it. Further ahead, the kiosk could answer spoken questions, with an assistant using the same data as the portal.
Stack
- Astro (SSR on Node), Tailwind v4, DaisyUI v5, Lucide, self-hosted fonts,
- the website’s Directus as the source of services, departments and places,
- Debian, cage and Chromium in kiosk mode, Plymouth, systemd with a watchdog,
- Python: a kiosk service linking the board, the sensor and speech over WebSocket,
- Piper TTS with a Polish voice, running locally,
- ATmega32U4 with custom Arduino firmware,
- Docker.
Was this useful?
New posts by e-mail
Every now and then, when a new post or project goes up. No ads.
Got an idea, a question or a comment? Write to me:Enable JavaScript to see the e-mail address




Comments
No comments yet. Be the first.