Homebridge-xiaomi-roborock-vacuum: Wrong battery status and stopping problem

[Tim2309]

Since the update 0.6.8 i noticed the massage battery low and the problem #105 is still not solved.

[yesman82]

Same here with Roborock s5 - activateCharging is called but the device just stops cleaning.
Log says

[2/10/2020, 9:04:30 PM] [Eve] DEB ensureDevice | roborock.vacuum.s5 | The socket is still on. Reusing it.
[2/10/2020, 9:04:30 PM] [Eve] ACT setCleaning | roborock.vacuum.s5 | Stop cleaning and go to charge.
  thing:miio:96663193 -> (5) {"method":"app_stop","params":[],"id":15} +3s
  miio:packet -> <Buffer 21 31 00 50 00 00 00 00 05 c2 f6 99 5e 41 b7 4e fa 9c 75 c6 97 ff c2 45 b7 0a eb da 99 bc 09 f2> +3s
  miio:packet <- <Buffer 21 31 00 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4e 12 c7 19 ff 5b 66 c7 88 5b 02 28 4c c2 61 38 ec> +143ms
  miio:packet <- <Buffer 21 31 00 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4e 12 c7 19 ff 5b 66 c7 88 5b 02 28 4c c2 61 38 ec> +1ms
  thing:miio:96663193 <- Message: `{"result":["ok"],"id":15}` +146ms
  thing:miio:96663193 -> (5) {"method":"app_charge","params":[],"id":16} +0ms
  miio:packet -> <Buffer 21 31 00 50 00 00 00 00 05 c2 f6 99 5e 41 b7 4e 11 b4 f6 e3 0a 6c df e8 de 11 f1 42 f3 36 1a 86> +2ms
  miio:packet <- <Buffer 21 31 00 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4e 94 9b a5 72 9c f4 50 ce e6 99 20 c8 06 a9 83 a0> +117ms
  miio:packet <- <Buffer 21 31 00 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4e 94 9b a5 72 9c f4 50 ce e6 99 20 c8 06 a9 83 a0> +1ms
  thing:miio:96663193 <- Message: `{"result":["ok"],"id":16}` +120ms
  thing:miio:96663193 -> (5) {"method":"get_status","params":[],"id":17} +1s
  miio:packet -> <Buffer 21 31 00 50 00 00 00 00 05 c2 f6 99 5e 41 b7 4f 0a c7 4c af fb d2 d5 35 f4 10 fa 05 d7 61 44 60> +1s
  thing:miio:96663193 -> (5) {"method":"get_consumable","params":[],"id":18} +1ms
  miio:packet -> <Buffer 21 31 00 50 00 00 00 00 05 c2 f6 99 5e 41 b7 4f da a0 e8 cc 28 ef cc 80 95 9a 10 2f e6 46 14 21> +1ms
  miio:packet <- <Buffer 21 31 01 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4f 2b 94 95 5b ac 55 2d 1f e2 89 7a 48 3e 42 fc c4> +6ms
  miio:packet <- <Buffer 21 31 01 40 00 00 00 00 05 c2 f6 99 5e 41 b7 4f 2b 94 95 5b ac 55 2d 1f e2 89 7a 48 3e 42 fc c4> +1ms
  thing:miio:96663193 <- Message: `{"result":[{"msg_ver":3,"msg_seq":140,"state":3,"battery":98,"clean_time":15,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"lock_status":0}],"id":17}` +9ms
  miio:packet <- <Buffer 21 31 00 d0 00 00 00 00 05 c2 f6 99 5e 41 b7 4f d7 f5 8c d2 5b e6 60 64 1a c2 ea 26 c2 20 a7 d4> +1ms
  miio:packet <- <Buffer 21 31 00 d0 00 00 00 00 05 c2 f6 99 5e 41 b7 4f d7 f5 8c d2 5b e6 60 64 1a c2 ea 26 c2 20 a7 d4> +1ms
  thing:miio:96663193 <- Message: `{"result":[{"main_brush_work_time":502577,"side_brush_work_time":502577,"filter_work_time":502577,"filter_element_work_time":0,"sensor_dirty_time":43910}],"id":18}` +2ms
  thing:miio:96663193 Property state changed from cleaning to waiting +5s
  EventedHTTPServer [::ffff:192.168.178.22] Sending HTTP event '2.28' with data: {"characteristics":[{"aid":2,"iid":28,"value":false}]} +1s
  EventedHTTPServer [::ffff:192.168.178.77] Muting event '2.28' notification for this connection since it originated here. +5ms
  EventedHTTPServer [::ffff:192.168.178.86] Sending HTTP event '2.28' with data: {"characteristics":[{"aid":2,"iid":28,"value":false}]} +0ms
  EventedHTTPServer [::ffff:192.168.178.77] HTTP Response is finished +2ms
[2/10/2020, 9:04:32 PM] [Eve] MON changedCleaning | roborock.vacuum.s5 | CleaningState is now false
[2/10/2020, 9:04:32 PM] [Eve] INF changedCleaning | roborock.vacuum.s5 | Cleaning is OFF.

Pause and Dock is set to false

[terriblefox]

I also still have the stop problem. Solved it with a automation when the robot stops to stop the robot again , then it docks.

[afharo]

Oh! That's good to know... Maybe it's simply a timing thing. Let's add a delay before calling the "app_charge" command.

[terriblefox]

Oh! That's good to know... Maybe it's simply a timing thing. Let's add a delay before calling the "app_charge" command.

worth a try

[afharo]

Definitely! I'll try to do the change sometime this weekend.

Regarding the battery low. Can you further explain what the issue is about?

[Tim2309]

Since the last Firmwareupdate of the S6 the batterybug seem to be solved