the update should have solved the loading time issue. The widgets will come next up Good morning and good start of the week

@uddgren no, it is not fixed in 6.3 yet. I have not seen a fix in testing either

still wonder why the Last 7 or 30 days Time ranges are not selectable on all widget, and why the user choices aren’t stored as a setting.

Spotted a small typo error in Sleep analysis in the suunto app: [image: 1759385661986-e6de20eb-76b2-4c16-918f-caa1319a2f2e-image.png]

I mentioned this issue here app version 5.4: @Wilson75 said in 5.4.X: @Squirrel strange. I hope It will be fixed. FYI I have a similar issue with POIs I can’t delete them from SuuntoApp. I have a similar issue with POI since April 2023… reported here https://forum.suunto.com/topic/8050/pois-don-t-stay-deleted/18?_=1759147452627

@Egika und @Shrek3k Vielen Dank für den Tip und Hinweis. Ja so funktioniert es wieder. LG Enrico1705

@OutdoorMan I had the same a while ago. Well I always wondered why it was considered anerobic altough ZoneSense as well as heart-rate should consider this as aerobic or long-aerobic. Long story short: I updated the pace-zones in the watch to values that correlate and afterwards it was correct. If someone has an idea how it’s possible to control that (I’d prefer it would use the info coming from ZoneSense), it would be much appreciated

@Matteiva I’ve noticed the same with both Race S and Race. Every time a watch is paired to the app, it tries to sync all routes. Then it becomes difficult to remove routes from the watch because that repeatedly fails.

@Pietro-Ciarimboli I’ve had the same issue for the last couple of days

It’s a bug in the watch. In: Settings - Training - Intensity zones - Default HR zones… f. e. the value 145bpm is set as minimum of the Z3. (That is also showed in the app). But if You choose any activity and go to Exercise options - Intensity zones - HR zones - Set Target Zone. You’ll see, that the value 145bpm is set as the maximum of Z2 and as minimum of Z3. (I had this very same bug on Garmin FR955)

Same issue

@pumarkin it’s probably software, because 6.22 tags fine still on Android.

@Squirrel just updated to 6.2.2 stable

This works now! Not sure when it was fixed, but nice anyway