01-17-2023, 11:51 PM
"3) Which source files/database entries might I add/modify to give support for 12 buttons via GPIO, instead of 8? I'd prefer to able to setup the additional GPIO lines via the same gui as the first 8, but if this is too much work, I'm willing to do it via script/cli."
Regarding the screen going blank after login prompt briefly appears, IIRC this has to do with a config on the Lite version of RaspiOS that changes the getty target -- because it's meant to be headless and accessed only via SSH -- Something like that.
As far as getting your screen configured with its driver etc before moOde worker.php starts LocalUI (xinitrc) I would think that loading the driver from rc.local before the line that starts worker.php should work but I don't know what that driver does or wants so YMMV.
moOde startup sequence is as follows:
Code:
/var/www/daemon/gpio_buttons.py
/var/www/templates/gpio-config.html
/var/www/gpio-config.php
cfg_gpio SQL table (moodeutl -q "select * from cfg_gpio")Regarding the screen going blank after login prompt briefly appears, IIRC this has to do with a config on the Lite version of RaspiOS that changes the getty target -- because it's meant to be headless and accessed only via SSH -- Something like that.
As far as getting your screen configured with its driver etc before moOde worker.php starts LocalUI (xinitrc) I would think that loading the driver from rc.local before the line that starts worker.php should work but I don't know what that driver does or wants so YMMV.
moOde startup sequence is as follows:
Code:
Linux boot -> rc.local -> /var/www/daemon/worker.php -> systemctl start local -> /usr/bin/xinit