Feature request: Disable Sleep Schedule

The problem is, this is meant to be detecting sleep, so it isnt working. If we all have to program in exact times when we might be asleep, then it isnt detecting sleep, it's just being told when to start and end :/ 

This is my problem with sleep trackers, they advertise as this amazing thing, when in reality it is close to a timer app 

I think you misunderstood.

The schedule is more for the watch face to turn into sleep mode. Or you are telling Garmin my sleep window is around the timings in schedule.

As I mentioned above, even through your watch face turns into sleep mode, the actual sleep time is automatically detected.

Put sleep schedule from 10pm to 6am. Go for a run at 10pm. I am very sure your actual sleep will not start from 10pm because Garmin detects you are not sleeping yet.

No I do understand, and the extreme of going for a run will be easy for the watch, but as someone who can be sat down and it tells me i'm asleep...yeah setting the times doesnt work unless i go to sleep exactly the second i say I will, which to me doesnt count as detection

Because when you sit down, you are still and with low HR, the watch cannot differentiate between sleep and sit. It doesn't have eyes to see you.

This is the whole problem though. It is advertised as a SLEEP detector. If they sold it as a sit down detector then I couldnt have issue with it. 

If it works for you then great, but it clearly doesnt for other people, and the company doesnt need defending for flaws in major aspects of its products. Like if the sleep thing doesnt work, that effects every aspect of training and recovery so :/ bit rubbish innit

I recently migrated from a 245 to a 265. I like most things about the upgrade - but these forced sleep schedule is such an impediment that I would have bought a different watch had I known I couldn't disable it.

I have a highly erratic work schedule - night sleep, day sleep, multiple shorter sleep periods, naps... some days I don't sleep at all. I don't care to use the sleep features of my watch but, if I did, I'd be happy to start/stop sleep mode manually.

The practical problems with this forced, automatic sleep schedule are twofold:

1. If I manually start sleep mode and the automatic sleep schedule ends while I'm still sleeping, my watch makes noise / vibrations when notifications arrive
2. If I'm awake and working when Garmin forces sleep mode to start on a schedule, I miss notifications

Regarding #1, the watch should at least respect my manual setting - if I explicitly start sleep mode, it should never automatically end it. The only way around this at the moment is to edit the sleep schedule itself, with its requisite dozen+ clicks, when I go to bed. That's ridiculous.

With respect to #2, I have the sleep schedule set to be 1 minute long. I've only had this watch for a few weeks and there have been multiple occasions on which I've missed important incoming notifications because they happened to coincide with this forced sleep mode schedule. I keep fiddling with the schedule in hopes of finding a time when I can safely miss messages, but there is none.

The net effect is that the 265 is less reliable for me than the 245 was - I can't reliably stay asleep because the watch automatically ends sleep mode (i.e. enables notifications) while I'm in bed, and I can't reliably receive notifications when I'm awake because Garmin forces me to start sleep mode on a schedule.

Garmin, please just let us turn the schedule off. We know our own use cases best.

You can take it in and out of sleep mode, but i think that mainly serves the purpose of turning on the do not disturb setting, as well as changing the watchface appearance 

The sad bit is that even when not wanting to use the sleep features, if you wear it to sleep in, the dara is used to calculate everything else. Meaning training readiness, and body battery, and recovery, and anything else that is to do with recovery is ruined on the watch because it is miscalculating it because of the sleep inaccuracies. 

It really is a bigger problem than some people seem to think :/