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

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Neuer Adapter für Roborock-Staubsauger

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

      @myssv 👍 ist aber kein Bug, eher request.
      Die Jungs werden das schon einordnen. 😉

      1 Reply Last reply Reply Quote 0
      • T
        Taddy81 last edited by

        Ich bekomme den Updater irgendwie nicht installiert, wo ist denn hier der Fehler?

         iobroker url https://github.com/copystring/ioBroker.roborock --host IOBroker --debug

install copystring/ioBroker.roborock#55d231dfd585a3d93537081d313ef52daa272acd

Installing copystring/ioBroker.roborock#55d231dfd585a3d93537081d313ef52daa272acd... (System call)

npm warn skipping integrity check for git dependency ssh://git@github.com/copystring/ioBroker.roborock.git

npm warn deprecated npmlog@7.0.1: This package is no longer supported.

npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported.

npm warn deprecated gauge@5.0.2: This package is no longer supported.

npm warn deprecated sinon@9.2.4: 16.1.1

> node dist/install.js

RequestError: getaddrinfo EAI_AGAIN github.com

npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-11-02T11_12_49_396Z-debug-0.log

npm warn skipping integrity check for git dependency ssh://git@github.com/copystring/ioBroker.roborock.gitnpm warn deprecated npmlog@7.0.1: This package is no longer supported.npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported.npm warn deprecated gauge@5.0.2: This package is no longer supported.npm warn deprecated sinon@9.2.4: 16.1.1RequestError: getaddrinfo EAI_AGAIN github.comnpm error code 1npm error path /opt/iobroker/node_modules/go2rtc-staticnpm error command failednpm error command sh -c node dist/install.jsnpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-11-02T11_12_49_396Z-debug-0.loghost.IOBroker Cannot install copystring/ioBroker.roborock#55d231dfd585a3d93537081d313ef52daa272acd: 1

ERROR: Process exited with code 25
        Thomas Braun 2 Replies Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Taddy81 last edited by

          @taddy81

          Grundsätzlich funktioniert das.

          $ iobroker url copystring/ioBroker.roborock --host chet --debug

install copystring/ioBroker.roborock
Installing copystring/ioBroker.roborock... (System call)
Support for loading ES Module in require() is an experimental feature and might change at any time(Use `node --trace-warnings ...` to show where the warning was created)
npm warn deprecated npmlog@7.0.1: This package is no longer supported.
npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported.
npm warn deprecated gauge@5.0.2: This package is no longer supported.
npm warn deprecated sinon@9.2.4: 16.1.1
> go2rtc-static@1.9.4 install> node dist/install.js
> node install.js
added 223 packages, and changed 1 package in 1m227 packages are looking for funding run `npm fund` for details
upload [13] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [12] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [10] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [9] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [7] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [5] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [4] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/uk/translations.json i18n/uk/translations.json application/json
upload [3] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [2] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/jsonConfig.json jsonConfig.json application/json
upload [1] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/roborock.png roborock.png image/png
Updating objects from io-package.json for adapter "roborock" with version "0.6.17"
Process exited with code 0

          RequestError: getaddrinfo EAI_AGAIN github.com

          Ist immer ein Hinweis auf Netzwerk-Trouble. github.com kann nicht erreicht werden.

          1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Taddy81 last edited by

            @taddy81

            Verwende

            iobroker url copystring/ioBroker.roborock --host IOBroker --debug

            auf dem System...

            1 Reply Last reply Reply Quote 0
            • T
              Taddy81 last edited by

              @thomas-braun

              Danke,

              hat funktioniert.

              Dein Code hat geklappt, warum hat denn der GitHub Repo nicht geklappt hat?

              Ein Problem war bei mir noch, dass meine Firewall die URL von Roborock blockiert hat. Ist nun aber gefixt und ich kann auf die Instanz zugreifen.

              Vielen Dank

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Taddy81 last edited by

                @taddy81 sagte in Neuer Adapter für Roborock-Staubsauger:

                Dein Code hat geklappt, warum hat denn der GitHub Repo nicht geklappt hat?

                Was genau hast du denn wo ausgewählt?

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

                  Seit 2 Tagen gabs in iOS ein Update der Roborock App sieht auch optisch anders aus. Seitdem funktioniert in ioBroker die Steuerung nicht mehr. Ich bekomm werte soweit alles gut aber keine Reaktion beim z.b starten des Saugers.

                  Jemand das gleiche Problem ?

                  C H 2 Replies Last reply Reply Quote 0
                  • C
                    chuck2941 @breaksrmine last edited by

                    @breaksrmine Also ich habe kein Update, die App sieht immer noch gleich aus und die Steuerung über ioBroker funktioniert.
                    Was aber immer im Log kommt wenn der Sauger läuft ist folgendes

                    roborock.0
