WearOS: Connection loss to nightscout when switching from WiFi to cellular (no phones involved)

[thepartisan]

Situation

Working mirroring of data from a direct-to-watch paired Libre3 to nightscout while the watch being on WiFi, phone completely turned off. Leaving WiFi range now into cellular/LTE.

Actual behaviour

Data not received anymore by nightscout server. This can be worked around by force-restarting Juggluco on the watch once wifi connection is lost. After that data is received again on this path: Libre3 -bluetooth-> Watch -cellular-> nightscout URL

Impact

As my 11-year-old son keeps forgetting to restart, this leads to negative vibes in the family.

Expectation

The data keeps getting transmitted, as the URL did not change. No need for a restart of Juggluco.

Hint

If you start Juggluco while there is no WiFi connection established, a WiFi connection dialog pops up. After ignoring this pop-up, LTE/cellular is used and everything works until you enter WiFi the next time.

System details

Google Pixel Watch 2 LTE
Libre 3 bluetooth direct-to-watch (rock-solid, btw.)
No phones involved here (except for pairing every two weeks)

Being a software engineer myself, but with no Android development experience at all, I can offer to have a look into that myself if someone can give me a hint where in the code base I should start looking.

[j-kaltes]

You mean that you have configured a Nightscout Uploader on Juggluco for WearOS. It uploads via WIFI, but doesn't switch to LTE automatically when the watch comes out of WIFI reach. Only after restarting Juggluco on the watch does that happen.

What happens when you turn mobile data off and on, or turn the uploader off and on?