At one time approximately a year ago, Schedule Rules failed when the Start Time and End Time were on different days (e.g., Start at 2300 and End at 0600). That was corrected, I presume, in the Wyze servers that control Schedule Rules. For some time now Schedule Rules that span two adjacent days have been working, until 0600 23 May 2020 for me. My primary Schedule Rule was to turn ON a Plug Group at 2300 and OFF at 0600. The Start time of 2300 worked on 22 May but the End time (0600 the next day) was not executed. But now one day later, this identical Schedule Rule did work as it has in the past, sort of – the Plug Group was turned ON at 2313 instead of 2300, but it did turn the Group OFF at 0600. So, its partially fixed.
In my case, something happened between 0600 22 May 2020 and 0600 23 May that caused a failure. But, as of today, this Schedule Rule appears to work properly.
Here is a temporary solution I implemented. The primary Schedule Rule (ON at 2300, OFF at 0600) is left intact. I added a secondary Schedule Rule that turns the Group ON at 2301 with no End Time, and a tertiary Schedule Rule that turns the Group OFF at 0601, again with no End Time. Yeah, this is very redundant however only temporary; but if any action on the primary Schedule Rule fails (either ON fails or OFF fails, or both ON and OFF fail), then the secondary and tertiary Schedule Rules, which do not span two successive calendar days should/may be effective and provide the intended outcome. By the way, these temporary Schedule Rules can remain programmed in the App but not enabled, effectively putting them on pause without deleting them.