Yesterday evening my watch updated to the latest firmware, 20.29. This morning I checked an it didn't record my sleep hours (I went to bed about 3hrs after the update).
Has anyone else noticed a similar issue?
Best regards,
Yesterday evening my watch updated to the latest firmware, 20.29. This morning I checked an it didn't record my sleep hours (I went to bed about 3hrs after the update).
Has anyone else noticed a similar issue?
Best regards,
Same here , last two snaps were not recorded. Also there was no REM during sleep
20.29 missed a >90 minute nap this afternoon. Naps not always recorded if short but longer ones usually are. Will check sleep tonight.
I had the exact same issue last night. Updated around 6pm and went to bed 4 hours later. No sleep data or heart beat recorded since the update. On to of that the battery drained from 11d to 5d during that…
Same issue. I'll add that after update, HRV has also gone mad.
Waiting for a fix.
Sleep and nap tracking has gone off the rails with this latest patch. If I wake up in the middle of the night, my garmin 965 (same as 955 but with amoled screen) will think I'm up for the day even though I go right back to sleep. Also, this AM, I noticed that the watch says I took a nap about 15 minutes ago for about 8 minutes when I was clearly up grocery shopping. (Guess I was sleeping in the cold case without realizing it ;). Hope Garmin reads forums. Since Garmin's training readiness calculation relies heavily on the body battery concept, it loses its value as a training advisor if they don't fix this.
Ich habe auch das Problem. Update am 21 September installiert. Dann keine Schlafdaten und keine HFV über Nacht. Habe mit dem Support gechattet, ein paar Einstellungen vorgenommen, hat aber nix geholfen. Jetzt mal abwarten.
But obviously the error is just for some.
I was on 20.26 and am on 20.29 now and sleep data and HRV are ok.
Just wanted to let you know, there have to be some special circumstances to trigger the error.
Do you know what mistakes they are?
No, sorry.
If I knew, I would tell the Garmin engineers so they could fix it.
This seems to be one of the ever repeating Garmin update mysteries, where after the update some users are effected by strange errors, while for others with the exact same firmware this error just does not exist.