Related

Fenix 7s stops tracing stress through the night

Sarah138
2 days ago

Sporadically over the past month, my Fenix 7s stops tracking stress through the night. It varies from between midnight and around 2am. It tracks some nights no issues and then some nights it stops. 

I can't remember what day it updated firmware, but a couple of days ago I updated to 20.12 (on Beta programme) hoping it would fix it. I don't know how to downgrade to last known official release to test this but since the upgrade, tracking has stopped consistently every night on 20.12.

HRV tracking is fine. If I remove the watch on wake up, and activate the sensor, it tracks again or I can reboot the watch to restore it. 

I have done a soft reset but didn't make a difference. Am concerned it's a bug. 

  • 0 2 days ago

    When you open the Stress widget directly on your watch, is the stress data there for the concerned time, or is it missing there too? If it is there, while missing on Garmin Connect, then the data transfer failed during syncing. The Device Sync Audit (at the bottom of the Settings menu on the app) could perhaps reveal some clues about the reason of the failure.

    To exclude any BT connectivity issues, you can try disabling Bluetooth on the watch for the night, during a couple of the next days, and syncing the data over the USB cable in the morning. Another possible reason of gaps in some data is the date and time on the watch not matching the time on the phone. And also Removing and Adding the Device From the Garmin Connect App may fix some issues of missing data, though I think it is not the case here. Worth of trying anyway. 

  • 0 1 day ago in reply to trux

    Hi

    Thanks. You have helped me here and I'm very grateful. 

    The stress widget has recorded the data so that helps me rule out a fault with the watch. 

    I've checked the audit file and for last night, it syncs at 1:18 all fine then at 6:58 when I wake, the sync fails - this corresponds to the missing data in Connect.

    I did remove the device at the weekend, which doesn't seem to make any difference. 

    Time and date seems to match but I can send this log to Garmin to see if they can work it out. 

    Much appreciated.

    Here's the log file in question 

    ---Timestamp---

    Tue, Jan 21 2025 @ 6:59 AM

    ---Sync Info---

    ******************** SYNC STARTED: AUTOMATIC_STANDARD *******************

    ******************** SYNC RESULT: AUTOMATIC_STANDARD: fenix 7S/90:F1:57:D4:CC:51 ********************

    Overall Sync Status=SUCCESS

    IsConnected=true

    GCUploadAgent=Uploadable=[FIT_TYPE_71, FIT_TYPE_70, FIT_TYPE_73, FIT_TYPE_72, GPSData, FIT_TYPE_52, FIT_TYPE_74, KPI, FIT_TYPE_77, FIT_TYPE_32, FIT_TYPE_35, FIT_TYPE_57, FIT_TYPE_79, FIT_TYPE_58, FIT_TYPE_38, FIT_TYPE_9, FitnessHistory, IQErrorReports, GOLF_SCORECARD, BACKUP_SUPPLEMENTARY, FIT_TYPE_61, ErrorShutdownReports, FIT_TYPE_41, FIT_TYPE_44, FIT_TYPE_66, FIT_TYPE_68, BACKUP_PRIMARY, FIT_TYPE_28, FIT_TYPE_49, FIT_TYPE_4, BLELogs, ACTIVITY_GCPD, ULFLogs, WELLNESS_TYPE_1]

    Total Files=5: VisibleFailures=0

    UPLOAD: FIT_TYPE_68/1246B: ARCHIVED - 41f1f9b0-0000-0176-0100-0000000004de

    UPLOAD: BIOMETRIC(44)/1219B: ARCHIVED - 41f1f9b0-0000-0173-0100-0000000004c3

    UPLOAD: MONITORING_B(32)/17559B: ARCHIVED - DEVICE_UNKNOWN_ITEM: Read failed: Provided id doesn't exist  - 41f1f9b0-0000-0171-0100-000000004497

    UPLOAD: MONITORING_B(32)/549B: ARCHIVED - 41f1f9b0-0000-0171-0100-000000000225

    UPLOAD: SLEEP_DATA(49)/824B: ARCHIVED - 41f1f9b0-0000-0177-0100-000000000338

    ****** ***********************************************

  • 0 1 day ago in reply to Sarah138

    Yes, there seems to be a problem with he monitoring data (which indeed includes the stress too). Hopefully the following line could help the Support:

    "UPLOAD: MONITORING_B(32)/17559B: ARCHIVED - DEVICE_UNKNOWN_ITEM: Read failed: Provided id doesn't exist  - 41f1f9b0-0000-0171-0100-000000004497" 

  • 0 1 day ago in reply to trux

    Exactly what I was thinking. Thank you!