Worx Landroid Binding

cypresss · October 18, 2022, 1:19pm

Yes! Same here since yesterday evening.

sihui · October 18, 2022, 1:26pm

Same here

rvogt · October 18, 2022, 3:29pm

At least I’m not the only one with that block message. Binding worked without problems for months now. Problems also started yesterday evening at around 19:40.

mito · October 20, 2022, 7:04am

Hi together, I am receiving this “blocked by worx” error for about 2 days now, so even after 24h I cannot connect any more. Any ideas?

EDIT: Or is the 24h-timer starting again on each try? During the last 2 days I tried to disable and enable the bridge Thing several times to see, if my 24 hours are over. Is this maybe the reason, why my 24h are not ending?

EDIT 2: I now tried to create a completely new Worx Account with a new Email-Adress and registered my Landroid there. I also removed the Binding, all Things and Items from OpenHab. After that I started again from scratch, but when I added the Landroid Bridge as a new Thing and enter my (new) account data, I receive “Error: Error calling Worx Landroid WebApi! HTTP Status = 404”. Full Details from log:

2022-10-20 13:22:08.444 [INFO ] [d.internal.WorxLandroidBridgeHandler] - Start retrieving AWS certificate
2022-10-20 13:22:08.505 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Iniialization error - class: org.openhab.binding.worxlandroid.internal.webapi.WebApiException
2022-10-20 13:22:08.507 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Iniialization error - message: Error calling Worx Landroid WebApi! HTTP Status = 404
2022-10-20 13:22:08.508 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Iniialization error - stacktrace: [Ljava.lang.StackTraceElement;@1b2d392
2022-10-20 13:22:08.510 [ERROR] [d.internal.WorxLandroidBridgeHandler] - Iniialization error - toString: org.openhab.binding.worxlandroid.internal.webapi.WebApiException: Error calling Worx Landroid WebApi! HTTP Status = 404

What is happening here? Any help would be appreciated…

sihui · October 21, 2022, 5:39am

Same here, no solution found yet.

cypresss · October 27, 2022, 6:41am

Seems like this time only openHAB is affected
DeskApp ist working without issues.

sihui · October 27, 2022, 6:47am

Interesting: not for me. openHAB and DeskApp are down.

2022-10-27 08_46_57-Einstellungen

cypresss · October 27, 2022, 7:18am

That’s strange…

PilotIoTSystems · October 27, 2022, 7:08pm

OpenHAB and DeskApp stopped for me too!
The DeskApp stopped only after I removed the mower from the account and then added it to the account again.

Matthias_Kaufmann · October 27, 2022, 8:02pm

I can confirm same issue without any changes on OpenHAB (3.3.0).

PilotIoTSystems · October 27, 2022, 8:15pm

The Android app works for me, but the Desktop App and OpenHAB (3.3.0) has stopped!
Previously (when OpenHAB Binding had already stopped), the Desktop APP continued to work, but after I reconnected the mower to the account, the DeskApp kept reporting an MQTT communication error.

Mercur · November 4, 2022, 8:01am

Hi,
the Landroid-Binding v3.2-beta works fine for me. No problems !
Refresh Status Intervall: 1200; Polling Intervall: 599 (max. Value by UI)

OpenHAB 3.3 (stable)

PilotIoTSystems · November 4, 2022, 8:46am

Is the problem solved?
It still doesn’t work for me…
Unable to unblock.
Previously it was set to:
refreshStatusInterval=60, pollingInterval=300
I also tried with this setting:
refreshStatusInterval=1200, pollingInterval=599
The end result is the same!
What values are set for you?

MyWorx Bridge
Status:
OFFLINE
COMMUNICATION_ERROR
Connection blocked from Worx, please try again in 24h!

cypresss · November 4, 2022, 8:51am

Interesting!
Maybe they changed the max. Polling Intervall on the API. I’ll give it a try…

sihui · November 4, 2022, 9:26am

Nope.

Same here.

Unfortunately, the maintainer of the binding did not find a fix yet:

github.com/nibi79/worxlandroid

AWS new authorization (Worx connection blocked, App operates normal, waiting does not resolve)

opened 08:34AM - 21 Oct 22 UTC

LukasA83

bug

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?

PilotIoTSystems · November 4, 2022, 9:43am

Thanks for the reply!
I’ll wait for it to be resolved then.

Why is it that the error occurs only in certain cases and does not cause an error in everyone? Strange.

Klaus_Schuster · November 17, 2022, 10:22am

same problem at the moment with oh3

hermanno · November 21, 2022, 3:56pm

same problem at the moment with oh3
d.internal.WorxLandroidBridgeHandler] - AWS connection failure

sihui · December 11, 2022, 7:02am

As a workaround I installed ioBroker, who are using a different technique to connect to the mower, on a virtual machine, installed the MQTT client and the Worx adapter and configured the datapoints to be sent to my openHAB instance via MQTT.
Even the new torque settings introduced by newer firmwares can be adjusted via openHAB now …

But I hope this is only a temporary workaround.

mito · December 13, 2022, 7:27am

Sounds interesting, sihui.
My mower is powered off now until March and I still hope that there will be native solution, but if not, I will maybe try your workaround then.
Would it be possible that you provide some more detailed step-by-step instructions for your configuration?
Is it possible to install ioBroker, the MQTT client and the Worx adapter on a Raspberry PI in parallel to an existing OpenHab installation or will this have any negative impacts related to stability, performance or whatever?