Blink Binding

MarcoZan · February 7, 2024, 9:26am

Hi Wouter, i tried your reviewed jar, but still have the same problem I was experiencing with previous versions. When I enable the binding, I immediately get the following error:
COMMUNICATION_ERROR
java.util.concurrent.ExecutionException: org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header

I don’t receive any authentication code, and therefore the binding won’t work.

Can you help me to understand what’s happening? Am I doing something wrong?

thanks and regards
Marco

Jogobo · April 4, 2024, 6:54am

Since last night I cannot login to my blink account. Error message is “Blink API Call unsuccessful <Status 403>”.
I tried to delete the account and add it again. But I don’t receive the 2fa PIN code.

TheTiGeR · April 4, 2024, 10:19am

Same error for me also since this night

Jogobo · April 4, 2024, 12:49pm

Using “curl” with the api works.

tomka · April 4, 2024, 1:47pm

Same here.
Could anyone help, please?

Bert.99 · April 4, 2024, 4:41pm

Same error😒

SLC-Josh · April 4, 2024, 4:57pm

Also, getting the same error. Tried the newer jar and still getting it.

dheneghan · April 4, 2024, 5:21pm

Unfortunately, the same here:

Blink API Call unsuccessful <Status 403>

I guess Blink have changed something their end as they want our money!! The Mobile App has recently changed also and now defaults to Cloud storage all the time so states ‘no clips’ and have to manually change back to internal storage.

Hope someone here with more knowledge than me can figure it out and amend the binding.

SLC-Josh · April 4, 2024, 5:36pm

Odd my app still defaults to Local Storage, did have a few updates so maybe they are having issues with the app too.

patrick.ritter · April 5, 2024, 4:29pm

Where can i found the api spec? maybe this will help to found the Problem in source code - openhab-addons/bundles/org.openhab.binding.blink at blinkbinding · moesterheld/openhab-addons · GitHub

Jogobo · April 6, 2024, 9:16am

The information can be found here

The difference in login is that with “curl” I don’t use a “unique_id”. Maybe this should not be sent during login?

aes · April 9, 2024, 1:40pm

Same issue here

doktormo · April 10, 2024, 10:49am

Hi folks,
I will take a look into this this week. If it is doable without too big of a workload I will address the changes necessary.
I have moved on from OpenHab, so I need to set up a development environment once again to test it. Please bear with me while I do that.
This will then be my last contribution to the binding. If anyone versed in Java development wants to take over, please go ahead and fork the branch.
Matthias

aes · April 10, 2024, 1:45pm

From what @Jogobo said up here, maybe removing this line can be the first thing to try (I’m just trying to help, not saying what you should do, I’m only a grateful user willing to help to the best of my knowledge):

github.com

moesterheld/openhab-addons/blob/7f98b5b635931fb7a48708df1dcc315dee13152e/bundles/org.openhab.binding.blink/src/main/java/org/openhab/binding/blink/internal/service/AccountService.java#L63


      
           */
          public BlinkAccount login(@Nullable AccountConfiguration configuration, String generatedClientId, boolean start2FA)
                  throws IOException {
              if (configuration == null) {
                  throw new IllegalArgumentException("Cannot authenticate without configuration");
              }
              String uri = "/api/v5/account/login";
              Map<String, String> params = new HashMap<>();
              params.put("email", configuration.email);
              params.put("password", configuration.password);
              params.put("unique_id", generatedClientId);
              if (!start2FA) {
                  params.put("reauth", "true");
              }
              BlinkAccount login = apiRequest("prod", uri, HttpMethod.POST, null, params, BlinkAccount.class);
              if (login.account == null || login.auth == null)
                  throw new IOException("Did not receive valid account or token from API.");
              return login;
          }
          
          /**

Jogobo · April 10, 2024, 2:02pm

As far as I digged into the login process via curl and bash I can say that it depends on the time since last “rauth”. If it is too long “reauth” fails and a login with ‘{ “reauth”:false }’ results in a new PIN sent via SMS.

So if there is an auth token and login with “reauth=true” fails, I send a login request with “reauth=no”, verify the PIN and everything I moved to bash scripts works as expected. Set the time between two logins with “reauth=true” to 12 hours and up to now, I had no problems.

_radza · April 11, 2024, 9:11am

That’s great ! Thank very much. If you need help testing you can count on me again.

muggel · April 13, 2024, 1:22pm

How can I set up?
I tried to delete the blink-thing an add a new blink-account, but there are no options to set “reauth”.
For a new think, no pin is generated and the error “Blink API Call unsuccessful <Status 403>” is shown immediately after activating the blink account.

Jogobo · April 14, 2024, 10:06am

There is no way to do this manually in openHAB (at least for the moment). My posting was just a hint for the developper of the binding where the solution might be found.

doktormo · April 18, 2024, 8:29pm

Alright. Another heads-up. This is caused by the User-Agent header set by the Jetty Library used in OpenHab (Jetty/9.4.50.v20221201, can reproduce it in Postman)

See also Change User Agent in HTTP Binding

I must see if I can find a way around that.

doktormo · April 18, 2024, 9:08pm

So it turned out that the AWS service blink is using got a little more restrictive. Next to the user agent, it also discarded parameters not sent in the body (don’t know why I didn’t implement it that way in the first place). So after jumping from 403 to 403, here’s a working version:

Please let me know it that works for you