Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. JavaScript
    5. Roborock Adapter tester gesucht

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Roborock Adapter tester gesucht

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

      @dontoben Wieso muehselig bei einem PI?

      Kannst das Betriebssystem auch updaten:

      https://forum.iobroker.net/topic/47213/upgrade-von-debian-10-buster-auf-11-bullseye?page=1

      Vorher natuerlich ein Backup machen.

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

        SIGSEGV steht für Segmentation fault. Ein Programm stürzt also ab. Dass das von meinen Adapter direkt kommt ist eher unwahrscheinlich. Es wird wohl eher daher kommen, dass entweder eine Bibliothek (vielleicht canvas von npm) abstürzt oder ein RPi nicht damit klar kommt, dass die Karte jede Sekunde neu erstellt wird. Beim meinen Server lief das auch nicht richtig aber es kam nie ein Absturz. Daher hatte ich das bereits auf 2 Sekunden reduziert.

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

          @dontoben said in Roborock Adapter tester gesucht:

          @hunter-0 said in Roborock Adapter tester gesucht:

          @dontoben
          Ist Node v16 nicht voraussetzen? Du hast: (node: v14.18.1)

          Gleiches Problem mit Node v16.19.0

          Hier mal der Log vom installieren des Adapters. Waren das schon immer so viele Meldungen?

          $ iobroker url copystring/ioBroker.roborock --host raspberrypi --debug
          
          install copystring/ioBroker.roborock
          
          NPM version: 6.14.5
          
          Installing copystring/ioBroker.roborock... (System call)
          
          > canvas@2.11.0 install /opt/iobroker/node_modules/canvas> node-pre-gyp install --fallback-to-build --update-binary
          
          node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.0/canvas-v2.11.0-node-v93-linux-glibc-arm.tar.gz
          
          node-pre-gyp WARN Pre-built binaries not installable for canvas@2.11.0 and node@16.19.0 (node-v93 ABI, glibc) (falling back to source compile with node-gyp) node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.0/canvas-v2.11.0-node-v93-linux-glibc-arm.tar.gz
          
          (node:4471) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
          
          (Use `node --trace-deprecation ...` to show where the warning was created)
          
          make: Verzeichnis „/opt/iobroker/node_modules/canvas/build“ wird betreten
          
          SOLINK_MODULE(target) Release/obj.target/canvas-postbuild.node
          
          CXX(target) Release/obj.target/canvas/src/backend/Backend.o
          
          CXX(target) Release/obj.target/canvas/src/backend/ImageBackend.o
          
          CXX(target) Release/obj.target/canvas/src/backend/PdfBackend.o
          
          CXX(target) Release/obj.target/canvas/src/backend/SvgBackend.o
          
          CXX(target) Release/obj.target/canvas/src/bmp/BMPParser.o
          
          ../src/bmp/BMPParser.cc: In member function ‘void BMPParser::Parser::parse(uint8_t*, int, uint8_t*)’:../src/bmp/BMPParser.cc:186:16: warning: comparison of integer expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare] E(ptr - data > imgdOffset, "image data overlaps with another structure"); ~~~~~~~~~~~^~~~~~~~~~~~../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg) ^~~~../src/bmp/BMPParser.cc:201:27: warning: comparison of integer expressions of different signedness: ‘uint32_t’ {aka ‘unsigned int’} and ‘int’ [-Wsign-compare] E(ptr - data + imgdSize > len, "not enough image data"); ~~~~~~~~~~~~~~~~~~~~~~^~~~~../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg) ^~~~
          
          CXX(target) Release/obj.target/canvas/src/Backends.o
          
          CXX(target) Release/obj.target/canvas/src/Canvas.o
          
          CXX(target) Release/obj.target/canvas/src/CanvasGradient.o
          
          CXX(target) Release/obj.target/canvas/src/CanvasPattern.o
          
          CXX(target) Release/obj.target/canvas/src/CanvasRenderingContext2d.o
          
          ../src/CanvasRenderingContext2d.cc: In member function ‘void Context2d::setTextPath(double, double)’:../src/CanvasRenderingContext2d.cc:2494:10: warning: enumeration value ‘TEXT_ALIGNMENT_LEFT’ not handled in switch [-Wswitch] switch (state->textAlignment) { ^../src/CanvasRenderingContext2d.cc:2494:10: warning: enumeration value ‘TEXT_ALIGNMENT_START’ not handled in switch [-Wswitch]
          
          CXX(target) Release/obj.target/canvas/src/closure.o
          
          CXX(target) Release/obj.target/canvas/src/color.o
          
          CXX(target) Release/obj.target/canvas/src/Image.o
          
          CXX(target) Release/obj.target/canvas/src/ImageData.o
          
          CXX(target) Release/obj.target/canvas/src/init.o
          
          CXX(target) Release/obj.target/canvas/src/register_font.o
          
          SOLINK_MODULE(target) Release/obj.target/canvas.node
          
          COPY Release/canvas.node
          
          make: Verzeichnis „/opt/iobroker/node_modules/canvas/build“ wird verlassen
          
          npm WARN crc@4.1.1 requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself.npm WARN http-cookie-agent@4.0.2 requires a peer of tough-cookie@^4.0.0 but none is installed. You must install peer dependencies yourself.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.8 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          
          + iobroker.roborock@0.0.6-alpha.0added 45 packages from 35 contributors and updated 1 package in 346.618s
          
          48 packages are looking for funding run `npm fund` for details
          
          upload [11] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/de/translations.json i18n/de/translations.json application/json
          
          upload [10] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/en/translations.json i18n/en/translations.json application/json
          
          upload [9] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/es/translations.json i18n/es/translations.json application/json
          
          upload [6] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
          
          upload [5] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
          
          upload [4] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
          
          upload [3] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
          
          upload [0] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/roborock.png roborock.png image/png
          
          Process exited with code 0
          

          Ist dies das selbe Problem https://github.com/copystring/ioBroker.roborock/issues/40?
          Für die Karte wird canvas benötigt und canvas scheint es für RPi (bzw. für arm) nicht zu geben... Daher 404 beim Herunterladen von canvas. Es scheint auch keine ältere Version von canvas für den RPi (arm) zu geben.
          Vielleicht gibt es eine alternative, welche auch auf dem RPi läuft...

          DonToben created this issue in copystring/ioBroker.roborock

          closed 0.0.6 Adapter startet ständig neu #40

          D 1 Reply Last reply Reply Quote 0
          • wendy2702
            wendy2702 last edited by wendy2702

            @DonToben

            mal versucht Canvas zu installieren:

            cd /opt/iobroker/
            npm install canvas
            
            1 Reply Last reply Reply Quote 0
            • copystring
              copystring last edited by wendy2702

              Vergiss was ich gesagt habe. canvas wurde anschließend erfolgreich kompiliert.
              Der eigentliche Fehler ist bei:

              npm WARN crc@4.1.1 requires a peer of buffer@>=6.0.3 but none is installed.
              
              1 Reply Last reply Reply Quote 0
              • wendy2702
                wendy2702 last edited by

                @copystring sagte in Roborock Adapter tester gesucht:

                buffer@>=6.0.3

                Da habe ich ja Glueck gehabt das es die bei mir gibt:

                 npm ls buffer
                [sudo] password for mi:
                iobroker.inst@2.0.3 /opt/iobroker
                +-- iobroker.modbus@5.0.11
                | `-- crc@4.1.1
                |   `-- buffer@6.0.3
                +-- iobroker.mqtt@4.0.7
                | `-- mqtt-connection@4.1.0
                |   `-- mqtt-packet@6.10.0
                |     `-- bl@4.1.0
                |       `-- buffer@5.7.1
                +-- iobroker.sayit@1.12.6
                | `-- aws-sdk@2.1071.0
                |   `-- buffer@4.9.2
                `-- iobroker.shelly@6.3.1
                  `-- shelly-iot@1.1.2
                    `-- coap@0.26.0
                      `-- bl@5.1.0
                        `-- buffer@6.0.3 deduped
                
                
                1 Reply Last reply Reply Quote 0
                • D
                  DonToben @copystring last edited by DonToben

                  @copystring said in Roborock Adapter tester gesucht:

                  @dontoben said in Roborock Adapter tester gesucht:

                  @hunter-0 said in Roborock Adapter tester gesucht:

                  @dontoben
                  Ist Node v16 nicht voraussetzen? Du hast: (node: v14.18.1)

                  Gleiches Problem mit Node v16.19.0

                  Hier mal der Log vom installieren des Adapters. Waren das schon immer so viele Meldungen?

                  $ iobroker url copystring/ioBroker.roborock --host raspberrypi --debug
                  
                  install copystring/ioBroker.roborock
                  
                  NPM version: 6.14.5
                  
                  Installing copystring/ioBroker.roborock... (System call)
                  
                  > canvas@2.11.0 install /opt/iobroker/node_modules/canvas> node-pre-gyp install --fallback-to-build --update-binary
                  
                  node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.0/canvas-v2.11.0-node-v93-linux-glibc-arm.tar.gz
                  
                  node-pre-gyp WARN Pre-built binaries not installable for canvas@2.11.0 and node@16.19.0 (node-v93 ABI, glibc) (falling back to source compile with node-gyp) node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.0/canvas-v2.11.0-node-v93-linux-glibc-arm.tar.gz
                  
                  (node:4471) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
                  
                  (Use `node --trace-deprecation ...` to show where the warning was created)
                  
                  make: Verzeichnis „/opt/iobroker/node_modules/canvas/build“ wird betreten
                  
                  SOLINK_MODULE(target) Release/obj.target/canvas-postbuild.node
                  
                  CXX(target) Release/obj.target/canvas/src/backend/Backend.o
                  
                  CXX(target) Release/obj.target/canvas/src/backend/ImageBackend.o
                  
                  CXX(target) Release/obj.target/canvas/src/backend/PdfBackend.o
                  
                  CXX(target) Release/obj.target/canvas/src/backend/SvgBackend.o
                  
                  CXX(target) Release/obj.target/canvas/src/bmp/BMPParser.o
                  
                  ../src/bmp/BMPParser.cc: In member function ‘void BMPParser::Parser::parse(uint8_t*, int, uint8_t*)’:../src/bmp/BMPParser.cc:186:16: warning: comparison of integer expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare] E(ptr - data > imgdOffset, "image data overlaps with another structure"); ~~~~~~~~~~~^~~~~~~~~~~~../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg) ^~~~../src/bmp/BMPParser.cc:201:27: warning: comparison of integer expressions of different signedness: ‘uint32_t’ {aka ‘unsigned int’} and ‘int’ [-Wsign-compare] E(ptr - data + imgdSize > len, "not enough image data"); ~~~~~~~~~~~~~~~~~~~~~~^~~~~../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg) ^~~~
                  
                  CXX(target) Release/obj.target/canvas/src/Backends.o
                  
                  CXX(target) Release/obj.target/canvas/src/Canvas.o
                  
                  CXX(target) Release/obj.target/canvas/src/CanvasGradient.o
                  
                  CXX(target) Release/obj.target/canvas/src/CanvasPattern.o
                  
                  CXX(target) Release/obj.target/canvas/src/CanvasRenderingContext2d.o
                  
                  ../src/CanvasRenderingContext2d.cc: In member function ‘void Context2d::setTextPath(double, double)’:../src/CanvasRenderingContext2d.cc:2494:10: warning: enumeration value ‘TEXT_ALIGNMENT_LEFT’ not handled in switch [-Wswitch] switch (state->textAlignment) { ^../src/CanvasRenderingContext2d.cc:2494:10: warning: enumeration value ‘TEXT_ALIGNMENT_START’ not handled in switch [-Wswitch]
                  
                  CXX(target) Release/obj.target/canvas/src/closure.o
                  
                  CXX(target) Release/obj.target/canvas/src/color.o
                  
                  CXX(target) Release/obj.target/canvas/src/Image.o
                  
                  CXX(target) Release/obj.target/canvas/src/ImageData.o
                  
                  CXX(target) Release/obj.target/canvas/src/init.o
                  
                  CXX(target) Release/obj.target/canvas/src/register_font.o
                  
                  SOLINK_MODULE(target) Release/obj.target/canvas.node
                  
                  COPY Release/canvas.node
                  
                  make: Verzeichnis „/opt/iobroker/node_modules/canvas/build“ wird verlassen
                  
                  npm WARN crc@4.1.1 requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself.npm WARN http-cookie-agent@4.0.2 requires a peer of tough-cookie@^4.0.0 but none is installed. You must install peer dependencies yourself.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.8 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  
                  + iobroker.roborock@0.0.6-alpha.0added 45 packages from 35 contributors and updated 1 package in 346.618s
                  
                  48 packages are looking for funding run `npm fund` for details
                  
                  upload [11] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/de/translations.json i18n/de/translations.json application/json
                  
                  upload [10] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/en/translations.json i18n/en/translations.json application/json
                  
                  upload [9] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/es/translations.json i18n/es/translations.json application/json
                  
                  upload [6] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
                  
                  upload [5] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
                  
                  upload [4] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
                  
                  upload [3] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
                  
                  upload [0] roborock.admin /opt/iobroker/node_modules/iobroker.roborock/admin/roborock.png roborock.png image/png
                  
                  Process exited with code 0
                  

                  Ist dies das selbe Problem https://github.com/copystring/ioBroker.roborock/issues/40?
                  Für die Karte wird canvas benötigt und canvas scheint es für RPi (bzw. für arm) nicht zu geben... Daher 404 beim Herunterladen von canvas. Es scheint auch keine ältere Version von canvas für den RPi (arm) zu geben.
                  Vielleicht gibt es eine alternative, welche auch auf dem RPi läuft...

                  @copystring
                  Ja das ist issue 40.
                  Ich mache dann heute mit deinen Anweisungen aus issue 40 weiter. Oder soll ich noch etwas anderes installieren?

                  DonToben created this issue in copystring/ioBroker.roborock

                  closed 0.0.6 Adapter startet ständig neu #40

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

                    @dontoben Siehe github.

                    1 Reply Last reply Reply Quote 0
                    • H
                      Hunter 0 last edited by

                      Da es noch keine neue Version ist, weiß ich nicht ob es ein Issue für Github ist. Main Branch stand jetzt:

                      7cd7913e-bf82-4187-a7b8-7215639b4d14-grafik.png

                      wendy2702 1 Reply Last reply Reply Quote 0
                      • wendy2702
                        wendy2702 @Hunter 0 last edited by wendy2702

                        @hunter-0 Bitte vollständiges Log als text in Code Tags </> posten.

                        Und vielleicht noch mitteilen was für ein System das ist.

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

                          Hi,

                          aktualisieren sich bei euch die Objekte noch?

                          Unser Sauger ist eben gefahren und ich kann keine Änderung in den Objekten feststellen.

                          Batterie z.B.

                          5a9042d0-3407-47c1-9d2b-009e5da13712-grafik.png

                          Nach knapp 45 minuten Arbeit unverändert.

                          Bisschen was RAM belegt er auch:

                          03ad756a-f681-465d-be1e-9c224b365418-grafik.png

                          Und im Log passiert zum Adapter nichts mehr.

                          Erst nach restart kommen die neuen Werte aber beim RAM hochzählen kann ich zugucken:

                          RAM.gif

                          Restart log ohne Debug:

                          mirko@iobroker:~$ tail -f /opt/iobroker/log/iobroker.current.log |grep roborock
                          2023-02-02 15:50:38.847  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
                          2023-02-02 15:50:38.851  - info: roborock.0 (77838) Got terminate signal TERMINATE_YOURSELF
                          2023-02-02 15:50:38.853  - info: roborock.0 (77838) terminating
                          2023-02-02 15:50:38.854  - info: roborock.0 (77838) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2023-02-02 15:50:39.007  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
                          2023-02-02 15:50:40.012  - info: host.iobroker stopInstance system.adapter.roborock.0 killing pid 77838
                          2023-02-02 15:50:40.323  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2023-02-02 15:50:42.148  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89295
                          2023-02-02 15:50:43.974  - info: roborock.0 (89295) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                          2023-02-02 15:50:44.177  - info: roborock.0 (89295) MQTT initialized
                          2023-02-02 15:51:23.345  - info: host.iobroker "system.adapter.roborock.0" disabled
                          2023-02-02 15:51:23.346  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
                          2023-02-02 15:51:23.360  - info: roborock.0 (89295) Got terminate signal TERMINATE_YOURSELF
                          2023-02-02 15:51:23.364  - info: roborock.0 (89295) terminating
                          2023-02-02 15:51:23.365  - info: roborock.0 (89295) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2023-02-02 15:51:23.392  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
                          2023-02-02 15:51:23.954  - warn: roborock.0 (89295) get state error: Connection is closed.
                          2023-02-02 15:51:23.956  - error: roborock.0 (89295) 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-02-02 15:51:23.956  - error: roborock.0 (89295) unhandled promise rejection: DB closed
                          2023-02-02 15:51:23.956  - error: roborock.0 (89295) Error: DB closed
                          2023-02-02 15:51:23.956  - error: roborock.0 (89295) DB closed
                          2023-02-02 15:51:24.059  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2023-02-02 15:52:43.193  - info: host.iobroker "system.adapter.roborock.0" enabled
                          2023-02-02 15:52:43.422  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89332
                          2023-02-02 15:52:44.603  - info: roborock.0 (89332) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                          2023-02-02 15:52:44.827  - info: roborock.0 (89332) MQTT initialized
                          2023-02-02 15:54:25.755  - info: host.iobroker "system.adapter.roborock.0" disabled
                          2023-02-02 15:54:25.756  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
                          2023-02-02 15:54:25.769  - info: roborock.0 (89332) Got terminate signal TERMINATE_YOURSELF
                          2023-02-02 15:54:25.772  - info: roborock.0 (89332) terminating
                          2023-02-02 15:54:25.772  - info: roborock.0 (89332) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2023-02-02 15:54:25.800  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
                          2023-02-02 15:54:26.440  - warn: roborock.0 (89332) get state error: Connection is closed.
                          2023-02-02 15:54:26.441  - error: roborock.0 (89332) 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-02-02 15:54:26.441  - error: roborock.0 (89332) unhandled promise rejection: DB closed
                          2023-02-02 15:54:26.442  - error: roborock.0 (89332) Error: DB closed
                          2023-02-02 15:54:26.442  - error: roborock.0 (89332) DB closed
                          2023-02-02 15:54:26.533  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          
                          

                          @copystring : soll ich ein Issue aufmachen?

                          Desweiteren, kann man es vielleicht so machen das die Karte nur aktualisiert wird wenn das Kerlchen fährt?

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

                            @wendy2702 Ja bitte ein Issue öffnen. Es scheint so zu sein, dass viel RAM belegt wird wenn unbekannte Befehle oder Statusnachrichten vorliegen. Siehe https://github.com/copystring/ioBroker.roborock/issues/34 und https://github.com/copystring/ioBroker.roborock/issues/49
                            Für solche Probleme brauche ich Tester da ich den passenden Saugroboter nicht habe. Hier z.B. den Roborock S7 MaxV (Ultra). Für den Roboter kann https://github.com/copystring/ioBroker.roborock/compare/update_robot_attributes getestet werden.

                            mproper23 created this issue in copystring/ioBroker.roborock

                            closed Unsupported attribute #34

                            mproper23 created this issue in copystring/ioBroker.roborock

                            closed extreme RAM Usage #49

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

                              @copystring sagte in Roborock Adapter tester gesucht:

                              a bitte ein Issue öffnen

                              Ich habe mich an das Issue dran gehangen, oder wolltest du zwingend ein neues?

                              https://github.com/copystring/ioBroker.roborock/issues/49

                              Für das Map Update neues Issue:

                              https://github.com/copystring/ioBroker.roborock/issues/50

                              mproper23 created this issue in copystring/ioBroker.roborock

                              closed extreme RAM Usage #49

                              wendy2702 created this issue in copystring/ioBroker.roborock

                              closed Anpassung Kartenupdate #50

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

                                @wendy2702 Ist schon ok so.

                                M-A Hueb 1 Reply Last reply Reply Quote 0
                                • M-A Hueb
                                  M-A Hueb @copystring last edited by M-A Hueb

                                  Hab mir jetzt mal Seq installiert, dann kann man besser das Log ziehen.
                                  Seq
                                  Gibts auch nen Adapter dazu

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    simplyclever @M-A Hueb last edited by

                                    @m-a-hueb Die Funktion suche ich auch. Aktuell lade ich den Log runter und (Linux/Mac) führe dann dieses Kommando in einer Shell aus:
                                    grep ": roborock" log.txt | sed 's/Name1/Kind1/' | sed 's/Name2/Kind2/' > robolog.txt

                                    Das grep filtert die roborock Eintröge aus dem Log, die beiden sed ersetzen die realen Namen meiner Kinder (die Räume sind so benannt) durch KindX..

                                    M-A Hueb 1 Reply Last reply Reply Quote 0
                                    • M-A Hueb
                                      M-A Hueb @simplyclever last edited by

                                      @simplyclever Danke aber bin unter Windows unterwegs. Mit dem Seq Tool ist das recht easy jetzt

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

                                        Log in Notepad++ geht auch

                                        M-A Hueb 1 Reply Last reply Reply Quote 0
                                        • M-A Hueb
                                          M-A Hueb @wendy2702 last edited by

                                          @wendy2702 Wie meinst du?

                                          wendy2702 1 Reply Last reply Reply Quote 0
                                          • wendy2702
                                            wendy2702 @M-A Hueb last edited by

                                            @m-a-hueb Das Log kann man auch in Notepad++ öffnen und einfach nach Roborock filtern. bzw. suchen.

                                            Dann erhält man auch eine Ausgabe in der nur die Daten vom Roborock Adapter stehen.

                                            Könnte dann z.B. so aus sehen mit FTP Plugin rechts auf iobroker und dort direkt das log anklicken. Dann mit STRG+F im Beispiel nach allen "ical.2" einträgen in der offenen Datei gesucht. Ergebnis dann unten.

                                            f5101111-cc3b-4d48-a23d-0447e705e3f1-grafik.png

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            718
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            51
                                            766
                                            145870
                                            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