DoorBird D2101V User manual

DoorBird Doorstation Driver
Compatible Control4 Systems:
OS 3.1 and above
Compatible Hardware:
All DoorBird models and configurations
D101(S), D2101V, D2101KV, D2101KH, D1101V
DoorBird Hardware Tips:
Install the DoorBird according to the installation manual.
The DoorBird can use Wifi or PoE (Preferred).
The DoorBird must be on the same subnet as Control4 director.
The DoorBird app should work BEFORE Control4 setup. Make sure you can view the
DoorBird camera and communicate to the unit via the DoorBird app prior to Control4
setup.
Overview
The Control4 Home Automation system can control nearly all aspects of a customer’s smart
home, including security. Security is extremely important for any homeowner, and smart
doorbells offer several features to maintain a safe and secure home. DoorBird is the industry
standard for smart doorbells, with top-of-the-line cameras, real-time notifications, and video
playback. Installing a DoorBird system in your customers’ home gives homeowners peace of
mind knowing that their property is protected. With the DoorBird driver, customers can easily
and conveniently see who is at the door, grant or deny access to their home by triggering a
smart lock, and play back surveillance video all in the Control4 interface.
In addition to the main features customers can receive alerts when motion is detected at the
door, when someone rings the doorbell, when a code is entered on the keypad (specific
models), and more. Icons show the states of the DoorBird, visually communicating that motion
has been detected, when the doorbell rings, if the doorbell has been silenced, and more.
DoorBird App Setup
1. Log into the DoorBird App

2. Go to Settings -> Administration and sign into the DoorBird as admin user (0000)
3. Create user 0002 (example: gxyddsa0002)
4. Enable all permissions for this user
5. Press Save
6. Enable SDDP from DoorBird app
Driver Setup
1. Add Control4 Agents to project:
History Agent (required)
Communication Agent (required for Intercom)
Push Notification Agent (if using Push Notifications)
Announcement Agent (if setting announcements)
2. Connect DoorBird to Control4 via:
SDDP: If the SDDP setting in DoorBird is enabled, the DoorBird should be discoverable
in your project under the Items -> Discovered. Double click the DoorBird to add to the
project.
Other: Add driver to project, go to the Connections tab, select the Network tab in the
Connections section, and either drag the SDDP under Available Devices to the DoorBird
driver or enter the IP address after selecting the driver.
3. Once connected, enter username and password for user 0002 into the driver
4. Refresh navigators and test
5. If intercom with touchscreens is needed, dealers may need to press the doorbell button
once to sync the Control4 sip server with the DoorBird. Monitor driver logs by setting
property Debug Mode to 'On' and view them on the lua tab
Your driver setup is now complete! You may now continue to customizing all of the features of
the driver.
Control4 Proxies:
The DoorBird Doorstation is a great intercom and door entry system. Camera, Intercom, and
UI are available for Control4 projects:
Camera Proxy:
The driver will automatically setup the camera settings during setup. Local and Remote
viewing supported via Control4 T3 touchscreens, Control4 GUI, and MyHome App.
Intercom Proxy:
DoorBird units integrate with the intercom proxy via SIP. Upon successful connection with
DoorBird unit, the driver will register the DoorBird with the Control4 sip server, set the username
and password, and then test for proper communication back from the sip server. Once the sip
settings are sent to the DoorBird, the driver’s work is finished. Communication between
DoorBird and Control4 sip server are handled outside of the driver’s sandbox and control.
Proper functionality between Touchscreens and Intercom Anywhere should be tested and

verified before changing settings in the driver.
Advanced Settings Some projects require greater control of the sip server or are not using
Control4 as the sip server. For these projects, the dealer will need to program the sip Domain,
Username, and Password for their particular setup. This is done via the Intercom - Sip Driver
Property. Set this property to Manual and set the corresponding values (Domain, Username
and Password). This is not needed for most installations.
UI Proxy:
The DoorBird driver comes with an icon for customers to trigger the gate/lock connected to the
DoorBird or other custom actions the dealer wishes (Example: use the Control4 Navigator Agent
to show the DoorBird camera directly via Control4 touch screens). The actions associated with
single/double tapping the icon are set via the property UIButton: Single/Double Tap. Options are
Trigger Relay 1 (default), Trigger Relay 2, Silence Alerts, Display Status, and Nothing. Note:
Composer Events for single and double tap will still occur regardless of this setting. Display
Status and Silence Alerts are special actions that do the following:
Display Status: This feature will send a general information message about the current
status and driver event history to Control4 touchscreens. The information is the same
as Display Status under the Driver Actions drop down.
Silence Alerts: This feature will turn off (silence) alerts notifications programmed in the
driver.
Normal: Driver is working
Motion Detected
Doorbell has been pressed
Relay has been triggered
Silenced. When this state is active, Doorbell and Motion
announcements in home are silenced. Notification on DoorBird
App will still be enabled

