Navigation

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

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Mihome-vacuum.0-Fehler

    This topic has been deleted. Only users with topic management privileges can see it.
    • MathiasJ
      MathiasJ @sigi234 last edited by MathiasJ

      @sigi234
      Adapter 5.2.0 und ja, die Fehlermeldung kommt wieder.
      Wobei ich nicht weiß, welches Objekt fehlt. Ich habe den kpl Sauger gelöscht.

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

        Mach da mal auf github ein isdue auf, bitte. Wenn es geht, auch noch ein bisschen log rundherum, also wann das auftritt. Ich schaue es mir dann die tage an.

        MathiasJ 2 Replies Last reply Reply Quote 0
        • MathiasJ
          MathiasJ @dirkhe last edited by MathiasJ

          @dirkhe
          Vielen Dank dafür. Es tritt auf, sobald der Sauger zu reinigen beginnt. Ich habe den Reiter Protokolle beim Start des Saugers mit der App im Hintergrund laufen lassen.
          Nun das ganze Protokoll löschen und nach dem nächsten Start des Saugers herunterladen.
          Das passiert aber erst morgen.....
          Ich habe den Objektbaum control mehrmals gelöscht.
          Das Objekt cleanhome wird jedoch nicht angelegt.

          Hier die log-Datei:

          
2025-05-05 02:05:17.087 - Info : host.iobroker Protokolldatei iobroker.2025-04-27.log.gz löschen
05.05.2025 06:58:07.290 - Info : admin.0 (642) Aktuelles Repository anfordern ...
05.05.2025 06:58:07.727 – Info : host.iobroker. Aktualisierung des Repository „stable“ unter „http://download.iobroker.net/sources-dist.json“.
05.05.2025 06:58:12.253 – Info : admin.0 (642) Repository erfolgreich empfangen.
2025-05-05 19:02:31.516 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:03:12.167 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:04:53.671 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:05:25.930 - info : admin.0 (642) Adapterbewertung aktualisiert
2025-05-05 19:27:35.340 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:29:16.730 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:32:59.913 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:33:20.995 - Warnung : mihome-vacuum.0 (2118) Der Status „mihome-vacuum.0.control.clean_home“ hat kein vorhandenes Objekt, dies könnte in zukünftigen Versionen zu einem Fehler führen
2025-05-05 19:53:30.021 - Info : admin.0 (642) ==> Verbunden mit system.user.admin von ::ffff:192.168.178.21
          1 Reply Last reply Reply Quote 0
          • MathiasJ
            MathiasJ @dirkhe last edited by

            @dirkhe
            Doch keine Idee, woran es liegt?
            Das Objekt cleanhome gibt es tatsächlich nicht, es wird auch nicht angelegt.
            Gruß,
            Mathias

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

              @mathiasj clean_home wird nur angelegt, wenn alexa angehakt ist. Was mich wundert, warum dann eine fehlermeldung kommt. Stell mal auf debug bitte

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

                @dirkhe sagte in Mihome-vacuum.0-Fehler:

                alexa angehakt

                Ich habe den DP auch.
                72d5daec-4dc4-4e49-81aa-d902540c828d-image.png

                Für Alexa finde ich in der Instanz keinen Anhakpunkt.
                Und diesen DP nehme ich um den Robo nach Hause zu schicken.
                Funktioniert eigentlich seit Anfang an.

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

                  @bahnuhr ich habe gerade mal geschaut, das ist in der config ausgeblendet, warum kann ich gerade nicht sehen, muss ich mal tiefer rein...
                  Ich vermute, dass es irgendwo ein script gibt, der das command sendet. der adapter versucht dann den ack zu setzten, daher brauche ich mal das debug log von @MathiasJ .
                  aber wie gesagt, das andere muß ich mir dann ml in ruge zur gemüte führen

                  MathiasJ haselchen 2 Replies Last reply Reply Quote 0
                  • MathiasJ
                    MathiasJ @dirkhe last edited by

                    @dirkhe
                    Anbei das Protokoll im debug:

                    0
3
Log-Größe: 93.5 KB

1
Zeit
debug
Nachricht

mihome-vacuum.0
2025-05-08 21:52:33.659	debug	Time difference between Mihome Vacuum and ioBroker: -1746666287 sec

mihome-vacuum.0
2025-05-08 21:52:33.658	debug	Receive <<< Helo <<< 2131002000000000261cfcc100010852ffffffffffffffffffffffffffffffff

