-
Notifications
You must be signed in to change notification settings - Fork 30
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
I get this error message when i put in my credentials #18
Comments
Hi @JePeSWE the first thing I'd verify is whether your Home Asisstant's external URL matches what you specified as the authentication callback domain for your Strava API application (see screenshot). In particular, as the name suggest, the authentication callback DOMAIN's syntax is slightly different from your HA external URL. In fact, the domain is only a particular fraction of the URL. It’s anything between the http:// (or https://) and the first “/” of the path in your URL. E.g. if you entire external URL is https://xyz.ui.nabu.casa/, the the callback domain (which you have to put into Strava) is “xyz.ui.nabu.casa” I hope that helps. |
I just hit the same problem @codingcyclist. What I realised is it will throw that error if you try to add the integration while using the internal URL in your browser / app (homeassistant.local). When I pointed the browser at the external URL, and then tried adding the integration again, it worked fine. |
I've got this working fine on an existing setup, but when I try to set up on a new device (complete fresh build) i manage to get to the authorisation page...but when clicking authorise, I get a screen saying the following 500 Internal Server Error Server got itself in trouble Is this a Strava issue? or something on my own end? Please ignore...after googling a bit more, and finding someone else with the same issue...it was because when selecting the client secret...an extra space was copied and therefore pasted...but now all good.... Thanks again for a great integration....lets me bore my mates even more than I usually do |
did you solve this problem?: |
Same error here, it's not working: {"message":"Bad Request","errors":[{"resource":"Application","field":"redirect_uri","code":"invalid"}]} |
{"message":"Bad Request","errors":[{"resource":"Application","field":"redirect_uri","code":"invalid"}]}
This addon dont work?
The text was updated successfully, but these errors were encountered: