You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of application_credentials some integrations use oauth2, for example home connect. As part of the setup process I as user need to enter my redirect_uri at the data provider website, but there is no way for me to easily find the redirect_uri which is send by application_credentials to the server, for oatu2h to work the redirect_uri I configure at the server should match the string send. For example see the documentation of home_connect at https://www.home-assistant.io/integrations/home_connect/, when my home assistant is disabled it says http://192.168.0.2:8123/auth/external/callback, http://homeassistant.local:8123/auth/external/callback, but what does HA send. Maybe add the redirect_uri as display string to the form asking client id/scecret
What version of Home Assistant Core has the issue?
core-2024.5.0
What was the last working version of Home Assistant Core?
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (application_credentials) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of application_credentials can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign application_credentials Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
Hey there @DavidMStraub, mind taking a look at this issue as it has been labeled with an integration (home_connect) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of home_connect can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign home_connect Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
As part of application_credentials some integrations use oauth2, for example home connect. As part of the setup process I as user need to enter my redirect_uri at the data provider website, but there is no way for me to easily find the redirect_uri which is send by application_credentials to the server, for oatu2h to work the redirect_uri I configure at the server should match the string send. For example see the documentation of home_connect at https://www.home-assistant.io/integrations/home_connect/, when my home assistant is disabled it says
http://192.168.0.2:8123/auth/external/callback, http://homeassistant.local:8123/auth/external/callback
, but what does HA send. Maybe add the redirect_uri as display string to the form asking client id/scecretWhat version of Home Assistant Core has the issue?
core-2024.5.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
application_credentials
Link to integration documentation on our website
https://www.home-assistant.io/integrations/application_credentials
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: