Kasa Camera's KC 100/200 stop detecting motion and recording after Kasa App Update - UPDATE SOLVED
Wifi Router Archer A10 Hardware Archer A10 v1 00000000 Firmware 1.0.2 0.9.1 v1000.0 Build 190305 Rel.62969n(5553)
2x Kasa KC 100 Spot Hardware Version 2 Firmware Version 2.3.0
2x Kasa KC 200 Hardware Version 1 Firmware Version 2.2.36
Kasa App Version 2.22 Buld 794
I have been having issues with my cameras detecting motion and recording since the last Kasa App update ~2 weeks ago. The only way i have found to fix this is rebooting the A10 which lasts for only a few hours before i get issues again. I have reset and reconfigure the cameras and power cycled all hardware including the A10, seems that the Kasa App has caused a bug somewhere. I have even tried a different channel on the 2.4GHz wifi
Please investigate
UPDATE - IP V6 was the cause of the issue. IP V6 was diabled in the TP Link Archer A10. Seems the camera's would get a IP V6 DNS entry and could not resolve the TP Link servers. Quite wierd as this worked for months without an issue
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello,
Except for the Kasa app update, is there any other change in your network, such as firmware update on the A10?
How about the LEDs on the Kasa cameras when the modem detection or recording has an issue? Please try to change the DNS setting on the A10 to 8.8.8.8, then reboot both the A10 and cameras.
Is the internet on the A10 always working fine on other devices?
- Copy Link
- Report Inappropriate Content
Hi Brook
for context this issue only started after the app update, no firmware change on anything
so what i tried today is:
i returned and replaced the A10 today to see if that made any difference but no the issues still remains
I deleted the cameras and did a full reset on them, re added them into the app and they started to detect motion again then a few hours latter stopped recording motion. The LED indicates solid green so a connection to TP Link is fine.
i have changed wifi channels as well from auto to 8 to 11 no change
if i reboot the A10 and the cameras start working recording motion again
as I mentioned above, everything was working perfectly until the app update
- Copy Link
- Report Inappropriate Content
Hi, thanks for the details again.
From what I may understand, there might be a DNS resolution issue between the camera and the cloud server, it is suggested to change the WAN DNS server on the A10 to 8.8.8.8 to give it a go.
BTW, may I have more details on how is the detection or recording not working? Do you mean it just cannot trigger a detection or you cannot watch the recording? Is there any error message?
- Copy Link
- Report Inappropriate Content
Hi Brook, i am sort failing to see why changing the WAN DNS to 8.8.8.8 will help? Given the fact that all was working perfectly untill the app update and all devices that are connected to the WLAN network are able to browse the internet. As the A10 has a DHCP lease update of 120mins i would expect the issue should arise more frequently.
Can you please explain why changing to a DNS of 8.8.8.8 will help (just curious)
Currently the DNS is set to the IP adress of the A10, i have also tried using my ISP's DNS servers as well to no effect
The issue up to the point of failure is if i move infront of the camera, the camera in the Devices list in the Kasa App would show "activity detected less than 1 min ago" on the camera.
When the issue arises i move infront of the camera, the camera in the Devices list is the Kasa App would show "activity detected (what ever time the previous detection was when the motion detection was working) min/hour ago" on the camera. The video when the camera did detect activity is fine and has recorded correctly.
- Copy Link
- Report Inappropriate Content
Hi Brook
Tonight i did notice that the LED's on the KC100's were flashing green indicating that the camerea's lost connection to the cloud, the KC200's took a while before they started flashing and as per usual they stopped motion detection. This has not always been the case
When you mean change the WAN DNS to 8.8.8.8 you mean on the DHCP server? Because i have no control of the WAN interface as my ISP assigns all that via my bridged VHDSL modem.
I have changed my DHCP server Primary and Secondary DNS to Primary 8.8.8.8 and Secondary to 8.8.4.4 as per the google DNS server addresses and will trial this. Cameras are back capturing motion again at this point
I still think this is all wierd as the camerea have been working perfectly without a hickup and the only thing that has changed is the Kasa App Version
Please read and comment on what you mean by the WAN DNS
- Copy Link
- Report Inappropriate Content
Hi Brook
This issue has once again happened tonight, all the camera's are now using 8.8.8.8 DNS and were rebooted along with the A10, now i am absolutly certain that the App update has caused a bug that shows its self after a while.
I can confirm that the LED's on the camera's are a solid green indicating they are connected to the cloud while this issue is occuring
The A10 has no access control or MAC filtering set up on it. The App has been installed on an IPhone 6s Plus
This issue needs to be investigated further by TP Link, i need these camera's for security, if the issue cannot be resolved i will have no choice but to return the A10 and the 4 camera's to place of purchase for a refund
- Copy Link
- Report Inappropriate Content
Bump
- Copy Link
- Report Inappropriate Content
Brook, this issue is still happening even after the latest app update to 2.23. I wish you people would seem interested in actaully helping, i am getting really tired of this, i have a support case setup for this and no one is replying. I will just keep creating post so that this issue gets attention if thats what i need to do
- Copy Link
- Report Inappropriate Content
This is becoming tire some. i have never seen such disregard for issues by TP link, 4 weeks this has been happening. I am not going to go away and will just keep reposting this every day
- Copy Link
- Report Inappropriate Content
Hello, terribly sorry to respond late.
I find you have already raised a ticket which has been followed up by our engineers, please reply them directly and they will surely investigate it.
Thanks.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1884
Replies: 10
Voters 0
No one has voted for it yet.