Bug in Omada Software 5.9.9 For Force AP Lock
trying the Force AP Lock doesnt really work
if you set it to say a Certain AP on a device and then you click reconnect button in the Omada.. it will still conect to the other AP even with the one chosen to lock is 2 feet away from the device
rebooting omada software the devices, the eaps, removing the 2nd eap to force it onto renamed eap.. doesnt help if you remove the 2nd eap thats not 2 feet away.. so it forces to connect to the renamed one.. but when you re add the 2nd eap650 and if you if the device disconnects or reboot it it will jump back to the other EAP not the one is forced... i havent tried uninstalling and re install the program.. . as i dont see a Factory Reset the Omada Software.. to delete it so all i know is uninstall delete all exisit content and re install just to be able to Factory Reset it
another bug is if you happen to lock aps with a certain AP but after you decide to rename the AP from the mac address of the EAP650s so you can read it better... the locks are still of the old Name so when you rename an AP it doesnt rename all locations of that Address.. and then it jumps to the next AP..
so
example
11-11-11-11 if thats the AP and you have linked 30 devices to 11-11-11-11
and if you decide to rename 11-11-11-11 to AP1 all 30 devices are still pointed to 11-11-11-11 and jumps to the next AP
it will not goto AP1 so if you rename 11-11-11-11 to AP1 then 30 devices Force Locked AP should also be renamed from 11-11-11-11 to AP1
and a FEATURE REQUEST... be a button to Enable Omada Software to be Enabled as a Windows Service and setup Firewall rules.. the pain of doing it with the nssm and then setting up Firewall rules to get it to work... be nice just a Check Box to enable and Disable it as a Windows Server