Hello!
I noticed in the RPIConnect documentation under known problems (https://www.raspberrypi.com/documentati ... own-issues) that it writes:
Thank you so much! Any insight would be appreciated.
I noticed in the RPIConnect documentation under known problems (https://www.raspberrypi.com/documentati ... own-issues) that it writes:
I have two follow-ups related to this:Upgrading rpi-connect and rpi-connect-lite using Connect’s remote shell is not supported. The upgrade process will terminate all remote shell sessions and drop all connections. To upgrade Connect in a remote shell session, use a tool like screen or tmux to ensure the process continues uninterrupted after your connection is closed.
- I'm hoping to remotely update a raspberry pi out in the field using Raspberry Pi Connect (meaning run: and then
Code:
sudo apt updateWould this similarly be a potential problem? Assuming that the raspberry pi is known that it will stay on, are there any risks with trying to do this remotely to be aware of? If it then tries to update raspberry pi connect during that process, this will mess up the update, right? Are there any good alternatives to setting up remote system updates like this?Code:
sudo apt full-upgrade
- I'm also hoping to remotely upgrade Raspberry Pi Connect versions. All my past pis are running older versions of RPi Connect. Has anyone updated Raspberry Pi Connect using tmux? Have you found consistent success? I've never used it before and will do more research on it, but if anyone has any good resources/advice about using it safely, would love to hear!
Thank you so much! Any insight would be appreciated.
Statistics: Posted by julia! — Tue Jan 20, 2026 7:52 pm