Custom Component: Dreame Vacuum

I don’t know what to make of this. Can you share the HA log when you try to add the device?

Yes of course tell me how to get it?
Main log is empty

Thanks for that but unfortunately it doesn’t work. I have a script as follows:

clean_daily:
  sequence:
    - service: vacuum.send_command
      data:
        command: action
        params:
          did: "6.2"
          siid: 6
          aiid: 2
          in:
            - piid: 4
              value: "{\"customeClean\":[[1,3,1,1,0],[2,3,4,2,2],[3,3,1,1,0],[4,3,4,2,2],[9,3,4,2,2],[6,3,1,1,0]]}"
      target:
        entity_id: vacuum.dreamebot
mode: single

I have more rooms that those but I only want to clean 1, 2, 3, 4, 9 and 6. When I run this script nothing happens. Not even an error occurs.

You cannot set cleaning mode with clean_segment service, it is not supported by the device.
Please refer to these topics

Update your logger settings and look for the home-assistant.log file.

logger:
  default: warn
  logs:
    custom_components.dreame_vacuum: info

Now I am totally confused :frowning: Didn’t I do what the offered workaround describe? I mean, I copied the code in the workaround and just changed the numbers.
I just want to understand what I did wrong and how to do it right …

Many thanks for your efforts and, of course, the brilliant result!

I have Dreame X10; it easily adds to my home assistant, but there are some issues:

  1. I can see the map only if I turn on “multi-floor map”. If this option is disabled, the map is unavailable.

  2. I use the “Xiaomi vacuum map card”, but it doesn’t show the current location of the vacuum, and the map also doesn’t show the history track of cleaning.

  3. When I enabled “customized cleaning,” nothing happened. Room entities are still unavailable, and in the attributes option, it has the state “false.”


It sounds like encryption problem with the current map, you can see other maps when you enable multi-floor map because they are stored unencrypted. Also room entities are tied to the current map but generated from all maps.
Can you share the HA log with the full model number of your vacuum?

Thanks for response, as you suggested, in logs i have some errors like “decryption failed” and several else.



Hallo tasshack,

thank you in advance for your great work. Unfortunately, I have the problem that I cannot connect to my Dreame D9 vacuum robot.

I also checked the token with PiotrMachowski’s extractor and everything is correct.

in the xiaomi intergation the “connection” works but i can’t control the device.

do you have a solution suggestion for me?
many thanks in advance.

I hope the google translator did a good job

I have checked the key store and r2215 actually does not have a private key specified in the integration.
I am going to add the key for your device and your issue will be fixed on the next release.
Thanks for pointing out a really important bug.

1 Like

Please make sure your vacuum and HA is at the same subnet.

Many thanks for fast response! Will be looking forward to new releases!

Also on GitHub in ToDo list i find very desired features:

  • Live camera stream support
  • AI Obstacle image support

Is it really possible to make a camera stream? Cause in Mi app camera stream unavailable, only in Dreame app this option exist. And it’s always difficult trade-off between camera support, and good automations in home assistant

Functionality is in the device, it is just not populated on Mi Home App plugin. I can make it work with HA, it just needs a little bit of reverse engineering. Unfortunately i don’t have a vacuum with camera or access to Dreamehome App and it is hard to find people willing to gave access to their device which has a camera on it.

I can give you access to my Dreame x10. Please check your PM.

Hi,
I was looking into automating specific room cleening of my L10s. I found in the documentation how to do the vacuuming, but i can’t seem to do the mopping. I would like to setup a mopping run only on a room. Any info on how i should set it up?

What i already tried:

service: dreame_vacuum.vacuum_clean_segment
data:
  segments: 5
  suction_level: 0
  water_volume: 2
target:
  entity_id: vacuum.dreamebot_l10s_ultra

Regards

Really good work! Thank you.

Any idea if (dreame.vacuum.p2041o) will be supported?

On the next release…

1 Like

You cannot both set cleaning mode and start cleaning at the same time like the suction level and water volume settings, it is not supported by the vacuum. Instead, you need to update the cleaning mode before sending the clean segment action via select option service of the cleaning mode entity.

aah i see, thanks for the help. I just realised that it would probably be something like that :slight_smile: