-
Notifications
You must be signed in to change notification settings - Fork 10
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
Comments
I have the same problem. |
Today, I have joined the Club. |
Me as well. I have an error: Failed setup, will retry: 400, message='Bad Request', url='https://api.myuplink.com/oauth/token' |
+1 |
1 similar comment
+1 |
oint today the same issue, any solution already available? |
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". |
I can reach my NIBE through https://www.myuplink.com/ but in Home Assistant every entity is unavailable, restarted HA without success.
Any ideas?
The text was updated successfully, but these errors were encountered: