Blink documentation update #2293
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added force_update service and increased time between server calls
2 tasks
Landrash
requested changes
Mar 19, 2017
source/_components/blink.markdown
Outdated
| @@ -33,15 +33,16 @@ Once loaded, your front end will have the following components: | |||
| * 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. The image can only be updated in Home Assistant every 60 seconds in order to not overwhelm Blink's servers with API requests. | |||
| 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. Any camera-specific sensor typically only has its value updated when the image is updated, so relying on, for example, the temperature sensor reporting accurate data is not recommended. | |||
There was a problem hiding this comment.
Double spaces between sentences.
Unsure what your trying to say in the last sentence.
There was a problem hiding this comment.
Yeah that sentence is poorly written. Basically, each camera has a built in temp sensor that is only updated when an image is pulled from the camera so if you wanted to use it as an accurate sensor (something you could base automatons on, for example) is not a great idea.
source/_components/blink.markdown
Outdated
|
|
||
| For arm_system, the value sent can be either "True" or "False" and will arm and disarm the whole blink system, respectively | ||
| For ``blink.arm_system``, the value sent can be either "True" or "False" and will arm and disarm the whole blink system, respectively |
source/_components/blink.markdown
Outdated
| @@ -50,21 +51,23 @@ Arm system example | |||
| } | |||
| ``` | |||
|
|
|||
| 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 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: | |||
source/_components/blink.markdown
Outdated
| ```json | ||
| { | ||
| "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 ``blink.snap_picture`` service takes the camera name as the payload and with take a new picture with your camera. |
source/_components/blink.markdown
Outdated
| ``` | ||
| { | ||
| "friendly_name": "Living Room" | ||
| } | ||
| ``` | ||
|
|
||
| The ``blink.force_update`` service can simply be called with no payload to force a server update. |
|
@Landrash pushed the requested changes (forgot to mention it). Hopefully my rewording makes sense now? Let me know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Added force_update service and increased time between server calls
Pull request in home-assistant (if applicable): home-assistant/core#6696