sleep tracking not working after most recent update
-
My watch software was updated earlier this week. The night of the update, I had 53 minutes of sleep tracked - it looks like it stopped tracking at the time of the update.
Have confirmed that all settings are correct, sleep tracking enabled, 24/7 HR monitoring, sleep hours set. Had changed none of these myself.
Have restarted watch and phone.
The last time this happened, I needed to restore a prior firmware version in order to get it working. That was a while back (months, maybe a year ago).
Very frustrating - anyone else seen this pop up recently? Any success?
-
If the sleep tracking stop was matched with the OHR measurement stop, i.e., no led blinking, you’re not alone.
-
I bought the Suunto 9 Peak Pro 1 week ago, and it also happened to me tonight. The HR sensor stopped working, no data, no blinking, and the HR view showed “measuring” continuously. A reset enabled it again, and it works now. I have the latest software, 2.48.16.
Suunto customer service told me that a reset is the only solution for now, and if more people report the problem, a future Firmware update could fix it. But if a 1-week-old watch has that problem, it is known and already reported issue, and it has not been fixed since months, I’d better return it… Or do you have any tricks or solutions for it? How often does it happen?
-
@Jaxdu this should not be occurring anymore. I will inquire about it and test my S9PP as well.
-
@Jaxdu, this issue persecuted my watch for a very loong time, firmware after firmware; then, with the “old” firmware 2.40.44, the issue seemed to be solved.
However, with all the firmware releases between 2.40.44 and 2.48.16, the issue came back, so I always downgraded the watch to 2.40.44.
Now, actually for the last 2 weeks, my watch is running with firmware 2.48.16 without problems (

).Once I’ve installed the latest firmware, I’ve only proceed with a watch soft reset, as usually suggested: give it a try!
-
@Matúš Thank you very much! And let’s see, I will continue testing and communicate if the issue occurs again. I read about those issues, also that Sunnto messed up and had to revert some updates or introduced the issue again… But your message clarifies the full history a lot, better than reading different old discussions without clear conclusions (and much better than the info from the official chat/service department).