From 20f1201c1c333c438427f8af3fe9d1f782485b22 Mon Sep 17 00:00:00 2001 From: Kevin Fronczak Date: Tue, 26 May 2020 06:06:44 -0400 Subject: [PATCH] Blink battery sensor moved to binary sensor platform (#13441) Co-authored-by: Franck Nijhof --- source/_integrations/blink.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index efd528aacf8..947089e46b9 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -60,8 +60,8 @@ Once Home Assistant starts and you authenticate access, the `blink` integration - An `alarm_control_panel` to arm/disarm the whole blink system (note, `alarm_arm_home` is not implemented and will not actually do anything, despite it being an option in the GUI). - A `camera` for each camera linked to your Blink sync module. -- A `sensor` per camera for temperature, wifi strength, and battery status -- A `binary_sensor` motion detection and camera armed status +- A `sensor` per camera for temperature and Wi-Fi strength. +- A `binary_sensor` motion detection, camera armed status, and battery status. Since the cameras are battery operated, setting the `scan_interval` must be done with care so as to not drain the battery too quickly, or hammer Blink's servers with too many API requests. The cameras can be manually updated via the `trigger_camera` service which will ignore the throttling caused by `scan_interval`. 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.