Worx Landroid smart home integration, free and open source
Worx Landroid robot mowers (Kress, LandXcape too): status, battery, rain delay, start, pause, home.
Published by guim31
- Devices
- Version 1.0.1
- Requires Gladys >=5.1.0
- ★ 0
Overview
This integration brings your Worx Landroid robot mowers into Gladys Assistant, and the mowers of the sister brands of the same cloud, Kress and LandXcape. Each mower becomes one device: its state, battery, rain delay and mowing times, with buttons to start, pause and send it back to its base.
It reads the mowers from the vendor cloud, where the app stores them: their state arrives in real time (MQTT), with a regular check as a fallback.
The integration is a community project, not affiliated with Worx or Positec. It was developed without the hardware: feedback is welcome on the repository's issues.
Requirements
- Gladys Assistant 5.1 or later.
- A mower already added in the Worx Landroid app (or Kress, LandXcape), and the e-mail and password of that account.
- Internet access from Gladys: the integration only talks to the vendor cloud.
Configuration
- In Gladys, open Integrations, find Worx Landroid and install it (or Install from
GitHub with
https://github.com/guim31/gladys-landroid). - In the Configuration tab, choose the brand of your app, then enter the e-mail and the password of the account.
- Choose the language of the texts: the names of the features (set when the mower is added) and the status and error texts. French by default.
- Leave Share the GPS position off unless your model has GPS (4G module, RTK) and you want its position in Gladys.
- Save. The Check the connection button lists the mowers found.
- Open the Discovery tab and add your mowers.
The tokens are kept in the integration's volume: a restart does not log in again.
The mower device
| Feature | Type | Detail |
|---|---|---|
| Status | text | Mowing, returning to base, charging, at the base, error, rain… |
| Error | text | The current fault, or "No error" |
| Mowing | yes / no | The mower is out working |
| Battery | % | |
| Charging | yes / no | |
| Battery temperature | °C | |
| Rain detected | yes / no | The rain sensor is wet |
| Rain delay remaining | minutes | Wait before mowing again after rain |
| Rain delay | minutes, settable | Wait after rain, 0 to 12 hours in 30-minute steps |
| Current zone | number | Zone being mowed (multi-zone models) |
| Mowing time today | minutes | Counted from the start of the local day |
| Total blade time | hours | Lifetime counter |
| Total mowing time | hours | Lifetime counter |
| Wi-Fi signal | % | -100 dBm or less = 0 %, -50 dBm or more = 100 % |
| GPS position | text | Only when enabled and reported by the model |
| Start mowing | button | |
| Pause | button | |
| Return to base | button | |
| Edge cut | button | Only the models that have it |
| Lock | on / off | The anti-theft lock (PIN) |
| Schedule | on / off | Turns the mowing schedule of the app on or off |
A feature only appears when the mower reports it: an older model without rain sensor has no rain features. Start, pause and return are buttons, not switches, so a voice assistant can never start the blades by mistake.
Widget
The Robot mower widget shows the state of one mower (with the fault or the rain delay when there is one), its battery and today's mowing time, and the Start, Pause and Base buttons (plus Edge cut on the models that have it). Choose the mower in the widget settings.
Scene triggers
- Mower error: the mower reports a new fault. Filter by mower and by kind of fault (trapped, lifted or upside down, outside the boundary, blade, battery or charge, charging base, cover open, other). Information passed on: mower name, error text, kind, error code. Rain is not a fault: use the Rain detected feature.
- Mowing finished: the mower is back at its base after working (end of schedule, rain or on request). Information passed on: mower name, session length in minutes, battery, back because of rain.
Scene action
- Mow once: a one-time mowing session outside the schedule, from 10 to 480 minutes, with or without the edge first. Only on the models with a one-time schedule.
Scene examples
- Warn me when the mower is stuck: trigger Mower error, kinds trapped and lifted → send a message "{{mower name}}: {{error}}".
- Mow after the sprinklers: when the watering scene ends, action Mow once, 60 minutes, edge first.
- Keep the lawn free for a party: when the "Garden party" mode starts, press Return to base and turn the Schedule off; turn it back on at the end.
Troubleshooting
- "The account refused the e-mail or password": check them in the vendor app, then save the configuration again. The integration does not retry a refused password on its own.
- "The cloud asked to slow down": the cloud answered "too many requests". Everything pauses (one hour, then longer) and resumes on its own. Do not restart the integration in a loop: that would make it worse.
- App and integration both stopped working: Worx may block an account for up to 24 hours. The fix the community documents: on the Worx website, unlink the mower from the account, then add it again in the app.
- Orange dot on the device badge: the real-time link is down; the mower is read every 30 minutes until it comes back.
- A command fails with "Real-time link down": commands need the real-time link; wait for it to come back.
- More detail: set the
LOG_LEVELenvironment variable of the integration todebug.
Limits
- Cloud only: the mowers have no local API. Without Internet, Gladys keeps the last values.
- Quotas, to avoid the vendor's temporary bans (no official number exists; these are the conservative values of the community clients): at most 50 commands per mower per day, one command every 1.1 s, 96 cloud requests per day, 5 password logins per day. The cloud is read every hour while the real-time link works, every 30 minutes otherwise; the real-time link reconnects after 1 minute, then waits longer each time, up to 30 minutes.
- Mowing time today starts at 0 the first day: what the mower mowed before the integration saw it is unknown.
- Schedules, zones and cutting height are not edited from Gladys; firmware updates and resets are left to the app on purpose.
- The Mowing finished and Mower error events need the real-time link: while it is down, a short session can go unnoticed.
- Developed without the hardware: the field reports of Vision and RTK owners are especially welcome.
Configuration settings
These are the settings Worx Landroid asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Your vendor account | section | No | Use the e-mail and password of the Worx Landroid (or Kress, LandXcape) app, where your mowers are already added. The integration reads them from the vendor cloud and is not affiliated with Worx or Positec. |
| Brand | select | Yes | The app your account was created in. |
string | Yes | ||
| Password | secret | Yes | |
| Language of the texts | select | Yes | Language of the feature names (set when the mower is added) and of the status and error texts. |
| Share the GPS position | boolean | No | Only for the models with GPS (4G module, RTK). Off by default: the position is personal data. |
How to install Worx Landroid in Gladys
- In Gladys, open Integrations: Worx Landroid appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-landroid:1.0.1), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/guim31/gladys-landroid.
Worx Landroid requires Gladys >=5.1.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Worx Landroid is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by guim31, not by the Gladys core team.
- Browse all integrations, native and community
- Build and publish your own external integration
- Source code on GitHub — source of this documentation