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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I looks like that way. I have a support case open with Tapo camera support.
- Copy Link
- Report Inappropriate Content
@Virgo Tapo support has come back. There is an issue in camera firmware. If it's ever controlled by onvif software, it wouldn't release dynamic IP. I used iSpy for a little short while and that seemed related to the issue. Likely Tapo team will need more investigation and patch this issue.
- Copy Link
- Report Inappropriate Content
Turn off Tapo and write down your Tapo MAC. Clear the binding and reboot the router and controller and let the router reboot its services. After the boot of the controller and router, fill in the MAC address and desired IP. Boot up the Tapo.
- Copy Link
- Report Inappropriate Content
@Virgo thanks for the quick reply. I will give it a try.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Virgo I tried your tip last night and it didn't work. I end up had to reset camera from Tapo APP then re added them to the network. Luckily I could completed most of work in the mobile phone without physically pressing reset button in each camera. Here were the steps I took
1) To do so, I had to temporarily move the subnet back to the original IP range (192.168.53.1/24) so the camera back online and showed up in App.
2) in Tapo APP, I removed camera one by one, this trigger camera reset. (Funny thing, these camera still showed in Omada client list for as long as 30 min before next step).
3) in Omada, I moved the subnet back to the desired new IP range (10.10.53.1/24)
4) reactivate cameras and add them back to Tapo APP
5) I verify that now cameras are in expected subnet with reserved DHCP ip addresses.
This is a painful process because it causes all rest smart devices in IoT SSID off line.
With this process, I really couldn't tell what the problem was. Was it a bug in DHCP / router / other Omada networking devices or simply just the problem of Tapo cameras.
- Copy Link
- Report Inappropriate Content
I'm leaning toward it being a Tapo product issue.
"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.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."
If it is the omada issue, must occur on all IoT devices.
- Copy Link
- Report Inappropriate Content
I looks like that way. I have a support case open with Tapo camera support.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Virgo Tapo support has come back. There is an issue in camera firmware. If it's ever controlled by onvif software, it wouldn't release dynamic IP. I used iSpy for a little short while and that seemed related to the issue. Likely Tapo team will need more investigation and patch this issue.
- Copy Link
- Report Inappropriate Content
Have they released a fix yet?
I have a C120 that I was just needed to track down because it hasn't done a DHCP Request (to renew) in the last 16 days. So the lease and hostname are long expired.
It's firmware is currently up-to-date 1.1.12 Build 240117 (so Jan 17 2024?)
Rebooting/power cycling doesn't help. Never tries any DHCP again. So the camera now behaves like it it has a static IP assignment.
- Copy Link
- Report Inappropriate Content
I haven't seen a release yet. This is the response from support when I raised to them
"We currently found that the device will not follow the DHCP to get a new IP after control through Onvif, this issue needs to be further confirmed with the R&D team, please wait a little longer."
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 376
Replies: 10
Voters 0
No one has voted for it yet.