From ca0e7c2d01a3576b016f1310e9f8b641cd627eb4 Mon Sep 17 00:00:00 2001 From: Matt Snyder Date: Sun, 9 Sep 2018 17:26:13 -0500 Subject: [PATCH] Doorbird auth and event data --- source/_components/doorbird.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_components/doorbird.markdown b/source/_components/doorbird.markdown index 839a77a2e911..15e9b3808a09 100644 --- a/source/_components/doorbird.markdown +++ b/source/_components/doorbird.markdown @@ -22,6 +22,7 @@ To connect your device, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry doorbird: + token: RANDOM_STRING devices: - host: DOORBIRD_IP_OR_HOSTNAME username: YOUR_USERNAME @@ -38,6 +39,10 @@ doorbird: ``` {% configuration %} +token: + description: Token to be used to authenticate Doorbird calls to Home Assistant. + required: true + type: string devices: description: List of doorbird devices. required: true @@ -87,6 +92,13 @@ Home Assistant will fire an event any time a `monitored_condition` happens on a Enabling any monitored condition will delete all registered notification services on the doorstation every time Home Assistant starts. This will not affect notifications delivered by the DoorBird mobile app.

+#### {% linkable_title Event Data %} +Each event includes live image and live video URLs for the Doorbird device that triggered the event. These URLs can be found on the event data and can be useful in automation actions. For example, you could use `html5_viewer_url` on a notification to be linked directly to the live view of the device that triggered the automation. + +

+The URLs on the event will be based on the configuration used to connect to your Doorbird device. Ability to connect from outside your network will depend on your configuration. +

+ ### {% linkable_title Automation Example %} ```yaml - alias: Doorbird Ring