homebridge-xiaomi-roborock-vacuum

Nein geht wirklich nicht habe es gerade noch einmal versucht.bei Lampen kann ich es komischerweise ändern da erscheint ein Rahmen um die Lampe beim Ventilator oder Sensor nicht.
Kann es Update bedingt sein?

Gesendet von iPad mit Community

Zitat von vgnsxe

Du hast noch

Die neuen zusaetzlichen Icons fuer die Geraete gibt es erst seit iOS 13.1

Okay ja stimmt habe gerade auf iPad Update gemacht auf iOS 13.1 und jetzt geht es ?
Kann man sich die Kacheln innerhalb eines Gerätes verschieben bzw. eben anders anordnen?

Gesendet von iPad mit Community

Das würde mich auch interessieren, ob man die einzelnen Geräte innerhalb einer Kachel ändern kann ?????

Gesendet von iPhone mit Community

Hallo Zusammen,

irgendwie bekomme ich es nicht hin und brauche Hilfe.

Habe alles nach Anleitung installiert, aber bekomme schon beim Start scho einen Fehler. Hat jemand eine Idee woran es liegen kann?

Wäre sehr über Hilfe erfreut.

Danke Oberst

[2019-10-18 21:44:14] [RademacherHomePilot] Warning. No password has been configured. Consider protecting access to your HomePilot.

[2019-10-18 21:44:14] [Nuki] Send request to Nuki bridge 'http://192.168.001.222:8080' on '/callback/list' with '{"token":"FI6xkq"}'.

[2019-10-18 21:44:15] [RademacherHomePilot] Unknown product: 99999998

[2019-10-18 21:44:15] [RademacherHomePilot] { description: 'Ronny Iphone',

deviceGroup: 3,

did: 1010003,

automations: [ 130 ],

readings: { area_entered: true },

timestamp: 1571320752,

iconSetInverted: 0,

iconSet: { k: 'iconset38' },

name: 'RonnyiPhone(iPhone112)',

statusValid: true,

deviceNumber: '99999998',

uid: '9D873FCC-188A-45C8-B71E-1E2EB1E6DA5B',

visible: true }

[2019-10-18 21:44:15] [RademacherHomePilot] blinds are online: Rollo Kinderzimmer(Alexa) [1010004]

[2019-10-18 21:44:15] [RademacherHomePilot] blinds are online: Rollo Tür (Alexa) [1010002]

[2019-10-18 21:44:15] [RademacherHomePilot] blinds are online: Rollo Fenster (Alexa) [1010001]

[2019-10-18 21:44:15] [RademacherHomePilot] blinds are online: Rollo unten (Alexa) [1010000]

[2019-10-18 21:44:15] [Nuki] Request to Nuki bridge 'http://192.168.001.222:8080' finished with status code '200' and body '{"callbacks": [{"id": 1, "url": "http://192.168.001.223:51827/"}]}'. null

[2019-10-18 21:44:15] [Nuki] Webhook for plugin already exists.

[2019-10-18 21:44:16] [Blasi] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

(node:29578) UnhandledPromiseRejectionWarning: Error: Could not connect to device, handshake timeout

at Timeout.handshakeTimeout.setTimeout [as _onTimeout] (/usr/local/lib/node_modules/homebridge-xiaomi-roborock-vacuum/node_modules/miio/lib/network.js:432:17)

at ontimeout (timers.js:427:11)

at tryOnTimeout (timers.js:289:5)

at listOnTimeout (timers.js:252:5)

at Timer.processTimers (timers.js:212:10)

(node:29578) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

(node:29578) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[2019-10-18 21:44:16] [Fritz] Fritz!Box platform login successful

[2019-10-18 21:44:16] [Fritz] Discovering accessories

[2019-10-18 21:44:17] [Fritz] Using tr64 api for guest Wifi

[2019-10-18 21:44:21] [Fritz] Alarm sensors found: none