mihome-vacuum.0
2025-05-08 21:52:32.975	debug	creating map

mihome-vacuum.0
2025-05-08 21:52:32.917	debug	update_Map use old mapurl

mihome-vacuum.0
2025-05-08 21:52:32.917	debug	update_Map Mimap enabled

mihome-vacuum.0
2025-05-08 21:52:32.917	debug	Mappointer_updated

mihome-vacuum.0
2025-05-08 21:52:32.917	debug	MIIO RECIVE: {"id":142,"result":["roboroommap%2F639433921%2F3"],"exe_time":10}

mihome-vacuum.0
2025-05-08 21:52:32.916	debug	MIIO MESSAGE TESTING: {"id":142,"result":["roboroommap%2F639433921%2F3"],"exe_time":10}

mihome-vacuum.0
2025-05-08 21:52:32.891	debug	Message= {"id":142,"method":"get_map_v1"}

mihome-vacuum.0
2025-05-08 21:52:32.890	debug	Get Mappointer while cleaning

mihome-vacuum.0
2025-05-08 21:52:31.251	debug	MIIO RECIVE: {"id":141,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.250	debug	MIIO MESSAGE TESTING: {"id":141,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.231	debug	Message= {"id":141,"method":"get_carpet_mode"}

mihome-vacuum.0
2025-05-08 21:52:31.229	debug	MIIO RECIVE: {"id":140,"result":[90],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.228	debug	MIIO MESSAGE TESTING: {"id":140,"result":[90],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.210	debug	Message= {"id":140,"method":"get_sound_volume"}

mihome-vacuum.0
2025-05-08 21:52:31.207	warn	State "mihome-vacuum.0.control.clean_home" has no existing object, this might lead to an error in future versions

mihome-vacuum.0
2025-05-08 21:52:31.158	debug	MIIO RECIVE: {"id":139,"result":{"clean_time":142566,"clean_area":2096720000,"clean_count":201,"dust_collection_count":168,"records":[1746724471,1746602666,1746533804,1746476586,1746464534,1746362156,1746339445,1746292509,1746276079,1746255128,1746204423,1746113857,1746080285,1746033491,1745851904,1745649148,1745595207,1745565403,1745561888,1745305281]},"exe_time":21}

mihome-vacuum.0
2025-05-08 21:52:31.158	debug	MIIO MESSAGE TESTING: {"id":139,"result":{"clean_time":142566,"clean_area":2096720000,"clean_count":201,"dust_collection_count":168,"records":[1746724471,1746602666,1746533804,1746476586,1746464534,1746362156,1746339445,1746292509,1746276079,1746255128,1746204423,1746113857,1746080285,1746033491,1745851904,1745649148,1745595207,1745565403,1745561888,1745305281]},"exe_time":21}

mihome-vacuum.0
2025-05-08 21:52:31.157	debug	MIIO MESSAGE TESTING: {"id":138,"result":{"ssid":"Mathias-Zaspel","ip":"192.168.178.38","mac":"b0:4a:39:65:79:6e","bssid":"dc:15:c8:b3:b9:2b","rssi":-42},"exe_time":31}

mihome-vacuum.0
2025-05-08 21:52:31.157	debug	MIIO RECIVE: {"id":138,"result":{"ssid":"Mathias-Zaspel","ip":"192.168.178.38","mac":"b0:4a:39:65:79:6e","bssid":"dc:15:c8:b3:b9:2b","rssi":-42},"exe_time":31}

mihome-vacuum.0
2025-05-08 21:52:31.156	debug	MIIO MESSAGE TESTING: {"id":138,"result":{"ssid":"Mathias-Zaspel","ip":"192.168.178.38","mac":"b0:4a:39:65:79:6e","bssid":"dc:15:c8:b3:b9:2b","rssi":-42},"exe_time":31}

mihome-vacuum.0
2025-05-08 21:52:31.127	debug	Message= {"id":139,"method":"get_clean_summary"}

mihome-vacuum.0
2025-05-08 21:52:31.126	debug	MIIO MESSAGE TESTING: {"id":137,"result":[{"main_brush_work_time":142566,"side_brush_work_time":142566,"filter_work_time":142566,"filter_element_work_time":0,"sensor_dirty_time":7338,"strainer_work_times":11,"dust_collection_work_times":168,"cleaning_brush_work_times":176}],"exe_time":10}

mihome-vacuum.0
2025-05-08 21:52:31.125	debug	MIIO RECIVE: {"id":137,"result":[{"main_brush_work_time":142566,"side_brush_work_time":142566,"filter_work_time":142566,"filter_element_work_time":0,"sensor_dirty_time":7338,"strainer_work_times":11,"dust_collection_work_times":168,"cleaning_brush_work_times":176}],"exe_time":10}

mihome-vacuum.0
2025-05-08 21:52:31.124	debug	MIIO MESSAGE TESTING: {"id":137,"result":[{"main_brush_work_time":142566,"side_brush_work_time":142566,"filter_work_time":142566,"filter_element_work_time":0,"sensor_dirty_time":7338,"strainer_work_times":11,"dust_collection_work_times":168,"cleaning_brush_work_times":176}],"exe_time":10}

mihome-vacuum.0
2025-05-08 21:52:31.106	debug	Message= {"id":138,"method":"get_network_info"}

mihome-vacuum.0
2025-05-08 21:52:31.106	debug	Message= {"id":137,"method":"get_consumable"}

mihome-vacuum.0
2025-05-08 21:52:31.105	debug	setGetStatus {"msg_ver":2,"msg_seq":3402,"state":8,"battery":100,"clean_time":409,"clean_area":3790000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"back_type":-1,"wash_phase":0,"wash_ready":0,"fan_power":103,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":202,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":3,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"switch_map_mode":0,"dock_error_status":0,"charge_status":1,"unsave_map_reason":0,"unsave_map_flag":0,"error_text":"No error"}

mihome-vacuum.0
2025-05-08 21:52:31.104	debug	MIIO RECIVE: {"id":136,"result":[{"msg_ver":2,"msg_seq":3402,"state":8,"battery":100,"clean_time":409,"clean_area":3790000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"back_type":-1,"wash_phase":0,"wash_ready":0,"fan_power":103,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":202,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":3,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"switch_map_mode":0,"dock_error_status":0,"charge_status":1,"unsave_map_reason":0,"unsave_map_flag":0}],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.103	debug	MIIO MESSAGE TESTING: {"id":136,"result":[{"msg_ver":2,"msg_seq":3402,"state":8,"battery":100,"clean_time":409,"clean_area":3790000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"back_type":-1,"wash_phase":0,"wash_ready":0,"fan_power":103,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":202,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":3,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"switch_map_mode":0,"dock_error_status":0,"charge_status":1,"unsave_map_reason":0,"unsave_map_flag":0}],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:31.080	debug	Message= {"id":136,"method":"get_status"}

mihome-vacuum.0
2025-05-08 21:52:31.079	debug	get params for stock Vacuum

mihome-vacuum.0
2025-05-08 21:52:30.616	debug	creating map

mihome-vacuum.0
2025-05-08 21:52:30.555	debug	update_Map use old mapurl

mihome-vacuum.0
2025-05-08 21:52:30.555	debug	update_Map Mimap enabled

mihome-vacuum.0
2025-05-08 21:52:30.555	debug	Mappointer_updated

mihome-vacuum.0
2025-05-08 21:52:30.555	debug	MIIO RECIVE: {"id":135,"result":["roboroommap%2F639433921%2F2"],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:30.554	debug	MIIO MESSAGE TESTING: {"id":135,"result":["roboroommap%2F639433921%2F2"],"exe_time":11}

mihome-vacuum.0
2025-05-08 21:52:30.511	debug
                    1 Reply Last reply Reply Quote 0
                    • haselchen
                      haselchen Most Active @dirkhe last edited by

                      @dirkhe

                      Ich würde die Einstellungen im Adapter viel spannender finden....

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

                        @haselchen
                        Habe alle Einstellungen durch, die Fehlermeldung bleibt

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

                          @mathiasj wie gesagt, warum die Einstellung nicht mehr angezeigt wird, muss ich mir noch anschauen.
                          Wenn du die config gelöscht hast hast und den dp auch nicht hast, kann es nur von außen getriggert werden, vermute ich.
                          In dem debug sehe ich aber nicht die Fehlermeldung. Also im Prinzip brauchen wir das debug log, kurz bevor der Fehler Auftritt

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

                          Support us

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

                          945
                          Online

                          31.7k
                          Users

                          79.7k
                          Topics

                          1.3m
                          Posts

                          mihome error roborock s7
                          5
                          13
                          350
                          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