Am in the process of tracing some random system reboots, and found a lot of errors with the volumio-remote-updater in my logs.
Maybe you could include an exponential back off in the connection attempts?
$ systemctl status volumio-remote-updater.service
● volumio-remote-updater.service
Loaded: loaded (/lib/systemd/system/volumio-remote-updater.service; enabled)
Active: active (running) since Wed 2019-04-10 15:59:02 UTC; 2 weeks 0 days ago
Main PID: 542 (volumio-remote-)
CGroup: /system.slice/volumio-remote-updater.service
└─542 /usr/local/bin/volumio-remote-updater
Apr 24 20:53:38 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:38] [error] handle_connect error: Underlying Transport Error
Apr 24 20:53:48 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:48] [info] asio async_connect error: system:111 (Connection refused)
Apr 24 20:53:48 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:48] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Apr 24 20:53:48 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:48] [error] handle_connect error: Underlying Transport Error
Apr 24 20:53:58 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:58] [info] asio async_connect error: system:111 (Connection refused)
Apr 24 20:53:58 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:58] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Apr 24 20:53:58 Völümio volumio-remote-updater[542]: [2019-04-24 20:53:58] [error] handle_connect error: Underlying Transport Error
Apr 24 20:54:08 Völümio volumio-remote-updater[542]: [2019-04-24 20:54:08] [info] asio async_connect error: system:111 (Connection refused)
Apr 24 20:54:08 Völümio volumio-remote-updater[542]: [2019-04-24 20:54:08] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Apr 24 20:54:08 Völümio volumio-remote-updater[542]: [2019-04-24 20:54:08] [error] handle_connect error: Underlying Transport Error