Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All entities suddenly unavailable #174

Open
nolenjohan opened this issue Dec 10, 2024 · 7 comments
Open

All entities suddenly unavailable #174

nolenjohan opened this issue Dec 10, 2024 · 7 comments

Comments

@nolenjohan
Copy link

I can reach my NIBE through https://www.myuplink.com/ but in Home Assistant every entity is unavailable, restarted HA without success.

Any ideas?

@robbsterr
Copy link

I have the same problem.

@PolarFox
Copy link

Today, I have joined the Club.

@BogdanVosnjak
Copy link

Me as well. I have an error: Failed setup, will retry: 400, message='Bad Request', url='https://api.myuplink.com/oauth/token'

@joysfera
Copy link

+1

1 similar comment
@Ounakas
Copy link

Ounakas commented Dec 27, 2024

+1

@MaikSunny
Copy link

oint today the same issue, any solution already available?

@BogdanVosnjak
Copy link

From what I was able to figure out so far, there seems to be something going on with MyUplink public API. It feels very sluggish and poorly responsive. I tried the workaround suggested in another thread (#171) by creating a secondary integration and then deleting the first one, but it only worked for a while (max. 1h) and then it died again.

My current solution was to switch to the core MyUplink integration. As you may know, there are two integrations available for MyUplink: this one (from Jaroschek) and the core one in HA (https://www.home-assistant.io/integrations/myuplink). The core one seems to handle the new situation a little better, so I switched to it. Unfortunately that means I lost all historical data. There are still dropouts, though. For example, yesterday evening it failed for 6 hours. But it always comes back on its own so I'm sticking to it.

One detail that was important for me was this: when you configure the integration, you NEED to allow changing settings, not only reading statuses, which means you leave all the tick marks by default. If I allowed only Read-Only access to API, the integration would fail with error "Incorrect OAuth2 scope".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants