Maybe it has nothing to do with the Homey integration, but my blink account got deactivated by blink due to a „Suspicious device running an unauthorized application or integration“.
Homey is the only integration that I use…
Perhaps your polling interval is too short.
I use 3min polling, 15sec cloud and 30sec local motion check without issues.
My polling interval has been unchanged for a long time. Blink support told me the account was disabled because of “pinging the Blink server back to back within seconds apart”. Could an outdated authentication or a failed login loop after the recent changes also cause repeated requests, or do you think this points specifically to the polling settings?
Also just realized: The Homey Blink app updated automatically to version 2.1.5 two days ago. As far as I can tell, that’s exactly when all my Blink issues started and shortly afterwards my Blink account was deactivated…
The app update solves issues caused by an Api change on Blink side. Are your cameeas/account accessible in Homey? If not, try repair of account device (re-login). Peehaps that fixes an auth issue.
No I cant access my cameras anymore. Also cant re-login since my blink account is still suspended…
Hi,
I can no longer connect to my homey SHS blink account : “the login data is invalid” and doesn’t ask for the pin code.
It still works on both my Homey 2023
I checked that I provide the correct id/pwd than in the blink app
Sent a diag report : e877b8b4-1ce9-4457-99a4-95bee44b21b3
Did you get Blink to re-activate your account?
Hi, based on the log I assume Blink did not respond with an http error os something like that. At least the cookie for oAuth was not present.
I tried on my SHS but it’s working there. I can login with my account and can add the account device.
It the error still present for you?
Hi, yes the error is still there.
I just deleted the app and all the devices, restarted SHS/Synology, reinstalled the app and tried to login : “the login data is invalid”
I addes some logging to new test version 2.1.6.
Can you please try again, then send me a report?
Thank you.
9604a5d9-145f-4801-9585-ac69bc6619d2
