Home Assistant version: 2026.8.3
Installation type: Home Assistant OS (Home Assistant Green)
Remote access method: Nabu Casa (Home Assistant Cloud)
Issue
When setting up any integration that uses the OAuth my.home-assistant.io redirect flow (confirmed with both Google Nest and Tesla Fleet), the flow proceeds correctly through:
1. Application credentials entry (Client ID/Secret)
2. Redirect to the provider’s login (Google / Tesla)
3. Successful authentication (“Verified Successfully” on Tesla’s side)
4. Device/scope permission screen
5. Redirect back to my.home-assistant.io
…but then hangs indefinitely on the final “Link account” button. Tapping/clicking it does nothing — no error message, no redirect, no console output that I can find.
What I’ve ruled out
• Application credentials: Verified Client ID/Secret match exactly between the provider’s developer console and what’s entered in HA (re-copied character by character after an initial typo was found and fixed).
• Redirect URI: Confirmed set to Link to OAuth2 Authorize Callback – My Home Assistant exactly, on both integrations’ OAuth client configs.
• OAuth scopes: For Nest, confirmed the sdm.service scope was properly added to the Google OAuth consent screen (this was missing initially and caused a different, separate error — now resolved).
• Pub/Sub permissions (Nest-specific): Confirmed [email protected] has Publisher role on the Pub/Sub topic — this fixed an earlier distinct error but not the “Link account” hang.
• Home Assistant URL config: Settings → System → Network shows Internet URL correctly set to “Use Home Assistant Cloud” with the correct Nabu Casa URL; Local network URL also correctly set.
• Nabu Casa status: Checked status.nabucasa.com — all systems operational, no incidents reported.
• Browser/device: Reproduced identically across Safari (iPhone), Safari (Mac), Chrome (Mac), and in a fresh incognito/private window. Same hang every time.
• Stuck flows: Restarted Home Assistant multiple times between attempts to clear any orphaned config flow entries before retrying.
• Completely fresh credentials (Tesla): Registered a brand-new Tesla developer application from scratch (new Client ID/Secret, same scopes: Profile Information, Vehicle Information, Vehicle Charging Management only), deleted the old Application Credentials entry in HA, restarted HA, and tried again. Identical hang at “Link account.”
• HA logs at time of failure: Checked Settings → System → Logs immediately after tapping “Link account” on multiple attempts — nothing relevant logged (only an unrelated GE appliance integration warning with an unrelated timestamp).
What I haven’t been able to check
• Whether this is specific to my HA version or affects others on the same version/hardware (Home Assistant Green).
• Server-side logs on Nabu Casa’s / my.home-assistant.io’s end (no access from my side).
Question
Has anyone else run into the OAuth flow hanging specifically at “Link account” (as opposed to failing at the provider’s consent screen, or at credential entry)? Given it reproduces identically across two unrelated integrations, fresh credentials, browsers, and devices — with a completely clean HA log at the moment of failure — it feels like the failure is happening client-side in the my.home-assistant.io redirector itself, before it ever reaches my instance.
Happy to share any additional logs or screenshots if someone can point me to where to look.
If you have found an issue, it would need to be posted here:
¯\_(ツ)_/¯ Sounds like you are looking for…