Xiaomi Mi Robot Vacuum gen 1 not start cleaning with Zoned cleaning schedule
userosos opened this issue · 9 comments
An Xiaomi Mi Robot Vacuum gen 1 not start cleaning. Before this moment (3 Jun) it work ok 5 mounths about.
How to Reproduce
I think that it will be work everyday.
Screenshots
I use firefox 91.0.2 (64-bit)
Have you checked valetudo log (in settings->info) for clues?
Have you checked valetudo log (in settings->info) for clues?
Yes, but i cant understend it.
2021-08-31T15:56:30.875Z Timesync packet received
2021-08-31T15:26:30.875Z Timesync packet received
2021-08-31T14:56:30.876Z Timesync packet received
2021-08-31T14:26:30.875Z Timesync packet received
2021-08-31T13:56:30.875Z Timesync packet received
2021-08-31T13:26:30.875Z Timesync packet received
2021-08-31T12:56:30.875Z Timesync packet received
2021-08-31T12:26:30.875Z Timesync packet received
2021-08-31T11:56:30.875Z Timesync packet received
2021-08-31T11:26:30.875Z Timesync packet received
2021-08-31T10:56:30.875Z Timesync packet received
2021-08-31T10:26:30.875Z Timesync packet received
2021-08-31T09:56:30.875Z Timesync packet received
2021-08-31T09:26:30.875Z Timesync packet received
2021-08-31T08:56:30.875Z Timesync packet received
2021-08-31T08:26:30.875Z Timesync packet received
2021-08-31T07:56:30.875Z Timesync packet received
2021-08-31T07:26:30.875Z Timesync packet received
2021-08-31T06:56:30.877Z Timesync packet received
2021-08-31T06:26:30.875Z Timesync packet received
2021-08-31T05:56:30.875Z Timesync packet received
2021-08-31T05:26:30.875Z Timesync packet received
2021-08-31T04:56:30.876Z Timesync packet received
2021-08-31T04:26:30.875Z Timesync packet received
2021-08-31T03:56:30.875Z Timesync packet received
2021-08-31T03:26:30.876Z Timesync packet received
2021-08-31T02:56:30.875Z Timesync packet received
2021-08-31T02:26:30.875Z Timesync packet received
2021-08-31T01:56:30.875Z Timesync packet received
2021-08-31T01:26:30.876Z Timesync packet received
2021-08-31T00:56:30.629Z Timesync packet received
2021-08-31T00:56:30.624Z Robot connected
2021-08-31T00:56:21.028Z scheduled cleaning timezone offset set to 180
2021-08-31T00:56:20.993Z setting scheduled cleaning timezone to Europe/Moscow
2021-08-31T00:56:17.160Z Probed last id = 1001 using get_status (3 retries)
2021-08-31T00:56:16.144Z Webserver is running on port 80 (http)
2021-08-31T00:56:16.138Z Dummycloud is spoofing 203.0.113.1:8053 on 127.0.0.1:8053
2021-08-31T00:56:16.029Z No ssl key found. Expected path: /mnt/data/valetudo/key.pem
2021-08-31T00:56:16.027Z No ssl cert found. Expected path: /mnt/data/valetudo/cert.pem
2021-08-31T00:56:15.907Z timesync: 31 Aug 03:56:15 ntpdate[1728]: step time server 85.21.78.8 offset 1.583839 sec
2021-08-31T00:56:12.834Z Loading configuration file: /mnt/data/valetudo/config.json
Waiting for 30 sec after boot... done.
2021-08-31T00:26:25.859Z Timesync packet received
2021-08-30T23:56:25.859Z Timesync packet received
2021-08-30T23:26:25.859Z Timesync packet received
2021-08-30T22:56:25.859Z Timesync packet received
2021-08-30T22:26:25.859Z Timesync packet received
2021-08-30T21:56:25.859Z Timesync packet received
2021-08-30T21:26:25.859Z Timesync packet received
2021-08-30T20:56:25.859Z Timesync packet received
Well, and did you try creating new timers or just re-saving the existing ones?
Well, and did you try creating new timers or just re-saving the existing ones?
Yes, i created an new timers. Not helped for me.
Before this moment (3 Jun) it work ok 5 mounths about.
What did you change after it worked 5 months? Any configuration changes, updates,... ?
@pidator, probably valetudo was updated since we see 0.10.7 in screenshots and 5 month ago from June it simply didn't exist yet. So the only guess I could make is that after "watergrade" features were introduced in .10.6 there appeared a number of incompatibilities with existing timers configuration, though they should be fixed just by re-saving those older timers. Jeez, why the heck did I merge that stuff we'll never get in 1-2 gen devices at all? I'll never know...
@userosos, as the last solution you can try downgrading back to 0.10.5 release.
What did you change after it worked 5 months? Any configuration changes, updates,... ?
I think that i do nothing.
@pidator, probably valetudo was updated since we see 0.10.7 in screenshots and 5 month ago from June it simply didn't exist yet. So the only guess I could make is that after "watergrade" features were introduced in .10.6 there appeared a number of incompatibilities with existing timers configuration, though they should be fixed just by re-saving those older timers. Jeez, why the heck did I merge that stuff we'll never get in 1-2 gen devices at all? I'll never know...
May be. I think that it true.
@userosos, as the last solution you can try downgrading back to 0.10.5 release.
Ok. I will test it.
How can i do it without reinstall OS?
i do
sudo wget https://github.com/rand256/valetudo/releases/download/0.10.5/valetudo-re_0.10.5_armhf.deb
sudo dpkg -i valetudo-re_0.10.5_armhf.deb
Now i cant see web page valetudo-re.