The Blink plugin was working.....then my Polisy got corrupted during the upgrade to version 14.

Now I can't get my Blink system to successfully login. I am assuming it has something to do with the 2FA......

I've tried using my MFA app code, and I've even tried logging on on the web to grab the authorization code that gets sent via text message, and also tried going into the app --> Account and Privacy --> Manage Mobile Devices to swipe a code from there.

Is there any chance this plugin is ever going to work? @Panda88 , is this plugin still alive?

2025-11-01 09:55:25.606 Command    udi_interface.custom DEBUG    custom:load: CUSTOM: load {'LOGIN': 'Login Failed - Try again'}

2025-11-01 09:55:25.607 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking LOGIN / Login Failed - Try again

Can you send me a log with debug enabled and then restart the system

I have no issues last week when split my system in two - remember do not restart system after you update the F2A code - you save and wait

There are 2 other recent threads about Blink not working.

It seems something has changed - breaking the existing log in

I'll take a look to see if it can easily be fixed but need to understand the changes needed first - they are changing to a new authentication scheme it seems

The latest underlying API uses asyncIO which is a big change to the code, so it may take some time

I need to finish my YoLink update first

Edited November 2Nov 2 by Panda88

@Panda88, I understand that it takes time to crawl through these, and I've heard that Blink is particularly annoying, as they don't have an official API. We really appreciate the work you've done on it.

I attached the debug log, with my credentials redacted. If there is anything else that I can provide to help with the debugging, let me know!

Adam

Blink debug.log

I think I have to bite the bullet and change the node to use asyncio - the API version I use is too far behind. It will be an effort but I'll start look at it after I finish my yolink update

I am not an expert by any means, but let me know if I can help with testing or anything.

Thanks - Still fighting some (what I believe is 6.0 related) bug on Yolink - I know what to do on the Blink server, just need to find the time

I know, and we appreciate you giving your free time to work on it!

OK - I have an updated Blink Node - what is the best way to test it

I assume I can just make a new version, as the old ones do not work, but I could also release a version in the beta/non-production store - let me know

There are some changes - it required 2FA key every time the node restarts - it is the new authentication from Blink

I added a time stamp for latest update on cameras

There is a longer delay than before - especially during start up - 10-15 sec or so before it moves along

I have not been able to generate the network Names automatically under config - one will have to generate them manually by added a parameter for each network detected

I tested it a little but there may still be bug, so let me know if you find issues

Released 0.6.4

Uses the latest blinkpy (0.24.1) so features should be up to date

It uses the new login credentials method. It is similar to old version, but it is no longer possible to save the 2FA code, so one will need to add new 2FA code every time node is started. I have tested for 24 hours and it seems token renews correctly

Added a time stamp to cameras showing time for the latest poll of data

Let me know if any issues occur

Note, I have still not figured out how to automatically create the different networks automatically - one need to create them manually by copying the network names to configuration

Edited November 24Nov 24 by Panda88

Okay, I was able to install the plug-in, and it works!

The steps I took were as follows:

1) Install the plug-in. Pop-up appears requiring username and password. Entered username and password in the fields, Then had to restart the plug-in..

2) When the plug-in restarted, it needed a 2FA token that Blink texted to me. I entered it in the correct spot in the configuration.

3) Notifications popped up telling me the networks that were detected. I followed the steps, creating the custom configuration parameters, and enabling them.

4) I waited, but I had to restart the plug-in (and enter the 2FA token that was sent again).

5) The plug-in pulled in all of the Blink cameras in the system, and they were able to be controlled as before!

Nice work!

@Panda88 I agree - Nice Work!

Many thanks for getting the Blink Authorization to work again. It's great to have eisy be able to Arm/Disarm Blink motion, especially when combined with eisy Geofence capability to arm/disarm these cameras when entering or leaving the premise. Really appreciate your digging into this issue.

@Panda88 Impressive! Thank you!

On 11/23/2025 at 8:22 PM, Panda88 said:

Released 0.6.4

Uses the latest blinkpy (0.24.1) so features should be up to date

It uses the new login credentials method. It is similar to old version, but it is no longer possible to save the 2FA code, so one will need to add new 2FA code every time node is started. I have tested for 24 hours and it seems token renews correctly

Added a time stamp to cameras showing time for the latest poll of data

Let me know if any issues occur

Note, I have still not figured out how to automatically create the different networks automatically - one need to create them manually by copying the network names to configuration

I managed to break my Blink plugin connection to eisy. Plugin version: 0.6.4. It had been running fine for a week under IoX 5.9.1 and allowed eisy programs to arm and disarm the Blink devices. Yesterday, I upgraded the eisy IoX to version 6.0.3. Programs and plugins except Blink seem to be running properly. When I restart the Blink plugin, or restart or power cycle eisy, I do not receive a 2FA code from the Blink servers. I do however receive a 2FA code if I try to change a setting in the Blink app. Blink plugin configuration remains the same as it was in IoX 5.91 - Blink app password has not been changed. I have tried deleting the AUTH_KEY field in the plugin and restarted the Blink plugin, but no 2FA code is received. Debug log excerpt is shown below. I'm not sure how to correct the ERROR shown. Suggestions on how to correct this will be greatly appreciated. Thanks.

2025-12-05 07:42:52.787 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message longPoll
2025-12-05 07:42:52.787 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING longPoll
2025-12-05 07:42:52.787 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS longPoll message {} from Polyglot
2025-12-05 07:42:52.788 Thread-62 (systemPoll) udi_interface      INFO     udiBlinkController:systemPoll: System Poll executing: longPoll
2025-12-05 07:42:52.788 Thread-62 (systemPoll) udi_interface      ERROR    BlinkSystem:wrapper: Error executing async method refresh: 'NoneType' object has no attribute 'base_url'

I often find you need to run the upgrade more than once to everything installed correctly

Did you reintall all nodes after the upgrade ? - I wonder if a library is missing - base_url is part of the library

Thanks. I'll run the IoX upgrade again. Only reinstalled the Blink plugin but will try the reinstall ALL after an IoX upgrade.

Ran the IoX update twice, then a reinstall All plugins in PG3. Restarted the Blink plugin. Still, no 2FA received. Same error showing in debug log shown below. Any other suggestions? Thanks.

2025-12-05 13:48:08.839 Thread-14 (systemPoll) udi_interface      INFO     udiBlinkController:systemPoll: System Poll executing: longPoll
2025-12-05 13:48:08.840 Thread-14 (systemPoll) udi_interface      ERROR    BlinkSystem:wrapper: Error executing async method refresh: 'NoneType' object has no attribute 'base_url'

Can you send (PM) me the full log including the PG3 long and install log?

Will do. Thanks.

Just checked - Amazon/Blink has changed the authentication method again - need to figure out how it is done now

Don't restart the node until a fix is in place

That’s got to be tough on you. Thanks for finding the problem; hope you find that it’s an easy fix.

Unfortunately, I suffered a power outage, and am also getting a 'login failed' message.

Just released 0.6.5 It fixes the issue on my side

You may need to refresh the node store for it to show up - it takes a while to propagate on its own

@Panda88 0.6.5 is working great! Thanks for the fast response and your effort to fix the new authorization issue. Well done.