Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter mihome-vacuum v2.0.x

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Test Adapter mihome-vacuum v2.0.x

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

      @BamBam89 Du hast nurdie Filterung auf debug eingestellt. Du musst dem Adapter in den Instanzen aud debug einstellen:
      5d70ad97-748e-4096-bcb5-42519867df77-image.png

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

        @DarkDevil Ist schon tausendmal geschrieben worden, wahrscheinlich musst du canvas manuell installieren, bitte mal die sufu nutzen oder halt das readme lesen

        1 Reply Last reply Reply Quote 0
        • B
          BamBam89 @dirkhe last edited by

          @dirkhe

          und wieder was dazu gelernt....

          hier ein Auszug aus dem Log:

          mihome-vacuum.0	2020-04-10 22:58:59.846	info	(27269) connecting, this can take up to 10 minutes ...
          mihome-vacuum.0	2020-04-10 22:58:59.846	debug	(27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90de13ffffffffffffffffffffffffffffffff
          mihome-vacuum.0	2020-04-10 22:58:54.860	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:58:54.859	debug	(27269) no answer for undefined(id:3) received, giving up
          mihome-vacuum.0	2020-04-10 22:58:49.858	debug	(27269) sendMsg[3] >>> {"id":3,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:44.857	debug	(27269) sendMsg[2] >>> {"id":3,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:39.856	debug	(27269) sendMsg[1] >>> {"id":3,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:39.850	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:58:39.849	info	(27269) connecting, this can take up to 10 minutes ...
          mihome-vacuum.0	2020-04-10 22:58:39.848	debug	(27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddffffffffffffffffffffffffffffffffff
          mihome-vacuum.0	2020-04-10 22:58:34.862	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:58:34.861	debug	(27269) no answer for undefined(id:2) received, giving up
          mihome-vacuum.0	2020-04-10 22:58:29.860	debug	(27269) sendMsg[3] >>> {"id":2,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:24.859	debug	(27269) sendMsg[2] >>> {"id":2,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:19.858	debug	(27269) sendMsg[1] >>> {"id":2,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:19.849	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:58:19.848	info	(27269) connecting, this can take up to 10 minutes ...
          mihome-vacuum.0	2020-04-10 22:58:19.847	debug	(27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddebffffffffffffffffffffffffffffffff
          mihome-vacuum.0	2020-04-10 22:58:14.970	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:58:14.969	debug	(27269) no answer for undefined(id:1) received, giving up
          mihome-vacuum.0	2020-04-10 22:58:09.968	debug	(27269) sendMsg[3] >>> {"id":1,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:04.967	debug	(27269) sendMsg[2] >>> {"id":1,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:58:02.153	debug	(27269) Xiaomi Cloud: Login successful
          mihome-vacuum.0	2020-04-10 22:58:00.368	info	(27269) set nächster Timer: Nicht verfügbar
          mihome-vacuum.0	2020-04-10 22:57:59.965	debug	(27269) sendMsg[1] >>> {"id":1,"method":"get_status"}
          mihome-vacuum.0	2020-04-10 22:57:59.940	debug	(27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
          mihome-vacuum.0	2020-04-10 22:57:59.938	info	(27269) connecting, this can take up to 10 minutes ...
          mihome-vacuum.0	2020-04-10 22:57:59.937	debug	(27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddd7ffffffffffffffffffffffffffffffff
          mihome-vacuum.0	2020-04-10 22:57:59.847	debug	(27269) server started on 0.0.0.0:54321
          mihome-vacuum.0	2020-04-10 22:57:59.828	debug	(27269) Ios Token decrypted to: #i ~;e~O%v\p"FqXzcn&FlZ8O
          mihome-vacuum.0	2020-04-10 22:57:59.824	info	(27269) Create state clean_home for controlling by cloud adapter
          mihome-vacuum.0	2020-04-10 22:57:59.822	info	(27269) Expert mode enabled, states created
          mihome-vacuum.0	2020-04-10 22:57:59.808	debug	(27269) Xiaomi Cloud: Logging in
          mihome-vacuum.0	2020-04-10 22:57:59.806	debug	(27269) load Map creator... true
          mihome-vacuum.0	2020-04-10 22:57:59.709	info	(27269) starting. Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0
          mihome-vacuum.0	2020-04-10 22:57:57.610	debug	(27269) statesDB connected
          mihome-vacuum.0	2020-04-10 22:57:57.609	debug	(27269) States connected to redis: 127.0.0.1:9000
          mihome-vacuum.0	2020-04-10 22:57:57.596	debug	(27269) States create System PubSub Client
          mihome-vacuum.0	2020-04-10 22:57:57.593	debug	(27269) States create User PubSub Client
          mihome-vacuum.0	2020-04-10 22:57:57.585	debug	(27269) Redis States: Use Redis connection: 127.0.0.1:9000
          mihome-vacuum.0	2020-04-10 22:57:57.582	debug	(27269) objectDB connected
          mihome-vacuum.0	2020-04-10 22:57:57.575	debug	(27269) Objects connected to redis: 127.0.0.1:9001
          mihome-vacuum.0	2020-04-10 22:57:57.558	debug	(27269) Objects client initialize lua scripts
          mihome-vacuum.0	2020-04-10 22:57:57.557	debug	(27269) Objects create User PubSub Client
          mihome-vacuum.0	2020-04-10 22:57:57.556	debug	(27269) Objects create System PubSub Client
          mihome-vacuum.0	2020-04-10 22:57:57.551	debug	(27269) Objects client ready ... initialize now
          mihome-vacuum.0	2020-04-10 22:57:57.167	debug	(27269) Redis Objects: Use Redis connection: 127.0.0.1:9001
          
          1 Reply Last reply Reply Quote 0
          • D
            dirkhe Developer last edited by

            Geh mal in die xiaomi App und verbinde dich mit dem robbi. Manchmal hilft das.

            1 Reply Last reply Reply Quote 0
            • D
              DarkDevil last edited by

              Die Installation (bzw. das Update) haben schonmal geklappt. Danke dafür.
              Jetzt habe ich aber anscheinend den gleichen Fehler wie BamBam89

              mihome-vacuum.0	2020-04-11 07:47:03.668	info	(28242) connecting, this can take up to 10 minutes ...
              mihome-vacuum.0	2020-04-11 07:47:03.668	warn	(28242) Time difference between Mihome Vacuum and ioBroker: 1 sec
              mihome-vacuum.0	2020-04-11 07:47:03.667	debug	(28242) Receive <<< Helo <<< 21310020000000000706b6555e9159d8ffffffffffffffffffffffffffffffff
              mihome-vacuum.0	2020-04-11 07:46:58.788	debug	(28242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
              mihome-vacuum.0	2020-04-11 07:46:58.787	debug	(28242) no answer for undefined(id:1) received, giving up
              mihome-vacuum.0	2020-04-11 07:46:55.373	debug	(28242) system.adapter.admin.0: logging true
              mihome-vacuum.0	2020-04-11 07:46:53.786	debug	(28242) sendMsg[3] >>> {"id":1,"method":"get_status"}
              mihome-vacuum.0	2020-04-11 07:46:48.785	debug	(28242) sendMsg[2] >>> {"id":1,"method":"get_status"}
              mihome-vacuum.0	2020-04-11 07:46:46.064	debug	(28242) Xiaomi Cloud: Login successful
              mihome-vacuum.0	2020-04-11 07:46:45.241	debug	(28242) system.adapter.admin.0: logging false
              mihome-vacuum.0	2020-04-11 07:46:44.177	info	(28242) set nächster Timer: Nicht verfügbar
              mihome-vacuum.0	2020-04-11 07:46:43.784	debug	(28242) sendMsg[1] >>> {"id":1,"method":"get_status"}
              mihome-vacuum.0	2020-04-11 07:46:43.755	debug	(28242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
              
              haselchen 1 Reply Last reply Reply Quote 0
              • haselchen
                haselchen Most Active @DarkDevil last edited by

                @DarkDevil

                Hast du, wie vorher schonmal geraten, die MiHome App geöffnet ?

                D 1 Reply Last reply Reply Quote 0
                • B
                  BamBam89 last edited by

                  Morgen zusammen,

                  also ich hab das schon gemacht, allerdings ohne besondere Verbesserung:

                  mihome-vacuum.0	2020-04-11 09:33:39.352	debug	(5753) sendMsg[1] >>> {"id":478,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:33:39.349	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:33:39.348	info	(5753) connecting, this can take up to 10 minutes ...
                  mihome-vacuum.0	2020-04-11 09:33:39.348	debug	(5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172d3ffffffffffffffffffffffffffffffff
                  mihome-vacuum.0	2020-04-11 09:33:34.353	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:33:34.353	debug	(5753) no answer for undefined(id:477) received, giving up
                  mihome-vacuum.0	2020-04-11 09:33:29.353	debug	(5753) sendMsg[3] >>> {"id":477,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:33:24.352	debug	(5753) sendMsg[2] >>> {"id":477,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:33:19.351	debug	(5753) sendMsg[1] >>> {"id":477,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:33:19.346	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:33:19.346	info	(5753) connecting, this can take up to 10 minutes ...
                  mihome-vacuum.0	2020-04-11 09:33:19.346	debug	(5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172bfffffffffffffffffffffffffffffffff
                  mihome-vacuum.0	2020-04-11 09:33:14.351	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:33:14.350	debug	(5753) no answer for undefined(id:476) received, giving up
                  mihome-vacuum.0	2020-04-11 09:33:09.349	debug	(5753) sendMsg[3] >>> {"id":476,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:33:04.349	debug	(5753) sendMsg[2] >>> {"id":476,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:32:59.347	debug	(5753) sendMsg[1] >>> {"id":476,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:32:59.346	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:32:59.346	info	(5753) connecting, this can take up to 10 minutes ...
                  mihome-vacuum.0	2020-04-11 09:32:59.346	debug	(5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172abffffffffffffffffffffffffffffffff
                  mihome-vacuum.0	2020-04-11 09:32:54.354	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:32:54.354	debug	(5753) no answer for undefined(id:475) received, giving up
                  mihome-vacuum.0	2020-04-11 09:32:49.353	debug	(5753) sendMsg[3] >>> {"id":475,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:32:44.352	debug	(5753) sendMsg[2] >>> {"id":475,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:32:39.351	debug	(5753) sendMsg[1] >>> {"id":475,"method":"get_status"}
                  mihome-vacuum.0	2020-04-11 09:32:39.348	debug	(5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                  mihome-vacuum.0	2020-04-11 09:32:39.347	info	(5753) connecting, this can take up to 10 minutes ...~~~~
                  ```~~
                  
                  haselchen 1 Reply Last reply Reply Quote 0
                  • haselchen
                    haselchen Most Active @BamBam89 last edited by

                    @BamBam89
                    Welcher Sauger welche Firmware Version?

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      BamBam89 @haselchen last edited by

                      @haselchen

                      Es handelt sich um einen S502-00
                      Firmware 3.5.7_002008

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

                        @BamBam89

                        Habe ich auch beides.
                        Welche Adapter Version hast du drauf?
                        Mit RC Nummer wenn du hast.

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          BamBam89 @haselchen last edited by

                          @haselchen

                          Version 2.0.9. Mit RC Nummer kann ich aber nichts anfangen 🙂

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

                            @BamBam89

                            Auf debug stellen über den Experten Modus und dann den Adapter neu starten. Im Log steht dann die RC Nummer hinter 2.0.9

                            B 1 Reply Last reply Reply Quote 0
                            • B
                              BamBam89 @haselchen last edited by

                              @haselchen

                              Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0

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

                                @BamBam89

                                Ist aktuell.
                                Und das Problem ist, dass er sich nicht verbindet?
                                Oder habe ich da was überlesen?

                                B 1 Reply Last reply Reply Quote 0
                                • L
                                  ltsalvatore @Diginix last edited by

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

                                  @iphone333 Dann passt was nicht. Sollte eigentlich so im RAW von fan_power aussehen:

                                  9c3fb928-bbb2-41ca-b77c-8fffd26ba795-image.png

                                  Welche Adapter Version nutzt du?

                                  Hi Dginix,

                                  ich wollte mal fragen, ob es mittlerweile ein lösung zu dem problem gibt.

                                  ich habe auch das problem wie @iphone333, dass trotz aktuellen adapter v2.0.7 über den wert von fan_power* keine änderungen vorgenommen werden können.

                                  auch bei mir sind die alten werte noch drin gewesen, habe diese um die von dir genannten ergänzt.. hilft aber leider nichts..

                                  kuriose ist dabei, wenn ich einen wert über vis eintrage, dann funktioniert es einwandfrei..
                                  nur über blockly script (sowohl text als auch zahl) nicht.

                                  haselchen L 2 Replies Last reply Reply Quote 0
                                  • B
                                    BamBam89 @haselchen last edited by

                                    @haselchen

                                    also wenn ich das richtig verstehe, müsste ich ja über die Buttons die entsprechenden Befehle ausgeben können:

                                    78c5822a-bd85-4787-88ce-11fbe9bbf34c-image.png

                                    Da tut sich aber nichts. Er wird auch in den Instanzen nicht grün

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

                                      @BamBam89

                                      Zeig mal bitte deine Adpatereinstellungen

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

                                        @ltsalvatore

                                        Aktuell wäre 2.0.9 RC7

                                        Habe das Blockly aus dem Forum.
                                        Es wird anscheinend von 100% ausgegangen für die einzelnen Stufen.
                                        99206ea4-bdf9-43eb-b9e6-7a9d632b921e-grafik.png

                                        L 1 Reply Last reply Reply Quote 0
                                        • D
                                          DarkDevil @haselchen last edited by

                                          @haselchen jo, das habe ich. Allerdings ohne Veränderung. Der Adapter bleibt gelb

                                          1 Reply Last reply Reply Quote 0
                                          • B
                                            BamBam89 @haselchen last edited by

                                            @haselchen

                                            24873234-4d38-4baa-9abf-2ce5b7186189-image.png

                                            e26a84e5-44e4-4a1e-9932-5fb0df3545ee-image.png

                                            5e8b4104-0328-499a-b818-e371c45eebd2-image.png

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            560
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

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