@APRC-P3-Tel, I see. Anyway, UNIX/Linux is very stable (all EAPs and OC200 run Linux), system uptimes of several months are no exception and if excluding planned reboots due to kernel/OS updates,...

@APRC-P3-Tel, why would you want to reboot APs and OC200 each day? We run EAPs and Omada Controller without a scheduled reboot for years now, only restarted after a firmware update. For example, one...

Hi @elmado, great that you found a workaround. Maybe in a future version of Omada Controller TP-Link will hopefully remove the platform dependency of Omada Controller, so that a native version of the...

GCisco wrote Issue fixed after changing the switch ports to tagging instead of untagging, however i kept the upstream Firewall as untagged, thanks for your reply. Ok, then it probably was this bug...

GCisco wrote 1. Are the EAPs getting valid IP addresses from DHCP Server and showing as Connected on the Controller? YES 2. If you configure the valid static IP on your wireless clients after...

@biomed32uk, just tested this with Omada Controller 3.2.4: Adopted an EAP225, changed device name to »Test EAP«, transferred some data: Then forgot the EAP: Device statistics are gone: