Package: remoteit 5.4.2 (arm64 RPi)
Download: https://downloads.remote.it/remoteit/latest/remoteit.arm64.rpi.deb
Summary:
The remoteit-main init script sources functions.sh and oem.sh, then calls r3_start_services. However, r3_start_services() is defined in sysvinit.sh, which is never sourced. The call silently fails
because it’s wrapped in 2>/dev/null.
As a result, remoteit-main start runs successfully but never starts the connectd processes — the device registers and appears in the dashboard but stays permanently offline.
Affected files:
- /etc/init.d/remoteit-main — sources functions.sh and oem.sh, calls r3_start_services
- /usr/share/remoteit/functions.sh — calls r3_start_services but does not define it
- /usr/share/remoteit/sysvinit.sh — defines r3_start_services() but is never sourced
Reproduction:
- Install remoteit.arm64.rpi.deb on Raspberry Pi OS (Trixie/arm64)
- Register device via bulk provisioning
- Run sudo /etc/init.d/remoteit-main start
- Observe: schannel and demuxer start, but no connectd processes are spawned
- Device shows as offline in remote.it dashboard
Workaround:
echo ‘. /usr/share/remoteit/sysvinit.sh’ >> /usr/share/remoteit/functions.sh
/etc/init.d/remoteit-main restart