Detection is not working on Tapo/Kasa Camera

Tapo C325WB , KC420WS , Tapo C110 , Tapo C320WS , Tapo C210 , Tapo C310 , KC310S2 , KC411S , KC120 , KC100 , KC200 , KC300 , KC125 , KC400 , KC401 , KC105 , Tapo C200P2 , Tapo C420S2 , Tapo C201 , Tapo C202 , Tapo C100 , Tapo C200 , Tapo C420 , Tapo C101 , KC300S3 , KC300S2 , KC110 , KC310 , KC410S , KC411 , KC115
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
The detection feature in a camera is a capability that allows it to identify and capture changes in the environment, such as a person walking by, a vehicle passing, or any alteration within its field of view. Once motion is detected, the camera can trigger various actions based on your settings, such as sending an alert/notification, recording video footage, etc.
There are two main detection types. The first employs pixel changes and AI motion algorithms to detect motion, primarily used by most cameras powered through an adapter. The second type, known as PIR motion sensors, activates alerts by sensing body heat and infrared energy. Battery-powered cameras often integrate an additional motion sensor, which, upon detecting a change in heat, activates the camera and further utilizes AI algorithms for recognition.
The detection issue is usually associated with the installation and configuration of the camera, involving the sensitivity settings within the app and the configuration of detection areas. If the detection feature is not set up correctly in the app, it may not function as intended. Nevertheless, other factors, such as the camera's installation location, height, and facing angle, can also contribute to this issue.
This article will guide you on how to troubleshoot when the detection feature does not work on non-battery models.
Note: If your camera is a battery model, please refer to the FAQ to troubleshoot: What should I do if my battery-powered camera can't detect the motion?
1. Confirm that the camera’s firmware and the Tapo/Kasa app are both up-to-date.
Please go to the APP Store and Google Play to upgrade the app to the latest version, and please refer to the following FAQ for upgrading the camera firmware: How to update the firmware of the Tapo&Kasa devices on the Tapo App.
2. Ensure the Detection Types and Sensitivity are enabled as desired.
Here, we take Tapo C210 as an example. Go to the camera’s Live View page > Device Settings > Detection, and enable the detection types as desired.
Note: different camera models have different detection types.
3. Adjust the suitable Detection Zones.
Here, we take Tapo C210 as an example. Go to the camera’s Live View page > Device Settings > Detection > Detection Zones, and set suitable zones.
If there is no detection zone setting included in the detection type, the activity zone is the full Live View screen.
4. Avoid placing the camera towards glasses.
The camera may face issues such as glare and infrared light reflection at night if it is aimed at glass surfaces. This can lead to ambiguous images, which may cause inaccurate detection or even non-detection of events, as the camera relies on algorithms that identify changes in pixel data to recognize events.
If you have finished all the above steps but the problem still persists, please contact TP-Link support for further troubleshooting.
Related FAQs
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.

TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or