Valetudo map in vacuum map card

[mannebk]

Folks, i use the vacuum map card, (xiaomi map card), and i use the map thing for extracting the valetudo map (MQTT Vacuum Camera), and have them both combined in my dashboard.

now my dreamy bots do create nice rectangle rooms. my dreame-valetudos make irregular polygons for each room, looks really untidy.

So i sat down, and fixed the map in the dashboard with new coordinates to fit the real rooms.

See the Dashboard of the robot named RobbyDobby (yea i know, thats a flat Harry Potter joke) thats L10s Ultra 1 actually, and i just wait for a pcb to root the other two as well.

Since yesterday, I cant select a room for cleaning any more. Do they need to have the same boundaries? I thought they would be selected by room id.

i can select a room, and can start cleaning, it reports success, but the bot doesn’t react to it at all.

However if I send it with clean all from the same dashboard, it works just fine.

I also havent figured out with the vacuum map card, how to switch between mob, sweep and sweep&mop mode.

And i would like to get rid of the blue background colour in the valetudo map.

Any ideas whats wrong here?

Your help is greatly appreciated.
Manny

[gsca075 (SandroC)]

In the option of the MQTT Vacuum Camera you can select the background color as you wish (condition for the camera to work properly is that the vacuum runs Valetudo) the issue with the coordinates looks like the calibration of the map did not work properly… and by the way I assume RobbyDobby is already "de-clouded) is that correct?

[mannebk]

indeed, the first two (mat and robbydobby) are a roborock s5(0) with valetudo, and a L10s Ultra with valetudo. the #2 and #3 need declouding badly. currently only active in my basement… got em broken for cheap and fixed em up. Waiting for my break out pcb to get rid of the cloude.

thanks for the hint, ill look into that.

In the mean time i did build myself a new dashboard view with just that robot, i let the card handle all.

it reports success, but the robot doesn’t move. no matter if zone, pin or room.

exception: a total clean up works fine (see at the end of the gif, the robot on the right changes states and starts moving.)

[gsca075 (SandroC)]

did you setup the topic in the card?

  internal_variables: 
    topic: valetudo/YOUR_TOPIC_HERE

for the colours of the camera setup… here

[mannebk]

@gsca075

topic

you talking about the front end xiaomi vacuum card? no, there is no query for it and i found no section in the code for it.

cant find any other place where i could enter these information.

i installed via hacs, so no manual stuff to do according to your link.

but i found the colour adjustment place

[gsca075 (SandroC)]

yes the card settings - yaml config there you need to add the lines I just proposed and YOUR_TOPIC_HERE need to be replaced with the one you found in the camera attributes.

[mannebk]

it is the second code snipet in the manual setup section, i found that.

but i used hacs, so it already should be there, cause in the hacs section there is no mention of it.

[gsca075 (SandroC)]

no buddy, it is normal, the card do not set the value for the topic automatically it is written on both camera and card docs, just please follow the instruction and it will start to works. I’m not at home right now but I can show you later how to do it is quite simple… just after the “vacuum_platform” add the two lines and use RobbyDobby or whatever topic the vacuum have so for example valetudo/RobbyDobby … onece you save the edited Code then pin one point and try… the vacuum must move.

type: custom:xiaomi-vacuum-map-card
map_source:
  camera: camera.valetudo_s5_glossyhardtofindnarwhal_camera
calibration_source:
  camera: true
entity: vacuum.valetudo_glossyhardtofindnarwhal
vacuum_platform: Hypfer/Valetudo
internal_variables:
  topic: valetudo/GlossyHardToFindNarwhal
map_modes:
...

the above is Yaml for the card I use to test camera … if you set like this you need simply go in the Developer Tools / States and filter the camera entries and once you click on the entity …

access_token: fb386bdd45a5dd0e376f9071a446d1f10bc2caa3c26efb2bd85b1355b074ef29
model_name: MQTT Vacuums
brand: MQTT Vacuum Camera
friendly_name: Valetudo S5 GlossyHardToFindNarwhal Camera
vacuum_topic: valetudo/GlossyHardToFindNarwhal

What after vacuum_topic: is what you need to use in the “topic:” under “internal_variables”.

If you follow this instructions all should work.

[mannebk]

finally, found it.

Followed the instructions and, it works! Who would have guessed… man i could kick my ass.

@gsca075: Please, in the documentation, add an other last point to the HACS installation section at the very end: a pointer to the “card config section” and add “important information for the card setup, please see “card config” !”

cause my brain did switch off when i noticed “manual setup” never realized there is an other headline below it.

Otherwise, thank you so much!

a) for your help with a blind guy like me
b) for this awesome add-on!

[mannebk]

Sandro, maybe you can enlighten me:

how do i get my battery level into the stats fields of the card?

and how do i change mode of operation between sweeping, mobbing and both together?

I currently made me a switch entity above each vacuum.

And i noticed, in the dreame robots, the van level is indicated by a fan with a number, on valetudo, the van is always a fan with ! exclamation mark… can i somehow change that?

also, valetudo robot has way less “info” bubbles belwo, compared to the same model same firmware dreame robot.

Did i miss an other seciton of your documentation?

thank you kindly.
Manny

[gsca075 (SandroC)]

Unfortunately at the moment the card isn’t providing the battery state because of some recent change on the states of the battery in home assistant the author of the card is aware of this and will be fix as soon. As temporary you can enable the status text of the camera from the options and see the battery state from there.

Added: Valetudo has currently no mopping state but for some vacuums like the L10s there are options to change the mopping way…