Dreame Mova vacuum restore map

Vital555 · December 28, 2025, 2:09pm

I’m using the dreame-vacuum integration with my Mova P50 Pro Ultra, and it generally works very well.
However, I sometimes have issues with the map becoming corrupted, probably due to dust on the sensors or reflections in the apartment.

Since the vacuum supports map backup and restore, I wanted to automate this through Home Assistant.
In the Dreame app I can choose between three states when restoring a map: Original, Edited, Backup

In Home Assistant there is the action vacuum_restore_map, where you have to specify index and ID.
The index is 1, but I have no idea where I can get the correct ID from.

If I leave the ID empty, the vacuum restores the Original map — but that is not the most recent backup I want to use.

In the “saved map” entity I found the following attributes, but the numbers inside do not work as IDs:

recovery_map_list:
  - date: 2025-12-28 14:19
    map_type: Backup
    object_name: ali_dreame/WI005600/909855125/102
  - date: 2025-12-12 14:55
    map_type: Edited
    object_name: ali_dreame/WI005600/909855125/101
  - date: 2025-12-05 18:39
    map_type: Original
    object_name: ali_dreame/WI005600/909855125/100

Does anyone know how to correctly obtain the map ID for the vacuum_restore_map service so that I can restore the Backup or Edited map instead of always restoring the Original one?

@tasshack Do you know how to obtain the right ID?

Thanks!

tasshack · December 28, 2025, 6:50pm

Map recovery does not use IDs for selecting maps because those are not static and always changes because of that you need to specify the map index which is order of the map from oldest to newest.

Index 1 = Original
Index 2 = Edited
Index 3 = Edited or Backup
Index 4 = Backup

github.com/Tasshack/dreame-vacuum

docs/map.md

b675e5305

# Map Support

Completely reverse engineered map data handling, decoding and rendering for live and multiple saved map support with all features provided with the official App.

<img src="https://raw.githubusercontent.com/Tasshack/dreame-vacuum/master/docs/media/live_map.jpg" width="400px">

- High resolution image rendering with layer caching for improving performance.
- All resources with icon position and color index finding algorithms are extracted from the official App for same look and feel.
- All map operations is handled on memory before it is sent to device for low latency updates.
- Fully featured highly optimized integrated map manager for map editing and handling partial maps.
- With dynamic refresh rate determined by map type, device state and last access time.

### High refresh rate with low latency

Partial map (P frame type) decoding for three seconds refresh rate with three seconds delay same as with the official App.

<a href="https://raw.githubusercontent.com/Tasshack/dreame-vacuum/master/docs/media/cleaning.gif" target="_blank"><img src="https://raw.githubusercontent.com/Tasshack/dreame-vacuum/master/docs/media/cleaning.gif" width="500px"></a>

> - P type maps are introduced with second generation robots and new devices only sends P frames to the cloud when running.
> - P maps are only containing the difference between its previous frame therefore handling is much harder than standard I type maps.

This file has been truncated. show original

github.com/Tasshack/dreame-vacuum

docs/services.md

b675e5305

# Services
The integration adds the following services to vacuum domain. 

## Vacuum Services
Services for actions that are not available via an entity.

<a href="https://my.home-assistant.io/redirect/developer_services/" target="_blank"><img src="https://my.home-assistant.io/badges/developer_services.svg" alt="Open your Home Assistant instance and show your service developer tools." /></a>

### `dreame_vacuum.vacuum_clean_segment`

Start selected room cleaning with optional customized cleaning parameters. 
> - If you are using integration with map feature, you can acquire segment ids from vacuum entity attributes.
> - Cleaning parameters and cleaning sequence are ignored by the device when `customized_cleaning` or `cleaning_sequence` is enabled.

**Examples:**

- Clean room 3
    ```yaml
    service: dreame_vacuum.vacuum_clean_segment
    data:

This file has been truncated. show original

Vital555 · December 28, 2025, 7:54pm

Thank you for quick response. This works.
For the recent backup map I use the Index=3.
In case of multiple maps it restores always the current selected one, right?

tasshack · December 28, 2025, 8:14pm

Restoring a non selected map causes it to be selected after restore by the device so there is no advantage of doing that, instead you can set selected map to you want to restore first using a script to not to deal with any map ids that are constantly changing.

action: select.select_option
target:
  entity_id: select.vacuum_selected_map
data:
  option: "Map Name"

Official app also does not allow you to restore a non selected map too.