HRV (again)
-
@JonasLarsson said in HRV (again):
It was worth a try. Did I expect help? No. Still. No response when you ask something here is like no reponse when you say hi to someone on the trail and they look away. We can do better.
hello ! i think it was sunday yesterday …:)
-
Slept 8.13 but that is not what the app says. Same kind of problem that I posted about yesterday? Beats me.
-
@JonasLarsson Weird. I usually only had one nap reported on the watch not recorded in the app but not such out of sync numbers. Did you try syncing again or the day after what will it tell you? Maybe they do some server side re-analysis of the data?
-
@EzioAuditore I had this problem only once before. Multiple syncs doesn’t change diff. Server? Not sure what you mean.
-
@JonasLarsson Well what Garmin does for example is they send the watch data to Backend services they re-analyse it and re-send it back to the watch, so in some cases the sleep data may change of what initially was said. Since Suunto is still not sending fitness data to the watch maybe it only reaches the application, hence the difference in values?
-
@JonasLarsson It looks like you woke up earlier and the watch synced with the app. Then you went back to sleep and the watch recorded the rest of your sleep, but the app didn’t update them anymore, hence the differences.
-
@maszop or this
-
@maszop said in HRV (again):
@JonasLarsson It looks like you woke up earlier and the watch synced with the app. Then you went back to sleep and the watch recorded the rest of your sleep, but the app didn’t update them anymore, hence the differences.
I was up drinking water and went back to sleep. This could explain it, but shouldn’t app reg again when I sync?
-
@JonasLarsson said in HRV (again):
@maszop said in HRV (again):
@JonasLarsson It looks like you woke up earlier and the watch synced with the app. Then you went back to sleep and the watch recorded the rest of your sleep, but the app didn’t update them anymore, hence the differences.
I was up drinking water and went back to sleep. This could explain it, but shouldn’t app reg again when I sync?
I was to fast to answer you. What you wrote doesn’t make sense. I did fall a sleep (which the watch registered) and drank water and went back to bed. If syncing is the problem the first face of sleep would be registered, right? App only registered my sleep after I went to bed again. The watch did register everything.
-
possibly if the app sync’d when you first woke up (before midnight the previous say) then it considered the first sleep as a ‘nap’ on the previous day and decided the sleep was from when you went back to sleep just before midnight through to when you woke up.
-
@far-blue But the Vertical doesn’t do naps?
-
@far-blue Also: The watch registered everything as sleep the morning after. How can the app loose hours of sleep when it gets the data from the watch?
-
@JonasLarsson The Vertical still uses FirstBeat algos for the sleep/step etc. (at least this is what I know) and will need time to move to full suunto native (like Race and Ocean).
-
Hi, it’ me again.
Hands up if you got this problem too. it is much easier when we stand together in this kind of really-important-for-me-as-a-human-being questions.
With that said, here a some beautiful pictures that will certainly make you wonder when will he stop. I get that.
-
@EzioAuditore actually I believe that Vertical is Suunto native but Race is licensed from a third party.
-
@seanvk
Or the opposite?
https://forum.suunto.com/post/131343 -
@EzioAuditore Did I answer you? Sorry if a didn’t. So what you are saying is that it will work better in the future? Sleep and HRV is obviously not correct today. Like last night the watch said that the sleep quality was good and that I was awake more than one hour. I was not.
-
@EzioAuditore said in HRV (again):
@JonasLarsson The Vertical still uses FirstBeat algos for the sleep/step etc. (at least this is what I know) and will need time to move to full suunto native (like Race and Ocean).
