02-25-2020 08:43
02-25-2020 08:43
So, I rowed on a rowing machine in the gym for 22 minutes, from 6:26 am to 6:48 am. I synch the Inspire and then add the exercise by selecting "rowing machine" and putting in the timeframe. It does not, however, recognize that my heart was beating during that time and says "Not Enough Data Available."
When I review my heart rate on the dashboard, however, the heart rate data during my row is very clearly there showing the peak, cardio and fatburn moments.
I get no HR data if I try to enter "workout" or "spinning" or "walking" during that time.
Just now, while typing this, I noticed that the app on my iPhone shows that the Inspire was "synched today, 6:36 am" although it is now 11:36 am. So there's a 5 hour difference between the app and the device somewhere which is strange because the dashboard HR info is aligned correctly.
I was able to successfully add the rowing workout if I changed the time to 1:26 - 1:48 am.
Any thoughts on how to get the time aligned?
Thanks
02-25-2020 18:13
02-25-2020 18:13
So, I reset the Inspire and then un-installed and re-installed the app on the iPhone. The synch time is now correct, no more 5 hour difference. Will have to wait till Thursday to see if it picks up HR while rowing.
02-27-2020 08:24
02-27-2020 08:24
I believe the sync time difference has been resolved which resolved the other issues by:
Un-installing Fitbit app from the iPhone
Turning the iPhone off and then back on
Removing all user data from the Inspire HR
Re-installing the Fitbit app
Setting up the Inspire HR while it is connected to its charger and charging. Having it connected to the charger seems to be key.
No issues since then.
02-28-2020 21:38
02-28-2020 21:38
Someone in another thread (https://community.fitbit.com/t5/Inspire-Inspire-HR/Inspire-HR-shows-0-calories-burned-during-logged-...) tried this and it didn't work. Has anyone else gotten this resolved by Support? I still have not received a response to my call 😞
02-29-2020 21:50
02-29-2020 21:50
Apparently there's an 'official' thread on this acknowledged by FitBit: