In my blog post, I noted that
Despite being almost constantly connected (in order to send notifications to the watch), the Zepp app doesn't seem to sync data very frequently. In fact, as far as I can make out, it often doesn't sync data at all until the app is next opened (I haven't yet tried leaving it for days though).
I've now tried leaving it for a few days - the result is that I ended up with gaps in my data. The app doesn't sync at all unless it's opened.
Whilst this isn't a problem with this sync script per se, it does affect it, so I'm raising this to look at options
Activity
19-Aug-23 11:43
assigned to @btasker
19-Aug-23 11:49
I had been hoping that there might be an intent that we could trigger to have the app sync, however no such luck:
So, instead, we need to use a sledgehammer to crack a nut - we can use Tasker to automatically launch the Zepp app (at least) once a day.
There is, however, still an issue with this.
I configured a tasker profile to run at 12:42 (i.e. a few minutes ago) and launch
Zepp
.It did exactly that.
But, Zepp was a little misleading - when I unlocked the screen it started syncing with the watch. This gave the impression that it only syncs when the screen is unlocked. However, as far as I can see, it had synced on launch - it must just launch a new sync when the display is unlocked.
26-Aug-23 15:59
mentioned in issue gadgetbridge_to_influxdb#8
02-Sep-23 16:51
Closing as Won't Fix - see #9