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 v2.0.x

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    16
    1
    306

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

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

Test Adapter mihome-vacuum v2.0.x

Scheduled Pinned Locked Moved Tester
xiaomiroborockmihome-vacuummap
1.5k Posts 144 Posters 541.0k Views 118 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.
  • ? A Former User

    @Meistertr Hi, hab den Admin komplett neu installiert, das gleiche. Dann ein Downgrade auf 3.7.9 gemacht, keine Änderung. Wieder ein Update auf die 4.0.5, das gleiche wie auf den Screenshots.
    Mit Firefox und Chrome getestet, Browser cache gelöscht, refresh crtl+F5, keine Änderung.

    Mit der Version von @dirkhe 2.0.8 gibts diese Darstellungsfehler nicht, dafür bleibt der Adapter auf gelb :cop:

    Daher hab ich jetzt wieder die 2.0.7 installiert, die läuft, keine Fehler im Log, halt nur in der Konfig die Darstellungsfehler..
    Alles auf Stand von latest, Node 10.19.0 NPM 6.13.7 , Linux Mint 18.3, VM.

    Habe auf einer meiner Test-VMs mit komplett neu aufgesetztem iobroker, debian 10, node 12, gerade auch die 2.0.7 von community installiert, dort tritt der Darstellungsfehler nicht auf.

    Hat also was mit meiner uralten iobroker konfig zu tun.. naja die VM ist 2 jahre alt, denke langsam wirds mal Zeit auf eine neue um zu ziehen.. die Tage.. ;-)

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

    @ilovegym wenn du meinen testet, könntest du da mal auf debug stellen und hier Posten?
    Wenn dort die config geht, kannst du da übrigens deinen Token einstellen und dann den anderen wieder installieren

    1 Reply Last reply
    0
    • D dirkhe

      @Meistertr, sithe gerade nicht am Rechner. Du machst ein JSON.parse und dann ein forsch. Wenn es ein Object ist und kein Array, geht das dann? Ist aber nur ein Schuss ins blaue.

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

      @dirkhe es ist ein array, ich hab die struktur geändert aber in der tat könnte da der fehler liegen da bei ihn ein objekt drin liegt @ilovegym lösch mal die instanz und leg sie neu an damit die config komplett geleert ist. oder lade nochmal die geräte vom server uns speichern dann nochmal öffnen dann sollte es auch gehen wenn es an dem punkt hakt

      1 Reply Last reply
      0
      • MeistertrM Offline
        MeistertrM Offline
        Meistertr
        Developer
        wrote on last edited by
        #479

        @ilovegym bitte nochmal von git dann sollte alles wieder gehen aber bitte geräte neu einlesen, da sich was geändert hat

        DiginixD ? 2 Replies Last reply
        0
        • MeistertrM Meistertr

          @ilovegym bitte nochmal von git dann sollte alles wieder gehen aber bitte geräte neu einlesen, da sich was geändert hat

          DiginixD Offline
          DiginixD Offline
          Diginix
          wrote on last edited by Diginix
          #480

          @Meistertr Letzte 2.0.7 läuft bei mir. Einstellungen und deren Darstellung passen auch. Aber weiterhin ist während des Saugens zwischendurch mal eine Karte die 10-20 Sekunden alt ist. Daran wird sich ja auch nichts ändern, auch wenn die App den Bug nicht hat.

          Aber hattest du noch deine Idee für das letzte Kartenupdate wenn Sauger in Station eingebaut?
          Bei mir ist das letzt Bild wieder mit Sauger 10 cm vor dem Dock. In der App ist er direkt im Dock.
          In der App sind ja aber auch alle Räume schon wieder farbig wenn der Sauger sich auf den Weg zum Dock macht. Das ist im Adapter nicht so. Da bleibt weiterhin nur der letzte gesaugte Raum farbig. Aber das Bild bekommst du ja komplett so vom Server oder?

          ..:: So long! Tom ::..

          NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

          1 Reply Last reply
          0
          • MathiasJM Offline
            MathiasJM Offline
            MathiasJ
            wrote on last edited by
            #481

            Ihr Glückspilze!
            ich bekomme die nicht mal installiert.

            $ ./iobroker upgrade mihome-vacuum
            Update mihome-vacuum from @1.1.5 to @2.0.7
            NPM version: 6.13.4npm install iobroker.mihome-vacuum@2.0.7 --loglevel error --prefix "/opt/iobroker" (System call)
            Package pixman-1 was not found in the pkg-config search path.Perhaps you should add the directory containing `pixman-1.pc'to the PKG_CONFIG_PATH environment variableNo package 'pixman-1' foundgyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
            gyp
             ERR! configure error gyp 
            ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
            gyp ERR! System Linux 4.19.97-v7l+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! 
            cwd /opt/iobroker/node_modules/canvasgyp ERR! node -v v10.19.0gyp ERR! node-gyp -v v5.0.5gyp ERR! not ok 
            node-pre-gyp
             ERR! build error 
            node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
            node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
            node-pre-gyp ERR! System Linux 4.19.97-v7l+node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvasnode-pre-gyp ERR! node -v v10.19.0node-pre-gyp ERR! node-pre-gyp -v v0.11.0node-pre-gyp ERR! not ok 
            npm
             ERR!
             code
             ELIFECYCLE
            npm 
            ERR! 
            errno 1
            npm 
            ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`
            npm 
            ERR! Exit status 1
            npm ERR!
             npm
             ERR!
             Failed at the canvas@2.6.1 install script.npm
             ERR!
             This is probably not a problem with npm. There is likely additional logging output above.
            npm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2020-03-03T05_40_34_693Z-debug.log
            ERROR: host.raspberrypi Cannot install iobroker.mihome-vacuum@2.0.7: 1
            ERROR: process exited with code 25
            

            IObroker auf dem NUC als VM.
            Da ich noch keine Aktoren habe, wird momentan via Radar nur der AB der Fritzbox ein- und ausgeschaltet.
            Welches Smarthome-System es letztendlich wird, weiß ich noch nicht. Vielleicht kommen auch nur Zigbee-Geräte ins Haus.

            D 1 Reply Last reply
            0
            • MathiasJM MathiasJ

              Ihr Glückspilze!
              ich bekomme die nicht mal installiert.

              $ ./iobroker upgrade mihome-vacuum
              Update mihome-vacuum from @1.1.5 to @2.0.7
              NPM version: 6.13.4npm install iobroker.mihome-vacuum@2.0.7 --loglevel error --prefix "/opt/iobroker" (System call)
              Package pixman-1 was not found in the pkg-config search path.Perhaps you should add the directory containing `pixman-1.pc'to the PKG_CONFIG_PATH environment variableNo package 'pixman-1' foundgyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
              gyp
               ERR! configure error gyp 
              ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
              gyp ERR! System Linux 4.19.97-v7l+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! 
              cwd /opt/iobroker/node_modules/canvasgyp ERR! node -v v10.19.0gyp ERR! node-gyp -v v5.0.5gyp ERR! not ok 
              node-pre-gyp
               ERR! build error 
              node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
              node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
              node-pre-gyp ERR! System Linux 4.19.97-v7l+node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvasnode-pre-gyp ERR! node -v v10.19.0node-pre-gyp ERR! node-pre-gyp -v v0.11.0node-pre-gyp ERR! not ok 
              npm
               ERR!
               code
               ELIFECYCLE
              npm 
              ERR! 
              errno 1
              npm 
              ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`
              npm 
              ERR! Exit status 1
              npm ERR!
               npm
               ERR!
               Failed at the canvas@2.6.1 install script.npm
               ERR!
               This is probably not a problem with npm. There is likely additional logging output above.
              npm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2020-03-03T05_40_34_693Z-debug.log
              ERROR: host.raspberrypi Cannot install iobroker.mihome-vacuum@2.0.7: 1
              ERROR: process exited with code 25
              
              D Offline
              D Offline
              dirkhe
              Developer
              wrote on last edited by
              #482

              @MathiasJ Readme!

              MathiasJM 1 Reply Last reply
              0
              • D dirkhe

                @MathiasJ Readme!

                MathiasJM Offline
                MathiasJM Offline
                MathiasJ
                wrote on last edited by MathiasJ
                #483

                @dirkhe sagte in Test Adapter mihome-vacuum v2.0.x:

                @MathiasJ Readme!

                ist installiert... muß mich erst mal einlesen, um die Karte ins VIS übertragen zu können.

                IObroker auf dem NUC als VM.
                Da ich noch keine Aktoren habe, wird momentan via Radar nur der AB der Fritzbox ein- und ausgeschaltet.
                Welches Smarthome-System es letztendlich wird, weiß ich noch nicht. Vielleicht kommen auch nur Zigbee-Geräte ins Haus.

                1 Reply Last reply
                0
                • K Offline
                  K Offline
                  K_o_bold
                  wrote on last edited by
                  #484

                  @Meistertr ,

                  ich bekomme immer wieder diesen error, obwohl er die Karte richtig lädt:

                  (1462) no map found on server___{"statusCode":403,"headers":{"server":"nginx","date":"Tue, 03 Mar 2020 10:51:09 GMT","content-length":"122","connection":"close","x-xiaomi-request-id":"6b964dae-6380-8e
                  mihome-vacuum.0	2020-03-03 11:50:41.160	error	(
                  

                  Adapter Version 2.0.7
                  Roborock S50

                  DiginixD 1 Reply Last reply
                  0
                  • K K_o_bold

                    @Meistertr ,

                    ich bekomme immer wieder diesen error, obwohl er die Karte richtig lädt:

                    (1462) no map found on server___{"statusCode":403,"headers":{"server":"nginx","date":"Tue, 03 Mar 2020 10:51:09 GMT","content-length":"122","connection":"close","x-xiaomi-request-id":"6b964dae-6380-8e
                    mihome-vacuum.0	2020-03-03 11:50:41.160	error	(
                    

                    Adapter Version 2.0.7
                    Roborock S50

                    DiginixD Offline
                    DiginixD Offline
                    Diginix
                    wrote on last edited by
                    #485

                    @K_o_bold Liest sich für mich nach einem 403 Forbidden welches der Adapter vom Xiaomi Server bekommt.
                    Stell mal die Instanz auf Loglevel debug und schau mal im Log nach "Xiaomi Cloud: Login successful".
                    Ansonsten wird sich @Meistertr schon dazu melden.

                    ..:: So long! Tom ::..

                    NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                    1 Reply Last reply
                    0
                    • T Offline
                      T Offline
                      tombox
                      wrote on last edited by tombox
                      #486

                      Gelöst nach 10min warten kamen die ersten Daten rein.

                      Keine Verbindung zu S50 mit 2008 firmware mit Adapter 2.0.7 installiert via github

                      mihome-vacuum.0	2020-03-03 14:04:16.825	debug	(1481) requesting params every: 60 Sec
                      mihome-vacuum.0	2020-03-03 14:04:16.825	silly	(1481) sendMsg[1] >>> {"id":9,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:04:16.822	info	(1481) Connected
                      mihome-vacuum.0	2020-03-03 14:04:16.820	silly	(1481) Receive <<< Helo <<< *************ffffffffffffffffffffffffffffffff
                      mihome-vacuum.0	2020-03-03 14:04:16.815	info	(1481) Disconnect
                      mihome-vacuum.0	2020-03-03 14:04:11.823	debug	(1481) no answer for get_status(id:8) received, giving up
                      mihome-vacuum.0	2020-03-03 14:04:06.821	silly	(1481) sendMsg[3] >>> {"id":8,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:04:01.816	silly	(1481) sendMsg[2] >>> {"id":8,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:03:56.812	silly	(1481) sendMsg[1] >>> {"id":8,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:03:54.843	debug	(1481) no answer for get_room_mapping(id:7) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:54.839	debug	(1481) no answer for get_carpet_mode(id:6) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:52.551	debug	(1481) no answer for get_sound_volume(id:5) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:52.352	debug	(1481) no answer for get_clean_summary(id:4) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:52.149	debug	(1481) no answer for get_consumable(id:3) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:51.971	warn	(1481) no answer received after after 3 times -> pause miIO.info from request parameters, try again in one hour
                      mihome-vacuum.0	2020-03-03 14:03:51.969	debug	(1481) no answer for miIO.info(id:2) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:51.948	debug	(1481) no answer for get_status(id:1) received, giving up
                      mihome-vacuum.0	2020-03-03 14:03:49.840	silly	(1481) sendMsg[3] >>> {"id":7,"method":"get_room_mapping"}
                      mihome-vacuum.0	2020-03-03 14:03:49.837	silly	(1481) sendMsg[3] >>> {"id":6,"method":"get_carpet_mode"}
                      mihome-vacuum.0	2020-03-03 14:03:47.549	silly	(1481) sendMsg[3] >>> {"id":5,"method":"get_sound_volume"}
                      mihome-vacuum.0	2020-03-03 14:03:47.350	silly	(1481) sendMsg[3] >>> {"id":4,"method":"get_clean_summary"}
                      mihome-vacuum.0	2020-03-03 14:03:47.148	silly	(1481) sendMsg[3] >>> {"id":3,"method":"get_consumable"}
                      mihome-vacuum.0	2020-03-03 14:03:46.966	silly	(1481) sendMsg[3] >>> {"id":2,"method":"miIO.info"}
                      mihome-vacuum.0	2020-03-03 14:03:46.946	silly	(1481) sendMsg[3] >>> {"id":1,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:03:44.837	silly	(1481) sendMsg[2] >>> {"id":7,"method":"get_room_mapping"}
                      mihome-vacuum.0	2020-03-03 14:03:44.834	silly	(1481) sendMsg[2] >>> {"id":6,"method":"get_carpet_mode"}
                      mihome-vacuum.0	2020-03-03 14:03:42.545	silly	(1481) sendMsg[2] >>> {"id":5,"method":"get_sound_volume"}
                      mihome-vacuum.0	2020-03-03 14:03:42.347	silly	(1481) sendMsg[2] >>> {"id":4,"method":"get_clean_summary"}
                      mihome-vacuum.0	2020-03-03 14:03:42.144	silly	(1481) sendMsg[2] >>> {"id":3,"method":"get_consumable"}
                      mihome-vacuum.0	2020-03-03 14:03:41.962	silly	(1481) sendMsg[2] >>> {"id":2,"method":"miIO.info"}
                      mihome-vacuum.0	2020-03-03 14:03:41.941	silly	(1481) sendMsg[2] >>> {"id":1,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:03:39.834	silly	(1481) sendMsg[1] >>> {"id":7,"method":"get_room_mapping"}
                      mihome-vacuum.0	2020-03-03 14:03:39.831	silly	(1481) sendMsg[1] >>> {"id":6,"method":"get_carpet_mode"}
                      mihome-vacuum.0	2020-03-03 14:03:39.820	debug	(1481) Xiaomi Cloud: Login successful
                      mihome-vacuum.0	2020-03-03 14:03:37.542	silly	(1481) sendMsg[1] >>> {"id":5,"method":"get_sound_volume"}
                      mihome-vacuum.0	2020-03-03 14:03:37.345	silly	(1481) sendMsg[1] >>> {"id":4,"method":"get_clean_summary"}
                      mihome-vacuum.0	2020-03-03 14:03:37.341	info	(1481) set nächster Timer: Nicht verfügbar
                      mihome-vacuum.0	2020-03-03 14:03:37.142	silly	(1481) sendMsg[1] >>> {"id":3,"method":"get_consumable"}
                      mihome-vacuum.0	2020-03-03 14:03:37.003	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.rooms.addRoom:{"val":"Kartenindex oder Zonenkoordinaten einfügen","ack":true,"ts":1583240616994,"q":0,"from":"system.adapter.mihome-
                      mihome-vacuum.0	2020-03-03 14:03:36.982	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":true,"ack":true,"ts":1583240616966,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","
                      mihome-vacuum.0	2020-03-03 14:03:36.982	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.queue:{"val":0,"ack":true,"ts":1583240616966,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1583
                      mihome-vacuum.0	2020-03-03 14:03:36.981	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":false,"ack":true,"ts":1583240616899,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin",
                      mihome-vacuum.0	2020-03-03 14:03:36.980	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.wifi_signal:{"val":"unavailable","ack":true,"ts":1583240616899,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.use
                      mihome-vacuum.0	2020-03-03 14:03:36.979	silly	(1481) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":false,"ack":true,"ts":1583240616898,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin",
                      mihome-vacuum.0	2020-03-03 14:03:36.975	silly	(1481) States system redis pmessage system.adapter.mihome-vacuum.0.logLevel/system.adapter.mihome-vacuum.0.logLevel:{"val":"silly","ack":true,"ts":1583240616891,"q":0,"from":"system.adapter.mihome-vac
                      mihome-vacuum.0	2020-03-03 14:03:36.958	silly	(1481) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
                      mihome-vacuum.0	2020-03-03 14:03:36.940	debug	(1481) requesting params every: 60 Sec
                      mihome-vacuum.0	2020-03-03 14:03:36.938	silly	(1481) sendMsg[1] >>> {"id":1,"method":"get_status"}
                      mihome-vacuum.0	2020-03-03 14:03:36.928	info	(1481) Connected
                      mihome-vacuum.0	2020-03-03 14:03:36.925	silly	(1481) Receive <<< Helo <<< *****************************ffffffffffffffffffffffffffffffff
                      mihome-vacuum.0	2020-03-03 14:03:36.819	debug	(1481) server started on 0.0.0.0:53421
                      mihome-vacuum.0	2020-03-03 14:03:36.807	info	(1481) Disconnect
                      mihome-vacuum.0	2020-03-03 14:03:36.781	info	(1481) Cloud control disabled
                      mihome-vacuum.0	2020-03-03 14:03:36.778	info	(1481) Expert mode disabled, states deleted
                      mihome-vacuum.0	2020-03-03 14:03:36.761	debug	(1481) Xiaomi Cloud: Logging in
                      mihome-vacuum.0	2020-03-03 14:03:36.758	debug	(1481) load Map creator... true
                      mihome-vacuum.0	2020-03-03 14:03:36.659	info	(1481) starting. Version 2.0.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0
                      
                      
                      1 Reply Last reply
                      0
                      • MeistertrM Meistertr

                        @ilovegym bitte nochmal von git dann sollte alles wieder gehen aber bitte geräte neu einlesen, da sich was geändert hat

                        ? Offline
                        ? Offline
                        A Former User
                        wrote on last edited by
                        #487

                        @Meistertr Hi, ja, läuft alles jetzt, keine Fehler 👍🙂
                        Dankeschön

                        1 Reply Last reply
                        0
                        • J Offline
                          J Offline
                          jensus11
                          wrote on last edited by
                          #488

                          Hallo,
                          ich habe bei mir Valetudo installiert und einige Zonen angelegt.
                          Die online Anbindung habe ich per Firewall unterbunden, da ich schon 2x das Vergnügen hatte das sich der Gen1 auf eine neue FW geupdatet hat oder wie auch immer sich selber resetet hat.
                          Adapter 2.0.8 ist installiert, FW 3.3.9-003468 und Valetudo in 0.4.0.
                          Mir werden auch alle Daten und Infos angezeigt, nur leider die Karten oder Zonen nicht.
                          Was kann ich machen, würde so gerne über Alexa die einzelnen Zonen steuern.

                          D 1 Reply Last reply
                          0
                          • J jensus11

                            Hallo,
                            ich habe bei mir Valetudo installiert und einige Zonen angelegt.
                            Die online Anbindung habe ich per Firewall unterbunden, da ich schon 2x das Vergnügen hatte das sich der Gen1 auf eine neue FW geupdatet hat oder wie auch immer sich selber resetet hat.
                            Adapter 2.0.8 ist installiert, FW 3.3.9-003468 und Valetudo in 0.4.0.
                            Mir werden auch alle Daten und Infos angezeigt, nur leider die Karten oder Zonen nicht.
                            Was kann ich machen, würde so gerne über Alexa die einzelnen Zonen steuern.

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

                            @jensus11 bitte auf debug stellen und mal Log hier posten

                            1 Reply Last reply
                            0
                            • J Offline
                              J Offline
                              jensus11
                              wrote on last edited by jensus11
                              #490
                              mihome-vacuum.0	2020-03-03 19:48:03.714	debug	(15538) Receive <<< {"result":[{"msg_ver":8,"msg_seq":3338,"state":8,"battery":100,"clean_time":224,"clean_area":7165000,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0}
                              mihome-vacuum.0	2020-03-03 19:48:03.708	debug	(15538) sendMsg[1] >>> {"id":29,"method":"get_status"}
                              mihome-vacuum.0	2020-03-03 19:47:50.191	warn	(15538) Could not receive Mappointer, giving up
                              mihome-vacuum.0	2020-03-03 19:47:50.191	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":28}
                              mihome-vacuum.0	2020-03-03 19:47:50.182	debug	(15538) 9. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:50.182	debug	(15538) sendMsg[1] >>> {"id":28,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:49.681	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":27}
                              mihome-vacuum.0	2020-03-03 19:47:49.662	debug	(15538) 8. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:49.662	debug	(15538) sendMsg[1] >>> {"id":27,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:49.160	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":26}
                              mihome-vacuum.0	2020-03-03 19:47:49.156	debug	(15538) 7. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:49.155	debug	(15538) sendMsg[1] >>> {"id":26,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:48.654	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":25}
                              mihome-vacuum.0	2020-03-03 19:47:48.642	debug	(15538) 6. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:48.641	debug	(15538) sendMsg[1] >>> {"id":25,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:48.141	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":24}
                              mihome-vacuum.0	2020-03-03 19:47:48.117	debug	(15538) 5. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:48.117	debug	(15538) sendMsg[1] >>> {"id":24,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:47.616	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":23}
                              mihome-vacuum.0	2020-03-03 19:47:47.610	debug	(15538) 4. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:47.610	debug	(15538) sendMsg[1] >>> {"id":23,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:47.109	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":22}
                              mihome-vacuum.0	2020-03-03 19:47:47.105	debug	(15538) 3. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:47.104	debug	(15538) sendMsg[1] >>> {"id":22,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:46.607	debug	(15538) CLEAN_LOGGING[{"Datum":"3.3","Start":"19:02","Saugzeit":"4 min","Fläche":"7.17 m²","Error":0,"Ende":false},{"Datum":"3.3","Start":"16:15","Saugzeit":"10 min","Fläche":"8.27 m²","Error":0,"Ende
                              mihome-vacuum.0	2020-03-03 19:47:46.600	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":21}
                              mihome-vacuum.0	2020-03-03 19:47:46.588	debug	(15538) 2. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:46.588	debug	(15538) sendMsg[1] >>> {"id":21,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:46.434	debug	(15538) Receive <<< {"result":[[1577275556,1577275612,14,0,0,0]],"id":20}
                              mihome-vacuum.0	2020-03-03 19:47:46.405	debug	(15538) sendMsg[1] >>> {"id":20,"method":"get_clean_record","params":[1577275556]}
                              mihome-vacuum.0	2020-03-03 19:47:46.210	debug	(15538) Receive <<< {"result":[[1577705584,1577707390,1705,27040000,0,1]],"id":19}
                              mihome-vacuum.0	2020-03-03 19:47:46.204	debug	(15538) sendMsg[1] >>> {"id":19,"method":"get_clean_record","params":[1577705584]}
                              mihome-vacuum.0	2020-03-03 19:47:46.086	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":18}
                              mihome-vacuum.0	2020-03-03 19:47:46.024	debug	(15538) Receive <<< {"result":[[1577707998,1577708227,229,4305000,0,1]],"id":17}
                              mihome-vacuum.0	2020-03-03 19:47:46.008	debug	(15538) 1. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:46.008	debug	(15538) sendMsg[1] >>> {"id":18,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:46.004	debug	(15538) sendMsg[1] >>> {"id":17,"method":"get_clean_record","params":[1577707998]}
                              mihome-vacuum.0	2020-03-03 19:47:45.830	debug	(15538) Receive <<< {"result":[[1577708513,1577708756,243,3115000,0,1]],"id":16}
                              mihome-vacuum.0	2020-03-03 19:47:45.803	debug	(15538) sendMsg[1] >>> {"id":16,"method":"get_clean_record","params":[1577708513]}
                              mihome-vacuum.0	2020-03-03 19:47:45.617	debug	(15538) Receive <<< {"result":[[1581150811,1581153929,3118,44420000,0,1]],"id":15}
                              mihome-vacuum.0	2020-03-03 19:47:45.602	debug	(15538) sendMsg[1] >>> {"id":15,"method":"get_clean_record","params":[1581150811]}
                              mihome-vacuum.0	2020-03-03 19:47:45.508	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":14}
                              mihome-vacuum.0	2020-03-03 19:47:45.491	debug	(15538) 0. Mappointer_nomap___map_upload_handler
                              mihome-vacuum.0	2020-03-03 19:47:45.491	debug	(15538) sendMsg[1] >>> {"id":14,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:45.416	debug	(15538) Receive <<< {"result":[[1582118288,1582120675,2387,39517500,0,1]],"id":13}
                              mihome-vacuum.0	2020-03-03 19:47:45.401	debug	(15538) sendMsg[1] >>> {"id":13,"method":"get_clean_record","params":[1582118288]}
                              mihome-vacuum.0	2020-03-03 19:47:45.223	debug	(15538) Receive <<< {"result":[[1583060389,1583063854,3465,54702500,0,1]],"id":12}
                              mihome-vacuum.0	2020-03-03 19:47:45.201	debug	(15538) sendMsg[1] >>> {"id":12,"method":"get_clean_record","params":[1583060389]}
                              mihome-vacuum.0	2020-03-03 19:47:45.012	debug	(15538) Receive <<< {"result":[[1583244883,1583245887,1004,17005000,0,1]],"id":11}
                              mihome-vacuum.0	2020-03-03 19:47:44.999	debug	(15538) sendMsg[1] >>> {"id":11,"method":"get_clean_record","params":[1583244883]}
                              mihome-vacuum.0	2020-03-03 19:47:44.990	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":10}
                              mihome-vacuum.0	2020-03-03 19:47:44.984	debug	(15538) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
                              mihome-vacuum.0	2020-03-03 19:47:44.804	debug	(15538) Receive <<< {"result":[[1583248554,1583249170,616,8267500,0,1]],"id":9}
                              mihome-vacuum.0	2020-03-03 19:47:44.799	debug	(15538) sendMsg[1] >>> {"id":9,"method":"get_clean_record","params":[1583248554]}
                              mihome-vacuum.0	2020-03-03 19:47:44.794	debug	(15538) Receive <<< {"result":"unknown_method","id":8}
                              mihome-vacuum.0	2020-03-03 19:47:44.791	info	(15538) create state for carpet_mode
                              mihome-vacuum.0	2020-03-03 19:47:44.791	debug	(15538) Receive <<< {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":7}
                              mihome-vacuum.0	2020-03-03 19:47:44.785	debug	(15538) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
                              mihome-vacuum.0	2020-03-03 19:47:44.785	debug	(15538) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
                              mihome-vacuum.0	2020-03-03 19:47:44.615	debug	(15538) Receive <<< {"result":[[1583258556,1583258934,224,7165000,0,0]],"id":6}
                              mihome-vacuum.0	2020-03-03 19:47:44.598	debug	(15538) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1583258556]}
                              mihome-vacuum.0	2020-03-03 19:47:44.597	debug	(15538) Receive <<< {"result":[397771,6147175000,265,[1583258556,1583248554,1583244883,1583060389,1582118288,1581150811,1577708513,1577707998,1577705584,1577275556]],"id":5}
                              mihome-vacuum.0	2020-03-03 19:47:44.585	debug	(15538) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
                              mihome-vacuum.0	2020-03-03 19:47:44.416	debug	(15538) Receive <<< {"result":[{"main_brush_work_time":398002,"side_brush_work_time":398002,"filter_work_time":182552,"sensor_dirty_time":12991}],"id":4}
                              mihome-vacuum.0	2020-03-03 19:47:44.384	debug	(15538) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
                              mihome-vacuum.0	2020-03-03 19:47:44.238	info	(15538) set nächster Timer: Nicht verfügbar
                              mihome-vacuum.0	2020-03-03 19:47:44.192	debug	(15538) Receive <<< {"result":[90],"id":3}
                              mihome-vacuum.0	2020-03-03 19:47:44.185	debug	(15538) sendMsg[1] >>> {"id":3,"method":"get_sound_volume"}
                              mihome-vacuum.0	2020-03-03 19:47:44.157	error	(15538) TypeError: Cannot read property 'id' of undefined
                              mihome-vacuum.0	2020-03-03 19:47:44.128	debug	(15538) 25444
                              mihome-vacuum.0	2020-03-03 19:47:44.011	debug	(15538) Receive <<< {"partner_id":"","id":2,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.3.9_003468","ap":{"ssid":"Wlan","bssid":"21:9B:C2:F5:08:F7","rssi":-50},"netif":{"l
                              mihome-vacuum.0	2020-03-03 19:47:43.986	debug	(15538) Next WiFi check: 03.03 19:48
                              mihome-vacuum.0	2020-03-03 19:47:43.985	debug	(15538) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
                              mihome-vacuum.0	2020-03-03 19:47:43.783	info	(15538) Connected
                              mihome-vacuum.0	2020-03-03 19:47:43.755	debug	(15538) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                              mihome-vacuum.0	2020-03-03 19:47:43.754	debug	(15538) Receive <<< {"result":[{"msg_ver":8,"msg_seq":3337,"state":8,"battery":100,"clean_time":224,"clean_area":7165000,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0}
                              mihome-vacuum.0	2020-03-03 19:47:43.740	debug	(15538) sendMsg[1] >>> {"id":1,"method":"get_status"}
                              mihome-vacuum.0	2020-03-03 19:47:43.732	debug	(15538) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                              mihome-vacuum.0	2020-03-03 19:47:43.731	info	(15538) connecting, This can take up to 5 minutes ...
                              mihome-vacuum.0	2020-03-03 19:47:43.731	warn	(15538) Time difference between Mihome Vacuum and ioBroker: -90 sec
                              mihome-vacuum.0	2020-03-03 19:47:43.730	debug	(15538) Receive <<< Helo <<< 21310020000
                              mihome-vacuum.0	2020-03-03 19:47:43.720	info	(15538) New generation or new fw(3.3.9,003468) detected, create new states goto and zoneclean
                              mihome-vacuum.0	2020-03-03 19:47:43.711	debug	(15538) server started on 0.0.0.0:53421
                              mihome-vacuum.0	2020-03-03 19:47:43.707	info	(15538) Disconnect
                              mihome-vacuum.0	2020-03-03 19:47:43.703	info	(15538) Create state clean_home for controlling by cloud adapter
                              mihome-vacuum.0	2020-03-03 19:47:43.703	info	(15538) Expert mode enabled, states created
                              mihome-vacuum.0	2020-03-03 19:47:43.696	debug	(15538) load Map creator... true
                              mihome-vacuum.0	2020-03-03 19:47:43.669	info	(15538) starting. Version 2.0.8 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0
                              mihome-vacuum.0	2020-03-03 19:47:39.709	info	(10066) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              mihome-vacuum.0	2020-03-03 19:47:39.708	info	(10066) terminating
                              mihome-vacuum.0	2020-03-03 19:47:39.708	info	(10066) Got terminate signal TERMINATE_YOURSELF
                              

                              Nach Neustart des Adapters.

                              D 1 Reply Last reply
                              0
                              • J jensus11
                                mihome-vacuum.0	2020-03-03 19:48:03.714	debug	(15538) Receive <<< {"result":[{"msg_ver":8,"msg_seq":3338,"state":8,"battery":100,"clean_time":224,"clean_area":7165000,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0}
                                mihome-vacuum.0	2020-03-03 19:48:03.708	debug	(15538) sendMsg[1] >>> {"id":29,"method":"get_status"}
                                mihome-vacuum.0	2020-03-03 19:47:50.191	warn	(15538) Could not receive Mappointer, giving up
                                mihome-vacuum.0	2020-03-03 19:47:50.191	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":28}
                                mihome-vacuum.0	2020-03-03 19:47:50.182	debug	(15538) 9. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:50.182	debug	(15538) sendMsg[1] >>> {"id":28,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:49.681	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":27}
                                mihome-vacuum.0	2020-03-03 19:47:49.662	debug	(15538) 8. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:49.662	debug	(15538) sendMsg[1] >>> {"id":27,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:49.160	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":26}
                                mihome-vacuum.0	2020-03-03 19:47:49.156	debug	(15538) 7. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:49.155	debug	(15538) sendMsg[1] >>> {"id":26,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:48.654	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":25}
                                mihome-vacuum.0	2020-03-03 19:47:48.642	debug	(15538) 6. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:48.641	debug	(15538) sendMsg[1] >>> {"id":25,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:48.141	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":24}
                                mihome-vacuum.0	2020-03-03 19:47:48.117	debug	(15538) 5. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:48.117	debug	(15538) sendMsg[1] >>> {"id":24,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:47.616	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":23}
                                mihome-vacuum.0	2020-03-03 19:47:47.610	debug	(15538) 4. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:47.610	debug	(15538) sendMsg[1] >>> {"id":23,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:47.109	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":22}
                                mihome-vacuum.0	2020-03-03 19:47:47.105	debug	(15538) 3. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:47.104	debug	(15538) sendMsg[1] >>> {"id":22,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:46.607	debug	(15538) CLEAN_LOGGING[{"Datum":"3.3","Start":"19:02","Saugzeit":"4 min","Fläche":"7.17 m²","Error":0,"Ende":false},{"Datum":"3.3","Start":"16:15","Saugzeit":"10 min","Fläche":"8.27 m²","Error":0,"Ende
                                mihome-vacuum.0	2020-03-03 19:47:46.600	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":21}
                                mihome-vacuum.0	2020-03-03 19:47:46.588	debug	(15538) 2. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:46.588	debug	(15538) sendMsg[1] >>> {"id":21,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:46.434	debug	(15538) Receive <<< {"result":[[1577275556,1577275612,14,0,0,0]],"id":20}
                                mihome-vacuum.0	2020-03-03 19:47:46.405	debug	(15538) sendMsg[1] >>> {"id":20,"method":"get_clean_record","params":[1577275556]}
                                mihome-vacuum.0	2020-03-03 19:47:46.210	debug	(15538) Receive <<< {"result":[[1577705584,1577707390,1705,27040000,0,1]],"id":19}
                                mihome-vacuum.0	2020-03-03 19:47:46.204	debug	(15538) sendMsg[1] >>> {"id":19,"method":"get_clean_record","params":[1577705584]}
                                mihome-vacuum.0	2020-03-03 19:47:46.086	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":18}
                                mihome-vacuum.0	2020-03-03 19:47:46.024	debug	(15538) Receive <<< {"result":[[1577707998,1577708227,229,4305000,0,1]],"id":17}
                                mihome-vacuum.0	2020-03-03 19:47:46.008	debug	(15538) 1. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:46.008	debug	(15538) sendMsg[1] >>> {"id":18,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:46.004	debug	(15538) sendMsg[1] >>> {"id":17,"method":"get_clean_record","params":[1577707998]}
                                mihome-vacuum.0	2020-03-03 19:47:45.830	debug	(15538) Receive <<< {"result":[[1577708513,1577708756,243,3115000,0,1]],"id":16}
                                mihome-vacuum.0	2020-03-03 19:47:45.803	debug	(15538) sendMsg[1] >>> {"id":16,"method":"get_clean_record","params":[1577708513]}
                                mihome-vacuum.0	2020-03-03 19:47:45.617	debug	(15538) Receive <<< {"result":[[1581150811,1581153929,3118,44420000,0,1]],"id":15}
                                mihome-vacuum.0	2020-03-03 19:47:45.602	debug	(15538) sendMsg[1] >>> {"id":15,"method":"get_clean_record","params":[1581150811]}
                                mihome-vacuum.0	2020-03-03 19:47:45.508	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":14}
                                mihome-vacuum.0	2020-03-03 19:47:45.491	debug	(15538) 0. Mappointer_nomap___map_upload_handler
                                mihome-vacuum.0	2020-03-03 19:47:45.491	debug	(15538) sendMsg[1] >>> {"id":14,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:45.416	debug	(15538) Receive <<< {"result":[[1582118288,1582120675,2387,39517500,0,1]],"id":13}
                                mihome-vacuum.0	2020-03-03 19:47:45.401	debug	(15538) sendMsg[1] >>> {"id":13,"method":"get_clean_record","params":[1582118288]}
                                mihome-vacuum.0	2020-03-03 19:47:45.223	debug	(15538) Receive <<< {"result":[[1583060389,1583063854,3465,54702500,0,1]],"id":12}
                                mihome-vacuum.0	2020-03-03 19:47:45.201	debug	(15538) sendMsg[1] >>> {"id":12,"method":"get_clean_record","params":[1583060389]}
                                mihome-vacuum.0	2020-03-03 19:47:45.012	debug	(15538) Receive <<< {"result":[[1583244883,1583245887,1004,17005000,0,1]],"id":11}
                                mihome-vacuum.0	2020-03-03 19:47:44.999	debug	(15538) sendMsg[1] >>> {"id":11,"method":"get_clean_record","params":[1583244883]}
                                mihome-vacuum.0	2020-03-03 19:47:44.990	debug	(15538) Receive <<< {"result":["map_upload_handler"],"id":10}
                                mihome-vacuum.0	2020-03-03 19:47:44.984	debug	(15538) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
                                mihome-vacuum.0	2020-03-03 19:47:44.804	debug	(15538) Receive <<< {"result":[[1583248554,1583249170,616,8267500,0,1]],"id":9}
                                mihome-vacuum.0	2020-03-03 19:47:44.799	debug	(15538) sendMsg[1] >>> {"id":9,"method":"get_clean_record","params":[1583248554]}
                                mihome-vacuum.0	2020-03-03 19:47:44.794	debug	(15538) Receive <<< {"result":"unknown_method","id":8}
                                mihome-vacuum.0	2020-03-03 19:47:44.791	info	(15538) create state for carpet_mode
                                mihome-vacuum.0	2020-03-03 19:47:44.791	debug	(15538) Receive <<< {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":7}
                                mihome-vacuum.0	2020-03-03 19:47:44.785	debug	(15538) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
                                mihome-vacuum.0	2020-03-03 19:47:44.785	debug	(15538) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
                                mihome-vacuum.0	2020-03-03 19:47:44.615	debug	(15538) Receive <<< {"result":[[1583258556,1583258934,224,7165000,0,0]],"id":6}
                                mihome-vacuum.0	2020-03-03 19:47:44.598	debug	(15538) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1583258556]}
                                mihome-vacuum.0	2020-03-03 19:47:44.597	debug	(15538) Receive <<< {"result":[397771,6147175000,265,[1583258556,1583248554,1583244883,1583060389,1582118288,1581150811,1577708513,1577707998,1577705584,1577275556]],"id":5}
                                mihome-vacuum.0	2020-03-03 19:47:44.585	debug	(15538) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
                                mihome-vacuum.0	2020-03-03 19:47:44.416	debug	(15538) Receive <<< {"result":[{"main_brush_work_time":398002,"side_brush_work_time":398002,"filter_work_time":182552,"sensor_dirty_time":12991}],"id":4}
                                mihome-vacuum.0	2020-03-03 19:47:44.384	debug	(15538) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
                                mihome-vacuum.0	2020-03-03 19:47:44.238	info	(15538) set nächster Timer: Nicht verfügbar
                                mihome-vacuum.0	2020-03-03 19:47:44.192	debug	(15538) Receive <<< {"result":[90],"id":3}
                                mihome-vacuum.0	2020-03-03 19:47:44.185	debug	(15538) sendMsg[1] >>> {"id":3,"method":"get_sound_volume"}
                                mihome-vacuum.0	2020-03-03 19:47:44.157	error	(15538) TypeError: Cannot read property 'id' of undefined
                                mihome-vacuum.0	2020-03-03 19:47:44.128	debug	(15538) 25444
                                mihome-vacuum.0	2020-03-03 19:47:44.011	debug	(15538) Receive <<< {"partner_id":"","id":2,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.3.9_003468","ap":{"ssid":"Wlan","bssid":"21:9B:C2:F5:08:F7","rssi":-50},"netif":{"l
                                mihome-vacuum.0	2020-03-03 19:47:43.986	debug	(15538) Next WiFi check: 03.03 19:48
                                mihome-vacuum.0	2020-03-03 19:47:43.985	debug	(15538) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
                                mihome-vacuum.0	2020-03-03 19:47:43.783	info	(15538) Connected
                                mihome-vacuum.0	2020-03-03 19:47:43.755	debug	(15538) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                                mihome-vacuum.0	2020-03-03 19:47:43.754	debug	(15538) Receive <<< {"result":[{"msg_ver":8,"msg_seq":3337,"state":8,"battery":100,"clean_time":224,"clean_area":7165000,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0}
                                mihome-vacuum.0	2020-03-03 19:47:43.740	debug	(15538) sendMsg[1] >>> {"id":1,"method":"get_status"}
                                mihome-vacuum.0	2020-03-03 19:47:43.732	debug	(15538) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                                mihome-vacuum.0	2020-03-03 19:47:43.731	info	(15538) connecting, This can take up to 5 minutes ...
                                mihome-vacuum.0	2020-03-03 19:47:43.731	warn	(15538) Time difference between Mihome Vacuum and ioBroker: -90 sec
                                mihome-vacuum.0	2020-03-03 19:47:43.730	debug	(15538) Receive <<< Helo <<< 21310020000
                                mihome-vacuum.0	2020-03-03 19:47:43.720	info	(15538) New generation or new fw(3.3.9,003468) detected, create new states goto and zoneclean
                                mihome-vacuum.0	2020-03-03 19:47:43.711	debug	(15538) server started on 0.0.0.0:53421
                                mihome-vacuum.0	2020-03-03 19:47:43.707	info	(15538) Disconnect
                                mihome-vacuum.0	2020-03-03 19:47:43.703	info	(15538) Create state clean_home for controlling by cloud adapter
                                mihome-vacuum.0	2020-03-03 19:47:43.703	info	(15538) Expert mode enabled, states created
                                mihome-vacuum.0	2020-03-03 19:47:43.696	debug	(15538) load Map creator... true
                                mihome-vacuum.0	2020-03-03 19:47:43.669	info	(15538) starting. Version 2.0.8 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0
                                mihome-vacuum.0	2020-03-03 19:47:39.709	info	(10066) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                mihome-vacuum.0	2020-03-03 19:47:39.708	info	(10066) terminating
                                mihome-vacuum.0	2020-03-03 19:47:39.708	info	(10066) Got terminate signal TERMINATE_YOURSELF
                                

                                Nach Neustart des Adapters.

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

                                @jensus11 Hmmm, ich glaube, da muss @Meistertr meistertmal einen Blick drauf werfen. Aber das ist aktuell der Adapter von mir, nehme zur Sicherheit hat 2.0.7 vom offiziellen Community github.

                                1 Reply Last reply
                                0
                                • J Offline
                                  J Offline
                                  jensus11
                                  wrote on last edited by
                                  #492

                                  Hatte 2.0.6 dann 2.0.7 und jetzt die von dir. Bei den anderen ging das auch nicht.

                                  MeistertrM 1 Reply Last reply
                                  0
                                  • J jensus11

                                    Hatte 2.0.6 dann 2.0.7 und jetzt die von dir. Bei den anderen ging das auch nicht.

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

                                    @jensus11 hast du valetudo in der config angeklickt? auf jedenfall hast du Xiaomi map mit angeklickt, was nicht sollte wenn du valetudo installiert hast

                                    D 1 Reply Last reply
                                    0
                                    • J Offline
                                      J Offline
                                      jensus11
                                      wrote on last edited by jensus11
                                      #494

                                      81D24DBD-9BAF-4434-BDE0-45FE3AB425B9.jpeg

                                      So habe ich das eingestellt.

                                      1 Reply Last reply
                                      0
                                      • MeistertrM Meistertr

                                        @jensus11 hast du valetudo in der config angeklickt? auf jedenfall hast du Xiaomi map mit angeklickt, was nicht sollte wenn du valetudo installiert hast

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

                                        @Meistertr sagte in Test Adapter mihome-vacuum v2.0.x:

                                        @jensus11 hast du valetudo in der config angeklickt? auf jedenfall hast du Xiaomi map mit angeklickt, was nicht sollte wenn du valetudo installiert hast

                                        Sollten wir dann da Radio Buttons von machen?

                                        MeistertrM 1 Reply Last reply
                                        0
                                        • D dirkhe

                                          @Meistertr sagte in Test Adapter mihome-vacuum v2.0.x:

                                          @jensus11 hast du valetudo in der config angeklickt? auf jedenfall hast du Xiaomi map mit angeklickt, was nicht sollte wenn du valetudo installiert hast

                                          Sollten wir dann da Radio Buttons von machen?

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

                                          @dirkhe jep wollte da noch ein deselect mit einbauen das nur eins geht

                                          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

                                          659

                                          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