DoorBird | IP Video Door Station | Version 3.1

Introduction & Manufacturer Profile

Bird Home Automation GmbH develops and manufactures IP-based video door intercoms, access control devices, indoor stations, and accessories under the DoorBird brand. The smart home products are made in Germany in line with the highest quality and security standards and installed worldwide.

Manufacturer Note: Before using this driver, you must change the notification mode in each station's administration settings to "Send only new version 2 notifications" and ensure every user has API-Operator permissions in the DoorBird app. The driver is designed exclusively for version 2 notifications; version 1 is being phased out by DoorBird.

---

Version History

• Version 3.0 — Initial release. Multi-station, multi-user support via HTTP/mDNS. Supports doorbell, motion, door relay, light, speaker/mic level, and station restart.
• Version 3.1 — Stability fixes: resolved intermittent relay command failures after initialization caused by a missing null guard on the relay array; fixed heartbeat loop to prevent it from stalling and leaving relays unresponsive.

---

Driver Features

• Multi-Station Support — Up to 6 DoorBird stations per driver instance
• Multi-User Support — Up to 4 users per station, each with independent credentials and relay access
• Door/Relay Control — Open any configured relay by name (up to 11 relays per user)
• Light Control — Trigger the DoorBird IR illuminator
• Doorbell & Motion Events — Push notifications via UDP multicast on port 6524 or 35344
• Station Restart — Remote reboot of any DoorBird station
• Speaker & Microphone Level — Set or adjust SIP call audio levels (1–100)
• mDNS Discovery — Use the ... picker in Integration Designer to discover stations by name
• MJPEG Video Feed — MJPEG URL exposed per user for use with the Generic MJPEG Object

---

System Requirements & Prerequisites

RTI System Requirements

• Integration Designer — 11.6.1 or later
• XP Firmware — 24.8.19 or later

Device Requirements

• DoorBird IP video door station with network (LAN) connectivity
• Notification mode set to: Administration → Expert Settings → Notification Mode → Send only new version 2 notifications
• API-Operator permission enabled for every user credential used by the driver (DoorBird app → Administration → Users)

---

Driver Configuration

It is extremely important when using this driver that you change the notification mode to "Send only new version 2 notifications" and ensure each user credential has "API-Operator" permissions in the DoorBird app. Without these settings the driver will not function as expected and will produce 401 responses.

General Settings

• Station Count — Number of DoorBird stations (1–6)
• Notification Monitor Port — UDP port for push notifications. Select 6524 or 35344 to match the port configured in the DoorBird app's HTTP call settings

Station Configuration (per station 1–6)

• Station Name — Display name for the station
• IP Address — IP address of the station, or use the ... picker to discover via mDNS
• Number of Users — Number of user credentials configured for this station (1–4)

User Configuration (per station, per user 1–4)

• Name of User — Internal label for this user credential
• Username — DoorBird API username. Found in the Digital Passport document included with the station; can be changed in the DoorBird app
• Password — DoorBird API password. Found in the Digital Passport document; can be changed in the DoorBird app
• Doorbell ID — Internal identifier for the doorbell associated with this user
• Door/Relay Access Count — Number of relays accessible to this user (0–11)

Relay Configuration (per user, per relay 1–11)

• Door/Relay Name — Display name shown in the function selector (e.g., Front Door, Gate)
• Door/Relay Controller ID — The relay ID string from the DoorBird station (e.g., 1, 2, opendoor)

---

Device Setup

Step 1: Connect the Station to the Network

Connect the DoorBird station to the same LAN as the RTI processor. Note the station's IP address from the DoorBird app under Administration → Network.

Step 2: Set the Notification Mode

1. Open the DoorBird app and navigate to Administration → Expert Settings
2. Set Notification Mode to Send only new version 2 notifications
3. Save the setting

Step 3: Verify API-Operator Permissions

1. In the DoorBird app, navigate to Administration → Users
2. For each user credential that will be entered in the driver, verify that API-Operator is enabled
3. Note the Username and Password for each user — these are also found in the Digital Passport document shipped with the station

Step 4: Configure HTTP Call Settings (Notification Port)

1. In the DoorBird app, navigate to Administration → HTTP Calls (or push notification settings)
2. Note the port in use (6524 or 35344) and enter the same port in the driver's Notification Monitor Port setting

Step 5: Configure the Driver

1. Set Station Count to the number of DoorBird stations
2. Enter the IP address (or use mDNS discovery) and user count for each station
3. For each user, enter the Username, Password, and relay configuration
4. Set the Notification Monitor Port to match the DoorBird app setting

---

Functions

Functions are organized per station and per user. The Station and User parameters are set automatically by Integration Designer based on how the function is added to a button.

Light On

LightOn — Activates the DoorBird station's IR illuminator.

No additional parameters.

Door/Relay Control

DoorRelay — Opens a configured door relay.

• Door/Relay — Select the relay to trigger. The dropdown lists only relays that are configured with a name and controller ID. Values 1–11.

Restart Station

RestartStation — Sends a remote restart command to the DoorBird station.

No additional parameters.

Set Speaker Level

SetSpeakerLevel — Sets the SIP call speaker volume to an absolute level.

• Level (Integer, 1–100, default 70) — Target speaker volume level

