homebridge-xiaomi-roborock-vacuum

Hi Leute,

ich habe heute in dem Homebridge User Interface etwas im Xiaomi Saugroboter Plugin "herumgespielt". Ich weiß nicht ob das der Auslöser war - jedenfalls funktioniert jetzt meine Homebridge nicht mehr. Ich habe hier im Forum durch die Suchfunktion ein paar Dinge ausprobiert - dort lag das Problem aber wahrscheinlich doch anders. Meine Config.json habe ich geprüft und es wurden mir keine Fehler angezeigt...

Anbei mal das komplette Log:

sudo systemctl restart homebridge; sudo journalctl -fau homebridge
-- Logs begin at Thu 2016-11-03 18:16:42 CET. --
Oct 10 18:46:12 raspberrypi homebridge[711]:     at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:156:12)
Oct 10 18:46:12 raspberrypi homebridge[711]:     at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)
Oct 10 18:46:12 raspberrypi homebridge[711]:     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
Oct 10 18:46:12 raspberrypi homebridge[711]:     at Module._compile (internal/modules/cjs/loader.js:1063:30)
Oct 10 18:46:12 raspberrypi homebridge[711]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
Oct 10 18:46:12 raspberrypi homebridge[711]:     at Module.load (internal/modules/cjs/loader.js:928:32)
Oct 10 18:46:12 raspberrypi sudo[696]: pam_unix(sudo:session): session closed for user root
Oct 10 18:46:12 raspberrypi homebridge[711]: [10/10/2020, 18:46:12] Got SIGTERM, shutting down Homebridge...
Oct 10 18:46:12 raspberrypi homebridge[711]: [10/10/2020, 18:46:12] [HomeMatic CCU] [RPC] Removing Event Server for Interface BidCos-RF.
Oct 10 18:50:01 raspberrypi systemd[1]: Started Node.js HomeKit Server.
Oct 10 18:50:04 raspberrypi homebridge[830]: [10/10/2020, 18:50:04] Loaded config.json with 1 accessories and 3 platforms.
Oct 10 18:50:04 raspberrypi homebridge[830]: [10/10/2020, 18:50:04] ---
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Loaded plugin: [email protected]
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Registering platform 'homebridge-config-ui-x.config'
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] ---
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Loaded plugin: [email protected]
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Registering platform 'homebridge-homematic.HomeMatic'
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] ---
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Loaded plugin: [email protected]
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] Registering platform 'homebridge-tuya-web.TuyaWebPlatform'
Oct 10 18:50:07 raspberrypi homebridge[830]: [10/10/2020, 18:50:07] ---
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] Loaded plugin: [email protected]
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] Registering accessory 'homebridge-xiaomi-roborock-vacuum.XiaomiRoborockVacuum'
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] ---
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] Loading 3 platforms...
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] Initializing HomeMatic platform...
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] [Core] merging configurations
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] Homematic Plugin Version 0.0.219
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] Plugin by thkl  https://github.com/thkl
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] Homematic is a registered trademark of the EQ-3 AG
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] Please report any issues to https://github.com/thkl/homebridge-homematic/issues
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] running in production mode
Oct 10 18:50:08 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] will connect to your ccu at 192.168.178.225
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:08] [HomeMatic CCU] IMPORTANT !! Starting this version, your homematic custom configuration is located in /var/homebridge/homematic_config.json
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] using xmprpc for communication with BidCos-RF
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] init RPC for BidCos-RF.
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] local ip used : 192.168.178.43. you may change that with local_ip parameter in config
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] init RPC for VirtualDevices.
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] local ip used : 192.168.178.43. you may change that with local_ip parameter in config
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [Config] Initializing config platform...
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [Config] Spawning homebridge-config-ui-x with PID 858
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [TuyaWebPlatform] Initializing TuyaWebPlatform platform...
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] Loading 1 accessories...
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [Xiaomi Mi Robot Vaccum 2st Generation] Initializing XiaomiRoborockVacuum accessory...
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] server for interface BidCos-RF. is listening on port 9090.
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] Creating Local HTTP Client for CCU RPC Events
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] server for interface VirtualDevices. is listening on port 9093.
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] Creating Local HTTP Client for CCU RPC Events
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] Error: Both "autoroom" and "rooms" config options can't be used at the same time.
Oct 10 18:50:09 raspberrypi homebridge[830]:       Please, use "autoroom" to retrieve the "rooms" config and remove it when not needed.
Oct 10 18:50:09 raspberrypi homebridge[830]:     at new XiaomiRoborockVacuum (/usr/local/lib/node_modules/homebridge-xiaomi-roborock-vacuum/index.js:128:13)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at /usr/local/lib/node_modules/homebridge/src/server.ts:357:50
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Array.forEach (<anonymous>)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:330:29)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:156:12)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Module._compile (internal/modules/cjs/loader.js:1063:30)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
Oct 10 18:50:09 raspberrypi homebridge[830]:     at Module.load (internal/modules/cjs/loader.js:928:32)
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] Got SIGTERM, shutting down Homebridge...
Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] [HomeMatic CCU] [RPC] Removing Event Server for Interface BidCos-RF.

