Automower Husqvarna

openhab_knx · July 16, 2022, 6:52pm

Hi everyone,

i would again need some hints out of the community.
Currently im am struggeling with the Automower binding.

I did the registration of the application + link of API and automower connect as described in the documentation. Added the Application Key + Email/PW in the binding to create the bridge but always facing:

grant type password to URL https://api.authentication.husqvarnagroup.dev/v1/oauth2/token failed with error code unauthorized_client, description Unauthorized client: grant_type is invalid

If i try manually with curl as posted in some other topics i can successfully get the mower ID. Currently i have no clue what is wrong.

Maybe someone can give me a hint. Thank you!

laursen · July 16, 2022, 6:55pm

Issue is known:

github.com/openhab/openhab-addons

[Automower] Binding does not work due to change in Husqvarna API Authentication

opened 10:53PM - 20 Jun 22 UTC

dobermai

bug

The Automower Connect API Authentication does not work anymore as they moved to …a new authentication method. (AppKey and AppSecret). Example of the new API: `curl -X POST -d "grant_type=client_credentials&client_id=XXX_Application_Key_XXX&client_secret=XXX_Applications_Secret_XXX" https://api.authentication.husqvarnagroup.dev/v1/oauth2/token` Apparently many/all(?) users are affected: https://community.openhab.org/t/automower-binding-g2/2854/102 ## Expected Behavior The Autower Addon should use the supported authentication method. ## Current Behavior The Automower Addon does not use a supported authentication method and the connectivity fails and no bridge can be configured successfully. ## Possible Solution Add a field for App Secret and change the Authentication method. Working example: `curl -X POST -d "grant_type=client_credentials&client_id=XXX_Application_Key_XXX&client_secret=XXX_Applications_Secret_XXX" https://api.authentication.husqvarnagroup.dev/v1/oauth2/token` ## Steps to Reproduce (for Bugs) 1. Create a new Automower Bridge 2. Use Valid credentials + Valid API Key 3. Bridge does not work and error from Husqvarna API is being logged > 2022-06-20 22:16:28.815 [ERROR] [oauth2client.internal.OAuthConnector] - grant type password to URL > https://api.authentication.husqvarnagroup.dev/v1/oauth2/token failed with error code unauthorized_client, description Unauthorized client: `grant_type` is invalid > 2022-06-20 22:16:28.824 [WARN ] [ternal.bridge.AutomowerBridgeHandler] - Unable to fetch automowers: Rest call failed: statusCode=-1, message=Unable to authenticate > 2022-06-20 23:16:29.134 [ERROR] [oauth2client.internal.OAuthConnector] - grant type password to URL https://api.authentication.husqvarnagroup.dev/v1/oauth2/token failed with error code unauthorized_client, description Unauthorized client: `grant_type` is invalid ## Your Environment Using OpenHAB 3.2.0 but also tried the development branch on Github of the openhab-addons (=3.3.0 afaik) with a fresh OpenHAB 3.3.0 installation from the website. ## Notes I tried to fix it myself but I couldn't get it to work with the OAuth Implementation provided by OpenHAB (the extension uses the built-in OAuth service) as I could not get it to change the grant_type. If there are any pointers how this could be achieved without rolling a new OAuth implementation myself, I'm happy to try to contribute. I am unsure if the 'old' username/password combination needs to be removed or if it needs to stay there for compatibility reasons.

openhab_knx · July 16, 2022, 6:57pm

Thank you for your quick response.

crnjan · August 14, 2022, 11:21pm

Adopted the login api change, please check automower jar, code changes - PR.

Michael_Grymonprez · August 16, 2022, 12:10pm

Hi.
I try the new version of the bindings but I still have the same interface with Username and Password.
I already made a clear-cache and restart but still.

Here is the configuration windows I have :

Thanks in advance for your help.

crnjan · August 16, 2022, 12:37pm

Hey!

Please first uninstall the “official” automower binding (from settings|binding) and then copy the provided jar above to addons folder.

Also, just in case, remove existing automower connect bridge and enter your app key&secret (you should see something as below):

At the end, please make sure to update bridge within your automowers (parent pbridge) so they use the newly added bridge.

That should do it. Please let me know how it goes.

Michael_Grymonprez · August 16, 2022, 1:33pm

Looks like I had download an old JAR. Don’t know.
Anyway all is ok now.
Many thanks for your help.

openhab_knx · August 21, 2022, 7:22pm

Thank you, working fine after installing the provided jar.

PEJ · October 25, 2022, 5:53pm

Hi I am new to the binding

tried the updated Automower binding, by crnjan’s link in post4

but i am redirected to JFrog login? (which i doesn’t have)

Then I downloaded addons .kar for 3.4.0.M3, and installed automower binding
Thing setup seems fine. And the thing goes online.

But channels/items doesnt work. I get 2 errors:
2022-10-23 20:18:00.863 [ERROR] [ore.common.registry.AbstractRegistry] - Cannot inform the listener “org.openhab.core.thing.internal.ChannelLinkNotifier@15a7b145” about the “ADDED” event: ‘boolean org.openhab.core.auth.client.oauth2.AccessTokenResponse.isExpired(java.time.Instant, int)’

2022-10-25 14:49:52.276 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NoSuchMethodError: ‘boolean org.openhab.core.auth.client.oauth2.AccessTokenResponse.isExpired(java.time.Instant, int)’

(However, i can make a working curl (as desribed Husqvarna API) in to get token + info

Is this somehow related to this:

github.com/openhab/openhab-core

[oauth] Token expiration is calculated from local time

opened 08:03PM - 16 Aug 22 UTC

closed 06:13AM - 22 Aug 22 UTC

jlaur

bug PR pending

When looking at openhab/openhab-addons#13274 I noticed a flaw in `AccessTokenRes…ponse`: It uses `LocalDateTime` for calculating token expiration. This means that the token creation time is dependent on system time-zone for being represented as an instant on the time-line. This has the potential to cause problems if system time-zone is changed or if the `LocalDateTime` provided for `isExpired` is generated differently than how `OAuthConnector` generates it. It would be less error-prone to use `Instant` for `setCreatedOn`, `getCreatedOn` and `isExpired`. I would propose to change this in five steps to avoid breaking addons: 1. In `AccessTokenResponse` change _createdOn_ internally to `Instant`. Add overload for `isExpired` taking `Instant` and deprecate current method. Deprecate `getCreatedOn` and add new `getCreatedOnAsInstant` (temporary, for migration). Change `setCreatedOn` to take `Instant` and adapt `OAuthConnector` accordingly (currently no addons use this method). 2. Adapt addons to use `getCreatedOnAsInstant` and new `isExpired` taking `Instant`. 3. Change implementation of `getCreatedOn` to the same as `getCreatedOnAsInstant` and deprecate the latter. Remove `isExpired` taking `LocalDateTime`. 4. Rename usages of `getCreatedOnAsInstant` to `getCreatedOn` in addons. 5. Remove `getCreatedOnAsInstant`. See also #2898.

?

laursen · October 25, 2022, 6:04pm

Yes, it is. To use the binding in version 3.4M2 or 3.4M3, you will also need core 3.4M3.

PEJ · October 28, 2022, 2:54pm

Updated to 3.4.M3, and everything works

ulij · November 28, 2022, 6:09pm

It stopped working for me with 3.4.M4 and upgrading to 3.4.M5 doesn’t work either.
If I got it right authentication now requires a redirect URL. Is the new authentication flow actually implemented?

Michael_Grymonprez · November 29, 2022, 5:22pm

Same here.