OMG, I just managed to add my Dreame X40 Ultra to HA using the latest beta v2.0.0b19.
Does anyone know what are the two checkboxes at the bottom of the list for?
Square map is for rendering the map image 1:1 instead of its own ratio, useful if you have more than one map on your dashboard to be displayed at same height.
Low resolution map is for HA instances running on machines lower than 2GB memory.
Hi everyone,
@tasshack thank you so much for explaining those two checkboxes.
As mentioned before I managed to add my Dreame X40 Ultra to Home Assistant using the HACS Dreame Vacuum integration.
I also installed the Xiaomi Vacuum Map Card to access features like the live map.
Here’s what I added to the dashboard:
Almost all the buttons seem to work out of the box without any additional configuration, except for the zone cleaning feature (or perhaps I’m using it incorrectly).
Could someone please clarify the purpose of the two buttons:
Zone Cleanup and the + (plus) sign?
My current understanding is:
- Zone Cleanup: starts cleaning a specific room or predefined zone.
- + (plus): allows you to manually add a zone to be cleaned.
Is that correct?
In any case, when I try to start cleaning using either of these options, I get the following error:
Action xiaomi_miio.vacuum_clean_zone not found.
Does anyone know why this error appears and how I can fix it?
Thanks
Select correct platform option from card configuration.
1 Like
Resolved: I just needed to select the correct option for the card.
Thank you so much, @tasshack! This HACS integration is awesome.
Just one last question: now that I’ve selected the correct platform option, room cleaning is working perfectly. However, when I click on the Rooms icon, I get a long list of repeated rooms, as shown below:
Is there something I’m missing? Do I need to edit the configuration YAML to tidy that up?
Hi all,
I would like to have my “Dreame X50 ultra complete” in HA, but seems this not (yet) compatible with the integration.
I tried V2.0.0B19 but got this
Any idea on a timeline 
Many thanks
Hi I wonder if you can add the model L10 Prime to the compatibility list. Thank you.
v1.0.6 has been released!
- Xiaomi 2FA and Captcha support
- Fix for deprecation warnings
v2.0.0b20 has been released!
- 50 new supported devices
- Xiaomi Captcha support
- Passable/Impassable threshold rendering
- Curtain rendering
- Ramp rendering
1 Like
Is there any way to integrate the mova 2461a?
Its a not released Vacuum Roboter.
Thx
Probably after its release.
OK, thx
The device will not be released in this form, as Mova is revising it based on tester feedback.
Have i any other possibility to integrate the device?
Any Idea?
If there any way to integrate the device as local?
Thx
no issue 
just thank you for the great integration. Impressive made!
I’m quite disappointed that this update introduces a donation notification, especially since the option to disable it doesn’t appear to work for me. This kind of forced messaging feels intrusive.
It only seems to appear once - it’s not something that appears on every core restart.
It will only display once after each version update and you can disable with the donated configuration option for future updates.
It is just for remind you how much time and afford is needed to keep this project up to date for over three years.
1 Like
I can only add support to the models that I can access its plugin via cloud API.
You cannot control it over local because it is only possible when the vacuum is installed on Mi Home app on older firmware versions.
I may not understand how to set the donated option, but when I make the selection via the device entry on the integration page, it simply resets itself.
That means your HA instance cannot save configuration changes for some reason and you need to fix it by understanding why. Also the same reason you keep seeing the notification every time.
This is definitely not the integrations fault when your Home Assistant is not working as expected.
I cannot reproduce this behaviour on any of the other options within that menu, they all store their selection properly. I spot nothing in the logs that would indicate a failure of some sort.
Are there any specific details I could check beyond that?
If that is the case then it might be my fault, I will fix it on the next release.
You can solve this issue by removing the device and adding it again with selecting the donated option at the last step of device configurator. You won’t be loosing any data when the device has been removed and added again.
But you should not be seeing the donation notification more than once even without the donated option until the next release, I cannot explain that, adding the device again also should fix that too.