2024-11-02 23:08:28.092	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.map.mapData" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:28.092	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.map.mapBase64Truncated" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:28.091	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.map.mapBase64" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.935	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.task_id" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.934	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.clean_times" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.933	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.dirty_replenish" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.932	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.manual_replenish" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.932	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.cleaned_area" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.931	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.map_flag" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.930	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.wash_count" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.930	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.929	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.dust_collection_status" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.929	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.finish_reason" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.928	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.clean_type" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.928	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.start_type" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.927	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.complete" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.926	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.error" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.925	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.area" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.924	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.duration" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.923	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.end" has no existing object, this might lead to an error in future versions

roborock.0
2024-11-02 23:08:27.923	warn	State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.22.begin" has no existing object, this might lead to an error in future versions

                    Ich kann die Einträge nicht finden in den Objekten

                    1 Reply Last reply Reply Quote 0
                    • H
                      hansano @breaksrmine last edited by hansano

                      @breaksrmine

                      Das kann ich so bestätigen, ist bei mir auch so

                      Edit: nach Neustart des Adapters läuft es wieder

                      B 1 Reply Last reply Reply Quote 1
                      • E
                        erickuttruff last edited by erickuttruff 

                        Failed to execute get_map_v1 on robot 2BFDPXMouOnerH911HQrgP (roborock.vacuum.a51): TypeError: The "chunk" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Array at _write (node:internal/streams/writable:480:13) at Gzip.Writable.end (node:internal/streams/writable:821:17) at zlibBuffer (node:zlib:129:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:776:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:70:11) at processTicksAndRejections (node:internal/process/task_queues:95:5)

                        Ich habe immer sehr viele Fehler wie im Screenshot zu sehen... An was liegt es?

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @erickuttruff last edited by

                          @erickuttruff sagte in Neuer Adapter für Roborock-Staubsauger:

                          wie im Screenshot zu sehen

                          Text bitte auch als TEXT in CodeTags eingebettet posten. Mit bunte Bildchens kann man nix anfangen.

                          E 1 Reply Last reply Reply Quote 0
                          • E
                            erickuttruff @Thomas Braun last edited by

                            @thomas-braun: Ich habe den Beitrag korrigiert...

                            1 Reply Last reply Reply Quote 0
                            • B
                              breaksrmine @hansano last edited by

                              @hansano bei mir auch so jetzt 🙂

                              1 Reply Last reply Reply Quote 0
                              • R
                                RISSN last edited by

                                unhandled promise rejection: Login returned empty userdata.

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

                                Error in getUserData: Login returned empty userdata.

                                Diese Fehler bekomme ich nach dem Updaten auf Version:
                                v0.6.17. Auch ein rücksetzen auf die Vorgängerversion bliebt ohne Erfolg. Hat das vielleicht noch jemand?

                                1 Reply Last reply Reply Quote 0
                                • Jey Cee
                                  Jey Cee Developer last edited by

                                  @rissn Meld dich mal in der App neu an, die hatte ein Update.
                                  Danach gehts wieder.

                                  R 1 Reply Last reply Reply Quote 0
                                  • R
                                    RISSN @Jey Cee last edited by

                                    @jey-cee vielen Dank, dass war es 👍

                                    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

                                    1.5k
                                    Online

                                    30.4k
                                    Users

                                    76.6k
                                    Topics

                                    1.2m
                                    Posts

                                    86
                                    690
                                    59568
                                    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