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

    NEWS

    • NEWS von ioBroker im Blog!

    • Cloud/Vis-Offline-Weihnachtsangebot 2024

    • js-controller Lucy (Version 7.0) jetzt im Stable Repository

    Test Adapter mihome-vacuum v2.0.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Coffeelover @volx3eet last edited by

      @volx3eet Hi. Du brauchst nur die Koordinaten. Mein Robbie ist schon so alt, der kann von sich aus garkeine Zonen. 🙂

      1 Reply Last reply Reply Quote 1
      • J
        Jaschkopf last edited by

        Servus, ich schon wieder. Ich habe jetzt vor ein paar Tagen beide beiden Roborock S50 mal komplett platt gemacht und auf Werkseinstellung zurück gesetzt. Danach beide auf die neuste Firmware geupdatet (3.5.7_002008). Das Update musste ich allerdings über die FloleVac App machen, weil es mir von Xiaomi Home nicht angeboten wurde.

        Trotzdem bricht immer noch die Verbindung zu meinem Erdgeschoss Roby ab. Ich habe die Verbindung mal per FLot aufgezeichnet und er trennt sich immer Nachts um 4Uhr. Im Log sieht man das einfach keine Daten mehr rein kommen.

        [{"msg_ver":3,"msg_seq":4172,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2911}
2020-12-20 03:58:43.981  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2913,"method":"get_status"}
2020-12-20 03:58:44.004  - debug: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4173,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2913}
2020-12-20 03:59:03.982  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2914,"method":"get_status"}
2020-12-20 03:59:03.997  - debug: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4174,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2914}
2020-12-20 03:59:23.988  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2915,"method":"get_status"}
2020-12-20 03:59:23.989  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2916,"method":"miIO.info"}
2020-12-20 03:59:23.989  - debug: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:00
2020-12-20 03:59:24.005  - debug: mihome-vacuum.0 (1071) Receive <<< {"partner_id":"","id":2916,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.7_002008","ap":{"ssid":"Laterne","bssid":"E8:DF:70:9E:5E:3D","rssi":-51},"netif":{"localIp":"192.168.178.27","mask":"255.255.255.0","gw":"192.168.178.1"},"model":"roborock.vacuum.s5","mac":"40:31:3C:AD:47:63","token":"4d747171777057373650316871615437","life":86362}}
2020-12-20 03:59:24.006  - debug: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4175,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2915}
2020-12-20 03:59:43.989  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2917,"method":"get_status"}
2020-12-20 03:59:44.008  - debug: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4176,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2917}
2020-12-20 04:00:00.019  - info: host.iobroker instance system.adapter.dwd.0 started with pid 3184
2020-12-20 04:00:03.990  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:07.268  - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-12-20 04:00:08.991  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:13.993  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:18.994  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2918 received, giving up
2020-12-20 04:00:23.994  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:23.997  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:23.997  - debug: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:28.997  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:28.998  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:28.999  - debug: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:33.998  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:33.999  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:33.999  - debug: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:38.999  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2919 received, giving up
2020-12-20 04:00:38.999  - debug: mihome-vacuum.0 (1071) no answer for miIO.info id:2920 received, giving up
2020-12-20 04:00:39.000  - warn: mihome-vacuum.0 (1071) no answer received after 3 times -> pause miIO.info try again in one hour
2020-12-20 04:00:39.000  - debug: mihome-vacuum.0 (1071) Next WiFi check: 20.12 05:00
2020-12-20 04:00:43.998  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:48.999  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:54.000  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:59.001  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2921 received, giving up
2020-12-20 04:01:03.999  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:09.000  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:14.001  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:19.002  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2922 received, giving up
2020-12-20 04:01:24.000  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:29.001  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:34.003  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:39.003  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2923 received, giving up
2020-12-20 04:01:44.002  - debug: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:49.004  - debug: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:54.005  - debug: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:59.006  - debug: mihome-vacuum.0 (1071) no answer for get_status id:2924 received, giving up
2020-12-20 04:02:04.004  - info: mihome-vacuum.0 (1071) Disconnected due last Restponse of 03:59:44.010

        Alles andere läuft problemlos im Netzwerk. Der Roby bleibt dann genau 24h offline und dann wieder Nachts um 4Uhr kann er die Verbindung wiederherstellen.

        Kann das am Germany Server liegen? Über welchen Server habt ihr eure Robys laufen?

        Gruß Jaschkopf

        Meistertr 1 Reply Last reply Reply Quote 0
        • Meistertr
          Meistertr Developer @Jaschkopf last edited by

          @Jaschkopf nein ist ist ein verbindungsptobleme durch deine netzwerkhardware. Um 4 Uhr macht der Roboter einen reboot danach kann er sich scheinbar nicht mehr verbinden. Er ist und beim nächsten reboot geht es dann wieder. Kann am robbi oder dem Router liegen. Ich jedoch nicht am Adapter selbst.

          1 Reply Last reply Reply Quote 0
          • V
            volx3eet last edited by

            Hallo zusammen,

            ich hab nochmal eine Frage. In der MiHome-App gibt es ja die Karte in der die Ladestation steht. Dort kann man ja dann Räume und Zonen etc. einstellen und speichern. Diese Karte kann ich auch in der App immer wieder herstellen, wenn ich z.b. auf einer weiteren Etage gesaugt habe.

            Gibt es im Adapter irgendeine Möglichkeit zwischen der manuellen und der automatischen Karte in der App per Befehl zu wechseln? (getMap oder load map o.ä?)

            Danke und VG
            Volx

            1 Reply Last reply Reply Quote 0
            • S
              Spampunk @Spampunk last edited by Spampunk

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

              Welche Ports müssen denn dafür offen sein? Meine F/W hat nur die Standard-Einstellungen (Fritzbox), da ist nichts sonderlich geblockt oder so.

              Wie lautet denn die Server-Adresse? Ich könnte ja mal einen Ping versuchen.

              Ich bekomme leider trotz diverser Anstrengungen keine Kartenhinweise in den DPs mihome-vacuum.0.map.map64, bzw. mihome-vacuum.0.map.mapURL.

              Aber wenn ich als command get_map_v1 sende, bekomme ich ["rubyslite%2F391549510%2F7"] zurück. Kann man damit etwas anfangen, um an die Karte zu kommen?

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

                @Spampunk ich kenne dein log ja nicht, aber das ger Map macht der Adapter ja auch. Mit der Antwort versucht er ja dann die Karte zu holen und zu interpretieren. Mach dein Log mal auf debug oder Silly, dann siehst du das

                S 1 Reply Last reply Reply Quote 0
                • V
                  volx3eet last edited by

                  @dirkhe Ich hab eine Karte mit vielen Räumen. Ich würde gerne in der VIS verschieden Raumkombinationen als Button hinterlegen. Kann ich dafür mihome-vacuum.0.rooms.multiRoomClean einfach kopieren und jeweils andere Räume zuordnen?

                  VG
                  Volx

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

                    @volx3eet Nein, den kannst du nicht kopieren. Du kannst Timer erstellen und den deaktivieren oder keinen Tag zuweisen. Den kannst du dann verschiedene Räume zuweisen. Über vis oder Script kannst du den dann "jetzt starten".

                    S V 2 Replies Last reply Reply Quote 1
                    • S
                      Sneaker75 @dirkhe last edited by

                      Seit dem Update auf Node.js v12.18.3 funktioniert in ioBroker die Kartendarstellung nicht mehr bei mir. Ich habe einen Roborock S5 und der ioBroker läuft auf einem Raspberry4. Ich habe gelesen, dass das eventuell mit "canvas" zusammenhängt. Wie kann ich das wieder fixen? Beim Neustart des Adapters kommt keine Fehlermeldung im Log.

                      ilovegym 1 Reply Last reply Reply Quote 0
                      • ilovegym
                        ilovegym Forum Testing @Sneaker75 last edited by

                        @Sneaker75 moin,
                        Steht in der Anleitung unter Installation 🙂

                        1 Reply Last reply Reply Quote 1
                        • V
                          volx3eet @dirkhe last edited by

                          @dirkhe Danke für den Hinweis. Ich versuche m die Timervariante zu realisieren.

                          Volx

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

                            @dirkhe

                            mihome-vacuum.0	2020-12-30 12:33:26.207	debug	(21720) Receive <<< {"result":[{"msg_ver":2,"msg_seq":1630,"state":8,"battery":100,"clean_time":633,"clean_area":7790000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state
mihome-vacuum.0	2020-12-30 12:33:26.195	debug	(21720) sendMsg[1] >>> {"id":36,"method":"get_status"}
mihome-vacuum.0	2020-12-30 12:33:08.221	debug	(21720) Mappointer_updated
mihome-vacuum.0	2020-12-30 12:33:08.221	debug	(21720) Receive <<< {"result":["rubyslite%2F391549510%2F2"],"id":35}
mihome-vacuum.0	2020-12-30 12:33:08.210	debug	(21720) sendMsg[1] >>> {"id":35,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-30 12:33:06.720	debug	(21720) Receive <<< {"result":[58666,930945000,57,[1608908397,1608713205,1608712956,1608455177,1608191161,1607671956,1607456532,1607454272,1607454221,1607453175,1607453044,1607452925,1607452864,160745
mihome-vacuum.0	2020-12-30 12:33:06.708	debug	(21720) sendMsg[1] >>> {"id":34,"method":"get_clean_summary"}
mihome-vacuum.0	2020-12-30 12:33:06.214	debug	(21720) Receive <<< {"result":[{"main_brush_work_time":59055,"side_brush_work_time":59055,"filter_work_time":59055,"filter_element_work_time":25310,"sensor_dirty_time":27041}],"id":33}
mihome-vacuum.0	2020-12-30 12:33:06.206	debug	(21720) sendMsg[1] >>> {"id":33,"method":"get_consumable"}
mihome-vacuum.0	2020-12-30 12:33:06.203	info	(21720) create states for water box filter
mihome-vacuum.0	2020-12-30 12:33:06.202	info	(21720) create states for water box
mihome-vacuum.0	2020-12-30 12:33:06.199	debug	(21720) Receive <<< {"result":[{"msg_ver":2,"msg_seq":1629,"state":8,"battery":100,"clean_time":633,"clean_area":7790000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state
mihome-vacuum.0	2020-12-30 12:33:06.189	debug	(21720) sendMsg[1] >>> {"id":32,"method":"get_status"}
mihome-vacuum.0	2020-12-30 12:32:54.039	debug	(21720) system.adapter.admin.0: logging true
mihome-vacuum.0	2020-12-30 12:32:51.331	debug	(21720) CLEAN_LOGGING[{"Datum":"25.12","Start":"15:59","Saugzeit":"11 min","Fläche":"7.79 m²","Error":0,"Ende":true},{"Datum":"23.12","Start":"09:46","Saugzeit":"91 min","Fläche":"76.64 m²","Error":0
mihome-vacuum.0	2020-12-30 12:32:51.137	debug	(21720) Receive <<< {"result":[[1607367090,1607367115,20,0,0,0,2,3,43]],"id":31}
mihome-vacuum.0	2020-12-30 12:32:51.125	debug	(21720) sendMsg[1] >>> {"id":31,"method":"get_clean_record","params":[1607367090]}
mihome-vacuum.0	2020-12-30 12:32:50.931	debug	(21720) Receive <<< {"result":[[1607367125,1607367186,58,1732500,0,0,2,3,43]],"id":30}
mihome-vacuum.0	2020-12-30 12:32:50.920	debug	(21720) sendMsg[1] >>> {"id":30,"method":"get_clean_record","params":[1607367125]}
mihome-vacuum.0	2020-12-30 12:32:50.726	debug	(21720) Receive <<< {"result":[[1607367191,1607367199,3,0,0,0,2,3,43]],"id":29}
mihome-vacuum.0	2020-12-30 12:32:50.717	debug	(21720) sendMsg[1] >>> {"id":29,"method":"get_clean_record","params":[1607367191]}
mihome-vacuum.0	2020-12-30 12:32:50.522	debug	(21720) Receive <<< {"result":[[1607367205,1607367233,23,0,0,0,2,3,43]],"id":28}
mihome-vacuum.0	2020-12-30 12:32:50.513	debug	(21720) sendMsg[1] >>> {"id":28,"method":"get_clean_record","params":[1607367205]}
mihome-vacuum.0	2020-12-30 12:32:50.317	debug	(21720) Receive <<< {"result":[[1607367239,1607367286,22,0,0,0,2,3,60]],"id":27}
mihome-vacuum.0	2020-12-30 12:32:50.307	debug	(21720) sendMsg[1] >>> {"id":27,"method":"get_clean_record","params":[1607367239]}
mihome-vacuum.0	2020-12-30 12:32:50.112	debug	(21720) Receive <<< {"result":[[1607414181,1607417452,3271,57070000,0,1,2,1,52]],"id":26}
mihome-vacuum.0	2020-12-30 12:32:50.104	debug	(21720) sendMsg[1] >>> {"id":26,"method":"get_clean_record","params":[1607414181]}
mihome-vacuum.0	2020-12-30 12:32:49.910	debug	(21720) Receive <<< {"result":[[1607452639,1607452684,14,0,0,0,2,3,43]],"id":25}
mihome-vacuum.0	2020-12-30 12:32:49.900	debug	(21720) sendMsg[1] >>> {"id":25,"method":"get_clean_record","params":[1607452639]}
mihome-vacuum.0	2020-12-30 12:32:49.709	debug	(21720) Receive <<< {"result":[[1607452864,1607452911,30,257500,0,0,2,3,43]],"id":24}
mihome-vacuum.0	2020-12-30 12:32:49.696	debug	(21720) sendMsg[1] >>> {"id":24,"method":"get_clean_record","params":[1607452864]}
mihome-vacuum.0	2020-12-30 12:32:49.501	debug	(21720) Receive <<< {"result":[[1607452925,1607453028,103,4085000,0,0,2,3,43]],"id":23}
mihome-vacuum.0	2020-12-30 12:32:49.492	debug	(21720) sendMsg[1] >>> {"id":23,"method":"get_clean_record","params":[1607452925]}
mihome-vacuum.0	2020-12-30 12:32:49.297	debug	(21720) Receive <<< {"result":[[1607453044,1607453165,121,1250000,0,0,2,3,43]],"id":22}
mihome-vacuum.0	2020-12-30 12:32:49.289	debug	(21720) sendMsg[1] >>> {"id":22,"method":"get_clean_record","params":[1607453044]}
mihome-vacuum.0	2020-12-30 12:32:49.173	debug	(21720) Mappointer_updated
mihome-vacuum.0	2020-12-30 12:32:49.171	debug	(21720) Receive <<< {"result":["rubyslite%2F391549510%2F1"],"id":21}
mihome-vacuum.0	2020-12-30 12:32:49.164	debug	(21720) 2. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-30 12:32:49.162	debug	(21720) sendMsg[1] >>> {"id":21,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-30 12:32:49.092	debug	(21720) Receive <<< {"result":[[1607453175,1607453310,60,1165000,0,0,2,3,43]],"id":20}
mihome-vacuum.0	2020-12-30 12:32:49.083	debug	(21720) sendMsg[1] >>> {"id":20,"method":"get_clean_record","params":[1607453175]}
mihome-vacuum.0	2020-12-30 12:32:48.887	debug	(21720) Receive <<< {"result":[[1607454221,1607454247,26,562500,0,0,2,3,43]],"id":19}
mihome-vacuum.0	2020-12-30 12:32:48.878	debug	(21720) sendMsg[1] >>> {"id":19,"method":"get_clean_record","params":[1607454221]}
mihome-vacuum.0	2020-12-30 12:32:48.683	debug	(21720) Receive <<< {"result":[[1607454272,1607454305,30,1482500,0,0,2,3,43]],"id":18}
mihome-vacuum.0	2020-12-30 12:32:48.674	debug	(21720) sendMsg[1] >>> {"id":18,"method":"get_clean_record","params":[1607454272]}
mihome-vacuum.0	2020-12-30 12:32:48.659	debug	(21720) Receive <<< {"result":["retry"],"id":17}
mihome-vacuum.0	2020-12-30 12:32:48.651	debug	(21720) 1. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-30 12:32:48.649	debug	(21720) sendMsg[1] >>> {"id":17,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-30 12:32:48.478	debug	(21720) Receive <<< {"result":[[1607456532,1607456997,286,2892500,0,0,2,1,64]],"id":16}
mihome-vacuum.0	2020-12-30 12:32:48.470	debug	(21720) sendMsg[1] >>> {"id":16,"method":"get_clean_record","params":[1607456532]}
mihome-vacuum.0	2020-12-30 12:32:48.274	debug	(21720) Receive <<< {"result":[[1607671956,1607677665,5430,77355000,0,1,2,1,52]],"id":15}
mihome-vacuum.0	2020-12-30 12:32:48.264	debug	(21720) sendMsg[1] >>> {"id":15,"method":"get_clean_record","params":[1607671956]}
mihome-vacuum.0	2020-12-30 12:32:48.145	debug	(21720) Receive <<< {"result":["retry"],"id":14}
mihome-vacuum.0	2020-12-30 12:32:48.138	debug	(21720) 0. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-30 12:32:48.136	debug	(21720) sendMsg[1] >>> {"id":14,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-30 12:32:48.068	debug	(21720) Receive <<< {"result":[[1608191161,1608204778,5591,78172500,0,1,2,1,52]],"id":13}
mihome-vacuum.0	2020-12-30 12:32:48.058	debug	(21720) sendMsg[1] >>> {"id":13,"method":"get_clean_record","params":[1608191161]}
mihome-vacuum.0	2020-12-30 12:32:47.864	debug	(21720) Receive <<< {"result":[[1608455177,1608455630,453,7960000,0,1,2,3,56]],"id":12}
mihome-vacuum.0	2020-12-30 12:32:47.852	debug	(21720) sendMsg[1] >>> {"id":12,"method":"get_clean_record","params":[1608455177]}
mihome-vacuum.0	2020-12-30 12:32:47.659	debug	(21720) Receive <<< {"result":[[1608712956,1608712963,7,0,0,0,2,1,60]],"id":11}
mihome-vacuum.0	2020-12-30 12:32:47.648	debug	(21720) sendMsg[1] >>> {"id":11,"method":"get_clean_record","params":[1608712956]}
mihome-vacuum.0	2020-12-30 12:32:47.629	debug	(21720) Receive <<< {"result":["retry"],"id":10}
mihome-vacuum.0	2020-12-30 12:32:47.620	debug	(21720) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-30 12:32:47.453	debug	(21720) Receive <<< {"result":[[1608713205,1608719264,5488,76642500,0,1,2,1,52]],"id":9}
mihome-vacuum.0	2020-12-30 12:32:47.444	debug	(21720) sendMsg[1] >>> {"id":9,"method":"get_clean_record","params":[1608713205]}
mihome-vacuum.0	2020-12-30 12:32:47.441	debug	(21720) Receive <<< {"result":[[16,"578001018676"],[17,"578001018675"],[18,"578001018677"],[19,"578001018618"],[20,"578001018680"],[21,"578001018679"],[22,"578001018682"],[24,"578001018678"],[25,"578
mihome-vacuum.0	2020-12-30 12:32:47.439	info	(21720) create state for carpet_mode
mihome-vacuum.0	2020-12-30 12:32:47.438	debug	(21720) Receive <<< {"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":7}
mihome-vacuum.0	2020-12-30 12:32:47.428	debug	(21720) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
mihome-vacuum.0	2020-12-30 12:32:47.421	debug	(21720) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
mihome-vacuum.0	2020-12-30 12:32:47.245	debug	(21720) Receive <<< {"result":[[1608908397,1608909030,633,7790000,0,1,2,3,56]],"id":6}
mihome-vacuum.0	2020-12-30 12:32:47.238	debug	(21720) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1608908397]}
mihome-vacuum.0	2020-12-30 12:32:47.233	debug	(21720) Receive <<< {"result":[58666,930945000,57,[1608908397,1608713205,1608712956,1608455177,1608191161,1607671956,1607456532,1607454272,1607454221,1607453175,1607453044,1607452925,1607452864,16074
mihome-vacuum.0	2020-12-30 12:32:47.221	debug	(21720) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
mihome-vacuum.0	2020-12-30 12:32:47.032	debug	(21720) Receive <<< {"result":[{"main_brush_work_time":59055,"side_brush_work_time":59055,"filter_work_time":59055,"filter_element_work_time":25310,"sensor_dirty_time":27041}],"id":4}
mihome-vacuum.0	2020-12-30 12:32:47.021	debug	(21720) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
mihome-vacuum.0	2020-12-30 12:32:46.827	debug	(21720) Receive <<< {"result":[90],"id":3}
mihome-vacuum.0	2020-12-30 12:32:46.820	debug	(21720) sendMsg[1] >>> {"id":3,"method":"get_sound_volume"}
mihome-vacuum.0	2020-12-30 12:32:46.749	info	(21720) set nächster Timer: Nicht verfügbar
mihome-vacuum.0	2020-12-30 12:32:46.632	debug	(21720) Receive <<< {"partner_id":"","id":2,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_1026","ap":{"ssid":"BoxiNet","bssid":"2c:91:ab:86:51:a4","rssi":-69},"netif":{"localIp":
mihome-vacuum.0	2020-12-30 12:32:46.629	debug	(21720) Next WiFi check: 30.12 12:33
mihome-vacuum.0	2020-12-30 12:32:46.623	debug	(21720) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
mihome-vacuum.0	2020-12-30 12:32:46.416	info	(21720) Connected
mihome-vacuum.0	2020-12-30 12:32:46.397	debug	(21720) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-30 12:32:46.393	debug	(21720) Receive <<< {"result":[{"msg_ver":2,"msg_seq":1628,"state":8,"battery":100,"clean_time":633,"clean_area":7790000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_stat
mihome-vacuum.0	2020-12-30 12:32:46.375	debug	(21720) sendMsg[1] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2020-12-30 12:32:46.284	debug	(21720) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-30 12:32:46.283	info	(21720) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2020-12-30 12:32:46.281	debug	(21720) Receive <<< Helo <<< 2131002000000000175692465fec655effffffffffffffffffffffffffffffff
mihome-vacuum.0	2020-12-30 12:32:46.271	info	(21720) New generation or new fw(3.5.8,1026) detected, create new states goto and zoneclean
mihome-vacuum.0	2020-12-30 12:32:46.263	debug	(21720) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
mihome-vacuum.0	2020-12-30 12:32:46.192	debug	(21720) server started on 0.0.0.0:53421
mihome-vacuum.0	2020-12-30 12:32:46.175	info	(21720) Create state clean_home for controlling by cloud adapter
mihome-vacuum.0	2020-12-30 12:32:46.173	info	(21720) Expert mode enabled, states created
mihome-vacuum.0	2020-12-30 12:32:46.161	debug	(21720) Xiaomi Cloud: Logging in
mihome-vacuum.0	2020-12-30 12:32:46.158	debug	(21720) load Map creator... true
mihome-vacuum.0	2020-12-30 12:32:46.014	info	(21720) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.0, js-controller: 3.1.6
mihome-vacuum.0	2020-12-30 12:32:43.640	debug	(21720) statesDB connected
mihome-vacuum.0	2020-12-30 12:32:43.638	debug	(21720) States connected to redis: 127.0.0.1:9000
mihome-vacuum.0	2020-12-30 12:32:43.604	debug	(21720) States create System PubSub Client
mihome-vacuum.0	2020-12-30 12:32:43.598	debug	(21720) States create User PubSub Client
mihome-vacuum.0	2020-12-30 12:32:43.578	debug	(21720) Redis States: Use Redis connection: 127.0.0.1:9000
mihome-vacuum.0	2020-12-30 12:32:43.575	debug	(21720) objectDB connected
mihome-vacuum.0	2020-12-30 12:32:43.562	debug	(21720) Objects connected to redis: 127.0.0.1:9001
mihome-vacuum.0	2020-12-30 12:32:43.531	debug	(21720) Objects client initialize lua scripts
mihome-vacuum.0	2020-12-30 12:32:43.530	debug	(21720) Objects create User PubSub Client
mihome-vacuum.0	2020-12-30 12:32:43.528	debug	(21720) Objects create System PubSub Client
mihome-vacuum.0	2020-12-30 12:32:43.521	debug	(21720) Objects client ready ... initialize now
mihome-vacuum.0	2020-12-30 12:32:43.452	debug	(21720) Redis Objects: Use Redis connection: 127.0.0.1:9001

                            In Zeile 37 gibt er die Karten-URL an den Adapter, stimmt. Aber warum verbindet er sich nicht mit dem Server? Kann ich mich versuchen, händisch einzuloggen? Wie dann?

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

                              @Spampunk ich bin da nicht so tief drin, habe aber gerade mal in den Code geschaut. Was hast du denn nun den settings für eine Karte eingestellt?

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

                                @dirkhe
                                Ein frohes Neues Jahr! 😊

                                Ich habe einmal Screenshots meiner Adapter-Einstellungen gemacht.

                                Screenshot 2021-01-01 122327.png
                                Screenshot 2021-01-01 122250.png
                                Screenshot 2021-01-01 122228.png

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Spampunk last edited by

                                  Wenn ich einzelne Räume anfahren möchte, bekomme ich folgende Fehlermeldung im Log:

                                  mihome-vacuum.0	2021-01-01 13:15:02.549	info	(3933) terminating
mihome-vacuum.0	2021-01-01 13:15:02.493	error	(3933) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:187:68 at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesI
mihome-vacuum.0	2021-01-01 13:15:02.491	error	(3933) uncaught exception: Cannot read property 'val' of null
mihome-vacuum.0	2021-01-01 13:15:02.481	info	(3933) trigger cleaning segment 20
mihome-vacuum.0	2021-01-01 13:14:09.645	info	(3933) create states for water box filter
mihome-vacuum.0	2021-01-01 13:14:09.644	info	(3933) create states for water box
mihome-vacuum.0	2021-01-01 13:14:00.678	info	(3933) create state for carpet_mode
mihome-vacuum.0	2021-01-01 13:13:59.668	info	(3933) Connected

                                  Ich verwende mihome vacuum Adapter Version 2.1.1

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Spampunk last edited by

                                    So langsam setzt der Frust ein. Ich habe jetzt wohl so alles durch, was in meiner Macht steht, um Zugriff zur Cloud zu bekommen.

                                    • Kompletter Reset des Saugers
                                    • Xiaomi-Konto komplett gelöscht und neu angelegt mit (auch mit anderer E-Mail-Adresse)
                                    • Adapter komplett gelöscht und neu installiert
                                    • Versucht, die Anmeldung direkt auf dem ioBroker-Server vorzunehmen
                                    • Versucht den Code zu verstehen (und total gescheitert)

                                    Händisch kann ich mich unter https://account.xiaomi.com anmelden, auch vom ioBroker-Server aus.

                                    Also, woran kann es noch liegen???

                                    Ich wäre echt dankbar, wenn das einer der Entwickler mit mir gemeinsam durchgehen könnte.

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

                                      @Spampunk das mit der Karte kenne ich auch nicht, für den anderen Fehler mit dem Raum, da mach nochmal auf debug bitte.

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

                                        @dirkhe
                                        Bis jetzt habe ich den Fehler nicht mehr gesehen. Ich melde mich, wenn er wiederkommen sollte.

                                        Wer kann mir denn da weiterhelfen mit der Cloud?

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          GrillKoenig @Meistertr last edited by

                                          @Meistertr
                                          Moin!
                                          Leider rausche ich in das gleiche Problem rein, kann aber keine Ursache ausmachen. Seit dem 14.12. bekomme ich keine Karte mehr aktualisiert. Und es ist wie immer "ich habe nichts gemacht" 😉

                                          relev. LogFile:

                                          mihome-vacuum.0	2021-01-04 12:27:19.433	debug	(8440) Next WiFi check: 04.01 12:28
mihome-vacuum.0	2021-01-04 12:27:19.433	debug	(8440) sendMsg[1] >>> {"id":78,"method":"miIO.info"}
mihome-vacuum.0	2021-01-04 12:27:19.432	debug	(8440) sendMsg[1] >>> {"id":77,"method":"get_status"}
mihome-vacuum.0	2021-01-04 12:27:16.690	debug	(8440) Mappointer_updated
mihome-vacuum.0	2021-01-04 12:27:16.689	debug	(8440) Receive <<< {"result":["robomap%2F118226113%2F7"],"id":76}
mihome-vacuum.0	2021-01-04 12:27:16.685	debug	(8440) 0. Mappointer_nomap___retry
mihome-vacuum.0	2021-01-04 12:27:16.684	debug	(8440) sendMsg[1] >>> {"id":76,"method":"get_map_v1"}
mihome-vacuum.0	2021-01-04 12:27:16.185	silly	(8440) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.map.loadMap:{"val":true,"ack":true,"ts":1609759636179,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":
mihome-vacuum.0	2021-01-04 12:27:16.182	debug	(8440) Receive <<< {"result":["retry"],"id":75}
mihome-vacuum.0	2021-01-04 12:27:16.176	debug	(8440) sendMsg[1] >>> {"id":75,"method":"get_map_v1"}
mihome-vacuum.0	2021-01-04 12:27:16.174	debug	(8440) stateChange mihome-vacuum.0.map.loadMap {"val":true,"ack":false,"ts":1609759636168,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1608539443740}
mihome-vacuum.0	2021-01-04 12:27:16.173	silly	(8440) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.map.loadMap:{"val":true,"ack":false,"ts":1609759636168,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1608539

                                          Ich hatte bis heute noch den "canvas" Error, den hab ich aber durch das Update (siehe Thread hier) behoben. Der Fehler ist nun weg, die Karte wird noch immer nicht aktualisiert. Weder automatisch beim saugen noch per "knopf" in der Objektliste!

                                          Model: roborock.vacuum.s5
                                          FW: 3.5.7_002008

                                          Ich ziehe mir die Karte über die Cloud, also keine Valetudo! Das Login klappt hier auch:

                                          mihome-vacuum.0	2021-01-04 12:17:01.726	debug	(8440) Xiaomi Cloud: Login successful

                                          Fritzbox ist OK, steht für den Sauger auf "Standard".

                                          Irgendeine Idee?

                                          Danke, viele Grüße
                                          Kai

                                          Messiahs 1 Reply Last reply Reply Quote 0
                                          • R
                                            reini @reini last edited by

                                            @reini said in Test Adapter mihome-vacuum v2.0.x:

                                            SWDK ZDG300

                                            geplant diesen zu implementieren?

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.5k
                                            Online

                                            30.7k
                                            Users

                                            77.2k
                                            Topics

                                            1.2m
                                            Posts

                                            map mihome-vacuum roborock xiaomi
                                            144
                                            1474
                                            221415
                                            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