[2019-10-18 21:44:22] [Fritz] Outlets found: 116570099522

[2019-10-18 21:44:23] [Fritz] Thermostats found: 109710536784,109710507504,109710507880,119610820280,119610823832

[2019-10-18 21:44:23] [Fritz] Sensors found: none

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Guest WLAN'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Dose Balkon'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Wohnzimmer Tür'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Wohnzimmer Fenster'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Heizung Kinderzimmer'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Heizung Schlafzimmer'...

[2019-10-18 21:44:23] [Fritz] Initializing platform accessory 'Heizung Bad'...

Setup Payload:

X-HM://0023ISYVR489D

Scan this code with your HomeKit app on your iOS device to pair with Homebridge:

Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:

??????????????

? 031-45-111 ?

??????????????

[2019-10-18 21:44:23] Homebridge is running on port 51826.

Und im Betrieb bekomme ich auch Fehler und somit auch keine Verbindung in Homekit:

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - Current target position: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - getting current position

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - getting obstruction detected

[2019-10-18 21:52:05] [Blasi] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:05] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:05] [Blasi] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:05] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:05] [Blasi] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:05] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:05] [Blasi] ERR getDocked | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:05] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:05] [Fritz] Getting outlet 116570099522 state

[2019-10-18 21:52:05] [Fritz] Getting guest WLAN state

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - Current target position: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - getting obstruction detected

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - getting current position

[2019-10-18 21:52:05] [Fritz] Getting thermostat 119610823832 battery status

[2019-10-18 21:52:05] [YSP-1600] HTTP GetStatus result:Off

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Kinderzimmer(Alexa) [1010004] - obstruction detected: 0 errors

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - obstruction detected: 0 errors

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - current position: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - current target: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Fenster (Alexa) [1010001] - current position: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Kinderzimmer(Alexa) [1010004] - current position: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Fenster (Alexa) [1010001] - current target: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - obstruction detected: 0 errors

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Fenster (Alexa) [1010001] - obstruction detected: 0 errors

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Tür (Alexa) [1010002] - current target: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo Kinderzimmer(Alexa) [1010004] - current target: 100

[2019-10-18 21:52:05] [RademacherHomePilot] Rollo unten (Alexa) [1010000] - current position: 100

[2019-10-18 21:52:07] [Blasi] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-10-18 21:52:09] [Blasi] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:09] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:09] [Blasi] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:09] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:09] [Blasi] ERR getDocked | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:09] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:09] [Blasi] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:09] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:11] [Blasi] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-10-18 21:52:11] [Blasi] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:11] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:11] [Blasi] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:11] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:11] [Blasi] ERR getDocked | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:11] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:11] [Blasi] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-10-18 21:52:11] [Blasi] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-10-18 21:52:13] [Blasi] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

Ich kopiere hier mal meinen Beitrag aus einem anderen Thread:

Versuch es mit der Installation doch mal so:

1. Abhängigkeit installieren

sudo npm install -g miio

2. Plugin global als Nutzer "root" installieren

sudo su -
npm install -g homebridge-xiaomi-roborock-vacuum@latest --unsafe-perm

3. Homebridge neustarten

sudo systemctl restart homebridge

spielt die Reihenfolge eine Rolle? habe alles so gemacht, nur das ich miio nach dem Plugin installiert habe.

Das sollte eigentlich nicht tragisch sein, zur Sicherheit kannst du ja alle vier Befehle von oben noch einmal nach einander eingeben (doppelt installiert wird im Zweifel nichts, keine Sorge)..

wie schaut denn dein Eintrag in der config.json aus?

Seit ein paar Tagen zeigt der Robo immer keine Antwort.

Wenn ich die Kachel dann öffne und kurz warte dann kommt er wieder als erreichbar,nach ein paar Minuten dann wieder keine Antwort.

Jemand eine Idee an was das liegen könnte?

kann es sein das sich der Token geändert hat?

In meinem Log sieht es auch ein bisschen komisch aus 😏

