Time is still out of sync
I have installed the latest Windows version of the Omada Controller 4.4.3 which was supposed to address the schedule bug causing the schedule to end an hour earlier. The schedule I have should end at 10:00 PM but it end at 9:00 PM, in order to get it to run at the "correct" time I need to set the schedule to end at 11:00 PM.
I also sometimes see some failed attempts in my logs that are an hour in the future, the first two entries at 2:XX AM actually occurred at 1:XX AM. it actually hasn't pasted 2:00 AM at the time of this post.
This would also explains why my schedule ends early, the time on the EAPs are still off by 1 hour. The Site is set to use the controller time, the timezone is correct as is the DST settings.
Would it make sense to factory reset the EAPs, login to the webui and set the timezone/DST settings manually then proceed to use Omada to adopt it back?
This is definitely related to DST as I never seen this problem come up in the winter.
This is very surprising that this hasn't been fixed for a business product, client and ssid names removed for privacy reasons.