I am pretty sure that one does not work with a Vision mower. The only working one for Vision is the altered version from @Bramante.
We encouraged him to make a PR to add that to the official binding, but I don’t think that has ever happened.
Ciao
I am working on the upgrade of the binding
you can give me an hand to make the binding works for other models
Please put the installed binding in debug mode and provide me the json
Hi All
i decided to re-write part of the current binding
the most problem is that the current binding map the json return by api call in a mapper and use it to give command and retrieve status of the mower
but vision models have another json and the mapper is broke and give the errors that the owner of the vision model has.
last time i only comment and rewrite some file (the map class and some part of the mapper) , but in this way, work for vision but not work anymore for the standard(wired) models
now i am in the process to rewrite the binding to be compatible with both and also others models
for do that i should rewrite and create new parts of the binding
that accept a generic json and based on some field decide if this is a wired model, vision or other (if exist)
i would like to ask you an help
simple to put the current (semi-official) binding in debug mode and provide me the json (without your sensitive data in the json) that return
in this way i have some test case to analyze
thanks for you feedback
FWYI, I have a strong feeling that current version could be merged in official repo targetting OHv5.2
Does anyone else keep getting this error?
Tried to subscribe on PRM100/****/commandOut when connection is closed
This has come up here before, but I don’t think there was a solution.
Yes, I’m getting the same warning
I don’t know if it’s the same problem but since a few days I again get the 405 error message (“Error calling Worx Landroid Api! HTTP Status = 405“). The binding worked well during the last season.
Hi All
I’ve finished integrating and working on the VISION models, and I hope I haven’t compromised compatibility with the WIRED models. I need someone to test them or provide me with the JSON file for the WIRED models so I can test them myself.
the link of the binary
here the github source
in the next days i want improve the binding adding some features, like “party mode”, the dynamic zones, cut edge, wifi lock for the vision models
Does it works with OH 5.1.4?
I have a wired model.
i have OH 5.1.4 and work for me
this is what i want know, i modified the binding to include vision models, so the wired should continue to work, but if i broke something i cannot know, because i cannot test it
you have 2 option to help
if you have installed already an old or currently semi-ufficial binding, put in debug mode and provide me the JSON (cleaned from sensitive data) from the API call, so i can test and simulate the wired version
if you want to try directly, you can install my modified version and check by yourself, if work i am very happy and i can do the pull request to the original one to include my modified, if not work, provide me the json and i check and fix it
I have installed your updated binding on the latest offical openhab version using a wire based worx roboter. It seems to work so far. I have sent you the JSON file as a private message.
Same with me “Error calling Worx Landroid Api! HTTP Status = 405” on openHAB 5.1.4 and binding version 4.3.0-SNAPSHOT
This seems to be triggered by a server side change.
I used to use GitHub - nefiertsrebliS/mqtt-landroid-bridge: Bridge for connecting the Worx (Kress or Landxcape) Lawn Mowers to IP-Symcon. · GitHub for some years now and this started logging
ERROR: {“message”:“The GET method is not supported for route api/v2/users/me. Supported methods: DELETE.”}
this weekend. So I went away from mqtt-landroid-bridge and asked the AI to create a new MQTT bridge using pyworxcloud · PyPI (the backend library used by HomeAssistant), which seems to work good at the moment as an in place replacement of mqtt-landroid-bridge.
How explain by RoRo
the error 405 is on an API call api/v2/users/me
this call is not more present in my modified version
the api call api/v2/users/me now accept only DELETE (in the bridge was used GET to retrieve some info, but not used in the binding), i think that Worx update the api, and only the delete of the account is used with this api call
It would be helpful to keep an overview in this thread for the official openHAB Landroid binding, if a separate thread were opened for each external version.
I face this 405 error also and will try to work on it.
I switched from the official 4.3 version to the 5.2 version of the binding, openHAB version snapshot 5.2 #5350.
Unfortunately the bridge does give me an error which I cannot resolve:
2026-05-07 10:20:01.500 [DEBUG] [id.internal.handler.WorxLandroidBridgeHandler] - Initializing Landroid API bridge handler.
2026-05-07 10:20:02.047 [DEBUG] [ding.worxlandroid.internal.api.WorxApiHandler] - URI: https://api.worxlandroid.com/api/v2/users/me
After disabling/enabling the bridge Thing I get an 405 error, following by an 403 error:
Android app is working fine, so the credentials are correct. Any idea?
BTW, thanks for not giving up on the long journey to have this binding merged 