Navigation

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

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter mihome-cloud

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      darksside last edited by darksside

      Hallo. Vielen Dank für einen guten Adapter. Es gibt eine Frage: Ich habe eine Viomi-Klimaanlage installiert, alles ist im Adapter erschienen, bis auf eine. Ich kann es nicht ein- oder ausschalten, es gibt keine solche Einstellung. Aber in der Mi home App kann ich das tun. Ist es möglich, dies dem Adapter hinzuzufügen?
      iobroker_mihome.jpg

      1 Reply Last reply Reply Quote 0
      • Иван Кужелев
        Иван Кужелев last edited by

        The same goes for the Viomi air conditioner. How to solve it?

        1 Reply Last reply Reply Quote 0
        • P
          pocket1607 last edited by

          Hi
          Ich bekomme keinen Login Anmeldedaten sind die selben wie in der App aber mit dem Adapter kommt nur Login Failed.
          Versuche einen x10+ in Iob zu bekommen.
          Anbei das Log vom Anmeldeversuch.


          mihome-cloud.0
          2024-07-26 21:45:30.140 error Login failed

          mihome-cloud.0
          2024-07-26 21:45:30.139 debug "&&&START&&&{"notificationUrl":"/identity/authStart?sid=xiaomiio&context=QAEbsfy5hSypv9Y0dR5aBTuIF7FW1pY27IJs3CtHkFqEJsSnAMd26NnpjxCMWBZ5nGk85uAAPCJBFn3nMvWvfumTBxbEGM7RuzUQNJ2MKD3BbBxOmtdbcK30NR58BRwJcdGjTFXn9zt5JYE91WSs8qV4CzWg3RbtdSKi4ATGRQa4MyJgY0XAw4n4ChxEVkeReuGVvenSZQ3yP0IcM-Uaf6yh8X_tIBFMOk5IpevXcgRBJY1I8JTq-r1HA08Mhi-wGsRhhDyhYHtXvmBE0BciqGicuevDFiiQ_3dTQ2kzH6CQ1btM8D55opwynhnd1zixFm-92gm1GkfSGU3-Df8dYdbq3XhsKSjl6rxHTs1XGQ5sHoMaEHOUDT8N6Dq593YzMqNN-eJ7dzEok9DjCYFOpF9C_NSOp1E4ym9IInY8UaAPM5WznCvh7g9gmbMRZ2dqDhvnnZTfEe1Dbkg8GlfcMll2QtXaarm2pSkR3zPqYO6cUdW4GCz9h5cuors40QUzw7hs6oEshEWWeS3s9n3OHR5UytrkKtuT86PpFnwVBmyBBqZd3eBjY8zq-lZ61GsLQ1-sWpGc1t3kmRYqwkI9lKCvWppeb4PzYMOst6kWkJ2E6mX300fq65ip5EO-R4TdRa5s6jXx3O356SoOVy3g9KZKHpMIAPl3gaAcmlpIyE0SXmn7CXjk5xIi8bq72QCdvaj2eSnDPdHEYha-KdE6patoGEr3XqE_BalatBgbgMKh2EQFMM4wMmkT_rn0Sn-OCTqnxvyJd5YYKc_YDEIGVg&_locale=de_DE","result":"ok","code":0,"captchaUrl":null,"description":"成功","location":"","securityStatus":16,"pwd":0,"child":0,"desc":"成功"}"

          mihome-cloud.0
          2024-07-26 21:45:29.692 debug "&&&START&&&{"serviceParam":"{\"checkSafePhone\":false,\"checkSafeAddress\":false,\"lsrp_score\":0.0}","qs":"%3Fsid%3Dxiaomiio%26_json%3Dtrue","code":70016,"description":"登录验证失败","securityStatus":0,"_sign":"0psXfr43eNI0IX6q9Suk3qWbRqU=","sid":"xiaomiio","result":"error","captchaUrl":null,"callback":"https://sts.api.io.mi.com/sts","location":"https://account.xiaomi.com/fe/service/login?_json=true&sid=xiaomiio&qs=%3Fsid%3Dxiaomiio%26_json%3Dtrue&callback=https%3A%2F%2Fsts.api.io.mi.com%2Fsts&_sign=0psXfr43eNI0IX6q9Suk3qWbRqU%3D&serviceParam={"checkSafePhone"%3Afalse%2C"checkSafeAddress"%3Afalse%2C"lsrp_score"%3A0.0}&showActiveX=false&theme=&needTheme=false&bizDeviceType=","pwd":0,"child":0,"desc":"登录验证失败"}"

          mihome-cloud.0
          2024-07-26 21:45:29.331 info Login to MiHome Cloud

          mihome-cloud.0
          2024-07-26 21:45:29.298 info starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.mihome-cloud, node: v18.16.1, js-controller: 5.0.19

          mihome-cloud.0
          2024-07-26 21:45:29.013 debug Plugin sentry Initialize Plugin (enabled=true)

          mihome-cloud.0
          2024-07-26 21:45:28.959 debug States connected to redis: 0.0.0.0:9000

          mihome-cloud.0
          2024-07-26 21:45:28.854 debug States create User PubSub Client

          mihome-cloud.0
          2024-07-26 21:45:28.854 debug States create System PubSub Client

          mihome-cloud.0
          2024-07-26 21:45:28.821 debug Redis States: Use Redis connection: 0.0.0.0:9000

          mihome-cloud.0
          2024-07-26 21:45:28.758 debug Objects connected to redis: 0.0.0.0:9001

          mihome-cloud.0
          2024-07-26 21:45:28.754 debug Objects client initialize lua scripts

          mihome-cloud.0
          2024-07-26 21:45:28.650 debug Objects create User PubSub Client

          mihome-cloud.0
          2024-07-26 21:45:28.650 debug Objects create System PubSub Client

          mihome-cloud.0
          2024-07-26 21:45:28.648 debug Objects client ready ... initialize now

          mihome-cloud.0
          2024-07-26 21:45:28.595 debug Redis Objects: Use Redis connection: 0.0.0.0:9001

          1 Reply Last reply Reply Quote 0
          • M
            mojo1986 last edited by

            Hallo Zusammen

            Ich wollte fragen, ob jemand hier eine Xiaomi Mi Scale 2 mit dem Mihome-cloud Adapter einbinden konnte? Bei mir wird zwar unter General alles schön ausgefüllt aber beim Status bleibt alles rot.

            1 Reply Last reply Reply Quote 0
            • mattgas
              mattgas last edited by

              @tombox: Ich versuche mit dem Adapter gerade einen Xiaomi X20+ Saugroboter zu integrieren, scheitere aber an den States, die ich setzen muss, um an die Karten ID bzw. Room-IDs zu kommen. Die oben beschriebenen Datenpunkte gibt es nicht, stattdessen nur map-req und update-map. Ich habe Werte entsprechend der Spec für den Roboter (https://home.miot-spec.com/spec/xiaomi.vacuum.c102gl) gesetzt, im IObroker log kommt

              
              mihome-cloud.0
              2024-11-03 10:26:44.136	info	Set 1066061049.status.robot-time to 1730625987270
              
              mihome-cloud.0
              2024-11-03 10:26:44.131	info	Set 1066061049.status.object-name to
              
              mihome-cloud.0
              2024-11-03 10:26:44.125	info	Set 1066061049.status.map-data to
              
              mihome-cloud.0
              2024-11-03 10:26:44.107	info	{"code":0,"message":"ok","result":{"did":"1066061049","miid":0,"siid":6,"aiid":1,"code":0,"out":["","",1730625987270],"exe_time":11,"net_cost":36,"ot_cost":7,"otlocalts":1730626004090158,"_oa_rpc_cost":60,"withLatency":0}}
              

              Ich gehe davon aus, dass in object-name und map-data Informationen zu Karte und Room-IDs auftauchen sollten, stattdessen gibts leere Einträge...kannst du (oder jemand anderes) hier weiterhelfen?

              Danke und Grüße

              1 Reply Last reply Reply Quote 0
              • David Peters
                David Peters last edited by

                @mattgas
                hast du das inzwischen hinbekommen? Ich hänge am selben Problem. Auch mit dem X20+

                Gruß

                David

                1 Reply Last reply Reply Quote 0
                • B
                  Beowolf last edited by Beowolf

                  Ich bekomme seit ein paar Tagen diese Fehlermeldungen.

                  mihome-cloud.0
                  	2025-01-27 10:11:16.663	error	{"code":0,"message":"invalid signature"}
                  mihome-cloud.0
                  	2025-01-27 10:11:16.663	error	AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:599:11) at IncomingMessage.emit (node:events:530:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1698:12) at processTicksAndRejections (node:internal/process/task_queues:82:21) at Axios.request (/opt/iobroker/node_modules/axios/lib/core/Axios.js:45:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.updateDevicesViaSpec (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:1043:9) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:103:9)
                  mihome-cloud.0
                  	2025-01-27 10:11:16.663	error	AxiosError: Request failed with status code 400
                  mihome-cloud.0
                  	2025-01-27 10:11:16.663	error	/miotspec/prop/get
                  

                  Was mache ich falsch?

                  Die Adapter von mihome-cloud und die mihome-vacuum Instanzen sind auf "grün"

                  1 Reply Last reply Reply Quote 0
                  • M
                    Manolo last edited by

                    Ich bekomme seit ein paar Tagen die gleiche Fehlermeldung.
                    Adapter mihome-cloud ist aber grün und die Objekte werden aktualisiert.
                    Hat da irgendwer schon eine Lösung?

                    Eduard77 1 Reply Last reply Reply Quote 0
                    • Eduard77
                      Eduard77 @Manolo last edited by

                      Hallo, wir der Adapter eigentlich weiter entwickelt?
                      Wenn ich die GitHub Seite anschaue, dann ist dort seit 2 jahren nichts passiert.
                      Schade eigentlich.
                      Ich bekomme auch vermehrt Fehler im Protokoll.

                      
                      mihome-cloud.0 2025-05-21 06:33:36.243	error	{"code":0,"message":"invalid signature"}
                      mihome-cloud.0 2025-05-21 06:33:36.243	error	AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:599:11) at IncomingMessage.emit (node:events:536:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1698:12) at processTicksAndRejections (node:internal/process/task_queues:82:21) at Axios.request (/opt/iobroker/node_modules/axios/lib/core/Axios.js:45:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.updateDevicesViaSpec (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:1043:9) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:103:9)
                      mihome-cloud.0 2025-05-21 06:33:36.243	error	AxiosError: Request failed with status code 400
                      mihome-cloud.0 2025-05-21 06:33:36.243	error	/miotspec/prop/get
                      mihome-cloud.0 2025-05-21 06:33:36.145	info	Login successful
                      mihome-cloud.0 2025-05-21 06:33:36.129	error	{"code":0,"message":"invalid signature"}
                      mihome-cloud.0 2025-05-21 06:33:36.129	error	AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:599:11) at IncomingMessage.emit (node:events:536:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1698:12) at processTicksAndRejections (node:internal/process/task_queues:82:21) at Axios.request (/opt/iobroker/node_modules/axios/lib/core/Axios.js:45:41) at processTicksAndRejections (node:internal/process/task_queues:95:5) at MihomeCloud.updateDevicesViaSpec (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:1043:9) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.mihome-cloud/main.js:103:9)
                      mihome-cloud.0 2025-05-21 06:33:36.129	error	AxiosError: Request failed with status code 400
                      mihome-cloud.0 2025-05-21 06:33:36.125	error	/miotspec/prop/get
                      
                      T 1 Reply Last reply Reply Quote 0
                      • T
                        tombox @Eduard77 last edited by

                        @edis77 Die GitHub version versteckt die Meldung

                        1 Reply Last reply Reply Quote 0
                        • E
                          eve11 last edited by eve11

                          Hallo zusammen,

                          ich wollte wieder einmal meinen Xiaomi Sauger benutzen, dabei ist mir aufgefallen, dass dieser nicht mehr mit dem WLAN verbunden war.
                          Als auch das die Sprache wieder auf Chinesisch war. Ich habe ihn dann zurück gesetzt und wieder in der Mi-Home App aufgenommen. Soweit so gut => In der App funktioniert er wieder.
                          Nur der Adapter will nicht. Ich kann mich auch nicht in der Xiaomi Cloud anmelden innerhalb des Adapter. In der App als auch mit dem Browser kann ich mich anmelden.
                          In der GetToken Windows App kann ich mich auch nicht anmelden.

                          
                          mihome-vacuum.0
                          2025-06-29 14:00:51.431	debug	Startup: setGetConsumable Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:51.431	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:51.276	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:51.275	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612af1ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:49.430	debug	Message= {"id":20,"method":"get_consumable"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:49.430	debug	Startup: setGetCleanSummary Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:49.430	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:47.429	debug	Message= {"id":19,"method":"get_clean_summary"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:47.428	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:45.428	debug	Message= {"id":18,"method":"get_sound_volume"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:45.427	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:43.426	debug	Message= {"id":17,"method":"get_network_info"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:43.425	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:41.425	debug	Message= {"id":16,"method":"get_status"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:41.424	debug	get params for stock Vacuum
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:41.273	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:41.272	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612ae7ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:31.270	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:31.270	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612addffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:21.424	debug	Startup: setGetConsumable Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:21.424	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:21.265	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:21.265	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612ad3ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:19.423	debug	Message= {"id":15,"method":"get_consumable"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:19.423	debug	Startup: setGetCleanSummary Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:19.422	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:17.421	debug	Message= {"id":14,"method":"get_clean_summary"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:17.421	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:15.420	debug	Message= {"id":13,"method":"get_sound_volume"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:15.420	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:13.420	debug	Message= {"id":12,"method":"get_network_info"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:13.419	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:11.418	debug	Message= {"id":11,"method":"get_status"}
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:11.418	debug	get params for stock Vacuum
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:11.261	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:11.261	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612ac9ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:01.259	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 14:00:01.257	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612abfffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:51.417	debug	Startup: setGetConsumable Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:51.417	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:51.191	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:51.191	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612ab5ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:49.416	debug	Message= {"id":10,"method":"get_consumable"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:49.416	debug	Startup: setGetCleanSummary Answer: false
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:49.415	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:47.414	debug	Message= {"id":9,"method":"get_clean_summary"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:47.413	debug	Startup: Delete getMultiMapsList
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:47.413	debug	Startup: getMultiMapsList Answer: true
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:47.413	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:45.413	debug	Message= {"id":8,"method":"get_multi_maps_list"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:45.412	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:43.412	debug	Message= {"id":7,"method":"get_sound_volume"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:43.411	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:41.410	debug	Message= {"id":6,"method":"get_network_info"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:41.410	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:41.187	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:41.187	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612aabffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.770	info	settest next timer: not available
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.408	debug	Message= {"id":5,"method":"get_status"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.408	debug	get params for stock Vacuum
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State done!
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State for map: loadMap
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State for map: mapURL
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State for map: mapStatus
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State for map: actualMap
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.407	debug	Create State for map: map64
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.364	debug	Create State for map:
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.319	debug	Create State for Queue: queue
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.230	debug	Create State for control: {"id":"mihome-vacuum.0.control"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.200	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.191	info	select standard vacuum protocol....
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.190	debug	DeviceModel set to: rockrobo.vacuum.v1
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.190	warn	No Answer for DeviceModel use model from Config
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.190	error	YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.190	debug	Get Device data..4
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.190	debug	GETMODELFROMAPI:Data: {}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:39.189	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:37.189	debug	Message= {"id":4,"method":"miIO.info"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:37.189	debug	Get Device data..3
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:37.188	debug	GETMODELFROMAPI:Data: {}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:37.188	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:35.187	debug	Message= {"id":3,"method":"miIO.info"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:35.187	debug	Get Device data..2
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:35.187	debug	GETMODELFROMAPI:Data: {}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:35.187	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:33.186	debug	Message= {"id":2,"method":"miIO.info"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:33.186	debug	Get Device data..1
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:33.186	debug	GETMODELFROMAPI:Data: {}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:33.185	debug	your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.184	debug	Message= {"id":1,"method":"miIO.info"}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.183	debug	Get Device data..0
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.183	debug	GETMODELFROMAPI:Data: {}
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.183	debug	Time difference between Mihome Vacuum and ioBroker: -2 sec
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.183	debug	your device is not connected, but this could be temporary
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.182	debug	MAIN: Connected to device, try to get model..
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.181	debug	Receive <<< Helo <<< 213100200000000004eb3cb668612aa1ffffffffffffffffffffffffffffffff
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.178	debug	server started on 0.0.0.0:53421
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.176	info	IOT disabled, delete state
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.174	debug	MIIO: Config: ip:192.168.178.44 token: 766e4a7754XXXXXXXXX
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.173	debug	Create State for deviceInfounsupported
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.173	debug	Create State for deviceInfowifi_signal
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.173	debug	Create State for deviceInfofw_ver
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.173	debug	Create State for deviceInfomodel
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.172	debug	Create State for deviceInfomac
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.172	debug	Create State for deviceInfo
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.158	error	SyntaxError: "undefined" is not valid JSON
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:31.148	info	starting. Version 5.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v20.19.1, js-controller: 7.0.3
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.984	debug	Plugin sentry Initialize Plugin (enabled=true)
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.939	debug	States connected to redis: 127.0.0.1:9000
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.853	debug	States create User PubSub Client
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.853	debug	States create System PubSub Client
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.819	debug	Redis States: Use Redis connection: 127.0.0.1:9000
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.774	debug	Objects connected to redis: 127.0.0.1:9001
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.771	debug	Objects client initialize lua scripts
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.699	debug	Objects create User PubSub Client
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.699	debug	Objects create System PubSub Client
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.698	debug	Objects client ready ... initialize now
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:30.658	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:26.364	info	terminating
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:25.865	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:25.864	info	terminating
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:25.864	error	Socket Close
                          
                          mihome-vacuum.0
                          2025-06-29 13:59:25.863	info	Got terminate signal TERMINATE_YOURSELF
                          

                          Hat jemand das selbe Problem ?

                          Danke

                          Heiko

                          Edit:
                          Sorry double post. Btw. wie kann ich diesen löschen ?

                          Danke

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          933
                          Online

                          31.9k
                          Users

                          80.2k
                          Topics

                          1.3m
                          Posts

                          42
                          196
                          22555
                          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