08-30-2017 03:50
08-30-2017 03:50
The app and website for fitbit does not match.
The app and watch shows a resting heart rate of 55 while the website shows 56. These are the screenshots taken at the same time.
08-30-2017 04:16 - edited 08-30-2017 04:18
08-30-2017 04:16 - edited 08-30-2017 04:18
Rounding issue for display value would be my guess, mobile display vs database display.
Good catch @Dafauti, the true calculation is most likely a fraction of a beat between the two whole values.
Have a great morning!
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-01-2017 19:08
09-01-2017 19:08
You say the app matches the Blaze. The app also has the ability to act as a remote display, and show what is on the tracker in real time.
The website does not have this ability, and the watch does not show the resting heartrate. It shows the current heartrate, which makes me believe the app is showing real time data.
09-01-2017 19:27
09-01-2017 19:27
I'm calling it a rounding issue as well. I first noticed the discrepancy over two years ago and I'm thinking I've only seen the website dashboard and the phone app agree no more than two days per month.
09-03-2017 21:07
09-03-2017 21:07
09-04-2017 04:18
09-04-2017 04:18
@Dafauti wrote:
I would like to clarify the following @Rich_Laue
1)The watch does show the resting heart rate (along with the real time
heart rate)
2) The website takes the data from the app, so it should show whatever the
watch shows, which it doesn't.
3) The app shows the real time data. Initially the website used to show
whatever the app showed, but not anymore.
Ummm, no, the website doesn't take data from the app; both the app and the web site pull their data from the Fitbit servers. As for how the data gets to those servers, it is fed from the tracker via either the Fitbit Connect app which runs on a computer and/or a separate component built into the phone app.
09-04-2017 04:21
09-04-2017 04:21
09-04-2017 04:23
09-04-2017 04:23
@Dafauti wrote:
"the website doesn't take data from the app; both the app and the web site
pull their data from the Fitbit servers"
The server has to get the data from the app....there's no other way in
which it (website) can connect to the tracker.
Not true. I synch my Fitbit almost exclusively from my PC. Even when I do synch with my phone, that data is not stored on the phone itself, it is passed to the Fitbit servers, and then when you want to look at the app, it pulls it back from the server.
09-04-2017 04:29
09-04-2017 04:29
09-04-2017 05:50
09-04-2017 05:50
The point you're missing is there is in fact another way; believe it or not, the phone app displays data taken from the Fitbit servers. The path for the data is from the tracker, through upload/synch logic of Fitbit Connect or the phone app, to the Fitbit servers, and then back to the phone display or the Fitbit dashboard.
09-04-2017 21:35
09-04-2017 21:35
09-05-2017 02:01 - edited 09-05-2017 02:01
09-05-2017 02:01 - edited 09-05-2017 02:01
Why shouldn't there be a mismatch? If the software on the phone rounds down and the scripting for the web server is only able to round up, then there will virtually always be a mismatch. Remember, the phone APIs have fully functional language extensions, web service scripting tools such as HTML5 often do not.
09-05-2017 02:13
09-05-2017 02:13
09-05-2017 06:08
09-05-2017 06:08
Is your life going to be somehow more complete if your RHR is 1 beat per minute higher or lower?
09-05-2017 07:35
09-05-2017 07:35
09-05-2017 07:39
09-05-2017 07:39
Clearly you know nothing about the various programming tools available for developing something like this. As for the name calling, I will not respond in kind, that would be like shooting fish in a barrel.
09-05-2017 11:54
09-05-2017 11:54
Yes indeed, a change in resting heart rate is an indication of training intensity. As an example, if a person assumes he is over training once RHR reaches 59, if that 1 beat pushes past 58, he knows he needs to stop training and he will be making a bad decision. Irrespective of whether life depends or not a bug needs to be fixed. There is no room for error when a payment has been made to purchase a product / contract.
09-05-2017 11:57 - edited 09-05-2017 11:57
09-05-2017 11:57 - edited 09-05-2017 11:57
@Venkats wrote:Yes indeed, a change in resting heart rate is an indication of training intensity. As an example, if a person assumes he is over training once RHR reaches 59, if that 1 beat pushes past 58, he knows he needs to stop training and he will be making a bad decision. Irrespective of whether life depends or not a bug needs to be fixed. There is no room for error when a payment has been made to purchase a product / contract.
Sorry, not buying; one's RHR can vary for many-MANY different reasons, over training is just one of them; I submit a 1 BPM variance is irrelevant when it comes to a guideline for training.
09-05-2017 16:18 - edited 09-05-2017 16:20
09-05-2017 16:18 - edited 09-05-2017 16:20
@Dafauti the point @shipo is making.
A sync only happens when the data goes from your tracker to the Fitbit server, this can be done through the Fitbit app or Fitbit connect.
The fitbit softwate simply passes the data from the tracker on to the server. It does nothing to the data durring a sync.
The Fitbit server then processes the data, looking for sleep, auto detected exercises, combine multiple trackers, etc.
Now the app goes to the server to get the processed data and displays it.
The website gets its data from the same server.
When it comes to live data, yes you still have this option. Open the app and go for a walk, the app and tracker will start comunicating and the app will act as a remote display. You will have to waot for any sync to finish but it still works.
09-05-2017 21:21
09-05-2017 21:21
and even when shooting the fish in the barrel you surely will miss the target