Valetudo Map Card Installation Instructions

[tldp]

Tried to install Valetudo Map Card. Installed via HACS as suggested.

According to the instructions the card should be registered right away - it was not.
Also acc. to the instructions the path for manual registering should be

/community_plugin/lovelace-valetudo-map-card/valetudo-map-card.js

which also didn’t work for me.

I had to register the card by adding the path

/local/community/lovelace-valetudo-map-card/valetudo-map-card.js

to lovelace’s resources.

Hopefully this will save some time for the next poor soul trying to get this to work!

Side note: don’t forget to add the vacuum_entity property if you want buttons to show up.

[mibcat (Michael)]

Hi !
I have also problems installing this package and couldn’t solve it so far.

I’ve followed the installation instructions of hacs and the lovelace plugin several times with no success.

Always the same behavior: the card isn’t registered and attempts to add it manually fails obviously (but without any noticeable error message).

I’ve searched the location of the JavaScript file on my system and found it relatively to the root folder of my HA installation at

./www/community/lovelace-valetudo-map-card/valetudo-map-card.js

According to your post I tried both paths

• /local/community/lovelace-valetudo-map-card/valetudo-map-card.js
• /local/www/community/lovelace-valetudo-map-card/valetudo-map-card.js

but without success.

I’m using:

• Home Assistant 2021.8.8 running on a Raspberry PI 4 in Docker
• HACS 1.15.1
• Lovelace Valetudo Map Card v2021-08-12

Any hints that might solve the problem ?
(Maybe to enable logger for debug messages to see if the JavaScript file was found and loaded ?)…

Thanks,
Michael.

[tldp]

Hi and welcome to the forum!

No need to tinker with anything (anymore?), in the meantime I removed any manual changes I made and just installed it using HACS.

Please bear in mind that there will be no new card type visible in Lovelace, you have to configure it manually!

My current config looks as follows:

type: custom:valetudo-map-card
vacuum_entity: vacuum.robot
entity: camera.map
title: null

If you did that already try

• deleting your browser’s cache
• using a different browser
• using your browser’s private mode

[mibcat (Michael)]

Hi, and many thanks for your feedback.

According to your information I was finally able to fix it !!!

1. I had to add a new card explicitly to the dashboard.
   The above shown card was added automatically once the robot was detected the first time.
   But I had to adjust the lovelace config slightly (due to different valetudo firmware ?):

  type: custom:valetudo-map-card
  vacuum_entity: vacuum.valetudo_robot
  entity: camera.map_data
  title: Rockrobo Map

2. And I still had to add the JavaScript manually - there was no automatic detection:
   
   

[tldp]

Glad to hear that!
The IDs may differ, since you can set those manually when setting up the vacuum in HA.

#2 is weird, but as long as everything works now ¯_(ツ)_/¯

[mibcat (Michael)]

Yeah, I’m happy now

The map is showed but also a “not loaded” warning/error under hacs/frontend:

(had to split the message into parts because as new user I’m only allowed to upload one image)

[mibcat (Michael)]

Tried to remove the entry from config/lovelace/resources but than the card isn’t available:

[mibcat (Michael)]

Adding the resources back:

strange …

[poesel (Markus)]

Sorry to dig this up but I have the same problem. Installed HACS and the valetudo map, latest versions of course. HA is current.
The .js ended up in /config/www/community/lovelace-valetudo-map-card/.
There is no /local/… path on my system. Do I have to create it? (that would be no problem)

Thanks.

[Diabe]

Hey everyone, so recently I am the proud owner of a Dreame L10 Pro. I have rooted it with Valetudo and all is well.

The only issue i’m experiencing is that I can’t seem to get the map card working for lovelace.
It is showing the Valetudo image alright. But it keeps saying I need to install the map card.

I have installed it through HACS, also inspected the MQTT package from the vacuum and I see map data being sent. But somehow, no matter what I do it is not showing.

Also tried clearing my cache, makes no difference.

Hopefully someone can help me since it’s such a cool feature.

[PsyGanja (Steve Landisch)]

I have a problem too. The map is not displayed. Custom map is installed, entity found. But the entity is always idle.

Does somebody has any idea?

[Flodo1987]

Hi
I have the same problem as my pioneer, I’ve already searched the internet and haven’t found a solution. I just can’t get the card to work, hopefully someone else reading here can help.

[aaronk (Aaron)]

Hi @Flodo1987, this works for me:

- type: "custom:valetudo-map-card"
  vacuum: valetudo_roborock

I looked into the source code of the card and found this:

  getMapEntityName(vacuum_name) {
    return "camera." + vacuum_name + "_map_data";
  }

  getVacuumEntityName(vacuum_name) {
    return "vacuum." + vacuum_name;
  }

So it just expects the name and will derive the entity IDs from it.

[gsca075 (SandroC)]

For who is looking for a really easy way to do integrate the maps from Valetudo… the Valetudo Vacuum Camera is configurable with few simple steps, download, install, setup without a line of code written.

[solarsol (solar)]

Hi gsca075

I can’t manage to get Valetudo Vacuum Camera to work.

I own a X40 from dreame.

Are there any prerequisite aside of having the dreame integration effective? Said integration exposes camera.bot_map_data.

I proceeded to install yours and went to System > Devices and Services > + Add Integration > MQTT Camera Setup
And when I click the empty field, it offers only to enter vacuum.bot as expected. I click submit and I get “unknown error occurred”. Any idea?

[gsca075 (SandroC)]

Hi @solarsol
I’ve seen a similar report and I will check as soon… it looks there is small misunderstanding, MQTT Vacuum Camera… Did you check the install guide here? The vacuums are display and then it should be possible to add them anyhow as per recently there was another issue… similar to what you reported I will check… what firmware runs your X40 and what HA version are you using? Can you please eventually report your issue on here please. I 'm pretty sure that with the older version (currently still need to install and test the last of Valetudo)… it works as expected.

[solarsol (solar)]

Hey there! thanks for replying. here’s the answers. I will report my issue on the other place too.

I followed the install guide.

I’m running the latest HA (I actually installed 72h a go for the first time), latest X40 firmware 4.3.9_1536

[gsca075 (SandroC)]

@solarsol did replay already in there but…

• No logs of the issue you are reporting are available.
• There is only one scenario possible causing the issue you are reporting and it is the following:

• No MQTT connection (but you reported you can see the vacuum on HA)
• The vacuums has no map data / issue with the status text data (I’m checking).
• Either the cases MQTT_Vacuum_Camera must be setup there so the error comes after the integration is setup, then probably you deleted the camera correct?

[solarsol (solar)]

hello again.

So I investigated MQTT itself following your reply. Indeed it was stopped and couldn’t be started. I got it working but still no success with your plugins (still " unknonwn error occurred")

I have MQTT IO running:

1. Protection mode ON, configuration file
2. config.yml in /config/mqtt-io/ confirmed
3. mqtt:
   host: core-mosquitto
   port: 1883
   user: “username I defined” in HA system/people and users/users
   password: “password I defined” in HA system/people and users/users
4. however, in System/Devices & Services/MQTT there’s one entry: coremosquitto but no device or entities attached

is that normal?

[gsca075 (SandroC)]

@solarsol Again this is strange:
do you see those?

as you can see I run the same version.
The credential in the robot should be in here:

the host should be the IP address of your HA instance.

The camera setup:

After that we use the Topic, that by default is setup in the Vacuum.
if you can provide a log for instance… I can better investigate, meanwhile I will check if I get an X40 json and verify the startup.