This is related to the latest device firmware, it will be fixed on v2.0.0b17.
5 Likes
Oh. I donāt think I saw thatā¦
Finally got some progress. I donāt know how to figure out the error description or code, other than to listen for it. Hope this helps some L10S Ultra users out there:
alias: DRE_WheelsUp
description: ""
triggers:
- trigger: event
event_type: dreame_vacuum_error
event_data:
entity_id: vacuum.dreame_2
error: Wheels are suspended
code: 1
conditions: []
actions:
- data:
message: Robot is hung up with wheels up.
title: Dreame Notification
action: notify.mobile_app_pixel
enabled: true
mode: single
alias: DRE_PadsOff
description: ""
triggers:
- trigger: event
event_type: dreame_vacuum_error
event_data:
entity_id: vacuum.dreame_2
error: The mop pad comes off during the cleaning task.
code: 69
conditions: []
actions:
- data:
title: Dreame Notification
message: A mop pad has come off.
action: notify.mobile_app_pixel
mode: single
Final note. Apparently you can have multiple browser windows open to be able to listen to multiple events in the Dev Tools section. I plan to run all of them for a week, and see what pops up.
Ah Man, you are the best! 
1 Like
Am working on a mass water notification. Will update when completed.
First to say, I have no plan what i am doing, but for all who looks for X50 support.
First I go to the Dreame App and tap many times on cleaning history, you should come into the network information menue. there i look for the first characters of the sn. In my case its R2532H.
Now I add ādreame.vacuum.r2532hā, under DREAME_MODELS in the config_flow.py of the custom_components/dreame_vacuum. After this I am able to add the X50. Maybe not all functions but it works overall.
1 Like
Thanks it worked
You should not be doing that because the integration needs to know more information about the device other than its model number. Map support wonāt work and you may have serious issues about the specific cleaning options because every generation handles some settings differently.
Hey
Iām looking for some help understanding how custom cleaning works.
I have the x20+ which can mop and vacuum. If I want it to vacuum a room on a thursday and then mop that room on the friday, do I need to use set_custom_cleaning to modify the mode before sending it to clean that room? Would it also need to set the mode back to vacuum for the next time I want it vacuumed?
Is there an easier way that Iām missing?
Thanks
Matt
Ok thanks, even if it seems to work, Iām eagerly awaiting v2.0.0b17. 
1 Like
Yes you are correct but alternatively you can use the onboard schedule feature of the device to achieve that.
I know thats a crappy workaround and not all functions works like expected. But the main controls, sensors and the map (include segment cleaning over the Xiaomi vacuum map card) seems working so far. You said on GitHub that X50 support is not planned and until this changes, itās the only way for me to get some entities in home assistant. Sorryā¦
Hi @tasshack Iāve been trying to post an issue in GitHub but it seems that only Contributors can post them :/.
Anyway, what happens is this:
Describe the bug
When calling dreame_vacuum.vacuum_set_custom_cleaning two or three times it stops working.
To Reproduce
Set up an automation that have this action and run it a few times changing the cleaning_mode:
action: dreame_vacuum.vacuum_set_custom_cleaning
metadata: {}
data:
water_volume:
- 2
- 2
- 2
- 2
- 2
- 2
- 2
segment_id:
- 1
- 2
- 3
- 4
- 5
- 6
- 7
suction_level:
- 3
- 3
- 3
- 3
- 3
- 3
- 3
repeats:
- 1
- 1
- 1
- 1
- 1
- 1
- 1
cleaning_mode:
- 1
- 1
- 1
- 1
- 1
- 1
- 1
target:
device_id: 6f81798aac574a77b2e6fe8e9a4487ef
Some times it will take the change, but after 2 or 3 times it will just stop working.
There is a curious thing, the map of the integration always show the changes, but after I start a Job, for example:
action: dreame_vacuum.vacuum_clean_segment
target:
device_id: 6f81798aac574a77b2e6fe8e9a4487ef
data:
segments:
- 5
It will just go back to the previous value.
Expected behavior
I want to be able to set up Automations per Room having the ability to some times Mop and other times Vacuum.
Additional Information (please complete the following information)
- Model Name [e.g. dreame.vacuum.p2028]: dreame.vaccuum.r2449a
- Firmware Version [e.g. 1156]: 4.3.9_1683
- Home Assistant Version: 2025.1.4
- Integration Version: v2.0.0b16
- Configuration Type [With or without map support]: With map.
- Errors or warnings shown in the HA logs (if applicable): Here
Thanks! It would be helpful to post these kind of issues in GitHub though.
I donāt know what happened, but today everything seems to works perfectly with the X40 Ultra.
Please support xiaomi robot vacuum x20 max, it cannot be integrated via version v2.0.0b16, the device is not recognized yet since it was released on December 24. Thank you very much.
It may not be a vacuum that manufactured by Dreame. I need model number to check that but probably wonāt be.
Xiaomi Robot Vacuum X20 Max - xiaomi.vacuum.d109gl
Not a Dreame deviceā¦
Hi I am desperately trying to get the integration to work, whether beta or normal version I canāt log in.
I enter the correct username and password and always get the error message that I should check the login data.
Can anyone here help me?
Can the current Dreame X50 Ultra be integrated?
Hi @tasshack or anyone who can help 
Iām posting here because Iām not sure if this is an issue on my end or something to open a github issue for.
I have the version v2.0.0b16 installed and Iām connected with my DreameHome account. I have two devices (2x L10s Ultra), and everything seems to work, except that the shortcuts of only one device are working. Initially, the shortcuts of the second device would not even appear in the deviceās controlls list, then eventually they appeared but seem to be unavailable (grayed out, see screenshot).
Any idea what could cause this? If desired, i can open an issue on GitHub.
Thanks for the help
