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

    • 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-vacuum v2.0.x

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

      Hier nochmal mein aktuelles Log nach Start des Adapters.
      Leider wird keine Karte geladen.
      Genutzt wird Valetudo, wo auch eine Karte angelegt und Räume definiert sind.

      mihome-vacuum.0
      2020-03-09 11:00:07.838
      debug
      (19711) Receive <<< {"result":[402310,6205780000,274,[1583660641,1583575121,1583574577,1583574233,1583574180,1583573893,1583573844,1583573697,1583573614,1583258556,1583248554,1583244883,1583060389,158
      mihome-vacuum.0
      2020-03-09 11:00:07.828
      debug
      (19711) sendMsg[1] >>> {"id":40,"method":"get_clean_summary"}
      mihome-vacuum.0
      2020-03-09 11:00:07.337
      debug
      (19711) Receive <<< {"result":[{"main_brush_work_time":402541,"side_brush_work_time":402541,"filter_work_time":187091,"sensor_dirty_time":17530}],"id":39}
      mihome-vacuum.0
      2020-03-09 11:00:07.327
      debug
      (19711) sendMsg[1] >>> {"id":39,"method":"get_consumable"}
      mihome-vacuum.0
      2020-03-09 11:00:07.326
      debug
      (19711) Receive <<< {"result":[{"msg_ver":8,"msg_seq":1292,"state":8,"battery":100,"clean_time":217,"clean_area":3947500,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0}
      mihome-vacuum.0
      2020-03-09 11:00:07.319
      debug
      (19711) sendMsg[1] >>> {"id":38,"method":"get_status"}
      mihome-vacuum.0
      2020-03-09 10:59:53.748
      warn
      (19711) Could not receive Mappointer, giving up
      mihome-vacuum.0
      2020-03-09 10:59:53.747
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":37}
      mihome-vacuum.0
      2020-03-09 10:59:53.729
      debug
      (19711) 9. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:53.729
      debug
      (19711) sendMsg[1] >>> {"id":37,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:53.228
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":36}
      mihome-vacuum.0
      2020-03-09 10:59:53.222
      debug
      (19711) 8. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:53.221
      debug
      (19711) sendMsg[1] >>> {"id":36,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:52.721
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":35}
      mihome-vacuum.0
      2020-03-09 10:59:52.716
      debug
      (19711) 7. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:52.715
      debug
      (19711) sendMsg[1] >>> {"id":35,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:52.215
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":34}
      mihome-vacuum.0
      2020-03-09 10:59:52.201
      debug
      (19711) 6. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:52.201
      debug
      (19711) sendMsg[1] >>> {"id":34,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:52.081
      debug
      (19711) CLEAN_LOGGING[{"Datum":"8.3","Start":"10:44","Saugzeit":"4 min","Fläche":"3.95 m²","Error":0,"Ende":true},{"Datum":"7.3","Start":"10:58","Saugzeit":"71 min","Fläche":"54.66 m²","Error":0,"Ende
      mihome-vacuum.0
      2020-03-09 10:59:51.885
      debug
      (19711) Receive <<< {"result":[[1577275556,1577275612,14,0,0,0]],"id":33}
      mihome-vacuum.0
      2020-03-09 10:59:51.880
      debug
      (19711) sendMsg[1] >>> {"id":33,"method":"get_clean_record","params":[1577275556]}
      mihome-vacuum.0
      2020-03-09 10:59:51.693
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":32}
      mihome-vacuum.0
      2020-03-09 10:59:51.688
      debug
      (19711) 5. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:51.687
      debug
      (19711) sendMsg[1] >>> {"id":32,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:51.685
      debug
      (19711) Receive <<< {"result":[[1577705584,1577707390,1705,27040000,0,1]],"id":31}
      mihome-vacuum.0
      2020-03-09 10:59:51.679
      debug
      (19711) sendMsg[1] >>> {"id":31,"method":"get_clean_record","params":[1577705584]}
      mihome-vacuum.0
      2020-03-09 10:59:51.486
      debug
      (19711) Receive <<< {"result":[[1577707998,1577708227,229,4305000,0,1]],"id":30}
      mihome-vacuum.0
      2020-03-09 10:59:51.479
      debug
      (19711) sendMsg[1] >>> {"id":30,"method":"get_clean_record","params":[1577707998]}
      mihome-vacuum.0
      2020-03-09 10:59:51.285
      debug
      (19711) Receive <<< {"result":[[1577708513,1577708756,243,3115000,0,1]],"id":29}
      mihome-vacuum.0
      2020-03-09 10:59:51.277
      debug
      (19711) sendMsg[1] >>> {"id":29,"method":"get_clean_record","params":[1577708513]}
      mihome-vacuum.0
      2020-03-09 10:59:51.186
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":28}
      mihome-vacuum.0
      2020-03-09 10:59:51.182
      debug
      (19711) 4. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:51.182
      debug
      (19711) sendMsg[1] >>> {"id":28,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:51.081
      debug
      (19711) Receive <<< {"result":[[1581150811,1581153929,3118,44420000,0,1]],"id":27}
      mihome-vacuum.0
      2020-03-09 10:59:51.076
      debug
      (19711) sendMsg[1] >>> {"id":27,"method":"get_clean_record","params":[1581150811]}
      mihome-vacuum.0
      2020-03-09 10:59:50.882
      debug
      (19711) Receive <<< {"result":[[1582118288,1582120675,2387,39517500,0,1]],"id":26}
      mihome-vacuum.0
      2020-03-09 10:59:50.875
      debug
      (19711) sendMsg[1] >>> {"id":26,"method":"get_clean_record","params":[1582118288]}
      mihome-vacuum.0
      2020-03-09 10:59:50.682
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":25}
      mihome-vacuum.0
      2020-03-09 10:59:50.681
      debug
      (19711) Receive <<< {"result":[[1583060389,1583063854,3465,54702500,0,1]],"id":24}
      mihome-vacuum.0
      2020-03-09 10:59:50.676
      debug
      (19711) 3. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:50.676
      debug
      (19711) sendMsg[1] >>> {"id":25,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:50.673
      debug
      (19711) sendMsg[1] >>> {"id":24,"method":"get_clean_record","params":[1583060389]}
      mihome-vacuum.0
      2020-03-09 10:59:50.477
      debug
      (19711) Receive <<< {"result":[[1583244883,1583245887,1004,17005000,0,1]],"id":23}
      mihome-vacuum.0
      2020-03-09 10:59:50.472
      debug
      (19711) sendMsg[1] >>> {"id":23,"method":"get_clean_record","params":[1583244883]}
      mihome-vacuum.0
      2020-03-09 10:59:50.278
      debug
      (19711) Receive <<< {"result":[[1583248554,1583249170,616,8267500,0,1]],"id":22}
      mihome-vacuum.0
      2020-03-09 10:59:50.272
      debug
      (19711) sendMsg[1] >>> {"id":22,"method":"get_clean_record","params":[1583248554]}
      mihome-vacuum.0
      2020-03-09 10:59:50.176
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":21}
      mihome-vacuum.0
      2020-03-09 10:59:50.171
      debug
      (19711) 2. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:50.171
      debug
      (19711) sendMsg[1] >>> {"id":21,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:50.077
      debug
      (19711) Receive <<< {"result":[[1583258556,1583258934,224,7165000,0,0]],"id":20}
      mihome-vacuum.0
      2020-03-09 10:59:50.072
      debug
      (19711) sendMsg[1] >>> {"id":20,"method":"get_clean_record","params":[1583258556]}
      mihome-vacuum.0
      2020-03-09 10:59:49.878
      debug
      (19711) Receive <<< {"result":[[1583573614,1583573627,13,0,0,1]],"id":19}
      mihome-vacuum.0
      2020-03-09 10:59:49.872
      debug
      (19711) sendMsg[1] >>> {"id":19,"method":"get_clean_record","params":[1583573614]}
      mihome-vacuum.0
      2020-03-09 10:59:49.670
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":18}
      mihome-vacuum.0
      2020-03-09 10:59:49.667
      debug
      (19711) Receive <<< {"result":[[1583573697,1583573710,13,0,0,1]],"id":17}
      mihome-vacuum.0
      2020-03-09 10:59:49.665
      debug
      (19711) 1. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:49.665
      debug
      (19711) sendMsg[1] >>> {"id":18,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:49.662
      debug
      (19711) sendMsg[1] >>> {"id":17,"method":"get_clean_record","params":[1583573697]}
      mihome-vacuum.0
      2020-03-09 10:59:49.466
      debug
      (19711) Receive <<< {"result":[[1583573844,1583573857,13,0,0,1]],"id":16}
      mihome-vacuum.0
      2020-03-09 10:59:49.461
      debug
      (19711) sendMsg[1] >>> {"id":16,"method":"get_clean_record","params":[1583573844]}
      mihome-vacuum.0
      2020-03-09 10:59:49.266
      debug
      (19711) Receive <<< {"result":[[1583573893,1583573905,12,0,0,1]],"id":15}
      mihome-vacuum.0
      2020-03-09 10:59:49.260
      debug
      (19711) sendMsg[1] >>> {"id":15,"method":"get_clean_record","params":[1583573893]}
      mihome-vacuum.0
      2020-03-09 10:59:49.165
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":14}
      mihome-vacuum.0
      2020-03-09 10:59:49.160
      debug
      (19711) 0. Mappointer_nomap___map_upload_handler
      mihome-vacuum.0
      2020-03-09 10:59:49.160
      debug
      (19711) sendMsg[1] >>> {"id":14,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:49.066
      debug
      (19711) Receive <<< {"result":[[1583574180,1583574193,13,0,0,1]],"id":13}
      mihome-vacuum.0
      2020-03-09 10:59:49.060
      debug
      (19711) sendMsg[1] >>> {"id":13,"method":"get_clean_record","params":[1583574180]}
      mihome-vacuum.0
      2020-03-09 10:59:48.865
      debug
      (19711) Receive <<< {"result":[[1583574233,1583574244,11,0,0,1]],"id":12}
      mihome-vacuum.0
      2020-03-09 10:59:48.858
      debug
      (19711) sendMsg[1] >>> {"id":12,"method":"get_clean_record","params":[1583574233]}
      mihome-vacuum.0
      2020-03-09 10:59:48.680
      debug
      (19711) Receive <<< {"result":[[1583574577,1583574590,13,0,0,1]],"id":11}
      mihome-vacuum.0
      2020-03-09 10:59:48.658
      debug
      (19711) Receive <<< {"result":["map_upload_handler"],"id":10}
      mihome-vacuum.0
      2020-03-09 10:59:48.657
      debug
      (19711) sendMsg[1] >>> {"id":11,"method":"get_clean_record","params":[1583574577]}
      mihome-vacuum.0
      2020-03-09 10:59:48.645
      debug
      (19711) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
      mihome-vacuum.0
      2020-03-09 10:59:48.465
      debug
      (19711) Receive <<< {"result":[[1583575121,1583579377,4234,54657500,0,1]],"id":9}
      mihome-vacuum.0
      2020-03-09 10:59:48.457
      debug
      (19711) Receive <<< {"result":"unknown_method","id":8}
      mihome-vacuum.0
      2020-03-09 10:59:48.456
      debug
      (19711) sendMsg[1] >>> {"id":9,"method":"get_clean_record","params":[1583575121]}
      mihome-vacuum.0
      2020-03-09 10:59:48.452
      info
      (19711) create state for carpet_mode
      mihome-vacuum.0
      2020-03-09 10:59:48.452
      debug
      (19711) Receive <<< {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":7}
      mihome-vacuum.0
      2020-03-09 10:59:48.446
      debug
      (19711) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
      mihome-vacuum.0
      2020-03-09 10:59:48.445
      debug
      (19711) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
      mihome-vacuum.0
      2020-03-09 10:59:48.266
      debug
      (19711) Receive <<< {"result":[[1583660641,1583660858,217,3947500,0,1]],"id":6}
      mihome-vacuum.0
      2020-03-09 10:59:48.255
      debug
      (19711) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1583660641]}
      mihome-vacuum.0
      2020-03-09 10:59:48.254
      debug
      (19711) Receive <<< {"result":[402310,6205780000,274,[1583660641,1583575121,1583574577,1583574233,1583574180,1583573893,1583573844,1583573697,1583573614,1583258556,1583248554,1583244883,1583060389,158
      mihome-vacuum.0
      2020-03-09 10:59:48.246
      debug
      (19711) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
      mihome-vacuum.0
      2020-03-09 10:59:48.050
      debug
      (19711) Receive <<< {"result":[{"main_brush_work_time":402541,"side_brush_work_time":402541,"filter_work_time":187091,"sensor_dirty_time":17530}],"id":4}
      mihome-vacuum.0
      2020-03-09 10:59:48.045
      debug
      (19711) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
      mihome-vacuum.0
      2020-03-09 10:59:47.902
      debug
      (19711) system.adapter.admin.0: logging true
      mihome-vacuum.0
      2020-03-09 10:59:47.444
      info
      (19711) Connected
      mihome-vacuum.0
      2020-03-09 10:59:47.442
      debug
      (19711) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0
      2020-03-09 10:59:47.441
      debug
      (19711) Receive <<< {"result":[{"msg_ver":8,"msg_seq":1291,"state":8,"battery":100,"clean_time":217,"clean_area":3947500,"error_code":0,"map_present":1,"in_cleaning":0,"fan_power":100,"dnd_enabled":0
      mihome-vacuum.0
      2020-03-09 10:59:47.420
      debug
      (19711) sendMsg[1] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0
      2020-03-09 10:59:47.357
      debug
      (19711) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0
      2020-03-09 10:59:47.357
      info
      (19711) connecting, This can take up to 5 minutes ...
      mihome-vacuum.0
      2020-03-09 10:59:47.357
      warn
      (19711) Time difference between Mihome Vacuum and ioBroker: -96 sec
      mihome-vacuum.0
      2020-03-09 10:59:47.356
      debug
      (19711) Receive <<< Helo <<< 24e1002000000000098df8he5e111237ffffffffffffffffffffffffffffffff
      mihome-vacuum.0
      2020-03-09 10:59:47.341
      info
      (19711) New generation or new fw(3.3.9,003468) detected, create new states goto and zoneclean
      mihome-vacuum.0
      2020-03-09 10:59:47.322
      debug
      (19711) server started on 0.0.0.0:53421
      mihome-vacuum.0
      2020-03-09 10:59:47.318
      info
      (19711) Disconnect
      mihome-vacuum.0
      2020-03-09 10:59:47.314
      info
      (19711) Create state clean_home for controlling by cloud adapter
      mihome-vacuum.0
      2020-03-09 10:59:47.314
      info
      (19711) Expert mode enabled, states created
      mihome-vacuum.0
      2020-03-09 10:59:47.307
      debug
      (19711) load Map creator... true
      mihome-vacuum.0
      2020-03-09 10:59:47.101
      info
      (19711) starting. Version 2.0.9 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0
      mihome-vacuum.0
      2020-03-09 10:59:45.964
      debug
      (19711) statesDB connected
      mihome-vacuum.0
      2020-03-09 10:59:45.963
      debug
      (19711) States connected to redis: 0.0.0.0:9000
      mihome-vacuum.0
      2020-03-09 10:59:45.940
      debug
      (19711) States create System PubSub Client
      mihome-vacuum.0
      2020-03-09 10:59:45.934
      debug
      (19711) States create User PubSub Client
      mihome-vacuum.0
      2020-03-09 10:59:45.922
      debug
      (19711) Redis States: Use Redis connection: 0.0.0.0:9000
      mihome-vacuum.0
      2020-03-09 10:59:45.920
      debug
      (19711) objectDB connected
      mihome-vacuum.0
      2020-03-09 10:59:45.917
      debug
      (19711) Objects connected to redis: 0.0.0.0:9001
      mihome-vacuum.0
      2020-03-09 10:59:45.889
      debug
      (19711) Objects client initialize lua scripts
      mihome-vacuum.0
      2020-03-09 10:59:45.889
      debug
      (19711) Objects create User PubSub Client
      mihome-vacuum.0
      2020-03-09 10:59:45.888
      debug
      (19711) Objects create System PubSub Client
      mihome-vacuum.0
      2020-03-09 10:59:45.886
      debug
      (19711) Objects client ready ... initialize now
      mihome-vacuum.0
      2020-03-09 10:59:45.023
      debug
      (19711) Redis Objects: Use Redis connection: 0.0.0.0:9001
      mihome-vacuum.0
      2020-03-09 10:59:30.753
      info
      (27290) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      mihome-vacuum.0
      2020-03-09 10:59:30.753
      info
      (27290) terminating
      mihome-vacuum.0
      2020-03-09 10:59:30.753
      info
      (27290) Got terminate signal TERMINATE_YOURSELF
      
      
      1 Reply Last reply Reply Quote 0
      • Diginix
        Diginix @Patchwork 3001 last edited by Diginix

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

        ist das java oder blockly , Typeskript

        Nichts der drei genannten. Es ist Javascript.

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

          Hallo Zusammen,

          ich habe gestern versucht meinen S50 via Cloud im Adapter einzutragen. Zunächst war mein MI-Account nur via Handy-Nummer registriert und ich konnte somit den Adapter nicht nutzen. Dann habe ich in meinem Mi-Account noch eine Recovery-Email eingetragen. Nun ist es möglich sich mit dieser Email-Adresse und dem PW in den MI-Account einzuloggen. Wenn ich diese Kombination aber im Adapter eingebe passiert nichts. Wenn ich ein falsches PW dazu eingebe dann meckert er aber so dreht sich kurz der Kreis aber bei Geräte kommt nichts zum auswählen... was mache ich hier falsch? Liegt es am MI-Account der ursprünglich nur über Handy-Nummer registriert war ? Bei Manueller Eingabe steht noch der Token und IP das S50 aber darüber kann der Adapter aktuell nicht verbinden und bleibt Gelb. Muss bei Manuell alles raus wenn ich über Cloud verbinden will ?

          ? K 2 Replies Last reply Reply Quote 0
          • ?
            A Former User @backons last edited by

            @backons richtigen Server gewählt?

            1 Reply Last reply Reply Quote 0
            • K
              K_o_bold @backons last edited by

              @backons ,
              Es geht auch mit Handynummer.
              Einfach so eintragen
              +49.....

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

                @dirkhe Tatsache.... Manuell hinzufügen und danach einen Raum zuordnen ging nicht. Das ging bei allen anderen Objekten schon... Egal, das automatische hinzufügen nach Vergabe eines Raum & einer Funktion hat super geklappt. Danke!

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

                  @dirkhe Wenn man pro Raum unterschiedliche Saugstärken einstellt und diese Räume erst durch die Warteliste abgearbeitet werden, dann wirft er die Saugstärken durcheinander.

                  • bei mir ist default Saugstärke Turbo
                  • Raum 1 wird direkt gestartet und hat als roomFanPower aber "Max"
                  • Sauger fährt los und geht auf Max
                  • Ich trigger Raum 2 mit Turbo und dieser landet im queue
                  • Sauger stellt sich sofort auf Turbo zurück und saugt Raum 1 mit falscher Stärke
                  • Ich stelle manuell im Adapter "fan_power" wieder auf Max passend zu Raum 1
                  • Sauger saugt Raum 1 mit Max zu Ende und stellt bei Start von Raum 2 nicht auf Turbo wie es für Raum 2 definiert ist

                  Die roomFanPower dürften bei den Räumen auch erst an fan_power übergeben werden wenn der Raum tatsächlich begonnen wird.

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

                    @Diginix schau ich mir an, habe ich da wohl übersehen.

                    1 Reply Last reply Reply Quote 0
                    • J
                      Jaschkopf last edited by

                      Servus. Hab auch gerade geupdated. Kann mir jemand sagen warum ich im ioBroker die Version 2.0.7 angezeigt bekomme obwohl laut Github 2.0.9 die neuste ist? Wie komme ich auf die neuste Version?

                      Hab eine Frage zum MultiRoomClean. Wo und in welchem Format muss ich die Raumindexe eintragen damit ich mehrere Räume gleichzeitig reinigen kann?

                      Gruß Jaschkopf

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

                        Wichtig ist die Version, die im Log steht, wenn der Adapter startet. Wo grnau die version aus ioBroker herkommt, weiss ich auch nicht. Aber entweder nimmt man den aus ioBroker oder von github. Dann sollte man eh immer den aktuellen Thread mitlesen.
                        Für multiroom wählst du die ioBroker Räume aus. Die müssen natürlich auch an den einzelnen Channels verknüpft sein. Du kannst aber auch einen Timer anlegen, den du ioBroker Räume oder Channels zuweist. Der kann dann auch inaktiv gestellt werden und immer manuell ausgewählt werden.

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          Jaschkopf @dirkhe last edited by

                          @dirkhe wie verknüpfe ich die Räume mit dem channels? Und wie wähle ich die dann aus? Ich dachte eigentlich es gibt einen Kanal wo ich die Index eintragen (z.b. 1,2,3) und dann über den Button MultiRoomClean starten kann. Aber das klappt nicht 😅

                          Gruß Jaschkopf

                          Diginix 1 Reply Last reply Reply Quote 0
                          • Diginix
                            Diginix @Jaschkopf last edited by

                            @Jaschkopf Wäre schon fair sich die Mühe zu machen den Thread bzw die zum Adapter gehörenden wenigstens zu lesen.
                            Das ist alles inkl Screenshots mehr als einmal erklärt.

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

                              Du gehst über die Objektansicht und wählst dann den Raum aus

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

                                Hallo zusammen,

                                kann mir jemand erklären wie ich von meinem Gen1 mit ValetudoRE 0.8.1 / Firmware 3.3.9 - 3468 die bereits in Valetudo angelegten Zonen in ioBroker importieren und ansteuern kann?
                                Hab irgendwie den Überblick verloren und bekomme es so nicht hin....

                                0 1 Reply Last reply Reply Quote 0
                                • J
                                  Jaschkopf @Diginix last edited by

                                  @Diginix Entschuldigung das ich keine Zeit hatte die letzten 600 Beiträge zu lesen und die Frechheit besaß eine Frage zu stellen...

                                  Diginix 1 Reply Last reply Reply Quote 0
                                  • Diginix
                                    Diginix @Jaschkopf last edited by Diginix

                                    @Jaschkopf Jeder wie er es für richtig hält.
                                    So hat der nächste dann eine Ausrede weil es 601 Posts sind.
                                    Kann ja auch nicht jeder Suchende mit Suchfunktionen umgehen. Dafür gibt es hier dann eben freundliche Entwickler die Fragen gern mehrfach beantworten, als die Zeit für Entwicklung zu nutzen.
                                    Passt schon. Danke.

                                    1 Reply Last reply Reply Quote 1
                                    • J
                                      Jaschkopf last edited by

                                      Kann mir jemand auf die schnelle helfen wie ich mit Blockly der Variable "MultiRoomClean" die Räume zuweisen kann? Finde dazu keine Funktion wie ich den Wert "Raum" steuern kann. Über die manuelle Raumzuweisung in der Objektliste klappt es, aber möchte gerne unterschiedliche Zonen zusammen legen.

                                      Gruß Jaschkopf

                                      D 1 Reply Last reply Reply Quote 0
                                      • J
                                        Jaschkopf last edited by

                                        Hab gerade auf 2.0.9 über github geupdated und jetzt stürzen die Instanzen permanent ab. Hier ein Log:

                                        mihome-vacuum.0	2020-03-13 17:25:19.053	info	(17352) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.0	2020-03-13 17:25:18.606	info	(17352) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:25:18.577	info	(17352) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.0	2020-03-13 17:25:18.576	info	(17352) extend state mop for State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:25:18.574	info	(17352) change states from State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:25:18.500	info	(17352) Cloud control disabled
                                        mihome-vacuum.0	2020-03-13 17:25:18.498	info	(17352) Expert mode disabled, states deleted
                                        mihome-vacuum.0	2020-03-13 17:25:18.401	info	(17352) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        mihome-vacuum.1	2020-03-13 17:25:16.432	info	(17232) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.1	2020-03-13 17:25:15.979	info	(17232) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:25:15.927	info	(17232) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.1	2020-03-13 17:25:15.925	info	(17232) extend state mop for State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:25:15.924	info	(17232) change states from State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:25:15.894	info	(17232) Cloud control disabled
                                        mihome-vacuum.1	2020-03-13 17:25:15.891	info	(17232) Expert mode disabled, states deleted
                                        mihome-vacuum.1	2020-03-13 17:25:15.847	info	(17232) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        host.raspberrypi	2020-03-13 17:25:15.566	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                                        host.raspberrypi	2020-03-13 17:25:15.565	error	instance system.adapter.mihome-vacuum.0 terminated with code 156 (156)
                                        mihome-vacuum.0	2020-03-13 17:25:15.043	warn	(15936) Got terminate signal. Checking desired PID: 17352 vs own PID 15936
                                        mihome-vacuum.0	2020-03-13 17:25:15.040	info	(15936) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.0	2020-03-13 17:25:15.039	info	(15936) terminating
                                        mihome-vacuum.0	2020-03-13 17:25:15.036	warn	(15936) Got terminate signal. Checking desired PID: 0 vs own PID 15936
                                        host.raspberrypi	2020-03-13 17:25:15.031	info	instance system.adapter.mihome-vacuum.0 started with pid 17352
                                        host.raspberrypi	2020-03-13 17:25:13.415	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                                        host.raspberrypi	2020-03-13 17:25:13.414	error	instance system.adapter.mihome-vacuum.1 terminated with code 156 (156)
                                        mihome-vacuum.1	2020-03-13 17:25:12.888	warn	(15746) Got terminate signal. Checking desired PID: 17232 vs own PID 15746
                                        mihome-vacuum.1	2020-03-13 17:25:12.883	info	(15746) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.1	2020-03-13 17:25:12.881	info	(15746) terminating
                                        mihome-vacuum.1	2020-03-13 17:25:12.877	warn	(15746) Got terminate signal. Checking desired PID: 0 vs own PID 15746
                                        host.raspberrypi	2020-03-13 17:25:12.870	info	instance system.adapter.mihome-vacuum.1 started with pid 17232
                                        mihome-vacuum.0	2020-03-13 17:25:07.880	info	(15936) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:25:07.880	warn	(15936) Time difference between Mihome Vacuum and ioBroker: 1 sec
                                        mihome-vacuum.1	2020-03-13 17:25:05.913	info	(15746) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:24:48.390	info	(15936) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.0	2020-03-13 17:24:47.963	info	(15936) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:24:47.962	warn	(15936) Time difference between Mihome Vacuum and ioBroker: 1 sec
                                        mihome-vacuum.0	2020-03-13 17:24:47.932	info	(15936) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.0	2020-03-13 17:24:47.930	info	(15936) extend state mop for State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:24:47.929	info	(15936) change states from State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:24:47.863	info	(15936) Cloud control disabled
                                        mihome-vacuum.0	2020-03-13 17:24:47.862	info	(15936) Expert mode disabled, states deleted
                                        mihome-vacuum.0	2020-03-13 17:24:47.703	info	(15936) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        mihome-vacuum.1	2020-03-13 17:24:46.424	info	(15746) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.1	2020-03-13 17:24:45.995	info	(15746) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:24:45.933	info	(15746) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.1	2020-03-13 17:24:45.931	info	(15746) extend state mop for State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:24:45.930	info	(15746) change states from State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:24:45.894	info	(15746) Cloud control disabled
                                        mihome-vacuum.1	2020-03-13 17:24:45.891	info	(15746) Expert mode disabled, states deleted
                                        mihome-vacuum.1	2020-03-13 17:24:45.839	info	(15746) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        host.raspberrypi	2020-03-13 17:24:45.009	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                                        host.raspberrypi	2020-03-13 17:24:45.009	error	instance system.adapter.mihome-vacuum.0 terminated with code 156 (156)
                                        mihome-vacuum.0	2020-03-13 17:24:44.487	warn	(14925) Got terminate signal. Checking desired PID: 15936 vs own PID 14925
                                        mihome-vacuum.0	2020-03-13 17:24:44.479	info	(14925) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.0	2020-03-13 17:24:44.476	info	(14925) terminating
                                        mihome-vacuum.0	2020-03-13 17:24:44.469	warn	(14925) Got terminate signal. Checking desired PID: 0 vs own PID 14925
                                        host.raspberrypi	2020-03-13 17:24:44.463	info	instance system.adapter.mihome-vacuum.0 started with pid 15936
                                        host.raspberrypi	2020-03-13 17:24:42.832	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                                        host.raspberrypi	2020-03-13 17:24:42.831	error	instance system.adapter.mihome-vacuum.1 terminated with code 156 (156)
                                        mihome-vacuum.1	2020-03-13 17:24:42.291	warn	(14897) Got terminate signal. Checking desired PID: 15746 vs own PID 14897
                                        mihome-vacuum.1	2020-03-13 17:24:42.287	info	(14897) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.1	2020-03-13 17:24:42.286	info	(14897) terminating
                                        mihome-vacuum.1	2020-03-13 17:24:42.284	warn	(14897) Got terminate signal. Checking desired PID: 0 vs own PID 14897
                                        host.raspberrypi	2020-03-13 17:24:42.273	info	instance system.adapter.mihome-vacuum.1 started with pid 15746
                                        mihome-vacuum.0	2020-03-13 17:24:37.726	info	(14925) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:24:36.488	info	(14897) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:24:18.880	info	(14925) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:24:18.880	warn	(14925) Time difference between Mihome Vacuum and ioBroker: 1 sec
                                        mihome-vacuum.0	2020-03-13 17:24:18.864	info	(14925) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.0	2020-03-13 17:24:17.776	info	(14925) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.0	2020-03-13 17:24:17.775	info	(14925) extend state mop for State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:24:17.774	info	(14925) change states from State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:24:17.705	info	(14925) Cloud control disabled
                                        mihome-vacuum.0	2020-03-13 17:24:17.703	info	(14925) Expert mode disabled, states deleted
                                        mihome-vacuum.0	2020-03-13 17:24:17.608	info	(14925) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        mihome-vacuum.1	2020-03-13 17:24:15.944	info	(14897) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.1	2020-03-13 17:24:15.484	info	(14897) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:24:15.451	info	(14897) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.1	2020-03-13 17:24:15.449	info	(14897) extend state mop for State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:24:15.448	info	(14897) change states from State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:24:15.412	info	(14897) Cloud control disabled
                                        mihome-vacuum.1	2020-03-13 17:24:15.409	info	(14897) Expert mode disabled, states deleted
                                        mihome-vacuum.1	2020-03-13 17:24:15.365	info	(14897) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        host.raspberrypi	2020-03-13 17:24:14.429	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                                        host.raspberrypi	2020-03-13 17:24:14.429	error	instance system.adapter.mihome-vacuum.0 terminated with code 156 (156)
                                        mihome-vacuum.0	2020-03-13 17:24:13.903	warn	(13853) Got terminate signal. Checking desired PID: 14925 vs own PID 13853
                                        mihome-vacuum.0	2020-03-13 17:24:13.900	info	(13853) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.0	2020-03-13 17:24:13.899	info	(13853) terminating
                                        mihome-vacuum.0	2020-03-13 17:24:13.897	warn	(13853) Got terminate signal. Checking desired PID: 0 vs own PID 13853
                                        host.raspberrypi	2020-03-13 17:24:13.894	info	instance system.adapter.mihome-vacuum.0 started with pid 14925
                                        host.raspberrypi	2020-03-13 17:24:12.252	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                                        host.raspberrypi	2020-03-13 17:24:12.250	error	instance system.adapter.mihome-vacuum.1 terminated with code 156 (156)
                                        mihome-vacuum.1	2020-03-13 17:24:11.728	warn	(13825) Got terminate signal. Checking desired PID: 14897 vs own PID 13825
                                        mihome-vacuum.1	2020-03-13 17:24:11.724	info	(13825) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.1	2020-03-13 17:24:11.722	info	(13825) terminating
                                        mihome-vacuum.1	2020-03-13 17:24:11.718	warn	(13825) Got terminate signal. Checking desired PID: 0 vs own PID 13825
                                        host.raspberrypi	2020-03-13 17:24:11.712	info	instance system.adapter.mihome-vacuum.1 started with pid 14897
                                        mihome-vacuum.0	2020-03-13 17:24:06.409	info	(13853) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:24:04.362	info	(13825) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:23:46.924	info	(13853) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.0	2020-03-13 17:23:46.546	info	(13853) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:23:46.501	info	(13853) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.0	2020-03-13 17:23:46.498	info	(13853) extend state mop for State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:23:46.496	info	(13853) change states from State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:23:46.392	info	(13853) Cloud control disabled
                                        mihome-vacuum.0	2020-03-13 17:23:46.391	info	(13853) Expert mode disabled, states deleted
                                        mihome-vacuum.0	2020-03-13 17:23:46.292	info	(13853) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        mihome-vacuum.1	2020-03-13 17:23:44.873	info	(13825) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.1	2020-03-13 17:23:44.486	info	(13825) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:23:44.404	info	(13825) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.1	2020-03-13 17:23:44.387	info	(13825) extend state mop for State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:23:44.384	info	(13825) change states from State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:23:44.340	info	(13825) Cloud control disabled
                                        mihome-vacuum.1	2020-03-13 17:23:44.338	info	(13825) Expert mode disabled, states deleted
                                        mihome-vacuum.1	2020-03-13 17:23:44.294	info	(13825) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        host.raspberrypi	2020-03-13 17:23:43.876	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                                        host.raspberrypi	2020-03-13 17:23:43.876	error	instance system.adapter.mihome-vacuum.0 terminated with code 156 (156)
                                        mihome-vacuum.0	2020-03-13 17:23:43.354	warn	(12840) Got terminate signal. Checking desired PID: 13853 vs own PID 12840
                                        mihome-vacuum.0	2020-03-13 17:23:43.344	info	(12840) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.0	2020-03-13 17:23:43.343	info	(12840) terminating
                                        mihome-vacuum.0	2020-03-13 17:23:43.341	warn	(12840) Got terminate signal. Checking desired PID: 0 vs own PID 12840
                                        host.raspberrypi	2020-03-13 17:23:43.338	info	instance system.adapter.mihome-vacuum.0 started with pid 13853
                                        host.raspberrypi	2020-03-13 17:23:41.674	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                                        host.raspberrypi	2020-03-13 17:23:41.673	error	instance system.adapter.mihome-vacuum.1 terminated with code 156 (156)
                                        mihome-vacuum.1	2020-03-13 17:23:41.155	warn	(12812) Got terminate signal. Checking desired PID: 13825 vs own PID 12812
                                        mihome-vacuum.1	2020-03-13 17:23:41.149	info	(12812) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.1	2020-03-13 17:23:41.147	info	(12812) terminating
                                        mihome-vacuum.1	2020-03-13 17:23:41.143	warn	(12812) Got terminate signal. Checking desired PID: 0 vs own PID 12812
                                        host.raspberrypi	2020-03-13 17:23:41.137	info	instance system.adapter.mihome-vacuum.1 started with pid 13825
                                        mihome-vacuum.0	2020-03-13 17:23:36.598	info	(12840) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:23:33.629	info	(12812) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:23:16.466	info	(12840) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.0	2020-03-13 17:23:16.029	info	(12840) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.0	2020-03-13 17:23:15.997	info	(12840) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.0	2020-03-13 17:23:15.994	info	(12840) extend state mop for State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:23:15.992	info	(12840) change states from State control.fan_power
                                        mihome-vacuum.0	2020-03-13 17:23:15.917	info	(12840) Cloud control disabled
                                        mihome-vacuum.0	2020-03-13 17:23:15.915	info	(12840) Expert mode disabled, states deleted
                                        mihome-vacuum.0	2020-03-13 17:23:15.817	info	(12840) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        mihome-vacuum.1	2020-03-13 17:23:14.146	info	(12812) set nächster Timer: Nicht verfügbar
                                        mihome-vacuum.1	2020-03-13 17:23:13.722	info	(12812) connecting, this can take up to 10 minutes ...
                                        mihome-vacuum.1	2020-03-13 17:23:13.653	info	(12812) New generation or new fw(3.5.7,002008) detected, create new states goto and zoneclean
                                        mihome-vacuum.1	2020-03-13 17:23:13.651	info	(12812) extend state mop for State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:23:13.650	info	(12812) change states from State control.fan_power
                                        mihome-vacuum.1	2020-03-13 17:23:13.605	info	(12812) Cloud control disabled
                                        mihome-vacuum.1	2020-03-13 17:23:13.603	info	(12812) Expert mode disabled, states deleted
                                        mihome-vacuum.1	2020-03-13 17:23:13.557	info	(12812) starting. Version 2.0.9-RC03 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.18.0
                                        host.raspberrypi	2020-03-13 17:23:13.322	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                                        host.raspberrypi	2020-03-13 17:23:13.321	error	instance system.adapter.mihome-vacuum.0 terminated with code 156 (156)
                                        mihome-vacuum.0	2020-03-13 17:23:12.798	warn	(11748) Got terminate signal. Checking desired PID: 12840 vs own PID 11748
                                        mihome-vacuum.0	2020-03-13 17:23:12.794	info	(11748) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        mihome-vacuum.0	2020-03-13 17:23:12.792	info	(11748) terminating
                                        mihome-vacuum.0	2020-03-13 17:23:12.789	warn	(11748) Got terminate signal. Checking desired PID: 0 vs own PID 11748
                                        host.raspberrypi	2020-03-13 17:23:12.786	info	instance system.adapter.mihome-vacuum.0 started with pid 12840
                                        host.raspberrypi	2020-03-13 17:23:11.104	info	Restart adapter system.adapter.mihome-vacuum.1 because enabled
                                        host.raspberrypi	2020-03-13 17:23:11.104	error	instance system.adapter.mihome-vacuum.1 terminated with code 156 (156)
                                        mihome-vacuum.1	2020-03-13 17:23:10.571	warn	(11714) Got terminate signal. Checking desired PID: 12812 vs own PID 11714
                                        
                                        Diginix J 2 Replies Last reply Reply Quote 0
                                        • Diginix
                                          Diginix @Jaschkopf last edited by

                                          @Jaschkopf
                                          Raumzuweisung geht nicht per Skript, schon gar nicht mit eingeschränktem Blockly. War hier auch schon Thema.

                                          Dein Absturz kommt durch mind ein Zombieprozess. Entweder killst du die PID in der Kommandozeile oder startest alles komplett neu durch.

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

                                            @Jaschkopf dafür gibt es zoneclean oder x_sendcommand oder du machst es per Timer, habe ich auch schon mehrfach beschrieben

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            396
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

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