Doorbird Door Station| This
function block integrates a Doorbird video door station
via its local network interface (LAN API). The controller
reports doorbell and motion events, operates the door opener
and the light, and provides the camera image for the
Doorbird Door
Station control element. The camera image is fetched by the controller and forwarded to the operating devices over the existing connection — the door station only needs to be reachable in the controller's local network, so the display also works remotely via the app/VPN connection. Requirements:
Several doorbell buttons: On a system with several doorbell buttons (e.g. an apartment building) the output Ring pulse reports every button the same. With the parameter Number of doorbell buttons the block additionally gets one output per button (T1, T2, ...) and the output Doorbell button number (TN) with the button pressed last. Each button output can be wired, for example, to the trigger of a Push message uni-PRO APP block whose recipients are the users of the respective apartment. The Doorbird reports the button in an encrypted UDP broadcast in the local network (ports 6524 and 35344). The controller therefore has to be in the same network as the Doorbird; the user needs no additional permission. Nothing has to be set on the device. With 0 buttons the block behaves as before and opens no UDP port. Checking the button detection: Whether the buttons arrive on a given system can only be checked on site with the real Doorbird. Switch on the parameter Debug, press the buttons one after another, then load the controller log file in the Studio (or copy the channel Messages in the diagnostics window) and send it to support. The block then writes (texts in English):
Note: The Doorbird handles only about one API request per second. After several requests with a wrong password the device blocks authentication for one minute (error code 1 on the output). |
Inputs |
||
| FG |
Enable |
1 = block active (default). With 0 no connections to the door station are established. |
| TO |
Door opener trigger |
A rising edge operates the door opener (configured relay). |
| LI |
Light trigger |
A rising edge switches on the light (infrared/ white light of the door station). |
| CR |
Ring counter reset |
1 resets the ring counter to 0. |
Outputs |
||
| KL |
Ring pulse |
Pulse (duration = pulse length parameter) when the doorbell is pressed. |
| BW |
Motion pulse |
Pulse when motion is detected (motion sensor of the door station). |
| ST |
Status |
0 = offline, 1 = reachable, 2 = reachable and event connection active |
| KZ |
Ring counter |
Number of doorbell presses since the last reset. |
| ER |
Error code |
Last error: 0 = OK, 1 = authentication failed/blocked, 2 = timeout, 3 = permission missing (enable "watch always" for the Doorbird user), 4 = busy (another party is already talking) |
| TA |
Door opener pulse |
Pulse (duration = pulse length parameter) whenever the door opener is triggered — via input TO as well as via the button in the control element. This allows switching a door lock that is not wired to the Doorbird relay but to a separate actuator. Active with mode "Output" or "Both", see parameter Door opener via. |
| LA |
Light pulse |
Like TA, but for the light (parameter Light via). |
| TN |
Doorbell button number |
Number of the doorbell button pressed last (1, 2, ...). The value stays until the next button is pressed. Only present if the parameter Number of doorbell buttons is greater than 0. |
| T1 ... |
Doorbell button 1 ... |
Pulse (duration = parameter Pulse length) when the respective doorbell button is pressed. One output per button, as many as the parameter Number of doorbell buttons says. If the number is reduced, the last outputs are removed together with their connections. |
Parameters |
||
| IP address / host name |
Address of the Doorbird in the local network | |
| Port |
HTTP port of the door station (default 80) | |
| Use HTTPS |
Encrypted connection (port 443, self-signed certificate of the Doorbird). Only effective if the controller was built with SSL support. | |
| User / password |
Credentials of the Doorbird user for the controller (see requirements). | |
| Door opener relay |
Relay to switch, e. g. "1", "2" or "gggaaa@1" (paired door controller). Selectable via the connection test dialog. | |
| Door opener via |
Where the door opener command is routed — it applies
to the button in the control element as well as to input TO. Doorbird relay: the configured relay of the Doorbird (default). Output: output TA only. The Doorbird is not contacted at all — suitable when the door lock is wired to a separate actuator. Both: relay and output together. |
|
| Light via |
Like Door opener via, but for the light (output LA). | |
| Timeout |
Connection timeout in seconds | |
| Pulse length |
Duration of the ring, motion, door opener, light and doorbell button output pulses in seconds | |
| Number of doorbell buttons |
0 (default) = no button detection, the block behaves as before. From 1 on, each button gets an output (T1, T2, ...), plus the output TN with the number of the button pressed last. At most 24. See above, Several doorbell buttons. | |
| Debug |
Additional diagnostic output in the controller log file and in the diagnostics channel Messages: connections to the Doorbird, received events and the button detection. See above, Checking the button detection. Switch off after the test, every line is a write access to the controller's storage. | |