Failed to retrieve map from vacuum

[hugomickael]

Checklist

• I have updated the integration to the latest version available
• I have checked if the problem is already reported

The problem

The map doesn't appear, only the message "Failed to retrieve map from vacuum" and "Invalid calibration, please check your configuration".

Here is the card configuration:

type: custom:xiaomi-vacuum-map-card
title: Xiaomi Vacuum Map Card
preset_name: Live map
entity: vacuum.ramiro
map_source:
camera: camera.my_camera
calibration_source:
camera: true
vacuum_platform: default

What version of an integration has described problem?

v2.2.1

What was the last working version of an integration?

No response

What vacuum model do you have problems with?

rockrobo.vacuum.v1

What version of Home Assistant do you use?

2024.7.2

What type of installation are you running?

Home Assistant Container

Camera's configuration

- platform: xiaomi_cloud_map_extractor
  host: 192.168.1.91
  token: !secret token
  username: !secret email
  password: !secret xiaomi_password
  name: "My Camera"
  country: "de"
  draw: ["all"]
  attributes:
    - calibration_points

Errors shown in the HA logs (if applicable)

No response

Additional information

No response

[Smarthome-Creator]

I have exactly the same problem.
Unfortunately, I do not understand the problem and do not know how it comes about. I have set up everything as described in the documentation, but unfortunately it doesn't work.

- platform: xiaomi_cloud_map_extractor
  name: Wall-E Floor plan
  host: XXX.XXX.XXX.XXX
  token: !secret 
  username: !secret 
  password: !secret 
  draw: ['all']
  attributes:
    - calibration_points

It only worked once when I set it up, since then I always get this message.
What I find very strange is when I “turn on” the HA entity, I can no longer load the map in the original Xiaomi App. (“Network too slow”)

If I switch the entity “off” again in HA, the map can be loaded again in the app. I don't know what's going on.

[neiker]

Same here, it worked perfectly and without changing anything it started to fail.
Just in case I checked that the device's IP is still the same and it hasn't changed. Same with the token

[neiker]

It looks like Xiaomi bans you if you perform many requests too often. I added the blueprint mentioned here to disable the polling when the vacuum is docked. Now I guess I should wait until Xiaomi decides to lift the ban

[hugomickael]

Ok thanks, I applied the blueprint, let's see.

[vchatela]

Ok thanks, I applied the blueprint, let's see.

Any updates on your unban ? I am ban too...

[TrasteCC]

Ok thanks, I applied the blueprint, let's see.

Hey! I'm struggling with the same problem. Just applied the blueprint.

Did you get your ban lifted? How long did it take?

Thanks

[vchatela]

Myself it resolved 2 days after added the removal of refresh and local storage.
I had contacted roborock support at same time but there were useless in solving this.

[TrasteCC]

Myself it resolved 2 days after added the removal of refresh and local storage. I had contacted roborock support at same time but there were useless in solving this.

Thanks! I'll wait :-)

[neiker]

In my case, they lift the ban after 24 hours. But they don't disclose the duration or if it's longer in case of a repeat "offense"

[Smandurlo]

I have the same problem, but I have my camera off when it is docked since the very first time I used this custom component, so this is not the problem. Any idea?

[obsthaendler91]

i have the same issue, i try the blueprint and come back later

[obsthaendler91]

in my case:
configuration.yaml edit "auto_update: true" to false
i use the blueprint: https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor/blob/master/blueprints/automation/disable_vacuum_camera_update_when_docked.yaml

this works for me.

[ireun]

I use PiotrMachowski/update_map_extractor.yaml but it seems to work only when docked.. Otherwise the map does not update at all.. Xiaomi Vacuum here, rockrobo.vacuum.v1

Blueprint settings:

alias: Update Map Extractor camera 
description: ""
use_blueprint:
  path: PiotrMachowski/update_map_extractor.yaml
  input:
    vacuum: vacuum.rockrobo_v1_a259_robot_cleaner
    camera: camera.gorgie
    mode_to_handle: two_intervals
    interval_docked: 3600

Camera:

camera:
  - platform: xiaomi_cloud_map_extractor
    name: Gorgie
    host: !secret xiaomi_vacuum_host
    token: !secret xiaomi_vacuum_token_gorgie
    username: !secret xiaomi_cloud_username
    password: !secret xiaomi_cloud_password
    country: "de"
    draw: ["all"]
    auto_update: false
    attributes:
      - calibration_points

[eric-silva89]

Hey everyone. I have the same problem but it is sporadic. If I do not use the vacuum for a day or 2 I can generate a map. I also cannot use the Mi Home app as the map on the app will not generate. I suspect I am hitting an API limit against Xiaomi.

Here is my config

- platform: xiaomi_cloud_map_extractor
  host: !secret
  token: !secret
  username: !secret
  password: !secret
  country: us
  name: WALL-E Map
  draw: ['all']
  map_transformation:
    rotate: 180
    trim:
      top: 15
      bottom: 10
      left: 20
      right: 20
  colors:
    color_map_outside: [34, 53, 72]
  attributes:
    - calibration_points
    - charger
    - cleaned_rooms
    - country
    - goto
    - goto_path
    - goto_predicted_path
    - image
    - is_empty
    - map_name
    - no_go_areas
    - no_mopping_areas
    - obstacles
    - ignored_obstacles
    - obstacles_with_photo
    - ignored_obstacles_with_photo
    - path
    - room_numbers
    - rooms
    - vacuum_position
    - vacuum_room
    - vacuum_room_name
    - walls
    - zones
  scan_interval:
    seconds: 30
  auto_update: true
  store_map_raw: false
  store_map_image: true
  store_map_path: "/tmp"
  force_api: xiaomi

I suspect something in here is hitting the API limits. I am also using the blueprint PiotrMachowski/disable_vacuum_camera_update_when_docked.yaml