Yeah, and getting stranger by the hour too…
I see MQTT
MQTT Vacuum Camera doesn’t appear in thet list as no integration can be configured (the vacuum “unknown error”
In this terminal image, you can see that the command Mosquitto_pub works so something is connected right. I just don’t know what isn’t. (that specific command is the one recommended to test for errors in MQTT’s documentation
Valetudo V1 SilentTepidStinkbug Robot is the how should look the standard Valetudo… entity id isn’t it? you have a vacuum.bot I assume renamed entity in home assistant? is in your Entry of MQTT? if you have only the coremosquitto I think you can resolve it in this way… You need to delete the entity coremosquitto (that by the way is the cause at this point, because I had a similar problem in the past). So disable the entity in MQTT and delete then delete it.
After done, from the add-on store, restart Mosquito.
Then in devices add MQTT
I did all you said: disable then delete the integration entry, restart mosquito, re-add the entry and still unsuccessful. I’m gonna copy all I can here.
Yes, the bot has been renamed “bot” so the its entity is vacuum.bot, the camera is camera.bot_map, the current map data is camera.bot_map_data
First MQTT (Addon page, config.yml, configuration, and log), then Mosquito (same) then Dreame
1. MQTT
a. Settings>Addons>MQTT IO and the Configuration tab
b. MQTT add-on logs (Seems to me it’s all ok)
c. the config.yml itself
d. system>Devices & Services>MQTT gives me the mosquito integration but with no entry
e. system>Devices & Services>MQTT>Configure
f. system>Devices & Services>MQTT>Configure>Re-Configure
In here, I’ve put the username and password of my user
2. Mosquitto
a. Settings>Addons>Mosquitto Broker and the configuration tab
b. logs
3. Dreame
a. I’m on the latest beta as per HACS>Dreame Vacuum>Re-download>Releases
b. 1 device + 172 entities
system>Devices & Services>Dreame Vacuum
When I go into configure:
Do you need anymore data ?Tell me where to find it and I will bring it to you
mmmmm that is not Valetudo 
this is why the Camera isn’t working in your case… but okay… I will have a look to the integration you use and decide if we can get the maps data from there… are we okay with that?
So you mean to ask me to integrate my vacuum using valetudo?
aside that, totally okay with that what do you need from me ?
@solarsol no, absolutely I’m not asking you to integrate the vacuum with Valetudo but this thread and it’s contents are for Valetudo…, Xaiomi Map Extractor should handle your vacuums maps if not wrong… anyhow the Dreame integration as I see is providing the maps in one of this between the 172 entites in your screnshot… as Valetudo alternative… looks good…
If when you setup your MQTT there is no Vacuum… there isn’t much I can do… as the aim of the integration I’m developing is to somehow cover the luck of entities sometimes there is by using those “unclouded” vacuums in Home Assistant.
As I see from the link I provided, you should be good to Go… if you are okay with the cloud remote control… or whatever method this component offer to control your vacuum in Home Assistant…
Please remember “Never touch a running system” is the role number 1…
Anyhow I got to thank you as per… when the vacuum isn’t supported the MQTT Vacuum Camera integration should simply error “Unsupported vacuum” instead of “Unkown Error”… 
Alright, you clarified the whole thing for me, thank you very much.
Dreame integration provides its own map and so doesn’t do it over to valetudo, am I correct? hence why I can’t find it via MQTT.
This works good, I can even use Homekit bridge to display the map as a camera in homekit. However, when I go into it, the stream stay frozen and doesn’t update. only the preview on Homekit’s homepage.
Then there’s camera.current_map_data which also provides the same into homekit however: it says “install Lovelace valetudo card to see the data embedded here”. Hence why I contact you but I understand the burden isn’t on you, it’s on the dreame integration maker. am I correct?
@solarsol @gsca075 Dreame integration does actually provide a map data entity to be used by Valetudo Map Card but it is disabled by default.
You need to enable camera.[Device Name]_map_data entity manually from your device page then you can select your vacuum from the card configuration and it should work.
It is mainly intended to be used from low memory devices (<=2GB) since backend rendering of the map image has huge impact on. Idea is that you can disable the standard camera map entity and use Valetudo Map Card to render the map data in frontend to spare some memory and CPU time from server.
