Improving connection reliability

The Dataplicity agent reconnects after network changes, but the operating system and application still need reliable network, time, and power behaviour.

Keep time accurate

Incorrect system time can cause TLS certificate failures. Enable the distribution's supported time synchronisation service and verify it recovers after power loss and long offline periods.

For a systemd-based distribution:

timedatectl status
systemctl status systemd-timesyncd

Use the time service recommended by your Linux distribution if it does not use systemd-timesyncd.

Make networking recoverable

• Use the distribution's supported network manager
• Configure DNS and default routes explicitly
• Test DHCP lease renewal and access-point changes
• Add bounded retries with backoff to your own application
• Avoid custom scripts that restart undocumented Dataplicity processes or depend on internal agent paths

Design for field power conditions

• Use a reliable power supply sized for the hardware and attached peripherals
• Protect writable storage from abrupt shutdowns
• Test repeated power cycles
• Use a hardware watchdog where unattended recovery is required

Observe recovery

Test on a staging unit:

1. Disconnect and restore its network
2. Reboot the router while the device remains powered
3. Power-cycle the device
4. Correct a deliberately inaccurate system clock
5. Confirm the device returns online and resumes expected logs and monitors

Contact Dataplicity support before adding service-manager overrides for the agent. Supported process names and installation details can vary by agent release and operating system.