Notifications, Relays, Events:
The driver comes standard with many automatic notifications. These are configured under the
Driver Property DoorBird Events. These events have actions that can be triggered when the
event occurs. Below are the actions available. Note: not all events have access to all actions.
Message:
This is the message that will be sent to the customer when this event happens.
Note: custom variables are available for insertion into the message. See Custom Message
Variables for implementation
Intercom Group:
This intercom group will be executed (sip call) when the event is triggered (ex. DOORBELL
pressed event is triggered, make call to sip group All). Selecting None will cause the driver to
refresh the intercom group list.
Push:
This informs the driver to send a Control4 Push Notification (with doorbird image snapshot)
when the event is triggered. Options for alert levels are: Alarm, Alert, Info, or No (don't send an
alert). The subject line of the message is set under the property Email: Subject in the driver
(default: My Control4 Smart Home).
Announcement:
Trigger an announcement when the event is triggered. Selecting None will also cause the driver
to refresh the dropdown list..
Navigators:
Triggers a popup to be displayed on all touchscreens selected under driver property Control4
Navigators. An image and messages are displayed.
DoorBird Events:
These are the events the driver responds to when they happen on the DoorBird.
Doorbell:
Doorbell press event. Note: Some DoorBird units (MDU) have the ability to assign multiple
doorbells. All Doorbell events trigger this event. Custom events per doorbell can be achieved via
Composer Event programming using Conditional programming (ex. When the Doorbell event is
received and the last doorbell id is 103 do...).
Motion:
Event will trigger when motion is detected on DoorBird. Minimum wait time between motion
events is 30 seconds. Setup of motion sensitivity and zones is done via the DoorBird App.
Relay:

Event when a relay is triggered on the DoorBird. Note: The DoorBird App has a Lock icon for
customers to open the gate or door. Dealers can use Control4 Event programming to trigger a
lock not tied directly to the DoorBird to open when the icon is pressed. If the lock is wired
directly to the DoorBird, no programming is required as the DoorBird controls the lock.
Note on relay wiring: The DoorBird does work with trigger (hold open for x seconds) and toggle
type relays. However, the DoorBird api does not support toggle type relay control currently
(2.2020). Keep this in mind when setting up a solution.
RFID:
Some DoorBird units support RFID tags to be triggers for opening Doors and Gates. Control4
dealers can program off of these events in programming. By default, Push notifications are sent
whenever a RFID tag is used. Conditional programing for specific users is available. The driver
records the last user name for this purpose.
Keypad:
Similar to RFID, the keypad event occurs when a user enters their user code on the DoorBird
(keypad models). The username can be used for custom event programming if needed.
Silenced:
The driver has the ability to mute or silence alerts from the DoorBird for a specific amount of
time. After this event is triggered, the driver will not trigger any event notification if it occurs until
the timer expires. Note: Control4 Event programming will still trigger.
Custom Message Variables:
Variables can be inserted into the notification using special hook characters. See the examples
below. Dealers can modify the Message property of an event and insert variables using the
following format.
Driver Variables:
{Device_Variable_Name} => This will use the value of this driver variable. Names must be
spelled the same way as the variable on the driver.
Ex. [LAST_USER_NAME] has opened the door. Would become: Chad Kroeger has opened
the door.
Other Driver Variables:
{deviceId:Variable_Name} => This will use the value of the Variable attached to the device Id
and Variable Name. Note: Variable_Name must be spelled the same way as the variable on
the driver.
Ex. The lights in the family room are at {123:LIGHT_LEVEL}%. Would become: The lights in
the family room are at 23%.

Composer Variables:
{composer_variable} => This will look at the Variables agent and retrieve the variable that is
named.
Ex. vacation mode is now set to {vacation_mode} mode. Would become: vacation mode is
now set to away mode.
DoorBird Variables:
These are variables about the specific driver:
[Driver_Message] => Displays main Current Status (ex. Someone is at the Door)
[NAME] => The Name of the driver in the project (example: DoorBird)
[STATE] => The current state of the driver (example: RELAY)
[OLDSTATE] => The state prior to the new state notification
[SILENCE] => Amount of hours of the current silence timer
[USER] => Displays the last username from either keypad or RFID event
[RELAY] => The name of the relay in the DoorBird
[DOORBELL] => The name of the doorbell in the DoorBird
Driver Actions:
These options are accessible to the dealer to simplify setup, testing, and troubleshooting.
Actions include:
View Status: views status and history of the DoorBird, lua tab
Simulate Doorbell: simulates doorbell event
Show Icon in All Rooms: makes DoorBird icon visible in all rooms
Hide Icon in All Rooms: hides DoorBird icon in all rooms
Print User and Relay Info: shows user and relays found in the DoorBird app so that
dealer can program without logging into the DoorBird app
Reset DoorBird: start setup from scratch
Control4 Push Notification Setup and Configuration:
The driver supports automatic push notification using the Control4 app. This will send
notifications to registered MyHome devices. For notifications to work, homeowners must have
the Control4 app on the phone and notifications enabled:
Configure Control4 Account: https://customer.control4.com.
Once logged in, go to “My Notifications” under “My Devices".
Select a mobile device you want to receive notifications on.
Configure specific areas, category, and severity of notifications.
“Save” configuration before continuing.

Support:
For Hardware Related Support: [email protected]
For Driver and Setup related support: https://help.drivercentral.io
Developer Information:
Cinegration Development, LLC
https://www.cindev.com