Weiß jemand was das bedeutet?

sieht ganz so aus, da wirst du den Token nochmal extrahieren müssen

Zitat von det

sieht ganz so aus, da wirst du den Token nochmal extrahieren müssen

sieht der Logo so aus als würde es Token liegen oder könnte es auch etwas anderes sein?

also am Token liegt es auch nicht kommt der selbe raus jemand eine Idee?

hier nochmal der Log

[2019-11-2 1:55:54 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:02 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:04 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:04 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getBattery | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:04 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:04 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getCharging | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:04 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:06 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:14 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:14 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:14 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:14 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:16 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:20 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getSpeed | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:20 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:20 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getCleaning | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:20 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getBattery | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getCharging | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:22 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:24 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:24 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getDocked | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:24 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:24 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getPauseState | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:24 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:26 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

[2019-11-2 1:56:42 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR getBatteryLow | No vacuum cleaner is discovered yet.

[2019-11-2 1:56:42 PM] [Xiaomi Mi Robot Vaccum 2st Generation] INF ensureDevice | undefined | The socket was destroyed or not initialised, initialising the device

[2019-11-2 1:56:44 PM] [Xiaomi Mi Robot Vaccum 2st Generation] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout

(node:13832) UnhandledPromiseRejectionWarning: Error: Could not connect to device, handshake timeout

at Timeout.handshakeTimeout.setTimeout [as _onTimeout] (/usr/local/lib/node_modules/homebridge-xiaomi-roborock-vacuum/node_modules/miio/lib/network.js:432:17)

at ontimeout (timers.js:436:11)

at tryOnTimeout (timers.js:300:5)

at listOnTimeout (timers.js:263:5)

at Timer.processTimers (timers.js:223:10)

(node:13832) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)

Zitat von vgnsxe

Hast du nochmal das Wifi aktualisiert in den Einstellungen vom Roborock? Bzw nochmal neu mit dem Netzwerk verbunden?

nein hab ich nicht.

was genau müsste ich dazu machen?

habe das wlan zurück gesetzt und nun sieht es so aus als ob es wieder läuft

Hey Zusammen☺️
ich nutze VoiceOver zusammen mit der Home Bridge App und habe einen Roborock s50

Und möchte den halt gerne in der Home Bridge einbinden

Wenn ich in der App unter Tools, Config manuell bearbeite

Wo ist denn da mein Fehler dass das Ganze anfängt zu streiken?

{

"bridge" : {

"username" : "CD:22:3D:E3:CE:12",

"name" : "Homebridge",

"pin" : "031-45",

"port" : 51826

},

"accessories" : [

{

"shutdownGraceTime" : "45",

"accessory" : "NetworkDevice",

"pingInterval" : "15",

"mac" : "EX:AM:PL:E:PC",

"wakeGraceTime" : "20",

"ip" : "192.168.178.1",

"name" : "Example PC"

},

{

"name" : "Pi Temp",

"accessory" : "RaspberryPiTemperature"

},

{

"dock" : true,

"pause" : false,

"accessory" : "XiaomiRoborockVacuum",

"name" : "Xiaomi Mi Robot Vaccum 1st Generation",

"ip" : "192.168.1.150",

"token" : "abcdef1234567890abcdef1234567890"

}

]

}

Hallo und willkommen hier im Forum,

... was mir auffällt ist die "pin" bei der Homebridge, sollte so aussehen: 031-45-001

... wenn der "token" vom Roborock nur ein Platzhalter ist und der "echte" definitiv stimmt, schaut eigentlich alles gut aus

Loky Gehen wir mal systematisch vor:

1. Hast du das passende Homebridge Plugin installiert?
2. Wenn ja, wie genau bist du dabei vorgegangen?

3. Welche Meldung erscheint im Log (bitte Codeblock „</>“ nutzen), wenn du den Befehl

sudo systemctl restart homebridge; sudo journalctl -fau homebridge

eingibst?