ERR getState | {"code":"timeout"}
**I checked the log, the first error message came on June 2nd.**

> [37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | Connected to: 192.168.178.39
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | Model: roborock.vacuum.t4
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | State: charging
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | FanSpeed: 102
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | BatteryLevel: 100
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mINF getSerialNumber | roborock.vacuum.t4 | Serial Number is R0701S92404457
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | Serialnumber: R0701S92404457
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mINF getFirmware | roborock.vacuum.t4 | Firmwareversion is 3.5.8_0358
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mSTA getDevice | Firmwareversion: 3.5.8_0358
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mINF changedCleaning | roborock.vacuum.t4 | Cleaning is OFF.
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mMON changedCharging | roborock.vacuum.t4 | ChargingState is now true
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mINF changedCharging | roborock.vacuum.t4 | Charging is active
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mMON changedSpeed | roborock.vacuum.t4 | FanSpeed is now 102%
[37m[6/2/2020, 9:52:30 PM] [39m[36m[Roborock T4] [39mINF changedSpeed | roborock.vacuum.t4 | Speed was changed to 102% (Balanced), for HomeKit 50%
[37m[6/2/2020, 9:54:42 PM] [39m[36m[Roborock T4] [39m[31mERR getState | {"code":"timeout"}[39m

On May 22, [37m[5/22/2020, 1:55:21 AM] [39mLoaded plugin: homebridge-xiaomi-roborock-vacuum@0.8.4
No error message, everything works perfectly.

> [37m[6/2/2020, 9:48:53 PM] [39m[33mError loading accessory requested in your config.json at position 2[39m
[37m[6/2/2020, 9:48:53 PM] [39m[31mError: The requested accessory 'XiaomiRoborockVacuum' was not registered by any plugin.[39m
[31m    at PluginManager.getPluginForAccessory (/usr/local/lib/node_modules/homebridge/src/pluginManager.ts:198:15)[39m
[31m    at /usr/local/lib/node_modules/homebridge/src/server.ts:346:37[39m
[31m    at Array.forEach (<anonymous>)[39m
[31m    at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:329:29)[39m
[31m    at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:155:12)[39m
[31m    at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)[39m
[31m    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)[39m
[31m    at Module._compile (internal/modules/cjs/loader.js:1158:30)[39m
[31m    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)[39m
[31m    at Module.load (internal/modules/cjs/loader.js:1002:32)[39m
[37m[6/2/2020, 9:48:53 PM] [39mGot SIGTERM, shutting down Homebridge...

Then, updated on May 23, 

> [0;37m[5/23/2020, 2:24:18 PM] [0m[0;36m[Config][0m Running Command: sudo -E -n npm install homebridge-xiaomi-roborock-vacuum@latest
> [0;37m[5/23/2020, 2:25:05 PM] [0m[0;36m[Config][0m [0;31mCommand failed. Please review log for details.[0m
> But no error message as the title of this issue.

Next updated on June 2nd, 
> [0;37m[6/2/2020, 9:48:42 PM] [0m[0;36m[Config][0m Running Command: sudo -E -n npm install homebridge-xiaomi-roborock-vacuum@latest
> [37m[6/2/2020, 9:48:42 PM][0m [36m[HB Supervisor][0m Homebridge Process Ended. Code: 143, Signal: null

But after the update, I have the following error message:
> [37m[6/2/2020, 9:48:53 PM] [39m[33mError loading accessory requested in your config.json at position 2[39m

> [37m[6/2/2020, 9:48:53 PM] [39m[31mError: The requested accessory 'XiaomiRoborockVacuum' was not registered by any plugin.[39m
> [31m    at PluginManager.getPluginForAccessory (/usr/local/lib/node_modules/homebridge/src/pluginManager.ts:198:15)[39m
> [31m    at /usr/local/lib/node_modules/homebridge/src/server.ts:346:37[39m
> [31m    at Array.forEach (<anonymous>)[39m
> [31m    at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:329:29)[39m
> [31m    at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:155:12)[39m
> [31m    at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)[39m
> [31m    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)[39m
> [31m    at Module._compile (internal/modules/cjs/loader.js:1158:30)[39m
> [31m    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)[39m
> [31m    at Module.load (internal/modules/cjs/loader.js:1002:32)[39m
> [37m[6/2/2020, 9:48:53 PM] [39mGot SIGTERM, shutting down Homebridge...

Then, the log showed I restarted Homebridge several times, and the same error message showed too until it came back to work. But it showed the error message in the beginning of the issue.

And today, I did not use my Rockrobo T4.
At 9:28 PM today, it started the auto self-check(?) as follows:
> [37m[6/28/2020, 9:39:58 PM] [39m[36m[Roborock T4] [39mINF getCleaning | roborock.vacuum.t4 | Cleaning is false
> [37m[6/28/2020, 9:39:58 PM] [39m[36m[Roborock T4] [39mINF getBatteryLow | roborock.vacuum.t4 | Batterylevel is 100%
> [37m[6/28/2020, 9:39:58 PM] [39m[36m[Roborock T4] [39mINF getSpeed | roborock.vacuum.t4 | Fanspeed is 102 over miIO. Converting to HomeKit
> [37m[6/28/2020, 9:39:58 PM] [39m[36m[Roborock T4] [39mINF getSpeed | roborock.vacuum.t4 | Fanspeed is 102 over miIO "Balanced" > HomeKit speed 50%

then in 15 min, at 9:54 PM, it showed the timeout error message with no reason.
> [37m[6/28/2020, 9:54:44 PM] [39m[36m[Roborock T4] [39m[31mERR getState | {"code":"timeout"}[39m

If you need any further information, please let me know.