Video Doorbell Not Sending Notifications? A Step-by-Step Check
You press the doorbell, see a visitor on the indoor screen, but your phone stays quiet. That result does not automatically mean the camera is offline. The doorbell response, event recording, internet connection and phone notification are separate parts of the setup. Testing each part helps you find where the chain stops.
This guide uses the Bextgoo 2K peephole doorbell, whose current listing specifies 2.4GHz Wi-Fi and Smart Life or Tuya app access. Menu names depend on the app and phone version; follow the instructions supplied with your exact unit when pairing or changing device settings.
Test a button press before testing motion
Choose a normal moment when another person can help. Note the time, then have them press the button once. Record three results: what happens on the indoor unit, whether a corresponding event is visible in the app, and whether the phone displays a notification. Allow the normal response time before repeating; rapid button pressing makes individual events harder to match.
Then test ordinary movement separately, if motion detection is enabled. A physical button press and a detected-motion event are different triggers. Success with one does not prove that the other is enabled or configured as you intended.
On a phone, scroll the table sideways to see all columns.
| Observed result | What to check next |
|---|---|
| The indoor unit does not respond as expected | Power, charging and the installation instructions before phone settings. |
| The indoor response works, but remote live view fails | The doorbell's Wi-Fi connection, home internet and the phone's internet. |
| Live view works, but no matching event appears | The correct device, event type, detection configuration and any schedules offered in the app. |
| A matching event appears, but the phone stays quiet | App message settings, phone notification permission, alert style and Focus or Do Not Disturb. |
These are starting points for diagnosis, not proof that a particular component is faulty. Keep the original test time so you can compare the same event across the screen, app and phone.
Check the connection with the door closed
The Bextgoo 2K peephole doorbell uses 2.4GHz Wi-Fi; a 5GHz-only network is not supported. Check the intended router network during setup, then test in the final position with the door closed. The conditions during pairing beside a router may differ from those at the installed door.
Try opening live view from your phone over mobile data. That checks the remote path instead of only proving that the phone is on the home's local network. If it fails, confirm the phone itself has internet access and whether the doorbell is shown online. Make one change at a time; avoid a factory reset before recording the current settings and symptoms.
Check app settings before changing the whole phone
Confirm you are looking at the correct device in the intended Smart Life or Tuya account. Review the device's available event and message settings. If it provides a detection schedule, alert toggle or a quiet period, compare those settings with the time of the missed event. Do not assume every firmware version offers the same controls.
Check each household member's phone separately. Access to a shared camera and permission to display notifications are not the same setting. One person receiving an alert does not establish that another phone is configured identically.
Then check the phone's notification controls
On iPhone: open Settings, then Notifications, and review the camera app's permission and alert style. Sound and visible alerts can be configured separately. Also check whether a Focus setting is suppressing the app during your test. Apple's guides cover notification settings and Do Not Disturb and Focus.
On Android: review the app under the phone's notification settings and any notification categories the app provides. An alert may be set to silent rather than blocked. Google notes that the available settings vary by device in its Android notification guide. If alerts arrive only after opening the app, also consult your phone manufacturer's guidance on background activity and battery restrictions for that app.
Keep permissions proportionate to the feature you need. You do not have to expose message previews on the lock screen to everyone nearby just to check whether notifications arrive.
Repeat the test as you normally use the phone
- Restore the phone's normal internet connection and leave the app in its usual background state.
- Lock the phone and repeat one doorbell-button test.
- Match the new event's time with the app's event record and phone notification.
- If motion alerts matter, repeat one ordinary movement test separately.
- Repeat on a second authorised phone only if you need to distinguish a device-wide issue from one phone's settings.
If you observe a delay, record the approximate delay rather than calling it instantaneous or completely broken. Local Wi-Fi, internet service, app delivery and phone settings can affect the path; one test cannot identify the cause on its own.
Keep alerts, footage and purchase decisions separate
A missing notification does not by itself prove no footage was recorded. Equally, an alert does not prove that a recording was saved successfully. Check playback independently using the local-versus-cloud storage guide. Buying cloud storage should not be treated as a general fix for phone notification permissions.
If the issue persists, send Bextgoo support your model, app and phone versions, the test time, the error wording and which stages worked. Keep account passwords and pairing codes private. If you are still choosing a doorbell, compare peephole and exterior-mounted designs: the right door fit, indoor screen and practical network connection matter alongside headline resolution.
By Bextgoo. Product details checked against the current listings on 25 September 2026. Images are product illustrations; the checks and filming exercises in this guide are suggested routines, not claimed hands-on test results.