As before don't be using "~" in this scenario or in your scripts, that path will only qualify when running as the pi user. Use the full paths.
Have you tried running it as root in a shell?
e.g.
or...
The above lines (those beginning with cd ...) are doing exactly the same as what your launcher shell script is doing, you don't need a script for that.
When executing a process in a non-interactive environment such as cron, rc.local, you cannot assume environment variables and paths are exported as in a user's interactive shell as no user profile is being sourced.
Still, did you try running from rc.local as the pi user as shown in my last post?
Have you tried running it as root in a shell?
e.g.
Code:
sudo -i
cd /home/pi/Adafruit_Python_SSD1306/raspberry-oled-monitor && ./monitor.pyor...
Code:
sudo -i
cd /home/pi/Adafruit_Python_SSD1306/raspberry-oled-monitor && /usr/bin/python ./monitor.pyThe above lines (those beginning with cd ...) are doing exactly the same as what your launcher shell script is doing, you don't need a script for that.
When executing a process in a non-interactive environment such as cron, rc.local, you cannot assume environment variables and paths are exported as in a user's interactive shell as no user profile is being sourced.
Still, did you try running from rc.local as the pi user as shown in my last post?
