rPi Kiosk Mode + Airplay w/ piBeacon
Posted: Mon Feb 15, 2021 1:22 pm
My current rPi deployment is raspian light that boots directly into a no curser chromium which loads directly into an indigo control page. Simultaneously, sharpoint-sync (airplay) is loaded. This is attached to HDMI 1 on 4 TVs throughout the house.
SIDENOTE: I'm experimenting with other browsers besides chromium to find one that is more command line friendly so I could automated changing a URL.
Experiment 1: I’ve got a project rPi running piBeacon. I've tried following the steps (see bottom of post) to add kiosk mode to the rPi without much success.
Experiment 2: On my Kiosk rPi, I've installed piBeacon, but it too isn't working well. The plugin will see it, but that's about it. It's not recognizing tags, etc.
My best guess (from a non-programmer POV) it's a start-up thing. I think both (chromium + piBeacon) are trying to use the startx thing but they look at different startup files I think.
On my Kiosk rPi, the startup file is edited by
This is Experiment 2, currently displaying an indigo control page, streaming audio from iTunes on indigo machine and piBeacon is running in the background, but not beaconing:
Ideally, I will be able to get a rPi 3B+ to run in kiosk mode in the foreground with airplay and piBeacon stuff running in the background. These are the build steps I followed for the Kiosk Mode and AirPlay if anyone else wants to follow along and give it a shot.
Airplay: https://appcodelabs.com/7-easy-steps-to-apple-airplay-on-raspberry-pi
Raspberry [url]Kiosk: https://die-antwort.eu/techblog/2017-12 ... iosk-mode/[/url]
SIDENOTE: I'm experimenting with other browsers besides chromium to find one that is more command line friendly so I could automated changing a URL.
Experiment 1: I’ve got a project rPi running piBeacon. I've tried following the steps (see bottom of post) to add kiosk mode to the rPi without much success.
Experiment 2: On my Kiosk rPi, I've installed piBeacon, but it too isn't working well. The plugin will see it, but that's about it. It's not recognizing tags, etc.
My best guess (from a non-programmer POV) it's a start-up thing. I think both (chromium + piBeacon) are trying to use the startx thing but they look at different startup files I think.
On my Kiosk rPi, the startup file is edited by
- Code: Select all
sudo nano /etc/xdg/openbox/autostart
This is Experiment 2, currently displaying an indigo control page, streaming audio from iTunes on indigo machine and piBeacon is running in the background, but not beaconing:
Ideally, I will be able to get a rPi 3B+ to run in kiosk mode in the foreground with airplay and piBeacon stuff running in the background. These are the build steps I followed for the Kiosk Mode and AirPlay if anyone else wants to follow along and give it a shot.
Airplay: https://appcodelabs.com/7-easy-steps-to-apple-airplay-on-raspberry-pi
Raspberry [url]Kiosk: https://die-antwort.eu/techblog/2017-12 ... iosk-mode/[/url]