ER605 not able to assign vlan1 IP range
After upgrading to v6.0.0.34 3 days ago, the gateway refuses to assign 15 EAPs and the SG2210P switch to vlan1 192.168.0.0/24. It will only assign the client IPs to 192.168.188.0/24. I really don't know why this is happening. I do not see any other rogue dhcp servers on the same network. so it cannot adopt all the IPs under 192.168.188.xxx.
ER605 v2 firmware 2.3.0 on 192.168.0.1
OC200 latest firmware on 192.168.0.3
SG2210P latest firmware on 192.168.188.72
10 out of 15 EAP225 v3-outdoor on 192.168.188.72
5 out of 15 EAP225 v3-outdoor on 192.168.0.xxx
I would like to downgrade the back to v5 to try to resolve, but there is no option do this on omada cloud management. I do not have physical access to the network. Its a 2hr plane ride from my home. I have asked someone onsite to reset the SG2210P switch, but it still shows IP 192.168.188.x. How is this possible unless someone onsite plugged in another dhcp server to the network? I have already rebooted all network hardware multiple time.
vlan1 is very basic and nothing special. No other vlans are configured. The SG2210P switch is only used for a couple of EAPs and the controller for power, and an downlink to a POE switch for 10 other EAPs and 2 VIGI NVRs. Again nothing special. I have have asked someone to reset the SG2210P and i assume that it was correctly reset becuase the device name was changed to its MAC address. But it's IP address is still 192.168.188.xxx. At this point i'm ready to reset the this gateway.
This install is for my 10 room backpacker villa. So nothing special as far as networking requirments. I have a local ISP and starlink as backup. Can someone please assist on next step tshoot?

Caption
Caption