DoorBird Notification Utility

Version 1.1

The DoorBird Notification Utility allows an RTI system to enable, disable, toggle, and confirm the DoorBird doorbell notify schedule. It supports up to six independently configured DoorBird stations. Before every change, the driver reads the current schedule and changes only the enabled value for the selected doorbell notify entry. Existing days and times are preserved.

Important behavior

Disabling DoorBird notifications can stop DoorBird app push notifications, associated cloud recording, the standard RTI DoorBird driver's Doorbell Ringing event, and notification-dependent peripherals such as an IP Door Chime. It does not disable the physical button, live video or audio, relay operation, or unrelated schedule entries. Test the exact behavior of installed peripherals during commissioning.

This utility does not monitor button presses. Continue using the standard RTI DoorBird driver for video, audio, relay control, and doorbell events while notifications are enabled.

Requirements

1. A compatible DoorBird with LAN API firmware 000110 or later.

2. A dedicated DoorBird API Operator user with schedule access.

3. Local HTTP connectivity from the RTI processor to each DoorBird.

4. The correct doorbell input number. This is normally 1 on a single-button station.

DoorBird permits no more than one new API connection per second. The driver serializes all requests and defaults to 1200 milliseconds between connections.

Driver Properties

Number of Stations exposes configuration for one through six stations.

Each Station Configuration section contains Station Name, Station IP Address, and HTTP Port. The station name appears in command selectors, variables, events, and logs. Do not include http:// or an API path in the Station IP Address field. HTTP Port 80 is typical. This is not the UDP notification-monitor port used by the full RTI DoorBird driver.

Each Station User 1 Configuration section contains Name of User, Login - Username, Login - Password, and Doorbell ID. Name of User defaults to User 1. Use a dedicated user with API operator permission. Doorbell ID identifies the doorbell input schedule and is normally 1 on a single-button station. The schedule is station-wide, so only one API Operator user is required per station. Additional users in the full RTI DoorBird driver do not need to be duplicated. Credentials are never logged.

Startup Delay controls the wait before the first schedule read. Poll Interval controls how often a complete feedback cycle is performed across all configured stations. Request Timeout controls how long the driver waits for a response. Request Spacing controls the minimum interval between API connections and must remain at least 1000 milliseconds. Communication Failure Threshold determines when a station is marked offline.

Enable Trace provides normal operational diagnostics. Verbose Trace adds every request and routine state confirmation and should be enabled only temporarily.

Commands

Set Doorbell Notifications provides Station and State parameters. State can be Enable or Disable. It reads the current selected entry, sets only enabled to 1 or 0, writes the complete current entry, and verifies the result. Use Set in macros where the intended result must be deterministic.

Toggle Doorbell Notifications reverses the confirmed state. Toggle is rejected until Feedback Synchronized is true.

Refresh Notification State immediately reads one selected DoorBird. Refresh All Notification States queues a read for every valid configured station.

Variables and events

Driver variables report overall status, configured and online station counts, request queue depth, and the current driver error. Last Driver Error displays No errors since startup after initialization and after all affected stations recover. An active error remains visible until its station communicates successfully, and recovery by one station does not conceal an error from another station.

Each station provides Status, Communication Online, Communication Offline, Feedback Synchronized, Notifications State, Notifications, Notifications Enabled, Notifications Disabled, Command Pending, Last Command Result, Last Successful Communication, and Last Error. Last Error displays No errors since startup after initialization or successful recovery. Notifications is Boolean feedback intended for toggle buttons: true means enabled and false means disabled. Notifications State is Unknown until a valid schedule is read. All notification Boolean variables remain false while state is unknown, so use Feedback Synchronized to distinguish startup Unknown from a confirmed disabled state.

Each station provides Feedback Synchronized, Notifications Enabled, Notifications Disabled, Command Completed, Command Failed, Command Rejected, Communication Online, Communication Offline, and Authentication Failed events. Startup creates a silent initial baseline. Feedback Synchronized fires after the first valid read, but the initial state does not generate a historical Notifications Enabled or Notifications Disabled event.

Setup and commissioning

1. Add the driver to Integration Designer.

2. Select Number of Stations.

3. Enter Station Name, Station IP Address, and HTTP Port for each station.

4. Under Station User 1 Configuration, enter Name of User, Login - Username, Login - Password, and Doorbell ID for a user with API operator permission.

5. Add GUI controls using Set Doorbell Notifications or Toggle Doorbell Notifications.

6. Use Notifications as toggle-button feedback. Hide or disable controls until Feedback Synchronized is true so startup Unknown is not mistaken for Disabled.

7. Send the project to the processor and wait for the Startup Delay and serialized initial reads.

8. Confirm each configured station reports Operational and Feedback Synchronized.

9. Disable and enable each station while observing RTI feedback and the DoorBird app schedule.

10. Confirm that schedule times remain preserved and test the expected behavior of app notifications, cloud recording, the standard RTI DoorBird event, and connected peripherals.

Troubleshooting

HTTP 401 indicates invalid API Operator credentials. HTTP 403 indicates insufficient permission. HTTP 423 may indicate a temporary DoorBird authentication lockout after failed attempts; verify credentials and wait at least one minute.

If no notify schedule is found, confirm Doorbell ID and create a notification schedule in the DoorBird app. If feedback remains Unknown, check IP address, port, credentials, network access, and Last Error.

If the standard RTI DoorBird ringing event stops while notifications are disabled, that is expected. Enable notifications to restore that event path.

The full RTI DoorBird driver's Notifications Configuration port 6524 or 35344 is not used by this utility. Those ports are for UDP event monitoring.

Security

The local DoorBird API uses HTTP Basic authentication. Use a trusted automation LAN and a dedicated least-privilege API Operator. The driver does not store credentials in logs or feedback.

Developed & Supported By

Buttonwood Technologies, LLC

rti@buttonwoodtechnologies.com

https://www.buttonwoodtechnologies.com

Version History

Version 1.1: Standardized dealer documentation, Buttonwood Technologies support information, third-party driver notice and disclaimer, and access/notification operational warnings. Runtime communications, commands, variables, events, and DoorBird schedule behavior are unchanged from version 1.0.

Version 1.0: Initial release with six-station support, verified read-modify-write schedule control, polling, startup-safe feedback, per-station failure isolation, events, and diagnostics.

Product Specific Warning

Disabling a DoorBird notification schedule can suppress DoorBird-generated ringing or notification behavior, including applicable peripherals configured through DoorBird. This utility does not monitor the physical call button and does not replace the standard RTI DoorBird driver, the DoorBird application, an access-control system, or a security system. The dealer must confirm the selected station and notification entry, preserve the customer's intended schedule, verify post-command state, and provide another notification path where a missed visitor or call would have consequential impact.

Third-Party Driver Notice and Disclaimer

This driver is independently developed by Buttonwood Technologies, LLC and is not developed, endorsed, supported, or certified by the manufacturers or service providers with which it interoperates, unless expressly stated otherwise. The driver is provided “AS IS” and “WITH ALL FAULTS,” without warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, and noninfringement. To the maximum extent permitted by applicable law, Buttonwood Technologies, LLC shall not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, loss of data, loss of use, service interruption, or lost profits arising from installation or use of the driver. Nothing in this notice excludes or limits liability that cannot lawfully be excluded or limited.