Nabu Casa Account link gives "Too many requests" when auth for NVent Raychem Senz integration

After the latest update my Home Assistant lost track of my Raychem Nvent Senz floor heating controllers. This happens every now and then, so I did what I usually do: uninstalled the integrationen, restarted, readded and logged on according to the authentication flow. But now, after loggin in to raychem and choosing “Yes” allow I get redir to https://account-link.nabucasa.com/ where I get “Unexpected response Too Many Requests”. I have tried from different browsers, private browser to exlude cookies, changed where I do it from (ip, device). I have paused and tried again a different day.

I cant get around this to make the integration re-installed. Any advice?

Exact workflow:

  1. Settings/Devices and services/Integrations/Add integration
  2. Pick nVent Raychem Senz from the list
  3. Redirect to Senz . Login works. I allow access and click “Yes, Allow”
  4. Redirect to Nabu Casa Account Link
  5. Page shows error " Oops… an error occured Unexpected response Too Many Requests"

Version-info:
Home Assistant OS on Raspi 4

  • Core: 2025.12.4
  • Supervisor: 2025.12.3
  • Operating System: 16.3
  • Frontend: 20251203.3

Integration:
[nVent RAYCHEM SENZ - Home Assistant]
(nVent RAYCHEM SENZ - Home Assistant)

Any log-file-entries related to this, which you could share ?

I tried finding somehting, but at least the core logs shows no activity. I think it is because the install integration flow starts with the authentication, and when that fails no install is made. The error appears to occur in the account-linking on nabu casa side. But any advice on where to look is welcome, since the lack of logs is frustrating…

Nabu Casa tech support should be able to tell you how many times you hit their server before it objected, and if there is a design flaw that you have exposed.

Nabu Cass kindly referred me to the developer, and it seems they are aware:

1 Like

I’m running into this issue with nabucasa as well, but for a regular Tibber integration. I’m a bit unsure why we even need this nabucasa thing.

Shouldn’t it be able to just connect to my home assistant instance to finish the whole setup? This whole issue came after updating HA to 2026.1.0 BTW. It used to work fine before.

6 Likes

I have the Issue since updating to 2026.1 with Tibber…

3 Likes

As a workaround, I’ve found that following the instructions at Tibber - Home Assistant gets things going again. That is, presuming your HA instance is publicly reachable of course.

3 Likes

I also ran into this with 2026.1 with Tibber…

2 Likes

Count me in on the Tibber integration after upgrade of HA to 2026.1.0

2 Likes

Thanks for sharing!

And the redirect URL is this one?
https://•••••••••••••••••.ui.nabu.casa/redirect/oauth

Yep, count me in as well for tibber. Same issue since 2026.1.0

Having the same issue with Tibber since 2026.1.0 upgrade…!

same here after upgrade to 2026.1.0

1 Like
1 Like

THX. Works fine for me.
I used Link to OAuth2 Authorize Callback – My Home Assistant for redirect URL

I followed the same instructions but I didn’t get it working :frowning:

Is your system open to Internet or not?

https://community.home-assistant.io/t/oops-an-error-occured-unexpected-response-too-many-requests/972077/26

Tibber has now increased the rate limit, so it should now work without having to add a custom client id.