You could probably build the image from scratch to start on another port. Unless there is an option in Linux to divert the port?
I don’t know Linux to well.
Regarding updating. It’s not something I have tired, so I can’t answer that I am afraid. Might be best asking on Dustcloud or Valetudo GitHub’s
Has someone given thought to modify Valetudo to make use of MQTT ? This might make integration into HA much easier, as there is already an MQTT vacuum component.
I’m using Ubuntu 16.04 LTS using VirtualBox on a Windows 10 Machine. I tried it with Ubuntu 14.04 per the instructions but there were too many issues with Python and VENV versions being too old.
The newest firmware available according to the links on the instructions is v11_003254
All the steps work fine except for the final steps to upload the firmware
When I enter this into the terminal the result is: python dustcloud/devices/xiaomi.vacuum/firmwarebuilder/flasher.py -f output/v11_003254.pkg
Flasher for Xiaomi Vacuum
Address is not set. Trying to discover.
Connecting to device 10.0.2.2...
Sending handshake to get token
Unable to discover a device at address 10.0.2.2
Traceback (most recent call last):
File "dustcloud/devices/xiaomi.vacuum/firmwarebuilder/flasher.py", line 206, in <module>
main()
File "dustcloud/devices/xiaomi.vacuum/firmwarebuilder/flasher.py", line 148, in main
m = vacuum.do_discover()
File "/home/sebastian/dc/.venv/lib/python3.5/site-packages/miio/device.py", line 162, in do_discover
raise DeviceException("Unable to discover the device %s" % self.ip)
miio.exceptions.DeviceException: Unable to discover the device 10.0.2.2
So I added the IP address of the MiRobot (when it’s in WIFI connecting mode) and get the below result: python dustcloud/devices/xiaomi.vacuum/firmwarebuilder/flasher.py -f output/v11_003254.pkg -a 192.168.8.1
Flasher for Xiaomi Vacuum
Connecting to device 192.168.8.1...
Sending handshake to get token
Starting local http server...
Serving http server at 10.0.2.15:38069
Sending ota command with parameters: {"mode": "normal", "file_md5": "a37aa29d89780201fae295f4f42b6f2b", "app_url": "http://10.0.2.15:38069/output/v11_003254.pkg", "proc": "dnld install", "install": "1"}
Ota started!
Firmware downloaded successfully.
Exiting.
It gets to “firmware download successfully” very quickly. I’d expect the MiRobot to tell me it will update and do it’s thing but it does nothing at this point. To get my MiRobot working again i have to use the MiHome app and get it connected back to my wifi router.
Any advice? Do you think it’s new Xiaomi firmware blocking my downgrade?
For the benefit of anyone reading this thread (and not great with linux commands), here are the steps I took to install Valetudo onto the MiRobot after I rooted it to gain SSH access.
Just a quick offtopic question regarding the firmware. Is it possible to update the firmware with the Mi Home app or will I loose root access after that?
It throws an error that “…/dc/image” doesn’t exist midway through the process. This doesn’t happen when i do it for firmware v3254. Despite this I still try to flash it to my Mi Robot however it doesn’t work. MiRobot rejects it.
Is anyone else here using a rooted firmware on their Gen 1 Mi Robot that higher than v3254?
you need to download latest pkg and do the whole rooting process again either from here:
or by doing this: https://github.com/dgiese/dustcloud/wiki/VacuumRobots-disableUpdates and then start the firmware update from your app, then copy firmware from temp folder (look it up in google) and rooting that one, reenabling the crypto and start the firmware upgrade with mirobo.