Widget resources

[ggrego]

Hello I received my race 2 yesterday my resource widget showed me 94 this morning after a day of work it remained at 94 I have already seen a discussion thread on this subject is it normal?

[2b2bff]

@ggrego let the watch get to know you better for two to three weeks. Then look again on that data.

[freeheeler]

@ggrego
yes please do so and let us know, because I am curious about other people’s experience

[ggrego]

After 8 days the resources are still bad I go to bed at 98 and wake up at 99 but the resource curve starts to move a little more during the day but nothing to do with my vertical 1

[ggrego]

Hello I have had my race 2 for 6 weeks now and finally the widget resources starts to go down to about 40% but as soon as I drive or other normal task the widget goes up to 88% in 2 hours of time I don’t understand why? Resting heart rate and periods at 38 bpm (minimum heart rate during the night)

[Elad Solomon]

@ggrego resources does not work for me at all, I have done 2hrs cycling workout and I am on 85 with active status.

[ggrego]

Yes it did the same for me 4h00 of walking I went down to 80% and 1h00 after I was at 90 it’s the first time after wearing the watch for 6 weeks that I went down to 40% but it goes up right away in the day

[Elad Solomon]

@ggrego gave up anyway, I stopped checking i go by feeling rather by a widget that tell me I am on 99% after 2 hrs of sleeping because my newborn decided not to sleep the whole night

[ggrego]

Apparently you have to wait 6 weeks for it to start being reliable but hey I can’t find a real explanation and no help on the suunto forum

[Elad Solomon]

@ggrego I have waited a bit more than 6 weeks, waiting from April

[ggrego]

On the suunto leaflet he advises to put the minimum heart rate of sleep as heart rate at rest I will see in the next how it evolves

[ggrego]

22:17
cardiaque pour vous assurer d’obtenir les mesures les plus précises. Par défaut, la valeur FC repos est définie sur 60 bpm et la valeur FC max est définie en fonction de votre âge.
Ces valeurs de FC peuvent être facilement modifiées dans les paramètres sous Général
» Personnel.
@ CONSEIL: Pour définir votre valeur FC repos, utilisez la mesure de fréquence cardiaque la plus basse mesurée pendant votre sommeil.
Depuis le cadran de la montre, tournez la couronne ou balayez l’écran vers le haut pour faire défiler jusqu’au widget des ressources.
16 h
85%
…
Récupération
suunto.com

[_Luki]

@ggrego said:

cardiaque pour vous assurer d’obtenir les mesures les plus précises. Par défaut, la valeur FC repos est définie sur 60 bpm et la valeur FC max est définie en fonction de votre âge.
Ces valeurs de FC peuvent être facilement modifiées dans les paramètres sous Général

Hi everyone,

I’m noticing that the Resource tracking on my Race 2 seems completely off and overly optimistic.

Yesterday: I did a heavy 36-round HIIT circuit session. Despite the high physiological load, the app recorded 0 hours of stress and 20.5 hours of recovery. The resources dropped only slightly to around 75–80% during the workout and shot right back up to nearly 90% shortly after while sitting on the couch.

Today: I woke up to 98% (Very High) resources with 10 hours of recovery and 0 hours of stress logged so far today.

It feels like the HRV stress thresholds are set way too high/insensitive, treating almost the entire day as “Recovery” and ignoring EPOC/post-workout physical stress altogether. As a result, the widget is essentially stuck between 90–99% every day, making it unusable for actual recovery and training load management.

Is anyone else experiencing this “Stuck on High” resource behavior, or is a fix planned for the upcoming firmware update?

Update with graphical proof:

Here is my 6-month resource history chart, which clearly shows when the issue started:

March – July (Suunto Race S): Realistic and dynamic resource fluctuations. After hard workouts, resources dropped properly (sometimes below 20%) and recovered naturally.

August – Present (Suunto Race 2): Exclusively after switching to the Race 2 in August, the algorithm got stuck at the top. Resources barely ever drop below 60–70%, no matter how hard the training was.

This clearly confirms it’s not a user-specific HRV baseline anomaly, but a model-specific algorithm regression/bug introduced on the Race 2.