DHCP bug on tapo C320ws h
DHCP bug on tapo C320ws h
when I choose advanced settings >> network settings and deactivate the static IP choice there and click save, the camera after reboot stays always with static IP enable if I have choose in my rooter static IP lease. The problem is that it assigns static IP on the camera level and not on router level so in case of IP conflict the camera is not accessible. The correct behaviour would be to remember and respect the user choice of no static IP at the camera level. The camera should then request an IP from the DHCP server of the local network and if the user wants a static lease at the router level so it be.
This persistence with static IP on the camera level sometimes but not always remain or changed erattically even without reboot. So I chose NOT static IP on advanced settings >> network settings and after a while (from minutes to hours) I found again the toggle button enabled for static IP.
Someone has to seriously review the code there guys 😕
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
Do you mean the operation to disable the Static IP feature does not work properly on the Tapo C320WS? If so, please confirm:
1. The model number of your router. Have you enabled the feature such as address reservation on the router?
2. Is the camera connected to a NVR/PC/NAS via RTSP/ONVIF?
3. Ensure the Tapo app is up to date.
Best Regards
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
Is the static IP address feature enabled automatically on the Tapo app after something happens? For example, reboot the camera, reboot the router, etc.
Or the static IP address feature will be enabled randomly after disabling it.
Best Regards
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
I have reported the issue to the tech team, and they will likely reach out to you via email to continue troubleshooting your issue. Please check your email box and confirm.
Best Regards
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
1. Yes, I have sent them the link to this thread for reference, they may want to learn more about the usage scenario and network environment when the problem occurs.
2. Generally, we will try to reproduce the problem, but due to the various of customer usage scenarios and network environments, we may not be able to reproduce the problem successfully. Therefore, your cooperation is appreciated in providing the log when the problem occurs in a specific scenario for further analysis. You can inform the tech team of your situation by email, and they will continue to help you handle the case.
Best Regards
- Copy Link
- Report Inappropriate Content
Hi,
I have 2 C320WS affected by the same problem. I configured out of the box to get dynamically an IP (my router's dhcp assign them a fixed IP).
Never watched this setting in the app, but they always showed issues in the router config page. Despite the router couldn't detect them, as if they were powered off, the cams worked perfectly, so I didn't think of resolving the issue.
I then found this post on the forum and went into the app and found that the cams had fixed ip configured with the parameters they took from router's DHCP only on the first configuration. I disabled this setting on both, the router finally detected them. After a couple hours the fixed ip setting is on again.
So this is definitely a bug. both the cam are on firmware v.1.1.15 that is the newest.
Please fix it soon
- Copy Link
- Report Inappropriate Content
Hi,
Is the camera connected to a third-party app via RTSP/Onvif connection?
If so, can you disconnect the RTSP/Onvif connection and then check if you can disable the Static IP option successfully on the Tapo app? If the problem remains, factory reset and reconfigure the camera for a try.
Best Regards
- Copy Link
- Report Inappropriate Content
Mikrotik RB5009 with DHCP server on it
Mikrotik cAPax connected to the RB5009 to which the cameras are connected to via wifi
Other TP-LINK cameras (2x C210, 1x C110, 1x C310) connected the same way have no issues
The issue happened even when I used 3x Deco M4 connected to the RB5009 instead of the cAPax
the two C320WS ar the only devices out of 30 doing this
I already factory reset twice one of them. Same issue
clearly there is no third part device interacting with the cameras that would be able to force the firmware to enable again something has been disable using the only way possible to disable it (the app). If it could be possibile, well you have a big security issue to solve first.
Open the code and fix it please
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 559
Replies: 17
Voters 1
