We use some essential cookies to make our website work.

We use optional cookies, as detailed in our cookie policy, to remember your settings and understand how you use our website.

Raspberry Pi Connect is out of beta: simple remote access, now even better

It’s been just over a year since we launched the Raspberry Pi Connect beta, giving you simple, remote access to your Raspberry Pi straight out of the box, from anywhere in the world. The response from users has been fantastic, and we rapidly reached an install base of over 100,000 devices. Today we’re excited to announce that following the recent release of version 2.5, we’re dropping the “beta”.

Composite image: screen grabs of the Raspberry Pi Connect Dashboard, a connected device desktop showing Connect system tray icons, and the Connect command line interface

Smarter wake-ups: data-efficient connections in v2.5

Prior to version 2.5, the Connect client software running on a Raspberry Pi device connected to the service would continually poll Raspberry Pi’s servers for requests to connect. This worked well for us because it was easy to scale – traffic was a predictable shape; there was just a lot of it. But wasn’t ideal for users – their devices were regularly waking up to make HTTP requests, and data usage was higher than it needed to be.

Starting with version 2.5, the Connect client now holds a single long-lived HTTP connection to a Raspberry Pi server.  Now when you click the “Connect” button on connect.raspberrypi.com, an event is broadcast to the device to wake it up and start the process of establishing a connection.

Screen grab of a Raspberry Pi Connect dashboard showing a loading screen that reads: "Waiting for response from pitowers"

Optimised heartbeat for leaner dashboard updates

Separately from connection negotiation, the Connect client sends heartbeats to Raspberry Pi servers, periodically and also on startup and shutdown of a device and in response to changes to its internal state. For example, the user disallowing screen sharing via the CLI (command line interface) would trigger a heartbeat. This information is then used to keep your dashboard on connect.raspberrypi.com up to date. 

Prior to version 2.5, the Connect client would send four heartbeats in rapid succession; this wasn’t a conscious design decision, but a side effect of how the client evolved over time. Starting with 2.5, these heartbeats are now debounced, and users should see many fewer requests to the Connect API outside of connection negotiation.

Also starting in 2.5, each individual heartbeat is now compressed before it is sent to the server, making it about 50% smaller.

Screen grab of a Raspberry Pi Connect dashboard showing four devices and their connection status

How to update

To update to the latest version of Raspberry Pi Connect only, run the following commands (if you have installed Connect Lite, replace rpi-connect with rpi-connect-lite):

sudo apt update
sudo apt install --only-upgrade rpi-connect

This week’s other Raspberry Pi software news is that we’ve released a new version of Raspberry Pi OS; this has the latest version of Connect installed, so you might want to consider updating your OS. Read our post about the new release for instructions on how to do that.

If you haven’t tried Connect yet, check out our official guide to get it up and running on your devices.

18 comments

Wyatt avatar

Great news, guys! Ever since Connect wwas released I’ve dropped TeamViewer and no plans to go back.

Thanks for all the effort!

Ashley Whittaker avatar

Today is definitely a Top 5 Friday.

Eric avatar

So does this matter for lite? Can I benefit from it as a headless user?
If so. Can it be set to ping other servers and not the one its set to?

Jeff Geerling avatar

Yes; I use it on some Pis running Lite if I just want to be able to log into the console remotely without setting up a VPN or tunnel to it. Still quite useful!

San avatar

I really love how it just works. But the only issue I face is if my iPad browser loses focus for some time, the connection is lost and I have to reconnect.

With the terminal, if I lose that connection, I cannot get that session again and have to start with a fresh new terminal. So a running task is probably running in the background and I can’t do anything about it.

AndrewS avatar

You could use screen or tmux, as suggested in the documentation https://www.raspberrypi.com/documentation/services/connect.html#remote-shell

sdnscottie avatar

The raspberry pi connect is fantastic, I use it or Rustdesk..
Both are excellent.
Thanks for all the hard work, Scottie

Tomer avatar

Any future plans for file transfer?

Arsalan avatar

Yes. This is the first thing on my mind. Not sure if the pi connect client is based off the VNC client but both are missing file transfer. The move to bookworm and wayland means RealVNC is no longer there. It would be nice if the Raspi team bring this feature to parity with what was available in bullseye.

DotLYHiyou avatar

Can RPI Connect work with Raspberry Pi Lite 64-bit (no gui)

Don Wills avatar

Can there be multiple users associated with a remote RPi, and therefore there can be a super-user that sees them all, with other users seeing only sub-groups of computers that those people control, without giving them access to other RPis?

AndrewS avatar

I’m not sure what you’re asking for, but it sounds like you might be interested in Connect for Organisations https://www.raspberrypi.com/news/raspberry-pi-connect-for-organisations-plus-full-screen-support/

Don Wills avatar

Thanks for your response. No, Connect for Organizations is not what I’m looking for. Here’s an example. I am an independent contractor. I support 3 customers, each of which has a Raspberry Pi or 2 that they access with their own group. Each customer wants me to occasionally fix something, so I log into their account with Raspberry Pi Connect, connect to their machine and do my work. So now I have 3 Raspberry Pi accounts, but I don’t have control of the passwords. My business grows. I now support 40 customers. Untenable. The solution is to allow each remote Raspberry Pi to be visible to both their own group and my personal group. Thus my statement – can there be multiple users/groups associated with a given Raspberry Pi so that any of them can get access. It is perfectly acceptable if one account has connected to a Raspberry Pi, other accounts are rejected until the first account closes the connection.

alan bromley avatar

I attemted to load plasma-desktop from the lite version.
The installation was ok.
When i ran sddm the plasma login screen was ok but when I entered the password all I got was a blank screen with a cursor.
HELP!!!

AndrewS avatar

It’s possible that plasma-desktop doesn’t support the Wayland protocols needed by Connect. See https://www.raspberrypi.com/documentation/services/connect.html#troubleshooting

Tobias avatar

Rpi-connect is amazing, but when using the 5 inch lcd screen from waveshare and installing drivers from github (https://github.com/goodtft/LCD-show.git) the screenshare option completely disappears from connect.raspberrypi.com. Is there a solution for this? When using rpi-connect doctor it says there’s a wayland compositor available which you can get by being on the latest version of raspberrypi, but I am already on the latest version. This is what I run:

raspberrypi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME=”Debian GNU/Linux 12 (bookworm)”
NAME=”Debian GNU/Linux”
VERSION_ID=”12″
VERSION=”12 (bookworm)”
VERSION_CODENAME=bookworm
ID=debian
HOME_URL=”https://www.debian.org/”
SUPPORT_URL=”https://www.debian.org/support”
BUG_REPORT_URL=”https://bugs.debian.org/”

rabbi avatar

Is there a way to directly connect without going through the Pi Connect website?
I have a Pi installed aboard my sailboat, but the Wifi often lacks internet access. Yet I’d like to connect to the Pi from a windows PC.
Like using some VNC client to directly connect to the PI?
Thanks!

Comments are closed