Related
Options

Instinct 2 "schedule overlap" when trying to set sleep time

7380277
over 1 year ago

If trying to set ending sleep time after 00:00 my watch says "schedule overlap" and have to choose a new ending time. For example, setting sleep from 21:00 - 00:01 is not possible. Yesterday I had the same problem and after checking my sleep data the watch had added 12 or 24 hours to the time I was sleeping. Had to remove the extra hours in GC. I fear that this will happen with all new sleep data from now on. My date and time is correct on my watch and I have tried to reboot it without solution. One clue (before I got this problem) is that I one evening when the watch was in sleep mode I changed the sleep schedule with a few hours to be awake a little longer. The watch was no longer in sleep mode after, but I could see that it still was measuring pulseOX (red light) which it is set to only do during sleep. Because of this I rebooted the device and it was no longer checking pulseOX (good). Guess I found a bug?

  • 0 over 1 year ago

    Update: For this night the watch is telling me I have slept over 34 hours. I can see that it used my detected starting point of sleep for Saturday instead of Sunday. Realize that it is not possible to edit my sleep data in GC because the classification of sleep type is different. If editing, there is no deep sleep. All of this is pretty frustrating and it is destroying the collecting of data that I am interested in following. I do not trust data of nightly hrv, resting heart rate and similar anymore. Using System Software 13.21.

  • +1 over 1 year ago

    Update 2: Sorry for having my own show here, but found a solution by my self. Maybe it can help someone else in the future so I will write what I did (Garmin still need to fix this bug). Change the sleep schedule of the current day for a short sleep of 1 or a few minutes. Do this any time before the time you want to later set as your regular sleeping start time. Let the watch sleep and when it is awake again reboot it (Not sure if reboot is necessary but I did it). Now you can go and change the sleeping schedule for the one you want to have and you can set a sleeping start time that starts before 00:00 and an ending sleep time that ends after 00:00. The watch will not say "schedule overlaps" anymore.

  • 0 over 1 year ago in reply to 7380277

    Did you find a solution? You’re having exactly the same as my issue. It tells me +24h of sleep & if I edit that sleep it doesn’t show the deep sleep data; in addition, I can’t change my sleep schedule to after 12am as it says overlap. 

    Please tell me you found a solution?

  • 0 8 months ago in reply to 4972722

    I have the same issue and I've tried all the methods I could find. I really wish they'd just let you set the times you intended to sleep.

  • 0 7 months ago in reply to 7380277

    Recently had a similar problem and fixed it in a similar way, no reboot or watch going to sleep necessary 

    Go into the settings on the watch itself, not the connect app, then system > sleep mode > schedule

    Change any day to end time 12:00 AM/00:00/0000, save, and when it asks to apply to other days, apply it to all other days

    Then change any day to start time 11:59 PM/23:59/2359, save, apply to all other days

    Now you should be able to set an end time of 12:01 AM/00:01/0001 or later, change everything to your preferred sleep end time, then change your start times

    If you're like me and have a DPSD, changing your start time to also be past midnight will now show your sleep period as being on a single day in the settings 

    Eg. 0300 - 1100 Monday, rather than 0300 - 1100 Sunday - Monday

  • 0 7 months ago in reply to Breuger

    I suspect there's a conflict between the connect app's general sleep time that you set when you make a profile in it and the individual watch's sleep time settings when you change a specific watch's settings -in the app- because the connect app profile setting does not specify a start and end day of the week, only a singular day. So the automatic conversion from profile setting to watch setting gets messed up