WHR (Wrist Heart Rate) / Sensor Hub firmware module 2.60

Don't think so, at least not with 'official/final' firmwares. It is supported for beta firmwares though...

Well..let's hope Garmin release a Firmware correction rapidly. In my case the previous firmware was much better than this.

Thanks

Garmin has received the reports or devices no longer tracking heart rate accurately/HR data missing from the beginning of the run. Our engineering team is investigating to determine the root cause, so that this can be resolved. I do apologize for the inconvenience, and as always we appreciate the feedback that has been provided.

While I have not done a run since the update, I have notice breaks in the 24 hr HR data at the rate of around 3 per day with a period of about 10-15 mins. In each case they seem to appear just when the HR is on the increase. Getting up and walking around for example. Obviously the same thing happens when starting a run but to a greater extent.

Just wanted to point out that this behaviour doesn't seem to be restricted to a RUN activity,

So I wore the watch all weekend with no issue. Didn't do an activity, just used the HR widget. Didn't wear it all day yesterday and when I checked it last night the issue was back. HR would display for 10 seconds and then the lines would show up. If I leave the widget and then go back in it's the same thing. HR shows briefly and then gone.

Let's go Garmin. Don't make us wait months for an update.

I do apologize for the inconvenience that this caused. This is an issue that is actively being worked on by our device team, and we are continuing to update the case that is open for this issue to provide as much information as possible to our device team.

While I have not done a run since the update, I have notice breaks in the 24 hr HR data at the rate of around 3 per day with a period of about 10-15 mins. In each case they seem to appear just when the HR is on the increase. Getting up and walking around for example. Obviously the same thing happens when starting a run but to a greater extent.

Just wanted to point out that this behaviour doesn't seem to be restricted to a RUN activity,

I'm maybe thinking that my issue may not be related and could be a Garmin connect issue? For example I logged an Indoor Bike ride this morning using a HR strap and again a chunk of data is missing, BUT if you look at the detail in the activity itself, it is all there, so it may be that the data in the HR trace and timeline is missing some of the data or it is corrupted in GC. (See attached)


Apologies if I have confused the issue, however GC needs fixing in so many ways which doesn't help resolving issues with the watch...

I came across a post in the Vivoactive HR forum where a user did a little experiment to test his oHRM. He started a "run" activity, took off his Vivoactive HR and placed it on a pillow. He stated the HR increased while on the pillow. I decided to test my 235. I started a "run" activity with a HR of 69. I took off my 235, placed it on a pillow and gradually watch the HR go from 69 to 125. It bounced between 123-125 for about a minute before finally going to a no HR reading. I tried two other devices with oHRM. Neither had an increase in HR and lost the HR reading within a couple of seconds. I'm curious if someone who isn't having any issues with the WHR2.60 update will duplicate this test. I want to see if my 235 is defective, or if this is some strange behavior with Garmin's Elevate technology.

I came across a post in the Vivoactive HR forum where a user did a little experiment to test his oHRM. He started a "run" activity, took off his Vivoactive HR and placed it on a pillow. He stated the HR increased while on the pillow. I decided to test my 235. I started a "run" activity with a HR of 69. I took off my 235, placed it on a pillow and gradually watch the HR go from 69 to 125. It bounced between 123-125 for about a minute before finally going to a no HR reading. I tried two other devices with oHRM. Neither had an increase in HR and lost the HR reading within a couple of seconds. I'm curious if someone who isn't having any issues with the WHR2.60 update will duplicate this test. I want to see if my 235 is defective, or if this is some strange behavior with Garmin's Elevate technology.

Well, one of the issues with the OHR is that it adjusts like crap. So it easily takes 30 seconds to a minute before it actually reacts to for example an increase in heartrate when you increase intensity during a run (hence the uselesness of the OHR for interval trainings). Could have, or probably has, something to do with that?

And that is not so much a general OHR (Cross brands I mean, the MIO sensor doesn't seem to have this) issue, but more an issue with the FR235 (garmin home made) one. Not an issue with your specific FR235 at least I'd say.

I think in the last update, in an effort to resolve some of the oHR issues, Garmin engineers have added new algorithms that attempt to intellegently compensate for inaccuraces and poor performance of the technology. These algorithms probably define what to do when the watch has lost syncand is trying to predict what is happening while not actually sensing for a period of time.

I think what they did was poorly tested and validated as overall (and in its current state) it's worse than what it was but it's a step in the right direction I believe. The only issue is it's not ready for prime time and shouldn't have been released in the state it was released in.

Unfortunately, we all continue to be volunteer beta testers (with or without knowing). Why pay a few developers to properly test their software when the poor schmucks who paid good money for the device will just do the work for free? Bloody annoying it is and I've given up.

I think what they did was poorly tested and validated as overall (and in its current state) it's worse than what it was ...

Unfortunately, we all continue to be volunteer beta testers (with or without knowing). Why pay a few developers to properly test their software when the poor schmucks who paid good money for the device will just do the work for free? Bloody annoying it is and I've given up.

damn right man!

but i also think that simple HR readings with no other algorithms was better than this piece of sh***t: my older wtek sensor is better than 235 hrm today! it simply does not record 200/220bpm never! so why 235 needs to register these absurd values... well for me is a mistery!

I have had pretty good results overall. Not perfect but an improvement
http://www.midpackgear.com/2016/05/elevate-hr-monitoring-on-forerunner-235.html