Nice project, you helped me alot with this one, although I went for a more manual approach on changing screens using GPIO and a touch sensor and a switch for turning off the display once I'm done and away from desk. I use this for clock, calendar and HomeAssistant dashboard.
Nice demo, Firefox also has kiosk mode and can be configured to run on a chosen display in a 2 display system if os is running X11. (untested) raspi os can be configured to run X11, it is in the raspi-config (terminal version) Advanced options = A6 Wayland (gives choice Wayland or X11) 2024-08-05 seems xdotool also exists, works on my rpi5 X11. (xdotool keyboard uses qwerty layout)
can someone help me, the wayfire folder has another folder that says default.ini. thats where you put the autostart comand, but its read only. does anyone have any solutions
During testing I managed to get this to work with Firefox as well! You can change the line where we open chromium to instead open firefox. The start up options are different and a quick google search can find them. But the rest of the guide should be nearly the same, but some parts may need a little modification here and there.
There is no option to launch another. It should be Firefox, but its too buged in kiosk mode. btw chromium not perfect too - this version cant work with all kind of cameras.
Just get it to open the address! There are a lot of ways to host a webpage, and we have a guide on how to host one on a microcontroller if you are interested. This is mainly for controlling hardware plugged into the microcontroller, but it might be a good starting point! czcams.com/video/hLLUxuFxLOI/video.html
We attached the active cooler to the pi and had no issues! The case is aluminium and isn't completely airtight + looking at a webpage isn't too intensive of a task. As long as you have a Pi with at least a passive cooler on there, you shouldn't have too much of an issue.
Use DietPi instead of Raspbian. No bloat, just what you need and starting into kiosk mode is literally a checkbox in the config manager... Runs smoothly on the older models too.
We went with Raspbian as it allows people to follow other guides they may also want to run on their Pi at the same time. But if I were to get an old Pi 3B or 2 out of the cupboard and run it in kiosk, DietPi would be the way to go!
KIOSK mode means that the user will never see either the desktop or the panel. As u can see - desktop and panel was loading before browser opens. I wrote about this mistake everywhere (official forums too). The problem is - [core] module in wayfire.ini file is not declared. Thats some explanation: # this option turns on [autostart] plugin [core] plugins = \ autostart # When plugin is declared - this part of configuration should working [autostart] # next parameter disables wallpaper, start a panel and dock autostart_wf_shell = false # turn off screensaver screensaver = false # turn off Display Power Management Signaling dpms = false # starts chromium with specific page in KIOSK mode, without error dialogs, without panels and bars, without welcome message, using Ozone platform abstraction layer chromium = chromium-browser google.com --kiosk --noerrdialogs --disable-infobars --no-first-run --ozone-platform=wayland > U can check it on my GitHub page: githubadress/nozloy/rpi-wayland-wayfire-kiosk
You could use ydotool to simulate scroll wheel movements, or your could use wtype to press the arrow keys. Something like: wtype -P Down sleep 1 wtype -p Down The capital -P means press the key, then sleep for how ever long you need, then the lower case -p means to release it.
If you open the shell script and you don't get the options to execute, open, etc... then you haven't made it an executable properly. Try running "sudo chmod +x run_kiosk.sh" again. If it does open that little option window, then double check your code. If you are still having issue with it, feel free to post on our dedicated forum topic for this video, we have a lot of maker eyes over there that can help just give us some info of the problem. Cheers! forum.core-electronics.com.au/t/how-to-set-up-a-raspberry-pi-kiosk-launch-a-fullscreen-webpage-on-boot/20578
Just to mention --- the Pi Imager has an OS called "Full Page OS" that already does much of the same thing.
Your guide is cooler than their setup tho
Thank you for this! i wanted to do a project like this for so long!
Nice
Thank your Mr Bossman
Great information. Just the thing I wanted for the Pi5 LCD I ordered yesterday. 🤩
We're a little bit psychic like that sometimes 😎
Nice project, you helped me alot with this one, although I went for a more manual approach on changing screens using GPIO and a touch sensor and a switch for turning off the display once I'm done and away from desk. I use this for clock, calendar and HomeAssistant dashboard.
Very nice touch with the inputs 👌
Not sure about chromium but chrome has plugin to rotate between tabs, really handy we used it as a screen for Jenkins / jira etc
What are you using to create the full page dashboard? I’m currently using DAKBoard but would love to move to something with no cost.
Nice demo, Firefox also has kiosk mode and can be configured to run on a chosen display in a 2 display system if os is running X11. (untested)
raspi os can be configured to run X11, it is in the raspi-config (terminal version) Advanced options = A6 Wayland (gives choice Wayland or X11) 2024-08-05
seems xdotool also exists, works on my rpi5 X11. (xdotool keyboard uses qwerty layout)
"unclutter" command seems to hide the mouse
unclutter is brilliant, we have it in our x11 guide as well, such a shame it doesn't work on Wayland yet. 😔
Bro, this is killer! The idea cauldron is bubbling! Thank you! Liked and subbed my guy!
Idea cauldron, never heard it put that way but it really gets the idea across, happy making!
can someone help me, the wayfire folder has another folder that says default.ini. thats where you put the autostart comand, but its read only. does anyone have any solutions
Can I use another browser instead of Chrome?
During testing I managed to get this to work with Firefox as well! You can change the line where we open chromium to instead open firefox. The start up options are different and a quick google search can find them. But the rest of the guide should be nearly the same, but some parts may need a little modification here and there.
@@Core-ElectronicsThanks
There is no option to launch another. It should be Firefox, but its too buged in kiosk mode.
btw chromium not perfect too - this version cant work with all kind of cameras.
How to show a local webpage you are hosting?
Just get it to open the address! There are a lot of ways to host a webpage, and we have a guide on how to host one on a microcontroller if you are interested. This is mainly for controlling hardware plugged into the microcontroller, but it might be a good starting point!
czcams.com/video/hLLUxuFxLOI/video.html
no fan in your case. How long can your raspi work ?
We attached the active cooler to the pi and had no issues! The case is aluminium and isn't completely airtight + looking at a webpage isn't too intensive of a task. As long as you have a Pi with at least a passive cooler on there, you shouldn't have too much of an issue.
Use DietPi instead of Raspbian.
No bloat, just what you need and starting into kiosk mode is literally a checkbox in the config manager...
Runs smoothly on the older models too.
We went with Raspbian as it allows people to follow other guides they may also want to run on their Pi at the same time. But if I were to get an old Pi 3B or 2 out of the cupboard and run it in kiosk, DietPi would be the way to go!
KIOSK mode means that the user will never see either the desktop or the panel.
As u can see - desktop and panel was loading before browser opens. I wrote about this mistake everywhere (official forums too).
The problem is - [core] module in wayfire.ini file is not declared. Thats some explanation:
# this option turns on [autostart] plugin
[core]
plugins = \
autostart
# When plugin is declared - this part of configuration should working
[autostart]
# next parameter disables wallpaper, start a panel and dock
autostart_wf_shell = false
# turn off screensaver
screensaver = false
# turn off Display Power Management Signaling
dpms = false
# starts chromium with specific page in KIOSK mode, without error dialogs, without panels and bars, without welcome message, using Ozone platform abstraction layer
chromium = chromium-browser google.com --kiosk --noerrdialogs --disable-infobars --no-first-run --ozone-platform=wayland >
U can check it on my GitHub page: githubadress/nozloy/rpi-wayland-wayfire-kiosk
and the keyboard?
9:13 how do you get it to do a auto scroll down on pages?
You could use ydotool to simulate scroll wheel movements, or your could use wtype to press the arrow keys. Something like:
wtype -P Down
sleep 1
wtype -p Down
The capital -P means press the key, then sleep for how ever long you need, then the lower case -p means to release it.
@@Core-Electronics thanks
double clicking the script file does nothing for me....doesn't fire up browser
If you open the shell script and you don't get the options to execute, open, etc... then you haven't made it an executable properly. Try running "sudo chmod +x run_kiosk.sh" again. If it does open that little option window, then double check your code.
If you are still having issue with it, feel free to post on our dedicated forum topic for this video, we have a lot of maker eyes over there that can help just give us some info of the problem. Cheers!
forum.core-electronics.com.au/t/how-to-set-up-a-raspberry-pi-kiosk-launch-a-fullscreen-webpage-on-boot/20578
It is like android
Not really 😂 it’s more Linux 😅