Core: Blink cameras don't show up

Created on 10 Oct 2018  ·  12Comments  ·  Source: home-assistant/core


CC @fronzbot

Home Assistant release with the issue:
dev-branch

Last working Home Assistant release (if known):
N/A

Operating environment (Hass.io/Docker/Windows/etc.):
OS/X dev environment

Component/platform:
blink

Description of problem:
cameras don't show up... only 1 entity: alarm_control_panel.blink_sync

Possibly related to #16942

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

blink:
  username: [email protected]
  password: redacted

  binary_sensors:
    monitored_conditions:
      - motion_enabled
      - motion_detected
  sensors:
    monitored_conditions:
      - battery
      - temperature
      - status
      - wifi_strength

Traceback (if applicable):

No error

Additional information:

All 12 comments

Can you change your config to the following and report back?

blink:
    username: [email protected]
    password: yourpassword

I'm now testing your blinkpy library directly and the cameras also don't show up :(

Better move to an issue there

Are you sure your cameras are linked to your sync module?

I have 1 sync module with 3 cameras. Since updating to 0.80, only 2 cameras show up. The camera that is not showing an image is also the battery at -100 and WiFi as unknown. The temperature is displaying within a degree or two of the other cameras. I changed the batteries and removed and re-added the camera and still get the same thing. I cannot find it now but I seen in a log or somewhere in ha, that it failed to get an image url for that camera.

Take a look at this and see if it fixes the issue

Take a look at this and see if it fixes the issue

That was it, Thanks.

If you are having problems with the Blink platform and are willing to test, please follow the instructions for testing here. I tried to be as detailed as possible.

I'm just CC'ing people I know that have reported issues, in case you want to test.
@tgrecojr @dib0 @haqwin

Followed the instructions suggested in the above post and it's working fine
now.

On Tue, Oct 16, 2018, 1:03 PM Kevin Fronczak notifications@github.com
wrote:

If you are having problems with the Blink platform and are willing to
test, please follow the instructions for testing here
https://github.com/fronzbot/blinkpy/pull/97#issuecomment-430331783. I
tried to be as detailed as possible.

I'm just CC'ing people I know that have reported issues, in case you want
to test.
@tgrecojr https://github.com/tgrecojr @dib0 https://github.com/dib0
@haqwin https://github.com/haqwin


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/17316#issuecomment-430336331,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJnZz2pAnpjsdklRW2VcraIgJ7-LPVJYks5ulh9dgaJpZM4XWNTZ
.

After updating Home Assistant 0.80.2, I am getting.........
(Invalid config for [blink]: value is not allowed @ data['blink']['sensors']['monitored_conditions'][2]. Got 'status'. (See /config/configuration.yaml, line 555). Please check the docs at https://home-assistant.io/components/blink/)

This is what I have in my Configuration file........
blink:
username: _my-username_
password: _my-password_
scan_interval: 60
binary_sensors:
monitored_conditions:
- motion_enabled
- motion_detected
sensors:
monitored_conditions:
- battery
- temperature
- status
- wifi_strength

I have tried rebooting several times.

Remove status from monitored_conditions as it had to be removed due to reliance on an unreliable API endpoint. I expected the change to be added to 0.81.0 rather than 0.80.2 so the docs haven't been updated yet. It was mentioned in the linked PR though.

BTW, unless you choose NOT to have any of those sensors, adding all of those monitored conditions is unnecessary since they're added by default. Your config above ends up producing indentical behavior to this:

blink:
  username: blah
  password: somepassword

That's what i just tried. Removed everything, rebooted and went back to what you posted and its working. Thanks

Thanks @fronzbot for all the work. It's really stable and works really well now! 👍

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TheZoker picture TheZoker  ·  3Comments

Elmardus picture Elmardus  ·  3Comments

kirichkov picture kirichkov  ·  3Comments

flsabourin picture flsabourin  ·  3Comments

sh0rez picture sh0rez  ·  3Comments