Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Neuer Adapter für Roborock-Staubsauger

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    Neuer Adapter für Roborock-Staubsauger

    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      frankyboy73 last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • F
        frankyboy73 last edited by

        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
        1 Reply Last reply Reply Quote 0
        • F
          frankyboy73 last edited by frankyboy73

          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,

          1 Reply Last reply Reply Quote 0
          • S
            stefu87_CH last edited by

            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?

            copystring 1 Reply Last reply Reply Quote 0
            • copystring
              copystring @stefu87_CH last edited by

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

              M 1 Reply Last reply Reply Quote 0
              • M
                michael 1975 @copystring last edited by 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 1 Reply Last reply Reply Quote 0
                • S
                  stefu87_CH @michael 1975 last edited by

                  @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 1 Reply Last reply Reply Quote 0
                  • M
                    michael 1975 @stefu87_CH last edited by

                    @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 copystring 2 Replies Last reply Reply Quote 0
                    • S
                      stefu87_CH @michael 1975 last edited by

                      @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

                      1 Reply Last reply Reply Quote 0
                      • copystring
                        copystring @michael 1975 last edited by

                        @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.

                        Standarduser created this issue in copystring/ioBroker.roborock

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

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          michael 1975 @copystring last edited by

                          @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 Reply Last reply Reply Quote 0
                          • S
                            stefu87_CH @michael 1975 last edited by

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • copystring
                              copystring last edited by

                              Hallo Leute,

                              nach viele Arbeit konnte ich es endlich schaffen, 0.5.0 herauszubringen. Danke für das fleißige Testen der dev Version. Dadurch konnte ich diverse Fehler beheben.

                              Flexer 1 Reply Last reply Reply Quote 2
                              • Flexer
                                Flexer @copystring last edited by

                                @copystring Einfach nur Mega Arbeit von Dir! Macht wirklich Spaß wenn man Feedback vom Tester so super umgesetzt bekommt! Vielen Dank!

                                1 Reply Last reply Reply Quote 0
                                • copystring
                                  copystring last edited by

                                  Direkt einen Fehler übersehen. 0.5.0 wird leider nie erscheinen. Dafür aber 0.5.1. Sorry 🙂

                                  1 Reply Last reply Reply Quote 1
                                  • BanditFG
                                    BanditFG last edited by

                                    ich habe aktuell Version 0.4.4 installiert und viele Fehler im Log, kann mir bitte jemand erklären wie ich auf Version 0.5.1 updaten kann.???

                                    Danke

                                    L 1 Reply Last reply Reply Quote 0
                                    • L
                                      localhorst @BanditFG last edited by localhorst

                                      @banditfg
                                      Ich bekomme auch als stable nur die 0.4.4 angeboten.
                                      Die 0.5.1 kannst du direkt über diesen Pfad installieren:
                                      https://github.com/copystring/ioBroker.roborock/tree/v0.5.1

                                      Die Dev lief nun bei mir mit meinem Q8 Max Plus eine ganze Weile schon total stabil.
                                      Die direkte Verbindung zum Roborock ohne Cloud macht das ganze echt rocksolid.
                                      Auch nach dem Update auf die 0.5.1 war er sofort wieder erreichbar.
                                      Top Job und nochmals tausend Dank an copystring!

                                      1 Reply Last reply Reply Quote 0
                                      • copystring
                                        copystring last edited by

                                        0.5.1 ist nur in latest verfügbar. In stable noch nicht.

                                        A 1 Reply Last reply Reply Quote 0
                                        • A
                                          andibr @copystring last edited by

                                          also bei mir verursacht der 0.5.1 folgenden Fehler:

                                          roborock.0
	2024-01-04 14:07:07.858	error	Failed to get home details: TypeError: Cannot read properties of null (reading 'rrHomeId') at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:184:41) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0
	2024-01-04 14:07:07.444	info	starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17

                                          Ich habe einen Roborock S7 Max Ultra, der Datenpunkt Online zeigt abwechselnd immer mal wieder "false". Das obwohl der W-Lan Accesspoint eigentlich über der Docking-Station hängt und der Sauger drin steht.

                                          1 Reply Last reply Reply Quote 0
                                          • copystring
                                            copystring last edited by

                                            Sorry für den schlechten Release 0.5.1. Ich habe den wieder gelöscht. 0.5.0 kam ohnehin nie raus. Bitte installiert 0.4.4, wenn die bei euch läuft. Ich kümmere mich um einen neuen Release. Habe leider aktuell nur wenig Zeit.

                                            T 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            514
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            111
                                            796
                                            141767
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo