xiaomi cloud might be using a cached map, but it is able to wake up the vacuum. Try it yourself - even when vacuum is asleep (shows “sleeping” in the mi app - you can cause this sleep by removing it from dock - say by sending to a target and letting it sit there for some time), you can send it any command and it wakes up. however the map extractor as well as xiaomi vacuum integration doesn’t work during that time.
the trimming bug exists in 1.0.0 (the version i see installed in my HACS)
I use the same library as built-in Xiaomi vacuum integration, so I have the same limitations (my first idea - not tested - is that “normally” vacuum is listening for commands and when it’s “sleeping” it pulls data from the cloud periodically).
Anyway, I can sometimes get good results cleaning zone by zone, max 2 zones. Just too bad that Xiaomi people stopped firmware development for this model… This card will increase life of my cleaner!
Also interested in the dreame f9, this is the same as the xiaomi mi essential, right? Does it support no-go zones? I need that… I have heard it was experimental, and now removed…
i am going to buy a second cleaner for upstaris, i was thinking for the Dreame F9 , is it supported?
this custom component works for HA integration: https://github.com/microfrost1/xiaomi_vacuum
but will the map extractor work?