Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Time in zones - is completely broken connect android / web and on my Forerunner 235

HugoHouyez
over 2 years ago

Hi everyone,

I don't understand how is that possible that my time in zone is completely messed up (this happen every single time i save a run)

Example today with screen : 

- #1 avg bpm + max bpm during my run => /resized-image/__size/320x240/__key/communityserver-discussions-components-files/92/8738.screen1.png

- #2 time in zone completely broken with >254 bpm (impossible) => /resized-image/__size/320x240/__key/communityserver-discussions-components-files/92/screen2.png

- #3 setting of my zones (default one cause i already tried to reset my forunner) on my watch => /resized-image/__size/320x240/__key/communityserver-discussions-components-files/92/7178.screen3.png

How do i fix that ?

  • 0 over 2 years ago

    The screenshots are not really well readable, but it looks indeed strange. If you could post a link to the concerned activity, it may perhaps help finding the culprit better.

  • 0 over 2 years ago in reply to HugoHouyez

    No, I cannot, the activity is private. You have to set the privacy level of this specific activity to Everyone (click the padlock icon on that page)

  • 0 over 2 years ago in reply to trux

    Done, sorry rarely open activities to public

  • 0 over 2 years ago in reply to HugoHouyez

    The HRZ table on the activity page is completely broken: Z2 & Z4 lower limits are 1 beat higher than the upper limits!!! And Z3 is 111 beat wide!. Possibly coming for the continuous (and apparently buggy) adjustment of the HR-Reserve based HRZ to the ever changing Resting HR and Max HR values.

    First of all, I'd reset the zone table, and would also choose a different base - either BPM for a fixed table, or the LTHR base, which is generally the best choice. You should then conduct the Guided Lactate Threshold test, though. Also make sure you are looking at the right HRZ table - on many watches there are up to 4 different HRZ tables available (general, running, cycling, and swimming).

    In any case, it looks like a bug of the algorithm adjusting the table limits (and it is not the first time I see it), so I'd suggest reporting it to the Support anyway.