Lawn mower started mowing
The Lawn mower started mowing trigger fires when a mower begins a mowing run. Use it to react when yard work starts, like muting another routine, sending a confirmation, or turning on a light along the first part of the route.
Requires the Purpose-specific triggers and conditions Labs preview feature. Enable it at Settings > System > Labs.
Using this trigger from the user interface
If you prefer building automations visually, Home Assistant walks you through this trigger step by step. You pick what to watch, tweak a few options, and save. No YAML knowledge required.
To use this trigger in an automation:
- Go to Settings > Automations & scenes.
- Open an existing automation, or select Create automation > Create new automation.
- In the When section, select Add trigger.
- From the search box, search for and select Lawn mower started mowing.
- Select what you want to monitor. Under By target (see Targets), pick the area where your mower is used. You can also select a floor, a device, a specific entity, or a label.
- Under Trigger when (see Behavior), pick Each, First, or All.
- Under For at least, set how long the mower must stay in the mowing state before the trigger fires. Leave it at zero to fire immediately.
- Select Save.
Options in the UI
When multiple lawn mowers are targeted, controls when the trigger fires. Pick Each to fire every time any targeted mower starts mowing, First to fire only when the first targeted mower starts mowing, or All to fire only after every targeted mower has started mowing.
Using this trigger in YAML
If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.
In YAML, refer to this trigger as lawn_mower.started_mowing. A basic example looks like this:
trigger: lawn_mower.started_mowing
target:
entity_id: lawn_mower.backyard
This fires when lawn_mower.backyard starts mowing.
Options in YAML
YAML sometimes provides additional options for more complex use cases that are not available through the UI.
Targets of the trigger
This trigger requires a target. The target is the object that Home Assistant will watch. You can select a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label as a target, and Home Assistant will watch every matching lawn_mower entity behind that target.
-
Entity: one specific lawn_mower entity, such as
lawn_mower.living_room. - Device: every lawn_mower entity that belongs to a device.
- Area: every lawn_mower entity in a room or area.
- Floor: every lawn_mower entity on a floor.
- Label: every lawn_mower entity that shares a label.
You can also select different target types in one trigger. For example, you can add a specific entity and an area as targets in the same trigger to monitor both of them at once.
Behavior with multiple targets
When you target more than one entity (or select an area, floor, or label that contains several), the Trigger when option controls how the trigger responds:
-
Each (
anyin YAML, default): the trigger fires every time any one of the targeted entities transitions. For example, if you monitor three motion sensors in the living room and someone walks past sensor 1, the automation fires. When they walk past sensor 2 a moment later, it fires again. Every individual event counts. -
First (
firstin YAML): the trigger fires only on the first transition in the targeted group, then waits until all targeted entities have reset before it fires again. For example, if you monitor the same three motion sensors, the automation fires when the first one picks up movement (someone entered the room). The other two firing afterward are ignored, so you get one notification per “someone walked in” event instead of three. -
All (
lastin YAML): the trigger fires only after the last targeted entity in the group has fired, meaning all of them are now in the expected state. For example, if you monitor the lights in the living room, bedroom, and hallway, the automation fires only once all three have turned off. This is useful for scenarios like “start the robot vacuum only after every light on the floor is off,” so you know the room is truly empty.
Good to know
- The trigger only fires when a mower changes into the mowing state from a known state. If a mower comes back from
unavailableorunknown, that recovery does not fire this trigger. - Use For at least if you want to ignore a short transition while the mower leaves the dock.
Try it yourself
Ready to test this? Go to Settings > Automations & scenes, create a new automation, and add this trigger. Save the automation, then change the state of the targeted entity to watch the trigger fire on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more].
More examples
Real scenarios where this trigger fires in automations and scripts. Copy any example and adapt it to your setup.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.
Automation: Let your household know the mower has started
If someone is about to let pets or children into the yard, a quick message can help them avoid the mowing area.
-
Trigger: Lawn mower started mowing
- Target: Backyard mower
-
Action: Send a notification message
-
Target: My Device (
notify.my_device)
-
Target: My Device (
YAML example for a mowing-start notification
alias: "Notify when the mower starts"
triggers:
- trigger: lawn_mower.started_mowing
target:
entity_id: lawn_mower.backyard
actions:
- action: notify.send_message
target:
entity_id: notify.my_device
data:
message: "The backyard mower has started mowing."
Automation: Turn off the sprinkler automation when mowing begins
If the mower and sprinklers should never run at the same time, turn off the sprinkler automation as soon as the mowing run starts.
-
Trigger: Lawn mower started mowing
- Target: Backyard mower
- For at least: 00:02:00
- Action: Turn off automation
YAML example for pausing the sprinkler schedule
alias: "Turn off sprinklers when mowing starts"
triggers:
- trigger: lawn_mower.started_mowing
target:
entity_id: lawn_mower.backyard
options:
for: "00:02:00"
actions:
- action: automation.turn_off
target:
entity_id: automation.water_the_backyard
Still stuck?
The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the trigger you’re using and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain triggers or suggest the right one when you describe what you want in plain language.