Tapo baby cry detection not working or giving false alarms? What's going on and what to do

Which Tapo cameras have baby crying detection?

TP-Link's sound detection FAQ lists the indoor models: Tapo C100, C101, C103, C104, C200, C200P2, C201, C202, C206, C207, C210, C212, C216, C21A, C220, C222, C225, C230, C232, C236 and the TC60 to TC74 series. The C110 is sold as a camera "with Baby Crying Detection" too. Not every model hears every sound: "Some specific models support all types of Sound Detection. Other indoor Tapo cameras support Baby Crying Detection only."

The detection runs on the camera and costs nothing. Tapo Care, the paid subscription, adds cloud clips and notifications with a snapshot; it does not change whether the camera hears a cry. You turn the feature on under Device Settings → Detection → Sound Detection (or Baby Crying Detection), where the sensitivity lives too, next to TP-Link's note that for beta detection types "accuracy may vary and false triggers may occur."

If the camera isn't by the crib yet, the Tapo camera as a baby monitor guide covers placement and the Camera Account. This page is for when it is set up and misbehaving.

What to check when Tapo cry detection misses cries or alerts late

Steps 1, 4 and 5 are about the camera hearing the cry; steps 2, 3 and 6 about the alert reaching you.

1. Check the detection and its sensitivity. Open the camera → Device Settings → Detection → Baby Crying Detection and make sure it is on. TP-Link's advice: missed cries, raise the sensitivity; false alarms, lower it. No setting does both, so expect to nudge it a couple of times in the first week.
2. Check the notification chain inside the Tapo app. The camera's Notifications toggle must be on. Under Me → Notifications there is a schedule: set to Custom Time, cries outside the window are silently dropped. The app has its own Do Not Disturb schedule as well.
3. Let the Tapo app live in the background. TP-Link's page on delayed notifications names Android battery optimization as the usual cause: exempt the Tapo app, add it to "never sleeping apps" on Samsung, allow autostart on Xiaomi and Huawei, lock it in the recents list. Google Play services must run, since the push arrives through Google. On iPhone, check Settings → Notifications → Tapo and any Focus mode.
4. Update the firmware and the app. C225 V2 owners reported that the camera "started not to detect baby crying" after firmware 1.1.0; TP-Link's pinned thread says 1.1.1 "optimized the Baby Crying Detection performance." An update is the first thing to rule out.
5. Move the camera closer and unblock the microphone. TP-Link's troubleshooting page recommends 1.5–4 feet (0.5–1.2 m) from the baby, a clean mic hole and a higher microphone volume in the camera settings. A white noise machine next to the camera or a closed door between camera and crib works against you.
6. Make sure the camera has internet, not just Wi-Fi. TP-Link's knowledge base: you can watch the live view locally without internet, but "Notification or any other service associated with the TP-Link Cloud will not work if there is no internet access." A router that is up while the line to your provider is down delivers no alerts. The C200 uses 2.4 GHz only; a weak signal to the nursery delays alerts too.
7. Test it on purpose. Play a recording of a crying baby at the crib for 15–20 seconds and time the alert. Within half a minute: the chain works and you are tuning sensitivity. Nothing: back to steps 2 and 6.

Why does a detector on the camera misfire?

None of this is specific to TP-Link. A cry detector in an inexpensive camera has a small processor, one microphone a few feet from the crib, and a rule that turns sound into a single yes-or-no event.

• Loudness and classification are different jobs. Noticing a loud sound is easy; deciding it was a cry rather than a laugh, a cough or a sibling next door is the hard part. Higher sensitivity catches quieter cries and more laughs; lower drops the laughs and some cries. Owners describe both at once: a C225 that hears "baby laughing from another room" yet misses real cries, a C200 that "sometimes works really well" and other times sends nothing after several loud cries.
• It needs a stretch of crying before it commits. One owner estimated the C225 wanted "at least 10 seconds." Short cries with pauses may never cross that line; one long wail does. Not broken, just a threshold you can't see.
• Every event is the same notification, with no difference between a whimper and a real cry. It then crosses TP-Link's cloud, Google's or Apple's push service and your phone's battery rules; each hop adds seconds, or on a strict Android, minutes.

Keep the camera, let the phone listen

The other way around an on-camera detector is to let something with more processing power listen: your phone. Mamoon connects to the same Tapo camera over your home Wi-Fi (it needs the Camera Account, like any RTSP app) and shows its picture and sound, night vision included. The cry detection runs on the phone, and no audio leaves it.

• Three levels instead of one slider: "Only crying", "Crying and fussing" (default) or "Every sound". A dog, a door, the TV or voices show as Stirring, not as crying.
• Fast: Mamoon alerts within seconds of the first cry, and the room's state on screen is always Calm, Stirring or Crying.
• Alerts with the nursery sound muted and the screen locked, no cloud in between, and an alert if the camera stops sending video. If you use Do Not Disturb, allow Mamoon in that mode so it can make noise.
• A morning overview: the night on one timeline with a frame from every sound.

Frequently asked questions