ZoneSense bug

[Mirek_R]

@cosme-costa I used two apps in same time. I will use ZoneSense only and will see if this helps. If not then uninstall/install ZoneSense. I realy care because I think it could be very helpful. Thanks for sugestions.

[SuuntoR]

@Mirek_R or is it just this https://forum.suunto.com/post/154320 and will be fixed hopefully soon…

[Mff73]

@Mirek_R
Same bug today for me.
Climb S+ app in parallel to ZoneSense.
Gauges (circle and bar) stucked in anaerobic zone, but timers were counting “correctly” as per my feeling, and correct results are displayed in app after.

Vo2Max zone timer increasing but still orange tooth and circle

Aerobic timer increasing

[Mirek_R]

@SuuntoR Indeed, it looks the same. Another values “on fly” and another after synchonization. Let’s see if update will solve it.

[Mirek_R]

@Mff73 I see there is topic ZoneSense - maybe moderator could move our posts there? I had same issue. It means it is not coincident. @Brad_Olwin

[halajos]

@Mff73 my findings here: https://forum.suunto.com/post/154454

[far-blue]

I suspect there’s a chance the SuuntoPlus app is going to be using the data from the last sync as the basis for it’s live analysis because the watch might not have the computational power to crunch the full numbers directly. So I’d guess there’s a chance while it is learning about you that the suuntoplus app will be a bit out of whack for a few activities. Syncing with the phone app would allow the data to be re-analysed and then the suuntoplus app would be updated with better reference data for you for next time.

Just a thought.

[Mff73]

@far-blue
In the case of this bug, computation on the watch seems exactely the same as in app after sync (looking at times in zones). Just the display seems frozen in terms of graphics.

[The_77]

Another with a ZoneSense bug - stuck on calibrating after ten minutes, so no pointer and display looked off. Was using that, Burner and a route.

Interestingly, at the end I switched to breadcrumb and it resolved the issue.

/edit from 27.9

Different bug today, using it in conjunction with a route and S+ Pace loops - it wasn’t stuck on calibrating this time, but rather showed no time in zones, and didn’t want to show a value for NGP.

[Mff73]

Too many posts about zonesense, I continue here for this bug (not related to race S as I have a SV).
Run with only S+ ZoneSense yesterday (removing climb app) and nothing was stuck. Tends to prove, like others, a relation between ZS and other apps in parallel.