Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter mihome-vacuum v2.0.x

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

Test Adapter mihome-vacuum v2.0.x

Geplant Angeheftet Gesperrt Verschoben Tester
xiaomiroborockmihome-vacuummap
1.5k Beiträge 144 Kommentatoren 499.5k Aufrufe 118 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • J Jaschkopf

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

    DiginixD Offline
    DiginixD Offline
    Diginix
    schrieb am zuletzt editiert von Diginix
    #597

    @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.

    ..:: So long! Tom ::..

    NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

    1 Antwort Letzte Antwort
    1
    • J Offline
      J Offline
      Jaschkopf
      schrieb am zuletzt editiert von
      #598

      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 Antwort Letzte Antwort
      0
      • J Offline
        J Offline
        Jaschkopf
        schrieb am zuletzt editiert von
        #599

        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
        
        DiginixD J 2 Antworten Letzte Antwort
        0
        • J Jaschkopf

          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
          
          DiginixD Offline
          DiginixD Offline
          Diginix
          schrieb am zuletzt editiert von
          #600

          @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.

          ..:: So long! Tom ::..

          NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

          1 Antwort Letzte Antwort
          0
          • J Jaschkopf

            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 Nicht stören
            D Nicht stören
            dirkhe
            Developer
            schrieb am zuletzt editiert von
            #601

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

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

              @Diginix Fix ist im Git 2.0.9-RC05.

              Übrigens so sieht meine Vis aus, wenn de State eines Raumchannels gefüllt ist:
              09502dfe-16d2-48ed-a098-ff561a5bbc43-image.png

              X 1 Antwort Letzte Antwort
              5
              • 0 0018

                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 Offline
                0 Offline
                0018
                schrieb am zuletzt editiert von
                #603

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

                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?

                Jemand ne Auskunft für mich? Ist das mit Gen1 möglich oder wird dieser nicht in dem Adapter integriert?

                Mfg
                0018

                haselchenH 1 Antwort Letzte Antwort
                0
                • 0 0018

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

                  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?

                  Jemand ne Auskunft für mich? Ist das mit Gen1 möglich oder wird dieser nicht in dem Adapter integriert?

                  haselchenH Offline
                  haselchenH Offline
                  haselchen
                  Most Active
                  schrieb am zuletzt editiert von
                  #604

                  @dirkhe

                  RC06 ist online...changelog?

                  Synology DS218+ & 2 x Fujitsu Esprimo (VM/Container) + FritzBox7590 + 2 AVM 3000 Repeater & Homematic & HUE & Osram & Xiaomi, NPM 10.9.4, Nodejs 22.21.0 ,JS Controller 7.0.7 ,Admin 7.7.19

                  D 1 Antwort Letzte Antwort
                  0
                  • K Offline
                    K Offline
                    Kludi
                    schrieb am zuletzt editiert von
                    #605

                    Hallo
                    Ich wollte von Version 1.1.5 stable auf die 2.07 last Version updaten.
                    Leider bekomme ich immer die Fehlermeldung "Fertig mit Fehler: host.tinkerboard Cannot install iobroker.mihome-vacuum@2.0.7: 1"

                    $ ./iobroker upgrade mihome-vacuum
                    Update mihome-vacuum from @1.1.5 to @2.0.7
                    NPM version: 6.13.4
                    npm install iobroker.mihome-vacuum@2.0.7 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                    Package pixman-1 was not found in the pkg-config search path.Perhaps you should add the directory containing `pixman-1.pc'to the PKG_CONFIG_PATH environment variableNo package 'pixman-1' found
                    gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
                    gyp
                     ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR!
                     stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.69-rockchipgyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! cwd /opt/iobroker/node_modules/canvasgyp ERR! node -v v10.19.0gyp ERR! 
                    node-gyp -v v5.0.5gyp ERR! not ok 
                    node-pre-gyp
                     ERR! build error 
                    node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp
                     ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack
                         at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                    node-pre-gyp ERR! System Linux 4.19.69-rockchipnode-pre-gyp ERR!
                     command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvasnode-pre-gyp ERR! node -v
                     v10.19.0node-pre-gyp ERR! node-pre-gyp -v v0.11.0node-pre-gyp ERR! not ok 
                    npm
                     ERR! code ELIFECYCLEnpm ERR! errno 1
                    npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the canvas@2.6.1 install script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                    
                    npm ERR! A complete log of this run can be found in:npm ERR!     /root/.npm/_logs/2020-03-15T16_15_09_710Z-debug.log
                    ERROR: host.tinkerboard Cannot install iobroker.mihome-vacuum@2.0.7: 1
                    ERROR: process exited with code 25
                    

                    Was mach ich falsch?

                    MFG Kludi

                    D 1 Antwort Letzte Antwort
                    0
                    • haselchenH haselchen

                      @dirkhe

                      RC06 ist online...changelog?

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

                      @haselchen https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/commits/master

                      1 Antwort Letzte Antwort
                      1
                      • K Kludi

                        Hallo
                        Ich wollte von Version 1.1.5 stable auf die 2.07 last Version updaten.
                        Leider bekomme ich immer die Fehlermeldung "Fertig mit Fehler: host.tinkerboard Cannot install iobroker.mihome-vacuum@2.0.7: 1"

                        $ ./iobroker upgrade mihome-vacuum
                        Update mihome-vacuum from @1.1.5 to @2.0.7
                        NPM version: 6.13.4
                        npm install iobroker.mihome-vacuum@2.0.7 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                        Package pixman-1 was not found in the pkg-config search path.Perhaps you should add the directory containing `pixman-1.pc'to the PKG_CONFIG_PATH environment variableNo package 'pixman-1' found
                        gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
                        gyp
                         ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR!
                         stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.69-rockchipgyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! cwd /opt/iobroker/node_modules/canvasgyp ERR! node -v v10.19.0gyp ERR! 
                        node-gyp -v v5.0.5gyp ERR! not ok 
                        node-pre-gyp
                         ERR! build error 
                        node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp
                         ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack
                             at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                        node-pre-gyp ERR! System Linux 4.19.69-rockchipnode-pre-gyp ERR!
                         command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvasnode-pre-gyp ERR! node -v
                         v10.19.0node-pre-gyp ERR! node-pre-gyp -v v0.11.0node-pre-gyp ERR! not ok 
                        npm
                         ERR! code ELIFECYCLEnpm ERR! errno 1
                        npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the canvas@2.6.1 install script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                        
                        npm ERR! A complete log of this run can be found in:npm ERR!     /root/.npm/_logs/2020-03-15T16_15_09_710Z-debug.log
                        ERROR: host.tinkerboard Cannot install iobroker.mihome-vacuum@2.0.7: 1
                        ERROR: process exited with code 25
                        

                        Was mach ich falsch?

                        MFG Kludi

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

                        @Kludi Bitte readme lesen, ganz im Anfang. Das Problem ist die canvas

                        V 1 Antwort Letzte Antwort
                        0
                        • D dirkhe

                          @Diginix Fix ist im Git 2.0.9-RC05.

                          Übrigens so sieht meine Vis aus, wenn de State eines Raumchannels gefüllt ist:
                          09502dfe-16d2-48ed-a098-ff561a5bbc43-image.png

                          X Offline
                          X Offline
                          xADDRx
                          schrieb am zuletzt editiert von
                          #608

                          @dirkhe deine Vis sieht echt gut aus. Teilen du mit uns :D?

                          Sonos, Intel Nuc, Iobroker Pro, Proxmox, IPad Air (Wand), Vis, Xiaomi, Devolo, Bose, Philips Hue, Instar, Synology

                          D 1 Antwort Letzte Antwort
                          1
                          • J Jaschkopf

                            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
                            
                            J Offline
                            J Offline
                            jayfizzle
                            schrieb am zuletzt editiert von
                            #609

                            @Jaschkopf Habe ein ähnliches Problem, konntest du deins lösen? Ein Neustart des raspi, Neuinstallation brachte keinen Erfolg. Bin nun auf die 2.0.7 gegangen, diese läft ohne die Connection Probleme.

                            1 Antwort Letzte Antwort
                            0
                            • X xADDRx

                              @dirkhe deine Vis sieht echt gut aus. Teilen du mit uns :D?

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

                              @xADDRx Na klar, Grundlage sind die materialdesign widgets

                              Hier sind die 4 Views:
                              staubi-vis-views.json
                              Ich weiss nicht, ob man die direkt so einlesen kannst, sonst eben einzeln importieren

                              M 1 Antwort Letzte Antwort
                              1
                              • D dirkhe

                                @xADDRx Na klar, Grundlage sind die materialdesign widgets

                                Hier sind die 4 Views:
                                staubi-vis-views.json
                                Ich weiss nicht, ob man die direkt so einlesen kannst, sonst eben einzeln importieren

                                M Offline
                                M Offline
                                mameier1234
                                schrieb am zuletzt editiert von
                                #611

                                @dirkhe

                                Danke fürs teilen... Aber so krieg ich das leider nicht rein.. Da kommt immer ein JSON Fehler.. auch wenn ich die einzelnen Views importieren will...

                                Hat das sonst jemand geschafft ??? Sind nämlich echt schön....

                                Grüße,

                                Martin

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

                                  @mameier1234 Hier sind mal die 3 einzeln:

                                  staubi-wartung-vis-views.json
                                  staubi-history-vis-views.json
                                  staubi-steuerung-vis-views.json

                                  M 1 Antwort Letzte Antwort
                                  0
                                  • I Offline
                                    I Offline
                                    iphone333
                                    schrieb am zuletzt editiert von
                                    #613

                                    Hallo zusammen,

                                    dieser Wert kann doch nicht stimmen, dürfte doch nur bis 100% gehen oder? Ist ein Roborock S5 Max.
                                    faxpower.JPG

                                    DiginixD 1 Antwort Letzte Antwort
                                    0
                                    • I iphone333

                                      Hallo zusammen,

                                      dieser Wert kann doch nicht stimmen, dürfte doch nur bis 100% gehen oder? Ist ein Roborock S5 Max.
                                      faxpower.JPG

                                      DiginixD Offline
                                      DiginixD Offline
                                      Diginix
                                      schrieb am zuletzt editiert von
                                      #614

                                      @iphone333 Das sind keine Prozentwerte. Ist ja auch keine Einheit dahinter.
                                      Es sind einfach numerische Werte für die einzelnen Saugstärken und die liegen alle über 100. Nur die alten Sauger bzw. mit alter Firmware gab es das in Prozent (0-100%). Daher wurden die neuen Saugstärken (min, max, turbo usw.) von Xiaomi/Roborock evtl. auch oberhalb 100 festgelegt.

                                      ..:: So long! Tom ::..

                                      NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                                      I 1 Antwort Letzte Antwort
                                      0
                                      • DiginixD Diginix

                                        @iphone333 Das sind keine Prozentwerte. Ist ja auch keine Einheit dahinter.
                                        Es sind einfach numerische Werte für die einzelnen Saugstärken und die liegen alle über 100. Nur die alten Sauger bzw. mit alter Firmware gab es das in Prozent (0-100%). Daher wurden die neuen Saugstärken (min, max, turbo usw.) von Xiaomi/Roborock evtl. auch oberhalb 100 festgelegt.

                                        I Offline
                                        I Offline
                                        iphone333
                                        schrieb am zuletzt editiert von
                                        #615

                                        @Diginix
                                        @iphone333 Das sind keine Prozentwerte. Ist ja auch keine Einheit dahinter.
                                        Es sind einfach numerische Werte für die einzelnen Saugstärken und die liegen alle über 100. Nur die alten Sauger bzw. mit alter Firmware gab es das in Prozent (0-100%). Daher wurden die neuen Saugstärken (min, max, turbo usw.) von Xiaomi/Roborock evtl. auch oberhalb 100 festgelegt.
                                        Es wird aber kein Wert wie mix, max, übernommen

                                        DiginixD 1 Antwort Letzte Antwort
                                        0
                                        • I iphone333

                                          @Diginix
                                          @iphone333 Das sind keine Prozentwerte. Ist ja auch keine Einheit dahinter.
                                          Es sind einfach numerische Werte für die einzelnen Saugstärken und die liegen alle über 100. Nur die alten Sauger bzw. mit alter Firmware gab es das in Prozent (0-100%). Daher wurden die neuen Saugstärken (min, max, turbo usw.) von Xiaomi/Roborock evtl. auch oberhalb 100 festgelegt.
                                          Es wird aber kein Wert wie mix, max, übernommen

                                          DiginixD Offline
                                          DiginixD Offline
                                          Diginix
                                          schrieb am zuletzt editiert von Diginix
                                          #616

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

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

                                          Welche Adapter Version nutzt du?

                                          ..:: So long! Tom ::..

                                          NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                                          I L 2 Antworten Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          885

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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