Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. mihome vacuum - login failed

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    mihome vacuum - login failed

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dirkhe Developer @Thomas Braun last edited by

      @thomas-braun Also in dem log sagt er ja, dass er die map aktualisiert hat. Wie sieht denn das log aus, wenn du get Devices drückst? Bitte auch mal schauen, ob der Browser keinen Fehler wirft

      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @dirkhe last edited by

        @dirkhe

        Im Grunde passiert im Log nichts, wenn ich get devices anklicke:

        2025-07-24 18:04:24.351  - debug: mihome-vacuum.0 (168226) discover__{}
2025-07-24 18:04:27.706  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882598bffffffffffffffffffffffffffffffff
2025-07-24 18:04:37.709  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825995ffffffffffffffffffffffffffffffff
2025-07-24 18:04:47.712  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882599fffffffffffffffffffffffffffffffff
2025-07-24 18:04:56.642  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
2025-07-24 18:04:56.642  - debug: mihome-vacuum.0 (168226) Message= {"id":96,"method":"get_status"}
2025-07-24 18:04:56.648  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":947,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":60,"dnd_enabled":0}],"id":96}
2025-07-24 18:04:56.649  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":947,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":true,"in_cleaning":false,"fan_power":60,"dnd_enabled":false,"error_text":"No error"}
2025-07-24 18:04:56.650  - debug: mihome-vacuum.0 (168226) Message= {"id":97,"method":"get_network_info"}
2025-07-24 18:04:56.655  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":97}
2025-07-24 18:04:56.656  - debug: mihome-vacuum.0 (168226) Message= {"id":98,"method":"get_sound_volume"}
2025-07-24 18:04:56.663  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":98}
2025-07-24 18:04:56.664  - debug: mihome-vacuum.0 (168226) Message= {"id":99,"method":"get_carpet_mode"}
2025-07-24 18:04:56.674  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":99}

        Es wird nur die erste Zeile ausgeworfen:
        2025-07-24 18:04:24.351 - debug: mihome-vacuum.0 (168226) discover__{}

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

          @thomas-braun Das ist seltsam, denn es müssten im debug ja auch die Loginversuche auftauchen. Kannst du ggf. mla deinenen Browser refreshen?

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

            Also ich habe den Adapter auch gerade im produktiven System installiert, bei mir funktioniert soweit alles. Da müssen wir dann mal sehen, wo es genau hakt bei euch

            1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @dirkhe last edited by

              @dirkhe sagte in mihome vacuum - login failed:

              Kannst du ggf. mla deinenen Browser refreshen?

              Browser neugestartet, sieht aber exakt aus wie zuvor.

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

                @thomas-braun Kanst du mal die Browser console aufmachen, ob er da irgendeinen Fehler wirft? Obwohl das bei der Anfrage zumindest komisch ist, er müsste da auf jeden Fall was loggen... Der discovery Eintrag kommt ja dann zum Schluß...

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

                  @thomas-braun Schau mal bitte in dein Log, die Einträge vorher. Die Einträge direkt vor dem discovery kommen von der Kommunikation mit dem Sauger selber, das kann sein, dass mdu da ein bisschen früher schauen muss.
                  Die Fangen alle mit CloudApi an

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @dirkhe last edited by

                    @dirkhe

                    2025-07-24 18:49:52.416  - debug: mihome-vacuum.0 (172290) CloudApi-Login gestartet…
