- ページ 5

インターホン・システム DoorBird D101のPDF クイック・スタート・マニュアルをオンラインで閲覧またはダウンロードできます。DoorBird D101 7 ページ。 Doorstation driver

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%.