Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. mihome vacuum - login failed

NEWS

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

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

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.2k

mihome vacuum - login failed

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
loginmihomevacuum
51 Beiträge 9 Kommentatoren 3.4k Aufrufe 11 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • bahnuhrB bahnuhr

    @dirkhe
    Danke für die Info.
    Wäre halt schade wenn die map nicht mehr geht.
    Und lt. Issue werden es ja auch mehr, bei denen es nicht mehr geht.

    D Nicht stören
    D Nicht stören
    dirkhe
    Developer
    schrieb am zuletzt editiert von
    #11

    aber ich denke, die map ist ein anderes problem

    bahnuhrB 1 Antwort Letzte Antwort
    0
    • D dirkhe

      aber ich denke, die map ist ein anderes problem

      bahnuhrB Online
      bahnuhrB Online
      bahnuhr
      Forum Testing Most Active
      schrieb am zuletzt editiert von bahnuhr
      #12

      @dirkhe sagte in mihome vacuum - login failed:

      aber ich denke, die map ist ein anderes problem

      glaube ich nicht.

      Die map wird laut Einstellungen direkt von der cloud geholt.
      0cba0565-9568-467c-ba99-d23ecd4d287b-image.png

      Und wenn er da sich nicht einloggen kann, dann klappt es halt nicht mit der map.

      Alles andere funktioniert ja: Steuerung des robo; Raum einzeln ansteuern, etc.

      Adapter wird grün, alles funktioniert, außer halt der map.

      Nachtrag:
      get devices in der Instanz funktioniert auch nicht (weil er sich ja nicht einloggen kann).
      Es kommt Hinweis: Error login failed.


      Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
      Danke.
      gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
      ScreenToGif :https://www.screentogif.com/downloads.html

      1 Antwort Letzte Antwort
      0
      • 9 Offline
        9 Offline
        900icarD
        schrieb am zuletzt editiert von
        #13

        Guten Abend,

        ich habe ebenso das "Login failed" Problem nachdem ich heute den Adapter neu installiert habe da ich dachte, dass ggf. irgendwas mit meinem neuen Passwort nicht stimmen würde.
        Erst danach bin ich auf diesen Thread hier gestoßen ;-(

        1 Antwort Letzte Antwort
        0
        • D Nicht stören
          D Nicht stören
          dirkhe
          Developer
          schrieb am zuletzt editiert von
          #14

          Ich habe gestern den ganzen tag rumprogramiert und geforscht.

          • Also auf 2fa werde ich das nicht umprogrammieren, da zu aufwendig. Hier gab es mal die Idee für iobroker etwas allgemeines zu bauen, der dann auch einen antwortenden service bietet incl. Zertifikate usw.
          • ich habe in der config ejne captcha anfrage eingebaut, aber die will er irgendwie noch nicht schlucken...
          • ich habe den user agent verändert, jetzt bekomme ich keine captcha anfrage mehr und kann da nicht weiter testen...
          • ich hatte in dem zuge alles von request auf axios umgebaut und jetrt funktioniert die verschlüsselung nicht mehr, ich vermute, dass die beiden bibliotheken da irgenwie das format anders übermitteln
          bahnuhrB 1 Antwort Letzte Antwort
          0
          • D dirkhe

            Ich habe gestern den ganzen tag rumprogramiert und geforscht.

            • Also auf 2fa werde ich das nicht umprogrammieren, da zu aufwendig. Hier gab es mal die Idee für iobroker etwas allgemeines zu bauen, der dann auch einen antwortenden service bietet incl. Zertifikate usw.
            • ich habe in der config ejne captcha anfrage eingebaut, aber die will er irgendwie noch nicht schlucken...
            • ich habe den user agent verändert, jetzt bekomme ich keine captcha anfrage mehr und kann da nicht weiter testen...
            • ich hatte in dem zuge alles von request auf axios umgebaut und jetrt funktioniert die verschlüsselung nicht mehr, ich vermute, dass die beiden bibliotheken da irgenwie das format anders übermitteln
            bahnuhrB Online
            bahnuhrB Online
            bahnuhr
            Forum Testing Most Active
            schrieb am zuletzt editiert von
            #15

            @dirkhe
            Danke für die Info.

            Schade wäre halt, wenn die map zukünftig nicht mehr funktionieren würde.
            Und auch der grundsätzliche login am Anfang bei Installation der Instanz dürfte dann auch nicht mehr funktionieren.

            @dirkhe sagte in mihome vacuum - login failed:

            Also auf 2fa werde ich das nicht umprogrammieren,

            Hier müsste es doch Adapter geben die das schon umgesetzt haben. Kann man sich da Hilfe holen ?


            Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
            Danke.
            gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
            ScreenToGif :https://www.screentogif.com/downloads.html

            D 1 Antwort Letzte Antwort
            0
            • bahnuhrB bahnuhr

              @dirkhe
              Danke für die Info.

              Schade wäre halt, wenn die map zukünftig nicht mehr funktionieren würde.
              Und auch der grundsätzliche login am Anfang bei Installation der Instanz dürfte dann auch nicht mehr funktionieren.

              @dirkhe sagte in mihome vacuum - login failed:

              Also auf 2fa werde ich das nicht umprogrammieren,

              Hier müsste es doch Adapter geben die das schon umgesetzt haben. Kann man sich da Hilfe holen ?

              D Nicht stören
              D Nicht stören
              dirkhe
              Developer
              schrieb am zuletzt editiert von
              #16

              Update.

              Ich denke, ich habe es jetzt wieder hinbekommen, habe aber bis jetzt nur Fragmente. Als nächstes muss ich das alles wieder in den Adapter zusammenbauen....

              Ich habe jetzt schon 2 Urlaubstage damit verbaselt, weiss nicht, ob ich es diese Woche noch fertig bekomme.Aber ich denke, dann gibt es ja Hoffnung..

              D 1 Antwort Letzte Antwort
              5
              • D dirkhe

                Update.

                Ich denke, ich habe es jetzt wieder hinbekommen, habe aber bis jetzt nur Fragmente. Als nächstes muss ich das alles wieder in den Adapter zusammenbauen....

                Ich habe jetzt schon 2 Urlaubstage damit verbaselt, weiss nicht, ob ich es diese Woche noch fertig bekomme.Aber ich denke, dann gibt es ja Hoffnung..

                D Nicht stören
                D Nicht stören
                dirkhe
                Developer
                schrieb am zuletzt editiert von
                #17

                Hallo zusammen,

                auf github gibt es jetzt eine neue Version, bitte mal testen.
                Ich habe es zwar nicht hinbekommen, das captcha zu lösen, weil er irgendwie nicht dieselbe Session nutzten will, aber ich habe generell den Agent dynamisch geändert und jetzt bekomme ich halt gar keine captcha Frage mehr.
                Falls es aber eine captcha Abfrage oder eine 2fa Anfrage gibt, wird es entsprechend geloggt.

                Karte geht auch wieder

                bahnuhrB 1 Antwort Letzte Antwort
                1
                • D dirkhe

                  Hallo zusammen,

                  auf github gibt es jetzt eine neue Version, bitte mal testen.
                  Ich habe es zwar nicht hinbekommen, das captcha zu lösen, weil er irgendwie nicht dieselbe Session nutzten will, aber ich habe generell den Agent dynamisch geändert und jetzt bekomme ich halt gar keine captcha Frage mehr.
                  Falls es aber eine captcha Abfrage oder eine 2fa Anfrage gibt, wird es entsprechend geloggt.

                  Karte geht auch wieder

                  bahnuhrB Online
                  bahnuhrB Online
                  bahnuhr
                  Forum Testing Most Active
                  schrieb am zuletzt editiert von bahnuhr
                  #18

                  @dirkhe
                  vor dem map log kommt weiterhin failed:

                  mihome-vacuum.0
                  2025-07-24 17:21:11.983	info	create states for mop
                  
                  mihome-vacuum.0
                  2025-07-24 17:21:11.735	warn	Login failed
                  

                  Nachtrag:
                  get devices in der Instanz geht nicht; es kommt weiterhin "error login"


                  Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
                  Danke.
                  gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
                  ScreenToGif :https://www.screentogif.com/downloads.html

                  Thomas BraunT 1 Antwort Letzte Antwort
                  0
                  • bahnuhrB bahnuhr

                    @dirkhe
                    vor dem map log kommt weiterhin failed:

                    mihome-vacuum.0
                    2025-07-24 17:21:11.983	info	create states for mop
                    
                    mihome-vacuum.0
                    2025-07-24 17:21:11.735	warn	Login failed
                    

                    Nachtrag:
                    get devices in der Instanz geht nicht; es kommt weiterhin "error login"

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von
                    #19

                    @bahnuhr @dirkhe
                    Kann ich bestätigen, get devices funktioniert nicht.
                    Map wohl auch nicht, kann ich aber nicht richtig testen, da keine vis.
                    Debug sagt:

                    2025-07-24 17:43:13.090  - info: mihome-vacuum.0 (168226) starting. Version 5.2.0 (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v24.4.1, js-controller: 7.0.7
                    2025-07-24 17:43:13.144  - debug: mihome-vacuum.0 (168226) Create State for deviceInfo
                    2025-07-24 17:43:13.145  - debug: mihome-vacuum.0 (168226) Create State for deviceInfomac
                    2025-07-24 17:43:13.145  - debug: mihome-vacuum.0 (168226) Create State for deviceInfomodel
                    2025-07-24 17:43:13.146  - debug: mihome-vacuum.0 (168226) Create State for deviceInfofw_ver
                    2025-07-24 17:43:13.147  - debug: mihome-vacuum.0 (168226) Create State for deviceInfowifi_signal
                    2025-07-24 17:43:13.147  - debug: mihome-vacuum.0 (168226) Create State for deviceInfounsupported
                    2025-07-24 17:43:13.149  - debug: mihome-vacuum.0 (168226) MIIO: Config: ip:192.168.178.23 token: 753955485aXXXXXXXXX
                    2025-07-24 17:43:13.154  - info: mihome-vacuum.0 (168226) IOT enabled, create state
                    2025-07-24 17:43:13.157  - debug: mihome-vacuum.0 (168226) server started on 0.0.0.0:53421
                    2025-07-24 17:43:13.171  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825491ffffffffffffffffffffffffffffffff
                    2025-07-24 17:43:13.172  - debug: mihome-vacuum.0 (168226) MAIN: Connected to device, try to get model..
                    2025-07-24 17:43:13.177  - debug: mihome-vacuum.0 (168226) your device is not connected, but this could be temporary
                    2025-07-24 17:43:13.179  - debug: mihome-vacuum.0 (168226) GETMODELFROMAPI:Data: {}
                    2025-07-24 17:43:13.179  - debug: mihome-vacuum.0 (168226) Get Device data..0
                    2025-07-24 17:43:13.181  - debug: mihome-vacuum.0 (168226) Message= {"id":1,"method":"miIO.info"}
                    2025-07-24 17:43:13.193  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXXXXX","life":51120}}
                    2025-07-24 17:43:13.194  - debug: mihome-vacuum.0 (168226) GETMODELFROMAPI:Data: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXX":51120}}
                    2025-07-24 17:43:13.195  - debug: mihome-vacuum.0 (168226) Get Device data..1
                    2025-07-24 17:43:13.195  - debug: mihome-vacuum.0 (168226) Get Device data from robot.. {"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXX":51120}
                    2025-07-24 17:43:13.288  - debug: mihome-vacuum.0 (168226) DeviceModel set to: rockrobo.vacuum.v1
                    2025-07-24 17:43:13.319  - debug: mihome-vacuum.0 (168226) load Map creator... true
                    2025-07-24 17:43:13.323  - info: mihome-vacuum.0 (168226) select standard vacuum protocol....
                    2025-07-24 17:43:13.330  - debug: mihome-vacuum.0 (168226) CloudApi-Login gestartet…
                    2025-07-24 17:43:13.331  - debug: mihome-vacuum.0 (168226) CloudApi-CloudApi-Step 1: Getting sign token
                    2025-07-24 17:43:13.529  - debug: mihome-vacuum.0 (168226) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                    2025-07-24 17:43:13.660  - debug: mihome-vacuum.0 (168226) CloudApi-Step 2: Authenticating user
                    2025-07-24 17:43:13.794  - debug: mihome-vacuum.0 (168226) CloudApi-Step 3: Fetching service token
                    2025-07-24 17:43:13.967  - debug: mihome-vacuum.0 (168226) CloudApi-Login erfolgreich!
                    2025-07-24 17:43:14.066  - info: mihome-vacuum.0 (168226) settest next timer: not available
                    2025-07-24 17:43:14.150  - debug: mihome-vacuum.0 (168226) Create State for control: {"id":"mihome-vacuum.0.control"}
                    2025-07-24 17:43:14.400  - debug: mihome-vacuum.0 (168226) Create State for Queue: queue
                    2025-07-24 17:43:14.478  - debug: mihome-vacuum.0 (168226) Create State for map: 
                    2025-07-24 17:43:14.521  - debug: mihome-vacuum.0 (168226) Create State for map: map64
                    2025-07-24 17:43:14.522  - debug: mihome-vacuum.0 (168226) Create State for map: actualMap
                    2025-07-24 17:43:14.523  - debug: mihome-vacuum.0 (168226) Create State for map: mapStatus
                    2025-07-24 17:43:14.525  - debug: mihome-vacuum.0 (168226) Create State for map: mapURL
                    2025-07-24 17:43:14.525  - debug: mihome-vacuum.0 (168226) Create State for map: loadMap
                    2025-07-24 17:43:14.526  - debug: mihome-vacuum.0 (168226) Create State done!
                    2025-07-24 17:43:14.527  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                    2025-07-24 17:43:14.528  - debug: mihome-vacuum.0 (168226) Message= {"id":2,"method":"get_status"}
                    2025-07-24 17:43:14.536  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":889,"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":2}
                    2025-07-24 17:43:14.537  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":889,"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 17:43:14.691  - debug: mihome-vacuum.0 (168226) Message= {"id":3,"method":"get_map_v1"}
                    2025-07-24 17:43:14.699  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":["retry"],"id":3}
                    2025-07-24 17:43:15.001  - debug: mihome-vacuum.0 (168226) Message= {"id":4,"method":"get_map_v1"}
                    2025-07-24 17:43:17.003  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:43:17.305  - debug: mihome-vacuum.0 (168226) Message= {"id":5,"method":"get_map_v1"}
                    2025-07-24 17:43:17.313  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":["roboroommap%2F74213525%2F2"],"id":5}
                    2025-07-24 17:43:17.313  - debug: mihome-vacuum.0 (168226) Mappointer_updated
                    2025-07-24 17:43:17.315  - debug: mihome-vacuum.0 (168226) update_Map Mimap enabled
                    2025-07-24 17:43:17.315  - debug: mihome-vacuum.0 (168226) update_Map need new mapurl
                    2025-07-24 17:43:17.321  - debug: mihome-vacuum.0 (168226) CloudApi-call: https://api.io.mi.com/app/home/getmapfileurl with {"data":"{\"obj_name\":\"roboroommap%2F74213525%2F2\"}"}
                    2025-07-24 17:43:17.328  - debug: mihome-vacuum.0 (168226) Message= {"id":6,"method":"get_room_mapping"}
                    2025-07-24 17:43:17.337  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":6}
                    2025-07-24 17:43:17.340  - debug: mihome-vacuum.0 (168226) Message= {"id":7,"method":"get_consumable"}
                    2025-07-24 17:43:17.342  - debug: mihome-vacuum.0 (168226) Message= {"id":8,"method":"get_network_info"}
                    2025-07-24 17:43:17.349  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"main_brush_work_time":1320,"side_brush_work_time":330828,"filter_work_time":1320,"sensor_dirty_time":1343}],"id":7}
                    2025-07-24 17:43:17.351  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":8}
                    2025-07-24 17:43:17.352  - debug: mihome-vacuum.0 (168226) Message= {"id":9,"method":"get_sound_volume"}
                    2025-07-24 17:43:17.358  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":9}
                    2025-07-24 17:43:17.360  - debug: mihome-vacuum.0 (168226) Message= {"id":10,"method":"get_multi_maps_list"}
                    2025-07-24 17:43:17.368  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":10}
                    2025-07-24 17:43:17.369  - debug: mihome-vacuum.0 (168226) Startup: getMultiMapsList Answer: true
                    2025-07-24 17:43:17.370  - debug: mihome-vacuum.0 (168226) Startup: Delete getMultiMapsList
                    2025-07-24 17:43:17.371  - debug: mihome-vacuum.0 (168226) Message= {"id":11,"method":"get_clean_summary"}
                    2025-07-24 17:43:17.386  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[330035,4140217500,288,[]],"id":11}
                    2025-07-24 17:43:17.388  - debug: mihome-vacuum.0 (168226) Startup: setGetCleanSummary Answer: true
                    2025-07-24 17:43:17.389  - debug: mihome-vacuum.0 (168226) Startup: Delete setGetCleanSummary
                    2025-07-24 17:43:17.389  - debug: mihome-vacuum.0 (168226) Message= {"id":12,"method":"get_consumable"}
                    2025-07-24 17:43:17.399  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"main_brush_work_time":1320,"side_brush_work_time":330828,"filter_work_time":1320,"sensor_dirty_time":1343}],"id":12}
                    2025-07-24 17:43:17.400  - debug: mihome-vacuum.0 (168226) Startup: setGetConsumable Answer: true
                    2025-07-24 17:43:17.401  - debug: mihome-vacuum.0 (168226) Startup: Delete setGetConsumable
                    2025-07-24 17:43:17.402  - debug: mihome-vacuum.0 (168226) Message= {"id":13,"method":"get_carpet_mode"}
                    2025-07-24 17:43:17.411  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":13}
                    2025-07-24 17:43:17.412  - info: mihome-vacuum.0 (168226) create state for carpet_mode
                    2025-07-24 17:43:17.413  - debug: mihome-vacuum.0 (168226) Message= {"id":14,"method":"get_carpet_mode"}
                    2025-07-24 17:43:17.498  - debug: mihome-vacuum.0 (168226) Message= {"id":15,"method":"get_clean_summary"}
                    2025-07-24 17:43:19.200  - debug: mihome-vacuum.0 (168226) CloudApi-get {"code":0,"message":"ok","result":{"url":"https://cnbj2.fds.api.xiaomi.com/robomap/roboroommap/74213525/2?Expires=1753373599000&GalaxyAccessKeyId=5ZIFFERN5&Signature=ERSETZT=","obj_name":"roboroommap/74213525/2","method":"GET","expires_time":1753373599,"ok":true}}
                    2025-07-24 17:43:19.202  - debug: mihome-vacuum.0 (168226) update_Map got new url:https://cnbj2.fds.api.xiaomi.com/robomap/roboroommap/74213525/2?Expires=1753373599000&GalaxyAccessKeyId=5ZIFFERN5&Signature=ERSETZT=
                    2025-07-24 17:43:19.203  - debug: mihome-vacuum.0 (168226) update_Map got new expires:1753373599
                    2025-07-24 17:43:19.204  - debug: mihome-vacuum.0 (168226) update_Map got new time:1753371797
                    2025-07-24 17:43:19.415  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:43:19.501  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:43:19.657  - debug: mihome-vacuum.0 (168226) creating map
                    2025-07-24 17:43:23.181  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882549bffffffffffffffffffffffffffffffff
                    2025-07-24 17:43:33.185  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254a5ffffffffffffffffffffffffffffffff
                    2025-07-24 17:43:43.190  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254afffffffffffffffffffffffffffffffff
                    2025-07-24 17:43:53.193  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254b9ffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:03.196  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254c3ffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:13.201  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254cdffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:20.417  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                    2025-07-24 17:44:20.418  - debug: mihome-vacuum.0 (168226) Message= {"id":16,"method":"get_status"}
                    2025-07-24 17:44:22.420  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:44:22.420  - debug: mihome-vacuum.0 (168226) Message= {"id":17,"method":"get_network_info"}
                    2025-07-24 17:44:23.204  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254d7ffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:24.421  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:44:24.422  - debug: mihome-vacuum.0 (168226) Message= {"id":18,"method":"get_sound_volume"}
                    2025-07-24 17:44:26.423  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                    2025-07-24 17:44:26.424  - debug: mihome-vacuum.0 (168226) Message= {"id":19,"method":"get_carpet_mode"}
                    2025-07-24 17:44:26.432  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":19}
                    2025-07-24 17:44:33.208  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254e1ffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:43.212  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254ebffffffffffffffffffffffffffffffff
                    2025-07-24 17:44:53.214  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254f5ffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:03.220  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254ffffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:13.226  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825509ffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:23.233  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825513ffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:27.486  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                    2025-07-24 17:45:27.487  - debug: mihome-vacuum.0 (168226) Message= {"id":20,"method":"get_status"}
                    2025-07-24 17:45:27.496  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":890,"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":20}
                    2025-07-24 17:45:27.497  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":890,"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 17:45:27.499  - debug: mihome-vacuum.0 (168226) Message= {"id":21,"method":"get_network_info"}
                    2025-07-24 17:45:27.505  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":21}
                    2025-07-24 17:45:27.506  - debug: mihome-vacuum.0 (168226) Message= {"id":22,"method":"get_sound_volume"}
                    2025-07-24 17:45:27.514  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":22}
                    2025-07-24 17:45:27.515  - debug: mihome-vacuum.0 (168226) Message= {"id":23,"method":"get_carpet_mode"}
                    2025-07-24 17:45:27.644  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":23}
                    2025-07-24 17:45:33.238  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882551dffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:43.241  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825527ffffffffffffffffffffffffffffffff
                    2025-07-24 17:45:53.249  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825531ffffffffffffffffffffffffffffffff
                    2025-07-24 17:46:03.254  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882553bffffffffffffffffffffffffffffffff
                    2025-07-24 17:46:13.256  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825545ffffffffffffffffffffffffffffffff
                    2025-07-24 17:46:23.261  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882554fffffffffffffffffffffffffffffffff
                    2025-07-24 17:46:28.758  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                    2025-07-24 17:46:28.759  - debug: mihome-vacuum.0 (168226) Message= {"id":24,"method":"get_status"}
                    2025-07-24 17:46:28.768  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":915,"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":24}
                    2025-07-24 17:46:28.769  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":915,"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 17:46:28.771  - debug: mihome-vacuum.0 (168226) Message= {"id":25,"method":"get_network_info"}
                    2025-07-24 17:46:28.782  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":25}
                    2025-07-24 17:46:28.783  - debug: mihome-vacuum.0 (168226) Message= {"id":26,"method":"get_sound_volume"}
                    2025-07-24 17:46:28.947  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":26}
                    2025-07-24 17:46:28.948  - debug: mihome-vacuum.0 (168226) Message= {"id":27,"method":"get_carpet_mode"}
                    2025-07-24 17:46:28.958  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":27}
                    2025-07-24 17:46:33.267  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825559ffffffffffffffffffffffffffffffff
                    
                    

                    Schaut aber für mich eigentlich sauber aus.

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    D 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @bahnuhr @dirkhe
                      Kann ich bestätigen, get devices funktioniert nicht.
                      Map wohl auch nicht, kann ich aber nicht richtig testen, da keine vis.
                      Debug sagt:

                      2025-07-24 17:43:13.090  - info: mihome-vacuum.0 (168226) starting. Version 5.2.0 (non-npm: iobroker-community-adapters/ioBroker.mihome-vacuum) in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v24.4.1, js-controller: 7.0.7
                      2025-07-24 17:43:13.144  - debug: mihome-vacuum.0 (168226) Create State for deviceInfo
                      2025-07-24 17:43:13.145  - debug: mihome-vacuum.0 (168226) Create State for deviceInfomac
                      2025-07-24 17:43:13.145  - debug: mihome-vacuum.0 (168226) Create State for deviceInfomodel
                      2025-07-24 17:43:13.146  - debug: mihome-vacuum.0 (168226) Create State for deviceInfofw_ver
                      2025-07-24 17:43:13.147  - debug: mihome-vacuum.0 (168226) Create State for deviceInfowifi_signal
                      2025-07-24 17:43:13.147  - debug: mihome-vacuum.0 (168226) Create State for deviceInfounsupported
                      2025-07-24 17:43:13.149  - debug: mihome-vacuum.0 (168226) MIIO: Config: ip:192.168.178.23 token: 753955485aXXXXXXXXX
                      2025-07-24 17:43:13.154  - info: mihome-vacuum.0 (168226) IOT enabled, create state
                      2025-07-24 17:43:13.157  - debug: mihome-vacuum.0 (168226) server started on 0.0.0.0:53421
                      2025-07-24 17:43:13.171  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825491ffffffffffffffffffffffffffffffff
                      2025-07-24 17:43:13.172  - debug: mihome-vacuum.0 (168226) MAIN: Connected to device, try to get model..
                      2025-07-24 17:43:13.177  - debug: mihome-vacuum.0 (168226) your device is not connected, but this could be temporary
                      2025-07-24 17:43:13.179  - debug: mihome-vacuum.0 (168226) GETMODELFROMAPI:Data: {}
                      2025-07-24 17:43:13.179  - debug: mihome-vacuum.0 (168226) Get Device data..0
                      2025-07-24 17:43:13.181  - debug: mihome-vacuum.0 (168226) Message= {"id":1,"method":"miIO.info"}
                      2025-07-24 17:43:13.193  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXXXXX","life":51120}}
                      2025-07-24 17:43:13.194  - debug: mihome-vacuum.0 (168226) GETMODELFROMAPI:Data: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXX":51120}}
                      2025-07-24 17:43:13.195  - debug: mihome-vacuum.0 (168226) Get Device data..1
                      2025-07-24 17:43:13.195  - debug: mihome-vacuum.0 (168226) Get Device data from robot.. {"hw_ver":"Linux","fw_ver":"3.5.8_004028","ap":{"ssid":"WLana-del-Rey","bssid":"1C:ED:6F:57:F0:44","rssi":-52},"netif":{"localIp":"192.168.178.23","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"rockrobo.vacuum.v1","mac":"78:11:DC:7E:2A:27","token":"753955485aXXXXXX":51120}
                      2025-07-24 17:43:13.288  - debug: mihome-vacuum.0 (168226) DeviceModel set to: rockrobo.vacuum.v1
                      2025-07-24 17:43:13.319  - debug: mihome-vacuum.0 (168226) load Map creator... true
                      2025-07-24 17:43:13.323  - info: mihome-vacuum.0 (168226) select standard vacuum protocol....
                      2025-07-24 17:43:13.330  - debug: mihome-vacuum.0 (168226) CloudApi-Login gestartet…
                      2025-07-24 17:43:13.331  - debug: mihome-vacuum.0 (168226) CloudApi-CloudApi-Step 1: Getting sign token
                      2025-07-24 17:43:13.529  - debug: mihome-vacuum.0 (168226) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                      2025-07-24 17:43:13.660  - debug: mihome-vacuum.0 (168226) CloudApi-Step 2: Authenticating user
                      2025-07-24 17:43:13.794  - debug: mihome-vacuum.0 (168226) CloudApi-Step 3: Fetching service token
                      2025-07-24 17:43:13.967  - debug: mihome-vacuum.0 (168226) CloudApi-Login erfolgreich!
                      2025-07-24 17:43:14.066  - info: mihome-vacuum.0 (168226) settest next timer: not available
                      2025-07-24 17:43:14.150  - debug: mihome-vacuum.0 (168226) Create State for control: {"id":"mihome-vacuum.0.control"}
                      2025-07-24 17:43:14.400  - debug: mihome-vacuum.0 (168226) Create State for Queue: queue
                      2025-07-24 17:43:14.478  - debug: mihome-vacuum.0 (168226) Create State for map: 
                      2025-07-24 17:43:14.521  - debug: mihome-vacuum.0 (168226) Create State for map: map64
                      2025-07-24 17:43:14.522  - debug: mihome-vacuum.0 (168226) Create State for map: actualMap
                      2025-07-24 17:43:14.523  - debug: mihome-vacuum.0 (168226) Create State for map: mapStatus
                      2025-07-24 17:43:14.525  - debug: mihome-vacuum.0 (168226) Create State for map: mapURL
                      2025-07-24 17:43:14.525  - debug: mihome-vacuum.0 (168226) Create State for map: loadMap
                      2025-07-24 17:43:14.526  - debug: mihome-vacuum.0 (168226) Create State done!
                      2025-07-24 17:43:14.527  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                      2025-07-24 17:43:14.528  - debug: mihome-vacuum.0 (168226) Message= {"id":2,"method":"get_status"}
                      2025-07-24 17:43:14.536  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":889,"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":2}
                      2025-07-24 17:43:14.537  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":889,"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 17:43:14.691  - debug: mihome-vacuum.0 (168226) Message= {"id":3,"method":"get_map_v1"}
                      2025-07-24 17:43:14.699  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":["retry"],"id":3}
                      2025-07-24 17:43:15.001  - debug: mihome-vacuum.0 (168226) Message= {"id":4,"method":"get_map_v1"}
                      2025-07-24 17:43:17.003  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:43:17.305  - debug: mihome-vacuum.0 (168226) Message= {"id":5,"method":"get_map_v1"}
                      2025-07-24 17:43:17.313  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":["roboroommap%2F74213525%2F2"],"id":5}
                      2025-07-24 17:43:17.313  - debug: mihome-vacuum.0 (168226) Mappointer_updated
                      2025-07-24 17:43:17.315  - debug: mihome-vacuum.0 (168226) update_Map Mimap enabled
                      2025-07-24 17:43:17.315  - debug: mihome-vacuum.0 (168226) update_Map need new mapurl
                      2025-07-24 17:43:17.321  - debug: mihome-vacuum.0 (168226) CloudApi-call: https://api.io.mi.com/app/home/getmapfileurl with {"data":"{\"obj_name\":\"roboroommap%2F74213525%2F2\"}"}
                      2025-07-24 17:43:17.328  - debug: mihome-vacuum.0 (168226) Message= {"id":6,"method":"get_room_mapping"}
                      2025-07-24 17:43:17.337  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":6}
                      2025-07-24 17:43:17.340  - debug: mihome-vacuum.0 (168226) Message= {"id":7,"method":"get_consumable"}
                      2025-07-24 17:43:17.342  - debug: mihome-vacuum.0 (168226) Message= {"id":8,"method":"get_network_info"}
                      2025-07-24 17:43:17.349  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"main_brush_work_time":1320,"side_brush_work_time":330828,"filter_work_time":1320,"sensor_dirty_time":1343}],"id":7}
                      2025-07-24 17:43:17.351  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":8}
                      2025-07-24 17:43:17.352  - debug: mihome-vacuum.0 (168226) Message= {"id":9,"method":"get_sound_volume"}
                      2025-07-24 17:43:17.358  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":9}
                      2025-07-24 17:43:17.360  - debug: mihome-vacuum.0 (168226) Message= {"id":10,"method":"get_multi_maps_list"}
                      2025-07-24 17:43:17.368  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":10}
                      2025-07-24 17:43:17.369  - debug: mihome-vacuum.0 (168226) Startup: getMultiMapsList Answer: true
                      2025-07-24 17:43:17.370  - debug: mihome-vacuum.0 (168226) Startup: Delete getMultiMapsList
                      2025-07-24 17:43:17.371  - debug: mihome-vacuum.0 (168226) Message= {"id":11,"method":"get_clean_summary"}
                      2025-07-24 17:43:17.386  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[330035,4140217500,288,[]],"id":11}
                      2025-07-24 17:43:17.388  - debug: mihome-vacuum.0 (168226) Startup: setGetCleanSummary Answer: true
                      2025-07-24 17:43:17.389  - debug: mihome-vacuum.0 (168226) Startup: Delete setGetCleanSummary
                      2025-07-24 17:43:17.389  - debug: mihome-vacuum.0 (168226) Message= {"id":12,"method":"get_consumable"}
                      2025-07-24 17:43:17.399  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"main_brush_work_time":1320,"side_brush_work_time":330828,"filter_work_time":1320,"sensor_dirty_time":1343}],"id":12}
                      2025-07-24 17:43:17.400  - debug: mihome-vacuum.0 (168226) Startup: setGetConsumable Answer: true
                      2025-07-24 17:43:17.401  - debug: mihome-vacuum.0 (168226) Startup: Delete setGetConsumable
                      2025-07-24 17:43:17.402  - debug: mihome-vacuum.0 (168226) Message= {"id":13,"method":"get_carpet_mode"}
                      2025-07-24 17:43:17.411  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":13}
                      2025-07-24 17:43:17.412  - info: mihome-vacuum.0 (168226) create state for carpet_mode
                      2025-07-24 17:43:17.413  - debug: mihome-vacuum.0 (168226) Message= {"id":14,"method":"get_carpet_mode"}
                      2025-07-24 17:43:17.498  - debug: mihome-vacuum.0 (168226) Message= {"id":15,"method":"get_clean_summary"}
                      2025-07-24 17:43:19.200  - debug: mihome-vacuum.0 (168226) CloudApi-get {"code":0,"message":"ok","result":{"url":"https://cnbj2.fds.api.xiaomi.com/robomap/roboroommap/74213525/2?Expires=1753373599000&GalaxyAccessKeyId=5ZIFFERN5&Signature=ERSETZT=","obj_name":"roboroommap/74213525/2","method":"GET","expires_time":1753373599,"ok":true}}
                      2025-07-24 17:43:19.202  - debug: mihome-vacuum.0 (168226) update_Map got new url:https://cnbj2.fds.api.xiaomi.com/robomap/roboroommap/74213525/2?Expires=1753373599000&GalaxyAccessKeyId=5ZIFFERN5&Signature=ERSETZT=
                      2025-07-24 17:43:19.203  - debug: mihome-vacuum.0 (168226) update_Map got new expires:1753373599
                      2025-07-24 17:43:19.204  - debug: mihome-vacuum.0 (168226) update_Map got new time:1753371797
                      2025-07-24 17:43:19.415  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:43:19.501  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:43:19.657  - debug: mihome-vacuum.0 (168226) creating map
                      2025-07-24 17:43:23.181  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882549bffffffffffffffffffffffffffffffff
                      2025-07-24 17:43:33.185  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254a5ffffffffffffffffffffffffffffffff
                      2025-07-24 17:43:43.190  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254afffffffffffffffffffffffffffffffff
                      2025-07-24 17:43:53.193  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254b9ffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:03.196  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254c3ffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:13.201  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254cdffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:20.417  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                      2025-07-24 17:44:20.418  - debug: mihome-vacuum.0 (168226) Message= {"id":16,"method":"get_status"}
                      2025-07-24 17:44:22.420  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:44:22.420  - debug: mihome-vacuum.0 (168226) Message= {"id":17,"method":"get_network_info"}
                      2025-07-24 17:44:23.204  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254d7ffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:24.421  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:44:24.422  - debug: mihome-vacuum.0 (168226) Message= {"id":18,"method":"get_sound_volume"}
                      2025-07-24 17:44:26.423  - debug: mihome-vacuum.0 (168226) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                      2025-07-24 17:44:26.424  - debug: mihome-vacuum.0 (168226) Message= {"id":19,"method":"get_carpet_mode"}
                      2025-07-24 17:44:26.432  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":19}
                      2025-07-24 17:44:33.208  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254e1ffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:43.212  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254ebffffffffffffffffffffffffffffffff
                      2025-07-24 17:44:53.214  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254f5ffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:03.220  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c6895688254ffffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:13.226  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825509ffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:23.233  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825513ffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:27.486  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                      2025-07-24 17:45:27.487  - debug: mihome-vacuum.0 (168226) Message= {"id":20,"method":"get_status"}
                      2025-07-24 17:45:27.496  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":890,"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":20}
                      2025-07-24 17:45:27.497  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":890,"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 17:45:27.499  - debug: mihome-vacuum.0 (168226) Message= {"id":21,"method":"get_network_info"}
                      2025-07-24 17:45:27.505  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":21}
                      2025-07-24 17:45:27.506  - debug: mihome-vacuum.0 (168226) Message= {"id":22,"method":"get_sound_volume"}
                      2025-07-24 17:45:27.514  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":22}
                      2025-07-24 17:45:27.515  - debug: mihome-vacuum.0 (168226) Message= {"id":23,"method":"get_carpet_mode"}
                      2025-07-24 17:45:27.644  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":23}
                      2025-07-24 17:45:33.238  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882551dffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:43.241  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825527ffffffffffffffffffffffffffffffff
                      2025-07-24 17:45:53.249  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825531ffffffffffffffffffffffffffffffff
                      2025-07-24 17:46:03.254  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882553bffffffffffffffffffffffffffffffff
                      2025-07-24 17:46:13.256  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825545ffffffffffffffffffffffffffffffff
                      2025-07-24 17:46:23.261  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c68956882554fffffffffffffffffffffffffffffffff
                      2025-07-24 17:46:28.758  - debug: mihome-vacuum.0 (168226) get params for stock Vacuum
                      2025-07-24 17:46:28.759  - debug: mihome-vacuum.0 (168226) Message= {"id":24,"method":"get_status"}
                      2025-07-24 17:46:28.768  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"msg_ver":8,"msg_seq":915,"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":24}
                      2025-07-24 17:46:28.769  - debug: mihome-vacuum.0 (168226) setGetStatus {"msg_ver":8,"msg_seq":915,"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 17:46:28.771  - debug: mihome-vacuum.0 (168226) Message= {"id":25,"method":"get_network_info"}
                      2025-07-24 17:46:28.782  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":"unknown_method","id":25}
                      2025-07-24 17:46:28.783  - debug: mihome-vacuum.0 (168226) Message= {"id":26,"method":"get_sound_volume"}
                      2025-07-24 17:46:28.947  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[90],"id":26}
                      2025-07-24 17:46:28.948  - debug: mihome-vacuum.0 (168226) Message= {"id":27,"method":"get_carpet_mode"}
                      2025-07-24 17:46:28.958  - debug: mihome-vacuum.0 (168226) MIIO RECIVE: {"result":[{"enable":0,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":27}
                      2025-07-24 17:46:33.267  - debug: mihome-vacuum.0 (168226) Receive <<< Helo <<< 2131002000000000046c689568825559ffffffffffffffffffffffffffffffff
                      
                      

                      Schaut aber für mich eigentlich sauber aus.

                      D Nicht stören
                      D Nicht stören
                      dirkhe
                      Developer
                      schrieb am zuletzt editiert von
                      #20

                      @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 BraunT 1 Antwort Letzte Antwort
                      0
                      • D dirkhe

                        @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 BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #21

                        @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__{}

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        • D Nicht stören
                          D Nicht stören
                          dirkhe
                          Developer
                          schrieb am zuletzt editiert von
                          #22

                          @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 BraunT 2 Antworten Letzte Antwort
                          0
                          • D dirkhe

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

                            D Nicht stören
                            D Nicht stören
                            dirkhe
                            Developer
                            schrieb am zuletzt editiert von
                            #23

                            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 Antwort Letzte Antwort
                            0
                            • D dirkhe

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

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #24

                              @dirkhe sagte in mihome vacuum - login failed:

                              Kannst du ggf. mla deinenen Browser refreshen?

                              Browser neugestartet, sieht aber exakt aus wie zuvor.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              D 2 Antworten Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @dirkhe sagte in mihome vacuum - login failed:

                                Kannst du ggf. mla deinenen Browser refreshen?

                                Browser neugestartet, sieht aber exakt aus wie zuvor.

                                D Nicht stören
                                D Nicht stören
                                dirkhe
                                Developer
                                schrieb am zuletzt editiert von
                                #25

                                @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 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @dirkhe sagte in mihome vacuum - login failed:

                                  Kannst du ggf. mla deinenen Browser refreshen?

                                  Browser neugestartet, sieht aber exakt aus wie zuvor.

                                  D Nicht stören
                                  D Nicht stören
                                  dirkhe
                                  Developer
                                  schrieb am zuletzt editiert von
                                  #26

                                  @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 BraunT 1 Antwort Letzte Antwort
                                  0
                                  • D dirkhe

                                    @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 BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    schrieb am zuletzt editiert von
                                    #27

                                    @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"}
                                    
                                    

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    1 Antwort Letzte Antwort
                                    0
                                    • D Nicht stören
                                      D Nicht stören
                                      dirkhe
                                      Developer
                                      schrieb am zuletzt editiert von
                                      #28

                                      @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 BraunT 1 Antwort Letzte Antwort
                                      0
                                      • D dirkhe

                                        @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 BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von Thomas Braun
                                        #29

                                        @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__{}
                                        
                                        

                                        Linux-Werkzeugkasten:
                                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                        NodeJS Fixer Skript:
                                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                        D 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT 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 Nicht stören
                                          D Nicht stören
                                          dirkhe
                                          Developer
                                          schrieb am zuletzt editiert von
                                          #30

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

                                          this.logger.error(`CloudApi: executeEncryptedApiCall Error:${err.message}`);
                                          
                                          Thomas BraunT bahnuhrB 2 Antworten Letzte Antwort
                                          1
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          572

                                          Online

                                          32.6k

                                          Benutzer

                                          82.2k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe