Hi,
I would have a question about an attribute I didn’t see in other integrations. What is the meaning of “sensor dirty (time) left” and what do I have to do about that? Simply cleaning the sensor like described for example in Sensors Cleaning XIAOMI Dreame D9
Thank you!
Can you check the logs for possible errors?
Where to check the log? I found this message after a long time waiting.
And there is an error log in my HA.
Logger: homeassistant
Source: runner.py:96
First occurred: November 11, 2022, 11:40:42 PM (906 occurrences)
Last logged: 9:20:26 PM
Error doing job: Unclosed client session
Hi everyone,
Thanks for the work on this integration. My dreame came true.
Unfortunately i seem to have problems using the integration.
My dreame l10pro is residing in another VLAN on another subnet and no matter what i try. I cannot seem to make the integration work.
All i get is:
Retrying setup: Unable to discover the device 10.0.20.213
I can ping the robot from hass without problems and all services are alowed to be routed.
I see home assistant is sending packets to the robot but its not responding at all.
Anyone else ran into this? Any solutions?
Is running the robot on a separate subnet supported or will the robot just not communicate over anything else than its own subnet?
Actually this is a well known limitation from the xiaomi devices.
https://python-miio.readthedocs.io/en/latest/troubleshooting.html#discover-devices-across-subnets
Please check this solution.
Oh thanks, i missed that!
I only used zigbee devices from xiaomi up to now.
Ill try and work out masquerading the traffic tonight! 
Dear tasshack,
Question please: will there be support in your custom component for the DREAME F9 robot?
THANK YOU for your answer!
Wonderful integration @tasshack, I have been looking for this quite some time. My L10 Pro just got smart(er).
One question though, in the Mi Home app I can send my robot to a certain room. But can I do this with your integration? I don’t see anything obvious, but I guess I can tweak the order of each room in a script (but only chose the one room I want to clean) and run that as a script or automation?!
I am working on it right now but it will not be available soon.
Thanks @tasshack for your addition to Home Assistant. However, I am having some issues post- setup and install. My Home Assistant server, clean install - rPi 3b+, gets stuck in a crash loop when the vacuum is running. I’ve tried removing and reinstalling the integration. (Testing both “prefer cloud connection” and without, same results) Specifically, where in the logs should I be looking for a diagnosis?
First you need to check for warnings and errors created by dreame_vacuum integration.
Second, you need to update the log level to info for getting more information about what the integration is doing.
logger:
default: warn
logs:
custom_components.dreame_vacuum: info
I am not sure that the rpi 3 can handle the map image rendering fast enough but you may consider using valetudo map card instead of live map camera entitiy.
Prefer cloud connection feature is not stable yet i will fix it on the next release. Also having another xiaomi integration installed like miot auto also will cause an stability issue with the cloud connection and i hope to fix that too (I think there is an rate limiting with the xiaomi cloud api that causes the problem).
Hope it will support Mi Mop Pro 2 (dreame.vacuum.p2041o) soon 
I want to know if I have to connect Mi App? I cannot use Dreame app to connect the vacuum?
You need to use Mi Home App and account.
Sorry to bother, but it seems I cannot connect when using a subnet.
My home assistant is connected to router, router is connected by LAN to access point, and then vacuum connects to access point.
When trying to setup, it seems to have the IP address of the access point. Is there a way for it to use the IP address of the router? If I select “prefer cloud” it works no problem
Prefer cloud actually communicates with the device over cloud and not recommended to use if server and device are at the same network.
Please check this solution
Thank you for your reply. I do not know if it is coincidence but I added the device via Xiaomi Miot integration first using the IP address and token method. After that I add Dreame Vacuum integration and it seemed to work properly (added correctly without selecting prefer cloud)
Previously it would say Initializing and then fail, attempting to communicate with the device on the wrong IP without any ability to change.
Either way, thank you for this integration. I gave what I could, times are tough and I appreciate you making this.
Thanks for the contribution.
Dreame devices do not respond to api requests from different subnet and this is a known issue because of that Xiaomi Miot also uses similar feature like Prefer Cloud.