Don’t worry, apparently it’s only the “non-Pi” install that’s the pain in the ass. 
I’m still nowhere with it and I guess now the help desk is closed.
Thanks, @leukipp. This worked great for me on two different Pis (one 3B+ with an original touch screen and one 5 with a touch screen 2) both with fresh bookworm 64-bit installations.
I had tried autostarting Chromium or Firefox in fullscreen mode on the devices, but the touchscreen functionality using the browsers was pretty bad. I have been using the wallpanel extension as a screensaver on both devices, and the settings for wallpanel continue to work just fine with touchkio.
Nicely done!
1 Like
Don’t know if its a feature request for this project or its a configuration setting somewhere, but it seems each time the Raspberry Pi is restarted you have to log back into homeassistant again, is the kiosk browser cache lost each time and is there a way to retain it so you don’t have to login so frequently?
Ideally I wouldn’t restart the pi too much but while testing its a little annoying, fantastic project though it was so simple to install and setup! thanks for your efforts in developing this project!
@lukefourfour the cache is written to ~/.config/touchkio/Cache/ and should be retained through reboots. At least for me, I didn’t have to log in for a long time now and restarted almost 100x since I started using touchkio.
@thatzmatt just out of curiosity. What do you mean with “I guess now the help desk is closed.”? If you refer to the github issues, please keep in mind that this is a one man project and @leukipp (as most other open source devs) has limited time. Some people try to help out if possible but it’s still a hobby and no commercial product.
However, I’ll try to spin up a debian installation (or another lightweight x64 linux) later today to see if I can get it running. I’ll come back to you on that topic.
2 Likes
@thatzmatt Alright. So I now tested a Debian 12 installation with xfce, which did not work out of the box due to some missing dependencies in regards of KDE. Since I want to provide the most easy way to install a ready-to-go system that’s not based on a RPI, the easiest one I achieved (not tested all combinations) would be to install Debian with the KDE desktop environment. Make sure to not set a root password in the installer. After the installation, just use the autoinstaller of touchkio and you should be ready to go.
1 Like
Love this, thanks for creating it! Any chance for compatibility with GitHub - thomasloven/hass-browser_mod: 🔹 A Home Assistant integration to turn your browser into a controllable entity and media player for more customizations?
Thanks @pdsccode for your time testing different setups! 
Most of the browser_mod features should just work fine, at least it was reported here:
I too can confirm that browser_mod is working great for me. Running an HA dashboard with disabled sidebar and also incorporating the URL control via browser mod.
1 Like
Hi I was wondering if anyone found a decent touch screen that would turn on/off with presence please?
Are you referring to one that has a built in presence sensor? I am not aware of any. However, you can combine any presence detecting sensor in Home Assistant with the mqtt switch of touchkio to turn on/off the display. Or you can add a presence sensor to a pi that powers touchkio and read it’s sensor data via touchkio as described in the readme at leukipp/touchkio: Home Assistant Touch Panel Kiosk application for a Linux device (e.g. Raspberry Pi) with Touch Display.
I noticed that there are updates to some TouchKio files.
How can I update without damaging the settings?
Just re-run the installation script on RpiOS (Rpi5 8Gb)?
After the last RpiOS update, the unsightly circle mouse cursor disappeared and now everything is perfect, so I don’t want to ruin the installation by doing the wrong TouchKio update procedure.
Just follow the installation manual from the github repro. At the end you get the question to run the setup script. If you answer with a “N”, your settings are not changed.
Can anyone help? I’m having a big problem. I can’t connect to MQTT, and after rebooting, TouchKio won’t start. I don’t understand which IP address I should enter: for Home Assistant or for Raspberry Pi Kiosk. I have a Raspberry Pi 5 installed, and Raspberry Pi OS and Home Assistant are installed on other computers.
I’ve just installed this and it’s working great!
And I happen to have set it up to toggle the screen using my presence sensor in the kitchen I’ve installed it in.
Using the controls exposed when connected over MQTT, it was VERY easy to make an automation to light: turn on the kiosk display, when someone enters the room, and light: turn off when everyone leaves the room.
1 Like
Damn my display keeps waking randomly, no peripherals plugged in at all, and using a non touch monitor, so no idea why it wakes up when no one is in the room 
What type of presence sensor is it? A classic PIR? I had very bad experience with this type over the years in general. Constant false detections.
If it’s a PIR sensor, maybe you can try to use an mmWave or tie it so some other event that happens everytime you want the display to turn on (e. g. if you always turn on the smart light when you enter the room).
Just to understand your architecture. You have touchkio installed on a Pi5 and HA is installed on a different device, right? If so, then the IP address you need to enter is the one of the HA instance.
When it comes to touchkio not starting, what does a “systemctl --user status touchkio.service” report when ran on the Pi you have touchkio installed?
Hello all,
Just wanted to let you guys know this works great, many thanks for the time and effort it took you to create the project!
Initially I received the ‘Oops’ errors and i am also experiencing the screen that will not turn off, but both of those issues have already been logged.
2 Likes
Very cool - worked like a charm - thank you!
1 Like
touchkio recently got featured in a YouTube video btw:
2 Likes