just started using this binding and am impressed that it is working really good. Thanks a lot!
Just one question: resetting the blade time (in the app) isnāt reflected in the binding. I have seen this question in other homeautomation integration too, but I canāt find how to fix this for OH.
Problems since Firmware 3.26
SInce that update i allways get the message that Worx blocks me and i should wait 24 h .
I am using Oh 2.5 and test 3.2 but same Problem on both systems.
Same here, also with 3.26 firmware on Landroid WR141E. I am using OH 3.1.1, tried the v3.1-beta of the addon and also the last final v3.0
Same behaviour, always the error that I should wait 24h
I had the same issue and it turned out that the two values in the bridge just need to be altered to produce less calls to the Worx API.
I set them to: refreshStatusInterval=3600, pollingInterval=3600 and since then I was never blocked again.
This doesnāt mean that the telemetry data is only updated after an hour. The data is still pushed to the binding.
Just to share an info from my side: I also had the situation that I was blocked by Worx. For me it was due to a dumb error in one of my rules that in the end caused a lot of requests to my Landroid. Somehow āmy blockā was not removed even after a week.
What did the trick for me was to remove my Landroid from my Account and to just add it again (to the same Worx Account). It worked immediatedly and I even did not loose my 3 years warranty!
Hi,
I kindly wanted to ask whether this binding is still under development.
Itās working great so far (except for the āRefreshStatusRunnableā Errors I get frequently).
I found out about an API extension regarding live torque settings for the mower since firmware version 3.26.
Hello Nibi,
thank you for your great work. The binding worked straight away from the excellent examples and made my Landroid 167E settings/adjustments a breeze.
I ignore the regular messages in the log (RefreshStatusRunnable: Unknown error) because there are no negative effects to be seen.
I am also interested in the question of whether it is possible to find out which areas the Landroid has processed in the current or last run, i.e. a grid of points in which the mown areas are recognizable. (You can see it even after a few weeks on the lawn itself, but if the interface could deliver the dataā¦
Best regards from the Black Forest, Germany
Mercur
Iām not sure, whether Iām alone with this problem, but starting yesterday (2022-09-26 22:55) I observe the following error message in my log every 5 minutes:
I didnāt touch the configuration and the Android app and the Desktop-App work as expected with the (unchanged) credentials.
I can also login to Worx with this credentials.
Any ideas, whatās going wrong here?