Managing DoorBird Push Notifications: Multiple Call Buttons, Custom Sounds & Motion Alerts

Push notifications are how most people actually experience their DoorBird system day to day — a ring alert while you're at work, a motion ping while you're in another room. Getting notifications tuned correctly means understanding that they're controlled in three separate places: on the device itself, inside the app, and at the operating system level on your phone. Mixing those up is the most common reason a notification setting doesn't seem to "stick."

Notifications for Multiple Call Buttons

On a device with more than one call button — common at multi-tenant entrances, gated properties, or homes with a separate button for a gate and a front door — each button can generally be configured to notify a different person or group rather than sending every ring to everyone. This mapping between a specific button and its notification recipients is a device-side setting, configured in the outdoor station's Administration settings, and it typically requires the installer-level admin credentials to change rather than just app-level account access.

• Confirm each call button is associated with the correct resident, unit, or user account before relying on it — a misconfigured button will either notify the wrong person or notify no one.
• If a household or building has recently added or removed a resident, that button-to-user mapping is the first place to check when notifications seem to be going to the wrong phone.

Choosing a Custom Ring Notification Sound

Being able to tell a DoorBird ring apart from every other app's notification by sound alone is genuinely useful, but exactly how you set a custom sound depends on your phone's platform rather than a single universal app setting:

• On iOS, custom notification sounds are generally chosen from within the app's own notification settings for that device, since iOS lets individual apps bundle and offer their own alert tones.
• On Android, ring notifications are typically tied to a notification channel that the app creates, and the sound for that channel is usually set through your phone's system-level notification settings for the app rather than inside the app itself — this is standard Android behavior for any app targeting recent Android versions, not something unique to DoorBird.

If a custom sound you selected stops playing after a phone or app update, it's worth reopening that notification channel or setting and reselecting it, since OS updates occasionally reset per-app sound preferences.

Turning Off Motion Notifications Without Losing Ring Alerts

Ring events and motion events are treated as separate notification types in the app, which means you can subscribe to one without the other. This is an app-level setting — found in the notification preferences for that device within the app itself — rather than something that requires admin access to the device.

• Open the notification settings for the specific device you want to adjust, since these preferences are typically set per device rather than globally for the whole account.
• Look for separate toggles or entries for ring events and motion events, and disable only the motion entry while leaving the ring entry enabled.
• It's worth being explicit about what this does and doesn't change: turning off motion notifications stops the push alert from arriving on your phone, but it does not disable motion detection itself. If your plan includes motion-triggered recording or cloud event history, those events will typically still be captured and viewable in the app's history — you simply won't be interrupted by a push alert every time it happens.

If Ring Notifications Stop Arriving

When ring alerts that used to work suddenly stop, the cause is usually on the phone rather than the device or the app's internal settings. Check these before assuming something is misconfigured in the app:

• Notification permission — confirm the app still has permission to send notifications at all; this can be revoked by an OS update or a manual settings change without you noticing.
• Do Not Disturb or Focus modes — a scheduled Do Not Disturb window or a Focus mode that only allows certain apps through will silently suppress alerts that are otherwise working correctly.
• Battery optimization — on Android in particular, aggressive battery optimization settings can prevent an app from receiving push notifications reliably while it's not actively open, since the OS may restrict its background activity.
• A stale app session — if the app hasn't been opened in a while, its push token can occasionally go stale; opening the app and letting it fully load will usually refresh it.

Still need help? If you've checked all of the above and notifications still aren't behaving as expected, submit a ticket to the DB Store USA support team with the device and phone platform involved, and we'll help you track it down.