Blink integration broken after HA restart — cannot complete 2FA PIN entry (EU/UK, SMS 2FA)

My Blink integration was working fine until HA restarted overnight. Now I cannot re-authenticate because the 2FA PIN entry field never appears during setup.

My setup:

  • HA version: 2026.6
  • Blink account: UK, linked to Amazon UK
  • 2FA method: SMS
  • Installation: Home Assistant OS

What happens:

  1. Go to Settings → Devices & Services → Add Integration → Blink
  2. Enter credentials
  3. Receive SMS code on phone
  4. HA spins indefinitely — no PIN field ever appears
  5. Eventually fails with "unexpected error"

What I've tried:

  • Deleting and re-adding the integration multiple times
  • Restarting HA
  • Stopping nightly HA restart
  • Using Developer Tools to find blink.send_pin — not available in 2026.6

Related issues:

Has anyone found a working workaround for UK/EU accounts with SMS 2FA?

Following for the same issue in Canada.

Following. Having same issue in US.

Following… Same in Mexico :confused:

Same issue here.

I saw this thread, but not sure how to actually apply the patch. Sounds like they don't intend on fixing it.

Same in EU

me too @fronzbot

Same issue, any fixes yet?

Issue still persists :confused:

Blink authentication bug on HA 2026.6.x has been fixed in PR #174356 (Fix blink 2fa auth flow by drbayer · Pull Request #174356 · home-assistant/core · GitHub) and has been merged on June 22, 2026 into the dev branch.
I guess that fixes will be included in the next HA release but until then, a manual patch can be applied.

Same issue with the 2026.7.2 release of the HA Docker image. The screen to enter the 2FA validation code received via SMS does not appear during the Blink plugin integration.

I get the box to enter the PIN but never receive the PIN. Not in SMS nor email, including the junk folder.

Same thing with Chrome, Brave, etc. No screen to enter the PIN code.

I have the same in Canada, Quebec

Sorry to report broken blink! login from Germany as well.

Broke in uk also .. quite annoying :face_with_symbols_on_mouth:

Same here in Germany but Claude fixed it for me! Here is what he found and its working again :slight_smile:
Blink now rejects non-UUID hardware_id (HTTP 406) - HA hardcodes “Home Assistant”
I reproduced the actual server behavior from inside the HA container (2026.7.2, blinkpy 0.25.6):

  • GET https://api.oauth.blink.com/oauth/v2/authorize with all the parameters blinkpy sends and hardware_id="Home Assistant" → 406 Not Acceptable
  • The identical request with a random UUID as hardware_id → 200 OK (sign-in page)

So Blink appears to have enabled server-side validation requiring hardware_id to be a UUID. The HA integration hardcodes HARDWARE_ID = "Home Assistant" in homeassistant/components/blink/const.py and injects it into every config flow — which is why every HA install worldwide broke at roughly the same time (as soon as its access token expired), regardless of region, while the app (which sends a real device UUID) is unaffected. blinkpy itself would generate a UUID as fallback (auth.py), but HA always overrides it.

Workaround that fixed it for me (advanced users, container install):

  1. Generate a UUID and patch it into const.py inside the container: HARDWARE_ID = "<your-UUID>" (this is lost on every core update).
  2. Stop HA, edit .storage/core.config_entries → blink entry → data.hardware_id from "Home Assistant" to the same UUID (backup the file first; never edit .storage while HA is running), start HA.
  3. Install recovered immediately — the existing refresh token was accepted with the new hardware_id, no re-auth/2FA was needed.

Hi Daniel

That’s great can I ask a few questions pls so I can get mine working.

How did you generate a UUID.

How did you identify you are running a container install .. think I may have found that in about where is says Home Assistant OS , so am I right to say this fix won’t work for me ?

Many thank

Andy

Daniel,

Thanks for this clue. I run my HA on Hyper-V and, with a little help from ChatGPT, I was able to translate your steps to my environment.

Everything is working now.

I’ve got a markdown document that summarizes what I did:

Appreciate it!

Thank you for taking the time to create this.

Very useful.

I tried it on my HA OS install but it fails at step 3 after stopping ha core as terminal becomes unresponsive.

Any idea how to get round this .

Thanks