Tapo C325 Cameras get stuck in old DHCP ip and Omada Controller can't refresh their IP addresses
I have a very annoying DHCP problem in Omada solution. here is the network config.
- ER605 V3 router
- Netgear L2 managed switch
- Omada Controller 5.13
- EAP245 x 3
there are 2 SSID, each on its own VLAN.
main vlan1: 10.10.0.1/24
IoT vlan53: 10.10.53.1/24.
The IoT vlan used to be in sub net 192.168.53.1/24 and set up DHCP to assign dynamic IPs to all IoT devices. recently, I decided to update the IoT subnet to 10.10.53.1/24 and applied reserved DHCP address to IoT devices including 30+ smart devices ( 10~TP link smart plugs, 5~ Wemo switches, 4 Eufy cameras and 4 Tapo cameras). After the subnet change was successfully deployed to the router. All IoT devices, excep Tapo Camera, receive their respective reserved IP and get online. However, those Tapo cameras are stuck in their old 192.168.53.x IP and don't move to the new subnets.
I have tried everything I can think of including steps below
1) reboot router, APs
2) unplug camera, and replug in.
However, none of the attempts worked. now Tapo cameras (mounted outside to the wall) are all offline. It would take quite a bit of efforts to unmount and reset the camera as they are outdoor devices. (it's -15 degree in my area outside).
I read some posts in this community in regards to the DHCP issue in ER router. the DHCP issue was supposed to fix in latest firmware back in 2022. I confirm that my ER605 has been in the latest firmware (2.2.3 Build 20231201 Rel.32918).
Does everyone have thoughts how to resolve this weird problem.