-
Notifications
You must be signed in to change notification settings - Fork 20
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
AWS new authorization (Worx connection blocked, App operates normal, waiting does not resolve) #73
Comments
No ideas from my side, but I have this problem also since 3 days. |
I also have no idea |
Same here, there are several more reports: https://community.openhab.org/t/worx-landroid-binding/95246/223 |
The same thing happened to me... I did the following:
|
But did it solve the issue in Openhab, @PilotIoTSystems ? |
@LukasA83 No, there is no solution yet! It still doesn't work! |
Have do some research, API Req./Resp. looks good, get Bearer token + mqtt_endpoint (from .../users/me) + certificate (from .../users/certificate) but it seems that there is no mqtt connection req. to the mqtt_endpoint.
I tried your 3.2-beta binding |
When you get the response with the certificate you get also a value 'active' and this value is false. And when the certificate is not valid/active it is not possible to get a mqtt connection. Some other Implementation (e.g. iobroker) use a solution without certificate but I have not been able to solve it this way yet. |
and I also asked POSITEC (provider of the API) for support but so far without success! |
hmmm, thats true, when I have a look to my older logs it was always active:true. Last time at the 6th Oct. and this problem hits only a few users? strange. what's your status? still active:true? had a look to the received certificate and it looks good so far.
yeah, the support is unfortunately not that fast 👎 |
No it's also not working for me and I think it's not working for all users in generall!? |
@mitch-geht-ab When I had the problem with MyWorx Bridge (OpenHAB 3.3), the Desktop APP was still working fine. After the mower re-pair, the Desktop APP also stopped. EISHA wrote to this (sorry for the German language): "Entscheident ist das active:false im certificate. Offenbar zieht Positec nun die mqtt Verbindung ohne Zertifikat durch." |
@mitch-geht-ab |
@nibi79 |
Yes that is what I meant:
|
Looks like the awsiot sdk for java does not support adding custom auth headers via websocket. Not sure if there is any alternative?! |
you're right! and there are alternatives but I didn't get them to work until now... |
I'll try to publish a new repository with a small testproject tomorrow .... maybe someone else has an idea and can help me... |
as promised yesterday -> https://github.com/nibi79/WorxTest in this testproject I use another library: Here it's possible to set header information, but I'm not sure how to handle the token.
Maybe someone else has a solution or an idea |
Sorry... no connection |
[Completed exceptionally: software.amazon.awssdk.crt.mqtt.MqttException: The connection was closed unexpectedly.] ErrorCode 5134 |
I also spent couple of hours on this, but ended up with the same error. Is there anyway to get more detailed logs on the sdk used to connect to aws? |
@nibi79: I spent some time and got the MQTT connection working, see my pull request on the test repository: Hopefully you can continue from there. |
How can community support @nibi79, @LukasA83, @mitch-geht-ab , @PilotIoTSystems ? |
I'm still workig on this but I think i have a interims solution for this, |
Great to hear! |
hi all, @mitch-geht-ab, @sihui62, @LukasA83, @PilotIoTSystems, @MatzeMuc86 I have put in a lot of effort and managed to create a new version of the binding. However, I had to implement some workarounds to make it work properly:
I may be able to resolve these issues in a different way in the future. As of now, the software works with OH 3.4.1 and OH 3.4.2, but not with OH 3.2 (I had to update my installation to 3.4.1). I am unsure about compatibility with other versions of OH. I hope your mowers are not still in hibernation. Please give your feedback after testing this new version -> https://github.com/nibi79/worxlandroid/releases/tag/v3.4.1-beta |
don't forget to set the loglevel -> |
I cannot set reconnect to 0 as @olflo. I've updated my binding with the latest version from github repo (it is version 3.4.1). @foobar26 version is unreachable (it was version 3.4.0.202304130533). I didn't tried to set reconnect to 0 with the latter so I can't tell if it is a version problem or else. |
Do you use .thing files or the GUI to configure your things ? |
GUI |
same |
ok, I only use file-based configuration, so I will check this. |
I deleted my repo after @nibi79 integrated my changes. @olflo @cinadr did you try to clear the Openhab cache (see https://community.openhab.org/t/clear-the-cache/36424)? |
My instance is running now for over a week without any issue. |
same for me. have also cleared the cache with
interestingly the worx binding disappeared and I had to reinstall it with
but with this settings
oh (3.4.2) complains about the 0
just to clarify, the md5 of the jar is
|
Maybe something went wrong by uploading the jar file. I have just uploaded the jar again. MD5 6ABEA9CE05EC7C96652736B73FEE9434 |
@mitch-geht-ab thank you for the hint Let me know if this jar works for you |
yes... now it works with
please increase the version number with any patch... or switch from semantic versioning to a mix of semantic for major and minor and replace patch 0.0.x on a daily timestamp base 0.0.yyyymmdd |
After changing the pollingrate to 3600 (hint from foobar) my Binding Version 09.03.23 works fine since 5 days ! By the way: |
'03' was a typo |
Hi, I just installed the new version but without success... `2023-04-24 13:12:32.789 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'worxlandroid:worxlandroidBridge:f86c460516' changed from UNINITIALIZED to INITIALIZING 2023-04-24 13:12:34.687 [ERROR] [worxlandroid.internal.mqtt.AWSClient] - Exception: software.amazon.awssdk.crt.mqtt.MqttException: The connection was closed unexpectedly.` |
Please check your settings are changed according to the above comments. Issue is not resolved just by using a different version of the binding. |
Hi @foobar26 I tried it today again without any change. And it works. Crazy. Thanks for your support. |
WIth the last binding version I had a more or less stable connection until the 26th.
I detected it today by accident because my improved rain-delay-rule hadn't worked as expected. But it was the offline UMV. I thought there is an exception to handle a diconnect from AWS? my settings are |
I do have kind of same error with MD5 6ABEA9CE05EC7C96652736B73FEE9434 of binding.
and settings are: |
New AWSClient Error
Resolveable with an bundle:stop bundle:start... so can it be fixed in the binding? |
Maybe it would be enough to disable and re-enable the bridge!?
I am sure that this is possible. I'll take a look at this when I have time. |
probably it is, but bundle stop start is also fast. today another exception, maybe also handable with exception handling in the code
was also resolvable with bundle stop start ;) maybe you can implement an exception handler, when triggered check for x-times in an interval of y-minutes to reconnect. |
For me too:
|
Hello, This summer I did not yet use the Plugin for my robomower because it got all the time blocked. I checked the Manual and it says set this values to avoid beeing blocked: refreshStatusInterval | 1200 But if I set pollingItnervall to 3600 i get the error: Any ideas what should I do? |
I guess because of the extended time you did not use the binding you need to upgrade your Thing: delete it and recreate it. You should use the same UID to not have to adapt all your linked items. |
Are you sure you are using the right version (https://github.com/nibi79/worxlandroid/releases/tag/v3.4.1-beta)? Could you please double check? |
Sometimes a restart of the openHAB service is needed if I remember correctly (I am not on 3.x anymore). If you can't get it to work you should open a thread in the community forum as this github issue is for our fellow developers and should not be used for individual setup problems. |
Short feedback, it was really an issue of picking the right version. So not yet relevant for this thread. |
Hi,
Since around 1 week I got the blocked message in the binding. I tried to wait 48 hours and also remove and add back the mower to my worx account without success. The Worx app operates normally.
Here is the log:
2022-10-21 10:20:42.915 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Connection blocked from Worx, please try again in 24h 2022-10-21 10:22:50.060 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://id.eu.worx.com/oauth/token 2022-10-21 10:22:50.692 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"token_type":"Bearer","expires_in":3600,"access_token":"***hidden for debug log***","refresh_token":"***hidden for debug log***"} 2022-10-21 10:22:50.696 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://api.worxlandroid.com/api/v2/users/me 2022-10-21 10:22:50.858 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"id":267139,"user_type":"customer","push_notifications":true,"location":null,"mqtt_endpoint":"a1optpg91s0ydf-ats.iot.eu-west-1.amazonaws.com","actions_on_google_pin_code":null,"created_at":"2020-03-27 20:33:54","updated_at":"2022-10-21 04:45:35"} 2022-10-21 10:22:50.874 [INFO ] [d.internal.WorxLandroidBridgeHandler] - Start retrieving AWS certificate 2022-10-21 10:22:50.877 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://api.worxlandroid.com/api/v2/users/certificate 2022-10-21 10:22:51.024 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"id":160983,"pkcs12":"***hidden for debug log***","active":false,"created_at":"2020-04-10 11:21:16","updated_at":"2020-04-10 11:21:16"} 2022-10-21 10:22:51.034 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Connection blocked from Worx, please try again in 24h 2022-10-21 10:23:43.735 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://id.eu.worx.com/oauth/token 2022-10-21 10:23:44.169 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"token_type":"Bearer","expires_in":3600,"access_token":"***hidden for debug log***","refresh_token":"***hidden for debug log***"} 2022-10-21 10:23:44.175 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://api.worxlandroid.com/api/v2/users/me 2022-10-21 10:23:44.236 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"id":267139,"user_type":"customer","push_notifications":true,"location":null,"mqtt_endpoint":"a1optpg91s0ydf-ats.iot.eu-west-1.amazonaws.com","actions_on_google_pin_code":null,"created_at":"2020-03-27 20:33:54","updated_at":"2022-10-21 04:45:35"} 2022-10-21 10:23:44.251 [INFO ] [d.internal.WorxLandroidBridgeHandler] - Start retrieving AWS certificate 2022-10-21 10:23:44.254 [DEBUG] [nternal.webapi.request.WebApiRequest] - URI: https://api.worxlandroid.com/api/v2/users/certificate 2022-10-21 10:23:44.387 [DEBUG] [nternal.webapi.request.WebApiRequest] - Worx Landroid WebApi Response: {"id":160983,"pkcs12":"***hidden for debug log***","active":false,"created_at":"2020-04-10 11:21:16","updated_at":"2020-04-10 11:21:16"} 2022-10-21 10:23:44.459 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Connection blocked from Worx, please try again in 24h
Any idea?
The text was updated successfully, but these errors were encountered: