This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have strange situation with my eap225 ap.
WiFi Scheduler, one profile, two items:
1 - custom days: monday-friday, time 08:00-16:00
2 - every day: 01:00-07:00
Both are associated with one ap. first rule works both second don't.
Why? Is it my mistake?
Hi @zikobiko,
Just a SWAG, but I would suspect that there is a bug in OMADA/SDN which is failing to process the second rule . Or if it is atempting to be processed, the evaluation heuristic is somehow causing a conflict between the two rules to be detected.
Try the following:
1) In your current off profile, swap rule #1 and rule #2. This should demonstrate the the first rule takes precedent (or is the only one being processed).
2) I'm not sure if this is possible, but see if you can create two separate profiles (e.g. off1 and off2), each with one rule, and associate both with the AP.
-Jonathan
JSchnee21 wrote
2) I'm not sure if this is possible, but see if you can create two separate profiles (e.g. off1 and off2), each with one rule, and associate both with the AP.
IIRC, there can be only one profile at a time associated with an AP. But according to the manual it's perfectly legal to add more time range items to a single profile:
Dear @zikobiko,
I tested the WiFi scheduler with EAP225 V3 Build 20200630 via EAP's web UI (tplinkeap.net) in standalone mode, it works fine.
Are you configuring the WiFi Scheduler via Omada Controller 3.xx or via EAP's web UI (tplinkeap.net) in standalone mode? Do you use Daylight saving time?
Ad 1. - via eap web ui - standalone mode.
ad 2. - yes. but system time on device information is correct. this isn't problem with dst. One time rule works properly.
Helpful: 0
Views: 880
Replies: 4
No one has voted for it yet.
We use cookies and browser activity to improve your experience, personalize content and ads, and analyze how our sites are used. For more details, please read our Privacy Policy.
