Custom Home Assistant integration for Worx Landroid Vision / Vision Cloud / RTK mowers.
This integration is built on top of the community pyworxcloud library and adds a cleaner Home Assistant entity layer for Vision mowers: mower controls, useful sensors, diagnostics, schedule calendar, RTK map rendering and live-ish robot position tracking.
Integration prepared by Smart Service.
If this integration helps you, you can support Smart Service:
- Native Home Assistant
lawn_mowerentity. - Start, pause and dock commands.
- One-time mowing controls with runtime, edge cutting and optional RTK zone selection.
- On-demand edge cutting button.
- Native firmware
updateentity with OTA install support when Worx exposes it. - Rain delay, schedule time-extension, lawn area and lawn perimeter number entities.
- Switches for firmware auto update, mower lock and native schedule.
- Battery, status, error and connectivity sensors.
- Useful maintenance, cloud/MQTT diagnostic and mowing-readiness sensors.
- Schedule sensor and Home Assistant calendar entity.
- RTK map camera rendered from the Worx private map API with a recent RTK trail overlay.
- RTK robot position as a
device_tracker. - Optional RTK address sensor using OpenStreetMap Nominatim reverse geocoding, disabled by default.
- Switches for Smart edge cutting, Save the hedgehogs and schedule edge procedure.
- Daily mowing progress, remaining progress, mowed area, lawn area and efficiency sensors when available from the API.
- Separate smart mowing automation blueprint repository.
- Polish and English translations.
- Optional raw payload entities for debugging, disabled by default.
- Open HACS.
- Add this repository as a custom repository.
- Select category
Integration. - Install Worx Vision Cloud PLUS.
- Restart Home Assistant.
- Go to
Settings > Devices & services > Add integration. - Search for
Worx Vision Cloud PLUS.
Copy this directory:
custom_components/worx_vision_cloud
to your Home Assistant config directory:
/config/custom_components/worx_vision_cloud
Then restart Home Assistant and add the integration from Settings > Devices & services.
Use the same e-mail and password as in the Worx Landroid app.
Supported cloud selector values:
worxkresslandxcape
Most users should keep SSL verification enabled.
The exact entity list depends on what your mower reports. Typical entities include:
lawn_mowermower controlbuttonrefresh, reset blade runtime, reset battery cycles and start edge cuttingcalendarmowing schedulecameraRTK mapdevice_trackerRTK robot positionsensorbattery, status, error, readiness, cloud connection, RSSI, schedule, rain delay, RTK map, RTK trail, daily progress, remaining progress, mowed area, runtime, efficiency and maintenance valuesbinary_sensoronline, IoT/MQTT registration, locked, rain, party mode and pause modeswitchfirmware auto update, mower lock, native schedule, Smart edge cutting, Save the hedgehogs and schedule edge procedurenumberrain delay, schedule time extension, lawn area and lawn perimeterupdatefirmware version, release notes and OTA install when supported
See docs/entities.md for a more detailed list.
Home Assistant blueprints and automations are maintained in a separate repository:
SmartServicePL/worx_vision_cloud_plus_automation
The smart mowing schedule blueprint lives there, together with its setup guide and the My Home Assistant import button.
For compatible Vision Cloud / RTK mowers the integration tries to read the private Worx map endpoint and renders a Home Assistant camera entity as SVG.
The map can include:
- mowing boundary
- excluded areas
- markers and station information when available
- current robot position from RTK payload
- recent RTK trail kept in memory by Home Assistant
The map is not a video stream. It updates when Home Assistant receives new data from Worx Cloud or when the integration refreshes cached API data.
The integration includes a disabled-by-default RTK address sensor. When enabled, it reverse-geocodes the mower's rounded RTK coordinates with OpenStreetMap Nominatim and caches the result for 24 hours.
Enable this entity only if you accept sending approximate mower coordinates to the reverse-geocoding provider. This is intentionally opt-in because RTK coordinates can reveal a home or garden location. Lookups are rounded, cached and throttled to respect the public Nominatim service.
RTK maps and address lookups can contain precise garden geometry and coordinates. Do not publish debug dumps, Home Assistant storage files, access tokens, serial numbers, raw API responses or screenshots showing exact locations.
Before opening an issue, remove private data from logs and screenshots. See SECURITY.md.
The Worx / Positec cloud API is not officially public. Some endpoints used here are reverse-engineered and can change without notice. This is a best-effort custom integration, not official Worx software.
- Uses
pyworxcloud. - Integration prepared by Smart Service.
