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

donate donate
  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.5k

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

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

Neuer Adapter für Roborock-Staubsauger

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
925 Beiträge 137 Kommentatoren 326.0k Aufrufe 126 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.
  • D DarkDevil

    @copystring und ich glaube das das aktualisieren beim reinigen nicht funktioniert, sondern nur beim starten des Adapters.

    copystringC Offline
    copystringC Offline
    copystring
    schrieb am zuletzt editiert von
    #392

    @darkdevil ja, der Fehler ist der dev behoben. Es dauert leider noch ein bisschen, bis ein neuer Release kommt. Ich brauche noch Tester von der dev auf GitHub.

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

    da_WoodyD 2 Antworten Letzte Antwort
    0
    • copystringC copystring

      @darkdevil ja, der Fehler ist der dev behoben. Es dauert leider noch ein bisschen, bis ein neuer Release kommt. Ich brauche noch Tester von der dev auf GitHub.

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

      @copystring OK, also über die Katze insten. Bin ja gerne dabei...

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

      1 Antwort Letzte Antwort
      1
      • copystringC copystring

        @flexer das ginge schon aber die Position der Karte kann sich immer Mal ändern und dann müsstest du jedes Mal deine Zeichnung anpassen.

        FlexerF Offline
        FlexerF Offline
        Flexer
        schrieb am zuletzt editiert von
        #394

        @copystring Was müsste ich denn dafür tun damit ich das mal ausprobieren könnte? Karte ist bei mir fast immer an der gleichen position. Müsste klappen

        Unterm Strich ist alles besser.


        Ja, voll geil hier!

        copystringC 1 Antwort Letzte Antwort
        0
        • FlexerF Flexer

          @copystring Was müsste ich denn dafür tun damit ich das mal ausprobieren könnte? Karte ist bei mir fast immer an der gleichen position. Müsste klappen

          copystringC Offline
          copystringC Offline
          copystring
          schrieb am zuletzt editiert von copystring
          #395

          @flexer du müsstest aus der mapCreator.js alles entfernen, was nicht gezeichnet werden soll.

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

          FlexerF 1 Antwort Letzte Antwort
          0
          • copystringC copystring

            @flexer du müsstest aus der mapCreator.js alles entfernen, was nicht gezeichnet werden soll.

            FlexerF Offline
            FlexerF Offline
            Flexer
            schrieb am zuletzt editiert von
            #396

            @copystring OK schau ich mir mal an

            Unterm Strich ist alles besser.


            Ja, voll geil hier!

            1 Antwort Letzte Antwort
            0
            • copystringC copystring

              @darkdevil ja, der Fehler ist der dev behoben. Es dauert leider noch ein bisschen, bis ein neuer Release kommt. Ich brauche noch Tester von der dev auf GitHub.

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

              @copystring oi, hab ich den deppensonntag erwischt?
              hab jetzt schon einige versuche gemacht. bin aber noch immer auf der 0.4.4
              einfach zu dämlich auf die 0.5.1 zu kommen...

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

              copystringC 1 Antwort Letzte Antwort
              0
              • da_WoodyD da_Woody

                @copystring oi, hab ich den deppensonntag erwischt?
                hab jetzt schon einige versuche gemacht. bin aber noch immer auf der 0.4.4
                einfach zu dämlich auf die 0.5.1 zu kommen...

                copystringC Offline
                copystringC Offline
                copystring
                schrieb am zuletzt editiert von
                #398

                @da_woody den Release von 0.5.1 habe ich zurückgenommen weil dieser zu viele Fehler hatte. Es gibt nur 0.4.4 oder die dev auf GitHub.

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

                da_WoodyD 1 Antwort Letzte Antwort
                0
                • da_WoodyD Offline
                  da_WoodyD Offline
                  da_Woody
                  schrieb am zuletzt editiert von
                  #399

                  @copystring dann kann ich lange probieren, angezeigt wirds aber als l8est...
                  bin aber zu dämlich die dev zu insten. tritt in den allerwärtesten wäre nötig.

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

                  jahnbesJ 1 Antwort Letzte Antwort
                  0
                  • da_WoodyD da_Woody

                    @copystring dann kann ich lange probieren, angezeigt wirds aber als l8est...
                    bin aber zu dämlich die dev zu insten. tritt in den allerwärtesten wäre nötig.

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

                    Hallo @da_woody
                    falls es darum geht, wie die dev zu installieren ist, hier das how_to:
                    robo_dev_installieren.jpg
                    Die DEV Branch installierst Du, wie im obigen Screenshot angedeutet:
                    • iobroker aufrufen
                    • auf [Adapter] gehen
                    • Handling auf [Admin] setzen (1)
                    • [Github] einstellen (2)
                    • [benutzerdefinierte] Installation aufrufen (3)
                    • DEV Branch link eintragen (4)
                    • Naja, und zum Schluß auf [Installieren] drücken
                    Den DEV Branch link findest Du:
                    https://github.com/copystring/ioBroker.roborock/tree/dev

                    da_WoodyD 1 Antwort Letzte Antwort
                    0
                    • jahnbesJ jahnbes

                      Hallo @da_woody
                      falls es darum geht, wie die dev zu installieren ist, hier das how_to:
                      robo_dev_installieren.jpg
                      Die DEV Branch installierst Du, wie im obigen Screenshot angedeutet:
                      • iobroker aufrufen
                      • auf [Adapter] gehen
                      • Handling auf [Admin] setzen (1)
                      • [Github] einstellen (2)
                      • [benutzerdefinierte] Installation aufrufen (3)
                      • DEV Branch link eintragen (4)
                      • Naja, und zum Schluß auf [Installieren] drücken
                      Den DEV Branch link findest Du:
                      https://github.com/copystring/ioBroker.roborock/tree/dev

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

                      @jahnbes :+1: ich dödel bin am dev link gescheitert...
                      be6c3f7c-7a9e-4872-a142-dcb3610092e0-grafik.png

                      werd berichten. danke.gif

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

                      1 Antwort Letzte Antwort
                      0
                      • copystringC copystring

                        @da_woody den Release von 0.5.1 habe ich zurückgenommen weil dieser zu viele Fehler hatte. Es gibt nur 0.4.4 oder die dev auf GitHub.

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

                        @copystring zo, mal den typen losgejagt. update der karte klappt mal! banane2.gif
                        durch die neue struktur gewuselt.
                        wie kann ich goto fixieren? im xiaomi hatte ich das mal, irgendwann dann nicht mehr... (ich glaub, ich hab das damals in den objekten eingetragen)
                        wie kann ich roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.deviceStatus.error_code auswerten, damit ich nur den error(8) (hängen geblieben) anzeigen kann?

                        meine kleinen probleme in iQontrol:
                        mir ist die map zu klein. witziger weise ist die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64Truncated gößer als die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64
                        klappt dafür aber in FF und chrome ohne scrolleisten. bewusst mal den background eingeblendet:
                        b56effce-d9ef-4801-a45b-9a5f96ade28c-grafik.png
                        verkleinern kann ich.

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

                        copystringC 1 Antwort Letzte Antwort
                        0
                        • da_WoodyD da_Woody

                          @copystring zo, mal den typen losgejagt. update der karte klappt mal! banane2.gif
                          durch die neue struktur gewuselt.
                          wie kann ich goto fixieren? im xiaomi hatte ich das mal, irgendwann dann nicht mehr... (ich glaub, ich hab das damals in den objekten eingetragen)
                          wie kann ich roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.deviceStatus.error_code auswerten, damit ich nur den error(8) (hängen geblieben) anzeigen kann?

                          meine kleinen probleme in iQontrol:
                          mir ist die map zu klein. witziger weise ist die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64Truncated gößer als die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64
                          klappt dafür aber in FF und chrome ohne scrolleisten. bewusst mal den background eingeblendet:
                          b56effce-d9ef-4801-a45b-9a5f96ade28c-grafik.png
                          verkleinern kann ich.

                          copystringC Offline
                          copystringC Offline
                          copystring
                          schrieb am zuletzt editiert von
                          #403

                          @da_woody said in Neuer Adapter für Roborock-Staubsauger:

                          wie kann ich goto fixieren? im xiaomi hatte ich das mal, irgendwann dann nicht mehr... (ich glaub, ich hab das damals in den objekten eingetragen)

                          Was meinst du damit?

                          @da_woody said in Neuer Adapter für Roborock-Staubsauger:

                          wie kann ich roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.deviceStatus.error_code auswerten, damit ich nur den error(8) (hängen geblieben) anzeigen kann?

                          Dafür müsstest du dir ein Script schreiben.

                          @da_woody said in Neuer Adapter für Roborock-Staubsauger:

                          witziger weise ist die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64Truncated gößer als die

                          Natürlich, weil die alle Ränder entfernt sind.

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

                          da_WoodyD 1 Antwort Letzte Antwort
                          0
                          • T Offline
                            T Offline
                            tritanium
                            schrieb am zuletzt editiert von
                            #404

                            Also ich habe keine Ahnung mehr welche Version ich probieren soll....

                            Mit der stable 0.4.4, funktioniert der Adapter zwar, schmeisst aber etliche Fehler:

                            oborock.0
                               2024-01-14 20:57:18.551	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 5681 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:57:15.011	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7884 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:57:13.418	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2698 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:57:10.253	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5909 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:57:08.128	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:57:08.052	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:57:03.410	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:57:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1082 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:58.439	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 4253 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:55.018	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7890 timed out after 10 seconds for response.102
                            knx.0
                               2024-01-14 20:56:54.253	info	State value to set for "knx.0.Licht.Erdgeschoss.LEDSpots_Küche_HSV_Dimmwert" has to be one of type "string", "number", "boolean" but received type "object"
                            roborock.0
                               2024-01-14 20:56:53.121	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:56:53.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:56:48.430	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2630 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:45.009	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8986 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:40.229	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 6033 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:38.114	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:56:38.047	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:56:33.533	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9299 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:30.222	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5724 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:28.365	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:25.029	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8772 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:23.111	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:56:23.028	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:56:18.358	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1989 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:15.020	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7488 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:13.505	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 7258 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:10.254	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1712 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:08.136	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:56:08.064	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:56:03.496	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1005 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:56:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8210 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:55.022	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4104 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:53.106	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:55:53.059	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:55:48.441	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 3081 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:45.013	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8080 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:39.996	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4227 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:38.152	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:55:38.079	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                            roborock.0
                               2024-01-14 20:55:29.987	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1750 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:25.007	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 9715 timed out after 10 seconds for response.102
                            roborock.0
                               2024-01-14 20:55:23.116	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                            roborock.0
                               2024-01-14 20:55:23.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev t
                            

                            Die aktuelle /dev (vor 5 Minuten aktualisiert) schemisst auch nur noch Fehler raus und startet in einer loop neu...:

                            host.iobroker
                               2024-01-14 20:41:44.145	info	Restart adapter system.adapter.roborock.0 because enabled
                            host.iobroker
                               2024-01-14 20:41:44.145	info	instance system.adapter.roborock.0 terminated with code 0 (NO_ERROR)
                            host.iobroker
                               2024-01-14 20:41:44.145	error	Caught by controller[7]: at TCP.<anonymous> (node:net:323:12)
                            host.iobroker
                               2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:domain:489:12)
                            host.iobroker
                               2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:events:514:28)
                            host.iobroker
                               2024-01-14 20:41:44.145	error	Caught by controller[7]: at Object.onceWrapper (node:events:629:26)
                            host.iobroker
                               2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[7]: Error: Connection is closed.
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[6]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at TCP.<anonymous> (node:net:323:12)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:domain:489:12)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:events:514:28)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at Object.onceWrapper (node:events:629:26)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                            host.iobroker
                               2024-01-14 20:41:44.144	error	Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[5]: Error: Connection is closed.
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at TCP.<anonymous> (node:net:323:12)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:domain:489:12)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:events:514:28)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at Object.onceWrapper (node:events:629:26)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                            host.iobroker
                               2024-01-14 20:41:44.143	error	Caught by controller[3]: Error: Connection is closed.
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at TCP.<anonymous> (node:net:323:12)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:events:514:28)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at Object.onceWrapper (node:events:629:26)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                            host.iobroker
                               2024-01-14 20:41:44.142	error	Caught by controller[1]: Error: Connection is closed.
                            host.iobroker
                               2024-01-14 20:41:44.141	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                            roborock.0
                               2024-01-14 20:41:43.853	info	terminating
                            roborock.0
                               2024-01-14 20:41:43.393	info	Terminated (NO_ERROR): Without reason
                            roborock.0
                               2024-01-14 20:41:43.391	info	terminating
                            roborock.0
                               2024-01-14 20:41:43.339	warn	Restart initiated
                            roborock.0
                               2024-01-14 20:41:43.243	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:43.121	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:42.121	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:41.979	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:40.979	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:40.821	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:39.821	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:39.679	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:38.679	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:38.568	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:37.567	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:37.451	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:36.451	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:36.347	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:35.347	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:35.226	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:34.225	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:34.086	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:33.086	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:32.975	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:31.974	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:31.859	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:30.858	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:30.730	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:29.730	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:29.617	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:28.616	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:28.447	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:27.448	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:27.319	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:26.318	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:26.192	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:25.192	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:25.072	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:24.072	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:23.959	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:22.959	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:22.833	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:21.833	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:21.706	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:20.706	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:20.595	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:19.595	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:19.482	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:18.482	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:18.341	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:17.341	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:17.207	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:16.207	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:16.087	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:15.086	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:14.962	warn	MQTT connection reconnect.
                            roborock.0
                               2024-01-14 20:41:13.962	warn	MQTT connection close.
                            roborock.0
                               2024-01-14 20:41:13.338	info	MQTT initialized
                            roborock.0
                               2024-01-14 20:41:07.232	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
                            roborock.0
                               2024-01-14 20:41:07.178	info	starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
                            host.iobroker
                               2024-01-14 20:41:02.286	info	instance system.adapter.roborock.0 started with pid 1519525
                            host.iobroker
                               2024-01-14 20:41:01.775	info	"system.adapter.roborock.0" enabled
                            

                            Aufgrund dessen habe ich den Adapter erst mal "deaktivert". Wie macht ihr das?

                            Funktionieren bei euch die Roboter? Ich habe 2 dran (Q7 Max+ & Q Revo).

                            Danke für eure Hilfe :-)

                            copystringC 1 Antwort Letzte Antwort
                            0
                            • T tritanium

                              Also ich habe keine Ahnung mehr welche Version ich probieren soll....

                              Mit der stable 0.4.4, funktioniert der Adapter zwar, schmeisst aber etliche Fehler:

                              oborock.0
                                 2024-01-14 20:57:18.551	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 5681 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:57:15.011	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7884 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:57:13.418	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2698 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:57:10.253	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5909 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:57:08.128	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:57:08.052	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:57:03.410	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:57:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1082 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:58.439	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 4253 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:55.018	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7890 timed out after 10 seconds for response.102
                              knx.0
                                 2024-01-14 20:56:54.253	info	State value to set for "knx.0.Licht.Erdgeschoss.LEDSpots_Küche_HSV_Dimmwert" has to be one of type "string", "number", "boolean" but received type "object"
                              roborock.0
                                 2024-01-14 20:56:53.121	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:56:53.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:56:48.430	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2630 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:45.009	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8986 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:40.229	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 6033 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:38.114	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:56:38.047	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:56:33.533	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9299 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:30.222	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5724 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:28.365	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:25.029	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8772 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:23.111	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:56:23.028	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:56:18.358	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1989 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:15.020	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7488 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:13.505	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 7258 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:10.254	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1712 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:08.136	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:56:08.064	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:56:03.496	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1005 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:56:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8210 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:55.022	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4104 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:53.106	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:55:53.059	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:55:48.441	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 3081 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:45.013	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8080 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:39.996	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4227 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:38.152	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:55:38.079	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
                              roborock.0
                                 2024-01-14 20:55:29.987	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1750 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:25.007	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 9715 timed out after 10 seconds for response.102
                              roborock.0
                                 2024-01-14 20:55:23.116	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
                              roborock.0
                                 2024-01-14 20:55:23.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev t
                              

                              Die aktuelle /dev (vor 5 Minuten aktualisiert) schemisst auch nur noch Fehler raus und startet in einer loop neu...:

                              host.iobroker
                                 2024-01-14 20:41:44.145	info	Restart adapter system.adapter.roborock.0 because enabled
                              host.iobroker
                                 2024-01-14 20:41:44.145	info	instance system.adapter.roborock.0 terminated with code 0 (NO_ERROR)
                              host.iobroker
                                 2024-01-14 20:41:44.145	error	Caught by controller[7]: at TCP.<anonymous> (node:net:323:12)
                              host.iobroker
                                 2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:domain:489:12)
                              host.iobroker
                                 2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:events:514:28)
                              host.iobroker
                                 2024-01-14 20:41:44.145	error	Caught by controller[7]: at Object.onceWrapper (node:events:629:26)
                              host.iobroker
                                 2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[7]: Error: Connection is closed.
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[6]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at TCP.<anonymous> (node:net:323:12)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:domain:489:12)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:events:514:28)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at Object.onceWrapper (node:events:629:26)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                              host.iobroker
                                 2024-01-14 20:41:44.144	error	Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[5]: Error: Connection is closed.
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at TCP.<anonymous> (node:net:323:12)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:domain:489:12)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:events:514:28)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at Object.onceWrapper (node:events:629:26)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                              host.iobroker
                                 2024-01-14 20:41:44.143	error	Caught by controller[3]: Error: Connection is closed.
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at TCP.<anonymous> (node:net:323:12)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:events:514:28)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at Object.onceWrapper (node:events:629:26)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                              host.iobroker
                                 2024-01-14 20:41:44.142	error	Caught by controller[1]: Error: Connection is closed.
                              host.iobroker
                                 2024-01-14 20:41:44.141	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                              roborock.0
                                 2024-01-14 20:41:43.853	info	terminating
                              roborock.0
                                 2024-01-14 20:41:43.393	info	Terminated (NO_ERROR): Without reason
                              roborock.0
                                 2024-01-14 20:41:43.391	info	terminating
                              roborock.0
                                 2024-01-14 20:41:43.339	warn	Restart initiated
                              roborock.0
                                 2024-01-14 20:41:43.243	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:43.121	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:42.121	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:41.979	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:40.979	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:40.821	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:39.821	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:39.679	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:38.679	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:38.568	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:37.567	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:37.451	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:36.451	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:36.347	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:35.347	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:35.226	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:34.225	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:34.086	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:33.086	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:32.975	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:31.974	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:31.859	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:30.858	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:30.730	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:29.730	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:29.617	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:28.616	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:28.447	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:27.448	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:27.319	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:26.318	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:26.192	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:25.192	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:25.072	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:24.072	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:23.959	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:22.959	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:22.833	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:21.833	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:21.706	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:20.706	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:20.595	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:19.595	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:19.482	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:18.482	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:18.341	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:17.341	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:17.207	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:16.207	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:16.087	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:15.086	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:14.962	warn	MQTT connection reconnect.
                              roborock.0
                                 2024-01-14 20:41:13.962	warn	MQTT connection close.
                              roborock.0
                                 2024-01-14 20:41:13.338	info	MQTT initialized
                              roborock.0
                                 2024-01-14 20:41:07.232	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
                              roborock.0
                                 2024-01-14 20:41:07.178	info	starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
                              host.iobroker
                                 2024-01-14 20:41:02.286	info	instance system.adapter.roborock.0 started with pid 1519525
                              host.iobroker
                                 2024-01-14 20:41:01.775	info	"system.adapter.roborock.0" enabled
                              

                              Aufgrund dessen habe ich den Adapter erst mal "deaktivert". Wie macht ihr das?

                              Funktionieren bei euch die Roboter? Ich habe 2 dran (Q7 Max+ & Q Revo).

                              Danke für eure Hilfe :-)

                              copystringC Offline
                              copystringC Offline
                              copystring
                              schrieb am zuletzt editiert von
                              #405

                              @tritanium lösch Mal dein UserData und starte den Adapter neu.

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

                              T 2 Antworten Letzte Antwort
                              0
                              • copystringC copystring

                                @tritanium lösch Mal dein UserData und starte den Adapter neu.

                                T Offline
                                T Offline
                                tritanium
                                schrieb am zuletzt editiert von
                                #406

                                @copystring

                                Du meinst im Adapter Benutzername/Passwort ?? ....oder die Datenpunkte unter den Objekten ??

                                Mit welcher Version soll ich das machen ... stable oder /dev ??

                                1 Antwort Letzte Antwort
                                0
                                • copystringC copystring

                                  @tritanium lösch Mal dein UserData und starte den Adapter neu.

                                  T Offline
                                  T Offline
                                  tritanium
                                  schrieb am zuletzt editiert von
                                  #407

                                  @copystring

                                  Okay, folgend verfahren :-)

                                  1. aktuelle /dev "gerade eben" installiert.
                                  2. Alle Objekte undter "roborock.0" gelöscht
                                  3. Adapter gestartet.

                                  -> Sieht schon besser aus, jedenfalls kommt kein crash bzw. restart mehr ... :-)

                                  Nur noch die hier:

                                  roborock.0
                                     2024-01-14 21:20:21.553	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.19.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:18.942	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.18.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:16.829	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.17.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:14.711	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.16.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:12.283	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.15.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:10.153	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:08.024	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.13.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:05.826	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.12.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:03.337	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.11.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:20:01.058	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.10.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:58.918	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.9.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:56.988	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.8.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:54.802	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.7.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:52.713	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.6.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:50.432	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.5.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:48.282	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.4.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:47.373	warn	Failed to execute get_status on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
                                  roborock.0
                                     2024-01-14 21:19:45.473	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.3.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:43.123	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.2.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:40.852	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.1.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:19:38.588	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.0.map_flag" has no existing object, this might lead to an error in future versions
                                  roborock.0
                                     2024-01-14 21:17:16.350	info	MQTT initialized
                                  

                                  Ich denke aber, damit kann/muss ich wohl derzeit leben :-)

                                  Dann beobachte ich nun erst einmal weiter ....

                                  Danke für den "anschubser" ....

                                  copystringC T 2 Antworten Letzte Antwort
                                  0
                                  • T tritanium

                                    @copystring

                                    Okay, folgend verfahren :-)

                                    1. aktuelle /dev "gerade eben" installiert.
                                    2. Alle Objekte undter "roborock.0" gelöscht
                                    3. Adapter gestartet.

                                    -> Sieht schon besser aus, jedenfalls kommt kein crash bzw. restart mehr ... :-)

                                    Nur noch die hier:

                                    roborock.0
                                       2024-01-14 21:20:21.553	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.19.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:18.942	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.18.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:16.829	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.17.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:14.711	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.16.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:12.283	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.15.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:10.153	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:08.024	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.13.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:05.826	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.12.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:03.337	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.11.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:20:01.058	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.10.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:58.918	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.9.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:56.988	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.8.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:54.802	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.7.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:52.713	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.6.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:50.432	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.5.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:48.282	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.4.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:47.373	warn	Failed to execute get_status on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
                                    roborock.0
                                       2024-01-14 21:19:45.473	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.3.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:43.123	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.2.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:40.852	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.1.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:19:38.588	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.0.map_flag" has no existing object, this might lead to an error in future versions
                                    roborock.0
                                       2024-01-14 21:17:16.350	info	MQTT initialized
                                    

                                    Ich denke aber, damit kann/muss ich wohl derzeit leben :-)

                                    Dann beobachte ich nun erst einmal weiter ....

                                    Danke für den "anschubser" ....

                                    copystringC Offline
                                    copystringC Offline
                                    copystring
                                    schrieb am zuletzt editiert von
                                    #408

                                    @tritanium Für den Fehler erstellt bitte ein Issue auf GitHub mit Debuglog. Dann kann ich das auch noch lösen.

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

                                    T 1 Antwort Letzte Antwort
                                    0
                                    • T tritanium

                                      @copystring

                                      Okay, folgend verfahren :-)

                                      1. aktuelle /dev "gerade eben" installiert.
                                      2. Alle Objekte undter "roborock.0" gelöscht
                                      3. Adapter gestartet.

                                      -> Sieht schon besser aus, jedenfalls kommt kein crash bzw. restart mehr ... :-)

                                      Nur noch die hier:

                                      roborock.0
                                         2024-01-14 21:20:21.553	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.19.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:18.942	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.18.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:16.829	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.17.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:14.711	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.16.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:12.283	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.15.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:10.153	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:08.024	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.13.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:05.826	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.12.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:03.337	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.11.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:20:01.058	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.10.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:58.918	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.9.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:56.988	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.8.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:54.802	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.7.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:52.713	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.6.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:50.432	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.5.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:48.282	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.4.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:47.373	warn	Failed to execute get_status on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
                                      roborock.0
                                         2024-01-14 21:19:45.473	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.3.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:43.123	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.2.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:40.852	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.1.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:19:38.588	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.0.map_flag" has no existing object, this might lead to an error in future versions
                                      roborock.0
                                         2024-01-14 21:17:16.350	info	MQTT initialized
                                      

                                      Ich denke aber, damit kann/muss ich wohl derzeit leben :-)

                                      Dann beobachte ich nun erst einmal weiter ....

                                      Danke für den "anschubser" ....

                                      T Offline
                                      T Offline
                                      tritanium
                                      schrieb am zuletzt editiert von
                                      #409

                                      hmm, okay, nach durchsicht aller neu angelegten Objekte fiel mir der hier auf:

                                      56e722fd-c5e6-406c-b353-bd9e6b5ed8e3-grafik.png

                                      Ich denke der war auch gemeint , oder ??

                                      Nun gut, jetzt läufts ja erst einmal wieder... Ich bin aber auch ein Schussel :rolling_on_the_floor_laughing:

                                      copystringC 1 Antwort Letzte Antwort
                                      0
                                      • T tritanium

                                        hmm, okay, nach durchsicht aller neu angelegten Objekte fiel mir der hier auf:

                                        56e722fd-c5e6-406c-b353-bd9e6b5ed8e3-grafik.png

                                        Ich denke der war auch gemeint , oder ??

                                        Nun gut, jetzt läufts ja erst einmal wieder... Ich bin aber auch ein Schussel :rolling_on_the_floor_laughing:

                                        copystringC Offline
                                        copystringC Offline
                                        copystring
                                        schrieb am zuletzt editiert von
                                        #410

                                        @tritanium said in Neuer Adapter für Roborock-Staubsauger:

                                        Ich denke der war auch gemeint , oder ??

                                        Ja, genau das meinte ich.

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

                                        1 Antwort Letzte Antwort
                                        0
                                        • copystringC copystring

                                          @tritanium Für den Fehler erstellt bitte ein Issue auf GitHub mit Debuglog. Dann kann ich das auch noch lösen.

                                          T Offline
                                          T Offline
                                          tritanium
                                          schrieb am zuletzt editiert von
                                          #411

                                          @copystring

                                          Ich schaue mir das mal an, den DP den das LOG anmäkelt, habe ich unter den Objekten...

                                          -> Ich lasse glecih mal einen saugen und gucke was sich tut....

                                          Aber mal was anderes:

                                          Nachdem der Adapter nun vermeindlich sauber funktioniert, hat mich die App gerade darauf hingewiesen, das mein Konto "auf einem anderen Gerät angemeldet ist"

                                          -> Ignorier ich das, oder was soll mir das sagen ....??

                                          Meine Frau hat die Appa auch installiert und nutzt diese, aber da kam keine solche Meldung....

                                          Bin ratlos

                                          copystringC 1 Antwort Letzte Antwort
                                          0
                                          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

                                          483

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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