(2021-08-09, 09:43)ExTechOp Wrote: So now the Raspberry PI Kodi distribution OSMC switched to Kodi 19 Matrix, and the aged "Pimon" screen saver is no longer available.
The "Turn Off" screensaver seems to be the choice for a replacement. Testing it very quickly this morning, the screen goes correctly into power saving, but unfortunately it doesn't seem to come back. The remote control seems to go to never-never-land, even if I intentionally set incorrect power saving options and the screen stays on. Anyone have good ideas what could be causing this, before I have more time to mess around with it?
I was attempting to use DPMS (built-in) and a I above said, I suspect it's also shutting down everything on Raspberry Pi 2 that is USB-powered, including the keyboard and ethernet, since the device disappeared off my network when the screen saver activated.
However, following the hints above I found out that from a ssh shell,
/opt/vc/bin/vcgencmd display_power 0 does switch the display off, and parameter 1 restores it. So the issues using vcgencmd seem to only be related the path.
Editing the file .kodi/addons/screensaver.turnoff/screensaver.py I changed the vcgencmd to include the full path I've given above, so in this file you have the following:
Code:
22 dict(name='no-signal-rpi', title='No Signal on Raspberry Pi (using vcgencmd)',
23 function='run_command',
24 args_off=['/opt/vc/bin/vcgencmd', 'display_power', '0'],
25 args_on=['/opt/vc/bin/vcgencmd', 'display_power', '1']),
This makes the screen saver behave just fine. I'm a bit mystified, was vcgencmd somewhere else along $PATH at some point or what is going on here, how did it ever work without the complete path?