Configuration variables:
+-
+
- username (Required): Your username to login to Blink. +
- password (Required): Your password to login to Blink. +
Once loaded, your front end will have the following components:
- A camera image for each camera in your system. @@ -84,41 +89,33 @@
- A sensor per camera that reports battery level.
- A sensor per camera that reports unread notification (ie. detected motion events).
Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the blink.snap_picture service followed by a blink.force_update service call to force Home Assistant to request an update from Blink’s servers. If the blink.force_update service is not called, the image will be updated within a 180 second interval, set so that automatic server requests don’t overwhelm the Blink API. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended.
Services: -There are three services availiabe for the blink platform:
+Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the snap_picture service to force Home Assistant to request an update from Blink’s servers. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended.
Services:
+This services are available for the blink component:
- arm_system
- arm_camera
- snap_picture -
- force_update
For blink.arm_system, the value sent can be either “True” or “False” and will arm and disarm the whole blink system, respectively
Arm system example
+For arm_system, the value sent can be either True or False and will arm and disarm the whole Blink system. Arm system example:
{
"device_armed": "True"
}
Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if I have a camera named “Living Room” and I want to turn off motion detection on that camera, I’d call the blink.arm_camera service with the following payload:
Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named “Living Room” and you want to turn off motion detection on that camera, you would call the arm_camera service with the following payload:
{
"friendly_name": "Living Room",
"device_armed": "False"
}
The blink.snap_picture service takes the camera name as the payload and with take a new picture with your camera.
{
+The snap_picture service takes the camera name as the payload and with take a new picture with your camera.
+{
"friendly_name": "Living Room"
}
-The blink.force_update service can simply be called with no payload to force a server update.
-Configuration variables:
-
- - username (Required): Your username to login to Blink
- - password (Required): Your password to login to Blink
-
diff --git a/docs/automation/trigger/index.html b/docs/automation/trigger/index.html
index 13e4759caf..8ee05fd6d5 100644
--- a/docs/automation/trigger/index.html
+++ b/docs/automation/trigger/index.html
@@ -150,6 +150,21 @@
offset: '-00:45:00'
Sometimes you may want more grainular control over an automation based on the elevation of the sun. This can be used to layer automations to occur as the sun lowers on the horizon even after when it is below the horizon. This is also useful when the “sunset” event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting.
+automation:
+ alias: "Exterior Lighting on when dark outside"
+ trigger:
+ platform: numeric_state
+ entity_id: sun.sun
+ value_template: "{{ state.attributes.elevation }}"
+ # Can be a positive or negetive number
+ below: -4.0
+ action:
+ service: switch.turn_on
+ entity_id: switch.exterior_lighting
+The US Naval Observatory has a tool that will help you estimate what the solar angle will be at any specific time.
Template trigger
Template triggers work by evaluating a template on each state change. The trigger will fire if the state change caused the template to render ‘true’. This is achieved by having the template result in a true boolean expression ({{ is_state('device_tracker.paulus', 'home') }}) or by having the template render ‘true’ (example below).
With template triggers you can also evaluate attribute changes by using is_state_attr ({{ is_state_attr('climate.living_room', 'away_mode', 'off') }})