“The connection was gone” is not enough for diagnosis. It helps to separate the cases: no session starts, only sound or video is missing, the drop happens during a network change, or the app status is unclear. That makes troubleshooting much calmer.
Diagnosis flow
From symptom to likely cause
No session starts
Look first at pairing, Wi-Fi, permissions, and local access rather than assuming a server-side fault.
The session later drops
Battery optimization, background rules, and network changes are often the real cause.
Only sound or video is missing
That often points to media permissions or role-specific access rather than a total connection failure.
Status is unclear
If parents cannot tell whether the app is reconnecting or fully disconnected, the interface itself is part of the problem.
The most common cause often sits in the role logic
Many connection problems start because a device is no longer consistently acting as the baby or parent device. The nursery phone gets used for something else, the screen locks, a permission was denied earlier, or the app ends up inside the manufacturer’s power-saving logic. Parents experience this as “unstable Wi-Fi,” even though the device role was interrupted.
Android devices in particular handle background apps very differently by manufacturer. If you use an old phone as the baby device, remove obvious sources of trouble first: battery optimization, notifications from other apps, changing network profiles and everyday use for other tasks.
| Symptom | Common cause | First useful test |
|---|---|---|
| No session can be created | Pairing, permissions, network access, or device role issue | Restart both devices and try again on the same network |
| Sound is missing | Microphone permission, muted device, blocked microphone | Test the microphone outside the app once |
| Video is missing | Camera was not granted or is intentionally disabled | Enable video separately and check camera access |
| The session drops later | Battery optimization, background restrictions, network change | Review power settings and screen/background behavior |
Routers and network paths matter, but not first
NAT, hotel Wi-Fi, device isolation and weak connections can cause real problems. If an app is meant to work over the internet and not only locally, these topics matter. Still, the simple checks come first: permissions, roles, battery, power supply and current network state.
Support pages from established products often follow that order: check the device first, then the app, then the network, and only afterwards special cases.
The order that keeps troubleshooting calm
check roles, permissions, and same-network behavior before rebooting the whole home router.
check background and power behavior first, because that is often the hidden cause.
treat media access as a separate layer rather than declaring the whole connection broken.
The best protection against night stress is a test run
You should not learn a baby monitor for the first time during a real failure. Test once how the app looks when everything is fine, how reconnecting is shown, and how a true disconnect appears. Then a message at night is not a mystery.
That sounds basic, but it helps. If you know the failure patterns, you stop jumping between ten explanations and check the likely causes one after another.
Five-minute troubleshooting checklist
- Keep the baby and parent devices in clear, stable roles.
- Check microphone, camera, and local permissions separately.
- Review battery optimization and background restrictions.
- Repeat one test on the same Wi-Fi before judging special network conditions.
- Learn what each connection-state label in the app really means.
Sources and further reading
- Wifi Connected Family Product Support · Safety 1st
- Dormi — Baby Monitor for Android · Dormi
- Getting started with WebRTC · WebRTC
- Request app permissions · Android Developers
- NSLocalNetworkUsageDescription · Apple Developer Documentation
- Requesting access to protected resources · Apple Developer Documentation
- MediaDevices: getUserMedia() · MDN Web Docs
- Babyphone Timmy security and architecture · Babyphone Timmy