Video Doorbell Rings Locally but Only One Phone Receives the Call

Symptoms

The physical chime sounds and one phone is notified while a second household phone stays silent. This guide addresses that particular contrast, not every fault that can occur with the product or service.

• Observable failure: The physical chime sounds and one phone is notified while a second household phone stays silent.
• Control test: Compare alert permissions and account notification preferences for both phones.
• A confirmed correction must meet this outcome: Both authorized phones receive a test ring without duplicate alerts.

A "connected" indicator usually reports one portion of the process, not end-to-end success. Keep the service, device and user-visible outcome separate in your observations.

Why It Happens

A video stream, a cloud acknowledgment and a physical door release represent different subsystems. Access credentials, egress safety and residents' permissions take precedence over convenience changes.

Treat the problem as three testable possibilities rather than assuming the product is broken: phone notification channel disabled, shared-user notifications off, or background battery restriction. The order matters because the least disruptive test should come first.

Three competing explanations

1. Phone notification channel disabled.
2. Shared-user notifications off.
3. Background battery restriction.

These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports phone notification channel disabled does not automatically exclude shared-user notifications off; the comparison needs to separate them.

Before Making Changes

Protect legitimate emergency entry and fire egress. Change permissions only through the authorized owner or building administrator. Do not expose home entry video or guest lists in support logs.

Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.

Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.

Problem-Specific Diagnosis

Run this discriminating test before restarting or resetting the entire system: Compare alert permissions and account notification preferences for both phones. Compare the observed result against the three paths below.

Now apply the least-disruptive change that corresponds to the evidence: Enable the specific doorbell calling notification on the affected phone. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.

Solution Checklist

Common Mistakes to Avoid

• Assuming phone notification channel disabled is proven simply because the visible symptom matches this page.
• Changing multiple accounts, rules, connections or device settings before running the control: Compare alert permissions and account notification preferences for both phones.
• Skipping this safety boundary: Do not expose home entry video or guest lists in support logs.
• Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.

A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.

How to Verify the Fix

The primary pass condition is specific: Both authorized phones receive a test ring without duplicate alerts. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.

• Record the before-and-after state in the same location, account and operating mode.
• Repeat the original comparison: Compare alert permissions and account notification preferences for both phones.
• Check the stated pass result: Both authorized phones receive a test ring without duplicate alerts.
• Confirm that normal security, notification, storage or physical safety protections remain enabled.

If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.

If the Problem Continues

If the safe correction does not work, move to a focused deeper investigation: Inspect push token registration and account invitations, restoring only affected session. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.

When escalating to the device owner, building manager or access-control service provider, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether phone notification channel disabled, shared-user notifications off and background battery restriction were supported or contradicted by evidence.

Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.

Prevent Recurrence

Keep a short reference note with the working configuration and the successful check: Both authorized phones receive a test ring without duplicate alerts. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.

Watch for the condition that originally made the failure visible: The physical chime sounds and one phone is notified while a second household phone stays silent. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.

FAQ

How can I tell whether phone notification channel disabled is responsible?

Run the controlled comparison: Compare alert permissions and account notification preferences for both phones. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.

What if the real cause is shared-user notifications off rather than phone notification channel disabled?

Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect push token registration and account invitations, restoring only affected session. Keep the earlier working configuration recorded so you can reverse the test.

When is this particular issue resolved?

The decisive result is: Both authorized phones receive a test ring without duplicate alerts. If it fails after the normal workflow is repeated, document whether background battery restriction still explains the remaining behavior and escalate with non-sensitive observations.