[PROJECT] Driver for Blink API

OK. This is weird. I just tried to arm the system from the Blink App. (iOS) And I can't. It responds with System busy!

I'm thinking the sync module might be going bad. I tried power cycling it and it took about 5 minutes to boot. I have a new Blink Sync Module 2 that I never put into service. So, I will try replacing the original sync module with the newer one and see what happens. I've always been hesitant to do this, because I have the original grandfathered system with free cloud storage.

It should still work. I have an XT2 and a Outdoor gen1 on the same sync module 2 and the XT2 has access to cloud while the Outdoor gen1 is saving to a USB stick.

However IFTTT triggers do NOT work with the (unsubscribed) Outdoor gen1, only the (grandfathered) XT2s.

Well, that was interesting. Posting this here in case it helps anyone else. Replaced the old 2017 era Blink Sync Module with a Module 2. Yes, everything works including the ability to arm/disarm using the Blink Integration from @snell. The Conflict errors went away. Thanks for responding.

2 Likes

I have alwayes error on the side of delay. I use 10 seconds and everything has ticked along just fine.

Continuing the discussion from Blink camera integration:

I am looking to use blink cameras as motion sensors. And would also like to arm/disarm. Is there a driver that will allow this? If so, could you share?

The drivers that this thread is for (see first post) can certainly do the arm/disarm part. Motion detection is probably not going to be what you might want though as the drivers are polling the API for the data (they cannot receive a push notification or however Blink does it for their own app).

1 Like

Best thing I’ve found for the motion is to use the Alexa app (don’t need to have an Alexa device) to set a virtual motion switch in HE.

4 Likes

I realized today that my cameras are not working anymore like they did a couple of days ago.

I found the following error message in the log file

I looked through the postings but were not able to find any related post.

The only change I made was setting up a passkey for my Amazon account.
Any ideas?

Edit: I can neither arm nor disarm the system or enable, disable motion detection. The link between HE and Blink seems to be broken.

Thanks in advance

406 is unusual - response not available in the format requested.

Thanks for your response. Any ideas what causes the "unusual - response"?

As I said I didn't change anything regarding the blink cameras but updated the hub to the latest release this morning.
Just restarted the blink module but no luck. :frowning:

I made this change (from IFTTT) when you mentioned it some time ago (thanks!). Works really well (although the app is a UX mess). When it comes to Blink cameras, Alexa routines have two added benefits over IFTTT:

  • The motion notification appears to be always sent immediately (IFTTT was usually fast but sometimes there was a significant delay, up to a couple of hours !)
  • works with both subscribed and unsubscribed cameras. IFTTT only seems to work with subscribed cameras (no official answer from Blink about this, after much back and forth...).
1 Like

Code hasn't changed recently to the best of my knowledge, so I'd try a reboot of the hub and if that doesn't work maybe a repair from HPM to force a recompile of the code.

Unfortunately no change after a hub reboot and a HPM repair. Still same behavior and same error messages.

Is there anything I have to setup after the HPM repair?

Thanks

Shouldn't have to do anything. Normally due to an Accept requirement in the headers that can't be fulfilled, but I don't see where @snell has any in the code.

I googled a bit about the http 406 error with blink. Got a little bit more light into the darkness.

I read a lot about VPN which causes the 406 issue. The strange thing is, the blink sync module and the HE hub are connected to the same net. Blink module using WiFi, C7 HE hub via LAN.

Never had such problem brfore. No VPN active in this network. If the WiFi mesh network could cause any problems?

I did the same... Blink also have an article on the topic -> https://support.blinkforhome.com/en_US/wi-fi-or-network-issues/how-to-resolve-http-406-errors which I don't think will help given your not using a VPN.

1 Like

Ok, I am on now so I can try to catch up on all of this. Unfortunately, I avoid checking online when I am during work hours.

@jb1: Unfortunately, I have not seen that error reported by anyone before. So... assuming NOTHING else has changed with your network or such:

  1. You already tried rebooting the hub, to no success. (This would not have been my first recommendation, but it is out of the way already).
  2. Have you tried reauthorizing the driver (using the Authorize command with reauthorize set to true)?
  3. If #2 fails... try resetting the authorization entirely by doing the Authorize with reauthorize set to false. This will require you to get the PIN from Blink (should arrive on whatever phone is tied to your account). Like when you first set up the Blink, you will then need to enter that PIN for the "Verify PIN" command.

Beyond that... It sounds like a network issue but you said nothing changed there, correct? You are not having any issues using the normal phone app? I hit the same link that @nutcracker provided when looking (and before I got through the whole line of posts).

It does not matter if the HE and the Blink devices are on the same network. This driver cannot communicate directly with any of them (nor does it try to). It communicates with the Blink API servers.

1 Like

Thanks for your reply @snell .

Currently so far no changes. Yesterday morning I still received temperature from the different cameras. Now everything is dead.

Unfortunately I had no time to dig into this deeper today. I will play and test a bit more over the weekend.

To me it looks like an network issue, but what I don't understand Phone and Blink sync module work fine and are connected to the same WiFi/LAN than HE hub.

Will connect the hub to a different network tomorrow and will test if this changes anything. Maybe the hub causes all this trouble. I don't know why, but maybe. I did a reboot, tomorrow I will try a power cycle and test with the network.

Authorization (true or false) didn't help, because it seems I can't reach the Blink server.

You got the same 406 error even for authorizations? That is VERY strange...

I will let you know if I think of anything to check otherwise.

1 Like