This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FR235 HRM and Sleep Data Comparison

Hi,

I have received my FR235 yesterday and am currently in the process of comparing its HR data and sleep data to other products I have been using so far.

HR: Compared vs Polar H7 chest strap recorded by Polar Beat iOS app. I am using mygpsfiles.com to compare.
Sleep data: Compared to iOS Sleep Cycle Alarm app.

I thought I might share this here in a thread.... so here you go :) I will add new comparison-results once I have completed them.

GPS Run 02 Dec 2015, Beta 3.13

Blue: FR235
Orange: H7

My first ever run with the FR235, I was trying different paces including walking to see how it would react. Over all I am satisfied with accuracy.
- at around 14:00 I slowed down for the first time and the FR235 lagged behind with dropping HR again.
- at 25:00 I did a sprint... the FR235 was suprisingly accurate with this one
- at 33:00 it was a little more inaccurate, maybe because at that point I was slowing down again
- From about 52:00 I was just sitting down... there the FR235 was jumping a lot more up and down than the H7

0 timgrose over 9 years ago

Smart recording is for everything and not just GPS. I mentioned this in another thread just now.

0 philippe.berini over 9 years ago

yeah, I just read your comment after my post 😄

0 philippe.berini over 9 years ago

Here's another Sleep Tracking comparison!

First, this is what my iOS app "Sleep Cycle Alarm" tells me. I'd say I had about 3h of deeper sleep from 1:30 to 4:30.

Here's what I get In GC. Not even one hour of deep sleep.

Movements however are similar to those recorded by Sleep Cycle Alarm. A bit more spikey.

But when I look at the movements in the GC app they are a lot less spikey. Of course we have a scaling issue here. But it even more gives me the impression that I DID have more than one hour of deeper sleep!

What do others say about sleep tracking so far?

0 Former Member over 9 years ago

Here's another Sleep Tracking comparison!

First, this is what my iOS app "Sleep Cycle Alarm" tells me. I'd say I had about 3h of deeper sleep from 1:30 to 4:30.

Here's what I get In GC. Not even one hour of deep sleep.

Movements however are similar to those recorded by Sleep Cycle Alarm. A bit more spikey.

But when I look at the movements in the GC app they are a lot less spikey. Of course we have a scaling issue here. But it even more gives me the impression that I DID have more than one hour of deeper sleep!

What do others say about sleep tracking so far?

I'm finding it a bit hit and miss compared to the Fitbit, which was pretty accurate. First night of wearing the 235 it didn't even register me waking up at 04.30 to go to the loo, which is bizarre. I think sleep tracking is relatively new, so will probably get ironed out.

0 philippe.berini over 9 years ago

Did you have HR tracking enabled? I wonder if HR tracking has any effect on the sleep statistics.

Yes, HRM is enabled... I don't think it is used for sleep tracking though.

Here's the HR from that night:

0 philippe.berini over 9 years ago

Todays Menu: Interval

On today's menu I had put an intervals run... of course I am still in comparison mode to my chest strap ;-)

Like in runs before the FR235 has mainly those two issues for me:

- during warmup and cooldown of the run it's mostly more off/spikey than else
- quite spikey (as usual)

BUT: I never compared to what my H7 is reading during the run, so I was quite satisfied to see the result was actually this good overall. I thought I would run much more into crossover lags or alike.

Here's also the run in GC: https://connect.garmin.com/modern/activity/978516467

0 philippe.berini over 9 years ago

I hope they don't just reduce the HRM intervals because that is detrimental to the activity tracking, especially the calorie burn. If they have an option to turn it off, that may make sense.

Anyway, they should be concentrating on sorting the battery issues, rather than robbing Peter to pay Paul.

After the update to 3.20 I checked this nights recordings. On first look the graph appeared much more flatlined than it used to.

Before I got about 14 readings in a 5 hour period (as far as I can tell from data points in the HR graph in GC). Tonite I counted only 9 data points in that period. So apparently they DID change HR reading frequency by abot 30-40%

We'll see how it turns out and if Peter still has enough to get some candy...

0 Former Member over 9 years ago

After the update to 3.20 I checked this nights recordings. On first look the graph appeared much more flatlined than it used to.

Before I got about 14 readings in a 5 hour period (as far as I can tell from data points in the HR graph in GC). Tonite I counted only 9 data points in that period. So apparently they DID change HR reading frequency by abot 30-40%

We'll see how it turns out and if Peter still has enough to get some candy...

Was that when you were asleep?

Be interested to see if the rate the HRM takes data is reduced during non activity periods as the stats for calories etc is going to be pretty much guess work.

0 philippe.berini over 9 years ago

Was that when you were asleep?

Be interested to see if the rate the HRM takes data is reduced during non activity periods as the stats for calories etc is going to be pretty much guess work.

Yes, that was when I was asleep... I'd say that during sleep calories consumption should not have a big variance?

As far as I can see so far, when moving around a bit, frequency of readings seem to increase. I think it says so in the manual or somewhere I read that... Then impact on calories consumption should be ok, no?

0 gpb11 over 9 years ago

Be interested to see if the rate the HRM takes data is reduced during non activity periods as the stats for calories etc is going to be pretty much guess work.

Perhaps. Though I suspect there are few use cases where there's no movement detected by the watch's accelerometer yet the wearer is generating a calorie burn substantially above BMR.