würde mich echt sehr freuen, wenn ihr mir weiterhelfen könntet

Viele Grüße

Tim

Zitat von Timbolot

Oct 10 18:50:09 raspberrypi homebridge[830]: [10/10/2020, 18:50:09] Error: Both "autoroom" and "rooms" config options can't be used at the same time.
Oct 10 18:50:09 raspberrypi homebridge[830]: Please, use "autoroom" to retrieve the "rooms" config and remove it when not needed.

Da steht doch alles, was du wissen musst.

Moin sschuste,

das war der Wink den ich gebraucht hab. Ich hatte erst versucht das Plugin einfach zu deinstallieren - was nicht so recht funktioniert hatte.

Jetzt hab ich die Config.json angepasst und die "Rooms" gelöscht - siehe da jetzt geht's wieder

Dankeschön!

Hi Leute,

ich habe das MiIO Plugin 0.15.6, sowie das Homebridge Xiaomi Roborock Vacuum installiert und den Mi Mop Pro inkl. Token in der Config eingetragen. Nun bekomme ich nach Start des Pi`s folgende Meldung:

[10/18/2020, 21:42:14] [Xiaomi Mi Robot Mop Pro] ERR getSerialNumber | Failed getting the serial number. Error: Call to device timed out

at Timeout.retry [as _onTimeout] (/usr/local/lib/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/network.js:519:23)

at listOnTimeout (internal/timers.js:549:17)

at processTimers (internal/timers.js:492:7) {

code: 'timeout'

}

kann mir vielleicht jemand weiterhelfen?

Vielen Dank im Voraus

Daniel

Zitat von Lordcord

Hallo zusammen,

ich habe es mit rudimentären Kenntnissen hinbekommen, meinen Roborock S5 in HomeKit zu integrieren. Von meinen vier Räumen werden drei angesteuert, einer leider nicht. Der Roboter sagt dann: Raum nicht erreichbar oder so ähnlich.

Weiß zufällig jemand, woran das liegen kann?

Hi! Ich habe das selbe problem. (Roborock S5) Habe 5 Räume, 4 werden erfolgreich angesteuert, nur der Raum, in dem die Station steht, wird nicht angenommen. (Fehler siehe Screenshot; es wird kein Zimmer farblich gehighlighted).

Habe schon über 10 IDs ausprobiert...

Würde es was bringen, wenn man die Karte löscht und neu scannen lässt? Was passiert dann eigentlich mit den IDs?

Hi noch einmal,

zusätzlich habe ich ein regelmäßigen Fehler des Roborock S5, der alle 1-3 Tage spätestens die Homebridge/Homekit Verbindung zum Roborock killed.

Nach einem Neustart der Homebridge geht die Verbindung wieder.

Ich habe den gleichen Fehler schon unter einem anderen pi-System gehabt (mit hoobs). Nach der kompletten Neuinstallation mit Homebridge kommt der Fehler nun wieder.

ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed 

Die firmware ist die aktuellste (3.5.7_002008).

Ich hoffe, mir kann jemand weiterhelfen.

Vg, Chris

Hier ist der Fehlercode:

> [10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareMainBrush | roborock.vacuum.s5 | Mainbrush worktime is 386437 seconds / 35.78%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareMainBrush | roborock.vacuum.s5 | Mainbrush worktime is 386437 seconds / 35.78%.
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getDocked | roborock.vacuum.s5 | Robot Docked is true (Status is charging)
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO. Converting to HomeKit
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO "Turbo" > HomeKit speed 80%
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getBatteryLow | roborock.vacuum.s5 | Batterylevel is 100%
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:47] [Config] Homebridge restart request received
[10/25/2020, 12:11:48] [Config] No restart command defined, killing process...
[10/25/2020, 12:11:48] [HB Supervisor] Stopping services...
[10/25/2020, 12:11:48] Got SIGTERM, shutting down Homebridge...
[10/25/2020, 12:11:53] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[10/25/2020, 12:12:00] [HB Supervisor] OS: Linux 5.4.51-v7l+ arm
[10/25/2020, 12:12:00] [HB Supervisor] Node.js v12.19.0 /usr/local/bin/node
[10/25/2020, 12:12:00] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[10/25/2020, 12:12:00] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[10/25/2020, 12:12:00] [HB Supervisor] Starting Homebridge with extra flags: -I
[10/25/2020, 12:12:00] [HB Supervisor] Starting Homebridge with custom env: {"DEBUG":"DEBUG=\"miio:*,thing:*\""}
[10/25/2020, 12:12:00] [HB Supervisor] Started Homebridge v1.1.6 with PID: 6036
[10/25/2020, 12:12:00] Loaded config.json with 1 accessories and 1 platforms.
[10/25/2020, 12:12:00] ---
[10/25/2020, 12:12:01] Loaded plugin: [email protected]
[10/25/2020, 12:12:01] Registering platform 'homebridge-config-ui-x.config'
[10/25/2020, 12:12:01] ---
[10/25/2020, 12:12:02] Loaded plugin: [email protected]
[10/25/2020, 12:12:02] Registering accessory 'homebridge-xiaomi-roborock-vacuum.XiaomiRoborockVacuum'
[10/25/2020, 12:12:02] ---
[10/25/2020, 12:12:02] Loading 1 platforms...
[10/25/2020, 12:12:02] [Config] Initializing config platform...
[10/25/2020, 12:12:02] [Config] Running in Service Mode
[10/25/2020, 12:12:02] Loading 1 accessories...
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] Initializing XiaomiRoborockVacuum accessory...
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Schlafzimmer (17)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Badezimmer (18)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room die Küche (19)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Loft (20)
Setup Payload:
X-HM://0024N1UA7JC03
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:                           ┌────────────┐         │ xxxxxx │         └────────────┘                            [10/25/2020, 12:12:02] Homebridge is running on port 51142.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Connected to: 192.168.178.42
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Model: roborock.vacuum.s5
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | State: charging
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | FanSpeed: 103
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | BatteryLevel: 100
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF getSerialNumber | roborock.vacuum.s5 | Serial Number is R0018S82500012
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Serialnumber: R0018S82500012
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF getFirmware | roborock.vacuum.s5 | Firmwareversion is 3.5.7_002008
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Firmwareversion: 3.5.7_002008
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCleaning | roborock.vacuum.s5 | Cleaning is OFF.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] MON changedCharging | roborock.vacuum.s5 | ChargingState is now true
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCharging | roborock.vacuum.s5 | Charging is active
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCharging | roborock.vacuum.s5 | Robot was docked.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] MON changedSpeed | roborock.vacuum.s5 | FanSpeed is now 103%
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedSpeed | roborock.vacuum.s5 | Speed was changed to 103% (Turbo), for HomeKit 80%
HAP Warning: Characteristic 000000AC-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000040-0000-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 000000AB-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000040-0000-1000-8000-0026BB765291. Adding anyway.
[10/25/2020, 12:12:03] [Config] Homebridge Config UI X v4.30.0 is listening on :: port 8581
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO. Converting to HomeKit
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO "Turbo" > HomeKit speed 80%
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCharging | roborock.vacuum.s5 | Charging is true (Status is charging)
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getBattery | roborock.vacuum.s5 | Batterylevel is 100%

Zitat von Piiong

Hi! Ich habe das selbe problem. (Roborock S5) Habe 5 Räume, 4 werden erfolgreich angesteuert, nur der Raum, in dem die Station steht, wird nicht angenommen. (Fehler siehe Screenshot; es wird kein Zimmer farblich gehighlighted).

Habe schon über 10 IDs ausprobiert...

Würde es was bringen, wenn man die Karte löscht und neu scannen lässt? Was passiert dann eigentlich mit den IDs?

HY Piiong

ich habe es auch mehrmals versucht und bin verzweifelt ...

Aber du musst jeden "Raum" in der Roborock App anlegen auch den Raum der sich aufgrund der Anlage der anderen Räume ergibt

Vielleiht hilft es

Zitat von Martin-Dafa

HY Piiong

ich habe es auch mehrmals versucht und bin verzweifelt ...

Aber du musst jeden "Raum" in der Roborock App anlegen auch den Raum der sich aufgrund der Anlage der anderen Räume ergibt

Vielleiht hilft es

Alles anzeigen

Hey Martin,

Danke für den Tipp..

Meinst du in der Roborock App? Ich nutze die mi Home App.

Was meinst du genau mit anlegen? Ich habe einfach die Räume mir der Teilung getrennt.

Meine Lösung ist jetzt die, dass ich eine kleine Ecke im Raum angelegt habe als letzten "Raum", den ich nicht befahren muss. Nun ist mir egal, dass er den Bereich nicht erkennt ... die anderen Räume funktionieren ja

ich hoffe jemand kann noch das etwa größere Problem, was ich in #426 beschrieben habe, lösen...

Vg

Keiner eine Idee??? Komme nicht weiter

Zitat von Piiong

Hi noch einmal,

zusätzlich habe ich ein regelmäßigen Fehler des Roborock S5, der alle 1-3 Tage spätestens die Homebridge/Homekit Verbindung zum Roborock killed.

Nach einem Neustart der Homebridge geht die Verbindung wieder.

Ich habe den gleichen Fehler schon unter einem anderen pi-System gehabt (mit hoobs). Nach der kompletten Neuinstallation mit Homebridge kommt der Fehler nun wieder.

Code

ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed 

Die firmware ist die aktuellste (3.5.7_002008).

Ich hoffe, mir kann jemand weiterhelfen.

Vg, Chris

Hier ist der Fehlercode:

Code

> [10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareMainBrush | roborock.vacuum.s5 | Mainbrush worktime is 386437 seconds / 35.78%.
[10/25/2020, 12:00:33] [Xiaomi Roborock S5] INF getCareMainBrush | roborock.vacuum.s5 | Mainbrush worktime is 386437 seconds / 35.78%.
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:01:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getDocked | roborock.vacuum.s5 | Robot Docked is true (Status is charging)
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO. Converting to HomeKit
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO "Turbo" > HomeKit speed 80%
[10/25/2020, 12:01:11] [Xiaomi Roborock S5] INF getBatteryLow | roborock.vacuum.s5 | Batterylevel is 100%
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:01:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:02:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:02:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:03:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:03:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:04:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:04:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:05:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:05:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:06:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:06:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:07:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:07:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:08:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:08:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:09:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:09:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:10:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:10:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:11:02] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] INF ensureDevice | roborock.vacuum.s5 | The socket was destroyed or not initialised, initialising the device
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] ERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyed
[10/25/2020, 12:11:32] [Xiaomi Roborock S5] ERR getState | {"device":null}
[10/25/2020, 12:11:47] [Config] Homebridge restart request received
[10/25/2020, 12:11:48] [Config] No restart command defined, killing process...
[10/25/2020, 12:11:48] [HB Supervisor] Stopping services...
[10/25/2020, 12:11:48] Got SIGTERM, shutting down Homebridge...
[10/25/2020, 12:11:53] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[10/25/2020, 12:12:00] [HB Supervisor] OS: Linux 5.4.51-v7l+ arm
[10/25/2020, 12:12:00] [HB Supervisor] Node.js v12.19.0 /usr/local/bin/node
[10/25/2020, 12:12:00] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[10/25/2020, 12:12:00] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[10/25/2020, 12:12:00] [HB Supervisor] Starting Homebridge with extra flags: -I
[10/25/2020, 12:12:00] [HB Supervisor] Starting Homebridge with custom env: {"DEBUG":"DEBUG=\"miio:*,thing:*\""}
[10/25/2020, 12:12:00] [HB Supervisor] Started Homebridge v1.1.6 with PID: 6036
[10/25/2020, 12:12:00] Loaded config.json with 1 accessories and 1 platforms.
[10/25/2020, 12:12:00] ---
[10/25/2020, 12:12:01] Loaded plugin: [email protected]
[10/25/2020, 12:12:01] Registering platform 'homebridge-config-ui-x.config'
[10/25/2020, 12:12:01] ---
[10/25/2020, 12:12:02] Loaded plugin: [email protected]
[10/25/2020, 12:12:02] Registering accessory 'homebridge-xiaomi-roborock-vacuum.XiaomiRoborockVacuum'
[10/25/2020, 12:12:02] ---
[10/25/2020, 12:12:02] Loading 1 platforms...
[10/25/2020, 12:12:02] [Config] Initializing config platform...
[10/25/2020, 12:12:02] [Config] Running in Service Mode
[10/25/2020, 12:12:02] Loading 1 accessories...
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] Initializing XiaomiRoborockVacuum accessory...
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Schlafzimmer (17)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Badezimmer (18)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room die Küche (19)
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF createRoom | undefined | Room das Loft (20)
Setup Payload:
X-HM://0024N1UA7JC03
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:                           ┌────────────┐         │ xxxxxx │         └────────────┘                            [10/25/2020, 12:12:02] Homebridge is running on port 51142.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Connected to: 192.168.178.42
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Model: roborock.vacuum.s5
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | State: charging
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | FanSpeed: 103
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | BatteryLevel: 100
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF getSerialNumber | roborock.vacuum.s5 | Serial Number is R0018S82500012
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Serialnumber: R0018S82500012
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF getFirmware | roborock.vacuum.s5 | Firmwareversion is 3.5.7_002008
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] STA getDevice | Firmwareversion: 3.5.7_002008
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCleaning | roborock.vacuum.s5 | Cleaning is OFF.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] MON changedCharging | roborock.vacuum.s5 | ChargingState is now true
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCharging | roborock.vacuum.s5 | Charging is active
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedCharging | roborock.vacuum.s5 | Robot was docked.
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] MON changedSpeed | roborock.vacuum.s5 | FanSpeed is now 103%
[10/25/2020, 12:12:02] [Xiaomi Roborock S5] INF changedSpeed | roborock.vacuum.s5 | Speed was changed to 103% (Turbo), for HomeKit 80%
HAP Warning: Characteristic 000000AC-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000040-0000-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 000000AB-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000040-0000-1000-8000-0026BB765291. Adding anyway.
[10/25/2020, 12:12:03] [Config] Homebridge Config UI X v4.30.0 is listening on :: port 8581
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCleaning | roborock.vacuum.s5 | Cleaning is false
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSensors | roborock.vacuum.s5 | Sensors dirtytime is 28363 seconds / 26.26%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareFilter | roborock.vacuum.s5 | Filter worktime is 386437 seconds / 71.56%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCareSideBrush | roborock.vacuum.s5 | Sidebrush worktime is 386437 seconds / 53.67%.
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO. Converting to HomeKit
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 103 over miIO "Turbo" > HomeKit speed 80%
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getCharging | roborock.vacuum.s5 | Charging is true (Status is charging)
[10/25/2020, 12:16:54] [Xiaomi Roborock S5] INF getBattery | roborock.vacuum.s5 | Batterylevel is 100%

Alles anzeigen

Alles anzeigen

Hallo,

möchte nur kurz ein Feedback geben für Leute mit dem Xiaomi 1. Generation ...

Habe gerade das Plugin installiert, funktioniert einwandfrei.

beste Grüße

Guten Morgen,

ich möchte die Reinigung mit meinem Roborock automatisieren. Habe auch schon länger alles eingerichtet. Der Sauger wird bislang aber noch von der Xiaomi-App losgeschickt.

Ich würde gerne jeden Tag zwei Räume reinigen lassen. Ist das mit der Home-App von Apple zu realisieren?

Die Herausforderung dürfte sein, die beiden Räume nacheinander anzufahren oder muss ich einen Raum um 10 Uhr und den anderen um 15 Uhr reinigen?

Was heißt "Habe auch schon länger alles eingerichtet." ? Den Sauger? Das Plugin in der Hoembridge?

Ansonsten dürfte auf der github Seite zum Plugin alles unter "Room Cleaning" beschrieben sein:

https://github.com/homebridge-…rock-vacuum#room-cleaning

Wenn ich schreibe: es ist alles eingerichtet, dann heißt das natürlich, dass sowohl der Staubsauger als auch das Plugin installiert sind.

Zitat von Lordcord

Wenn ich schreibe: es ist alles eingerichtet, dann heißt das natürlich, dass sowohl der Staubsauger als auch das Plugin installiert sind.

Ich glaube, die letzten Updates des Plugins bieten nun die Möglichkeit, bestimmte Räume saugen zu lassen.

https://github.com/homebridge-…-roborock-vacuum/releases

Funktioniert bei euch alles noch?

Meine eingerichteten Zimmer gehen auf einmal nicht mehr...?!

Zitat von Dane03

Funktioniert bei euch alles noch?

Meine eingerichteten Zimmer gehen auf einmal nicht mehr...?!

Bei mir läuft noch alles, sowohl in der Xiaomi Home als auch in Homekit.

Ich bin jedoch nicht auf der aktuellsten Pluginversion.

Konkretisiere doch bitte, was genau anders ist. In der Xiaomi Home noch alles in Ordnung, betrifft es nur die Schalter in Homekit?

Hast du irgendwas an deinem Setup verändert, getestet, WLAN Einstellungen am Robo verändert oder an der config?

Habe alles auf der neuesten Version, Xiaomi App klappt weiter perfekt, auch an/aus...

Bei den letzten Updates war auch ein rollback dabei... Vlt war da was als Auslöser bei mir....

Hab grad gesehen, dass du ein issue eröffnet hast, dann mal warten, ob dort ne Idee kommt.

OT: Wall-E räum das das Kinderzimmer auf 😜. Gefällt mir 👍

Unsern haben wir Rocky genannt...

Jup - ich hoffe irgendwie erklärbar...

Nachdem wie im Garten das scharfe Gerät auf dem Rasen haben (Eva) muss Wall-E drinnen für Ordnung sorgen 😇

Für die Jungs auch super zu merken, sind fast Familienmitglieder 😬

Habe das selbe Problem wie Dane03. Keine Räume werden gefahren bei meinem S5 aber auch eine komplette Fahrt ist nicht möglich. „Gerät Antwortet nicht“ ist dann nach ein paar Minuten die Antwort seitens HK.

Bei mir gingen auch die meisten Automationen nicht weil das Plugin ständig Errors verursacht und da habe ich jetzt das Plugin komplett gelöscht. Siehe da alles läuft sauber.

Finde einfach den Fehler nicht schon mehrmals neuinstalliert, miio Update gefahren - keine Veränderung. Bin am verzweifeln (schon seit Anbeginn) mit diesem Plugin.