Note that my sleep mode is set to start at 12am and ends at 8am, and has since I started using the VENU 3 in July 2024.
Sleep tracking is deciding that I’ve woken up around 6am for several mornings in a row now and stops tracking at that time without my intervention.
Yesterday I slept in until 9am. My body battery continued climbing at the same pace as the rest of the night. Despite this, sleep tracking stopped at 6am. There was nothing remarkable about my heart rate, HRV, or stress level at the moment it decided I was awake. The first detection of me being ‘active’ happened quite awhile after it decided I was awake.
Today it was the same thing but the start was also off. I fell asleep at 11pm. If I fall asleep early, it always seems to catch this but it didn’t. Sleep mode triggers at midnight but tracking didn’t start until 1:16am and then stopped at 5:58am, despite the fact that I slept until 10am. Same as other nights, my body battery continued to climb(recharge) at the same rate until I actually woke up. There was nothing remarkable about my heart rate, HRV, or stress level at the time it decided I was awake. The first section of being ‘active’ happened 4 hours after it decided I was awake.
This VENU 3 is my second Garmin smart watch and since I started using it has been a wildly significant improvement in all ways over the VivoActive4 but especially with sleep tracking accuracy. Until now.
I have worn it nearly 24/7 since July 2024, and make a point of sleeping with it on every night. I clean it regularly, and ensure its fit properly above my wrist bone and not too loose or too tight. I do switch wrists occasionally (to let them rest given the 24/7 use) but always switch this setting in the profile. This problem doesn’t coincide with me switching wrists recently.
This is the first major issue with accuracy I’ve encountered. What’s the best course of action? I have the impression that Support won’t be of much help.
The only “remarkable” thing that happened before this started was that I slept without the watch for one night (the first in months) before this issue started.
There may have been a software update a few days ago but I can’t be sure.
EDIT: The only other change in the last few days is that I’ve suddenly been a lot more active. Over the last three days I’ve walked 7km, 5km, and 12km. Prior to this it was rare that I walked more than a couple of kilometres a day during the winter months.
Depending on how the models are trained, I wonder if any deviation from what could otherwise being considered ‘routine’ has the risk of throwing off accurate detection.