Worx Landroid Package (Deprecated)

Share your Projects!
41

Landroid L v2.92, and not able anymore to perform actions even from the Android App.
I was able to push the raindelay with the curl command few times but now it seems I’m blacklisted on AWS.
Contacted the Worx support for that:

we’ve noticed on our backend that you’re using an unofficial client to connect to the IoT. Unfortunately this is not possible at the moment, because these clients poll the Landroid way too many times per day and they generate a lot of traffic on the server side.

For this reason, when the server detects such unusual amounts of messages, they shut down the client for 24 hours. We advise you to use the official app to connect to the IoT.

But not even able to push from Android App.

Now in homeassistant, I’ve created a Rest sensor, to retrieve directly from Worx API website the values.
Next step, to be authorized to push and to try it.

2 Likes
42

keep us updated on how that goes! :smiley:

43

Yeah I’ve noticed that too, before I rebuilt the HASSIO package, the server pushed A LOT of requests to internet…

44

When connecting to the AWS from a non-Worx application it will cause an IP ban for 24h

45

Status and commands are now fixed in the original repo. See https://github.com/virtualzone/landroid-bridge/issues/88

46

This is available in HACS: https://github.com/MTrab/landroid_cloud

Currently only sensors, start, stop and pause - but working on controlling schedules and rain delay as well.

No need for the Landroid Bridge container.

3 Likes
47

Thanks for letting us know :slight_smile: Looks promising. I notice there is no documentation yet on adding to Lovelace. What entities does it create? Hard to differentiate from the existing Landroid_bridge ones already installed. Thanks

48

It creates these;

sensor.landroid_[NAME_FROM_APP]_battery
sensor.landroid_[NAME_FROM_APP]_error
sensor.landroid_[NAME_FROM_APP]_status

And then it adds these services:

landroid_cloud.start
landroid_cloud.stop
landroid_cloud.pause

And it’s fully compatible with multiple mowers in one account.

2 Likes
49

Should I update my Landroid WR100SI to firmware 3.52 or stay on the shipped 3.0 firmware?
Is there any problems with the newest firmware?

50

New firmwares remove errors and bring new errors. There will never be a perfect firmware for ALL gardens. Maybe the old works better for you, and the new one for me. Or vice versa.

51

I understand, but I mean if the api works as it should with Home Assistant? So I don’t loose the connection to HA after update?

52

At the moment both integrations work flawlessly. That’s all I can say :slight_smile:

53

Have you tried with latest HA, 109.2?

54

yes …

1 Like
55

Your “Landroid Cloud” integration works with HA Core 0.109.2

56 
                               Azor

Home Assistant 0.109.3

WR130E

MTrab/ landroid_cloud

ScreenShot_20200503183639
ScreenShot_20200503183639661×905 164 KB

ScreenShot_20200503184448
ScreenShot_20200503184448803×497 21.2 KB

57

Hey, everybody. I updated the package. It now works based on Landroid Cloud by @BlackChart.
For details see here:

4 Likes
58

Sweet! Look forward to testing :slight_smile: Thanks @Barmalej

59

Great piece of work!

I have added the firmware as a sensor, just add this to the package landroid.yaml under sensor:

landroid_firmware:
        friendly_name: "Landroid Firmware"
        value_template: "{{ state_attr('sensor.landroid_m_status', 'firmware_version') }}"

and this under customize:

sensor.landroid_firmware:
      friendly_name: "Firmware"
      icon: "mdi:camera-iris"

PS
change landroid_m_status to the label used in your setup :slight_smile:

60

Thank you. I am now rewriting the package and add this attribute as an attribute to the Entitties card