I just had another look into this, and I did spot an issue where getPressure could end up leaving the Barometer on if it got just one bad value, which it seems could in some cases cause this behaviour.
I did try adding a reset as you did (but in the firmware) but it wasn't quite that simple - I think I may have to leave some delay to allow the reset to take effect.
I've fixed the issue above though, so if you try a cutting edge firmware now it may fix it
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I just had another look into this, and I did spot an issue where
getPressure
could end up leaving the Barometer on if it got just one bad value, which it seems could in some cases cause this behaviour.I did try adding a reset as you did (but in the firmware) but it wasn't quite that simple - I think I may have to leave some delay to allow the reset to take effect.
I've fixed the issue above though, so if you try a cutting edge firmware now it may fix it