Robot Mower Scheduler

Blueprints Exchange
, ,
1

Hi all — I put together a scheduling blueprint for Mammotion robot mowers using the Mammotion HACS integration.

This blueprint is designed for Luba/Yuka-style setups where each mowing area is exposed as a Mammotion area switch, for example:

switch.my_mower_area_area_1
switch.my_mower_area_area_2
switch.my_mower_area_area_3

It supports 1–6 active zones, cycles through them in order, skips rain/wet-lawn sessions, and supports up to 4 daily mowing sessions.

What it does

  • Cycles through 1–6 mowing zones in order using a persistent input_number tracker.

  • Supports a configurable Number of Active Zones, so you do not need exactly 6 zones.

  • Supports up to 4 configurable daily session times.

  • Supports 1 or 2 zones per session.

  • Uses Mammotion area switch.* entities to select the zone.

  • Uses mammotion.start_mow with configurable Mammotion mowing parameters.

  • Supports configurable:

    • blade height
    • working speed
    • cutting path angle
    • cutting path mode
    • cutting path angle mode
    • mow order
    • no-go zone mowing laps
    • obstacle detection
    • path spacing
    • perimeter mowing laps
    • rain detection during mow

  • Skips mowing when the selected weather.* entity reports rain-like conditions.

  • Adds a configurable wet-lawn delay after rain.

  • Re-checks weather before Zone B when mowing 2 zones in one session.

  • Includes a manual skip toggle.

  • Includes a one-time pause recovery command in case the mower pauses right after undocking before beginning work.

  • Optional night-light setting support for mowers that expose a Mammotion night-light switch.

Mammotion note

This blueprint uses the area switch entities created by the Mammotion HACS integration.

Before each zone, the blueprint:

  1. Turns off the active area switches.
  2. Waits briefly.
  3. Turns on the target area switch.
  4. Waits for the mower/integration to register the zone.
  5. Calls mammotion.start_mow using that target area switch.

This is different from simply calling:

lawn_mower.start_mowing

The Mammotion-specific service allows the blueprint to send more complete mowing parameters.

Required helpers

Create these before importing/using the blueprint:

  1. input_number — Mower Last Zone

    • min: 0
    • max: 6
    • step: 1
    • initial: 0

  2. input_boolean — Mower Skip Today

    • Turn this on to skip scheduled mowing.
    • Turn it off to resume.

  3. input_datetime — Mower Last Run

    • Must be date and time type.

  4. input_datetime — Mower Rain Last Seen

    • Must be date and time type.
    • Used for the wet-lawn dry-out delay.

Simple installation instructions

  1. Install and configure the Mammotion HACS integration.

  2. Make sure your mower has a lawn_mower.* entity.

  3. Make sure each work area has a Mammotion area switch.* entity.

  4. Create the four helpers listed above.

  5. Import the blueprint into Home Assistant.

  6. Create a new automation from the blueprint.

  7. Select:

    • your mower entity
    • your active zone count
    • your zone area switches
    • your weather forecast entity
    • your helper entities
    • your mowing schedule

Start simple. I recommend testing first with:

Number of Active Zones: 1
Zones Per Session: 1
Zone Duration Ceiling: short/safe test value

Once that works, increase the active zone count and enable more sessions.

Forecast / weather entity instructions

The blueprint needs a Home Assistant weather.* entity.

A good simple option is Open-Meteo. Home Assistant’s Open-Meteo integration provides free weather forecasts, does not require an account or API key, and can be added from Settings → Devices & services → Add Integration → Open-Meteo. (Home Assistant)

To find your forecast entity:

  1. Go to Settings → Devices & services.
  2. Open your weather integration, such as Open-Meteo.
  3. Open the entities list.
  4. Look for an entity like:
weather.forecast_home

or:

weather.open_meteo_home
  1. Select that entity in the blueprint’s Forecast Weather Entity field.

The blueprint checks the weather entity’s current condition. Home Assistant weather entities use states like rainy, pouring, lightning-rainy, hail, snowy-rainy, and exceptional; those are the rain/wet-weather states this blueprint uses to skip mowing. (Home Assistant)

Rain behavior

The blueprint checks rain at multiple points:

  1. At session start.
  2. During the wet-lawn delay check.
  3. Before Zone B if mowing two zones.
  4. During the zone wait window, so the mower can be recalled if rain appears mid-session.

Rain states currently treated as unsafe:

rainy
pouring
lightning-rainy
hail
snowy-rainy
exceptional

Important notes

The Mammotion app or mower may still block mowing even if Home Assistant sends the command successfully. Common reasons include:

  • non-work hours
  • low battery
  • map/location issue
  • mower offline
  • rain lockout in Mammotion
  • mower not ready to start
  • connection issue

If the automation trace says the service executed but the mower did not move, check the mower state and Mammotion app restrictions first.

Blueprint

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Honest disclosure

This was built and tested around a Mammotion zone-switch workflow, with a lot of iteration and AI-assisted YAML cleanup. Please read through it before deploying and test with one zone first.

1 Like
2

Thanks for creating this Blueprint.
Could you maybe add another radio button to allow 3 laps of perimeter or obstacle mowing?

Thanks in advance :slight_smile:

1 Like