Schedule changes made in a row now all stick.
Fixed
- Setting a day's start and then its end could put the old start back. The time entities send both bounds of the window and read the other one from the last poll, so a script or an automation that set the start and then the end of the same day, or two quick edits in the UI, sent the previous start back to Microsoft. The integration now updates its own copy of the schedule as soon as Microsoft accepts a change, for the daily limit as for the time window.
Changed
set_screentime_intervalsacceptsend_hour: 24(withend_minute: 0) for a window that runs until midnight. Before, the end was capped at 23 and midnight could not be written through the service.
Tip for scripts: set_screentime_limit plus set_screentime_intervals per day writes both bounds in one request and is the most reliable way to apply a whole week.