Worx Landroid Binding

Is there actually any blocker why it is still in review?

If you filter for ā€œnew bindingā€ you will find even older PR which are not reviewed yet.
I guess, lack of maintainer time …

There is actually a show stopper : the inclusion of amazon mqtt sdk that weights on the binding size (~16Mb). I did not find any workaround.

Is it required to be part of the bindung or can it somehow be installed out of the binding?

Would it be possible to publish it as a market place binding until the issue is resolved?
That way at least a working binding is available for every user that only looks at the addons.

1 Like

Done Worxlandroid Binding [4.2.0;5.0.0)

4 Likes

Now, after I have sold my Landroid and got an Ambrogio…

Congratulations to make it official!

1 Like

This thread is some months old, so I am not sure if also the Vision models are supported now?
The bridge is online but now mower found.
I added manually but remains in ā€œinitializingā€ status.
I am on OH 4.3.4 and installed the binding from marketplace.

i create a modify version with Vision Support

you can find the jar file here

2 Likes

Great, thank you very much!
Installed and my vision was found and went online imediately.

Thank you very much for sharing. Worx(!) great.

Maybe you could push your repo tonthe opened PR in opehab/addons so we keep a single source base ?

1 Like

Any idea what the reason is for getting lots of these error messages?

Tried to subscribe on WX/MW/WR202E/9d90a24e-572b-4002-8cab-575dfef2718a/v1/commandOut when connection is closed

Thanks a lot first of all for this great binding!

One question: Does any of the Items show the next scheduled starting date/time at which the mower will actually run? It seems like LandroidMowerScheduleNextStart only shows the next date/time in the regular schedule, but not taking into account the automated schedule, nor any delays due to rain.

Hi,

I just recently discovered this a couple of weeks ago and it seemed to work good in the first place (got all expected data points, etc.). However, since 2 weeks it crashes my OpenHAB very often (as often at every 10 minutes, then again not for 1-2 days - I couldn’t figure out the circumstances when this happens).

Everytime, though, I have the following in my syslog:

2025-05-04T14:39:53.744774+00:00 openhab1 karaf[513013]: Exception in thread "Thread-134" java.lang.NullPointerException: Cannot invoke "java.util.List.size()" because "cfg.multiZones" is null
2025-05-04T14:39:53.744953+00:00 openhab1 karaf[513013]: #011at org.openhab.binding.worxlandroid.internal.vo.Mower.setStatus(Mower.java:328)
2025-05-04T14:39:53.745003+00:00 openhab1 karaf[513013]: #011at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.lambda$16(WorxLandroidMowerHandler.java:559)
2025-05-04T14:39:53.745038+00:00 openhab1 karaf[513013]: #011at java.base/java.util.Optional.ifPresent(Optional.java:178)
2025-05-04T14:39:53.745094+00:00 openhab1 karaf[513013]: #011at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.internalHandlePayload(WorxLandroidMowerHandler.java:558)
2025-05-04T14:39:53.745135+00:00 openhab1 karaf[513013]: #011at org.openhab.binding.worxlandroid.internal.handler.AWSClientThingHandler.onMqttMessage(AWSClientThingHandler.java:174)
2025-05-04T14:39:53.745477+00:00 openhab1 karaf[513013]: #011at software.amazon.awssdk.crt.mqtt.MqttClientConnection$MessageHandler.deliver(MqttClientConnection.java:48)
2025-05-04T14:39:53.745536+00:00 openhab1 karaf[513013]: Fatal error condition occurred in /codebuild/output/src3438736547/src/aws-crt-java/src/native/mqtt_connection.c:724: !aws_jni_check_and_clear_exception(env)
2025-05-04T14:39:53.745629+00:00 openhab1 karaf[513013]: Exiting Application
2025-05-04T14:39:53.745753+00:00 openhab1 karaf[513013]: ################################################################################
2025-05-04T14:39:53.745795+00:00 openhab1 karaf[513013]: Stack trace:
2025-05-04T14:39:53.745829+00:00 openhab1 karaf[513013]: ################################################################################
2025-05-04T14:39:53.745879+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_backtrace_print+0x4d) [0x790bfdcdce2d]
2025-05-04T14:39:53.745921+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_fatal_assert+0x44) [0x790bfdccbef4]
2025-05-04T14:39:53.745962+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x98b37) [0x790bfda98b37]
2025-05-04T14:39:53.746010+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xc9558) [0x790bfdac9558]
2025-05-04T14:39:53.746049+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xd6a70) [0x790bfdad6a70]
2025-05-04T14:39:53.746131+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xd6a25) [0x790bfdad6a25]
2025-05-04T14:39:53.746205+00:00 openhab1 karaf[513013]: message repeated 2 times: [ /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xd6a25) [0x790bfdad6a25]]
2025-05-04T14:39:53.746248+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_mqtt_topic_tree_publish+0x53) [0x790bfdad8193]
2025-05-04T14:39:53.746291+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xd218c) [0x790bfdad218c]
2025-05-04T14:39:53.746333+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_mqtt311_decoder_on_bytes_received+0x29c) [0x790bfdad3c5c]
2025-05-04T14:39:53.746376+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xd1840) [0x790bfdad1840]
2025-05-04T14:39:53.746415+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x123cde) [0x790bfdb23cde]
2025-05-04T14:39:53.746495+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x126245) [0x790bfdb26245]
2025-05-04T14:39:53.746540+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_websocket_decoder_process+0x32) [0x790bfdb26832]
2025-05-04T14:39:53.746584+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x122446) [0x790bfdb22446]
2025-05-04T14:39:53.746627+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(aws_h1_connection_try_process_read_messages+0x136) [0x790bfdaa68a6]
2025-05-04T14:39:53.746670+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0xa71e9) [0x790bfdaa71e9]
2025-05-04T14:39:53.746732+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x140b66) [0x790bfdb40b66]
2025-05-04T14:39:53.746775+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x135b5e) [0x790bfdb35b5e]
2025-05-04T14:39:53.746817+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x13627b) [0x790bfdb3627b]
2025-05-04T14:39:53.746857+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x13f5f2) [0x790bfdb3f5f2]
2025-05-04T14:39:53.746896+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x13a168) [0x790bfdb3a168]
2025-05-04T14:39:53.746936+00:00 openhab1 karaf[513013]: /var/lib/openhab/tmp/AWSCRT_15060357824765468151libaws-crt-jni.so(+0x2dd843) [0x790bfdcdd843]
2025-05-04T14:39:53.746975+00:00 openhab1 karaf[513013]: /lib/x86_64-linux-gnu/libc.so.6(+0x9caa4) [0x790c7469caa4]
2025-05-04T14:39:53.747017+00:00 openhab1 karaf[513013]: /lib/x86_64-linux-gnu/libc.so.6(+0x129c3c) [0x790c74729c3c]

Multi Zones is enabled in my setup and is also shown like that when the addon works correctly.

Any ideas?

Thanks, Daniel

Have you restarted openhab?
Have you reinstalled the binding?

Which version are you running?

There were some major changes with some issues on 4.3.4. solved on 4.3.5.

Yes and yes. I was using the version from the addon marketplace (dated November 2024). Is there a newer version somewhere?

4.3.5 (the behavior was the same on 4.3.4, though)

Can I also use this binding with a Kress? They are also using the Landroid Cloud.