Home Assistant automation blueprints for Worx Vision Cloud PLUS / Landroid Vision mowers.

This repository is separated from the custom integration repository on purpose:

• integration code lives in worx_vision_cloud_plus_github,
• automations and blueprints live here.

Prepared by Smart Service.

Import Blueprint

Manual import URL:

https://github.com/SmartServicePL/worx_vision_cloud_plus_automation/blob/main/blueprints/automation/worx_vision_cloud_plus/smart_mowing_schedule.yaml

Smart Mowing Schedule

The smart mowing blueprint estimates grass growth with a cool-season turf Growth Potential (GP) temperature model combined with rain, optional soil moisture, sunlight/UV data, and optional irrigation/fertilization corrections. It stores the estimated grass growth in an input_number, tracks the last full mowing cycle in an input_datetime, stores the next planned mowing time in another input_datetime, and starts the mower only when the lawn needs mowing. The automatic start threshold is tuned for robotic mowing: frequent light cuts, usually around 2-4.5 mm of estimated growth depending on the selected cutting height. The one-third blade rule is treated as a safety limit, not as the normal start threshold. In automatic mode it searches forecast-based mowing slots and prefers dry grass, no rain, and a sensible time inside the selected window preset. Forecast slots outside the configurable mowing temperature range are rejected; the default safe range is 10-25 C. If no safe slot exists in a selected daytime window, the blueprint chooses the nearest safe forecast slot between 06:00 and 22:00 instead of advertising an unsafe preferred hour. A night preset from 22:00 to 05:00 is available only when the user confirms that the mower has the FiatLux lighting accessory installed. When grass growth is already high, the automation prefers the nearest safe mowing window instead of waiting for ideal weather on a later day. Conditions and the hourly forecast are refreshed every 30 minutes and recalculated after completion or postponement; a notification is updated whenever this refresh changes the planned time. Every planned cycle starts with a dedicated edge-only command. Home Assistant then waits for the mower to return to the dock and recharge to at least 80% before sending the separate normal one-time mowing command. Temperature is checked again before that normal mowing command. Planning, completion and postponement notifications show accumulated grass growth and forecast conditions for the selected mowing time. Completion notifications also include actual start, finish and mowing duration. Manual mowing started from the WORX app is recognized after at least 10 minutes of mowing and updates the growth helpers when the mower returns to the dock.

Before enabling this blueprint, disable the mowing schedule in the WORX app so Home Assistant is the only scheduler controlling mower starts.

Before creating the automation from the blueprint, create three Home Assistant helpers:

• input_number for estimated grass growth, for example input_number.worx_estimated_grass_growth_mm.
• input_datetime for the last full mowing cycle, for example input_datetime.worx_last_full_mow.
• input_datetime for the next planned mowing time, for example input_datetime.worx_next_planned_mow.

Documentation:

• Smart mowing setup
• Helper package example

Blueprint path:

blueprints/automation/worx_vision_cloud_plus/smart_mowing_schedule.yaml

Requirements

• Home Assistant 2025.1.0 or newer.
• Worx Vision Cloud PLUS integration 1.0.11 or newer installed from SmartServicePL/worx_vision_cloud_plus_github.
• A lawn_mower entity for the mower.
• The one-time mowing service from the Worx Vision Cloud PLUS integration.
• Battery and rain entities from the integration.
• Temperature, rain/weather and sunlight/UV sources from Home Assistant.
• Optional automatic-irrigation setting for lawns that are watered regularly.
• Three helpers: estimated grass growth, last full mowing, next planned mowing.
• Optional soil moisture sensor.

Support

If this project helps you, you can support Smart Service:

Donate via Revolut

Privacy

Do not publish Home Assistant storage files, access tokens, serial numbers, raw API responses or screenshots showing exact garden coordinates.