Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Mihome-vacuum v3.1.6 Next Generarition

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    369

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    4.9k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.3k

Test Adapter Mihome-vacuum v3.1.6 Next Generarition

Scheduled Pinned Locked Moved Tester
1.2k Posts 100 Posters 408.3k Views 82 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • bahnuhrB bahnuhr

    @meistertr
    beim start der Instanz kommt sowas:

    mihome-vacuum.0
    2021-12-31 17:27:06.759	warn	{"statusCode":401,"body":"{\"code\":0,\"message\":\"auth err\"}","headers":{"server":"Tengine","date":"Fri, 31 Dec 2021 16:27:06 GMT","content-type":"text/plain; charset=utf-8","content-length":"31","connection":"close"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"de.api.io.mi.com","port":443,"hostname":"de.api.io.mi.com","hash":null,"search":null,"query":null,"pathname":"/app/home/getmapfileurl","path":"/app/home/getmapfileurl","href":"https://de.api.io.mi.com/app/home/getmapfileurl"},"method":"POST","headers":{"Content-Type":"application/x-www-form-urlencoded","x-xiaomi-protocal-flag-cli":"PROTOCAL-HTTP2","User-Agent":"Android-7.1.1-1.0.0-ONEPLUS A3010-136-9D28921C354D7 APP/xiaomi.smarthome APPV/62830","Cookie":"userId=1859580730; yetAnotherServiceToken=2jLptLTZl7Nib6yuI/b1+UavFv5+fTOMjdVL37UnxpvkV8RbwV9Cl9G8JDh+ISJWCrmHH1MH4RrOcUQ9rlQ1FiYv80gC4/VcNOs/tQYscg6lCCg=; serviceToken=2jLptLTZl7Nib6yuI/vtJPaXNiw51djOdZYAZO38Yd7qV137UnxpvkV8RbwV9Cl9G8JDh+ISJWCrmHH1MH4RrOcUQ9rlQ1FiYv80gC4/VcNOs/tQYscg6lCCg=; locale=de_DE; timezone=GMT%2B01%3A00; is_daylight=1; dst_offset=3600000; channel=MI_APP_STORE","accept-encoding":"gzip, deflate","content-length":148}}}
    

    (habe die token etwas gekürzt)

    JB_SullivanJ Offline
    JB_SullivanJ Offline
    JB_Sullivan
    wrote on last edited by JB_Sullivan
    #454

    @bahnuhr sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:

    @meistertr
    beim start der Instanz kommt sowas:

    mihome-vacuum.0
    2021-12-31 17:27:06.759	warn	{"statusCode":401,"body":"{\"code\":0,\"message\":\"auth err\"}","headers":{"server":"Tengine","date":"Fri, 31 Dec 2021 16:27:06 GMT","content-type":"text/plain; charset=utf-8","content-length":"31","connection":"close"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"de.api.io.mi.com","port":443,"hostname":"de.api.io.mi.com","hash":null,"search":null,"query":null,"pathname":"/app/home/getmapfileurl","path":"/app/home/getmapfileurl","href":"https://de.api.io.mi.com/app/home/getmapfileurl"},"method":"POST","headers":{"Content-Type":"application/x-www-form-urlencoded","x-xiaomi-protocal-flag-cli":"PROTOCAL-HTTP2","User-Agent":"Android-7.1.1-1.0.0-ONEPLUS A3010-136-9D28921C354D7 APP/xiaomi.smarthome APPV/62830","Cookie":"userId=1859580730; yetAnotherServiceToken=2jLptLTZl7Nib6yuI/b1+UavFv5+fTOMjdVL37UnxpvkV8RbwV9Cl9G8JDh+ISJWCrmHH1MH4RrOcUQ9rlQ1FiYv80gC4/VcNOs/tQYscg6lCCg=; serviceToken=2jLptLTZl7Nib6yuI/vtJPaXNiw51djOdZYAZO38Yd7qV137UnxpvkV8RbwV9Cl9G8JDh+ISJWCrmHH1MH4RrOcUQ9rlQ1FiYv80gC4/VcNOs/tQYscg6lCCg=; locale=de_DE; timezone=GMT%2B01%3A00; is_daylight=1; dst_offset=3600000; channel=MI_APP_STORE","accept-encoding":"gzip, deflate","content-length":148}}}
    

    (habe die token etwas gekürzt)

    Schließe mich dem mal an - bei mir auch das gleiche - habe es aber erst heute morgen gemerkt. Also erstmal kein Grund für wilden Aktionismus auf der User Seite?!?!

    BtW: @Meistertr - bist du der (weiter) Entwickler von dem Adapter? Das das mi-vaccum Widget seit Monaten aus dem VIS Editor respektive komplett aus dem Admin verschwunden ist, ist bekannt?

    ioBroker (since 2018) auf Intel Core i3-5005U NUC und Windwos10 Pro

    1 Reply Last reply
    0
    • gelberlemmyG gelberlemmy

      @saeft_2003 ich habe einmal geschaut im Adapter. Dort ist der Token wesentlich kürzer. Wie soll man den dann noch kürzen. Wenn ich aber einmal dort die Geräte neu anfrage, bekomme ich auch einen HTTP Error. Wie gesagt auch die MAP wird nicht mehr aktualisiert.

      D Offline
      D Offline
      dirkhe
      Developer
      wrote on last edited by
      #455

      @gelberlemmy er meint, du sollst das hier aus dem Forumsbeitrag kürzen oder schwärzen

      D gelberlemmyG 2 Replies Last reply
      0
      • D dirkhe

        @gelberlemmy er meint, du sollst das hier aus dem Forumsbeitrag kürzen oder schwärzen

        D Offline
        D Offline
        dirkhe
        Developer
        wrote on last edited by
        #456

        Auf github wurde geschrieben, das sich das auth Verfahren geändert hat, dass muss erst neu programmiert werden. Also abwarten.

        1 Reply Last reply
        0
        • D dirkhe

          @gelberlemmy er meint, du sollst das hier aus dem Forumsbeitrag kürzen oder schwärzen

          gelberlemmyG Offline
          gelberlemmyG Offline
          gelberlemmy
          wrote on last edited by
          #457

          @dirkhe sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:

          @gelberlemmy er meint, du sollst das hier aus dem Forumsbeitrag kürzen oder schwärzen

          Ohhh Brett vor dem Kopf.... Na klar.... Danke für Eure Hinweise....... 🤦🏼‍♂️

          1 Reply Last reply
          0
          • MeistertrM Meistertr

            @bahnuhr die Nachricht mit den Räumen auf der Karte kommt direkt vom Roboter ändert sich ein Raum hat man entweder selber an der Karte gedreht oder der Roboter hat einen neuen Raum selbstständig generiert.
            Die Räume werden bei Kartenwechsel, Neustart und alle 15 Minuten überprüft. Ein manuelles laden der Räume ist nicht notwendig.
            Mapindex und Raumnummer sind in der App nicht zu sehen, aber die Namen, die auch in dem Datenpunkt stehen. Raimids geht nur durch try and error...

            Räume die nicht mehr vorhanden sind auf dem Roboter kann der Adapter nicht erkennen. Da er nicht unterscheiden kann ob es nun eine andere Karte ist oder der Raum weg ist. daher müssen gelöschte Räume manuell aus iobroker gelöscht werden.

            S Offline
            S Offline
            saeft_2003
            Most Active
            wrote on last edited by saeft_2003
            #458

            @meistertr

            Mir ist klar das die Priorität im Moment wo anders liegt. Aber ist geplant das der Adapter den S7 maxV unterstützt?

            1C61C4B6-B355-4683-8594-5C3C3A37391F.jpeg

            MeistertrM 1 Reply Last reply
            0
            • D3ltoroxpD Offline
              D3ltoroxpD Offline
              D3ltoroxp
              wrote on last edited by
              #459

              Hallo zusammen,

              durch den Umzug auf mein neues System ist mir aufgefallen, das ich keine Karte mehr habe und ich bekomme sie auch nicht mehr. Die DP's sind leer.

              In der Log steht nichts. Wenn ich auf load map drücke tut sich auch nichts, in der Log taucht auch nichts auf.

              f744d445-39af-4b84-87ae-0edfd4fccc5b-grafik.png

              Die DP's sind write : false, wenn ich es auf true setzte kommt in der Log

              mihome-vacuum.0
              	2022-01-03 18:48:20.831	warn	can not set mapURL
              mihome-vacuum.0
              	2022-01-03 18:48:17.651	warn	can not set map64
              mihome-vacuum.0
              	2022-01-03 18:47:26.281	warn	can not set map64
              mihome-vacuum.0
              	2022-01-03 18:47:23.679	warn	can not set mapURL
              

              setzte ich sie wieder zurück auf original, kommt gar nichts mehr in der Log. Aber auch so bekomme ich die Map nicht mehr, auch nicht in der VIS.

              S 1 Reply Last reply
              0
              • D3ltoroxpD D3ltoroxp

                Hallo zusammen,

                durch den Umzug auf mein neues System ist mir aufgefallen, das ich keine Karte mehr habe und ich bekomme sie auch nicht mehr. Die DP's sind leer.

                In der Log steht nichts. Wenn ich auf load map drücke tut sich auch nichts, in der Log taucht auch nichts auf.

                f744d445-39af-4b84-87ae-0edfd4fccc5b-grafik.png

                Die DP's sind write : false, wenn ich es auf true setzte kommt in der Log

                mihome-vacuum.0
                	2022-01-03 18:48:20.831	warn	can not set mapURL
                mihome-vacuum.0
                	2022-01-03 18:48:17.651	warn	can not set map64
                mihome-vacuum.0
                	2022-01-03 18:47:26.281	warn	can not set map64
                mihome-vacuum.0
                	2022-01-03 18:47:23.679	warn	can not set mapURL
                

                setzte ich sie wieder zurück auf original, kommt gar nichts mehr in der Log. Aber auch so bekomme ich die Map nicht mehr, auch nicht in der VIS.

                S Offline
                S Offline
                saeft_2003
                Most Active
                wrote on last edited by saeft_2003
                #460

                @d3ltoroxp

                Die map geht bei uns alle im Moment nicht, der Adapter muss angepasst werden.

                D3ltoroxpD 1 Reply Last reply
                0
                • S saeft_2003

                  @d3ltoroxp

                  Die map geht bei uns alle im Moment nicht, der Adapter muss angepasst werden.

                  D3ltoroxpD Offline
                  D3ltoroxpD Offline
                  D3ltoroxp
                  wrote on last edited by
                  #461

                  @saeft_2003 Ah Gott sei Dank, ich dachte schon durch den Umzug, dann muss das grad zeitlich sich überschnitten haben, weil auf dem alten System gings noch. Ist mir nur am Tablet aufgefallen das auf einmal bei der VIS keine Karte mehr war.

                  Würde es denn was ändern wenn der Roborock Valetudo drauf hat ? Oder läuft das dann mit dem Adapter gar nicht mehr ?

                  1 Reply Last reply
                  0
                  • MeistertrM Meistertr

                    werde noch bis morgen abwarten und schauen ob es wieder geht, falls nicht muss ich mal schauen ob ich herausfinde was sie geändert haben...

                    Christian WöhrleC Offline
                    Christian WöhrleC Offline
                    Christian Wöhrle
                    wrote on last edited by
                    #462

                    @meistertr bei mir läuft die Karte problemlos.
                    Nutze den mija 1x auf dem China ServerScreenshot_20220103-194202.png

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      saeft_2003
                      Most Active
                      wrote on last edited by
                      #463

                      Seit heut Nacht läuft der Adapter gar nicht mehr. Vorher ging alles bis auf die map. Habt ihr das auch?

                      
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:14:16.469 - error: mihome-vacuum.0 (2943749) Unexpected token y in JSON at position 1
                      2022-01-04 07:14:16.475 - error: mihome-vacuum.0 (2943749) Socket Close
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token y in JSON at position 1
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:14:16.544 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:14:16.544 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:14:49.449 - error: mihome-vacuum.0 (2943767) uncaught exception: Unexpected token l in JSON at position 0
                      2022-01-04 07:14:49.450 - error: mihome-vacuum.0 (2943767) SyntaxError: Unexpected token l in JSON at position 0
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:14:49.451 - error: mihome-vacuum.0 (2943767) Unexpected token l in JSON at position 0
                      2022-01-04 07:14:49.457 - error: mihome-vacuum.0 (2943767) Socket Close
                      2022-01-04 07:14:49.524 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token l in JSON at position 0
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:14:49.525 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:14:49.525 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:15:22.385 - error: mihome-vacuum.0 (2943853) uncaught exception: Unexpected token C in JSON at position 0
                      2022-01-04 07:15:22.386 - error: mihome-vacuum.0 (2943853) SyntaxError: Unexpected token C in JSON at position 0
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:15:22.386 - error: mihome-vacuum.0 (2943853) Unexpected token C in JSON at position 0
                      2022-01-04 07:15:22.394 - error: mihome-vacuum.0 (2943853) Socket Close
                      2022-01-04 07:15:22.471 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token C in JSON at position 0
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:15:22.472 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:15:22.472 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:15:55.371 - error: mihome-vacuum.0 (2943901) uncaught exception: Unexpected token g in JSON at position 1
                      2022-01-04 07:15:55.372 - error: mihome-vacuum.0 (2943901) SyntaxError: Unexpected token g in JSON at position 1
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:15:55.373 - error: mihome-vacuum.0 (2943901) Unexpected token g in JSON at position 1
                      2022-01-04 07:15:55.380 - error: mihome-vacuum.0 (2943901) Socket Close
                      2022-01-04 07:15:55.467 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token g in JSON at position 1
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:15:55.468 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:15:55.469 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:15:55.469 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:15:55.469 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:16:28.510 - error: mihome-vacuum.0 (2943924) uncaught exception: Unexpected token Y in JSON at position 0
                      2022-01-04 07:16:28.511 - error: mihome-vacuum.0 (2943924) SyntaxError: Unexpected token Y in JSON at position 0
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:16:28.512 - error: mihome-vacuum.0 (2943924) Unexpected token Y in JSON at position 0
                      2022-01-04 07:16:28.520 - error: mihome-vacuum.0 (2943924) Socket Close
                      2022-01-04 07:16:28.601 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token Y in JSON at position 0
                      2022-01-04 07:16:28.601 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:16:28.602 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:16:28.602 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:17:01.788 - error: mihome-vacuum.0 (2943942) uncaught exception: Unexpected token s in JSON at position 0
                      2022-01-04 07:17:01.789 - error: mihome-vacuum.0 (2943942) SyntaxError: Unexpected token s in JSON at position 0
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:17:01.789 - error: mihome-vacuum.0 (2943942) Unexpected token s in JSON at position 0
                      2022-01-04 07:17:01.802 - error: mihome-vacuum.0 (2943942) Socket Close
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token s in JSON at position 0
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:17:01.883 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:17:01.883 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:17:34.829 - error: mihome-vacuum.0 (2944014) uncaught exception: Unexpected token S in JSON at position 0
                      2022-01-04 07:17:34.830 - error: mihome-vacuum.0 (2944014) SyntaxError: Unexpected token S in JSON at position 0
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:17:34.830 - error: mihome-vacuum.0 (2944014) Unexpected token S in JSON at position 0
                      2022-01-04 07:17:34.841 - error: mihome-vacuum.0 (2944014) Socket Close
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token S in JSON at position 0
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:17:34.910 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:17:34.910 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:18:04.842 - warn: host.iobroker "system.host.raspberrypi" is offline
                      2022-01-04 07:18:08.232 - error: mihome-vacuum.0 (2944057) uncaught exception: Unexpected token E in JSON at position 1
                      2022-01-04 07:18:08.233 - error: mihome-vacuum.0 (2944057) SyntaxError: Unexpected token E in JSON at position 1
                      at JSON.parse ()
                      at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      at Request.emit (events.js:400:28)
                      at Request.emit (domain.js:475:12)
                      at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:18:08.233 - error: mihome-vacuum.0 (2944057) Unexpected token E in JSON at position 1
                      2022-01-04 07:18:08.240 - error: mihome-vacuum.0 (2944057) Socket Close
                      2022-01-04 07:18:08.302 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected token E in JSON at position 1
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:436:22)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
                      2022-01-04 07:18:08.303 - error: host.iobroker Caught by controller[0]: at Object.onceWrapper (events.js:519:28)
                      2022-01-04 07:18:08.303 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                      2022-01-04 07:18:39.446 - error: mihome-vacuum.0 (2944108) adapter disabled
                      2022-01-04 07:18:40.077 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
                      
                      
                      1 Reply Last reply
                      0
                      • JackDanielJ Online
                        JackDanielJ Online
                        JackDaniel
                        wrote on last edited by
                        #464

                        ja, hab ihn gerade deaktiviert :(

                        Carpe diem

                        da_WoodyD 1 Reply Last reply
                        0
                        • JackDanielJ JackDaniel

                          ja, hab ihn gerade deaktiviert :(

                          da_WoodyD Online
                          da_WoodyD Online
                          da_Woody
                          wrote on last edited by
                          #465

                          @jackdaniel selbes thema
                          https://forum.iobroker.net/topic/50898/anmeldung-an-xiaomi-cloud-nicht-möglich-error-http-error

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

                          1 Reply Last reply
                          0
                          • D3ltoroxpD Offline
                            D3ltoroxpD Offline
                            D3ltoroxp
                            wrote on last edited by D3ltoroxp
                            #466

                            Indem Fall bekräftigt mich das, Valetudo auf zu spielen dann sollte der Adapter ja sauber laufen mit dem Sauger oder ?

                            In der Log kann ich aber momentan keine Anmeldefehler sehen.

                            S 1 Reply Last reply
                            0
                            • D3ltoroxpD D3ltoroxp

                              Indem Fall bekräftigt mich das, Valetudo auf zu spielen dann sollte der Adapter ja sauber laufen mit dem Sauger oder ?

                              In der Log kann ich aber momentan keine Anmeldefehler sehen.

                              S Offline
                              S Offline
                              saeft_2003
                              Most Active
                              wrote on last edited by
                              #467

                              @d3ltoroxp

                              Was hast du den für einen Saugroboter?

                              D3ltoroxpD 1 Reply Last reply
                              0
                              • S saeft_2003

                                @d3ltoroxp

                                Was hast du den für einen Saugroboter?

                                D3ltoroxpD Offline
                                D3ltoroxpD Offline
                                D3ltoroxp
                                wrote on last edited by
                                #468

                                @saeft_2003 einen Xiaomi Roborock S50 (also der weiße) Ich hab aber grad mal in dem anderen verlinkten Thread gelesen, kann vllt sein das ich den damals auch mit der China Cloud verheiratet hab, daher vllt keine Fehler beim Anmelden.

                                1 Reply Last reply
                                0
                                • S saeft_2003

                                  @meistertr

                                  Mir ist klar das die Priorität im Moment wo anders liegt. Aber ist geplant das der Adapter den S7 maxV unterstützt?

                                  1C61C4B6-B355-4683-8594-5C3C3A37391F.jpeg

                                  MeistertrM Offline
                                  MeistertrM Offline
                                  Meistertr
                                  Developer
                                  wrote on last edited by
                                  #469

                                  @saeft_2003 habs noch nicht getestet aber er sollte out of the Box gehen

                                  haselchenH S 2 Replies Last reply
                                  1
                                  • MeistertrM Meistertr

                                    @saeft_2003 habs noch nicht getestet aber er sollte out of the Box gehen

                                    haselchenH Offline
                                    haselchenH Offline
                                    haselchen
                                    Most Active
                                    wrote on last edited by
                                    #470

                                    @Meistertr

                                    War das jetzt ein Aufruf den Adapter wieder zu starten?
                                    Eine neue Version zu installieren?
                                    ....... ?

                                    Synology DS218+ & 2 x Fujitsu Esprimo (VM/Container) + FritzBox7590 + 2 AVM 3000 Repeater & Homematic & HUE & Osram & Xiaomi, NPM 10.9.4, Nodejs 22.21.0 ,JS Controller 7.0.7 ,Admin 7.7.19

                                    5 1 Reply Last reply
                                    0
                                    • haselchenH haselchen

                                      @Meistertr

                                      War das jetzt ein Aufruf den Adapter wieder zu starten?
                                      Eine neue Version zu installieren?
                                      ....... ?

                                      5 Offline
                                      5 Offline
                                      5tift
                                      wrote on last edited by
                                      #471

                                      @haselchen
                                      Bei mir läuft der Adapter seit 10 Uhr wieder ohne Fehler im Log

                                      S 1 Reply Last reply
                                      0
                                      • 5 5tift

                                        @haselchen
                                        Bei mir läuft der Adapter seit 10 Uhr wieder ohne Fehler im Log

                                        S Offline
                                        S Offline
                                        Strobelix
                                        wrote on last edited by
                                        #472

                                        @5tift Danke für den Hinweis.

                                        Bei mir geht es jetzt auch wieder

                                        Raspberrymatic, Homematic & Homematic IP Aktoren, ioBroker auf NUC i3, Nuki, Harmony Hub, Digitalstrom, Diverse Sonoff (Tasmota) und Shellies

                                        1 Reply Last reply
                                        0
                                        • MeistertrM Meistertr

                                          @saeft_2003 habs noch nicht getestet aber er sollte out of the Box gehen

                                          S Offline
                                          S Offline
                                          saeft_2003
                                          Most Active
                                          wrote on last edited by
                                          #473

                                          @meistertr sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:

                                          @saeft_2003 habs noch nicht getestet aber er sollte out of the Box gehen

                                          Super! Läuft wieder sogar die map geht wieder 👍

                                          haselchenH 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          691

                                          Online

                                          32.7k

                                          Users

                                          82.5k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe