KeexyBox's forum
Schedule does not seem to be working - Printable Version

+- KeexyBox's forum (https://forum.keexybox.org)
+-- Forum: Connection settings (https://forum.keexybox.org/Forum-Connection-settings)
+--- Forum: Profiles (https://forum.keexybox.org/Forum-Profiles)
+--- Thread: Schedule does not seem to be working (/Thread-Schedule-does-not-seem-to-be-working)



Schedule does not seem to be working - rdavila - 01-09-2023

Hello everyone,

I created a Profile with a schedule to only allow connections to the Internet during certain times of the day. I can see the Device is using the correct Profile, but I can still access the Internet on that Device outside of the Scheduled Time.

Below are the details of the Schedule configuration. (please see the attached file "Schedule Screenshot.jpg" for a screenshot of the schedule)
The goal is to allow access to the Internet only during the following times:
  • Monday through Thursday - 6:00pm to 7:00pm
  • Friday -  3:00pm to 10:00pm
  • Saturday - 12:00pm to 8:00pm
As a test, I browsed to a website today Monday at 1:25pm, which is outside of the Schedule, and I was able to access the Internet.
(please see the attached file "Access Log Screenshot.jpg" for a screenshot of the Access Log page)

If I click on the little "Eye Icon" in the Access Log page, it takes me to the Connection Information page for that Device, which confirms the correct Profile is being assigned.
(please see attached "Connection Information screenshot.jpg)

Any ideas of what I might be doing wrong?

Thanks in advance!


RE: Schedule does not seem to be working - rdavila - 01-11-2023

Well...
After playing around a lot with all the settings, I think I figured out what the issue was.
After assigning (or changing) a Profile to a Device, you must Reconnect that Device.
I did not see that mentioned in the documentation. Actually the Connect/Disconnect/Reconnect terms are not really explained very well in the documentation I think :-)

It seems the Connect/Reconnect action applies any new settings for the Device.

Anyway, if I find that this was not in fact the issue I will post it here, but I hope this helps anyone out there with the same issue.