Oh my word
OK looking at your dump of your /etc/rc.local file you misunderstood my last post.
So assuming your thing worked when running in a shell and as root...
e.g. as pi, switch to the root user...
... then run your script
If that works as root then the monitor works as the root user in a shell.
One would do the same in the rc.local file by just adding to the file before the 'exit 0' line...
That will be executed at boot time. So do that and get rid of the other commented out ones...
Now above those, what's this line?
... and why doesn't it have a '&' on the end? Is that a persistent process? If so nothing after it will run.
FYI you can see what processes are still running from rc.local by running..

OK looking at your dump of your /etc/rc.local file you misunderstood my last post.
So assuming your thing worked when running in a shell and as root...
e.g. as pi, switch to the root user...
Code:
sudo -i
... then run your script
Code:
cd /home/pi/Adafruit_Python_SSD1306/raspberry-oled-monitor && /usr/bin/python ./monitor.py
If that works as root then the monitor works as the root user in a shell.
One would do the same in the rc.local file by just adding to the file before the 'exit 0' line...
Code:
cd /home/pi/Adafruit_Python_SSD1306/raspberry-oled-monitor && /usr/bin/python ./monitor.py &
That will be executed at boot time. So do that and get rid of the other commented out ones...
Now above those, what's this line?
Code:
/home/pi/Flirc-moode.py
... and why doesn't it have a '&' on the end? Is that a persistent process? If so nothing after it will run.
FYI you can see what processes are still running from rc.local by running..
Code:
sudo systemctl status rc-local