10-07-2017
16:49
- last edited on
02-20-2018
16:20
by
MattFitbit
10-07-2017
16:49
- last edited on
02-20-2018
16:20
by
MattFitbit
Has anyone else noticed that the Heart Rate sensor is very inaccurate? Currently my Ionic is showing that my heart rate is in excess of 120, while at the same time my pulse ox machine (a medical device) is saying it's 82. The Samsung health app is inline with what the pulse ox is saying. I'm not sure if I have a defective Ionic or if others are having the same issue. ( Note: Sorry if there are any spelling errors, I am tryping around my cat, who has decided to sit directly in front of the screen)
Moderator edit: edited title for clarity
05-11-2018 02:20
05-11-2018 02:20
I found the samsung gear sport much better and accurate than the vivofit 3 and build quality and screen miles better
05-11-2018 05:08
05-11-2018 05:08
Hopefully somebody knows the sampling rate of the hear rate sensor.
Maybe to slow for fast actions 😉
But we will never know that.
I'm not sure that OS 2.1 will fix that problem with the accuracy.
Regards,
Mark
05-11-2018 05:38
05-11-2018 05:38
I love the passive always on screen of the Vivoactive, it's much like the screen of the last Pebble Time. In terms of build quality you're right, the Gear Sport delivers more. I just don't like the Samsung Universe, to take full advantage of the ecosystem you either have to install 3-4 apps or get a Samsung phone right away.
Considering the HR sensor of the Ionic, I still don't believe they can fix it with an update. It's not the sampling rate, it's the fact that they went with three sensors but only one LED. They want to win the game with the SPO2 sensor but forgot about the basics of HR measurement. They can't get enough light into the skin to get reliable information all the time. Just get in a dark room, and compare how a Fitbit Charge 2 (2 LED) or a Vivoactive 3 (3 LED) light the room and then in contrast the light coming out of the Ionic. It's simply less light.
05-11-2018 12:06
05-11-2018 12:06
Yes, that's why I 'd like to see the signal stenght of the heart rate sensor.
But I have had a 30 Euro Tracker with also one light and it shows my sleep stages. But I don't like there app design. Just data no graph.
That's why I still with Fitbit.
They can't show where the data is missing. I learn all raw data comes from the tracker and the calculation will be done online. So I assume there is the problem!
Regards
Mark
05-11-2018 13:08
05-11-2018 13:08
05-11-2018 13:31
05-11-2018 13:31
Your trying to transfer music that has digital rights management enabled on it. Must be music you downloaded a while ago. You may have to go back to iTunes and redownload new copies of the music with the DRM removed. I think they quit using DRM a while back.
05-14-2018 13:30
05-14-2018 13:30
05-14-2018 15:15 - edited 05-14-2018 15:17
05-14-2018 15:15 - edited 05-14-2018 15:17
@fluxx, returned my Versa today for precisely this reason. The single LED setup is way too finicky to get a consistent, accurate HR, even at rest. I'd be sitting still, the Versa nice and snug, and I'd still get 40 BPM spikes intermittently. Restarting it, pulse would display as normal.
Decided I'd rather have the $200 back and go on using my Blaze and Charge 2. When they wear out I'll probably go with Garmin. They seem to know what they're doing.
05-15-2018 07:24
05-15-2018 07:24
My issues with heart rate accuracy seem to be gone. I push the watch higher up on my arm when lifting and that seems to help. When running or biking the HR is fine.
05-15-2018 08:56
05-15-2018 08:56
06-01-2018 05:07
06-01-2018 05:07
Similar issue to many respondants. I've recently changed from the Surge to the Ionic. The resting heart rate is unchanged, however when I go for a run (usually for about one hour) the Surge reported my heartrate in the range 135 to 145, which seemed about right to me. Two runs with the Ionic showed my heartrate in the range 185 to 195 - which seems implausible (I can comfortably talk to people while I'm running - i.e. I'm not overdoing it). It'd be interesting to see if FitBit have anything to say (I tightened the strap for the 2nd run - will try the other wrist for the next run). I have some time to decide whether to return the Ionic.
06-01-2018 05:52
06-01-2018 05:52
06-01-2018 06:51
06-01-2018 06:51
06-01-2018 07:19
06-01-2018 07:19
Tried an "open box" Ionic short term. Installed all the latest firmware, unit appeared "as new" and seemed to be working great.
Tried a 3 mile walk on a known trail, GPS came back as 2.85 miles, pace was overstated. Loaded the .tcx file into Strava, it corrected it to a little over 3 miles (of course) Figured I could adjust my stride and calibrate it for the next session.
However, this morning I started having the "runaway heart rate" problem when at rest. It would repeatedly rise to 120 BPM, and then drop back to my normal 60 or so. I had the same problem with a Versa.
Decided to send it back to the vendor for a refund. I agree with a previous poster, the heart rate sensors on both the Ionic and Versa have a bad design, not enough illumination from the LEDs or something. The software gets confused and doubles the actual HR.
I think it's time to try a Garmin at this point.
06-01-2018 07:51
06-01-2018 07:51
06-01-2018 11:12
06-01-2018 11:12
@DaveEuph wrote:Similar issue to many respondants. I've recently changed from the Surge to the Ionic. The resting heart rate is unchanged, however when I go for a run (usually for about one hour) the Surge reported my heartrate in the range 135 to 145, which seemed about right to me. Two runs with the Ionic showed my heartrate in the range 185 to 195 - which seems implausible (I can comfortably talk to people while I'm running - i.e. I'm not overdoing it). It'd be interesting to see if FitBit have anything to say (I tightened the strap for the 2nd run - will try the other wrist for the next run). I have some time to decide whether to return the Ionic.
@DaveEuph: strange, I have the same history (Surge->Ionic) and similar issues with the heart-rate chart after running. It doesn't seem to correspond with my up-hill or faster paces during the run. In fact, it just seems to run steady in the 170 - 180 range. (which seems high).
Out of suspicion, I taped paper over my arm where I wear my Ionic and ran a standard 7.7 mile course yesterday. When finished, the heart-rate chart was identical to the last time I ran the course with Ionic directly on my skin.
If ionic will accurately measure heart rate with paper covering the green light, I don't understand the official guidance of where and how snugly to place it.
06-01-2018 12:50
06-01-2018 12:50
It sure seems that at times, Fitbit has applied machine learning to HR and replaces real data with predicted data. The only official statements from Fitbit about machine learning are about sleep stages.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
06-01-2018 20:35
06-01-2018 20:35
This reminds me of my post a while ago:
So there is some sort of proof that the Ionic does funny things with the real HR data.
06-03-2018 13:44
06-03-2018 13:44
I’m having the same issue with my Ionic. Today I went to the track for a 3 mile run walk. It shows me at an average heart rate of 153 BPM, and a max heart rate of 180 BPM.
At 75 years of age, this is a physical impossibility. I would estimate my average heart rate at 120 to 125 BPM, and my max heart rate at 145 BPM.
Even though my FitBit blaze was not accurate either, it was way more accurate than the ionic.
Any suggestions?
06-03-2018 13:59
06-03-2018 13:59