und unten anfügen:
Code0 1 * * * root /bin/systemctl restart homebridgeSpeichern und beenden.
jetzt wird jede stunde der Dienst Homebridge neu gestartet
Bedeutet dieser Crontab Code nicht Ausführung jeden Tag um 1 Uhr nachts?
det ?
Beiträge von Piiong
-
-
Keiner eine Idee??? Komme nicht weiter
Alles anzeigenHi 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.
CodeERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyedDie firmware ist die aktuellste (3.5.7_002008).
Ich hoffe, mir kann jemand weiterhelfen.
Vg, Chris
Hier ist der Fehlercode:
Code
Alles anzeigen> [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% -
Ach verstehe. Force reboot des iPhones, meinst du! Den habe ich noch nicht gemacht. Wäre tatsächlich ne gute Idee! Aber der Fehler besteht auf dem iPad exakt genauso, wie auf dem iPhone. Bei reddit beschrieb jemand den gleichen Fehler:
https://www.reddit.com/r/HomeK…ezing_when_editing_scene/
Denke deshalb, dass es nicht mehr ein Gerät ist, was sich verschluckt hat.
Wenn ich den force reboot mache... was wird genau gelöscht? Auch Einstellungen bei Homekit oder so?
-
Alles anzeigen
Home App auf 8 Geräten?
Versuch wert.
Home App löschen. Force restart (der Klammergriff hängt von der jeweiligen iPhone Version ab). Home App neu installieren.
Könnte funktionieren.
Nicht die home App auf 8 Geräten, sondern ich habe 8 Geräte, die auf Homekit via Cloud zugreifen, von der iCloud und dem Keychain abgemeldet. wie: HomePods, Apple TV, .Mac , iPad, iPhones.... in der Summe ca. 8. Die home app selber nutze ich auf 2 Geräten hauptsächlich. Und meine Freundin noch auf ihrem iPhone ...
Ist schon alles geschehen und hat nichts gebracht.
Gelöscht wurden: alle!!! Geräte, dann das „zuhause“ selber, dann natürlich auch die ganze App, und dann wie beschrieben habe ich alle Geräte abgemeldet, um Datenreste aus der Cloud bezüglich Homekit zu löschen.
Also komplett alles platt gemacht.
Danach wieder alles neu aufgelegt. -> Fehler besteht sogar beim neu aufgesetzten Homekit
hat jemand Thermostate (zb Eve thermo) und kann mal versuchen eine Szene damit zu erstellen und dann nochmal öffnen und in den Settings die Temperatur ändern. Ob der Fehler generell öfter vorkommt?
-
Hi. hat jemand ein ähnliches problem, dass sich die Homekit App aufhängt/einfriert, wenn man Thermostate in Szenen bearbeiten will? Normales verstellen der Soll-Temperatur ist ok, allerdings in Szenen friert die App ein, nachdem man das X drückt. (Siehe Bild) .... ich habe schon das ganze Homekit platt gemacht deswegen (incl. Abmelden von 8 Geräten aus der iCloud)... hat nichts gebracht. Deshalb sieht man da auch nur ein Thermostat auf dem Bild. Ist das erste Gerät was ich in ein frisches Homekit eingebunden habe. Super nervig!!!!! Bug?
-
Alles anzeigen
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
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
-
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.
CodeERR connect | miio.device, next try in 2 minutes | Error: Network communication is unavailable, device might be destroyedDie firmware ist die aktuellste (3.5.7_002008).
Ich hoffe, mir kann jemand weiterhelfen.
Vg, Chris
Hier ist der Fehlercode:
Code
Alles anzeigen> [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% -
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?
-
Alles anzeigen
So hab es dann doch mal schnell in der Mittagspause herausbekommen.
In der Textbox wo die URL drin steht, entfernst du ",daily " aus der URL
Damit bekommen wir schonmal die benötigten Daten.
Jetzt fügen wir "Variable abrufen" hier hinzu (Bild grüner pfeil) und wählen die
Variable "JSON"
Und noch ein paar andere Sachen.Sollte dann so aussehen
Nun steht uns die Variable TempMax zur weiteren verfügung bereit.
Sprich du kannst sie im weiter unten folgenden Textfeld hinzufügen.
Ja megaaaaaaa!
Hat alles geklappt, wie es soll! Danke für deine Hilfe!!!!
Schade, dass es so kompliziert ist... und das bei Apple. Ich denke mal in nächster Zeit kommt da ein einfaches preset. Und hoffentlich auch für die automatische Ansteuerung in Kurzbefehle für die AirPlay2 Ausgabe für die Sonos, HomePod und zipps....
Meines Wissens geht das auch noch nicht, richtig?
-
Genau. Hatte das mit der Eingabe „maxtemperatur“ auch versucht und es gab keine sprachliche Ausgabe.
Danke aber für s nachforschen. Es eilt ja auch nicht. ??
-
welchen Shortcut benutzt du denn? diesen hier oder den Shortcut mit Wetterinfos von Darksky?
Den von darksky. Funktioniert soweit einwandfrei. ?
Habe versucht maxtemperature einzufügen. Aber meine Kenntnisse sind dann doch zu limitiert;)
-
Hi FettesB!!
Klasse Shortcut mit dem Wetter! Danke. Versuche es etwas zu modifizieren. Leider klappt es nicht
Ich würde gerne statt der gefühlten die Maximale Temperature ausgeben lassen.
Hast du eine Idee?
Grüße
