Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter Mihome-vacuum v3.1.6 Next Generarition

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter Mihome-vacuum v3.1.6 Next Generarition

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

      @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 1 Reply Last reply Reply Quote 0
      • JB_Sullivan
        JB_Sullivan @bahnuhr last edited by JB_Sullivan

        @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?

        1 Reply Last reply Reply Quote 0
        • D
          dirkhe Developer @gelberlemmy last edited by

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

          D gelberlemmy 2 Replies Last reply Reply Quote 0
          • D
            dirkhe Developer @dirkhe last edited by

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

            1 Reply Last reply Reply Quote 0
            • gelberlemmy
              gelberlemmy @dirkhe last edited by

              @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 Reply Quote 0
              • S
                saeft_2003 Most Active @Meistertr last edited by 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

                Meistertr 1 Reply Last reply Reply Quote 0
                • D3ltoroxp
                  D3ltoroxp last edited by

                  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 Reply Quote 0
                  • S
                    saeft_2003 Most Active @D3ltoroxp last edited by saeft_2003

                    @d3ltoroxp

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

                    D3ltoroxp 1 Reply Last reply Reply Quote 0
                    • D3ltoroxp
                      D3ltoroxp @saeft_2003 last edited by

                      @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 Reply Quote 0
                      • Christian Wöhrle
                        Christian Wöhrle @Meistertr last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • S
                          saeft_2003 Most Active last edited by

                          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 Reply Quote 0
                          • JackDaniel
                            JackDaniel last edited by

                            ja, hab ihn gerade deaktiviert 😞

                            da_Woody 1 Reply Last reply Reply Quote 0
                            • da_Woody
                              da_Woody @JackDaniel last edited by

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

                              1 Reply Last reply Reply Quote 0
                              • D3ltoroxp
                                D3ltoroxp last edited by 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 1 Reply Last reply Reply Quote 0
                                • S
                                  saeft_2003 Most Active @D3ltoroxp last edited by

                                  @d3ltoroxp

                                  Was hast du den für einen Saugroboter?

                                  D3ltoroxp 1 Reply Last reply Reply Quote 0
                                  • D3ltoroxp
                                    D3ltoroxp @saeft_2003 last edited by

                                    @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 Reply Quote 0
                                    • Meistertr
                                      Meistertr Developer @saeft_2003 last edited by

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

                                      haselchen S 2 Replies Last reply Reply Quote 1
                                      • haselchen
                                        haselchen Most Active @Meistertr last edited by

                                        @Meistertr

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

                                        5 1 Reply Last reply Reply Quote 0
                                        • 5
                                          5tift @haselchen last edited by

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

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            Strobelix @5tift last edited by

                                            @5tift Danke für den Hinweis.

                                            Bei mir geht es jetzt auch wieder

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            677
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            100
                                            1198
                                            315296
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo