Closed Pyrdon closed 1 month ago
Hey there @pajzo, @astrandb, mind taking a look at this issue as it has been labeled with an integration (myuplink
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
myuplink documentation myuplink source (message by IssueLinks)
This message is intentional. The integration is designed for monitoring AND control of myUplink devices.
As a workaround you can create an additional account with myUplink and share access from your main account in read-only mode to your new account.. Then create API credentials (R/W) in your new account and use those in HA.
Well there is no error message saying why the authentication process was not accepted. I would expect it to indicate it needs the change permissions or support not allowing it. As it is now it took me a while and lots of trial and error to discover this was the root cause.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
I want to be able to connect to My Uplink to get status of my heat pump, but not make any changes. It however fails to authenticate unless I also include the "Make changes to your system" credential. Following this the integration says "Failed to setup: Incorrect OAuth2 scope"
What version of Home Assistant Core has the issue?
core-2024.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
MyUplink
Link to integration documentation on our website
https://www.home-assistant.io/integrations/myuplink
Diagnostics information
Diagnostics.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response