There is a channel for Cut-To-Edge. When the mower starts and this channel/linked item is set to On, Cut-To-Edge is started first, followed by mowing for the remaining time.

There is a channel for Cut-To-Edge. When the mower starts and this channel/linked item is set to On, Cut-To-Edge is started first, followed by mowing for the remaining time.

Is there any news about openhab 5 and the binding?
There is a download link in the marketplace topic for the 4.3 jar.
Drop it into your addons folder.
This should work fine in OH5:
Hey,
facing the mower thing (Vision) in state ‘Initializing’ while using latest 4.3 Snapshot jar. Any ideas?
Thx!
Hey there, I got a question about the error code item. When I start the mower in the dark (it does not come with the optional lighting) I would expect the error code item to say “insufficient light” as this is what the app also reports. I would like to evaluate this particular error but what the error code item does is to show “null” and then (one second later) it switches to “no error.”
Any thoughts on this? Thank you in advance! Olli
Is it possible to use this binding with openHAB 5.0.1? I am not able to install it via Community-Marketplace.
Thx. I can confirm that it is working this way.
Is there any progress or blocked again regarding the SDK?
Unfortunately not. No décision taken.
Good news, I think we’re close to have it finally merged. See PR
How is the progress?
Hi everybody,
I am running openHAB 5.0.3 and I’m having trouble with the Worx Landroid Binding (Version 4.3.0.202408061003 / Snapshot) to include my Worx WR303E (Cloud Vision RTK whatsoever).
While the Bridge connects successfully, the Mower Thing stays in HANDLER_INITIALIZING_ERROR. The logs show a validation error regarding the Channel UID naming conventions in OH5:
java.lang.IllegalArgumentException: UID segment 'multi-zones#allocation-%d-0' contains invalid characters. The last segment of the channel UID must match the pattern '[\w-]*(?:#[\w-]*)?'.
It seems the %d placeholder in the WorxLandroidMowerHandler.java (line 163) is being passed literally instead of being replaced by an index, or the naming convention itself is no longer allowed in OH5 due to the % character.
I have already tried:
Clearing the cache (openhab-cli clean-cache).
Reinstalling the binding via karafconsole as it’s not available in the marketplace.
Creating the thing manually via .things file.
Manually editing the YAML code (the error persists as it seems to be hardcoded in the initialization routine).
Is there a patched version available for openHAB 5, or could someone point me to a workaround to skip the multi-zone channel initialization?
Thanks in advance!
See some posts above.
I’ve already installed the Version from above (4.3.0.202408061003)
https://github.com/clinique/marketplace/raw/refs/heads/main/org.openhab.binding.worxlandroid-4.3.0-SNAPSHOT.jar
This one:
This link
is dead (404)
It is (was) the only one which works with the Vision modell AFAIK.
Does this one work?
It worked once but never received updates after first initialization. So i upgraded my OH to last stable version 5.1.3, purged the manuall installed Worx Landroid Binding and installed it via GUI from market place. Now i get a new exception on the Mower thing (Bridge Thing is “online”)
Cannot invoke "String.isEmpty()" because "this.dt" is null
I’ll have a look into it. (Falling back to your linked version resulted in the same Exception)
Full Stacktrace:
2026-04-10 11:29:50.548 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing ‘worxlandroid:mower:90323c16d8’: Cannot invoke “String.isEmpty()” because “this.dt” is null
java.lang.NullPointerException: Cannot invoke “String.isEmpty()” because “this.dt” is null
at org.openhab.binding.worxlandroid.internal.api.dto.Payload$Cfg.getDateTime(Payload.java:131) ~[?:?]
at org.openhab.binding.worxlandroid.internal.vo.Mower.getLastUpdate(Mower.java:403) ~[?:?]
at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.updateStateCfg(WorxLandroidMowerHandler.java:453) ~[?:?]
at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.processStatusMessage(WorxLandroidMowerHandler.java:185) ~[?:?]
at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.initializeData(WorxLandroidMowerHandler.java:128) ~[?:?]
at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.initialize(WorxLandroidMowerHandler.java:102) ~[?:?]
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:580) ~[?:?]
at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:149) ~[?:?]
at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]