dreame-mower

KO | EN

gitlite — search

#javascript #python #react #ai #typescript #go #machine-learning #rust #macos #awesome #kubernetes #awesome-list #mcp #open-source

(★ 108)

Dreame Mower integration for Home Assistant

File Explorer

Download Latest Version (.zip)

- - hacs.yml
  - hassfest.yml
  - release.yml
  - test.yml
- copilot-instructions.md
- FUNDING.yml
- - __init__.py
  - binary_sensor.py
  - button.py
  - camera.py
  - config_flow.py
  - const.py
  - coordinator.py
  - entity.py
  - lawn_mower.py
  - manifest.json
  - number.py
  - select.py
  - sensor.py
  - services.yaml
  - switch.py
  - time.py
- - README_device_data_analysis.md
  - README_properties_misc.md
- analyze_device_data.py
- device_cli.py
- list_devices.py
- probe_rest_properties.py
- realtime_monitor.py
- __init__.py
- conftest.py
- requirements.txt
- test_scheduling_property_handler.py
.gitignore
CLAUDE.md
CONTRIBUTING.md
hacs.json
LICENSE
mypy.ini
pytest.ini
README.md
run_test.sh

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# 🏡 Dreame & MOVA Lawn Mower Integration for Home Assistant

[![GitHub Release](https://img.shields.io/github/v/release/antondaubert/dreame-mower?style=flat-square)](https://github.com/antondaubert/dreame-mower/releases)
[![hacs_badge](https://img.shields.io/badge/HACS-Custom-orange.svg?style=flat-square)](https://hacs.xyz/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square)](https://opensource.org/licenses/MIT)

A Home Assistant integration for **Dreame** and **MOVA** robotic lawn mowers. Control your mower, view maps, track mowing sessions, and monitor battery status directly from Home Assistant.

*If this integration saves you time, consider to [buy me a ☕](https://buymeacoffee.com/antondaubert).*

### Disclaimer
This is an **community-developed integration** for interoperability with Home Assistant. It is not affiliated with or supported by Dreame Technology or MOVA.

Provided "as-is" under the MIT License for personal, non-commercial use with devices you own. Use at your own risk.

## Current Features
- **Live Maps** - See your mower's location and coverage in real-time
- **Session Tracking** - Current and previous mowing sessions  
- **Session History** - Keep track of past mowing activities
- **Remote Control** - Start, pause, stop, and dock your mower
- **Map Awareness** - Inspect known maps, zones, contours, and active task metadata
- **Cutting Height** - Read and set the cutting height of the active map
- **Edge Mowing** - Read and set how the mower treats the edges, per map or per zone
- **Charging Period** - Read and set the time window the mower is allowed to fully charge in
- **Rain Protection** - See when rain keeps the mower docked, and set how long it waits afterwards
- **Anti-Theft Alarm** - Read and set the lift alarm, the off-map alarm and the mower's position reports
- **Battery Status** - Current battery level and charging info
- **Mowing Progress** - Coverage percentage and session duration
- **Do Not Disturb** - View quiet hours settings
- **Notifications** - Status updates and error alerts

*Have suggestions? Check out [Discussions](https://github.com/antondaubert/dreame-mower/discussions)*

## UI Elements

The current release exposes map, zone, and edge selection as select entities in Home Assistant. Selecting **multiple zones or areas** at once is not yet available in the UI — use the service actions below for that.

### Switching Maps

The mower only switches its active map while **no mowing task is in progress**. A task that is running, paused, or interrupted on the way back to the dock all block the switch — the mower accepts the command and then ignores it. Finish or cancel the task first, then switch the map. The **Map** select reports an error instead of silently leaving the mower on the old map.

In automations that switch the map and then start mowing, give the mower a moment between the two steps so the new map is active before the run starts.

### Cutting Height

The **Cutting height** number entity sets the cutting height of the **active map**, in 0.5 cm steps. The entity is only created for models whose cutting height is adjustable from software; on models with a manual height dial (for example the MOVA 600 and MOVA 1000) it is omitted.

The selectable range depends on the model: most mowers go from 3 cm to 7 cm, while models with an extended range go up to 10 cm.

The entity always sets the height for the whole map. To set a height for a single zone, use the `dreame_mower.set_cutting_height` service action with a `zone_id`.

The mower entity exposes `cutting_height`, `zone_cutting_heights` and `mowing_preference_mode` as attributes, so automations can read back the current values and see which of the two is in effect. The mower announces a changed height, whoever changed it, so one set in the Dreame or MOVA app shows up within seconds.

### Edge Mowing

Three switches cover how the mower treats the edges of the **active map**:

- **Automatic Edge Mowing** - the mower mows the edges on its own once all-area or zone mowing has finished
- **Safe Edge Mowing** - the mower keeps a small buffer from the lawn boundary while mowing the edges, which spares the boundary but leaves a strip of uncut grass along it
- **EdgeMaster** - the blade disc shifts to the side for the edge laps so the mower cuts closer to the boundary than the centred disc reaches

Switching **EdgeMaster** on also raises a single edge lap to two, which the offset disc needs to cover the edge.

**Safe Edge Mowing** is the setting that keeps a mower away from the boundary even with obstacle avoidance turned off. Firmware that predates it keeps no such setting, and the switch is then omitted rather than offered as a control that cannot write.

The switches always change the active map as a whole. To change a single zone, or a map that is not active, use the `dreame_mower.set_edge_mowing_settings` service action.

The switches are created only for devices that reported their mowing settings, which are read when the integration starts and whenever the active map changes. The mower announces every change to them, whoever made it, so changes from the Dreame or MOVA app show up within seconds without reloading the integration.

### Charging Period

The mower can restrict full charging to a time window of your choosing. Three entities control it:

- **Charging Period** (switch) - turns the custom period on and off
- **Charging Period Start** (time) - when the window opens
- **Charging Period End** (time) - when the window closes

While the period is on, the mower only keeps a safe battery level when it sits idle at the station and fully charges inside the window. Turning the switch off returns it to charging whenever it is docked. Both times keep their value while the period is off, so an automation can switch it on and off without restating the window.

An end time earlier than the start time means the window runs past midnight into the next day, for example 22:00 to 06:00. Start and end must differ — the mower rejects a window of zero length. The times follow the clock of the mower itself, so they match Home Assistant only while both use the same time zone.

The entities are created only for devices that report their charging settings. The mower announces every settings change it makes, whoever made it, so changes from the Dreame or MOVA app show up within seconds without reloading the integration.

### Rain Protection

With rain protection on, the mower returns to its station when it detects rain and waits out a delay before it picks the interrupted task back up. Three entities cover it:

- **Rain Protection** (switch) - turns rain protection on and off
- **After-Rain Delay** (select) - how long the mower waits after rain
- **Mowing Resumes After Rain Protection** (sensor) - the timestamp the mower may work again, unknown at any other time

The delay is chosen from the same list the app offers: **Don't mow after rain** first, then **1 h** through **24 h**.

**Don't mow after rain** leaves the mower docked until it is started again. That is also the one setting where the mower names no time to resume at, so **Mowing Resumes After Rain Protection** stays unknown even while rain is keeping the mower docked; use the mower's own state for that case rather than this sensor.

A changed delay applies the next time rain protection triggers, and the mower only takes a new delay while rain protection is on — with it off it keeps the delay it holds and the entity reports an error.

The entities are created only for devices that report rain settings. The mower announces every settings change it makes, whoever made it, so changes from the Dreame or MOVA app show up within seconds without reloading the integration.

### Anti-Theft Alarm

The mower's anti-theft settings are exposed as switches:

- **Lift Alarm** - the mower locks itself and sounds an alarm as soon as it is lifted off the ground
- **Off-Map Alarm** - the mower locks itself and sounds an alarm as soon as it is carried away from its map
- **Real-Time Location** - the mower reports where it is, which is what makes a stolen mower traceable
- **PIN Check Before Power-Off** - the mower only switches off once its PIN code has been entered on it

Locking the mower and sounding the alarm is all the mower does on its own. **Off-Map Alarm** and **Real-Time Location** need the mower's cellular module to work away from home, and stay without effect on a mower that has none. **PIN Check Before Power-Off** exists only on models that keep such a switch, and is omitted elsewhere rather than offered as a control that cannot write.

The switches are created only for devices that report anti-theft settings. The mower announces every settings change it makes, whoever made it, so changes from the Dreame or MOVA app show up within seconds without reloading the integration.

### TODO: Hierarchical Mowing UI

The intended UI flow is:

1. Select the active map.
2. Pick a mowing scenario: all-area, edge, zone, spot, or manual.
3. If edge or zone is selected, choose one or more contours or zones.
4. If spot is selected, define the target rectangle.
5. Manual control is expected to depend on Bluetooth and remains further out in the roadmap.

The device layer already tracks map metadata and verified mowing modes so this UI can be added later without reworking the protocol layer again.

## Service Actions

Zone and area selection is available via the select entities in the UI. For mowing **multiple zones or areas** in a single run without returning to the station between them, use the service calls below.

### `dreame_mower.start_zone_mowing`

Start mowing one or more zones without the mower returning to the station between them.

```yaml
action: dreame_mower.start_zone_mowing
target:
  entity_id: lawn_mower.your_mower
data:
  zone_ids: [1, 3]
```

Zone IDs correspond to the zones defined on your map. You can find them via the zone select entities exposed by the integration.

### `dreame_mower.start_edge_mowing`

Start mowing the edges of one or more contours without the mower returning to the station between them.

```yaml
action: dreame_mower.start_edge_mowing
target:
  entity_id: lawn_mower.your_mower
data:
  contour_ids:
    - [1, 0]
    - [2, 0]
```

Contour IDs are two-integer pairs. The available pairs are exposed in the mower entity's `contours` attribute once the map has been fetched, and in the **Edge** select entity.

### `dreame_mower.start_spot_mowing`

Start mowing one or more spot areas by their IDs.

```yaml
action: dreame_mower.start_spot_mowing
target:
  entity_id: lawn_mower.your_mower
data:
  spot_area_ids: [2, 4]
```

### `dreame_mower.set_cutting_height`

Set the cutting height for a whole map. Use this instead of the **Cutting height** number entity when you want to change a map that is not currently active.

```yaml
action: dreame_mower.set_cutting_height
target:
  entity_id: lawn_mower.your_mower
data:
  height: 5.5
  map_id: 2
```

`height` is in centimeters and is rounded to the nearest 0.5 cm. `map_id` is optional and defaults to the active map; available map IDs are exposed in the mower entity's `maps` attribute.

To set the height for a single zone, add `zone_id`:

```yaml
action: dreame_mower.set_cutting_height
target:
  entity_id: lawn_mower.your_mower
data:
  height: 5
  zone_id: 3
```

Setting a zone height also switches that map to **per-zone** mowing settings, because a zone height has no effect while the map is applying one setting to everything. Every other zone keeps whatever it already had, and the map-wide height stops applying until you switch back.

### `dreame_mower.set_edge_mowing_settings`

Switch the edge mowing settings for a whole map, or for a single zone of it. Use this instead of the switch entities when you want to change a map that is not currently active, several settings at once, or a single zone.

```yaml
action: dreame_mower.set_edge_mowing_settings
target:
  entity_id: lawn_mower.your_mower
data:
  automatic_edge_mowing: true
  safe_edge_mowing: false
```

Every setting left out keeps the value it has. `map_id` is optional and defaults to the active map; `zone_id` changes a single zone instead of the whole map, which switches that map to **per-zone** mowing settings the same way `set_cutting_height` does.

The mower entity exposes `edge_mowing_settings` and `zone_edge_mowing_settings` as attributes so automations can read the settings back.

### `dreame_mower.set_mowing_preference_mode`

Switch a map between one map-wide setting and per-zone settings. Use this to go back to a single cutting height after setting one for an individual zone.

```yaml
action: dreame_mower.set_mowing_preference_mode
target:
  entity_id: lawn_mower.your_mower
data:
  mode: map_wide
```

`mode` is `map_wide` or `per_zone`, and `map_id` is optional. The mode governs the other mowing settings as well, not only the cutting height. The mower entity's `mowing_preference_mode` attribute shows the current value.

## Installation

1. Ensure [HACS](https://hacs.xyz/) is installed
2. Navigate to HACS → Integrations
3. Click ⋮ → Custom repositories  
4. Add: `https://github.com/antondaubert/dreame-mower`
5. Category: Integration
6. Settings → Devices & Services → Add Integration → "Dreame Mower"

## Example Automations

The following is a real-world example showing how to integrate the mower with a motorized gate/cover and a rain sensor (via the [Netatmo integration](https://www.home-assistant.io/integrations/netatmo/)). Adjust entity IDs to match your setup.

### Overview

The setup consists of three parts:

1. **Mowing script** — opens the gate, waits until it is fully open, then starts the mower and sends a notification.
2. **Close-gate automation** — closes the gate automatically once the mower has docked.
3. **Daily trigger automation** — fires at noon, skips mowing if it rained today (via Netatmo), otherwise runs the mowing script.

### 1. Script: Start Mowing

This script is called by the daily trigger automation. It opens the cover/gate first and only starts the mower once the gate is confirmed open.

```yaml
alias: "[Dreame] Start Mowing"
sequence:
  - action: cover.open_cover
    target:
      entity_id: cover.dreame_gate  # replace with your cover entity
  - wait_for_trigger:
      - trigger: state
        entity_id: cover.dreame_gate
        to: "open"
    timeout: "00:01:00"
  - if:
      - condition: state
        entity_id: cover.dreame_gate
        state: "open"
    then:
      - action: lawn_mower.start_mowing
        target:
          entity_id: lawn_mower.a2  # replace with your mower entity
      - action: notify.notify
        data:
          message: "Mower started"
          title: "Dreame Mower"
```

### 2. Automation: Close Gate When Docked

Closes the gate as soon as the mower transitions from *Mowing* or *Returning* to *Docked*.

```yaml
alias: "[Dreame] Close Gate"
triggers:
  - trigger: state
    entity_id: lawn_mower.a2
    from: mowing
    to: docked
  - trigger: state
    entity_id: lawn_mower.a2
    from: returning
    to: docked
actions:
  - action: cover.close_cover
    target:
      entity_id: cover.dreame_gate
```

### 3. Automation: Daily Mowing Trigger (Rain Check)

Fires every day at noon. Uses the Netatmo integration to check whether it has rained today. If no rain is detected, the mowing script is started. Otherwise a persistent notification is sent.

```yaml
alias: "[Dreame] Daily Mowing Trigger"
triggers:
  - trigger: time
    at: "12:00:00"
actions:
  - if:
      - condition: numeric_state
        entity_id: sensor.netatmo_rainfall_today  # replace with your Netatmo rain sensor
        below: 1
    then:
      - action: script.dreame_start_mowing
    else:
      - action: notify.persistent_notification
        data:
          title: "Dreame Mower"
          message: "Mowing skipped — rain detected today."
```

> **Tip:** The daily trigger automation can be kept disabled and run on-demand via another automation or a dashboard button. The rain check prevents unnecessary mowing after wet weather.

## Community & Support

- **Discussions**: Questions and ideas → [GitHub Discussions](https://github.com/antondaubert/dreame-mower/discussions)
- **Issues**: Bug reports and feature requests → [GitHub Issues](https://github.com/antondaubert/dreame-mower/issues)

## License

This project is licensed under the **MIT License** - see the [LICENSE](LICENSE) file for details.

---

## Acknowledgments & Development

This integration was developed through community collaboration for the purpose of achieving interoperability with Home Assistant. It builds upon:

- [Benedikt Hübschen's](https://github.com/bhuebschen/dreame-mower) original mower integration
- Insights from [Tasshack's](https://github.com/Tasshack/dreame-vacuum) vacuum integration
- Protocol analysis and testing by the Home Assistant community

Special thanks to the entire Home Assistant community for continuous support and feedback!

---

*Happy mowing! 🌱*

dreame-mower

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

dreame-mower

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

Download README