-
Notifications
You must be signed in to change notification settings - Fork 53
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
Authentication using Husqvarna-API takes endless... #187
Comments
Yes, it seem very long foir the integration to connect :) Could you put the plugin in debug mode and share the home assistant logs please ? |
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht Logger: gardena.smart_system 404 : {r['errors'][0]['title']} - {r['errors'][0]['detail']} |
Hum, have you activated the authentication api in the husqvarna website ? Did you set the level of the logs to debug for the plugin ? (think about hiding/masking your client id client secret if there are in the logs). |
I have the same problem, I deactivated the integration for now (as there's not much gardening going on currently). The Husqvarna Website is not too snappy either, but I can login there and the example 'curl' commands for my application get me an authorization token. But when I try the OpenAPI SwaggerUI at https://developer.husqvarnagroup.cloud/apis/gardena-smart-system-api?tab=openapi, I also get errors - usually "TypeError: Load failed": Using curl from my machine, this one yields something:
So it seems as if Husqvarna/Gardena did something with their API, although I don't know what. Somehow my authentication doesn't seem to work, as I can use the "authorize" button on the SwaggerUI, but there I won't get any valid response (again: "TypeError: Load failed"). But using curl (redacted API key here, but I used mine from the Website) I get:
|
hum, that is a strange behaviour. I am not sure the |
Yes, I was talking of these 2 APIs |
What I wanted to say is, that the API call via curl does work (without authentication when checking the 'health' endpoint), but their website - or the SwaggerUI frontend on the site - does not work. I can generate new authentication Tokens via curl, but they can't be used within the SwaggerUI, always resulting in the error message "TypeError: LoadFailed". Even when I authorize with both API key (see below) and a fresh token. I generated a new client secret and tried again, which did get me a fresh token. My main problem was choosing the right UUID for the API key. In the documentation they call it , but it is not the "client secret", it's the "client id" from the developer portal. When I tried to use that, it did indeed work - but I don't have any locations set up yet:
So maybe the lag in the HomeAssistant integration might come from that. |
i have the same issue here. try to connect to api does not work
|
Same here. No luck installing the api, takes forever until it falls. |
I have this Problem too. I installed the api again, deleted the authentication and tied to register ha again. The connection originally worked, then I had to change the gateway because the mower had a defect and was replaced. I deleted the old gateway and could not connect the new gateway. I get the same error after endless authentication. |
Could you give it another try woth latest version please ? (1.1.0-rc3) |
I just released version 1.1.0. Can you try with this version please ? |
i had no luck. you can find the log attached. @grm : thank you for your support!
|
For me as well, results are the same errors as posted above. My logs looks the same. |
Got it working… email adresses for Gardena Gateway and husqvarna API Must be the same, otherwise you get in the endless authentification loop |
same issue here, email is the same for app and API |
any update on this issue ?
|
I was not aware of that ! That is a very strange behaviour ... @andyblac can you it a try to see if that solve your issue ? Or is it not your case ? The 404 seems very odd, as this is a standard endpoint and is not spefic to your context (especially for the token) which may. why the solution from @Slowmover321 may work. |
It already uses the same address for both, so is not relevant to my issue. |
ok I just deleted my account from both dev and main husqvarnagroup and then setup them from scratch, that seemed to have sorted it, I can now use the integration, so it must have been a server side issue. Thanks for your help. |
....and I really mean: ENDLESS!
Ongoing since 3 days (yes, I forgot about it 🙈)
Any suggestions?
The text was updated successfully, but these errors were encountered: