Software update 2.30.32
-
I noticed something “new” today. Straight after waking up, my total sleep was shown by the watch as ~6,5 hours (0:15 - 06:45). This was afterwards synced and visible on my phone. After a while this was “corrected” to ~8,5 hours (0:15 - 08:45). The latter corresponds exactly with my actual sleep. No unreasonable awake time was visible anymore either. So it looks like the watch reevaluates the sleep after a while and corrects it after a new synchronisation.
-
@wmichi Yes I am on the same firmware as you. I will post this to the test site and see how we should proceed. It may require you all send logs but I will put this up. Clearly something that is reasonably prevalent is going on.
Never mind, I see that @Dimitrios-Kanellopoulos already commented on this. I am in the US so I miss a lot happening while I am sleeping. We should be able to figure out what is happening and get a solution going.
-
@Brad_Olwin Thanks! I wonder if it works generally for everyone in the US and here in Europe we all have the same problem. Maybe related to the timezone the user is in. Or related to daylight saving time… either way, I can provide logs at any time
I switched today before noon to S9PP (with newest firmware) and did a hard reset. After setting the watch up again, all the training stats have been correct. Then I did a 30min core workout, synced with the app and to my surprise, the values on the watch are still in line with the values in the app. With the Race this was never correct, even on the latest firmware. I am already curios what the watch displays tomorrow morning
-
@Theo-Lakerveld I saw the same on my Race. Right after waking up it only showed 5 hours sleep, 30min later the values have been corrected automatically (spot on),
-
@wmichi this is exactly the experience I had with the Race on the first day after the new update. App and watch was in sync both before and after a workout on the first day after updating the firmware. After midnight the Race and app got out of sync and new workouts were not properly reflected in the watch anymore,
So check your SPP after midnight today (or should I actually write tomorrow ) and see if app and SPP are still in agreement!
-
@Mads-Hintz-Madsen I will report back Who knows, maybe the hard reset did the trick.
-
@wmichi now the app shows 6,5 hours again while the watch shows 8.5. Seems that some adjusting still needs to be done at the sync algorithm.
-
@Mads-Hintz-Madsen The watch must have a full sync before you check. I have noticed that my watch does not necessarily sync when I wake up. I have to open the app and make sure the watch syncs. Sometimes the CTL values don’t sync the first time but require two syncs, this happens when I change watches. I tested today with a Vertical I have not used in awhile and after two syncs with SA the values match. I don’t think it has anything to do with time of day or time zone.
-
@Brad_Olwin trust me, I have done multiple syncs every day both before and after workouts! The issue is really real (for some of us at least)
BTW, I’m not sure what communication channels you have with Suunto developers but do you know if they have problems reproducing this issue?
-
Well, I now have a polar vantage v3 and I like it more than the suunto race. It’s about the fact that I don’t have any bugs. In appearance, model Race are generally nicer, but otherwise for men, when I scroll through the menu, do a leg regeneration test, let myself be guided by the workouts recommended by the watch or even the polar flow application itself, everything is better. unfortunately.
-
@Dimitrios-Kanellopoulos good morning!
My step counter is again stuck at 12 steps this morning. There is nothing I know I can do besides restarting the Race.
It seems to not be related to charging - I did not charge it this morning.
Any other hint from your side on how to reactivate the step and calories counter without restart??
-
@Olaf-Gottschalk good morning. Could you please send logs and private message me your Suunto app account email ?
Send logs via app - profile - settings - all the way down send logs to Suunto. (Android )
Then I can have this escalated and see if we can find a temporary solution or if it’s HW.
-
@Olaf-Gottschalk did the ohr work during when the step counter was stuck ?.
-
@Dimitrios-Kanellopoulos @Brad_Olwin
Hi, once more how this other bug ctl/atl/tsb/tss sync worked here in Finland between yesterday and today (text below is exactly the same I have written before, because the watch and the app works like this every day, with last software and the new one, tested once more, I have also pictures / screenshots of this happening if someone wants, also I can send you the logs of needed)
Yesterday evening: watch and app ctl, atl, tsb all synced and all good
Just after midnight and synced with app: new numbers for todays ctl, atl and tsb. All synced perfectly with the watch and the app.
This morning after synced with the app: ctl, atl, tsb are not synced anymore. On the app still todays numbers like it should. On the watch back to yesterdays numbers. And those wont be corrected on the watch before powering off and back on. After that works fine for today and also possible new tss scores add fine. If the power off and on is not done, also the new tss scores don’t show up.
I use ios, I don’t have multiple watches.
So once more I ask: is this sync problem also reported / someone is doing something finding a solution for this? Or do you even think this is a problem? Thank you
-
@SuuntoR Im my case (location Slovenia, it that matters at all) TSB, CTL, ATL are not syncing properly with the app. Values are different, not much, but they differ! I belive the correct one are on the watch itself. It’s a bug in my case!
-
@ppresing OT: Is that the Mangart in the background of your profile picture?
-
@robis Oh Yeeees!
-
@ppresing been there last year, made a ride on Visoska Ponca, Jalovec, Mangart. Awesome place!!!
-
@SuuntoR said in Software update 2.30.32:
@Dimitrios-Kanellopoulos @Brad_Olwin
So once more I ask: is this sync problem also reported / someone is doing something finding a solution for this? Or do you even think this is a problem? Thank youIs this Problem reported and will be solved next 2 years?
-
@GiPFELKiND next 3 years for sure.