Recovery time not working properly?
-
@ShailCaesar Unless you wear the watch it cannot calculate recovery. I doubt there is a fixed decay rate.
-
@Brad_Olwin if it says how many hours to rest I wouldn’t expect anything but a fixed rate.
-
@DMytro said in Recovery time not working properly?:
@Brad_Olwin if it says how many hours to rest I wouldn’t expect anything but a fixed rate.
It is not a fixed rate as it will monitor your HR and stress levels. For example, if you do another workout Recovery Time will increase. I am not sure how the Recovery Time behaves if it is not receiving data from the watch. It is not a simple decay calculation.
-
@Brad_Olwin so, my understanding is as follows:
You do workout - have to rest X hours
You rest for t hours, remaining recovery time is X - t
You do another workout - have to rest Y hours
Total rest time becomes X + Y - tBut I didn’t think that outside of workout there may be influences on the recovery time rate.
If this value, however, is dynamic, e.g. accounting for sleep, steps, etc - even better, but in this case having recovery measured in hours is a bit confusing in my opinion.
-
@DMytro For me it makes sense:
it’s about “rest x hours”.
it is not “wait x hours”
If I am not resting, those hours will simply not count down.Now the watch decides what “resting” is. Like below a certain HR level. If I’m working hard physically, like a builder etc. it would not count down my resting hours.
-
@Egika hm, ok, that’s fair. But does sb know if it actually works like this?
Because previously Brad mentioned that the decay rate of the recovery time may not be fixed, which I interpret as in some situations the hours may elapse quicker or slower than 60m, which seems weird to me.
But if you say, given a certain threshold, hours elapse as normal, that makes sense. -
@DMytro said in Recovery time not working properly?:
@Egika hm, ok, that’s fair. But does sb know if it actually works like this?
Because previously Brad mentioned that the decay rate of the recovery time may not be fixed, which I interpret as in some situations the hours may elapse quicker or slower than 60m, which seems weird to me.
But if you say, given a certain threshold, hours elapse as normal, that makes sense.I agree with @Egika, the watch needs information HR and likely HRV (stress) to determine count down rate. If the watch is off of the wrist I am not sure what happens. Since it does not have any data it may simply pause the countdown. Someone who knows more than I can answer. Also, I can add time to my recovery so it has to be somewhat flexible.
-
@ShailCaesar I opened a bug for this. Recovery time should drop regardless the stats. Just like on spartan or when hr is disabled.
-
@Dimitrios-Kanellopoulos Thanks for clarifying…I stand corrected:)
-
Is it correct for the recovery to reset to – if the watch is switched off? scenario as follows, I went for a run recovery stated 24hrs i had ghost notifications on the watch so i powered it off to clear them. when it powered back up the notifications were gone along with the recovery (its not returned since)
-
@minimark069 reboot don’t power off. Yes powering off shuts down all calcs. Not ideal I know.
-
@Dimitrios-Kanellopoulos I dont see a reboot option on my 9 peak pro.
-
@minimark069 Neither do I see on mine 9pp.
-
@Dimitrios-Kanellopoulos thanks it would be nice to get to the bottom of this before it wants me to rest for a whole week! I did start wearing it full time again just to see if it normalizes.
-
@skifun said in Recovery time not working properly?:
@minimark069 Neither do I see on mine 9pp.
Reset/Reboot
-
@minimark069 @skifun Upper button press for 12 sec.
-
@sartoric Thanks, didn’t know that rest=reboot. Isn’t the reset option only for when you need to clear a problem?
-
@Brad_Olwin awesome I didn’t realise.
-
@Brad_Olwin it resets some stuff but didn’t clear out the recovery time
-
@ShailCaesar said in Recovery time not working properly?:
@Brad_Olwin it resets some stuff but didn’t clear out the recovery time
Right but maybe it will countdown properly now. if not, this could be a bug.
-