This setting affects SIP calls only. It does not affect the DoorBird app volume.

Adjust Speaker Level

AdjSpeakerLevel — Adjusts the SIP call speaker volume relative to the current level.

• Direction — Up (+1) or Down (-1)
• Steps — Number of steps to adjust: 1, 2, 3, 4, or 5

Set Microphone Level

SetMicLevel — Sets the SIP call microphone level to an absolute value.

• Level (Integer, 1–100, default 30) — Target microphone level

This setting affects SIP calls only. It does not affect the DoorBird app audio.

Adjust Microphone Level

AdjMicLevel — Adjusts the SIP call microphone level relative to the current level.

• Direction — Up (+1) or Down (-1)
• Steps — Number of steps to adjust: 1, 2, 3, 4, or 5

---

Variables

Variables are organized per station (1–6) and per user (1–4). The station number appears as a zero-padded three-digit suffix (e.g., 001–006); user numbers are appended with an underscore (e.g., 001_001).

Station Variables (per station 001–006)

• Name (StationName001) (String) — Display name of the station
• Motion Sensed (StationMotion_001) (Boolean) — true when a motion event is received. Requires Notification Monitor Port to be set.
• Connection State (ConnectState001) (Integer) — 0 = Disconnected, 1 = Connected
• Disconnected (ConnectState00100) (Boolean) — true when the station is disconnected
• Connected (ConnectState00101) (Boolean) — true when the station is connected
• Doorbell Ringing (StationDoorBell_001) (Boolean) — true when a doorbell event is received. Requires Notification Monitor Port to be set.
• Speaker Level (StationSpeakerLevel001) (Integer, 1–100) — Current SIP speaker volume level
• Microphone Level (StationMicLevel001) (Integer, 1–100) — Current SIP microphone level

User Variables (per station 001–006, per user 001–004)

• Name of User (Name001_001) (String) — Display name of the user credential

---

Events

Initialization State

• INITIALIZATIONSTATE_00 — Driver is not initialized
• INITIALIZATIONSTATE_01 — Driver has initialized successfully
• INITIALIZATIONSTATE_02 — Driver is currently initializing

Station Events (per station 001–006)

Events for stations 2–6 follow the same pattern with the corresponding suffix (_002–_006).

• STATIONCONNECTED_001 — Station connected
• STATIONDISCONNECTED_001 — Station disconnected
• STATIONMOTION_001 — Motion sensed. Only fires when Notification Monitor Port is set.

User Events (per station 001–006, per user 001–004)

• STATIONDOORBELL_001_001 — Doorbell ringing for Station 1, User 1. Only fires when Notification Monitor Port is set.

User events for additional users follow the pattern STATIONDOORBELL_SSS_UUU where SSS is the zero-padded station number and UUU is the zero-padded user number.

---

Limitations

• This driver does not handle SIP calls. SIP functionality is handled through the VoIP Control object in Integration Designer. Refer to the included sample project and the RTI DoorBird SIP Configuration Guide for setup instructions.
• Speaker and microphone volume controls affect SIP call audio only; they have no effect on the DoorBird app audio.
• A MJPEG video stream URL is available per user for use with the Generic MJPEG Object in RTI IP-capable devices. Refer to the included RTI DoorBird SIP Configuration Guide for details.
• Push notification events (doorbell, motion) require the Notification Monitor Port setting to be configured and the DoorBird station's HTTP call notifications to be directed to the RTI processor on the same port.

---

Troubleshooting

401 Unauthorized Responses

Symptom: Driver logs show 401 responses; relay and light commands have no effect.

Solution:

1. Verify that each user credential in the driver has API-Operator permission enabled in the DoorBird app under Administration → Users
2. Confirm the Username and Password in the driver match those in the DoorBird app or Digital Passport document

No Doorbell or Motion Events

Symptom: Doorbell and motion events never fire despite activity at the station.

Solution:

1. Verify the Notification Monitor Port is set to either 6524 or 35344
2. In the DoorBird app, confirm the HTTP call / push notification port matches the driver's setting
3. Confirm the notification mode is set to Send only new version 2 notifications — the driver does not support version 1 notifications

Relay Commands Fail After Working Initially

Symptom: Door relay commands work after initialization but stop responding after a few minutes.

Solution:

1. Enable Debug Level 2 or 3 in the driver and check the log for the specific error
2. Verify the Door/Relay Controller ID in driver properties exactly matches the relay ID configured on the DoorBird station
3. Confirm the user credential still has API-Operator permission — some DoorBird firmware updates reset permissions

Station Shows Disconnected

Symptom: Station connection state shows disconnected; heartbeat log indicates station not found.

Solution:

1. Verify the IP address in driver properties is correct and reachable from the RTI processor
2. If using mDNS, confirm the station's mDNS hostname resolves correctly on the network
3. Ping the station IP from the network to confirm reachability
4. Check that the DoorBird station has network connectivity and power

---

System Testing

• Integration Designer — 11.14
• XP Processor Model — XP-6s
• XP Processor Firmware — 25.9.24
• Device Model(s) — D1101V, D2103V
• Device Firmware — Varies by device — most recent releases as of May 21, 2026

---

Support Contact

Remote Technologies Inc.

Phone: +1 952-253-3100

Email: support@rticontrol.com