Thanks @Fietspomp for your confirmation, I’m glad to know that you’re successfully using my code.
I upgraded a little bit the repo to fit better the default paths making easier to install.
Thanks @Fietspomp for your confirmation, I’m glad to know that you’re successfully using my code.
I upgraded a little bit the repo to fit better the default paths making easier to install.
Great, it’s working fine here, glad to see you updated it for other people to use.
The rooting is quite simple by the way, especially if you already know the token from old MiHome apk.
Then rooting is done within 10 minutes.
What a time to be alive, rooting the vacuum
Great, thank you @asphalter! Just hadn’t time to look for this for a month… and now it’s work (on my v2)
But in your README you might change ‘chown’ into ‘chmod’.
My vacuum seems to create a new map file at least every time I start a full clean-up. It seems like the map files will stay in .hassbian/vacuum, each about 3MB. I think we should clean up the old files from time to time.
How does the FloleVac app connect to Xiaomi servers and download the maps?
Is there any way we can implement something like this?
@asphalter If HA crashes the lock-file prevent the script from running on restart. I fixed this by modifying my HA start script to delete the lock-file.
Actually i believe the FLOLE app does not access the Xiaomi Cloud as it requires home network access. Maybe its possible to download the Map from the Robot directly without modifying any firmware?
I read a post by Flole on roboter-forum that said it downloads from straight from Xiaomi. I hope there is a chance it can happen!
Seems like its a TradeSecret, i was asking the FLOLE APP Support for some tips on how to achieve it, and the answer was: They are not allowed to talk about it.
Flole got the map from the cloud. I have tried blocking internet access for my vac and the map wouldn’t show on Flole.
Hey,
thanks for the great work!
I’m successfully using your code, just have one question:
the maps dosen’t seem to update “live” or (1-2s) like you mentioned above, but seems to update only when it’s moving and every minute maybe…?
should it be more like a live-feed similar to the one the official app gives? any idea of where i could look for a solution?
Hello guys!
Just a quick question: have any of you updated the FW of the vacuum using the Flole app?
One the Xiaomi app shows no update is available but on the Flole app I get this:
Thanks!
Hi everyone,
first of all I want to say thank you for your great work asphalter!
Now I only have one issue by setting up the “live map”
When I run the script on the vacuum I always get an error that it is not able to connect to homeassistant and I have to enter the password. I set up the acess with the ssh key files and I also can manually login on the homeassistant user from the vacuum with the keyfiles, but I always get a login error when I start the script.
Can anyone help me?
I fixed it. I had to rename the public key in id_rsa.
I am running it on a raspberry pi and the image is only refrashing every 5Minutes. The home assistant goes out of synch. On hich device does your home assistant ran?
I’m looking for someone who can help me with a particular problem regarding the maps. I’d like to clean my home and my business with my vacuum cleaner, so the idea is to use the wifi for the robot to identify where it is and load the correct map. Also is it possible to store zones on the map permanently, so if I take it to work and run it after hours it will only clean the zones I mapped out for it, not the whole map, basically prevent it from going into places where it gets stuck, without having to map out the zones every time.
If someone can solve this I’m willing to pay because it’s really annoying problem.
There’s no solution for this for the moment
Feel like I’m being thick. Tried for the past 45 minutes to root my Xiaomi Vacuum Gen2… Getting multiple error messages. Is there any easier way to do this? Am using Terminal on OSX.
Am stuck on step 10) of dustcloud.
Error returned is:
sudo /Users/x/dc/dustcloud/devices/xiaomi.vacuum/firmwarebuilder/imagebuilder.sh 0051518
Running on a Mac, adjusting commands accordingly
readlink from coreutils package not found! Please install it first (e.g. by brew install coreutils)
I’ve reinstalled coreutils several time, but no solution!
Help, please/
There is a warning on Dustcloud about Macs
These instructions used to work with Mac OS High Sierra. However, it seems as if the images created aren’t compatible anymore and cause the robot to revert to the currently installed image. See issue #83. The instructions are left as is at it may be working with older Mac OS
Do you have access to a standard Linux install or a Raspberry PI?
I rooted mine using a PI was easy to do.
Thanks for that. I had totally missed out on this info!
I have access to a Win 10 machine. Can set up a Pi, but that sounds like a pain. I’ll try on a PC first by running a docker Linux image! My Home Assistant server is hosted via Docker on a Synology.
I’m using your solution, with a few changes to accommodate to my system.
Since I’m running Hass.io I had troubles installing what I needed to get the script to run. Instead I run it in a Docker-container on a server which has the script modified to copy the resulting image to the RPi running Hass.io via samba, which in turn presents it as a camera-image.
It’s a bit of a messy solution, but it certainly gets the job done!
Have you thought about making this into a Hass.io-addon?
Thanks for your work on this!