Xiaomi Cloud Vacuum Map Extractor

Share your Projects! Custom Integrations
41

Nice finding! I will add it in documentation

1 Like
42

I m trying to make this work in the Xiaomi Vacuum Map Card. Here is the code.

- type: 'custom:xiaomi-vacuum-map-card'
        entity: vacuum.xiaomi_vacuum_cleaner
        map_camera: camera.xiaomi_roborock_map
        calibration_points:
          - vacuum:
              x: 25500
              'y': 25500
            map:
              x: 539
              'y': 285
          - vacuum:
              x: 26500
              'y': 26500
            map:
              x: 584
              'y': 241
          - vacuum:
              x: 25500
              'y': 26500
            map:
              x: 539
              'y': 241

Note: not sure why there is ’ ’ on the Y. Added automatically by HA.

The problem is when I command the vacuum cleaner to go to 1 point, it does the opposite. See below :

VacuumActualvsTarget
VacuumActualvsTarget744×338 59.7 KB

43

I have just published an update for extractor that calculates calibration_points for Lovelace Xiaomi Vacuum Map card. You can follow a progress of integration here.

1 Like
44

cool, this would be nice!

45

Right now you have to manually copy these values from attributes, but finally they will be taken from camera automatically

46

Hello
A stackable Vacuum-Mop P STYTJ02YM
Is your component not working?
It has navigation system and LDS (laser navigation sensor)

47

It should work if it’s natively supported by HA

48

it is supported by a custom component https://github.com/nqkdev/home-assistant-vacuum-styj02ym

49

It might work, you have to check it by yourself

50

checked, does not work. Maybe because I have Mi home by vevs installed

51

Still have the same problem. Why there is ‘Y’ added by HA?

- type: 'custom:xiaomi-vacuum-map-card'
        entity: vacuum.xiaomi_vacuum_cleaner
        map_camera: camera.xiaomi_roborock_map
        calibration_points:
          - vacuum:
              x: 25500
              'y': 25500
            map:
              x: 469
              'y': 318
          - vacuum:
              x: 26500
              'y': 26500
            map:
              x: 496
              'y': 293
          - vacuum:
              x: 25500
              'y': 26500
            map:
              x: 469
              'y': 293
52

This is just a formatting, it doesn’t affect anything. Is calibration correct?

53

I followed the calibration guide. The question i had is should use the map b4 or after trim? Also the the reference point (0,0) for Paint is on top left corner. Is this correct? Also why HA added ’ ’ for Y axis

54

Is there any hope to get support for Valetudo firmware?

1 Like
55

When you use calibration from attributes of a camera you don’t have to adjust anything , provided that you don’t modify image. If you want to do it, do it in a camera using trim.

56

Doesn’t valetudo already have a way to extract a map?

57

how to find out which xiaomi server you are connected to?
One of: ru , us , tw , sg , cn , de

and can it be that my server is not in the list?

58

I think it’s the connection you use in xiaomi app, I have europe, so I choose .de

59

Actually I’m trying to add this camera in your vacuum map card but couldn’t get it to work. There is something wrong with the calibration points. It seems to be rotated 180 deg.

60

It’s literally in the README:

calibration_points - Calculated calibration points for Lovelace Xiaomi Vacuum Map card. WARNING: this attribute doesn’t support map rotation.

Just remove rotate: 180 from your config