Roborock S50 doesn't finish cleaning.

[10bn]

Since a couple of days the robot doesn't clean the full apartment anymore.

Is there a log I can check to see why it stops and returns to the dock?

Vacuum Model: Roborock S50

Valetudo Version: v.0.10.7

Last System log:

2021-06-29T13:24:46.365Z MQTT Error : update_map_data_topic : mqtt updateMapDataTopic timed out
2021-06-29T13:23:14.340Z Timesync packet received
2021-06-29T12:59:52.687Z Connected successfully to mqtt server
2021-06-29T12:59:41.530Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:59:31.518Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:59:20.403Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:59:10.388Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:58:59.300Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:57:56.975Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:57:46.964Z MQTT Error : mqtt_general_error : {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"10.25.10.2","port":1883}
2021-06-29T12:53:14.339Z Timesync packet received
2021-06-29T12:23:14.339Z Timesync packet received
2021-06-29T11:53:14.339Z Timesync packet received
2021-06-29T11:23:14.338Z Timesync packet received
2021-06-29T10:53:14.339Z Timesync packet received
2021-06-29T10:23:14.338Z Timesync packet received
2021-06-29T09:53:14.339Z Timesync packet received
2021-06-29T09:23:14.339Z Timesync packet received
2021-06-29T08:53:14.338Z Timesync packet received
2021-06-29T08:23:14.339Z Timesync packet received
2021-06-29T07:53:14.339Z Timesync packet received
2021-06-29T07:23:14.338Z Timesync packet received
2021-06-29T06:53:14.339Z Timesync packet received
2021-06-29T06:23:14.339Z Timesync packet received
2021-06-29T05:53:14.339Z Timesync packet received
2021-06-29T05:23:14.339Z Timesync packet received
2021-06-29T04:53:14.339Z Timesync packet received
2021-06-29T04:23:14.338Z Timesync packet received
2021-06-29T03:53:14.339Z Timesync packet received
2021-06-29T03:23:14.339Z Timesync packet received
2021-06-29T02:53:14.339Z Timesync packet received
2021-06-29T02:23:14.339Z Timesync packet received
2021-06-29T01:53:14.339Z Timesync packet received
2021-06-29T01:23:15.897Z Connected successfully to mqtt server
2021-06-29T01:23:15.154Z Probed last id = 1001 using get_status (3 retries)
2021-06-29T01:23:14.085Z Timesync packet received
2021-06-29T01:23:14.078Z Robot connected
2021-06-29T01:23:13.804Z Webserver is running on port 80 (http)
2021-06-29T01:23:13.799Z Dummycloud is spoofing 203.0.113.1:8053 on 127.0.0.1:8053
2021-06-29T01:23:13.715Z No ssl key found. Expected path: /mnt/data/valetudo/key.pem
2021-06-29T01:23:13.714Z No ssl cert found. Expected path: /mnt/data/valetudo/cert.pem
2021-06-29T01:23:13.586Z timesync: giving up
2021-06-29T01:23:02.648Z timesync: retry
2021-06-29T01:22:51.711Z timesync: retry
2021-06-29T01:22:40.761Z timesync: retry
2021-06-29T01:22:30.656Z Loading configuration file: /mnt/data/valetudo/config.json

[rand256]

In most cases when you see such random-looking paths it means you need to clean dust from the side sensor, cause when it's dirty the device can think there are obstacles around it where there are actually none, and tries to avoid them correspondingly.

[10bn]

thx so much, that was an very easy an quick fix. :)