If your device is offline for several days, it may be that your clock is out of synch when Connect starts on boot (if rpi-connectd starts before your time is synchronised via NTP) meaning that it will send its required heartbeat to our API with an incorrect expiry date so it gets immediately deleted.
We are currently testing a fix for this but can you please see if that explains the behaviour you're seeing by checking your logs on boot:
If you see rpi-connect come up before systemd-timesyncd reports something like "Initial clock synchronization to Thu 2025-10-09 11:44:40.725006 BST." that might explain the issue.
We are currently testing a fix for this but can you please see if that explains the behaviour you're seeing by checking your logs on boot:
Code:
$ journalctl --boot --unit systemd-timesyncd --user-unit rpi-connectStatistics: Posted by paulmu — Thu Oct 09, 2025 10:53 am