Related

No stress data - night shown as active..

wojtek_b
5 days ago

Last night no stress data was calculated at all. Previous night it was ok, but this night shown as active…

  • 0 2 days ago

    i got the same today. All previous nights were getting it recorded just fine

    For this night I am also missing breathing rate - also was recorded fine for previous nights.

  • 0 2 days ago

    to get better view I also tried to export data using API and what I can see is that at around 23:30 when I probably fall asleep, the stress is recorded but very low numbers I have never had before - like around 2-8 all over my sleep duration. Similar is for breathing rate.

    It is clearly visible on attached screen.

  • 0 1 day ago

    This night the problem repeated. But i was able to see where it happens. 
    I had my watch on power save mode and was wearing ISM during night. 

    after i woke up i synced ISM with Garmin Connect. Stress data were visible in the app. Then i put on the watch disabled battery saver mode. Once it synced watch, the stress disappeared from night data and was only showing active. Stress over night is also not visible in garmin watch widget. So whatever happens it looks like the watch overwrites stress data even though the could no record any

  • 0 1 day ago in reply to emX0R

    You mention putting the watch into battery saver mode, does this disable Bluetooth?

    I don't do anything special to my watch, I just take it off and leave it on my bedside. So it will go into the same bedtime mode which it goes into when I wear it to bed, Bluetooth, HR sensor is active (although the lights are not flashing).

    I noticed in the morning when the data is synced that both devices (Fenix 7 & ISM) sync a couple of times. It might look a bit like this, ISM sync - Fenix 7 sync - ISM sync - Fenix 7 sync.

    I haven't had any issues with stress, sleep or body battery data showing in the app or on the watch. So in your case perhaps disable the battery saver mode and see if things work then. 

    The only issue I've had in the whole few weeks of using this is the other day when I took the ISM off, it didn't seem to go "to sleep" and the HR leds were flashing against the arm band. Anyway when my watch synced later in the day I had around 300 active cals added instantly. After a bit of investigating I noticed that the ISM was still syncing, and when I went to check it out this is when I noticed the LEDs still flashing. Funnily enough the HR data for this period is from my watch, but it seems to have combined the active calories from both devices. 

  • 0 1 day ago in reply to Nate_G

    Thanks. Yes battery saver mode disables also BT. I was trying before without battery saver and it was same. Some people were reporting if battery saver mode is not enabled on the watch then during some events watch can “wake up” and start overwriting the sleep monitor data so that was the reason i was trying with battery saver past night

  • 0 1 day ago in reply to emX0R

    Ok I see. 

    Yes there certainly seems to be some teething issues with the way data is handled.

    It should be simple enough really. Any sleep data synced from the ISM should be the primary data. If no sleep data from the ISM then it can use the secondary data from the watch.

    It would appear in Garmins efforts to "restrict" the ISM (can't wear it with the watch, doesn't collect steps when you visit the bathroom during the night etc) they may have introduced added complexity in how the data is handled between devices.

  • 0 1 day ago

    I just had this exact issue ie shows as active, no stress data, no respiration data. Don't think there was any difference between last night and the night before. Both watch and phone on charge overnight...

  • 0 1 day ago in reply to RosieG1979

    In my case it happened once as the watch was charged… maybe its the issue?

  • 0 1 day ago in reply to wojtek_b

    I don't know, but there is definitely a software issue. The watch data should never overwrite data recorded by the sleep monitor if it exists. I'll give it another try tonight, and if I encounter the same problem, I'll stop using it until this is sorted out, as it interferes with all the statistics.