Sleep tracking dos not work after update
-
Hello,
Today sleep tracking has not worked for me (It was working before the update). I’m one of those users whose HR is usually under 40bpm while sleeping
The watch is saying this:
But I have slept 6 hours. I have also not received the morning report.
Can anyone check if it has the same issue after the update? I will track again this night (UTC+1)
-
@dreamer_ Hi
I just check and my tracking went fine, duration is spot on and I just got my report with the sleep score
Maybe punctual issue ? Have a nice day -
@Josaiplu It is very strange and in fact the first (and only) day since I have the watch that I have had this issue. It was fine before.
What is your HR while sleeping? The changes are for those below 40. Thanks for the answer.
-
@dreamer_ My resting HR is 50-55 so could be linked to your range indeed
-
@Josaiplu the changes are from those who have 40 or less bpm. That is not your range.
These are the proves that sleep did not work:
The HR is tracked ok during the sleep. Here you can see the 6 hours of the sleep:
That means that the HR meassurements are fine. HR was tracked during the sleep
And here is the sleep report, which is broken:
-
@dreamer_ mine seemed to be fine this morning.
-
@Todd-Danielczyk The same I was telling @Josaiplu . The changes in firmware for sleep tracking are for those that have 40 bpm or less. That is not your case either.
-
I got the same figures (41/38) in the app , that could be a funny coincidence or a bug
In the watch 39/38
-
@sartoric in fact as you can see, I have 40/38 in my watch and 41/38 in the app. With your similar bmp, your sleep tracking was fine?
Thanks!
-
@dreamer_
yep the tracking was fine, at least the duration of it. -
@sartoric I Will check again tonight for sure. If I have the issue again, I’d like to help giving my logs or whatever is needed.
Thanks
-
Do a soft reset. Mine works just fine (almost every time)
-
@Iggge It worked!! Today the tracking is just perfect.
My bpm are a bit higher today (I have an exam and I’m not sleeping as much as I should)
@sartoric today I have the same info in the watch and the app but in the app I see in the first capture a minimum of 40 and in the second a minimum of 39. The watch says 40
-
Today the sleep tracking was again not accurate, after the update. It is not that bad like the first night (which was totally wrong), but It did not track correctly the sleep.
So from 3 days, I have a very bad tracking, a good one (after reset) and a not good one.
The watch detects that I’m sleeping at 1:19am but as you can see in the HR data, that is not true.
These accuracy issues are only happening after the update. Everything was fine before the update. All that I know is that I’m in the HR affected range of the update.
-
@dreamer_ Hi,
I am in the HR range of the update too, and, for now, I did not experience major differences from before, it seems that it is more precise in the awake time. Still it is not perfect, and I wish they will solve the licensing deal to obtain sleep stages and nap detection
-
@Manuele thanks for the report. I will check again tonight restarting the watch perhaps. There’s something there different. But these days, with an exam there, I’m also more nervous than usual.
I hope they can solve those licesing issues too. At the end, the Vertical is the best watch of the brand and that should be sorted, if possible. -
Last two days sleep tracking has been pretty solid. It is not 100% accurate but is definitively better as those two days I reported.
Btw. About that licensing issues, which is the problem exactly? The Race S seems to have the same algorythms as the Race has.
Thanks -
@dreamer_
Interpolate for new watches.
https://forum.suunto.com/post/131343 -
@Mff73 thanks. Very interesting that feedback. So it’s just a matter of time.
The only thing perhaps I don’t agree, is the strategy of keeping the (for now) worse algorythm just only in their best watch. I’m not sure if it’s fair for the people that bought the Vertical. But Suunto knows more those whys than us, of course.
-
@dreamer_
Read better
, maybe it is not only suunto wishes, but also some contractual constraints.
No insights here, but if a model was designed and “negociated” with certain “licensed” feature, it might be difficult to do without (legally speaking).
