utilities/zepp_to_influxdb#9: Development Ceased

As I've noted previously it was never my original intent to interact with Zepp's API at all and I certainly didn't want to be reliant on reverse engineering the App's behaviour every time I want to add a feature.

In that previous write up of this project, I noted my discomfort with the need to first send data to Zepp's servers

Although I've found a way to extract data, it relies on use of the official app, meaning that data continue to be sent into the cloud service of an organisation who may, or may not, do a good job of protecting it.

Even if they do protect it well, the health data that they hold gets aggregated and analysed: not only does the app currently make API calls to fetch globalised averages of some metrics, the company also makes data available to researchers.

Whilst health research is very important, the idea of a foreign commercial company acting as a data-broker does make me a little uncomfortable: they're not subject to the same weight of responsibility and regulation that a healthcare provider is, they don't have the benefit of an existing trust relationship and (if they do screw up) it'd likely be very difficult to obtain meaningful legal remedy.

It's worth noting too, that the watch has GPS, and even professional secret keepers have been caught out as the result of provider mistakes when handling location data.

Needless to say, I'd prefer my data didn't need to be sent to Zepp's servers in the first place and if/when someone manages to add Bip 3 support to Gadgetbridge, it's very likely that I'll pivot back to my original approach.

Gadgetbridge have now added support for the Bip3, so I've resumed developing gadgetbridge_to_influxdb (there's a write-up on using that here)

So, although the codebase and this issue tracker will remain online, it's very unlikely that there'll be any future changes made to the codebase.