Blink block account

Configuration
41

Depends on the level of integration you want - you may be better off posting a new thread in the Hardware category to ask the hive mind.

42

Hi All,
i got this message over the last couple of days, and now my blink integration won’t work. ANy suggestions on how best to move forward?

Thanks in advance.

Jason

"Dear Blink Customer,
You are receiving this email because your account has used automation scripts that use an outdated login method to connect to your Blink account. With security and customer protection as our top priority, that login method is being deprecated. This means that any scripts you are using will no longer work as of 5/11.

We encourage you to try out IFTTT, our supported 3rd party integration, for more secure automation functionality. If you have other feature preferences or requests, you can always email product feedback to [email protected] for consideration.
Thank you,

Team Blink"

43

There’s a really long thread about that here: Blink Camera's discontinuing "legacy" login

tl;dr. Fix is in the beta, or just wait for 0.110.0

2 Likes
44

Thanks @fronzbot, think i missed that, will check it out now, much appreciated on all your work.

Jason

45

I’ve made the move to HA 0.110.1 and removed previous blink scipt in configuration.yaml. All is working normally with the exception of trying to get the Blink.trigger_camera automation working using the lovelace UI. More specifically, here is a copy of my glace card visual editor:

aspect_ratio: 67%
camera_image: camera.blink_living_room_cam
entities:
  - entity: camera.blink_living_room_cam
image: 'https://demo.home-assistant.io/stub_config/kitchen.png'
title: Living Room
type: picture-glance
tap_action:
  action: call-service
  service: blink.trigger_camera
  data:
    name: living_room_cam
hold_action:
  action: more-info
theme: Dark - Blue/Purple
camera_view: live

The blink_trigger.camera service identifies the following error which I haven’t been able to resolve (It appears to be a syntax error, but I’ve been unable to locate/interpret documentation to correct.):

Expected a value of type {action,navigation_path,url_path,service,service_data} | undefined for tap_action.data but received {"name":"living_room_cam"}.

If of any help here is the associated error in the log:

Log Details (ERROR)

Logger: homeassistant.components.websocket_api.http.connection.1869319920
Source: core.py:1215
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:51:12 AM (1 occurrences)
Last logged: 8:51:12 AM

required key not provided @ data[‘name’]

Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 130, in handle_call_service connection.context(msg), File “/usr/src/homeassistant/homeassistant/core.py”, line 1215, in async_call processed_data = handler.schema(service_data) File “/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py”, line 272, in call return self._compiled([], data) File “/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py”, line 594, in validate_dict return base_validate(path, iteritems(data), out) File “/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py”, line 432, in validate_mapping raise er.MultipleInvalid(errors) voluptuous.error.MultipleInvalid: required key not provided @ data[‘name’]

Any insight much appreciated. Thanks.

46

Answer: It’s service_data: not data:

Simple answer, but spent a number of hours researching. Is the a source/documentation for this stuff somewhere?

47
1 Like