Blink motion detection not tiggering

Configuration
21

I’m thinking the same thing… I’m using the offline sync module and I can’t get motion alerts, even when I shorten the polling time.

22

So I just revisited this, as I was going down a rabbit hole trying to get IFTTT to work for multiple automations (web hooks only trigger one automation), and discovered that State works (and Device) doesn’t, e.g. this works:

platform: state
entity_id:

  • binary_sensor.blink_parcelbox_motion_detected
23

Does it work consistently? I recall when i was testing it before, it did work sometimes, but the issue was that it only worked sometimes. Likely for the polling reason explained by fronzbot. Are you no longer seeing that issue?

I just did a quick test on my end and it still isn’t working for me.

25

That’s a good point…. I thought that I had discovered the solution, but looking at my other automations… some have used the State approach previously…. And I’ve just supplemented IFTTT webhook as an additional trigger, so I’m not entirely sure, until I investigate a little further (via Trace) what is kicking off the automations…… is yours consistently not working? (as in it never works or rarely works?). Or is it just certain blink devices – some work better than others? I’m happy to investigate a little more – just got a couple of holidays coming up – but clearly I want to try to bottom this out properly rather than mislead you.

26

So, I’ve just spent some time testing and the short answer is no (they don’t work consistently). What I would say is that some Blink Cameras did fire (directly via HA) but others didn’t fire (directly via HA). What I mean by directly that is that I also have them set up in IFTTT and for some strange reasons (seems to point to HA Blink code) they fire 100% of the time from IFTTT (using webhooks) but not always from HA. My alarm automation tells when which has initiated the firing - IFTTT or a Blink camera directly.

1 Like
27

any solution for this?

28

no i stopped trying and used a different solution that didn’t involve this integration

29

What did you do finally?

30

I just used an alexa routine instead.

31

This was my method…Alexa routine that does the triggering of the motion detection, a hardkill activity trigger created using Node-RED Alexa Home Skill Bridge, then NodeRed monitoring for the Alexa trigger, to perform additional work.

So start by going to Node-RED Alexa Home Skill Bridge (hardill.me.uk) and create an activity, by - Add Device, name it something like Camera Motion Detected, Set Actions to On, and Application Type to Activity. Save it, and then get Alexa to discover new devices. When she’s finished move on.

Create an Alexa routine, under Smart Home choose Device and choose the camera, and select motion, and Detected. Then under Alexa will add action Smart Home, Scenes, and select the name of your Hardkill device e.g. Camera Motion Detected. Then Save

Now in NodeRed add Alexa Home (using contrib node-red-contrib-alexa-home-skill), if you’ve not use the contrib, you’ll have to add an account for the matching hardkill login, then refresh the list under Device. Now create your routine, and Deploy it

1 Like
32

I recently also want to use the motion sensor of the Blink camera, and detect the same issue. That the binary_sensor trigger about 5 minutes later that a video is recorded in Blink app.
Reading through the historical posts, it seems no way to solve it within Blink integration. I will try the way around as the last post mentioned.
However, I just have an idea to create a input_boolean and expose it to Alexa. Use Alexa routine to turn on/off the boolean as a trigger of motion detected. Could be easier that Node-Red.