did you try this to get your new token:
printf $(cat /mnt/data/miio/device.token) | xxd -p
Uhm, I have just discovered ssh is gone. RIP
Token should be good, it’s exposed in the Valetudo settings, the problem is that I can’t restore stock firmware via mirobo running in venv
If SSH is gone, is it possible that means the reset worked? Perhaps delete the vacuum in Mi Home and readd it there to see if it finds it.
I still have Valetudo, I’m searching a way to reset totally. Like fresh install. We are slightly OT 
By the way Valetudo rocks, but IMHO needs more documentation. I’m taking a break from it, hoping newer versions of stock firmware can fix the rotation problem 
I’m wondering how people with complex room cleaning automations deal with map rotation 
Before going down this route today, I had set up a pretty complex cleaning automation (include a nice automation that send the vacuum in after the cat used his litter box to sweep up all the messy litter he throws out of the box). And it worked great… until the map got messed up.
LOL we are in the same boat, looking for opposite solutions 
1 Like
SMART VACUUM NEWSSS
- Can’t SSH
- Can’t upload a custom firmware
- Can’t add to Xiaomi App : If I reset the wifi, I can set it up, it connects to wifi, but fails the last step and can’t add to my account/devices (probably something related to hosts file, even after removing all the Valetudo lines)
- Can’t connect to it via FloleVac
Until someone can help me figure out what to do,
RIP 4 days old vacuum 
(Can still use it locally but without map/zones through)
EDIT: After a 30 seconds reset hole push, it connects to Xiaomi Home, Valetudo still installed, still cannot flash any firmware.
Has anyone got zoned cleanup working on 0.3.1? I have copied the example from the website but my script doesnt work. The Status of the vacuum changes to “Sending command {“command”: “zoned_cleanup”, “zone_ids”: [“Living”]}…”
“Living” is currently setup in Valetudo and working perfectly from the web interface.
vacuum_living:
alias: "Vacuum the Living Room"
sequence:
- service: vacuum.send_command
data:
entity_id: 'vacuum.rockrobo'
command: 'zoned_cleanup'
params:
'zone_ids': ['Living']
1 Like
Hello Guys,
my map on my G1 robot expands often while cleaning up.
So after a few days the cordinates from florevac app doesnt match to my rooms anymore.
Does Valetudo fix this behaviour ?
@cherokee93 do you use an G1 or an G2 ?
SOLVED everything.
If somebody gets stuck on firmware 3.5.0 check this issue on dustcloud github.
@jmadden91 I had the same problem, never been able to make it work but gave up because of what @Dielee is saying. I’m waiting for Xiaomi to add the save map feature. Another workaround is to make zoned cleaning and NEVER full cleanup
@CountParadox try to follow the exact same steps from the valetudo wiki and use mirobo. Your tree should look like this :
tree -L 2 rockrobo/
rockrobo/
├── dustcloud
│ ├── cloudprotocol.pdf
│ ├── devices
│ ├── docker
│ ├── dummycloud
│ ├── dustcloud
│ ├── LICENSE
│ ├── Pipfile
│ ├── Pipfile.lock
│ ├── presentations
│ └── README.md
├── firmware
│ └── v11_001712.pkg
└── valetudo
├── deployment
│ ├── valetudo.conf
│ └── etc
│ ├── hosts
│ └── rc.local
└── valetudo
1 Like
Im using only zoned cleaning, but my map expands some times…
So rooting my vacuum and using Valetudo won’t fix my issue ?
Probably not! 
I feel your disappointment
Should the gen2 vacuums work better ?
Isn’t that for MQTT vacuum only?
I followed the steps exactly and the tree is like that thats why im confused…
it says the file isnt there, but if i cd my way over, there it is ?
Valetudo is exposed as MQTT vacuum to HA.
If you have discovery enabled, yes.
Guess I have to replace Xiaomi Vacuum with MQTT in the config.
Try to cd to image/ prior to running the firmware builder, and use sudo when doing it
Try using 192.168.8.1. I know that’s now your vacuum’s IP but that’s what I did and that’s what’s documented. Try that.