Xiaomi Cloud Vacuum Map Extractor

not sure what you mean ?

I got this from token extractor

Devices found for server “de”:

NAME: Roborock S7
ID: 3911xxxxxxxx
MAC: B0:4A:xxxxxxx
IP: 192.168.1.146
TOKEN: 7a375xxxxxxxxxxxxxxxxxxxxxx
MODEL: roborock.vacuum.a15

My lovelace code is:

  - type: custom:xiaomi-vacuum-map-card
    title: Mapping
    view_layout:
      grid-area: map
    card_mod:
      class: header
    language: GB
    entity: vacuum.roborock_vacuum_a15
    map_source:
      camera: camera.xiaomi_cloud_map_extractor
    calibration_source:
      camera: true

my configuration.yaml is:

camera:

  • platform: xiaomi_cloud_map_extractor
    host: 192.168.1.60
    token: 7a375xxxxxxxxxxxxxxxxxxxxxxxxxxxx
    username: [email protected]
    password: xxxxxxxxxxxxxxxxxxxxxx
    draw: [‘all’]
    attributes:
    • calibration_points

host ip of 192.168.1.60 is my homeassistant server/install
IP of 192.168.1.146 is the IP of the vacuum

i dont know if this is some type of conflict or probelm

but in my configuration.yaml i have the arlo HACS mod installed which uses this code

camera:

  • platform: aarlo
    ffmpeg_arguments: ‘-pred 1 -q:v 2’
    sensor:
  • platform: aarlo
    monitored_conditions:
    • total_cameras
    • last_capture
    • recent_activity
    • captured_today
    • battery_level
    • signal_strength
    • temperature
    • humidity
    • air_quality

I noticed the camera code is the same?

camera:

  • platform: xiaomi_cloud_map_extractor
    host: 192.168.1.60

would the word “camera:” be causing a problem ?

ok so i disabled the xiamoi plugins and removed the “camera” code from the config

now my arlo cameras are working again so it must be casuing a conflict having the same “camera” name

Can i change this to camera1 or something?

Uhhhhhh you should use IP of the vacuum, not HA server

You have to use these two entries in the same camera section

camera:
  - platform: aarlo
    ffmpeg_arguments: ‘-pred 1 -q:v 2’
  - platform: xiaomi_cloud_map_extractor
    ...
1 Like

thank you it was the double camera entry casuing the issue!

Dreame support released!

3 Likes

great job as always, thnx for supporting us!

1 Like

Did you ever figure this out? I’m getting the same error.

It should be fixed for viomi.vacuum.v18. Which vacuum model do you have?

Hi,

There’s any option to rotate the map? (I have rotated the map on the xiomi mobile app).

Thank You,

I have viomi.vacuum.v23

force_api: roidmi should solve your problem

@3_14 I dont know were to put the “rotate: 270” line :slight_smile:

type: custom:xiaomi-vacuum-map-card
entity: vacuum.roborock_s7
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
map_modes:
  - template: vacuum_clean_zone
  - template: vacuum_clean_segment
    predefined_selections:
      - id: 18
        label:
          text: 4
          x: 26200
          'y': 29300
          offset_y: 35
        icon:
          name: mdi:broom
          x: 26200
          'y': 29300
      - id: 17
        label:
          text: 2
          x: 30025
          'y': 26825
          offset_y: 35
        icon:
          name: mdi:broom
          x: 30025
          'y': 26825
      - id: 19
        label:
          text: 3
          x: 27300
          'y': 27150
          offset_y: 35
        icon:
          name: mdi:broom
          x: 27300
          'y': 27150
      - id: 20
        label:
          text: 1
          x: 29575
          'y': 35125
          offset_y: 35
        icon:
          name: mdi:broom
          x: 29575
          'y': 35125
      - id: 16
        label:
          text: מטבח
          x: 25575
          'y': 34850
          offset_y: 35
        icon:
          name: mdi:broom
          x: 25575
          'y': 34850
  - template: vacuum_follow_path
  - template: vacuum_goto
language: he
two_finger_pan: true
vacuum_platform: default
title: ''
map_locked: true
rotate: 270

In Map Extractor’s config

Thank you!

Thanks, that fixed the issue. Glad I asked because I obviously wasn’t going to figure that one out!

I appreciate you taking your time to solve this for me. :slight_smile:

Hello,
will the xiaomi ijai.vacuum.v3 also be integrated? I have model vacuum mop 2 pro and the integration shows me, that this model is not supported. It this integration planed?

Thank you,

It’s not planned at this moment, but I’m willing to help anyone that will try to implement it.
Related issue:

Hi, i have an error when the vacuum finished cleaning. i have two vacuums one roborock s7 and one roborock s7 maxV ultra. i do believe this error now came from S7. everything works ok but this error is displayed in the logs all the time when its finishing the clean.

  • STATE not supported: Definition missing for state 26, state_code: 26
  • STATE not supported: Definition missing for state 23, state_code: 23
1 Like