Hi, I love the product and am still learning all the tricks and best practices. I believe I’ve got everything set up. When looking at WiFi/Schedule/Turn off - it shows the incorrect time:
Under System/Timezone it’s set to America/New_York.
I tried setting it to another Timezone, and it still shows the same thing.
I tried rebooting/restarting the router10 with the same result.
Have others run into this?
TY
Sorry for the confusion, but the Now marker will always be in the local time zone of your browser, not necessarily the time zone of the site.
Hi, If i wanted to use the Schedule Turn off, and the time is incorrect, it wouldn’t work. Or am I missing something.
The time on the Access Points themselves will use the configured site time, and they will disallow access when the scheduled time arrives.
is the System/Timezone the configured site time? If not, can you please elaborate on where the setting is? TY
Yes, that is the site time zone.
If that is true, the correct time is not showing on the Schedule screen—I believe it was working before the latest update. Is there any way to change the time zone via command line?
This functionality hasn’t ever changed, that I know of. We have just improved the schedule display to show Now in the site’s time zone, though.
weird, it’s showing the correct time now. I haven’t changed a thing.
We pushed a release yesterday that uses the site’s time zone on the Schedule display.
Sorry for the dumb question, but does scheduling actually turn off or do any power saving on the AP’s?
@user31 Inasmuch as clients are generally unable to connect, the power consumption would go down due to the lower network utilization. However, the AP continues to run and transmit beacons during off-periods, to allow users to request access during down-time. If you want to save power completely, you would need to turn off POE on the AP’s port.
Would it be possible to schedule the POE On/Off to get that effect?
@ebuckland81 It’s definitely something we are considering, but there are other considerations like when channel planning and firmware updates occur, as well.
I believe this one is now solved through updates according to release notes for Control (cloud and On-premises):
