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

Venu 2 HRM green flashing won’t stop after 16.11 update

After the 16.11 update a few hours ago, I noticed 2 things. 
First, just as with some previous firmware updates that required later patches, my Venu 2’s heart rate monitor (HRM) that has previously been purposefully turned off by me in Settings, and is still set to off, but after the update to 16.11, the green flashing sensor under the watch is constantly running when it sees a surface (skin, tabletop, etc.). 
Normally, if I had the HRM turned on, the green flashing would flash for a second then go solid when it sees skin. 
With this buggy state in the off position since the update, the green flashing is constant flashing when it sees a surface, and it never goes solid until I turn on the HRM in Settings. And it doesn’t go off when I turn off the HRM. 
I DO NOT want the HRM on. I do not want the green flashing sensor to constantly run when the HRM is off. I do not want the green flashing at all as it drains the battery. 
Garmin, PLEASE turn off the unnecessary green flashing sensor as it’s killing my battery life. I stress that this bad buggy behavior started after the 16.11 update a few hours ago. 
(And, yes, I have tried hard powering off the watch numerous times. I’ve tried turning on and off the HRM. This same problem happened on at least 1 other previous update this past year, and it took another update to patch it.)

Second, I noticed (as another post has mentioned) the watch takes longer to charge since the 16.11 update. I’m actually fine with the phone taking longer to charge as long as Garmin fixes the green flashing sensor that is running down my battery even though the HRM is off in Settings.

Thank You Kindly for Your Consideration 

EDIT: My Venu 2 watch updated this morning (15 November 2023) to version 17.04 with an additional update to Sensor Hub: 27.16. There is now no unwanted green flashing sensor. This issue appears to be fixed. Thank you to the Garmin engineers for resolving that annoying problem.