uploads/20b50c66c5a9ee6e2a0080d4ee9aca2e/image.png

About 1 result found. (Query 0.4602 seconds)

• 

  #1 Don't write missed heart-rate reads : utilities/gadgetbridge_to_influxdb#1

  http://lomteqnxehqjdemqgzse7xchjlusgnpoxq2fpmz3yuukyfzc22t5gwyd.onion/gils_projects/issue/utilities/gadgetbridge_to_influxdb/1.html

  ---

  utilities/gadgetbridge_to_influxdb#1 Whilst investigating Zepp's heart-rate data, I found that the app [seems to use](https://www.bentasker.co.uk/posts/blog/software-development/extracting-data-from-zepp-app-for-local-storage-in-influxdb.html#init_hr_values) the values `255` and `254` as special values (indicating missed/skipped reads). Looking at the heart-rate data that we've pulled out of the Gadgetbridge database:  It looks like it's the watch itself supplying these values. The result is that we're currently writing quite a few `255`'s into Influx. The values can easily be excluded at querytime, but in `zepp_to_influxdb` I decided to [skip these values](https://projects.bentasker.co.uk/gils_projects/commits/utilities/zepp_to_influxdb/51fd5a2c46738dc043ebb6fa17860d168f1342c5.html#l69) so it'd probably make sense to keep things consistent by doing the same here.