5.83 Beta Issue - Barometer Mode

Former Member
Former Member
Since the 5.83 Beta, the watch in barometer mode generates random changes in elevation and barometric readings. This issue had been fixed in the last beta.
  • Message unclear. Are you saying the issue was fixed with 5.83 beta, or that it still exists with 5.83 beta?
  • Former Member
    0 Former Member over 7 years ago
    Sorry if unclear. The issue has re-emerged with 5.83 Beta. The instability was an issue until recently. It was fixed I believe two updates back. It has now returned with 5.83. Sudden, unpredictable changes in elevation/barometric pressure with auto calibration off and watch in barometer mode. Elevation should remain unchanged when manually set in this mode.
  • Ah, got'cha. Introduced with 5.83 is the ability to calibrate the barometer, whereas prior to 5.83 only the altimeter could be calibrated.

    Is the issue you're seeing only when in an activity, or when not in an activity? I haven't used barometer mode and I believe auto calibration of altimeter with GPS only fires up at the beginning of an activity.

    Maybe someone with more knowledge of the interaction will step in.
  • Former Member
    0 Former Member over 7 years ago
    Okay thanks for responding. I did just go into barometer calibration and set the sea level according to my own WX station, a Davis Vantage Vue. The pressure agreed with the elevation I had just manually calibrated. This issue has arisen when not in an activity. I will monitor over the next day and report, trying to see if any events trigger this behavior. I use this function to monitor weather and do not record much in the way of activities other than on a hike track.
  • Next time before reporting, double check. You ll economy a lot of Your and our time.
  • Former Member
    0 Former Member over 7 years ago
    Thank you for responding. I reported because I did double and triple check. The issue is real. I have verified all settings are correct and the new barometer setting ability is unrelated to this issue.
  • Former Member
    0 Former Member over 7 years ago
    This issue appears to have been resolved in the Beta 5.84 release!