Firstly: rpi-connect is absolutely brilliant! When on the road it's the best way to to check in on my Pi network with ease.
But (and there always is!): Sometimes I need to reboot my Pi's remotely from rpi-connect. I don't use auto-login, so I cannot connect to any of the desktop Pi's because a session has to be available. I don't like using auto-login for obvious security reasons.
I have followed this to enable auto-login with lock-screen after a few minutes: viewtopic.php?t=393135, but I would really like an option, if it's at all possible, for a desktop session to linger like a terminal session, and to auto-login after boot and go straight to the lock screen without timeout, but after an rpi-connect or physical login, to lock after 5 minutes of inactivity.
I'm not sure whether that's at all possible. It might need a change to swayidle to recognise the difference between reboot and real idle?
If anyone has any suggestions I would appreciate it.
But (and there always is!): Sometimes I need to reboot my Pi's remotely from rpi-connect. I don't use auto-login, so I cannot connect to any of the desktop Pi's because a session has to be available. I don't like using auto-login for obvious security reasons.
I have followed this to enable auto-login with lock-screen after a few minutes: viewtopic.php?t=393135, but I would really like an option, if it's at all possible, for a desktop session to linger like a terminal session, and to auto-login after boot and go straight to the lock screen without timeout, but after an rpi-connect or physical login, to lock after 5 minutes of inactivity.
I'm not sure whether that's at all possible. It might need a change to swayidle to recognise the difference between reboot and real idle?
If anyone has any suggestions I would appreciate it.
Statistics: Posted by Geeky_Tim — Wed Dec 10, 2025 10:15 pm