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

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

Community Forum

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

NEWS

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

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

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

Neuer Adapter für Roborock-Staubsauger

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
922 Beiträge 136 Kommentatoren 325.0k Aufrufe 125 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • S Offline
    S Offline
    samsungfreak
    schrieb am zuletzt editiert von
    #787

    Hallo,

    weiß jemand, wo die verfügbaren Werte dokumentiert sind vom Status "state"?
    Also Charging = Wert 8 usw.

    da_WoodyD jahnbesJ 2 Antworten Letzte Antwort
    0
    • S samsungfreak

      Hallo,

      weiß jemand, wo die verfügbaren Werte dokumentiert sind vom Status "state"?
      Also Charging = Wert 8 usw.

      da_WoodyD Offline
      da_WoodyD Offline
      da_Woody
      schrieb am zuletzt editiert von
      #788

      @samsungfreak
      https://github.com/copystring/ioBroker.roborock/wiki/Objekte-und-ihre-Bedeutung
      state - State

      Status
      

      Wert Bedeutung
      1 unbekannt
      2 schlafend, ohne laden
      3 inaktiv / idle
      5 reinigt
      6 Fahrt zur Ladestation
      7 Fernsteuerung
      8 laden
      10 Pause
      11 Punktreinigung
      12 Fehler
      16 Fahrt zum Ziel
      17 Zonenreinigung
      18 Raumreinigung
      22 Staubbehälter leeren (im Dock)
      23 Mopp waschen (im Dock)
      26 fahre Mopp waschen (im Dock)
      29 Karte erstellen

      gruß vom Woody
      HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

      1 Antwort Letzte Antwort
      0
      • S samsungfreak

        Hallo,

        weiß jemand, wo die verfügbaren Werte dokumentiert sind vom Status "state"?
        Also Charging = Wert 8 usw.

        jahnbesJ Offline
        jahnbesJ Offline
        jahnbes
        schrieb am zuletzt editiert von jahnbes
        #789

        @samsungfreak
        Hallo,
        wie immer stehen alle Angaben hier im Wiki.
        Viele Grüße, jahnbes.

        1 Antwort Letzte Antwort
        0
        • T Offline
          T Offline
          Tom_W
          schrieb am zuletzt editiert von
          #790

          Hallo,

          bei mir läuft das Log voll mit folgender Meldung:

          
          Failed to process get_status on robot 69MLydUJfX3n4mUt9S4WWy (roborock.vacuum.a97): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
          
          

          Weiß irgendjemand was das bedeutet und wie ich das weg bekomme?

          Danke

          Tom

          U 1 Antwort Letzte Antwort
          1
          • T Tom_W

            Hallo,

            bei mir läuft das Log voll mit folgender Meldung:

            
            Failed to process get_status on robot 69MLydUJfX3n4mUt9S4WWy (roborock.vacuum.a97): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
            
            

            Weiß irgendjemand was das bedeutet und wie ich das weg bekomme?

            Danke

            Tom

            U Online
            U Online
            uwe72
            schrieb am zuletzt editiert von
            #791

            @tom_w

            Bei mir leider auch

            Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
            
            1 Antwort Letzte Antwort
            0
            • VJ77V Online
              VJ77V Online
              VJ77
              schrieb am zuletzt editiert von
              #792

              Moin zusammen,

              ich habe meinen ioBroker von einem Windows-PC auf ein RPI umziehen lassen. Leider startet die Roborock-Instanz jetzt gar nicht mehr-
              dcbbdc4d-3e6c-4bf8-8479-4e4239f0f922-grafik.png
              Eine komplette Neuinstallation des Adapters hat leider auch nichts gebracht.

              Hat jemand eine Idee?

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • VJ77V VJ77

                Moin zusammen,

                ich habe meinen ioBroker von einem Windows-PC auf ein RPI umziehen lassen. Leider startet die Roborock-Instanz jetzt gar nicht mehr-
                dcbbdc4d-3e6c-4bf8-8479-4e4239f0f922-grafik.png
                Eine komplette Neuinstallation des Adapters hat leider auch nichts gebracht.

                Hat jemand eine Idee?

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #793

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

                Hat jemand eine Idee?

                Längeres Log posten. Ggfls. im debug modus.
                Und KEINE Screenshots von log-Texten.

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                VJ77V 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

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

                  Hat jemand eine Idee?

                  Längeres Log posten. Ggfls. im debug modus.
                  Und KEINE Screenshots von log-Texten.

                  VJ77V Online
                  VJ77V Online
                  VJ77
                  schrieb am zuletzt editiert von VJ77
                  #794

                  @thomas-braun

                  Danke für die Info mit dem Screenshot. Ich habe sowohl die Roborock-Instanz, als auch den Host auf Debug stehen. Von der Instanz kommen gar keine Meldungen, und vom Host immer wieder die gleichen Meldungen

                  code_text
                  host.iobroker
                  	2025-05-03 07:17:03.485	info	instance system.adapter.sbfspot.0 having pid 2614 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  host.iobroker
                  	2025-05-03 07:17:00.030	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2614
                  host.iobroker
                  	2025-05-03 07:16:53.482	info	Restart adapter system.adapter.roborock.1 because enabled
                  host.iobroker
                  	2025-05-03 07:16:53.482	info	instance system.adapter.roborock.1 terminated with code null ()
                  host.iobroker
                  	2025-05-03 07:16:53.482	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                  host.iobroker
                  	2025-05-03 07:16:52.215	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2585
                  host.iobroker
                  	2025-05-03 07:16:21.390	info	Restart adapter system.adapter.roborock.1 because enabled
                  host.iobroker
                  	2025-05-03 07:16:21.390	info	instance system.adapter.roborock.1 terminated with code null ()
                  host.iobroker
                  	2025-05-03 07:16:21.389	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                  host.iobroker
                  	2025-05-03 07:16:20.160	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2569
                  host.iobroker
                  	2025-05-03 07:16:03.562	info	instance system.adapter.sbfspot.0 having pid 2548 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  host.iobroker
                  	2025-05-03 07:16:00.071	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2548
                  host.iobroker
                  	2025-05-03 07:15:49.373	info	Restart adapter system.adapter.roborock.1 because enabled
                  host.iobroker
                  	2025-05-03 07:15:49.373	info	instance system.adapter.roborock.1 terminated with code null ()
                  host.iobroker
                  	2025-05-03 07:15:49.373	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                  host.iobroker
                  	2025-05-03 07:15:48.134	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2518
                  host.iobroker
                  	2025-05-03 07:15:30.962	info	instance system.adapter.dwd.0 having pid 2501 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  host.iobroker
                  	2025-05-03 07:15:27.035	info	instance system.adapter.dwd.0 in version "2.8.5" started with pid 2501
                  host.iobroker
                  	2025-05-03 07:15:17.314	info	Restart adapter system.adapter.roborock.1 because enabled
                  host.iobroker
                  	2025-05-03 07:15:17.313	info	instance system.adapter.roborock.1 terminated with code null ()
                  host.iobroker
                  	2025-05-03 07:15:17.313	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                  host.iobroker
                  	2025-05-03 07:15:16.108	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2489
                  host.iobroker
                  	2025-05-03 07:15:03.897	info	instance system.adapter.sbfspot.0 having pid 2471 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  host.iobroker
                  	2025-05-03 07:15:00.098	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2471
                  host.iobroker
                  	2025-05-03 07:14:45.117	info	Restart adapter system.adapter.roborock.1 because enabled
                  host.iobroker
                  	2025-05-03 07:14:45.117	info	instance system.adapter.roborock.1 terminated with code null ()
                  host.iobroker
                  	2025-05-03 07:14:45.117	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                  host.iobroker
                  	2025-05-03 07:14:43.904	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2442
                  host.iobroker
                  	2025-05-03 07:14:13.013	info	Restart adapter system.adapter.roborock.1 because enabled
                  
                  U D 2 Antworten Letzte Antwort
                  0
                  • VJ77V VJ77

                    @thomas-braun

                    Danke für die Info mit dem Screenshot. Ich habe sowohl die Roborock-Instanz, als auch den Host auf Debug stehen. Von der Instanz kommen gar keine Meldungen, und vom Host immer wieder die gleichen Meldungen

                    code_text
                    host.iobroker
                    	2025-05-03 07:17:03.485	info	instance system.adapter.sbfspot.0 having pid 2614 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    host.iobroker
                    	2025-05-03 07:17:00.030	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2614
                    host.iobroker
                    	2025-05-03 07:16:53.482	info	Restart adapter system.adapter.roborock.1 because enabled
                    host.iobroker
                    	2025-05-03 07:16:53.482	info	instance system.adapter.roborock.1 terminated with code null ()
                    host.iobroker
                    	2025-05-03 07:16:53.482	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                    host.iobroker
                    	2025-05-03 07:16:52.215	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2585
                    host.iobroker
                    	2025-05-03 07:16:21.390	info	Restart adapter system.adapter.roborock.1 because enabled
                    host.iobroker
                    	2025-05-03 07:16:21.390	info	instance system.adapter.roborock.1 terminated with code null ()
                    host.iobroker
                    	2025-05-03 07:16:21.389	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                    host.iobroker
                    	2025-05-03 07:16:20.160	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2569
                    host.iobroker
                    	2025-05-03 07:16:03.562	info	instance system.adapter.sbfspot.0 having pid 2548 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    host.iobroker
                    	2025-05-03 07:16:00.071	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2548
                    host.iobroker
                    	2025-05-03 07:15:49.373	info	Restart adapter system.adapter.roborock.1 because enabled
                    host.iobroker
                    	2025-05-03 07:15:49.373	info	instance system.adapter.roborock.1 terminated with code null ()
                    host.iobroker
                    	2025-05-03 07:15:49.373	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                    host.iobroker
                    	2025-05-03 07:15:48.134	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2518
                    host.iobroker
                    	2025-05-03 07:15:30.962	info	instance system.adapter.dwd.0 having pid 2501 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    host.iobroker
                    	2025-05-03 07:15:27.035	info	instance system.adapter.dwd.0 in version "2.8.5" started with pid 2501
                    host.iobroker
                    	2025-05-03 07:15:17.314	info	Restart adapter system.adapter.roborock.1 because enabled
                    host.iobroker
                    	2025-05-03 07:15:17.313	info	instance system.adapter.roborock.1 terminated with code null ()
                    host.iobroker
                    	2025-05-03 07:15:17.313	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                    host.iobroker
                    	2025-05-03 07:15:16.108	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2489
                    host.iobroker
                    	2025-05-03 07:15:03.897	info	instance system.adapter.sbfspot.0 having pid 2471 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    host.iobroker
                    	2025-05-03 07:15:00.098	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2471
                    host.iobroker
                    	2025-05-03 07:14:45.117	info	Restart adapter system.adapter.roborock.1 because enabled
                    host.iobroker
                    	2025-05-03 07:14:45.117	info	instance system.adapter.roborock.1 terminated with code null ()
                    host.iobroker
                    	2025-05-03 07:14:45.117	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                    host.iobroker
                    	2025-05-03 07:14:43.904	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2442
                    host.iobroker
                    	2025-05-03 07:14:13.013	info	Restart adapter system.adapter.roborock.1 because enabled
                    
                    U Online
                    U Online
                    uwe72
                    schrieb am zuletzt editiert von uwe72
                    #795

                    @Thomas-Braun
                    Einige Leuten einschließlich mir, bekommen ja diese Fehlermeldung. Gibts hier Ideen woher bzw. warum diese kommen? Dankeschön.

                    borock.0
                    2025-05-04 11:11:49.203	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:11:48.599	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:10:49.009	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:10:48.619	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:09:49.200	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:09:48.575	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:08:49.061	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:08:48.540	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:07:48.846	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:07:48.330	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:06:48.529	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:06:48.281	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:05:48.804	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:05:48.274	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:04:48.696	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:04:48.486	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:03:48.922	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:03:48.387	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:02:48.885	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    2025-05-04 11:02:48.306	error	Failed to process get_status on robot 15BGaiuMta5YcTl8IY1yWx (roborock.vacuum.a70): TypeError: Cannot read properties of undefined (reading 'dss') at requests_handler.getDockingStationStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:184:50) at requests_handler.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:252:43) at requests_handler.getStatus (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:114:4) at /opt/iobroker/node_modules/iobroker.roborock/main.js:104:8
                    
                    roborock.0
                    
                    1 Antwort Letzte Antwort
                    1
                    • VJ77V VJ77

                      @thomas-braun

                      Danke für die Info mit dem Screenshot. Ich habe sowohl die Roborock-Instanz, als auch den Host auf Debug stehen. Von der Instanz kommen gar keine Meldungen, und vom Host immer wieder die gleichen Meldungen

                      code_text
                      host.iobroker
                      	2025-05-03 07:17:03.485	info	instance system.adapter.sbfspot.0 having pid 2614 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      host.iobroker
                      	2025-05-03 07:17:00.030	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2614
                      host.iobroker
                      	2025-05-03 07:16:53.482	info	Restart adapter system.adapter.roborock.1 because enabled
                      host.iobroker
                      	2025-05-03 07:16:53.482	info	instance system.adapter.roborock.1 terminated with code null ()
                      host.iobroker
                      	2025-05-03 07:16:53.482	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                      host.iobroker
                      	2025-05-03 07:16:52.215	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2585
                      host.iobroker
                      	2025-05-03 07:16:21.390	info	Restart adapter system.adapter.roborock.1 because enabled
                      host.iobroker
                      	2025-05-03 07:16:21.390	info	instance system.adapter.roborock.1 terminated with code null ()
                      host.iobroker
                      	2025-05-03 07:16:21.389	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                      host.iobroker
                      	2025-05-03 07:16:20.160	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2569
                      host.iobroker
                      	2025-05-03 07:16:03.562	info	instance system.adapter.sbfspot.0 having pid 2548 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      host.iobroker
                      	2025-05-03 07:16:00.071	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2548
                      host.iobroker
                      	2025-05-03 07:15:49.373	info	Restart adapter system.adapter.roborock.1 because enabled
                      host.iobroker
                      	2025-05-03 07:15:49.373	info	instance system.adapter.roborock.1 terminated with code null ()
                      host.iobroker
                      	2025-05-03 07:15:49.373	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                      host.iobroker
                      	2025-05-03 07:15:48.134	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2518
                      host.iobroker
                      	2025-05-03 07:15:30.962	info	instance system.adapter.dwd.0 having pid 2501 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      host.iobroker
                      	2025-05-03 07:15:27.035	info	instance system.adapter.dwd.0 in version "2.8.5" started with pid 2501
                      host.iobroker
                      	2025-05-03 07:15:17.314	info	Restart adapter system.adapter.roborock.1 because enabled
                      host.iobroker
                      	2025-05-03 07:15:17.313	info	instance system.adapter.roborock.1 terminated with code null ()
                      host.iobroker
                      	2025-05-03 07:15:17.313	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                      host.iobroker
                      	2025-05-03 07:15:16.108	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2489
                      host.iobroker
                      	2025-05-03 07:15:03.897	info	instance system.adapter.sbfspot.0 having pid 2471 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      host.iobroker
                      	2025-05-03 07:15:00.098	info	instance system.adapter.sbfspot.0 in version "4.4.2" started with pid 2471
                      host.iobroker
                      	2025-05-03 07:14:45.117	info	Restart adapter system.adapter.roborock.1 because enabled
                      host.iobroker
                      	2025-05-03 07:14:45.117	info	instance system.adapter.roborock.1 terminated with code null ()
                      host.iobroker
                      	2025-05-03 07:14:45.117	warn	instance system.adapter.roborock.1 terminated due to SIGILL
                      host.iobroker
                      	2025-05-03 07:14:43.904	info	instance system.adapter.roborock.1 in version "0.6.19" started with pid 2442
                      host.iobroker
                      	2025-05-03 07:14:13.013	info	Restart adapter system.adapter.roborock.1 because enabled
                      
                      D Online
                      D Online
                      docsnyder7
                      schrieb am zuletzt editiert von
                      #796

                      @vj77

                      host.evccpi
                      	2025-05-08 12:12:01.585	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:12:01.584	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:12:01.382	info	stopInstance system.adapter.roborock.0 send kill signal
                      host.evccpi
                      	2025-05-08 12:12:01.330	info	stopInstance system.adapter.roborock.0 (force=false, process=true)
                      host.evccpi
                      	2025-05-08 12:12:01.329	info	"system.adapter.roborock.0" disabled
                      host.evccpi
                      	2025-05-08 12:11:59.398	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214464
                      host.evccpi
                      	2025-05-08 12:11:57.925	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:57.925	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:57.924	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:56.195	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214455
                      host.evccpi
                      	2025-05-08 12:11:54.716	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:54.716	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:54.716	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:53.223	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214446
                      host.evccpi
                      	2025-05-08 12:11:51.831	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:51.831	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:51.830	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:50.185	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214437
                      host.evccpi
                      	2025-05-08 12:11:48.715	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:48.715	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:48.714	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:47.174	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214429
                      host.evccpi
                      	2025-05-08 12:11:45.607	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:45.606	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:45.606	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:43.982	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214422
                      host.evccpi
                      	2025-05-08 12:11:42.498	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:42.498	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:42.497	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:40.949	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214415
                      host.evccpi
                      	2025-05-08 12:11:39.442	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:39.441	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:39.441	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:37.963	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214408
                      host.evccpi
                      	2025-05-08 12:11:36.465	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:36.465	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:36.465	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:34.934	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214401
                      host.evccpi
                      	2025-05-08 12:11:33.426	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:33.425	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:33.425	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:31.915	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214394
                      host.evccpi
                      	2025-05-08 12:11:30.433	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:30.432	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:30.432	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:28.950	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214385
                      host.evccpi
                      	2025-05-08 12:11:27.453	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:27.453	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:27.452	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:25.692	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214378
                      host.evccpi
                      	2025-05-08 12:11:24.216	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:24.215	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:24.215	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:22.751	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214370
                      host.evccpi
                      	2025-05-08 12:11:21.188	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:21.187	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:21.187	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:19.574	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214334
                      host.evccpi
                      	2025-05-08 12:11:17.830	info	Restart adapter system.adapter.roborock.0 because enabled
                      host.evccpi
                      	2025-05-08 12:11:17.830	info	instance system.adapter.roborock.0 terminated with code null ()
                      host.evccpi
                      	2025-05-08 12:11:17.829	warn	instance system.adapter.roborock.0 terminated due to SIGILL
                      host.evccpi
                      	2025-05-08 12:11:15.348	info	instance system.adapter.roborock.0 in version "0.6.18" started with pid 214324
                      host.evccpi
                      	2025-05-08 12:11:14.691	info	"system.adapter.roborock.0" enabled
                      

                      jetzt hat es mich erwischt... wollte leichtsinnig auf die 0.6.19 gehen und bekomme den Adapter nicht mehr ans Laufen. Auch ein retour auf die 0.6.18 verändert die Lage nicht.
                      Falls ich mit Daten dienen darf, immer her damit

                      Node.js: v20.19.1
                      NPM: 10.8.2
                      JS: 7.0.6
                      Rpi4 mit aktuellem OS

                      1 Antwort Letzte Antwort
                      1
                      • M Offline
                        M Offline
                        Manolo
                        schrieb am zuletzt editiert von Manolo
                        #797

                        Habe das Problem gefunden.
                        Einmal die App öffnen und die neuen Datenschutzrichtlinien akzeptieren, dann wird auch der Adapter wieder grün.
                        Da haben die von Roborock aber nen bösen Fallstrick eingebaut...

                        ioBroker auf Beelink J45, Slave auf Beelink BT3pro, Unifi Controller auf Raspi Pi 3; 4x VIS Fully Browser auf 10" und 7" Tablet; piVCCU auf 2x Raspi Pi 3 Redundanzsystem, ca. 50 HM-Geräte; Unifi USG, Switch, AP-AC-LR

                        D 1 Antwort Letzte Antwort
                        0
                        • M Manolo

                          Habe das Problem gefunden.
                          Einmal die App öffnen und die neuen Datenschutzrichtlinien akzeptieren, dann wird auch der Adapter wieder grün.
                          Da haben die von Roborock aber nen bösen Fallstrick eingebaut...

                          D Online
                          D Online
                          docsnyder7
                          schrieb am zuletzt editiert von docsnyder7
                          #798

                          @manolo Danke für den Tip!
                          Hat bei mir leider keinen Erfolg...
                          was bedeutet der Warneintrag "SIGILL" im Log?

                          Thomas BraunT M 2 Antworten Letzte Antwort
                          0
                          • D docsnyder7

                            @manolo Danke für den Tip!
                            Hat bei mir leider keinen Erfolg...
                            was bedeutet der Warneintrag "SIGILL" im Log?

                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von Thomas Braun
                            #799

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

                            SIGILL

                            Ist ein SIGnal einer ILLegalen Anweisung.

                            https://dsa.cs.tsinghua.edu.cn/oj/static/unix_signal.html

                            Linux-Werkzeugkasten:
                            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                            NodeJS Fixer Skript:
                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                            D 1 Antwort Letzte Antwort
                            1
                            • Thomas BraunT Thomas Braun

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

                              SIGILL

                              Ist ein SIGnal einer ILLegalen Anweisung.

                              https://dsa.cs.tsinghua.edu.cn/oj/static/unix_signal.html

                              D Online
                              D Online
                              docsnyder7
                              schrieb am zuletzt editiert von
                              #800

                              @thomas-braun kann das mit den Datenschutzgeschichte zu tun haben?

                              Thomas BraunT VJ77V 3 Antworten Letzte Antwort
                              0
                              • D docsnyder7

                                @thomas-braun kann das mit den Datenschutzgeschichte zu tun haben?

                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von
                                #801

                                @docsnyder7

                                Möglich.

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                1 Antwort Letzte Antwort
                                1
                                • D docsnyder7

                                  @thomas-braun kann das mit den Datenschutzgeschichte zu tun haben?

                                  VJ77V Online
                                  VJ77V Online
                                  VJ77
                                  schrieb am zuletzt editiert von
                                  #802

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

                                  @thomas-braun kann das mit den Datenschutzgeschichte zu tun haben?

                                  glaube ich nicht. Zum einen startet der Adapter ja im Grunde überhaupt nicht, Zum anderen kann ich bei mir auf dem Windows-System problemlos den Adapter starten. Nur auf meinem RPI geht es nicht.

                                  1 Antwort Letzte Antwort
                                  1
                                  • D docsnyder7

                                    @thomas-braun kann das mit den Datenschutzgeschichte zu tun haben?

                                    VJ77V Online
                                    VJ77V Online
                                    VJ77
                                    schrieb am zuletzt editiert von
                                    #803

                                    @docsnyder7 schau mal hier: https://github.com/copystring/ioBroker.roborock/issues/815

                                    1 Antwort Letzte Antwort
                                    1
                                    • copystringC Offline
                                      copystringC Offline
                                      copystring
                                      schrieb am zuletzt editiert von
                                      #804

                                      RPIs haben schon immer Probleme mit der canvas-Bibliothek gemach. Deshalb habe zu napi-rs/canvas-Bibliothek gewechselt. Die läuft deutlich besser, hat aber aktuell im Version 0.1.69 und 0.1.70 einen Fehler auf RPi4.

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

                                      VJ77V 1 Antwort Letzte Antwort
                                      1
                                      • D docsnyder7

                                        @manolo Danke für den Tip!
                                        Hat bei mir leider keinen Erfolg...
                                        was bedeutet der Warneintrag "SIGILL" im Log?

                                        M Offline
                                        M Offline
                                        Manolo
                                        schrieb am zuletzt editiert von
                                        #805

                                        @docsnyder7
                                        Hat bei mir auch nur mit der stable 0.6.18 funktioniert.
                                        Bei der 0.6.19 Version geht die Instanz auch wieder in Stopp.

                                        ioBroker auf Beelink J45, Slave auf Beelink BT3pro, Unifi Controller auf Raspi Pi 3; 4x VIS Fully Browser auf 10" und 7" Tablet; piVCCU auf 2x Raspi Pi 3 Redundanzsystem, ca. 50 HM-Geräte; Unifi USG, Switch, AP-AC-LR

                                        D 1 Antwort Letzte Antwort
                                        1
                                        • copystringC copystring

                                          RPIs haben schon immer Probleme mit der canvas-Bibliothek gemach. Deshalb habe zu napi-rs/canvas-Bibliothek gewechselt. Die läuft deutlich besser, hat aber aktuell im Version 0.1.69 und 0.1.70 einen Fehler auf RPi4.

                                          VJ77V Online
                                          VJ77V Online
                                          VJ77
                                          schrieb am zuletzt editiert von
                                          #806

                                          @copystring ich warte einfach mal ab und hoffe, dass das Problem sich von alleine erledigt :blush:

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


                                          Support us

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

                                          463

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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