2025-07-24 18:49:52.417  - debug: mihome-vacuum.0 (172290) CloudApi-CloudApi-Step 1: Getting sign token
2025-07-24 18:49:52.559  - debug: mihome-vacuum.0 (172290) CloudApi-Step 2: Authenticating user
2025-07-24 18:49:52.684  - debug: mihome-vacuum.0 (172290) CloudApi-Step 3: Fetching service token
2025-07-24 18:49:52.836  - debug: mihome-vacuum.0 (172290) CloudApi-Login erfolgreich!
2025-07-24 18:49:52.846  - debug: mihome-vacuum.0 (172290) CloudApi-call: https://-.api.io.mi.com/app/v2/homeroom/gethome with {"data":"{\"fg\":true,\"fetch_share\":true,\"fetch_share_dev\":true,\"limit\":300,\"app_ver\":7}"}
2025-07-24 18:49:52.995  - error: mihome-vacuum.0 (172290) CloudApi: executeEncryptedApiCall Error:
2025-07-24 18:49:52.996  - debug: mihome-vacuum.0 (172290) discover__{}
2025-07-24 18:49:55.667  - debug: mihome-vacuum.0 (172290) Receive <<< Helo <<< 2131002000000000046c689568826433ffffffffffffffffffffffffffffffff
2025-07-24 18:50:01.793  - debug: mihome-vacuum.0 (172290) get params for stock Vacuum
2025-07-24 18:50:01.794  - debug: mihome-vacuum.0 (172290) Message= {"id":10,"method":"get_status"}
2025-07-24 18:50:01.805  - debug: mihome-vacuum.0 (172290) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":991,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":60,"dnd_enabled":0}],"id":10}
2025-07-24 18:50:01.807  - debug: mihome-vacuum.0 (172290) setGetStatus {"msg_ver":8,"msg_seq":991,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":true,"in_cleaning":false,"fan_power":60,"dnd_enabled":false,"error_text":"No error"}
2025-07-24 18:50:01.932  - debug: mihome-vacuum.0 (172290) Message= {"id":11,"method":"get_map_v1"}
2025-07-24 18:50:01.939  - debug: mihome-vacuum.0 (172290) MIIO RECIVE: {"result":["retry"],"id":11}
2025-07-24 18:50:02.242  - debug: mihome-vacuum.0 (172290) Message= {"id":12,"method":"get_map_v1"}
2025-07-24 18:50:02.250  - debug: mihome-vacuum.0 (172290) MIIO RECIVE: {"result":["retry"],"id":12}
2025-07-24 18:50:02.552  - debug: mihome-vacuum.0 (172290) Message= {"id":13,"method":"get_map_v1"}
2025-07-24 18:50:04.556  - debug: mihome-vacuum.0 (172290) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2025-07-24 18:50:04.858  - debug: mihome-vacuum.0 (172290) Message= {"id":14,"method":"get_map_v1"}
2025-07-24 18:50:04.864  - debug: mihome-vacuum.0 (172290) MIIO RECIVE: {"result":["roboroommap%2F74213525%2F6"],"id":14}
2025-07-24 18:50:04.865  - debug: mihome-vacuum.0 (172290) Mappointer_updated
2025-07-24 18:50:04.869  - debug: mihome-vacuum.0 (172290) update_Map Mimap enabled
2025-07-24 18:50:04.870  - debug: mihome-vacuum.0 (172290) update_Map need new mapurl
2025-07-24 18:50:04.874  - debug: mihome-vacuum.0 (172290) CloudApi-call: https://api.io.mi.com/app/home/getmapfileurl with {"data":"{\"obj_name\":\"roboroommap%2F74213525%2F6\"}"}
2025-07-24 18:50:04.884  - debug: mihome-vacuum.0 (172290) Message= {"id":15,"method":"get_room_mapping"}
2025-07-24 18:50:04.894  - debug: mihome-vacuum.0 (172290) MIIO RECIVE: {"result":"unknown_method","id":15}
2025-07-24 18:50:04.896  - debug: mihome-vacuum.0 (172290) Message= {"id":16,"method":"get_consumable"}
2025-07-24 18:50:04.898  - debug: mihome-vacuum.0 (172290) Message= {"id":17,"method":"get_network_info"}
                    1 Reply Last reply Reply Quote 0
                    • D
                      dirkhe Developer last edited by

                      @thomas-braun ok, die entscheiden Zeile ist der executeEncryptedApiCall error, allerdings gibt er da nichts aus.
                      Kannst mal bitte direkt in Datei /ioBroker/iobroker.mihome-vacuum/lib/XiaomiCloudConnector.js gehen und bei folgender Zeile 304
                      aus err.message ein err machen, also das message wegmachen, bitte

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @dirkhe last edited by Thomas Braun

                        @dirkhe

                        Gemacht, Zeile 304:

                                    this.logger.error('CloudApi: executeEncryptedApiCall Error:', err);

                        aber da steht nix drin:

                        2025-07-24 19:01:04.008  - debug: mihome-vacuum.0 (172612) CloudApi-Login gestartet…
2025-07-24 19:01:04.009  - debug: mihome-vacuum.0 (172612) CloudApi-CloudApi-Step 1: Getting sign token
2025-07-24 19:01:04.112  - debug: mihome-vacuum.0 (172612) CloudApi-Step 2: Authenticating user
2025-07-24 19:01:04.244  - debug: mihome-vacuum.0 (172612) CloudApi-Step 3: Fetching service token
2025-07-24 19:01:04.407  - debug: mihome-vacuum.0 (172612) CloudApi-Login erfolgreich!
2025-07-24 19:01:04.418  - debug: mihome-vacuum.0 (172612) CloudApi-call: https://-.api.io.mi.com/app/v2/homeroom/gethome with {"data":"{\"fg\":true,\"fetch_share\":true,\"fetch_share_dev\":true,\"limit\":300,\"app_ver\":7}"}
2025-07-24 19:01:04.590  - error: mihome-vacuum.0 (172612) CloudApi: executeEncryptedApiCall Error:
2025-07-24 19:01:04.591  - debug: mihome-vacuum.0 (172612) discover__{}
                        D 1 Reply Last reply Reply Quote 0
                        • D
                          dirkhe Developer @Thomas Braun last edited by

                          @thomas-braun Ach ich dummbacke, das muss so sein

                          this.logger.error(`CloudApi: executeEncryptedApiCall Error:${err.message}`);
                          Thomas Braun bahnuhr 2 Replies Last reply Reply Quote 1
                          • Thomas Braun
                            Thomas Braun Most Active @dirkhe last edited by

                            @dirkhe

                            2025-07-24 19:15:21.641  - debug: mihome-vacuum.0 (1462) CloudApi-call: https://-.api.io.mi.com/app/v2/homeroom/gethome with {"data":"{\"fg\":true,\"fetch_share\":true,\"fetch_share_dev\":true,\"limit\":300,\"app_ver\":7}"}
2025-07-24 19:15:21.833  - error: mihome-vacuum.0 (1462) CloudApi: executeEncryptedApiCall Error:getaddrinfo ENOTFOUND -.api.io.mi.com
2025-07-24 19:15:21.834  - debug: mihome-vacuum.0 (1462) discover__{}
                            Thomas Braun D 2 Replies Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Thomas Braun last edited by

                              @thomas-braun sagte in mihome vacuum - login failed:

                              https://-.api.io.mi.com

                              Schaut für mich nach einer ungültigen URL aus.
                              Ich bin im übrigen auf dem chinesischen Server mit dem Sauger angemeldet. Falls das einen Unterschied macht.

                              1 Reply Last reply Reply Quote 0
                              • bahnuhr
                                bahnuhr Forum Testing Most Active @dirkhe last edited by

                                @dirkhe

                                so Rückinfo von mir.
                                Nochmal neu von git geholt.
                                login Fehler im log ist nun weg.

                                get devices geht auch; Sauger werden geholt.

                                Und die map geht auch wieder.

                                Vielen lieben Dank für deinen Ansatz und die Lösung.

                                Fazit:
                                Bei mir geht wieder alles.

                                (Anmerkung: Ich bin auf dem deutschen Server)

                                1 Reply Last reply Reply Quote 1
                                • D
                                  dirkhe Developer @Thomas Braun last edited by

                                  @thomas-braun stimmt, sehe den Fehler auch schon, Fix kommt gleich

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

                                    @thomas-braun bitte noch mal neu von github holen, ich hatte da noch ein bug drin. hatte das ja alles neu geschrieben....

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @dirkhe last edited by

                                      @dirkhe

                                      Nope. Get devices geht noch nicht.

                                      2025-07-24 19:59:42.943  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c68956882748fffffffffffffffffffffffffffffffff
2025-07-24 19:59:42.943  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 19:59:52.947  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c689568827499ffffffffffffffffffffffffffffffff
2025-07-24 19:59:52.947  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:00:02.950  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c6895688274a3ffffffffffffffffffffffffffffffff
2025-07-24 20:00:02.951  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:00:07.909  - debug: mihome-vacuum.0 (1462) discover__{}
2025-07-24 20:00:12.954  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c6895688274adffffffffffffffffffffffffffffffff
2025-07-24 20:00:12.955  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:00:22.329  - debug: mihome-vacuum.0 (1462) get params for stock Vacuum
2025-07-24 20:00:22.330  - debug: mihome-vacuum.0 (1462) Message= {"id":142,"method":"get_status"}
2025-07-24 20:00:22.339  - debug: mihome-vacuum.0 (1462) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":1051,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":60,"dnd_enabled":0}],"id":142}
2025-07-24 20:00:22.340  - debug: mihome-vacuum.0 (1462) setGetStatus {"msg_ver":8,"msg_seq":1051,"state":8,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":true,"in_cleaning":false,"fan_power":60,"dnd_enabled":false,"error_text":"No error"}
2025-07-24 20:00:22.342  - debug: mihome-vacuum.0 (1462) Message= {"id":143,"method":"get_network_info"}
2025-07-24 20:00:22.350  - debug: mihome-vacuum.0 (1462) MIIO RECIVE: {"result":"unknown_method","id":143}
2025-07-24 20:00:22.351  - debug: mihome-vacuum.0 (1462) Message= {"id":144,"method":"get_sound_volume"}
2025-07-24 20:00:22.361  - debug: mihome-vacuum.0 (1462) MIIO RECIVE: {"result":[90],"id":144}
2025-07-24 20:00:24.956  - debug: mihome-vacuum.0 (1462) Helo message Timeout
                                      D 1 Reply Last reply Reply Quote 0
                                      • D
                                        dirkhe Developer @Thomas Braun last edited by

                                        @thomas-braun gib mal bitte die passenden Logzeilen, die sind in dem Auschnitt nicht drin

                                        Thomas Braun 3 Replies Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @dirkhe last edited by

                                          @dirkhe

                                          Da ist auch nicht mehr. get devices geklickt um 20:40:23.105

                                          2025-07-24 20:40:08.922  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c689568827e09ffffffffffffffffffffffffffffffff
2025-07-24 20:40:08.922  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:40:18.926  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c689568827e13ffffffffffffffffffffffffffffffff
2025-07-24 20:40:18.927  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:40:23.105  - debug: mihome-vacuum.0 (1462) discover__{}
2025-07-24 20:40:28.930  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c689568827e1dffffffffffffffffffffffffffffffff
2025-07-24 20:40:28.931  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
2025-07-24 20:40:38.934  - debug: mihome-vacuum.0 (1462) Receive <<< Helo <<< 2131002000000000046c689568827e27ffffffffffffffffffffffffffffffff
2025-07-24 20:40:38.935  - debug: mihome-vacuum.0 (1462) Time difference between Mihome Vacuum and ioBroker: 1 sec
                                          1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @dirkhe last edited by

                                            @dirkhe

                                            Ah! Nochmal neugestartet, jetzt funktioniert es!

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            473
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            login mihome vacuum
                                            6
                                            44
                                            420
                                            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