Very late response, but I don't know how useful it is anyway:
Compared to a Fitbit Versa 3, I usually get within 5-10bpm consistently. They both use the photosomethingorother sensor, but in case there was some secret algorithm Fitbit uses, here's a roughly what I've found:
Fitbit likes to draw their graphs as "landscape" as possible, with a thick line that hides how spikey it gets, but usually it has the exact same peaks and valleys as Bangle.
Attached are screenshots of the graphs of both while shoveling and using a snowblower on and off for about an hour and a half.
Peaks in the Fitbit graph are 117bpm, then 132, 132, 132.
Corresponding peaks in Gadgetbridge are 90bpm, then 127, 130, 137.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Very late response, but I don't know how useful it is anyway:
Compared to a Fitbit Versa 3, I usually get within 5-10bpm consistently. They both use the photosomethingorother sensor, but in case there was some secret algorithm Fitbit uses, here's a roughly what I've found:
Fitbit likes to draw their graphs as "landscape" as possible, with a thick line that hides how spikey it gets, but usually it has the exact same peaks and valleys as Bangle.
Attached are screenshots of the graphs of both while shoveling and using a snowblower on and off for about an hour and a half.
Peaks in the Fitbit graph are 117bpm, then 132, 132, 132.
Corresponding peaks in Gadgetbridge are 90bpm, then 127, 130, 137.