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

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Neuer Adapter für Roborock-Staubsauger

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

      17390070-8e14-42aa-afc9-0b1d1fdeebee-image.png

      Frederik Buss 2 Replies Last reply Reply Quote 0
      • Frederik Buss
        Frederik Buss @copystring last edited by

        @copystring Wenn man Tomaten auf den Augen hat 🤦 Danke 🙂

        1 Reply Last reply Reply Quote 0
        • B
          berndpehome last edited by

          Hab jetzt das selbe Problem wie Sepp weiter oben, heute das Update beim Saros 10 R eingespielt und der Adapter 0.6.19 wird kurz grün und springt dann wieder auf rot, mit der alten Firmware war er zwar grün aber hat die Datenpunkte nicht aktuallisiert, wäre super wenn es bald eine Lösung geben würde da jetzt mein S7 Max Ultra auch nicht mehr über den Adapter verwendbar ist, ansonsten Super Adapter und vielen Dank @copystring für Deine Arbeit.

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

            Habt ihr in der DockingStation Werte stehen ? Also in den DP's Wassertank, Schmutzwassertank usw ? Da steht bei mir überall Unknown 0. Hab den Edge S5A.

            1 Reply Last reply Reply Quote 0
            • B
              berndpehome last edited by

              nein, bei mir ist der komplette Ordner devices Status mit NULL, also keine Werte beim Saros10R

              1 Reply Last reply Reply Quote 0
              • B
                berndpehome last edited by wendy2702

                seit der neuen Firmware am Saros 10R funktioniert der 0.6.18 Adapter nicht mehr, mit der 0.6.19 bleibt er Grün, liest aber den kompletten Devices Status vom 10R nicht aus, mein S7 Max Ultra funktioniert mit der 0.6.19 wieder.

                Fehler bei 0.6.18

                host.iobroker
	2025-07-20 10:31:40.135	error	instance system.adapter.roborock.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: }
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: code: 'ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH'
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: reason: 'wrong final block length',
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: library: 'Provider routines',
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at UDP.onMessage (node:dgram:951:8) {
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:domain:489:12)
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:events:524:28)
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33)
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25)
host.iobroker
	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Decipheriv.final (node:internal/crypto/cipher:193:29)
host.iobroker
	2025-07-20 10:31:40.133	error	Caught by controller[0]: Error: error:1C80006B:Provider routines::wrong final block length
roborock.0
	2025-07-20 10:31:39.641	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
roborock.0
	2025-07-20 10:31:39.639	info	terminating
roborock.0
	2025-07-20 10:31:39.599	error	Exception-Code: ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH: error:1C80006B:Provider routines::wrong final block length
roborock.0
	2025-07-20 10:31:39.598	error	Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:193:29) at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8)
roborock.0
	2025-07-20 10:31:39.598	error	uncaught exception: error:1C80006B:Provider routines::wrong final block length
roborock.0
	2025-07-20 10:31:34.496	info	MQTT initialized
roborock.0
	2025-07-20 10:31:31.770	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
roborock.0
	2025-07-20 10:31:31.742	info	starting. Version 0.6.18 in /opt/iobroker/node_modules/iobroker.roborock, node: v20.19.4, js-controller: 7.0.6


Fehler bei 0.6.19 :



adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:59.970	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:58.972	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:58.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:57.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:57.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:56.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:56.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:55.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:55.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:54.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
roborock.0
	2025-07-20 10:38:54.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

                der 5rgCW0HwnOPBAukwOrCdcG ist mein S7 Ultra

                der 7ieq4IEzXQzxO3VVPTTgvf ist der Saros 10R

                Mod Edit: Log in Code Tags gesetzt

                da_Woody 1 Reply Last reply Reply Quote 0
                • da_Woody
                  da_Woody @berndpehome last edited by

                  @berndpehome könnest du dein log bitte über 4c670f50-bfef-427b-a79c-75f53c19370f-grafik.png einfügen?

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    berndpehome @da_Woody last edited by

                    @da_woody entschuldige, nicht daran gedacht, danke fürs ändern und mach ich das nächste mal

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

                      @copystring Übrigens ein super extra Danke für Deine Arbeit! Ich habe nun 2 Programme auf den Hauptscreen gepackt und wenn auch aktuell nur über Cloud (Saros 10...), der Robbi tut was er soll. Meine Frau feiert es, mit dem Ding nicht mehr sprechen zu müssen und wie heisst es so schön - Happy wife, happy Life 🙂

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

                        @frederik-buss danke. Freut mich, dass es so läuft wie du dir das vorgestellt hast.

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

                          Hi, seit dem letzten Roborock Update für meinen Qrevo Curv kann der Adapter sich nicht mehr verbinden. Ich mache gleich noch ein Issue auf Github auf.

                          
Failed to process undefined on robot undefined (unknown device model): Failed to process message: Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:193:29) at local_api.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/local_api.js:248:25) at Socket.handleMessage (/opt/iobroker/node_modules/iobroker.roborock/lib/local_api.js:199:34) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8)

Failed to process mainUpdateInterval on robot InAokiWwEHHT4hwBeMGFU (roborock.vacuum.a135): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
                          F 1 Reply Last reply Reply Quote 0
                          • F
                            fritzkalle @Skyx3 last edited by

                            Hallo zusammen,

                            ich habe den Adapter jetzt eine Weile mit dem Saros 10R laufen und er funktioniert zwar, stürzt aber häufig ab und ist dann bis zum Neustart nicht ansprechbar 😞
                            Das hier sind die Fehlermeldungen:

                            setTimeout called, but adapter is shutting down

