Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Neuer Adapter für Roborock-Staubsauger

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.6k

Neuer Adapter für Roborock-Staubsauger

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
923 Beiträge 136 Kommentatoren 325.5k Aufrufe 125 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • copystringC copystring

    @tritanium genau so ist es.

    T Offline
    T Offline
    tritanium
    schrieb am zuletzt editiert von tritanium
    #350

    @copystring

    Warum auch immer habe ich in letzter Zeit:

    63af6974-e2ce-4c66-b7d6-ed5bba4a8dea-grafik.png

    JS: 5.0.17
    node: 18.17.0

    roboAdapter: "dev" branch, von letzter oder vorletzter Woche ?!

    71bbbe2f-9d01-45e1-b7a3-9e42ee553837-grafik.png

    Starte ich den Adapter neu, geht erst einmal wieder für ne Weile und dann kommt iobroker wieder mit der Screenshot Meldung....

    Dummerweise ist im Logging nicht viel ungewöhnliches.... Ideen, wie wir verfahren wollen ?

    Hier mal Debugs:

    roborock.0
    	2023-12-28 18:19:34.470	info	terminating
    roborock.0
    	2023-12-28 18:19:34.241	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.240	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.237	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.236	error	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().
    roborock.0
    	2023-12-28 18:19:34.221	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.220	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.218	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.217	error	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().
    roborock.0
    	2023-12-28 18:19:34.189	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.188	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.188	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.187	error	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().
    roborock.0
    	2023-12-28 18:19:34.135	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.135	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.134	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.133	error	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().
    roborock.0
    	2023-12-28 18:19:34.112	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.112	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.111	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.110	error	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().
    roborock.0
    	2023-12-28 18:19:34.101	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.101	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.100	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.100	error	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().
    roborock.0
    	2023-12-28 18:19:34.045	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.044	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.043	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.042	error	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().
    roborock.0
    	2023-12-28 18:19:34.038	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.037	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:34.035	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:34.035	error	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().
    roborock.0
    	2023-12-28 18:19:33.968	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
    roborock.0
    	2023-12-28 18:19:33.967	info	terminating
    roborock.0
    	2023-12-28 18:19:33.772	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:33.772	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:33.771	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:33.770	error	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().
    roborock.0
    	2023-12-28 18:19:33.748	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:33.747	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:19:33.741	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:33.740	error	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().
    roborock.0
    	2023-12-28 18:19:33.583	error	Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:19:29.269	info	State value to set for "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.programs.1047124.items.0.finishDpIds" has to be type "string" but received type "object"
    roborock.0
    	2023-12-28 18:19:29.267	info	State value to set for "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.programs.1047124.items.0.id" has to be type "string" but received type "number"
    roborock.0
    	2023-12-28 18:19:28.916	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.programs.1753875.items.0.finishDpIds" has to be type "string" but received type "object"
    roborock.0
    	2023-12-28 18:19:28.913	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.programs.1753875.items.0.id" has to be type "string" but received type "number"
    roborock.0
    	2023-12-28 18:19:27.606	info	MQTT initialized
    roborock.0
    	2023-12-28 18:19:26.073	info	starting. Version 0.4.4 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
    roborock.0
    	2023-12-28 18:18:52.878	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.877	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.877	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.877	error	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().
    roborock.0
    	2023-12-28 18:18:52.876	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.875	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.875	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.875	error	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().
    roborock.0
    	2023-12-28 18:18:52.874	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.873	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.873	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.873	error	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().
    roborock.0
    	2023-12-28 18:18:52.871	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.871	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.870	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.869	error	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().
    roborock.0
    	2023-12-28 18:18:52.863	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.863	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.862	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.861	error	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().
    roborock.0
    	2023-12-28 18:18:52.859	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.858	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.858	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.858	error	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().
    roborock.0
    	2023-12-28 18:18:52.851	error	Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.850	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
    roborock.0
    	2023-12-28 18:18:52.844	error	unhandled promise rejection: Connection is closed.
    roborock.0
    	2023-12-28 18:18:52.843	error	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().
    roborock.0
    	2023-12-28 18:18:52.789	info	terminating
    roborock.0
    	2023-12-28 18:18:52.637	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.636	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:18:52.635	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.635	error	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().
    roborock.0
    	2023-12-28 18:18:52.570	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.570	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:18:52.570	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.566	error	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().
    roborock.0
    	2023-12-28 18:18:52.560	error	Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.559	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
    roborock.0
    	2023-12-28 18:18:52.558	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
    roborock.0
    	2023-12-28 18:18:52.557	error	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().
    roborock.0
    	2023-12-28 18:18:52.540	error	Cannot read properties of null (reading 'devices')
    

    lg Micha

    L 1 Antwort Letzte Antwort
    0
    • T tritanium

      @copystring

      Warum auch immer habe ich in letzter Zeit:

      63af6974-e2ce-4c66-b7d6-ed5bba4a8dea-grafik.png

      JS: 5.0.17
      node: 18.17.0

      roboAdapter: "dev" branch, von letzter oder vorletzter Woche ?!

      71bbbe2f-9d01-45e1-b7a3-9e42ee553837-grafik.png

      Starte ich den Adapter neu, geht erst einmal wieder für ne Weile und dann kommt iobroker wieder mit der Screenshot Meldung....

      Dummerweise ist im Logging nicht viel ungewöhnliches.... Ideen, wie wir verfahren wollen ?

      Hier mal Debugs:

      roborock.0
      	2023-12-28 18:19:34.470	info	terminating
      roborock.0
      	2023-12-28 18:19:34.241	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.240	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.237	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.236	error	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().
      roborock.0
      	2023-12-28 18:19:34.221	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.220	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.218	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.217	error	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().
      roborock.0
      	2023-12-28 18:19:34.189	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.188	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.188	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.187	error	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().
      roborock.0
      	2023-12-28 18:19:34.135	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.135	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.134	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.133	error	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().
      roborock.0
      	2023-12-28 18:19:34.112	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.112	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.111	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.110	error	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().
      roborock.0
      	2023-12-28 18:19:34.101	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.101	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.100	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.100	error	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().
      roborock.0
      	2023-12-28 18:19:34.045	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.044	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.043	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.042	error	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().
      roborock.0
      	2023-12-28 18:19:34.038	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.037	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:34.035	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:34.035	error	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().
      roborock.0
      	2023-12-28 18:19:33.968	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      roborock.0
      	2023-12-28 18:19:33.967	info	terminating
      roborock.0
      	2023-12-28 18:19:33.772	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:33.772	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:33.771	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:33.770	error	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().
      roborock.0
      	2023-12-28 18:19:33.748	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:33.747	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:19:33.741	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:33.740	error	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().
      roborock.0
      	2023-12-28 18:19:33.583	error	Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:19:29.269	info	State value to set for "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.programs.1047124.items.0.finishDpIds" has to be type "string" but received type "object"
      roborock.0
      	2023-12-28 18:19:29.267	info	State value to set for "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.programs.1047124.items.0.id" has to be type "string" but received type "number"
      roborock.0
      	2023-12-28 18:19:28.916	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.programs.1753875.items.0.finishDpIds" has to be type "string" but received type "object"
      roborock.0
      	2023-12-28 18:19:28.913	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.programs.1753875.items.0.id" has to be type "string" but received type "number"
      roborock.0
      	2023-12-28 18:19:27.606	info	MQTT initialized
      roborock.0
      	2023-12-28 18:19:26.073	info	starting. Version 0.4.4 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
      roborock.0
      	2023-12-28 18:18:52.878	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.877	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.877	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.877	error	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().
      roborock.0
      	2023-12-28 18:18:52.876	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.875	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.875	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.875	error	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().
      roborock.0
      	2023-12-28 18:18:52.874	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.873	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.873	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.873	error	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().
      roborock.0
      	2023-12-28 18:18:52.871	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.871	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.870	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.869	error	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().
      roborock.0
      	2023-12-28 18:18:52.863	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.863	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.862	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.861	error	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().
      roborock.0
      	2023-12-28 18:18:52.859	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.858	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.858	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.858	error	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().
      roborock.0
      	2023-12-28 18:18:52.851	error	Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.850	error	Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      roborock.0
      	2023-12-28 18:18:52.844	error	unhandled promise rejection: Connection is closed.
      roborock.0
      	2023-12-28 18:18:52.843	error	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().
      roborock.0
      	2023-12-28 18:18:52.789	info	terminating
      roborock.0
      	2023-12-28 18:18:52.637	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.636	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:18:52.635	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.635	error	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().
      roborock.0
      	2023-12-28 18:18:52.570	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.570	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:18:52.570	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.566	error	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().
      roborock.0
      	2023-12-28 18:18:52.560	error	Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.559	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:531:32) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:953:23)
      roborock.0
      	2023-12-28 18:18:52.558	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
      roborock.0
      	2023-12-28 18:18:52.557	error	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().
      roborock.0
      	2023-12-28 18:18:52.540	error	Cannot read properties of null (reading 'devices')
      

      lg Micha

      L Offline
      L Offline
      localhorst
      schrieb am zuletzt editiert von
      #351

      @tritanium said in Neuer Adapter für Roborock-Staubsauger:

      roboAdapter: "dev" branch, von letzter oder vorletzter Woche ?!

      Moin Micha,

      copystring hat in den letzten Tagen eine ziemlich große Änderung eingepflegt: direkte Verbindung zum Robbie via TCP.
      Wenn deine Dev noch von letzter oder vorletzter Woche ist, würde ich die mal im ersten Schritt aktualisieren. Die läuft bis Dato ziemlich cremig.

      Gruß!

      T 1 Antwort Letzte Antwort
      0
      • David G.D Online
        David G.D Online
        David G.
        schrieb am zuletzt editiert von
        #352

        Hab mir die aktuelle Dev auch mal zum Testen gezogen.

        Mein log ist voll mit

        Failed to execute load_multi_map on robot xxxxxxxx Error: Local request with id 633 with method load_multi_map timed out after 10 seconds for response.102
        

        Die erste ID (im Beispiel 633) ist immer unterschiedlich.

        Zeigt eure Lovelace-Visualisierung klick
        (Auch ideal um sich Anregungen zu holen)

        Meine Tabellen für eure Visualisierung klick

        1 Antwort Letzte Antwort
        0
        • M Offline
          M Offline
          michael 1975
          schrieb am zuletzt editiert von
          #353

          Hallo zusammen habe seit heute das Problem das der Adapter zwar grün ist aber leider nichts geht wenn ich den Adapter neu starte kommt im Log folgendes.

          Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')

          was könnte ich machen?

          1 Antwort Letzte Antwort
          0
          • L localhorst

            @tritanium said in Neuer Adapter für Roborock-Staubsauger:

            roboAdapter: "dev" branch, von letzter oder vorletzter Woche ?!

            Moin Micha,

            copystring hat in den letzten Tagen eine ziemlich große Änderung eingepflegt: direkte Verbindung zum Robbie via TCP.
            Wenn deine Dev noch von letzter oder vorletzter Woche ist, würde ich die mal im ersten Schritt aktualisieren. Die läuft bis Dato ziemlich cremig.

            Gruß!

            T Offline
            T Offline
            tritanium
            schrieb am zuletzt editiert von
            #354

            @localhorst
            Habe gestern Abend mal die aktuelle "dev" installiert.

            Erst lief der Adapter sauber, aber heute wieder:

            02e49954-037d-442d-b53b-c1d7e5254402-grafik.png

            DEBUG Logs habe ich noch nicht kontrolliert, da ich noch auf der Arbeit bin.... das schaue ich mir nachher an ...

            T 1 Antwort Letzte Antwort
            0
            • T tritanium

              @localhorst
              Habe gestern Abend mal die aktuelle "dev" installiert.

              Erst lief der Adapter sauber, aber heute wieder:

              02e49954-037d-442d-b53b-c1d7e5254402-grafik.png

              DEBUG Logs habe ich noch nicht kontrolliert, da ich noch auf der Arbeit bin.... das schaue ich mir nachher an ...

              T Offline
              T Offline
              tritanium
              schrieb am zuletzt editiert von tritanium
              #355

              @copystring

              Soooo, nachdem unser Q Revo nun das aktuellste Firmware Update gerade bekommen hat (V2.17.78), ersaufe ich in folgenden Meldungen:

              e23e8bb2-8361-497a-bd9e-21ed265cf52e-grafik.png

              Scheinbar hat Roborock wieder gefummelt :-)

              Ob du hier mal schauen magst ...

              lg Micha

              F 1 Antwort Letzte Antwort
              0
              • T tritanium

                @copystring

                Soooo, nachdem unser Q Revo nun das aktuellste Firmware Update gerade bekommen hat (V2.17.78), ersaufe ich in folgenden Meldungen:

                e23e8bb2-8361-497a-bd9e-21ed265cf52e-grafik.png

                Scheinbar hat Roborock wieder gefummelt :-)

                Ob du hier mal schauen magst ...

                lg Micha

                F Offline
                F Offline
                frankyboy73
                schrieb am zuletzt editiert von
                #356

                @tritanium Hi, das gleiche habe ich mit meinem Q Revo auch.
                Zusätzlich habe ich noch das Problem das ich einige die Datenpunkte wie z.B.
                set_custom_mode und set_water_box_custom_mode
                nicht mehr steuern kann, werden nicht bestätigt und haben keine Auswirkungen auf das verhalten des Roboters.

                2023-12-29 10:01:06.810 - error: roborock.0 (2434) Failed to execute get_status on robot 3H1RtzirmjxWDKKt6bcR9P Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                2023-12-29 10:27:34.665 - warn: roborock.0 (28954) Failed to execute set_custom_mode on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 56 with method 57 timed out after 10 seconds for response.102
                2023-12-29 10:27:34.916 - warn: roborock.0 (28954) Failed to execute set_water_box_custom_mode on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 59 with method 60 timed out after 10 seconds for response.102
                

                Die neue DEV habe ich schon drauf, keine Besserung

                Schöne Grüße Frank

                1 Antwort Letzte Antwort
                0
                • M Offline
                  M Offline
                  michael 1975
                  schrieb am zuletzt editiert von
                  #357

                  bei mir geht seit gestern auch nichts mehr kann den Robi nicht mal mehr starten ist ein S8

                  1 Antwort Letzte Antwort
                  0
                  • F Offline
                    F Offline
                    frankyboy73
                    schrieb am zuletzt editiert von
                    #358

                    Hi, beim Adapterstart kommen jetzt auch einige Fehlermeldungen bei mir, mit denen ich leider nichts anfangen kann.

                    2023-12-30 11:26:22.292 - info: roborock.0 (2773) starting. Version 0.4.4 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17
                    2023-12-30 11:26:28.041 - info: roborock.0 (2773) MQTT initialized
                    2023-12-30 11:26:34.835 - warn: roborock.0 (2773) Restart initiated
                    2023-12-30 11:26:34.887 - info: roborock.0 (2773) terminating
                    2023-12-30 11:26:34.889 - info: roborock.0 (2773) Terminated (NO_ERROR): Without reason
                    2023-12-30 11:26:35.341 - info: roborock.0 (2773) terminating
                    2023-12-30 11:26:35.469 - error: roborock.0 (2773) 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().
                    2023-12-30 11:26:35.470 - error: roborock.0 (2773) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:26:35.477 - error: roborock.0 (2773) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.479 - error: roborock.0 (2773) Connection is closed.
                    2023-12-30 11:26:35.501 - error: roborock.0 (2773) 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().
                    2023-12-30 11:26:35.504 - error: roborock.0 (2773) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:26:35.505 - error: roborock.0 (2773) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.505 - error: roborock.0 (2773) Connection is closed.
                    2023-12-30 11:26:35.508 - error: roborock.0 (2773) 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().
                    2023-12-30 11:26:35.509 - error: roborock.0 (2773) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:26:35.509 - error: roborock.0 (2773) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.510 - error: roborock.0 (2773) Connection is closed.
                    2023-12-30 11:26:35.512 - error: roborock.0 (2773) 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().
                    2023-12-30 11:26:35.513 - error: roborock.0 (2773) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:26:35.513 - error: roborock.0 (2773) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.514 - error: roborock.0 (2773) Connection is closed.
                    2023-12-30 11:26:35.516 - error: roborock.0 (2773) Failed to get home details: Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.680 - error: host.raspberrypi Caught by controller[0]: 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(). The promise rejected with the reason:
                    2023-12-30 11:26:35.681 - error: host.raspberrypi Caught by controller[1]: Error: Connection is closed.
                    2023-12-30 11:26:35.681 - error: host.raspberrypi Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:26:35.682 - error: host.raspberrypi Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:26:35.682 - error: host.raspberrypi Caught by controller[1]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:26:35.682 - error: host.raspberrypi Caught by controller[1]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:26:35.682 - error: host.raspberrypi Caught by controller[1]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:26:35.682 - error: host.raspberrypi Caught by controller[1]: at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[2]: 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(). The promise rejected with the reason:
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[3]: Error: Connection is closed.
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[3]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[3]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:26:35.683 - error: host.raspberrypi Caught by controller[3]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:26:35.684 - error: host.raspberrypi Caught by controller[3]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:26:35.684 - error: host.raspberrypi Caught by controller[3]: at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.684 - error: host.raspberrypi Caught by controller[4]: 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(). The promise rejected with the reason:
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: Error: Connection is closed.
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:26:35.685 - error: host.raspberrypi Caught by controller[5]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[5]: at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[6]: 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(). The promise rejected with the reason:
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[7]: Error: Connection is closed.
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:26:35.686 - error: host.raspberrypi Caught by controller[7]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:26:35.687 - error: host.raspberrypi Caught by controller[7]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:26:35.687 - error: host.raspberrypi Caught by controller[7]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:26:35.687 - error: host.raspberrypi Caught by controller[7]: at TCP. (node:net:350:12)
                    2023-12-30 11:26:35.687 - info: host.raspberrypi instance system.adapter.roborock.0 terminated with code 0 (NO_ERROR)
                    2023-12-30 11:26:35.688 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                    2023-12-30 11:26:49.585 - info: alexa2.0 (2138) Subscribing to states...
                    2023-12-30 11:26:51.574 - info: alexa2.0 (2138) Alexa-Push-Connection (macDms = true) established. Disable Polling
                    2023-12-30 11:27:05.795 - info: host.raspberrypi instance system.adapter.roborock.0 started with pid 2789
                    2023-12-30 11:27:15.131 - info: alexa2.0 (2138) Initialization Done ...
                    2023-12-30 11:27:16.019 - info: roborock.0 (2789) starting. Version 0.4.4 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17
                    2023-12-30 11:27:21.940 - info: roborock.0 (2789) MQTT initialized
                    2023-12-30 11:27:27.682 - warn: roborock.0 (2789) Restart initiated
                    2023-12-30 11:27:27.697 - info: roborock.0 (2789) terminating
                    2023-12-30 11:27:27.700 - info: roborock.0 (2789) Terminated (NO_ERROR): Without reason
                    2023-12-30 11:27:28.189 - info: roborock.0 (2789) terminating
                    2023-12-30 11:27:28.220 - error: roborock.0 (2789) 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().
                    2023-12-30 11:27:28.221 - error: roborock.0 (2789) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:27:28.228 - error: roborock.0 (2789) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.229 - error: roborock.0 (2789) Connection is closed.
                    2023-12-30 11:27:28.251 - error: roborock.0 (2789) 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().
                    2023-12-30 11:27:28.252 - error: roborock.0 (2789) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:27:28.253 - error: roborock.0 (2789) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.253 - error: roborock.0 (2789) Connection is closed.
                    2023-12-30 11:27:28.256 - error: roborock.0 (2789) 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().
                    2023-12-30 11:27:28.257 - error: roborock.0 (2789) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:27:28.257 - error: roborock.0 (2789) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.258 - error: roborock.0 (2789) Connection is closed.
                    2023-12-30 11:27:28.260 - error: roborock.0 (2789) 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().
                    2023-12-30 11:27:28.261 - error: roborock.0 (2789) unhandled promise rejection: Connection is closed.
                    2023-12-30 11:27:28.262 - error: roborock.0 (2789) Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.262 - error: roborock.0 (2789) Connection is closed.
                    2023-12-30 11:27:28.264 - error: roborock.0 (2789) Failed to get home details: Error: Connection is closed.
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:632:26)
                    at Socket.emit (node:events:517:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.369 - error: host.raspberrypi Caught by controller[0]: 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(). The promise rejected with the reason:
                    2023-12-30 11:27:28.370 - error: host.raspberrypi Caught by controller[1]: Error: Connection is closed.
                    2023-12-30 11:27:28.370 - error: host.raspberrypi Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:27:28.371 - error: host.raspberrypi Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:27:28.371 - error: host.raspberrypi Caught by controller[1]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:27:28.371 - error: host.raspberrypi Caught by controller[1]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:27:28.371 - error: host.raspberrypi Caught by controller[1]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:27:28.372 - error: host.raspberrypi Caught by controller[1]: at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.372 - error: host.raspberrypi Caught by controller[2]: 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(). The promise rejected with the reason:
                    2023-12-30 11:27:28.372 - error: host.raspberrypi Caught by controller[3]: Error: Connection is closed.
                    2023-12-30 11:27:28.372 - error: host.raspberrypi Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:27:28.373 - error: host.raspberrypi Caught by controller[3]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:27:28.373 - error: host.raspberrypi Caught by controller[3]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:27:28.373 - error: host.raspberrypi Caught by controller[3]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:27:28.373 - error: host.raspberrypi Caught by controller[3]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:27:28.374 - error: host.raspberrypi Caught by controller[3]: at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.374 - error: host.raspberrypi Caught by controller[4]: 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(). The promise rejected with the reason:
                    2023-12-30 11:27:28.374 - error: host.raspberrypi Caught by controller[5]: Error: Connection is closed.
                    2023-12-30 11:27:28.374 - error: host.raspberrypi Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:27:28.375 - error: host.raspberrypi Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:27:28.375 - error: host.raspberrypi Caught by controller[5]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:27:28.375 - error: host.raspberrypi Caught by controller[5]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:27:28.375 - error: host.raspberrypi Caught by controller[5]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:27:28.376 - error: host.raspberrypi Caught by controller[5]: at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.376 - error: host.raspberrypi Caught by controller[6]: 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(). The promise rejected with the reason:
                    2023-12-30 11:27:28.377 - error: host.raspberrypi Caught by controller[7]: Error: Connection is closed.
                    2023-12-30 11:27:28.377 - error: host.raspberrypi Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-12-30 11:27:28.377 - error: host.raspberrypi Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-12-30 11:27:28.377 - error: host.raspberrypi Caught by controller[7]: at Object.onceWrapper (node:events:632:26)
                    2023-12-30 11:27:28.378 - error: host.raspberrypi Caught by controller[7]: at Socket.emit (node:events:517:28)
                    2023-12-30 11:27:28.378 - error: host.raspberrypi Caught by controller[7]: at Socket.emit (node:domain:489:12)
                    2023-12-30 11:27:28.378 - error: host.raspberrypi Caught by controller[7]: at TCP. (node:net:350:12)
                    2023-12-30 11:27:28.378 - info: host.raspberrypi instance system.adapter.roborock.0 terminated with code 0 (NO_ERROR)
                    2023-12-30 11:27:28.379 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                    2023-12-30 11:27:58.499 - info: host.raspberrypi instance system.adapter.roborock.0 started with pid 2815
                    2023-12-30 11:28:06.811 - info: roborock.0 (2815) starting. Version 0.4.4 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17
                    2023-12-30 11:28:12.744 - info: roborock.0 (2815) MQTT initialized
                    2023-12-30 11:30:12.088 - info: broadlink2.0 (2256) interface to be used: { netmaskBits: 24, address: '192.168.5.10/24', addrs: [ 192, 168, 5, 10 ], cidr: '192.168.5.10/24', bcaddr: '192.168.5.255'
                    }:
                    2023-12-30 11:30:12.090 - info: broadlink2.0 (2256) discover [ '192.168.5.86' ] from 0.0.0.0:56805
                    2023-12-30 11:30:30.675 - info: admin.0 (2027) ==> Connected system.user.admin from ::ffff:192.168.5.76
                    2023-12-30 11:30:34.936 - info: host.raspberrypi Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                    2023-12-30 11:31:14.449 - info: admin.0 (2027) <== Disconnect system.user.admin from ::ffff:192.168.5.76
                    2023-12-30 11:31:36.295 - info: roborock.0 (2815) State value to set for "roborock.0.Devices.3H1RtzirmjxWDKKt6bcR9P.programs.1850557.items.0.id" has to be type "string" but received type "number"
                    2023-12-30 11:31:36.297 - info: roborock.0 (2815) State value to set for "roborock.0.Devices.3H1RtzirmjxWDKKt6bcR9P.programs.1850557.items.0.finishDpIds" has to be type "string" but received type "object"
                    2023-12-30 11:31:36.367 - info: roborock.0 (2815) State value to set for "roborock.0.Devices.3H1RtzirmjxWDKKt6bcR9P.programs.1850517.items.0.id" has to be type "string" but received type "number"
                    2023-12-30 11:31:36.411 - info: roborock.0 (2815) State value to set for "roborock.0.Devices.3H1RtzirmjxWDKKt6bcR9P.programs.1850517.items.0.finishDpIds" has to be type "string" but received type "object"
                    2023-12-30 11:31:46.221 - warn: roborock.0 (2815) Failed to execute get_fw_features on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 0 with method get_fw_features timed out after 10 seconds for response.102
                    2023-12-30 11:31:46.226 - warn: roborock.0 (2815) Failed to execute get_status on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
                    2023-12-30 11:31:46.257 - warn: roborock.0 (2815) Failed to execute get_clean_summary on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 2 with method get_clean_summary timed out after 10 seconds for response.102
                    2023-12-30 11:32:36.173 - error: roborock.0 (2815) Failed to execute get_status on robot 3H1RtzirmjxWDKKt6bcR9P Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                    
                    

                    Schöne Grüße Frank

                    1 Antwort Letzte Antwort
                    0
                    • F Offline
                      F Offline
                      frankyboy73
                      schrieb am zuletzt editiert von
                      #359

                      Hi, es gab gestern noch mal ne neue DEV seit dem sind die Fehlermeldungen bei mir weg. Der Roboter lässt sich auch wieder steuern.
                      Nur das Problem, das ich "set_custom_mode" und "set_water_box_custom"_mode nicht setzen kann bzw. das nicht übernommen wird, besteht weiter.

                      2024-01-01 10:09:59.900 - warn: roborock.0 (20830) Failed to execute set_water_box_custom_mode on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 9790 with method 9791 timed out after 10 seconds for response.102
                      2024-01-01 10:10:04.691 - warn: roborock.0 (20830) Failed to execute set_custom_mode on robot 3H1RtzirmjxWDKKt6bcR9P Error: Local request with id 9792 with method 9793 timed out after 10 seconds for response.102
                      

                      Schöne Grüße Frank

                      1 Antwort Letzte Antwort
                      0
                      • F Offline
                        F Offline
                        frankyboy73
                        schrieb am zuletzt editiert von frankyboy73
                        #360

                        Hi, kann mir jemand sagen, was ich in den Datenpunkt "startprogram" reinschreiben muss damit ein Programm gestartet wird? Ich habe es mit einem String probiert (Programmname), das klappt aber leider nicht. Wenn ich direkt im Datenpunkt das Programm über das Auswahlmenü setzte klappt es aber.

                        robo1.jpg

                        robo2.jpg

                        Edit: Hat sich erledigt, ich habs gefunden. Man muss einfach die Programmnummer als String in den Datenpunkt schreiben,

                        Schöne Grüße Frank

                        1 Antwort Letzte Antwort
                        0
                        • S Offline
                          S Offline
                          stefu87_CH
                          schrieb am zuletzt editiert von
                          #361

                          Hallo zusammen

                          Ich bin auf der Suche nach einer Lösung für mein Problem und wollte mich mal bei euch erkundigen, ob ich der einzige bin oder ob es noch andere gibt.
                          Folgendes Thema:
                          Ich habe einen Roborock S8 Pro Ultra. Habe mit dem Adapter Roborock und Mihome-Vaccum versucht und bei beiden Adaptern bekomme ich keine Meldungen von der Station. In den App's wird aber jeweils angezeigt, wenn z.B. der Wasserbehälter leer ist.
                          Im Log erhalte ich auch keine Meldungen dazu. Bei mir bleibt der Wert im Adapter unverändert.
                          Ist das bei einem Anwender von euch auch so?

                          8 x Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
                          Gigabyte mit Proxmox
                          LXC Container mit Iobroker

                          copystringC 1 Antwort Letzte Antwort
                          0
                          • S stefu87_CH

                            Hallo zusammen

                            Ich bin auf der Suche nach einer Lösung für mein Problem und wollte mich mal bei euch erkundigen, ob ich der einzige bin oder ob es noch andere gibt.
                            Folgendes Thema:
                            Ich habe einen Roborock S8 Pro Ultra. Habe mit dem Adapter Roborock und Mihome-Vaccum versucht und bei beiden Adaptern bekomme ich keine Meldungen von der Station. In den App's wird aber jeweils angezeigt, wenn z.B. der Wasserbehälter leer ist.
                            Im Log erhalte ich auch keine Meldungen dazu. Bei mir bleibt der Wert im Adapter unverändert.
                            Ist das bei einem Anwender von euch auch so?

                            copystringC Offline
                            copystringC Offline
                            copystring
                            schrieb am zuletzt editiert von
                            #362

                            @stefu87_ch Der Adapter kann das aktuell nicht. Vielleicht finde ich irgendwann Zeit dafür, das einzubauen.

                            Unterstütze meine Arbeit gerne mit einer Spende über PayPal:
                            https://paypal.me/copystring

                            M 1 Antwort Letzte Antwort
                            0
                            • copystringC copystring

                              @stefu87_ch Der Adapter kann das aktuell nicht. Vielleicht finde ich irgendwann Zeit dafür, das einzubauen.

                              M Offline
                              M Offline
                              michael 1975
                              schrieb am zuletzt editiert von michael 1975
                              #363

                              @copystring der kann oder könnte das schon unter Dock Erros Status ist e eine bestimmte Zahl,
                              nur leider geht bei mir im Moment gar nichts. Ich habe im Log folgendes stehen
                              Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')
                              nach einem Neustart obwohl der Adapter grün ist.
                              @copystring hast du vielleicht dafür eine Lösung.

                              Gruß Michael

                              S 1 Antwort Letzte Antwort
                              0
                              • M michael 1975

                                @copystring der kann oder könnte das schon unter Dock Erros Status ist e eine bestimmte Zahl,
                                nur leider geht bei mir im Moment gar nichts. Ich habe im Log folgendes stehen
                                Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId')
                                nach einem Neustart obwohl der Adapter grün ist.
                                @copystring hast du vielleicht dafür eine Lösung.

                                Gruß Michael

                                S Offline
                                S Offline
                                stefu87_CH
                                schrieb am zuletzt editiert von
                                #364

                                @michael-1975 also bei mir ist beim Adapter Roborock und MiHome-vaccum jeweils eine 0 drin und steht ok. Auch wenn in der Station der Wassertank leer ist.

                                8 x Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
                                Gigabyte mit Proxmox
                                LXC Container mit Iobroker

                                M 1 Antwort Letzte Antwort
                                0
                                • S stefu87_CH

                                  @michael-1975 also bei mir ist beim Adapter Roborock und MiHome-vaccum jeweils eine 0 drin und steht ok. Auch wenn in der Station der Wassertank leer ist.

                                  M Offline
                                  M Offline
                                  michael 1975
                                  schrieb am zuletzt editiert von
                                  #365

                                  @stefu87_ch bei mir hat er bis vor 3 4 Tagen dort eine 38 oder39 reingeschrieben und diese zeigt dann Wassertank leer an hat super geklappt kam immer eine Meldung auf der Vis.
                                  Nur geht seither leider gar nichts mehr nicht einmal Starten und keiner weis warum so wie es aussieht.

                                  S copystringC 2 Antworten Letzte Antwort
                                  0
                                  • M michael 1975

                                    @stefu87_ch bei mir hat er bis vor 3 4 Tagen dort eine 38 oder39 reingeschrieben und diese zeigt dann Wassertank leer an hat super geklappt kam immer eine Meldung auf der Vis.
                                    Nur geht seither leider gar nichts mehr nicht einmal Starten und keiner weis warum so wie es aussieht.

                                    S Offline
                                    S Offline
                                    stefu87_CH
                                    schrieb am zuletzt editiert von
                                    #366

                                    @michael-1975 ok das ist speziell ja. Also ich hatte vor ca 4 Tagen ein FW Update auf dem Sauger. Ich verwende eigentlich MiHome Adapter und dann kann ich starten. Aber aus Intresse ob es bei Roborock klappt mit der Station habe ich testweise mal den Adapter installiert, aber ohne Erfolg

                                    8 x Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
                                    Gigabyte mit Proxmox
                                    LXC Container mit Iobroker

                                    1 Antwort Letzte Antwort
                                    0
                                    • M michael 1975

                                      @stefu87_ch bei mir hat er bis vor 3 4 Tagen dort eine 38 oder39 reingeschrieben und diese zeigt dann Wassertank leer an hat super geklappt kam immer eine Meldung auf der Vis.
                                      Nur geht seither leider gar nichts mehr nicht einmal Starten und keiner weis warum so wie es aussieht.

                                      copystringC Offline
                                      copystringC Offline
                                      copystring
                                      schrieb am zuletzt editiert von
                                      #367

                                      @michael-1975 said in Neuer Adapter für Roborock-Staubsauger:

                                      Nur geht seither leider gar nichts mehr nicht einmal Starten und keiner weis warum so wie es aussieht.

                                      Das stimmt nicht so ganz. Es gibt aktuell zwei Probleme. Eins davon ist bereits gelöst. Aber wie ersten Post geschrieben, werde ich mich nicht um Fehler des Adapters über das Forum kümmern.
                                      Für das zweite ausstehende Problem kannst du sehr gerne mithelfen, das Problem einzugrenzen, indem du hier nachschaust: https://github.com/copystring/ioBroker.roborock/issues/449#issuecomment-1871173235
                                      Wenn du den Fehler reproduzieren kannst, erstell doch bitte ein vollständiges Debuglog mit der aktuellen dev-Version von GitHub https://github.com/copystring/ioBroker.roborock/tree/dev in dem der Fehler zu sehen ist.
                                      In der aktuellen dev-Version sind bereits einige Fehler behoben.

                                      Unterstütze meine Arbeit gerne mit einer Spende über PayPal:
                                      https://paypal.me/copystring

                                      M 1 Antwort Letzte Antwort
                                      0
                                      • copystringC copystring

                                        @michael-1975 said in Neuer Adapter für Roborock-Staubsauger:

                                        Nur geht seither leider gar nichts mehr nicht einmal Starten und keiner weis warum so wie es aussieht.

                                        Das stimmt nicht so ganz. Es gibt aktuell zwei Probleme. Eins davon ist bereits gelöst. Aber wie ersten Post geschrieben, werde ich mich nicht um Fehler des Adapters über das Forum kümmern.
                                        Für das zweite ausstehende Problem kannst du sehr gerne mithelfen, das Problem einzugrenzen, indem du hier nachschaust: https://github.com/copystring/ioBroker.roborock/issues/449#issuecomment-1871173235
                                        Wenn du den Fehler reproduzieren kannst, erstell doch bitte ein vollständiges Debuglog mit der aktuellen dev-Version von GitHub https://github.com/copystring/ioBroker.roborock/tree/dev in dem der Fehler zu sehen ist.
                                        In der aktuellen dev-Version sind bereits einige Fehler behoben.

                                        M Offline
                                        M Offline
                                        michael 1975
                                        schrieb am zuletzt editiert von
                                        #368

                                        @copystring danke für die Info ich war bisher nicht wirklich auf Github unterwegs, aber die Lösung mit Objekte löschen und Adapter neustarten hat geholfen danke.
                                        @stefu87_CH ich werde berichten ob er mir auch wieder den Wasserstand anzeigt.

                                        Gruß Michael

                                        S 1 Antwort Letzte Antwort
                                        0
                                        • M michael 1975

                                          @copystring danke für die Info ich war bisher nicht wirklich auf Github unterwegs, aber die Lösung mit Objekte löschen und Adapter neustarten hat geholfen danke.
                                          @stefu87_CH ich werde berichten ob er mir auch wieder den Wasserstand anzeigt.

                                          Gruß Michael

                                          S Offline
                                          S Offline
                                          stefu87_CH
                                          schrieb am zuletzt editiert von
                                          #369

                                          @michael-1975 also beim Mihome Adapter habe ich jetzt was herausgefunden. Der Status der Station wird erst gesendet, wenn der Sauger einen Befehl bekommt zum reinigen, sonst passiert da nichts.

                                          8 x Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
                                          Gigabyte mit Proxmox
                                          LXC Container mit Iobroker

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          580

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe