Well done for both, API bridge AND mower are online now! Good job! Thank you for your efforts again.
Hi @glhopital,
API bridge AND Mower are online again and commands are passed throught… !!!GREAT JOB!!!
…expect the ZoneMeters this does not work…
BR
Michael
Hello,
Since I faced the error “HANDLER_INITIALIZING_ERROR multiple points” following the firmware update of my landroid WR141E, I decided to upgrade Openhab from 3.4.1 to 4.1.0-SNAPSHOT and use the latest worx landroid binding. I am facing two problems now:
- the Bridge is not created from the things file definition which was working fine in 3.4.1
- when trying to create the bridge manually from Web UI, I get the following error (edited)
COMMUNICATION_ERROR
Unexpected error deserializing
[
{
"id": ######,
"uuid": "#############",
"product_id": 49,
"user_id": ######,
"serial_number": "#############",
"mac_address": "#############",
"name": "#############",
"locked": false,
"firmware_version": "3.32.0+1",
"firmware_auto_upgrade": true,
"push_notifications": true,
"sim": {
"id": 4743,
"iccid": "#############",
"sim_status": "provisioned",
"pending_activation": false,
"contract_starts_at": "2020-08-06 00:00:00",
"contract_ends_at": "2026-08-06 00:00:00",
"created_at": "2020-08-06 09:49:51",
"updated_at": "2023-09-04 00:01:31"
},
"push_notifications_level": "warning",
"test": false,
"iot_registered": true,
"mqtt_registered": true,
"pin_code": "####",
"registered_at": "2020-07-25 00:00:00",
"online": true,
"app_settings": {
"cellular_setup_completed": true
},
"protocol": 0,
"pending_radio_link_validation": null,
"capabilities": [
"auto_lock",
"border_cut",
"digital_fence_settings",
"follow_border",
"lock",
"mqtt",
"multi_zone",
"multi_zone_percentage",
"one_time_scheduler",
"ota_upgrade",
"pairing_smartlink",
"pause_over_border",
"pause_over_wire",
"rain_delay",
"rain_delay_start",
"safe_go_home",
"scheduler_two_slots",
"unrestricted_mowing_time",
"zone_keeper"
],
"capabilities_available": [],
"features": {
"auto_lock": 3.25,
"chassis": "m_2019",
"digital_fence_settings": 3.25,
"display_type": "tube",
"input_type": "keyboard_tube",
"lock": true,
"mqtt": true,
"multi_zone": true,
"multi_zone_percentage": true,
"multi_zone_zones": 4,
"one_time_scheduler": 3.15,
"pause_over_wire": 3.26,
"rain_delay": true,
"rain_delay_start": 3.08,
"safe_go_home": 3.25,
"scheduler_two_slots": 3.15,
"unrestricted_mowing_time": true,
"wifi_pairing": "smartlink"
},
"accessories": {
"cellular": true
},
"mqtt_endpoint": "iot.eu-west-1.worxlandroid.com",
"mqtt_topics": {
"command_in": "PRM100/#############/commandIn",
"command_out": "PRM100/#############/commandOut"
},
"warranty_registered": true,
"purchased_at": "2020-07-17 00:00:00",
"warranty_expires_at": "2022-07-17 00:00:00",
"setup_location": {
"latitude": #############,
"longitude": #############
},
"city": {
"id": #############,
"country_id": 380,
"name": "#############",
"latitude": #############,
"longitude": #############,
"created_at": "2018-02-15 22:51:54",
"updated_at": "2018-02-15 22:51:54"
},
"time_zone": "Europe/Rome",
"lawn_size": 140,
"lawn_perimeter": 74,
"auto_schedule_settings": {
"boost": 0,
"exclusion_scheduler": {
"days": [
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
},
{
"slots": [],
"exclude_day": false
}
],
"exclude_nights": true
},
"grass_type": "festuca_arundinacea",
"irrigation": true,
"nutrition": null,
"soil_type": "ignore"
},
"auto_schedule": false,
"improvement": true,
"diagnostic": true,
"distance_covered": 365558,
"mower_work_time": 24872,
"blade_work_time": 24404,
"blade_work_time_reset": 3880,
"blade_work_time_reset_at": "2021-03-03 18:16:59",
"battery_charge_cycles": 363,
"battery_charge_cycles_reset": 0,
"battery_charge_cycles_reset_at": null,
"created_at": "2019-12-19 02:45:04",
"updated_at": "2023-07-31 22:05:53",
"last_status": {
"timestamp": "2023-09-04 15:20:19",
"payload": {
"cfg": {
"id": 0,
"sn": "#############",
"dt": "04/09/2023",
"tm": "17:20:17",
"lg": "en",
"cmd": 0,
"sc": {
"m": 1,
"d": [
[
"00:00",
0,
0
],
[
"16:00",
75,
1
],
[
"16:00",
75,
0
],
[
"16:00",
75,
0
],
[
"16:00",
75,
0
],
[
"16:00",
75,
1
],
[
"00:00",
0,
0
]
],
"dd": [
[
"00:00",
0,
0
],
[
"00:00",
0,
0
],
[
"00:00",
0,
0
],
[
"00:00",
0,
0
],
[
"00:00",
0,
0
],
[
"00:00",
0,
0
],
[
"00:00",
0,
0
]
],
"distm": 0,
"p": 0,
"ots": {
"wtm": 0,
"bc": 0
}
},
"mz": [
0,
0,
0,
0
],
"mzv": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"mzk": 0,
"rd": 180,
"al": {
"lvl": 0,
"t": 60
},
"tq": 0,
"modules": {
"4G": {
"enabled": 1,
"geo": {
"coo": [
#########,
#########
],
"rad": 33
}
}
}
},
"dat": {
"mac": "#############",
"fw": 3.32,
"fwb": 1,
"ls": 1,
"le": 0,
"conn": "4G",
"bt": {
"t": 31.6,
"v": 17.55,
"p": 13,
"nr": 363,
"c": 1,
"m": 0
},
"dmp": [
1.7,
-2.4,
259.6
],
"st": {
"b": 24483,
"d": 366825,
"wt": 24951,
"bl": 74
},
"act": 1,
"rsi": -75,
"lk": 0,
"tr": 0,
"lz": 0,
"rain": {
"s": 0,
"cnt": 0
},
"modules": {
"4G": {
"stat": "ok",
"vers": 2.55,
"batt": {
"t": 34,
"v": 4.11,
"l": 96
},
"mode": 1,
"geo": {
"stat": "in"
},
"gps": {
"coo": [
########,
########
]
},
"network": {
"status": "connected",
"mode": "EDGE",
"ICCID": "#############",
"IMSI": "#############",
"rssi": -75
}
}
}
}
}
}
}
]
java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 720 path $[0].app_settings
Is the error in any way related to the content of the app_settings?
PS: thanks for the great job maintaining this binding!
Can you tell me what does not work ? I have tested sending command to last-zone and it was good.
Yes, I think so. I’m going to take a look at it - should be easy to address;
Good morning @glhopital,
the last-zone command (multi-zones#last-zone, set with either 0 to 3) is working as expected. But i can’t set the definition when a zone begins (multi-zones#zone-1, set with the definition of meters e.g. 45).
There is no direct “fault” when i set the value for “multi-zones#zone-1; same for all four”. It seems that the values have been written but when i poll the mowers status they are set back to the value they had before…
Also when I send the mower via “multi-zones#last-zone” to the zone where i just changed the starting point, the mower will go to definition which was stored before
Other issure: I just have seen that the API brigde lost the connection over night “Reconnection to AWS unsuccessfull” (reconnect Interval: 250sec). Disabeling and Enabling the thing gets the bridge online again
Thx a lot, no problems so far after around 15 hours of operation on openHAB 4.0.2 stable.
Hi,
which settings you are using? My connection is lost after about 12h…
Reconnect Interval: 250sec
Refresh Status Interval: 300sec
Polling Interval: 3600sec
When I disable/enable the Bridge it works again.
Mine stopped working yesterday completely.
Nothing helps: disabling/reenabling the Bridge and Mower thing, restarting the binding, restarting openHAB, restarting the server 
Android app is still working, though …
I have same issue. My worx account was disabled. This is reason why I can not connect.@glhopital please, can you recommend settings?
I had the same issue and had to wait 24h before being able to restablish (including my dev environment - so no possibility to progress). I’m currently trying to study what can be done to avoid this and review appropriate settings.
Hi,
as per Update README.md with recommended polling/refresh values by BobMiles · Pull Request #86 · nibi79/worxlandroid · GitHub the docs contain a recommended setting. What settings did you use?
If you send a lot of requests you will be banned. So polling every five minutes or updating mower start times everytime an item changes will kick you out in no time.
Yep, same here: Blocked for 24h.
Binding and Worx App are offline 
My current settings (that worked before without getting banned):
Reconnect Interval: 300
Refresh Status Interval: 1200
Polling Interval: 3600
The recommended Reconnect Interval of “0” did not work for me. The Mower went offline after some time and did not reconnect on itself…
I’m currently working on it. Expect an updated version in the coming days.
3 Likes
The reconnect interval should not be causing the ban anyways. Do you have any rules sending commands to your mower on a regular basis?
Nope, like I said, these settings worked with a previous version of the binding and since @glhopital is working on a fix for this issue, I’m pretty sure it’s a bug in the current version.
Admittedly you are right. I got banned too, it just took a little longer…
This is for OH4, isnt it? I am still on OH 3.4.2 and dont want to update (never touch a running system). I also have the " HANDLER_INITIALIZING_ERROR multiple points" error. Could you also fix the binding for OH3 please?
My account is also blocked. The app still works. Why doesn’t it work with WORXX, which works without problems with other providers? I’m working with OH 4
Guys, give the binding maintainer some time, as you can see in a post above he is already working on it.
5 Likes