Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
Omada adoption of this TL-SG2428P switch is a real issue...I've configured this switch with a Static IP so that it properly works on my LAN. I've also set up LACP LAG between this switch and my OPNsense router. I have to do this in the switch's local UI config or there's no other way to get it onto my network. Omada insists on resetting everything to 192.168.0.1 which is odd because normally only a router/gateway on the LAN would have that IP. I don't use that IP address scheme anyway.
When I attempt to adopt this Switch, Omada COMPLETELY wipes the conifg, sets the IP to 192.168.0.1, and breaks my entire network. It erases ALL of my EXTREMELY basic configuration, which only includes a LACP LAG group in order to communicate properly with my router, and date/time settings adjusted for my time zone. Adoption completely and miserably fails.
How am I supposed to adopt this Switch to Omada if it blows away the entire switch's configuration and sets the IP to 192.168.0.1, essentially cutting it off from my network as well as my Omada Software Controller which resides on local LAN??? This is a major issue that needs to be addressed asap.
Switch updated to latest firmware, running Omada software controller v5.7.4. I have 6 other devices already adopted into Omada, including a TL-SG2210P v5.0 PoE+ switch, and 4 EAP's (EAP670 and EAP610-Outdoor). Note that 2 of the EAP's are connected directly to this switch via wire and powered by PoE, 1000Mbps full duplex.