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

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

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

                                  Ok, Frage hat sich erledigt, Adapter neu starten 😉
                                  Dann tut es wieder ✌

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

                                    Hm, bei mir kommt leider keine Karte, auch wenn ich sie per Schaltfläche anfordere tut sich rein gar nichts. Im Log vom Adapter nichts zu sehen. Adapter auch schon mehrmals neu gestartet.

                                    Was kommt sehe ich grad, wenn ich den Adapter an und aus schalte.

                                    149
                                    
                                    Log-Größe: 22.1 MB
                                    Zeit
                                    	
                                    Nachricht
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:46.577	info	create state for carpet_mode
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:46.052	info	create states for water box
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:46.005	info	change states from State control.fan_power
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.983	info	settest next timer: not available
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.971	info	Map selected create states...
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.844	warn	Login failed
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.844	warn	Login failed
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.458	info	select standard vacuum protocol....
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.332	info	IOT enabled, create state
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:45.266	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:15.605	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:15.605	info	terminating
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:15.604	error	Socket Close
                                    mihome-vacuum.0
                                    	2022-01-04 16:51:15.603	info	Got terminate signal TERMINATE_YOURSELF
                                    

                                    So sehen die DP's aus

                                    7a055f9f-a9a7-41c9-9f56-92a7eb2b4645-grafik.png

                                    da_Woody M 2 Replies Last reply Reply Quote 0
                                    • da_Woody
                                      da_Woody @D3ltoroxp last edited by

                                      @d3ltoroxp same here. auf germany bekomm ich den string, china ist leer. keine map64, keine malURL.

                                      bahnuhr 1 Reply Last reply Reply Quote 0
                                      • M
                                        Maxim-777 @D3ltoroxp last edited by

                                        @d3ltoroxp
                                        genau das gleiche Problem 🤔

                                        2022-01-04 20:04:17.468 - info: mihome-vacuum.1 (25044) starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.2, js-controller: 3.3.22
                                        2022-01-04 20:04:17.782 - info: mihome-vacuum.1 (25044) IOT enabled, create state
                                        2022-01-04 20:04:18.008 - info: mihome-vacuum.1 (25044) select standard vacuum protocol....
                                        2022-01-04 20:04:18.751 - info: mihome-vacuum.1 (25044) settest next timer: not available
                                        2022-01-04 20:04:19.172 - info: mihome-vacuum.1 (25044) Map selected create states...
                                        2022-01-04 20:04:19.448 - info: mihome-vacuum.1 (25044) change states from State control.fan_power
                                        2022-01-04 20:04:19.468 - info: mihome-vacuum.1 (25044) create states for water box
                                        2022-01-04 20:04:19.487 - info: mihome-vacuum.1 (25044) create states for water box mode
                                        2022-01-04 20:04:19.510 - info: mihome-vacuum.1 (25044) create states for mop
                                        2022-01-04 20:04:20.696 - info: mihome-vacuum.1 (25044) create new room: 212001008874
                                        2022-01-04 20:04:22.563 - info: javascript.0 (13710) script.js.System.Hilfsvariable.StaubsaugerS7_Betriebsstunden: Gesamtlaufzeit: 7Tage, 2. Stunden, 56 Minuten,
                                        2022-01-04 20:04:27.886 - info: mihome-vacuum.1 (25044) create state for carpet_mode
                                        

                                        Screenshot 2022-01-04 201321.jpg

                                        S 1 Reply Last reply Reply Quote 0
                                        • S
                                          Strobelix @Maxim-777 last edited by

                                          @maxim-777 hast du auf nodejs 14 geupdated?
                                          Wenn ja hilft das hier:

                                          Im Ordner opt/iobroker/node_modules den Ordner „Canvas“ löschen und dann unter opt/iobroker npm -rebuild ausführen.

                                          Hat bei mir geholfen und hab den Tipp aus nem github issue

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

                                            @strobelix Dann werde ich das mal probieren. Ich hatte auch vor ein paar Tagen auf nodejs 14 upgedated.

                                            Einfach nur

                                            opt/iobroker npm -rebuild
                                            

                                            oder muss das sein

                                            opt/iobroker npm -rebuild Canvas ?
                                            

                                            Installiert er nur Canvas neu, oder was passiert da noch bei rebuild ?

                                            In dem Update Thread steht was ähnliches.

                                            Manuelle Rebuilds
                                            
                                            Hier zu gibt es iobroker rebuild adaptername und falls das nicht reicht iobroker rebuild adaptername --install. Das einfach manuell an der Shell ausführen. Damit sollte alles idealerweise automatisiert erledigt sein.
                                            
                                            S 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            912
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            100
                                            1198
                                            317577
                                            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