Failed to process "get_clean_summary" on robot vArM2m3ap0E3f7dsbZWNX (roborock.vacuum.a144): Error: Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/maybeCallback.ts:129:17) at Roborock._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5017:26) at /opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2336:17

Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed.

Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/maybeCallback.ts:129:17) at Roborock._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5017:26) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at /opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2336:17

unhandled promise rejection: Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed.

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().

Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status": Connection is closed.

get state error: Connection is closed.

redis get roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.clean_type, error - Connection is closed.

setTimeout called, but adapter is shutting down

                            Ich weiß nicht, ob ich das mit dem Einfügen der Fehlermeldungen richtig gemacht habe. Ich bitte um Nachsicht. Auch weiß ich leider nicht ob und wie ich ein Issue auf Github aufmachen sollte.

                            Viele Grüße!

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

                              Immer erstmal auf GitHub nach schauen, ob jemand das gleiche Problem hat. Falls nicht, einfach ein GitHub Issue aufmachen. Ich schaue es mir dann an.

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

                                Hallo ich habe aktuell diesen Fehler. Kann mir einer verraten woran es liegt?

                                2025-07-26 17:58:52.423 - info: host.iobroker instance system.adapter.roborock.0 in version "0.6.19" (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) started with pid 2115372
2025-07-26 17:58:56.781 - info: roborock.0 (2115372) starting. Version 0.6.19 (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) in /opt/iobroker/node_modules/iobroker.roborock, node: v20.18.0, js-controller: 7.0.6
2025-07-26 17:58:56.799 - info: roborock.0 (2115372) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2025-07-26 17:58:56.821 - info: roborock.0 (2115372) Loaded existing clientID: ee6783f4-5d0a-4d48-b00e-7cafd23b31d9
2025-07-26 17:58:57.104 - error: roborock.0 (2115372) Failed to process undefined on robot undefined (unknown device model): TypeError: Cannot read properties of null (reading 'rrHomeId')
at http_api.getHomeID (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:111:31)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at http_api.updateHomeData (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:123:19)
at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:33:3)
at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-07-26 17:58:57.328 - info: roborock.0 (2115372) MQTT initialized
2025-07-26 17:58:57.329 - error: roborock.0 (2115372) 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().
2025-07-26 17:58:57.330 - error: roborock.0 (2115372) unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first
2025-07-26 17:58:57.330 - error: roborock.0 (2115372) Error: this.homeData is not initialized. Initialize via getHomeData() first
at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10)
at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)
2025-07-26 17:58:57.330 - error: roborock.0 (2115372) this.homeData is not initialized. Initialize via getHomeData() first
2025-07-26 17:58:57.343 - info: roborock.0 (2115372) terminating
2025-07-26 17:58:57.344 - warn: roborock.0 (2115372) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-07-26 17:58:57.402 - info: roborock.0 (2115372) MQTT connection established {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}.
2025-07-26 17:58:57.845 - info: roborock.0 (2115372) terminating
2025-07-26 17:58:57.994 - error: host.iobroker 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:
2025-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: Error: this.homeData is not initialized. Initialize via getHomeData() first
2025-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10)
2025-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)
2025-07-26 17:58:57.994 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-07-26 17:58:57.994 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled
2025-07-26 17:58:59.558 - warn: openknx.0 (1699916) Ignoring GroupValue_Write of unknown GA 9/0/4
2025-07-26 17:59:00.842 - info: host.iobroker "system.adapter.roborock.0" disabled
                                1 Reply Last reply Reply Quote 0
                                • C
                                  Creekhail last edited by

                                  Ich möchte mich für die Arbeit an diesem Adapter bedanken.

                                  Seit einigen Tagen sind wir auf den Saros 10R umgestiegen, vorher war der S7 MaxV im Einsatz. Dort hatte ich noch den Xiaomi-Adapter verwendet.
                                  Mit dem Umstieg auf das neue Modell habe ich auch bei der App den Wechsel zur Roborock-Original-App vollzogen. Somit musste auch im iobroker auf den neuen Adapter gewechselt werden.

                                  Nach leichten Anfangsschwierigkeiten (keine lokale Verbindung), läuft die Geschichte jetzt mit der Version 0.6.19
                                  Daher konnte ich heute auch im VIS die Anpassungen vornehmen, da die Steuerung doch in einigen Punkten vom bisherigen Xiaomi-Adapter abweicht.

                                  Die wesentlichen Dinge lassen sich jetzt wieder steuern bzw. ablesen, so dass auch ohne Handy der Roboter seinen Dienst verrichten kann.

                                  Anbei noch ein Screenshot von der VIS dazu.
                                  2025-07-26 23_32_06-vis.png

                                  T 1 Reply Last reply Reply Quote 0
                                  • T
                                    TimoWald @Creekhail last edited by

                                    @creekhail hallo könnte ich einen Export deiner Seite haben?

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      Creekhail @TimoWald last edited by

                                      @timowald Was genau hast du denn vor bzw. was meinst du mit "Export deiner Seite"?

                                      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

                                      960
                                      Online

                                      31.9k
                                      Users

                                      80.2k
                                      Topics

                                      1.3m
                                      Posts

                                      124
                                      864
                                      180610
                                      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