I am trying to be hopeful it is a glitch on their end that will be sorted out... When I manually try stuff on my end going to the server address I know, the server responds initially. But any deeper information is failing with that 502. If this IS a change it is too soon for the the other couple API projects I know of out there also as there is nothing new on any of them.
In the meantime I am still trying what I can... although I will have to pause soon whether I find something or not. Normal family life getting in the way of Hubitat.
EDIT:
Little further examination of the response behind the scenes... It appears to be referencing an error from cloudfront. When I combine that with the 502 message most of the information online appears geared around there being an SSL misconfiguration between the originating server and the cloudfront services that are used to help distribute it. So MAYBE there really is an error on their end that will be resolved? At this point I think I should "wait and see" a touch.
I hear ya, lol. I think I jumped the gun assuming something happened on my end. Since I tried deleting and reinstalling the device all the Auth is gone so now no access whatsoever, maybe I should have waited. No biggie, I am sure it's nothing too major, after all the app is still working from the phone. The was a new feature rolled out though, something to do with accessing a snapshot on android and ios devices. That was only last week.
The piece I saw when looking at stuff was an odd disconnect and reconnect of one of my sync modules from the network yesterday. My initial fear was maybe it got a firmware update to support some new server destination... except all my driver-side stuff continued fine yesterday and into today. But of course Blink (Amazon) does not publish any readme for their firmware and you cannot even find out about the version my sync has on it.
The push last week might have been related to the new pan/tilt module they added for the Mini cameras. Got one of those myself... but no indications it can be through the API. You cannot even control it unless you are using liveview. I was hoping to see if it could be set to automatically sweep, or center on a motion area when motion is detected, or similar stuff but nope (not yet at least).
Well if it continues it may be the nail in the coffin for our Blink system. Your integration saved it at the beginning of this journey. It's unfortunate that I just dumped a bunch of money into network infrastructure otherwise I'd be buying a bunch of G3 Flexs for inside.
The G5 Flex is in EA now... not sure when those will become available nor whether they are worth $50 more than the G3 Flex.
Even though I just got the Mini's pan/tilt... I am also getting a bit discouraged with the Blink system... I may start looking at alternatives. While I have a pretty decent Ubiquiti setup their cameras are basically all out of my price range for what they provide. Not that I have real high demands for the cameras (I mean, all my current ones are Blink after all). I WOULD prefer to have a local-only system that I can still interface with Hubitat...
All that said, I would not dump the Blink driver. Even if they made a change so it appears dead in the short-term there is the chance people will figure out where the new destination is and I would be able to revive it. Overall I still hope this is just a glitch. I have still been playing a bit on my side and no changes at all. Never gets a "Not Found" or "Not Authorized"... always just that Cloudfront-related 502.
Hi, just wondering if anyone else is having issues with the Blink API. I looked at my logs and it states:
2022-11-04 12:06:35.497 AMerror Blink API - 502 from Blink
I tried to reauthorize and did not get emailed a PIN but did get the following error dev:652022-11-04 07:56:15.257 AMerror Blink API - 502 from Blink during authorization
I checked and the app is up to date (via the HPM). I can turn it on/off manually and it is working.
@user1949: Home Assistant is still working fine? There have been no changes to the underlying code that supports their implementation (it is one of my references) and I have reached out to some other developers if they have seen anything (no answers yet).
All:
There have been no changes on my code side either. Which means that the change is something on Blink's side. There IS the chance that Blink is having issues... but at this point I have to consider that they may be blocking this driver from accessing the API specifically. Nothing I have done from my side has worked, including some stuff that I have not made normally available to users... so there is not much point yet in releasing an update (there is no fix yet).
I will continue to see if there is anything I can do from my side... or if things change otherwise... but if it does not improve this weekend then I will be adding a warning on the initial post that this may no longer be functional.
I do not know if related, but HA had core and supervisor updates the last 2 days.
I restarted several times, no error messages from the Blink Integration at all during update process and also not before.
I checked the log in HA, yesterday at arround the same time 502 happened in HE first time: but all running and up!
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))': /api/v3/accounts/XXXXXX/homescreen
November 2022 um 16:10:37 – (WARNING) components/blink/binary_sensor.py
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))': /api/v3/accounts/XXXXXXX/homescreen
November 2022 um 16:05:09 – (WARNING) components/blink/alarm_control_panel.py
[XXXXXXXXXXX] Entity alarm_control_panel.blink_front does not support this service.
November 2022 um 00:36:21 – (ERROR) Home Assistant WebSocket API
