NEWS
Proxmox VM friert ein
-
@crunchip
so wie ich es in der anderen Diskussion https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/ verstanden habe, geht es um den Kernel des Host-Systems. Dort wird vermutet und untersucht, ob es mit dem Prozessor N5105 ein Kernel-Problem mit der KVM-Virtualisierung gibt. Der Fehler scheint jedoch nicht wirklich reproduzierbar aufzutreten.
Das Numa habe ich erst nach dem letzten Absturz in der ioBroker VM aktiviert (weil die Raspberrymatic VM das setting hatte und stabil läuft).
Jetzt laufen die VMs seit zwei Tagen ohne Absturz. Ich warte erst mal bis zum nächsten Absturz, bis ich wieder Änderungen vornehme.@isi07 sagte in Proxmox VM friert ein:
geht es um den Kernel des Host-Systems
@isi07 sagte in Proxmox VM friert ein:
friert die IObroker-VM mit den beschriebenen Symptomen ein
@isi07 sagte in Proxmox VM friert ein:
Ich habe mehrere VMs und einen LXC Container. Das Problem tritt bei mir nur in der VM mit iobroker auf
ist dann aber etwas widersprüchlich deine Aussage
umgestiegen von Proxmox auf Unraid
-
@isi07 sagte in Proxmox VM friert ein:
geht es um den Kernel des Host-Systems
@isi07 sagte in Proxmox VM friert ein:
friert die IObroker-VM mit den beschriebenen Symptomen ein
@isi07 sagte in Proxmox VM friert ein:
Ich habe mehrere VMs und einen LXC Container. Das Problem tritt bei mir nur in der VM mit iobroker auf
ist dann aber etwas widersprüchlich deine Aussage
-
@crunchip
mag sein, habe diesen Thread bei Proxmox gefunden
ich kann nur schildern, welche Fehler bei mir auftreten
und bisher ist bei mir nur die ioBroker VM eingefroren@isi07 dann eher mal die Auslastung von iobroker selbst beobachten, js-controller cpu, load der Maschine, ...
-
Hallo Zusammen,
ich reihe mich hier mal ein in die Liste der Geplagten ein.
Bei mir läuft Proxmox (aktuell 7.3-4) mit 3 VMS.
Eine mit ioBroker (6.3.5 mit JS Controller 4.0.24), eine mit InfluxDB (1.8.6) und eine mit Grafana (9.3.5).Das ganze lief jetzt ein Jahr lang fast stabil, so aller 3-4 Monate hatte ich das Einfrierproblem und ich dachte erst, dass es (Hab jeweils Debian 11 VM mit Desktop drauf) daran liegt, dass wenn Debian sagt es wären neue Updates verfügbar, dass er dann einfriert. Die Meldung der Updates hab ich dann ausgeschalten, selbes Problem.
Seit Weihnachten haben sich die Ausfälle stark gehäuft so dass diese nun zwischen 2 und 48 Stunden auftreten.
Ich hab schon einiges ausprobiert, also diverse Adapter deaktiviert die ich in Verdacht hatte usw.Wenn "nur" die Grundinstallation von ioBroker aktiv ist, also Admin, BackitUp und Discovery läuft "scheint" es keine Probleme zu geben.
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch, dann hab ich gestern alle Adapter neu installiert und die meisten konfiguriert und zack, heute abgeschmiert.
CPU ist ein Cerleron N5105 ... keine Ahnung ob das wirklich an dem liegt, lief ja vorher auch.
Stutzig macht mich aber, dass auch die InfluxDB VM jetzt schon 2-3 mal abgeschmiert ist und auch die Grafana VM schon einmal.
Sehr, sehr strange.Das nächste was ich ausprobiere werde - wohl oder übel - ich werde mir eine AMD Kiste holen und dort Proxmox und die VMs neu aufsetzen.
Bin gespannt was dann passiert.Ich werde berichten. So richtig kann ich aber an den CPU Fehler nicht glauben.
Falls jemand schon weiter ist oder sogar das Problem schon eindeutig identifizieren konnte, gern posten ;-)Ärgerlich weil ich eigentlich an ioBroker weiter bauen will aber hilft nix, so kann ich damit nicht arbeiten.
Trotzdem einen schönen Abend an alle Geplagten.
-
Hallo Zusammen,
ich reihe mich hier mal ein in die Liste der Geplagten ein.
Bei mir läuft Proxmox (aktuell 7.3-4) mit 3 VMS.
Eine mit ioBroker (6.3.5 mit JS Controller 4.0.24), eine mit InfluxDB (1.8.6) und eine mit Grafana (9.3.5).Das ganze lief jetzt ein Jahr lang fast stabil, so aller 3-4 Monate hatte ich das Einfrierproblem und ich dachte erst, dass es (Hab jeweils Debian 11 VM mit Desktop drauf) daran liegt, dass wenn Debian sagt es wären neue Updates verfügbar, dass er dann einfriert. Die Meldung der Updates hab ich dann ausgeschalten, selbes Problem.
Seit Weihnachten haben sich die Ausfälle stark gehäuft so dass diese nun zwischen 2 und 48 Stunden auftreten.
Ich hab schon einiges ausprobiert, also diverse Adapter deaktiviert die ich in Verdacht hatte usw.Wenn "nur" die Grundinstallation von ioBroker aktiv ist, also Admin, BackitUp und Discovery läuft "scheint" es keine Probleme zu geben.
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch, dann hab ich gestern alle Adapter neu installiert und die meisten konfiguriert und zack, heute abgeschmiert.
CPU ist ein Cerleron N5105 ... keine Ahnung ob das wirklich an dem liegt, lief ja vorher auch.
Stutzig macht mich aber, dass auch die InfluxDB VM jetzt schon 2-3 mal abgeschmiert ist und auch die Grafana VM schon einmal.
Sehr, sehr strange.Das nächste was ich ausprobiere werde - wohl oder übel - ich werde mir eine AMD Kiste holen und dort Proxmox und die VMs neu aufsetzen.
Bin gespannt was dann passiert.Ich werde berichten. So richtig kann ich aber an den CPU Fehler nicht glauben.
Falls jemand schon weiter ist oder sogar das Problem schon eindeutig identifizieren konnte, gern posten ;-)Ärgerlich weil ich eigentlich an ioBroker weiter bauen will aber hilft nix, so kann ich damit nicht arbeiten.
Trotzdem einen schönen Abend an alle Geplagten.
-
@900icard sagte in Proxmox VM friert ein:
und die meisten konfiguriert und zack, heute abgeschmiert.
Und was steht dazu im ioBroker Log !?
@glasfaser said in Proxmox VM friert ein:
@900icard sagte in Proxmox VM friert ein:
und die meisten konfiguriert und zack, heute abgeschmiert.
Und was steht dazu im ioBroker Log !?
Meiner Meinung nach nichts verwertbares.
Das hier 17:15 zuletzt der SBFspot Adapter terminated wurde ist beliebig.
Die letzte Meldung ist immer eine andere. Kein wirkliches Muster zu erkennen.2023-01-18 17:15:01.118 - info: sbfspot.0 (13795) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24
2023-01-18 17:15:01.156 - info: sbfspot.0 (13795) nothing to do, because no daylight ...
2023-01-18 17:15:01.157 - info: sbfspot.0 (13795) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-18 17:15:01.677 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-18 18:58:04.097 - info: host.196-iobroker-vm-V2 iobroker.js-controller version 4.0.24 js-controller starting -
@glasfaser said in Proxmox VM friert ein:
@900icard sagte in Proxmox VM friert ein:
und die meisten konfiguriert und zack, heute abgeschmiert.
Und was steht dazu im ioBroker Log !?
Meiner Meinung nach nichts verwertbares.
Das hier 17:15 zuletzt der SBFspot Adapter terminated wurde ist beliebig.
Die letzte Meldung ist immer eine andere. Kein wirkliches Muster zu erkennen.2023-01-18 17:15:01.118 - info: sbfspot.0 (13795) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24
2023-01-18 17:15:01.156 - info: sbfspot.0 (13795) nothing to do, because no daylight ...
2023-01-18 17:15:01.157 - info: sbfspot.0 (13795) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-18 17:15:01.677 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-18 18:58:04.097 - info: host.196-iobroker-vm-V2 iobroker.js-controller version 4.0.24 js-controller starting -
Hallo Zusammen,
ich reihe mich hier mal ein in die Liste der Geplagten ein.
Bei mir läuft Proxmox (aktuell 7.3-4) mit 3 VMS.
Eine mit ioBroker (6.3.5 mit JS Controller 4.0.24), eine mit InfluxDB (1.8.6) und eine mit Grafana (9.3.5).Das ganze lief jetzt ein Jahr lang fast stabil, so aller 3-4 Monate hatte ich das Einfrierproblem und ich dachte erst, dass es (Hab jeweils Debian 11 VM mit Desktop drauf) daran liegt, dass wenn Debian sagt es wären neue Updates verfügbar, dass er dann einfriert. Die Meldung der Updates hab ich dann ausgeschalten, selbes Problem.
Seit Weihnachten haben sich die Ausfälle stark gehäuft so dass diese nun zwischen 2 und 48 Stunden auftreten.
Ich hab schon einiges ausprobiert, also diverse Adapter deaktiviert die ich in Verdacht hatte usw.Wenn "nur" die Grundinstallation von ioBroker aktiv ist, also Admin, BackitUp und Discovery läuft "scheint" es keine Probleme zu geben.
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch, dann hab ich gestern alle Adapter neu installiert und die meisten konfiguriert und zack, heute abgeschmiert.
CPU ist ein Cerleron N5105 ... keine Ahnung ob das wirklich an dem liegt, lief ja vorher auch.
Stutzig macht mich aber, dass auch die InfluxDB VM jetzt schon 2-3 mal abgeschmiert ist und auch die Grafana VM schon einmal.
Sehr, sehr strange.Das nächste was ich ausprobiere werde - wohl oder übel - ich werde mir eine AMD Kiste holen und dort Proxmox und die VMs neu aufsetzen.
Bin gespannt was dann passiert.Ich werde berichten. So richtig kann ich aber an den CPU Fehler nicht glauben.
Falls jemand schon weiter ist oder sogar das Problem schon eindeutig identifizieren konnte, gern posten ;-)Ärgerlich weil ich eigentlich an ioBroker weiter bauen will aber hilft nix, so kann ich damit nicht arbeiten.
Trotzdem einen schönen Abend an alle Geplagten.
@900icard sagte in Proxmox VM friert ein:
CPU ist ein Cerleron N5105 .
der sollte mit einem Passmark von 4000 nicht zu schwach sein.
wie sieht es denn mit RAM aus
oder Plattenplatz
mehr auf die VMs verteilt, als da ist?
Auch Proxmox benötigt Ressourcen! -
@900icard sagte in Proxmox VM friert ein:
Kein wirkliches Muster zu erkennen.
bitte den ganzen Log vor und nach dem
abgeschmiert.
hier posten und in Code-Tags </> einfügen.
ok, here we go. Gehen nur 100.000 Zeichen.
Wie gesagt, einige Adapter sind noch nicht fertig konfiguriert.2023-01-18 08:00:00.033 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13044 2023-01-18 08:00:01.413 - info: sbfspot.0 (13044) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:00:01.543 - info: sbfspot.0 (13044) start with mySQL 2023-01-18 08:00:01.590 - info: sbfspot.0 (13044) got data from with ID 0 2023-01-18 08:00:02.250 - info: sbfspot.0 (13044) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:00:02.771 - info: sbfspot.0 (13044) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:00:03.224 - info: sbfspot.0 (13044) all done ... 2023-01-18 08:00:03.225 - info: sbfspot.0 (13044) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:00:03.741 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:07:03.460 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:07:06.719 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:07:08.737 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:00.590 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:02.603 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:05.119 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:18.130 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:22.100 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:24.108 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:15:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13064 2023-01-18 08:15:01.474 - info: sbfspot.0 (13064) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:15:01.618 - info: sbfspot.0 (13064) start with mySQL 2023-01-18 08:15:01.665 - info: sbfspot.0 (13064) got data from with ID 0 2023-01-18 08:15:01.948 - info: sbfspot.0 (13064) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:15:02.280 - info: sbfspot.0 (13064) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:15:02.565 - info: sbfspot.0 (13064) all done ... 2023-01-18 08:15:02.567 - info: sbfspot.0 (13064) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:15:03.103 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:30:00.038 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13087 2023-01-18 08:30:01.459 - info: sbfspot.0 (13087) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:30:01.595 - info: sbfspot.0 (13087) start with mySQL 2023-01-18 08:30:01.634 - info: sbfspot.0 (13087) got data from with ID 0 2023-01-18 08:30:02.040 - info: sbfspot.0 (13087) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:30:02.484 - info: sbfspot.0 (13087) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:30:02.786 - info: sbfspot.0 (13087) all done ... 2023-01-18 08:30:02.788 - info: sbfspot.0 (13087) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:30:03.309 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:45:00.028 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13106 2023-01-18 08:45:01.407 - info: sbfspot.0 (13106) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:45:01.565 - info: sbfspot.0 (13106) start with mySQL 2023-01-18 08:45:01.614 - info: sbfspot.0 (13106) got data from with ID 0 2023-01-18 08:45:01.922 - info: sbfspot.0 (13106) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:45:02.280 - info: sbfspot.0 (13106) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:45:02.615 - info: sbfspot.0 (13106) all done ... 2023-01-18 08:45:02.617 - info: sbfspot.0 (13106) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:45:03.146 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:50:51.822 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:50:59.143 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:51:01.156 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:00:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13126 2023-01-18 09:00:01.502 - info: sbfspot.0 (13126) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:00:01.642 - info: sbfspot.0 (13126) start with mySQL 2023-01-18 09:00:01.691 - info: sbfspot.0 (13126) got data from with ID 0 2023-01-18 09:00:02.019 - info: sbfspot.0 (13126) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:00:02.340 - info: sbfspot.0 (13126) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:00:02.664 - info: sbfspot.0 (13126) all done ... 2023-01-18 09:00:02.665 - info: sbfspot.0 (13126) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:00:03.209 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:15:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13143 2023-01-18 09:15:01.166 - info: sbfspot.0 (13143) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:15:01.277 - info: sbfspot.0 (13143) start with mySQL 2023-01-18 09:15:01.313 - info: sbfspot.0 (13143) got data from with ID 0 2023-01-18 09:15:01.551 - info: sbfspot.0 (13143) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:15:01.810 - info: sbfspot.0 (13143) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:15:02.057 - info: sbfspot.0 (13143) all done ... 2023-01-18 09:15:02.058 - info: sbfspot.0 (13143) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:15:02.578 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:17:56.764 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:17:56.814 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 09:17:56.815 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 09:17:56.900 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 09:17:56.900 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 09:17:56.944 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 09:17:56.990 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 09:17:56.991 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 09:17:57.036 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 09:17:57.037 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 09:17:57.080 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 09:17:59.263 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:17:59.310 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 09:17:59.311 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 09:17:59.395 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 09:17:59.396 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 09:17:59.440 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 09:17:59.486 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 09:17:59.487 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 09:17:59.490 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 09:17:59.532 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 09:17:59.533 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 09:30:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13167 2023-01-18 09:30:01.093 - info: sbfspot.0 (13167) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:30:01.202 - info: sbfspot.0 (13167) start with mySQL 2023-01-18 09:30:01.246 - info: sbfspot.0 (13167) got data from with ID 0 2023-01-18 09:30:01.503 - info: sbfspot.0 (13167) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:30:01.768 - info: sbfspot.0 (13167) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:30:02.018 - info: sbfspot.0 (13167) all done ... 2023-01-18 09:30:02.019 - info: sbfspot.0 (13167) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:30:02.537 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:45:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13185 2023-01-18 09:45:01.079 - info: sbfspot.0 (13185) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:45:01.204 - info: sbfspot.0 (13185) start with mySQL 2023-01-18 09:45:01.260 - info: sbfspot.0 (13185) got data from with ID 0 2023-01-18 09:45:01.526 - info: sbfspot.0 (13185) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:45:01.788 - info: sbfspot.0 (13185) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:45:02.051 - info: sbfspot.0 (13185) all done ... 2023-01-18 09:45:02.052 - info: sbfspot.0 (13185) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:45:02.571 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:00:00.045 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13204 2023-01-18 10:00:01.194 - info: sbfspot.0 (13204) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:00:01.302 - info: sbfspot.0 (13204) start with mySQL 2023-01-18 10:00:01.334 - info: sbfspot.0 (13204) got data from with ID 0 2023-01-18 10:00:01.567 - info: sbfspot.0 (13204) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:00:01.798 - info: sbfspot.0 (13204) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:00:02.059 - info: sbfspot.0 (13204) all done ... 2023-01-18 10:00:02.060 - info: sbfspot.0 (13204) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:00:02.579 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:15:00.022 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13222 2023-01-18 10:15:01.121 - info: sbfspot.0 (13222) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:15:01.265 - info: sbfspot.0 (13222) start with mySQL 2023-01-18 10:15:01.313 - info: sbfspot.0 (13222) got data from with ID 0 2023-01-18 10:15:01.547 - info: sbfspot.0 (13222) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:15:01.765 - info: sbfspot.0 (13222) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:15:01.982 - info: sbfspot.0 (13222) all done ... 2023-01-18 10:15:01.984 - info: sbfspot.0 (13222) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:15:02.505 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:30:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13247 2023-01-18 10:30:01.154 - info: sbfspot.0 (13247) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:30:01.266 - info: sbfspot.0 (13247) start with mySQL 2023-01-18 10:30:01.310 - info: sbfspot.0 (13247) got data from with ID 0 2023-01-18 10:30:01.567 - info: sbfspot.0 (13247) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:30:01.815 - info: sbfspot.0 (13247) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:30:02.061 - info: sbfspot.0 (13247) all done ... 2023-01-18 10:30:02.062 - info: sbfspot.0 (13247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:30:02.586 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:45:00.019 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13266 2023-01-18 10:45:01.085 - info: sbfspot.0 (13266) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:45:01.189 - info: sbfspot.0 (13266) start with mySQL 2023-01-18 10:45:01.229 - info: sbfspot.0 (13266) got data from with ID 0 2023-01-18 10:45:01.452 - info: sbfspot.0 (13266) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:45:01.685 - info: sbfspot.0 (13266) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:45:01.932 - info: sbfspot.0 (13266) all done ... 2023-01-18 10:45:01.933 - info: sbfspot.0 (13266) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:45:02.453 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13285 2023-01-18 11:00:01.187 - info: sbfspot.0 (13285) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:00:01.291 - info: sbfspot.0 (13285) start with mySQL 2023-01-18 11:00:01.329 - info: sbfspot.0 (13285) got data from with ID 0 2023-01-18 11:00:01.571 - info: sbfspot.0 (13285) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:00:01.819 - info: sbfspot.0 (13285) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:00:02.038 - info: sbfspot.0 (13285) all done ... 2023-01-18 11:00:02.039 - info: sbfspot.0 (13285) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:00:02.561 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:15:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13303 2023-01-18 11:15:01.087 - info: sbfspot.0 (13303) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:15:01.193 - info: sbfspot.0 (13303) start with mySQL 2023-01-18 11:15:01.229 - info: sbfspot.0 (13303) got data from with ID 0 2023-01-18 11:15:01.487 - info: sbfspot.0 (13303) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:15:01.738 - info: sbfspot.0 (13303) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:15:01.971 - info: sbfspot.0 (13303) all done ... 2023-01-18 11:15:01.972 - info: sbfspot.0 (13303) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:15:02.491 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:30:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13326 2023-01-18 11:30:01.209 - info: sbfspot.0 (13326) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:30:01.318 - info: sbfspot.0 (13326) start with mySQL 2023-01-18 11:30:01.350 - info: sbfspot.0 (13326) got data from with ID 0 2023-01-18 11:30:01.587 - info: sbfspot.0 (13326) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:30:01.831 - info: sbfspot.0 (13326) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:30:02.044 - info: sbfspot.0 (13326) all done ... 2023-01-18 11:30:02.045 - info: sbfspot.0 (13326) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:30:02.565 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:45:00.022 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13345 2023-01-18 11:45:01.140 - info: sbfspot.0 (13345) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:45:01.242 - info: sbfspot.0 (13345) start with mySQL 2023-01-18 11:45:01.284 - info: sbfspot.0 (13345) got data from with ID 0 2023-01-18 11:45:01.500 - info: sbfspot.0 (13345) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:45:01.729 - info: sbfspot.0 (13345) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:45:01.985 - info: sbfspot.0 (13345) all done ... 2023-01-18 11:45:01.986 - info: sbfspot.0 (13345) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:45:02.505 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:00:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13364 2023-01-18 12:00:01.160 - info: sbfspot.0 (13364) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:00:01.269 - info: sbfspot.0 (13364) start with mySQL 2023-01-18 12:00:01.303 - info: sbfspot.0 (13364) got data from with ID 0 2023-01-18 12:00:01.559 - info: sbfspot.0 (13364) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:00:01.834 - info: sbfspot.0 (13364) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:00:02.076 - info: sbfspot.0 (13364) all done ... 2023-01-18 12:00:02.077 - info: sbfspot.0 (13364) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:00:02.599 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:15:00.016 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13384 2023-01-18 12:15:01.144 - info: sbfspot.0 (13384) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:15:01.255 - info: sbfspot.0 (13384) start with mySQL 2023-01-18 12:15:01.289 - info: sbfspot.0 (13384) got data from with ID 0 2023-01-18 12:15:01.519 - info: sbfspot.0 (13384) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:15:01.745 - info: sbfspot.0 (13384) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:15:01.968 - info: sbfspot.0 (13384) all done ... 2023-01-18 12:15:01.969 - info: sbfspot.0 (13384) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:15:02.497 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:30:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13406 2023-01-18 12:30:01.140 - info: sbfspot.0 (13406) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:30:01.244 - info: sbfspot.0 (13406) start with mySQL 2023-01-18 12:30:01.287 - info: sbfspot.0 (13406) got data from with ID 0 2023-01-18 12:30:01.506 - info: sbfspot.0 (13406) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:30:01.726 - info: sbfspot.0 (13406) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:30:01.961 - info: sbfspot.0 (13406) all done ... 2023-01-18 12:30:01.962 - info: sbfspot.0 (13406) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:30:02.482 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:45:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13425 2023-01-18 12:45:01.148 - info: sbfspot.0 (13425) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:45:01.248 - info: sbfspot.0 (13425) start with mySQL 2023-01-18 12:45:01.290 - info: sbfspot.0 (13425) got data from with ID 0 2023-01-18 12:45:01.535 - info: sbfspot.0 (13425) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:45:01.787 - info: sbfspot.0 (13425) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:45:02.027 - info: sbfspot.0 (13425) all done ... 2023-01-18 12:45:02.028 - info: sbfspot.0 (13425) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:45:02.546 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13444 2023-01-18 13:00:01.070 - info: sbfspot.0 (13444) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:00:01.177 - info: sbfspot.0 (13444) start with mySQL 2023-01-18 13:00:01.209 - info: sbfspot.0 (13444) got data from with ID 0 2023-01-18 13:00:01.445 - info: sbfspot.0 (13444) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:00:01.679 - info: sbfspot.0 (13444) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:00:01.945 - info: sbfspot.0 (13444) all done ... 2023-01-18 13:00:01.946 - info: sbfspot.0 (13444) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:00:02.465 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:09:09.145 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 13:09:09.196 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 13:09:09.197 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 13:09:09.285 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 13:09:09.286 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 13:09:09.330 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 13:09:09.379 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 13:09:09.380 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 13:09:09.424 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 13:09:09.427 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 13:09:09.429 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 13:15:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13462 2023-01-18 13:15:01.146 - info: sbfspot.0 (13462) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:15:01.271 - info: sbfspot.0 (13462) start with mySQL 2023-01-18 13:15:01.303 - info: sbfspot.0 (13462) got data from with ID 0 2023-01-18 13:15:01.522 - info: sbfspot.0 (13462) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:15:01.762 - info: sbfspot.0 (13462) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:15:02.029 - info: sbfspot.0 (13462) all done ... 2023-01-18 13:15:02.030 - info: sbfspot.0 (13462) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:15:02.549 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:30:00.028 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13484 2023-01-18 13:30:01.118 - info: sbfspot.0 (13484) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:30:01.237 - info: sbfspot.0 (13484) start with mySQL 2023-01-18 13:30:01.280 - info: sbfspot.0 (13484) got data from with ID 0 2023-01-18 13:30:01.560 - info: sbfspot.0 (13484) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:30:01.828 - info: sbfspot.0 (13484) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:30:02.062 - info: sbfspot.0 (13484) all done ... 2023-01-18 13:30:02.063 - info: sbfspot.0 (13484) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:30:02.580 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:45:00.025 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13503 2023-01-18 13:45:01.094 - info: sbfspot.0 (13503) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:45:01.213 - info: sbfspot.0 (13503) start with mySQL 2023-01-18 13:45:01.246 - info: sbfspot.0 (13503) got data from with ID 0 2023-01-18 13:45:01.530 - info: sbfspot.0 (13503) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:45:01.810 - info: sbfspot.0 (13503) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:45:02.062 - info: sbfspot.0 (13503) all done ... 2023-01-18 13:45:02.063 - info: sbfspot.0 (13503) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:45:02.581 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:00:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13522 2023-01-18 14:00:01.149 - info: sbfspot.0 (13522) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:00:01.261 - info: sbfspot.0 (13522) start with mySQL 2023-01-18 14:00:01.296 - info: sbfspot.0 (13522) got data from with ID 0 2023-01-18 14:00:01.544 - info: sbfspot.0 (13522) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:00:01.787 - info: sbfspot.0 (13522) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:00:02.050 - info: sbfspot.0 (13522) all done ... 2023-01-18 14:00:02.051 - info: sbfspot.0 (13522) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:00:02.574 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:15:00.025 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13541 2023-01-18 14:15:01.113 - info: sbfspot.0 (13541) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:15:01.216 - info: sbfspot.0 (13541) start with mySQL 2023-01-18 14:15:01.254 - info: sbfspot.0 (13541) got data from with ID 0 2023-01-18 14:15:01.493 - info: sbfspot.0 (13541) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:15:01.715 - info: sbfspot.0 (13541) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:15:01.976 - info: sbfspot.0 (13541) all done ... 2023-01-18 14:15:01.977 - info: sbfspot.0 (13541) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:15:02.497 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:30:00.027 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13565 2023-01-18 14:30:01.127 - info: sbfspot.0 (13565) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:30:01.231 - info: sbfspot.0 (13565) start with mySQL 2023-01-18 14:30:01.271 - info: sbfspot.0 (13565) got data from with ID 0 2023-01-18 14:30:01.550 - info: sbfspot.0 (13565) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:30:01.800 - info: sbfspot.0 (13565) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:30:02.037 - info: sbfspot.0 (13565) all done ... 2023-01-18 14:30:02.038 - info: sbfspot.0 (13565) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:30:02.558 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:45:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13584 2023-01-18 14:45:01.130 - info: sbfspot.0 (13584) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:45:01.233 - info: sbfspot.0 (13584) start with mySQL 2023-01-18 14:45:01.273 - info: sbfspot.0 (13584) got data from with ID 0 2023-01-18 14:45:01.491 - info: sbfspot.0 (13584) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:45:01.739 - info: sbfspot.0 (13584) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:45:01.965 - info: sbfspot.0 (13584) all done ... 2023-01-18 14:45:01.966 - info: sbfspot.0 (13584) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:45:02.484 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13603 2023-01-18 15:00:01.144 - info: sbfspot.0 (13603) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:00:01.249 - info: sbfspot.0 (13603) start with mySQL 2023-01-18 15:00:01.283 - info: sbfspot.0 (13603) got data from with ID 0 2023-01-18 15:00:01.554 - info: sbfspot.0 (13603) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:00:01.804 - info: sbfspot.0 (13603) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:00:02.025 - info: sbfspot.0 (13603) all done ... 2023-01-18 15:00:02.026 - info: sbfspot.0 (13603) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:00:02.544 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:08:32.588 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 15:08:32.634 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 15:08:32.635 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 15:08:32.717 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 15:08:32.719 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 15:08:32.764 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 15:08:32.810 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 15:08:32.811 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 15:08:32.856 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 15:08:32.857 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 15:08:32.901 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 15:15:00.026 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13622 2023-01-18 15:15:01.146 - info: sbfspot.0 (13622) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:15:01.254 - info: sbfspot.0 (13622) start with mySQL 2023-01-18 15:15:01.295 - info: sbfspot.0 (13622) got data from with ID 0 2023-01-18 15:15:01.581 - info: sbfspot.0 (13622) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:15:01.805 - info: sbfspot.0 (13622) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:15:02.024 - info: sbfspot.0 (13622) all done ... 2023-01-18 15:15:02.025 - info: sbfspot.0 (13622) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:15:02.544 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:30:00.019 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13644 2023-01-18 15:30:01.186 - info: sbfspot.0 (13644) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:30:01.302 - info: sbfspot.0 (13644) start with mySQL 2023-01-18 15:30:01.350 - info: sbfspot.0 (13644) got data from with ID 0 2023-01-18 15:30:01.589 - info: sbfspot.0 (13644) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:30:01.844 - info: sbfspot.0 (13644) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:30:02.095 - info: sbfspot.0 (13644) all done ... 2023-01-18 15:30:02.096 - info: sbfspot.0 (13644) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:30:02.618 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:34:21.089 - warn: hmip.0 (7979) ws connection closed (0) - code: 1006 - reason: 2023-01-18 15:34:31.156 - warn: hmip.0 (7979) ws connection error (0): Error: connect ECONNREFUSED 62.113.249.105:8888 2023-01-18 15:34:31.156 - warn: hmip.0 (7979) ws connection closed (2) - code: 1006 - reason: 2023-01-18 15:34:42.457 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:34:42.543 - warn: hmip.0 (7979) ws connection closed (3) - code: 1000 - reason: 2023-01-18 15:34:53.807 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:34:53.830 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:05.089 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:05.114 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:16.482 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:16.519 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:27.845 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:27.886 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:39.393 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:39.507 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:50.413 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:50.449 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:01.347 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:01.383 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:12.284 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:12.310 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:23.160 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:23.194 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:34.012 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:34.041 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:44.803 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:44.824 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:55.562 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:55.615 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:06.260 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:06.290 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:16.847 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:16.921 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:27.525 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:27.553 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:38.103 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:38.127 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:48.683 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:48.717 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:59.111 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:59.153 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:09.571 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:09.601 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:20.572 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:20.645 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:30.809 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:30.840 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:40.957 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:41.003 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:51.296 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:51.338 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:01.772 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:01.808 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:12.196 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:12.224 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:22.582 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:22.617 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:33.411 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:33.567 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:43.701 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:43.727 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:53.847 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:53.872 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:04.128 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:40:04.197 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:14.308 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:40:14.329 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:24.462 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:45:00.029 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13663 2023-01-18 15:45:01.177 - info: sbfspot.0 (13663) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:45:01.282 - info: sbfspot.0 (13663) start with mySQL 2023-01-18 15:45:01.322 - info: sbfspot.0 (13663) got data from with ID 0 2023-01-18 15:45:01.592 - info: sbfspot.0 (13663) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:45:01.870 - info: sbfspot.0 (13663) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:45:02.111 - info: sbfspot.0 (13663) all done ... 2023-01-18 15:45:02.112 - info: sbfspot.0 (13663) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:45:02.630 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:00:00.037 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13683 2023-01-18 16:00:01.211 - info: sbfspot.0 (13683) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:00:01.356 - info: sbfspot.0 (13683) start with mySQL 2023-01-18 16:00:01.398 - info: sbfspot.0 (13683) got data from with ID 0 2023-01-18 16:00:01.638 - info: sbfspot.0 (13683) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:00:01.864 - info: sbfspot.0 (13683) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:00:02.091 - info: sbfspot.0 (13683) all done ... 2023-01-18 16:00:02.092 - info: sbfspot.0 (13683) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:00:02.612 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:15:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13701 2023-01-18 16:15:01.230 - info: sbfspot.0 (13701) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:15:01.339 - info: sbfspot.0 (13701) start with mySQL 2023-01-18 16:15:01.372 - info: sbfspot.0 (13701) got data from with ID 0 2023-01-18 16:15:01.620 - info: sbfspot.0 (13701) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:15:01.851 - info: sbfspot.0 (13701) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:15:02.081 - info: sbfspot.0 (13701) all done ... 2023-01-18 16:15:02.082 - info: sbfspot.0 (13701) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:15:02.603 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:30:00.026 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13724 2023-01-18 16:30:01.197 - info: sbfspot.0 (13724) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:30:01.306 - info: sbfspot.0 (13724) start with mySQL 2023-01-18 16:30:01.342 - info: sbfspot.0 (13724) got data from with ID 0 2023-01-18 16:30:01.603 - info: sbfspot.0 (13724) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:30:01.883 - info: sbfspot.0 (13724) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:30:02.122 - info: sbfspot.0 (13724) all done ... 2023-01-18 16:30:02.124 - info: sbfspot.0 (13724) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:30:02.647 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:45:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13742 2023-01-18 16:45:01.138 - info: sbfspot.0 (13742) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:45:01.174 - info: sbfspot.0 (13742) nothing to do, because no daylight ... 2023-01-18 16:45:01.175 - info: sbfspot.0 (13742) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:45:01.698 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:51:01.900 - info: admin.0 (484) Adapter rating updated 2023-01-18 16:51:23.523 - info: admin.0 (484) Request actual repository... 2023-01-18 16:51:23.721 - info: host.196-iobroker-vm-V2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-01-18 16:51:26.156 - info: admin.0 (484) Repository received successfully. 2023-01-18 17:00:00.020 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13775 2023-01-18 17:00:01.149 - info: sbfspot.0 (13775) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 17:00:01.189 - info: sbfspot.0 (13775) nothing to do, because no daylight ... 2023-01-18 17:00:01.191 - info: sbfspot.0 (13775) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 17:00:01.711 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 17:15:00.034 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13795 2023-01-18 17:15:01.118 - info: sbfspot.0 (13795) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 17:15:01.156 - info: sbfspot.0 (13795) nothing to do, because no daylight ... 2023-01-18 17:15:01.157 - info: sbfspot.0 (13795) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 17:15:01.677 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 18:58:04.097 - info: host.196-iobroker-vm-V2 iobroker.js-controller version 4.0.24 js-controller starting 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 hostname: 196-iobroker-vm-V2, node: v16.19.0 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 ip addresses: 192.168.178.231 fe80::bcd2:16ff:fe39:8e82 2023-01-18 18:58:04.728 - info: host.196-iobroker-vm-V2 connected to Objects and States 2023-01-18 18:58:04.753 - info: host.196-iobroker-vm-V2 added notifications configuration of host 2023-01-18 18:58:05.118 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeCurrent" 2023-01-18 18:58:05.119 - info: host.196-iobroker-vm-V2 44 instances found 2023-01-18 18:58:05.149 - info: host.196-iobroker-vm-V2 starting 39 instances 2023-01-18 18:58:05.198 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeNewest" 2023-01-18 18:58:05.250 - info: host.196-iobroker-vm-V2 instance system.adapter.admin.0 started with pid 445 2023-01-18 18:58:05.258 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeNewestNext" 2023-01-18 18:58:05.307 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmCurrent" 2023-01-18 18:58:05.357 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmNewest" 2023-01-18 18:58:05.412 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmNewestNext" 2023-01-18 18:58:05.478 - info: host.196-iobroker-vm-V2 Some obsolete host states deleted. 2023-01-18 18:58:07.415 - error: admin.0 (445) admin.0 already running 2023-01-18 18:58:07.419 - warn: admin.0 (445) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:07.963 - error: host.196-iobroker-vm-V2 instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:07.964 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.admin.0 because enabled 2023-01-18 18:58:09.187 - info: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 started with pid 456 2023-01-18 18:58:10.347 - error: influxdb.0 (456) influxdb.0 already running 2023-01-18 18:58:10.349 - warn: influxdb.0 (456) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:10.898 - error: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:10.898 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.influxdb.0 because enabled 2023-01-18 18:58:13.268 - info: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 started with pid 467 2023-01-18 18:58:16.316 - error: javascript.0 (467) javascript.0 already running 2023-01-18 18:58:16.324 - warn: javascript.0 (467) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:16.897 - error: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:16.898 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.javascript.0 because enabled 2023-01-18 18:58:17.196 - info: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 started with pid 478 2023-01-18 18:58:18.689 - error: telegram.0 (478) telegram.0 already running 2023-01-18 18:58:18.691 - warn: telegram.0 (478) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:19.225 - error: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:19.226 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.telegram.0 because enabled 2023-01-18 18:58:20.254 - info: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 started with pid 489 2023-01-18 18:58:21.208 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 496 2023-01-18 18:58:22.311 - info: telegram.0 (489) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:22.961 - error: alexa2.0 (496) alexa2.0 already running 2023-01-18 18:58:22.964 - warn: alexa2.0 (496) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:23.514 - error: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:23.515 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.alexa2.0 because enabled 2023-01-18 18:58:25.181 - info: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 started with pid 515 2023-01-18 18:58:26.061 - error: hmip.0 (515) hmip.0 already running 2023-01-18 18:58:26.063 - warn: hmip.0 (515) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:26.597 - error: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:26.597 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hmip.0 because enabled 2023-01-18 18:58:29.183 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.0 started with pid 526 2023-01-18 18:58:30.102 - error: hue.0 (526) hue.0 already running 2023-01-18 18:58:30.104 - warn: hue.0 (526) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:30.643 - error: host.196-iobroker-vm-V2 instance system.adapter.hue.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:30.643 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hue.0 because enabled 2023-01-18 18:58:33.181 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.1 started with pid 537 2023-01-18 18:58:34.203 - error: hue.1 (537) hue.1 already running 2023-01-18 18:58:34.205 - warn: hue.1 (537) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:34.758 - error: host.196-iobroker-vm-V2 instance system.adapter.hue.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:34.759 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hue.1 because enabled 2023-01-18 18:58:37.183 - info: host.196-iobroker-vm-V2 instance system.adapter.meross.0 started with pid 548 2023-01-18 18:58:37.995 - info: host.196-iobroker-vm-V2 instance system.adapter.admin.0 started with pid 555 2023-01-18 18:58:38.366 - error: meross.0 (548) meross.0 already running 2023-01-18 18:58:38.368 - warn: meross.0 (548) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:38.902 - error: host.196-iobroker-vm-V2 instance system.adapter.meross.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:38.903 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.meross.0 because enabled 2023-01-18 18:58:39.120 - info: admin.0 (555) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:39.142 - info: admin.0 (555) requesting all states 2023-01-18 18:58:39.142 - info: admin.0 (555) requesting all objects 2023-01-18 18:58:39.590 - info: admin.0 (555) received all objects 2023-01-18 18:58:39.865 - info: admin.0 (555) Request actual repository... 2023-01-18 18:58:39.883 - info: admin.0 (555) http server listening on port 8081 2023-01-18 18:58:39.883 - info: admin.0 (555) Use link "http://localhost:8081" to configure. 2023-01-18 18:58:39.889 - info: admin.0 (555) socket.io server listening on port 8081 2023-01-18 18:58:40.076 - info: host.196-iobroker-vm-V2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-01-18 18:58:41.028 - info: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 started with pid 586 2023-01-18 18:58:41.157 - info: admin.0 (555) Repository received successfully. 2023-01-18 18:58:41.216 - info: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 started with pid 593 2023-01-18 18:58:42.025 - error: mqtt.0 (593) mqtt.0 already running 2023-01-18 18:58:42.027 - warn: mqtt.0 (593) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:42.260 - info: influxdb.0 (586) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.influxdb, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:42.277 - info: influxdb.0 (586) No stored data from last exit found 2023-01-18 18:58:42.278 - info: influxdb.0 (586) Connecting http://192.168.178.198:8086/ ... 2023-01-18 18:58:42.278 - info: influxdb.0 (586) Influx DB Version used: 1.x 2023-01-18 18:58:42.559 - error: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:42.559 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.mqtt.0 because enabled 2023-01-18 18:58:45.182 - info: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 started with pid 612 2023-01-18 18:58:46.194 - error: shelly.0 (612) shelly.0 already running 2023-01-18 18:58:46.195 - warn: shelly.0 (612) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:46.728 - error: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:46.728 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.shelly.0 because enabled 2023-01-18 18:58:46.929 - info: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 started with pid 623 2023-01-18 18:58:48.435 - info: javascript.0 (623) starting. Version 6.1.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:48.773 - info: javascript.0 (623) requesting all states 2023-01-18 18:58:48.773 - info: javascript.0 (623) requesting all objects 2023-01-18 18:58:49.152 - info: javascript.0 (623) received all objects 2023-01-18 18:58:49.185 - info: javascript.0 (623) received all states 2023-01-18 18:58:49.199 - info: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 started with pid 638 2023-01-18 18:58:50.006 - error: sonoff.0 (638) sonoff.0 already running 2023-01-18 18:58:50.008 - warn: sonoff.0 (638) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:50.544 - error: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:50.544 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.sonoff.0 because enabled 2023-01-18 18:58:53.193 - info: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 started with pid 649 2023-01-18 18:58:53.543 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 656 2023-01-18 18:58:54.098 - error: sonos.0 (649) sonos.0 already running 2023-01-18 18:58:54.099 - warn: sonos.0 (649) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:54.634 - error: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:54.634 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.sonos.0 because enabled 2023-01-18 18:58:54.684 - info: alexa2.0 (656) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:54.714 - info: alexa2.0 (656) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2023-01-18 18:58:56.653 - info: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 started with pid 675 2023-01-18 18:58:57.183 - info: host.196-iobroker-vm-V2 instance system.adapter.synology.0 started with pid 682 2023-01-18 18:58:57.911 - info: hmip.0 (675) starting. Version 1.20.0 in /opt/iobroker/node_modules/iobroker.hmip, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:58.393 - error: synology.0 (682) synology.0 already running 2023-01-18 18:58:58.395 - warn: synology.0 (682) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:58.414 - info: alexa2.0 (656) Update cookie in adapter configuration ... restarting ... 2023-01-18 18:58:58.474 - info: host.196-iobroker-vm-V2 stopInstance system.adapter.alexa2.0 (force=false, process=true) 2023-01-18 18:58:58.482 - info: alexa2.0 (656) Got terminate signal TERMINATE_YOURSELF 2023-01-18 18:58:58.489 - info: alexa2.0 (656) terminating 2023-01-18 18:58:58.490 - info: alexa2.0 (656) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 18:58:58.535 - info: host.196-iobroker-vm-V2 stopInstance system.adapter.alexa2.0 send kill signal 2023-01-18 18:58:58.965 - error: host.196-iobroker-vm-V2 instance system.adapter.synology.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:58.965 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.synology.0 because enabled 2023-01-18 18:58:59.046 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 18:59:00.683 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.0 started with pid 701 2023-01-18 18:59:01.225 - info: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 started with pid 708 2023-01-18 18:59:01.618 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 715 2023-01-18 18:59:02.246 - info: hue.0 (701) starting. Version 3.7.1 in /opt/iobroker/node_modules/iobroker.hue, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:03.036 - info: hue.0 (701) skip switch: Daylight.configured 2023-01-18 18:59:03.037 - info: hue.0 (701) skip switch: Daylight.sunriseoffset 2023-01-18 18:59:03.038 - info: hue.0 (701) skip switch: Daylight.sunsetoffset 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.alert 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.sensitivity 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.sensitivitymax 2023-01-18 18:59:03.043 - info: hue.0 (701) skip switch: BWM Gartenhaus.ledindication 2023-01-18 18:59:03.043 - info: hue.0 (701) skip switch: BWM Gartenhaus.usertest 2023-01-18 18:59:03.048 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.alert 2023-01-18 18:59:03.049 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.tholddark 2023-01-18 18:59:03.049 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.tholdoffset 2023-01-18 18:59:03.050 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.ledindication 2023-01-18 18:59:03.050 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.usertest 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.alert 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.ledindication 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.usertest 2023-01-18 18:59:03.094 - info: hue.0 (701) created/updated 11 sensor channels 2023-01-18 18:59:03.464 - info: alexa2.0 (715) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:03.651 - info: hue.0 (701) created/updated 12 light channels 2023-01-18 18:59:03.653 - info: alexa2.0 (715) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2023-01-18 18:59:03.673 - warn: hue.0 (701) channel "Terrasse" already exists, using "Terrasse_Room" for group 4 2023-01-18 18:59:03.682 - info: hue.0 (701) created/updated 8 groups channels 2023-01-18 18:59:03.684 - info: hue.0 (701) created/updated 36 scenes 2023-01-18 18:59:03.685 - info: hue.0 (701) creating/updating bridge device 2023-01-18 18:59:03.796 - info: hmip.0 (675) ws connection opened 2023-01-18 18:59:04.777 - error: zigbee.0 (708) zigbee.0 already running 2023-01-18 18:59:04.779 - warn: zigbee.0 (708) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:04.825 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.1 started with pid 742 2023-01-18 18:59:05.190 - info: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 started with pid 749 2023-01-18 18:59:05.336 - error: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:05.336 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.zigbee.0 because enabled 2023-01-18 18:59:06.817 - error: discovery.0 (749) discovery.0 already running 2023-01-18 18:59:06.818 - warn: discovery.0 (749) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:07.002 - info: hue.1 (742) starting. Version 3.7.1 in /opt/iobroker/node_modules/iobroker.hue, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:07.348 - error: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:07.348 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.discovery.0 because enabled 2023-01-18 18:59:07.658 - info: hmip.0 (675) hmip adapter connected and ready 2023-01-18 18:59:07.809 - info: hue.1 (742) skip switch: Daylight.configured 2023-01-18 18:59:07.809 - info: hue.1 (742) skip switch: Daylight.sunriseoffset 2023-01-18 18:59:07.810 - info: hue.1 (742) skip switch: Daylight.sunsetoffset 2023-01-18 18:59:07.811 - info: hue.1 (742) skip switch: BWM Hausflur oben.alert 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.sensitivity 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.sensitivitymax 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.ledindication 2023-01-18 18:59:07.813 - info: hue.1 (742) skip switch: BWM Hausflur oben.usertest 2023-01-18 18:59:07.814 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.alert 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.tholddark 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.tholdoffset 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.ledindication 2023-01-18 18:59:07.816 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.usertest 2023-01-18 18:59:07.817 - info: hue.1 (742) skip switch: Hue temperature sensor 1.alert 2023-01-18 18:59:07.818 - info: hue.1 (742) skip switch: Hue temperature sensor 1.ledindication 2023-01-18 18:59:07.818 - info: hue.1 (742) skip switch: Hue temperature sensor 1.usertest 2023-01-18 18:59:07.819 - info: hue.1 (742) skip switch: BWM Hausflur unten.alert 2023-01-18 18:59:07.819 - info: hue.1 (742) skip switch: BWM Hausflur unten.sensitivity 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.sensitivitymax 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.ledindication 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.usertest 2023-01-18 18:59:07.821 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.alert 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.tholddark 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.tholdoffset 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.ledindication 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.usertest 2023-01-18 18:59:07.823 - info: hue.1 (742) skip switch: Hue temperature sensor 2.alert 2023-01-18 18:59:07.824 - info: hue.1 (742) skip switch: Hue temperature sensor 2.ledindication 2023-01-18 18:59:07.824 - info: hue.1 (742) skip switch: Hue temperature sensor 2.usertest 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.alert 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.sensitivity 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.sensitivitymax 2023-01-18 18:59:07.826 - info: hue.1 (742) skip switch: BWM Kellertreppe.ledindication 2023-01-18 18:59:07.826 - info: hue.1 (742) skip switch: BWM Kellertreppe.usertest 2023-01-18 18:59:07.827 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.alert 2023-01-18 18:59:07.827 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.tholddark 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.tholdoffset 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.ledindication 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.usertest 2023-01-18 18:59:07.829 - info: hue.1 (742) skip switch: Hue temperature sensor 3.alert 2023-01-18 18:59:07.829 - info: hue.1 (742) skip switch: Hue temperature sensor 3.ledindication 2023-01-18 18:59:07.830 - info: hue.1 (742) skip switch: Hue temperature sensor 3.usertest 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.alert 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.sensitivity 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.sensitivitymax 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.ledindication 2023-01-18 18:59:07.832 - info: hue.1 (742) skip switch: BWM Vorratskeller.usertest 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.alert 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.tholddark 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.tholdoffset 2023-01-18 18:59:07.834 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.ledindication 2023-01-18 18:59:07.834 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.usertest 2023-01-18 18:59:07.835 - info: hue.1 (742) skip switch: Hue temperature sensor 4.alert 2023-01-18 18:59:07.836 - info: hue.1 (742) skip switch: Hue temperature sensor 4.ledindication 2023-01-18 18:59:07.836 - info: hue.1 (742) skip switch: Hue temperature sensor 4.usertest 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.alert 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.sensitivity 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.sensitivitymax 2023-01-18 18:59:07.838 - info: hue.1 (742) skip switch: BWM Waschkeller.ledindication 2023-01-18 18:59:07.838 - info: hue.1 (742) skip switch: BWM Waschkeller.usertest 2023-01-18 18:59:07.839 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.alert 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.tholddark 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.tholdoffset 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.ledindication 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.usertest 2023-01-18 18:59:07.844 - info: hue.1 (742) skip switch: Hue temperature sensor 5.alert 2023-01-18 18:59:07.845 - info: hue.1 (742) skip switch: Hue temperature sensor 5.ledindication 2023-01-18 18:59:07.845 - info: hue.1 (742) skip switch: Hue temperature sensor 5.usertest 2023-01-18 18:59:07.846 - info: hue.1 (742) skip switch: BWM Haustür.alert 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.sensitivity 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.sensitivitymax 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.ledindication 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.usertest 2023-01-18 18:59:07.848 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.alert 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.tholddark 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.tholdoffset 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.ledindication 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.usertest 2023-01-18 18:59:07.850 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.alert 2023-01-18 18:59:07.851 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.ledindication 2023-01-18 18:59:07.851 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.usertest 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.alert 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.sensitivity 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.sensitivitymax 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.ledindication 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.usertest 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.alert 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.tholddark 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.tholdoffset 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.ledindication 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.usertest 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.alert 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.ledindication 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.usertest 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.alert 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.sensitivity 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.sensitivitymax 2023-01-18 18:59:07.859 - info: hue.1 (742) skip switch: BWM Flur EG.ledindication 2023-01-18 18:59:07.859 - info: hue.1 (742) skip switch: BWM Flur EG.usertest 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.alert 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.tholddark 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.tholdoffset 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.ledindication 2023-01-18 18:59:07.861 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.usertest 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.alert 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.ledindication 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.usertest 2023-01-18 18:59:07.862 - info: hue.1 (742) created/updated 25 sensor channels 2023-01-18 18:59:08.082 - info: alexa2.0 (715) Initialize all Device states ... 2023-01-18 18:59:08.212 - info: hue.1 (742) created/updated 9 light channels 2023-01-18 18:59:08.215 - warn: hue.1 (742) channel "Kellergang" already exists, using "Kellergang_Room" for group 2 2023-01-18 18:59:08.216 - warn: hue.1 (742) channel "Haustür" already exists, using "Haustür_Room" for group 3 2023-01-18 18:59:08.217 - warn: hue.1 (742) channel "Garagentür" already exists, using "Garagentür_Room" for group 4 2023-01-18 18:59:08.219 - warn: hue.1 (742) channel "Gartentür" already exists, using "Gartentür_Room" for group 5 2023-01-18 18:59:08.224 - info: hue.1 (742) created/updated 9 groups channels 2023-01-18 18:59:08.226 - info: hue.1 (742) created/updated 26 scenes 2023-01-18 18:59:08.227 - info: hue.1 (742) creating/updating bridge device 2023-01-18 18:59:08.930 - info: host.196-iobroker-vm-V2 instance system.adapter.meross.0 started with pid 768 2023-01-18 18:59:09.203 - info: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 started with pid 775 2023-01-18 18:59:11.437 - error: backitup.0 (775) backitup.0 already running 2023-01-18 18:59:11.439 - warn: backitup.0 (775) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:11.561 - info: meross.0 (768) starting. Version 1.14.0 in /opt/iobroker/node_modules/iobroker.meross, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:11.975 - error: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:11.976 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.backitup.0 because enabled 2023-01-18 18:59:12.315 - info: meross.0 (768) Device 2106164874521890852648e1e97294bd initialized 2023-01-18 18:59:12.563 - info: meross.0 (768) Device: 2106164874521890852648e1e97294bd connected 2023-01-18 18:59:12.585 - info: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 started with pid 794 2023-01-18 18:59:12.736 - info: meross.0 (768) Devices initialized 2023-01-18 18:59:13.287 - info: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 started with pid 801 2023-01-18 18:59:15.646 - info: mqtt.0 (794) starting. Version 4.0.7 in /opt/iobroker/node_modules/iobroker.mqtt, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:15.984 - info: mqtt.0 (794) Starting MQTT server on 0.0.0.0:1884 2023-01-18 18:59:16.219 - error: cloud.0 (801) cloud.0 already running 2023-01-18 18:59:16.221 - warn: cloud.0 (801) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:16.768 - error: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:16.768 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.cloud.0 because enabled 2023-01-18 18:59:16.825 - info: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 started with pid 820 2023-01-18 18:59:17.186 - info: host.196-iobroker-vm-V2 instance system.adapter.web.0 started with pid 827 2023-01-18 18:59:18.576 - info: shelly.0 (820) starting. Version 6.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:18.681 - info: shelly.0 (820) Starting in MQTT mode. Listening on 0.0.0.0:1882 2023-01-18 18:59:18.707 - error: web.0 (827) web.0 already running 2023-01-18 18:59:18.709 - warn: web.0 (827) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:19.250 - error: host.196-iobroker-vm-V2 instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:19.250 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.web.0 because enabled 2023-01-18 18:59:20.568 - info: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 started with pid 846 2023-01-18 18:59:21.196 - info: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 started with pid 853 2023-01-18 18:59:21.724 - info: sonoff.0 (846) starting. Version 2.5.1 in /opt/iobroker/node_modules/iobroker.sonoff, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:21.759 - info: sonoff.0 (846) Starting MQTT authenticated server on port 1883 2023-01-18 18:59:22.351 - error: go-e.0 (853) go-e.0 already running 2023-01-18 18:59:22.353 - warn: go-e.0 (853) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:22.885 - error: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:22.886 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.go-e.0 because enabled 2023-01-18 18:59:24.656 - info: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 started with pid 872 2023-01-18 18:59:25.191 - info: host.196-iobroker-vm-V2 instance system.adapter.info.0 started with pid 879 2023-01-18 18:59:25.730 - info: sonos.0 (872) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.sonos, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:26.974 - error: info.0 (879) info.0 already running 2023-01-18 18:59:26.978 - warn: info.0 (879) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:27.514 - error: host.196-iobroker-vm-V2 instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:27.515 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.info.0 because enabled 2023-01-18 18:59:28.990 - info: host.196-iobroker-vm-V2 instance system.adapter.synology.0 started with pid 910 2023-01-18 18:59:29.191 - info: host.196-iobroker-vm-V2 instance system.adapter.logparser.0 started with pid 917 2023-01-18 18:59:30.322 - error: logparser.0 (917) logparser.0 already running 2023-01-18 18:59:30.324 - warn: logparser.0 (917) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:30.876 - error: host.196-iobroker-vm-V2 instance system.adapter.logparser.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:30.877 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.logparser.0 because enabled 2023-01-18 18:59:30.913 - info: synology.0 (910) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.synology, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:30.947 - info: synology.0 (910) Connecting to Synology 192.168.178.107:5001 2023-01-18 18:59:33.540 - info: synology.0 (910) DSM 7 2023-01-18 18:59:33.541 - info: synology.0 (910) DSM 7 detected, set all to true 2023-01-18 18:59:33.986 - info: vis.0 (936) starting. Version 1.4.15 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:34.011 - error: vis.0 (936) No license found for vis. Please get one on https://iobroker.net ! 2023-01-18 18:59:35.328 - info: vis.0 (936) Terminated (NO_ERROR): Without reason 2023-01-18 18:59:35.360 - info: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 started with pid 951 2023-01-18 18:59:35.887 - info: host.196-iobroker-vm-V2 instance system.adapter.vis.0 terminated while should be started once 2023-01-18 18:59:37.327 - info: host.196-iobroker-vm-V2 instance system.adapter.vis-inventwo.0 started with pid 962 2023-01-18 18:59:37.426 - info: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 started with pid 969 2023-01-18 18:59:37.586 - info: zigbee.0 (951) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:37.902 - info: zigbee.0 (951) Starting Zigbee npm ... 2023-01-18 18:59:39.290 - info: zigbee.0 (951) Installed Version: iobroker.zigbee@1.8.10 2023-01-18 18:59:40.212 - error: vis-inventwo.0 (962) vis-inventwo.0 already running 2023-01-18 18:59:40.214 - warn: vis-inventwo.0 (962) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:40.672 - info: discovery.0 (969) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:40.736 - info: zigbee.0 (951) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}} 2023-01-18 18:59:40.746 - info: zigbee.0 (951) Unable to disable LED, unsupported function. 2023-01-18 18:59:40.757 - info: zigbee.0 (951) --> transmitPower : high+ 2023-01-18 18:59:40.775 - error: host.196-iobroker-vm-V2 instance system.adapter.vis-inventwo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:40.776 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.vis-inventwo.0 because enabled 2023-01-18 18:59:40.776 - info: zigbee.0 (951) Currently no devices. 2023-01-18 18:59:40.777 - info: zigbee.0 (951) Zigbee started 2023-01-18 18:59:41.182 - info: host.196-iobroker-vm-V2 instance system.adapter.proxmox.0 started with pid 992 2023-01-18 18:59:42.012 - info: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 started with pid 999 2023-01-18 18:59:42.283 - error: proxmox.0 (992) proxmox.0 already running 2023-01-18 18:59:42.285 - warn: proxmox.0 (992) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:42.852 - error: host.196-iobroker-vm-V2 instance system.adapter.proxmox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:42.852 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.proxmox.0 because enabled 2023-01-18 18:59:43.404 - info: backitup.0 (999) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:43.527 - info: backitup.0 (999) [iobroker] backup was activated at every 1 day(s) 2023-01-18 18:59:45.188 - info: host.196-iobroker-vm-V2 instance scheduled system.adapter.sbfspot.0 */15 * * * * 2023-01-18 18:59:46.794 - info: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 started with pid 1018 2023-01-18 18:59:47.813 - info: cloud.0 (1018) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.cloud, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:47.847 - info: cloud.0 (1018) Connecting with https://iobroker.pro:10555 with "@pro_draci009@gmail.com_646bef80-7f06-11ed-85c5-e76fc4fe39c4" 2023-01-18 18:59:47.983 - info: cloud.0 (1018) Trying to connect as system.user.admin to cloud 2023-01-18 18:59:48.608 - info: cloud.0 (1018) Adapter redirected temporally to "https://iobroker.pro:10556" in 30 seconds. Reason: command from server 2023-01-18 18:59:48.610 - info: cloud.0 (1018) Connection changed: disconnect 2023-01-18 18:59:49.188 - info: host.196-iobroker-vm-V2 instance system.adapter.tankerkoenig.0 started with pid 1033 2023-01-18 18:59:49.285 - info: host.196-iobroker-vm-V2 instance system.adapter.web.0 started with pid 1040 2023-01-18 18:59:50.213 - error: tankerkoenig.0 (1033) tankerkoenig.0 already running 2023-01-18 18:59:50.215 - warn: tankerkoenig.0 (1033) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:50.451 - info: web.0 (1040) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:50.635 - info: web.0 (1040) socket.io server listening on port 8082 2023-01-18 18:59:50.637 - info: web.0 (1040) http server listening on port 8082 2023-01-18 18:59:50.745 - error: host.196-iobroker-vm-V2 instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:50.745 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.tankerkoenig.0 because enabled 2023-01-18 18:59:52.909 - info: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 started with pid 1059 2023-01-18 18:59:53.188 - info: host.196-iobroker-vm-V2 instance system.adapter.wled.0 started with pid 1066 2023-01-18 18:59:54.666 - error: wled.0 (1066) wled.0 already running 2023-01-18 18:59:54.669 - warn: wled.0 (1066) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:55.117 - info: go-e.0 (1059) starting. Version 1.0.23 in /opt/iobroker/node_modules/iobroker.go-e, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:55.134 - info: go-e.0 (1059) Server: 192.168.178.206 2023-01-18 18:59:55.135 - info: go-e.0 (1059) Intervall: 60 2023-01-18 18:59:55.135 - warn: go-e.0 (1059) Sentry enabled. You can switch it off in settings of the adapter. 2023-01-18 18:59:55.232 - error: host.196-iobroker-vm-V2 instance system.adapter.wled.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:55.232 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.wled.0 because enabled 2023-01-18 18:59:57.170 - info: host.196-iobroker-vm-V2 instance system.adapter.yahka.0 started with pid 1085 2023-01-18 18:59:57.551 - info: host.196-iobroker-vm-V2 instance system.adapter.info.0 started with pid 1092 2023-01-18 18:59:58.580 - error: yahka.0 (1085) yahka.0 already running 2023-01-18 18:59:58.582 - warn: yahka.0 (1085) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:59.127 - error: host.196-iobroker-vm-V2 instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:59.127 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.yahka.0 because enabled 2023-01-18 18:59:59.739 - info: info.0 (1092) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:59.791 - info: info.0 (1092) Reading/updating systemdata. -
ok, here we go. Gehen nur 100.000 Zeichen.
Wie gesagt, einige Adapter sind noch nicht fertig konfiguriert.2023-01-18 08:00:00.033 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13044 2023-01-18 08:00:01.413 - info: sbfspot.0 (13044) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:00:01.543 - info: sbfspot.0 (13044) start with mySQL 2023-01-18 08:00:01.590 - info: sbfspot.0 (13044) got data from with ID 0 2023-01-18 08:00:02.250 - info: sbfspot.0 (13044) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:00:02.771 - info: sbfspot.0 (13044) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:00:03.224 - info: sbfspot.0 (13044) all done ... 2023-01-18 08:00:03.225 - info: sbfspot.0 (13044) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:00:03.741 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:07:03.460 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:07:06.719 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:07:08.737 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:00.590 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:02.603 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:05.119 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:18.130 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:22.100 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:10:24.108 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:15:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13064 2023-01-18 08:15:01.474 - info: sbfspot.0 (13064) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:15:01.618 - info: sbfspot.0 (13064) start with mySQL 2023-01-18 08:15:01.665 - info: sbfspot.0 (13064) got data from with ID 0 2023-01-18 08:15:01.948 - info: sbfspot.0 (13064) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:15:02.280 - info: sbfspot.0 (13064) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:15:02.565 - info: sbfspot.0 (13064) all done ... 2023-01-18 08:15:02.567 - info: sbfspot.0 (13064) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:15:03.103 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:30:00.038 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13087 2023-01-18 08:30:01.459 - info: sbfspot.0 (13087) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:30:01.595 - info: sbfspot.0 (13087) start with mySQL 2023-01-18 08:30:01.634 - info: sbfspot.0 (13087) got data from with ID 0 2023-01-18 08:30:02.040 - info: sbfspot.0 (13087) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:30:02.484 - info: sbfspot.0 (13087) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:30:02.786 - info: sbfspot.0 (13087) all done ... 2023-01-18 08:30:02.788 - info: sbfspot.0 (13087) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:30:03.309 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:45:00.028 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13106 2023-01-18 08:45:01.407 - info: sbfspot.0 (13106) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 08:45:01.565 - info: sbfspot.0 (13106) start with mySQL 2023-01-18 08:45:01.614 - info: sbfspot.0 (13106) got data from with ID 0 2023-01-18 08:45:01.922 - info: sbfspot.0 (13106) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 08:45:02.280 - info: sbfspot.0 (13106) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 08:45:02.615 - info: sbfspot.0 (13106) all done ... 2023-01-18 08:45:02.617 - info: sbfspot.0 (13106) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 08:45:03.146 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 08:50:51.822 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:50:59.143 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 08:51:01.156 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:00:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13126 2023-01-18 09:00:01.502 - info: sbfspot.0 (13126) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:00:01.642 - info: sbfspot.0 (13126) start with mySQL 2023-01-18 09:00:01.691 - info: sbfspot.0 (13126) got data from with ID 0 2023-01-18 09:00:02.019 - info: sbfspot.0 (13126) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:00:02.340 - info: sbfspot.0 (13126) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:00:02.664 - info: sbfspot.0 (13126) all done ... 2023-01-18 09:00:02.665 - info: sbfspot.0 (13126) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:00:03.209 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:15:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13143 2023-01-18 09:15:01.166 - info: sbfspot.0 (13143) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:15:01.277 - info: sbfspot.0 (13143) start with mySQL 2023-01-18 09:15:01.313 - info: sbfspot.0 (13143) got data from with ID 0 2023-01-18 09:15:01.551 - info: sbfspot.0 (13143) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:15:01.810 - info: sbfspot.0 (13143) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:15:02.057 - info: sbfspot.0 (13143) all done ... 2023-01-18 09:15:02.058 - info: sbfspot.0 (13143) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:15:02.578 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:17:56.764 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:17:56.814 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 09:17:56.815 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 09:17:56.900 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 09:17:56.900 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 09:17:56.944 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 09:17:56.990 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 09:17:56.991 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 09:17:57.036 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 09:17:57.037 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 09:17:57.080 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 09:17:59.263 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 09:17:59.310 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 09:17:59.311 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 09:17:59.395 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 09:17:59.396 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 09:17:59.440 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 09:17:59.486 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 09:17:59.487 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 09:17:59.490 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 09:17:59.532 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 09:17:59.533 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 09:30:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13167 2023-01-18 09:30:01.093 - info: sbfspot.0 (13167) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:30:01.202 - info: sbfspot.0 (13167) start with mySQL 2023-01-18 09:30:01.246 - info: sbfspot.0 (13167) got data from with ID 0 2023-01-18 09:30:01.503 - info: sbfspot.0 (13167) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:30:01.768 - info: sbfspot.0 (13167) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:30:02.018 - info: sbfspot.0 (13167) all done ... 2023-01-18 09:30:02.019 - info: sbfspot.0 (13167) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:30:02.537 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 09:45:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13185 2023-01-18 09:45:01.079 - info: sbfspot.0 (13185) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 09:45:01.204 - info: sbfspot.0 (13185) start with mySQL 2023-01-18 09:45:01.260 - info: sbfspot.0 (13185) got data from with ID 0 2023-01-18 09:45:01.526 - info: sbfspot.0 (13185) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 09:45:01.788 - info: sbfspot.0 (13185) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 09:45:02.051 - info: sbfspot.0 (13185) all done ... 2023-01-18 09:45:02.052 - info: sbfspot.0 (13185) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 09:45:02.571 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:00:00.045 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13204 2023-01-18 10:00:01.194 - info: sbfspot.0 (13204) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:00:01.302 - info: sbfspot.0 (13204) start with mySQL 2023-01-18 10:00:01.334 - info: sbfspot.0 (13204) got data from with ID 0 2023-01-18 10:00:01.567 - info: sbfspot.0 (13204) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:00:01.798 - info: sbfspot.0 (13204) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:00:02.059 - info: sbfspot.0 (13204) all done ... 2023-01-18 10:00:02.060 - info: sbfspot.0 (13204) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:00:02.579 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:15:00.022 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13222 2023-01-18 10:15:01.121 - info: sbfspot.0 (13222) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:15:01.265 - info: sbfspot.0 (13222) start with mySQL 2023-01-18 10:15:01.313 - info: sbfspot.0 (13222) got data from with ID 0 2023-01-18 10:15:01.547 - info: sbfspot.0 (13222) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:15:01.765 - info: sbfspot.0 (13222) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:15:01.982 - info: sbfspot.0 (13222) all done ... 2023-01-18 10:15:01.984 - info: sbfspot.0 (13222) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:15:02.505 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:30:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13247 2023-01-18 10:30:01.154 - info: sbfspot.0 (13247) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:30:01.266 - info: sbfspot.0 (13247) start with mySQL 2023-01-18 10:30:01.310 - info: sbfspot.0 (13247) got data from with ID 0 2023-01-18 10:30:01.567 - info: sbfspot.0 (13247) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:30:01.815 - info: sbfspot.0 (13247) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:30:02.061 - info: sbfspot.0 (13247) all done ... 2023-01-18 10:30:02.062 - info: sbfspot.0 (13247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:30:02.586 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 10:45:00.019 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13266 2023-01-18 10:45:01.085 - info: sbfspot.0 (13266) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 10:45:01.189 - info: sbfspot.0 (13266) start with mySQL 2023-01-18 10:45:01.229 - info: sbfspot.0 (13266) got data from with ID 0 2023-01-18 10:45:01.452 - info: sbfspot.0 (13266) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 10:45:01.685 - info: sbfspot.0 (13266) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 10:45:01.932 - info: sbfspot.0 (13266) all done ... 2023-01-18 10:45:01.933 - info: sbfspot.0 (13266) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 10:45:02.453 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13285 2023-01-18 11:00:01.187 - info: sbfspot.0 (13285) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:00:01.291 - info: sbfspot.0 (13285) start with mySQL 2023-01-18 11:00:01.329 - info: sbfspot.0 (13285) got data from with ID 0 2023-01-18 11:00:01.571 - info: sbfspot.0 (13285) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:00:01.819 - info: sbfspot.0 (13285) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:00:02.038 - info: sbfspot.0 (13285) all done ... 2023-01-18 11:00:02.039 - info: sbfspot.0 (13285) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:00:02.561 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:15:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13303 2023-01-18 11:15:01.087 - info: sbfspot.0 (13303) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:15:01.193 - info: sbfspot.0 (13303) start with mySQL 2023-01-18 11:15:01.229 - info: sbfspot.0 (13303) got data from with ID 0 2023-01-18 11:15:01.487 - info: sbfspot.0 (13303) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:15:01.738 - info: sbfspot.0 (13303) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:15:01.971 - info: sbfspot.0 (13303) all done ... 2023-01-18 11:15:01.972 - info: sbfspot.0 (13303) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:15:02.491 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:30:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13326 2023-01-18 11:30:01.209 - info: sbfspot.0 (13326) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:30:01.318 - info: sbfspot.0 (13326) start with mySQL 2023-01-18 11:30:01.350 - info: sbfspot.0 (13326) got data from with ID 0 2023-01-18 11:30:01.587 - info: sbfspot.0 (13326) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:30:01.831 - info: sbfspot.0 (13326) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:30:02.044 - info: sbfspot.0 (13326) all done ... 2023-01-18 11:30:02.045 - info: sbfspot.0 (13326) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:30:02.565 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 11:45:00.022 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13345 2023-01-18 11:45:01.140 - info: sbfspot.0 (13345) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 11:45:01.242 - info: sbfspot.0 (13345) start with mySQL 2023-01-18 11:45:01.284 - info: sbfspot.0 (13345) got data from with ID 0 2023-01-18 11:45:01.500 - info: sbfspot.0 (13345) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 11:45:01.729 - info: sbfspot.0 (13345) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 11:45:01.985 - info: sbfspot.0 (13345) all done ... 2023-01-18 11:45:01.986 - info: sbfspot.0 (13345) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 11:45:02.505 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:00:00.035 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13364 2023-01-18 12:00:01.160 - info: sbfspot.0 (13364) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:00:01.269 - info: sbfspot.0 (13364) start with mySQL 2023-01-18 12:00:01.303 - info: sbfspot.0 (13364) got data from with ID 0 2023-01-18 12:00:01.559 - info: sbfspot.0 (13364) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:00:01.834 - info: sbfspot.0 (13364) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:00:02.076 - info: sbfspot.0 (13364) all done ... 2023-01-18 12:00:02.077 - info: sbfspot.0 (13364) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:00:02.599 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:15:00.016 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13384 2023-01-18 12:15:01.144 - info: sbfspot.0 (13384) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:15:01.255 - info: sbfspot.0 (13384) start with mySQL 2023-01-18 12:15:01.289 - info: sbfspot.0 (13384) got data from with ID 0 2023-01-18 12:15:01.519 - info: sbfspot.0 (13384) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:15:01.745 - info: sbfspot.0 (13384) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:15:01.968 - info: sbfspot.0 (13384) all done ... 2023-01-18 12:15:01.969 - info: sbfspot.0 (13384) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:15:02.497 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:30:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13406 2023-01-18 12:30:01.140 - info: sbfspot.0 (13406) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:30:01.244 - info: sbfspot.0 (13406) start with mySQL 2023-01-18 12:30:01.287 - info: sbfspot.0 (13406) got data from with ID 0 2023-01-18 12:30:01.506 - info: sbfspot.0 (13406) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:30:01.726 - info: sbfspot.0 (13406) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:30:01.961 - info: sbfspot.0 (13406) all done ... 2023-01-18 12:30:01.962 - info: sbfspot.0 (13406) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:30:02.482 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 12:45:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13425 2023-01-18 12:45:01.148 - info: sbfspot.0 (13425) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 12:45:01.248 - info: sbfspot.0 (13425) start with mySQL 2023-01-18 12:45:01.290 - info: sbfspot.0 (13425) got data from with ID 0 2023-01-18 12:45:01.535 - info: sbfspot.0 (13425) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 12:45:01.787 - info: sbfspot.0 (13425) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 12:45:02.027 - info: sbfspot.0 (13425) all done ... 2023-01-18 12:45:02.028 - info: sbfspot.0 (13425) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 12:45:02.546 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13444 2023-01-18 13:00:01.070 - info: sbfspot.0 (13444) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:00:01.177 - info: sbfspot.0 (13444) start with mySQL 2023-01-18 13:00:01.209 - info: sbfspot.0 (13444) got data from with ID 0 2023-01-18 13:00:01.445 - info: sbfspot.0 (13444) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:00:01.679 - info: sbfspot.0 (13444) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:00:01.945 - info: sbfspot.0 (13444) all done ... 2023-01-18 13:00:01.946 - info: sbfspot.0 (13444) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:00:02.465 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:09:09.145 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 13:09:09.196 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 13:09:09.197 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 13:09:09.285 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 13:09:09.286 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 13:09:09.330 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 13:09:09.379 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 13:09:09.380 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 13:09:09.424 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 13:09:09.427 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 13:09:09.429 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 13:15:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13462 2023-01-18 13:15:01.146 - info: sbfspot.0 (13462) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:15:01.271 - info: sbfspot.0 (13462) start with mySQL 2023-01-18 13:15:01.303 - info: sbfspot.0 (13462) got data from with ID 0 2023-01-18 13:15:01.522 - info: sbfspot.0 (13462) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:15:01.762 - info: sbfspot.0 (13462) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:15:02.029 - info: sbfspot.0 (13462) all done ... 2023-01-18 13:15:02.030 - info: sbfspot.0 (13462) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:15:02.549 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:30:00.028 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13484 2023-01-18 13:30:01.118 - info: sbfspot.0 (13484) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:30:01.237 - info: sbfspot.0 (13484) start with mySQL 2023-01-18 13:30:01.280 - info: sbfspot.0 (13484) got data from with ID 0 2023-01-18 13:30:01.560 - info: sbfspot.0 (13484) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:30:01.828 - info: sbfspot.0 (13484) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:30:02.062 - info: sbfspot.0 (13484) all done ... 2023-01-18 13:30:02.063 - info: sbfspot.0 (13484) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:30:02.580 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 13:45:00.025 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13503 2023-01-18 13:45:01.094 - info: sbfspot.0 (13503) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 13:45:01.213 - info: sbfspot.0 (13503) start with mySQL 2023-01-18 13:45:01.246 - info: sbfspot.0 (13503) got data from with ID 0 2023-01-18 13:45:01.530 - info: sbfspot.0 (13503) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 13:45:01.810 - info: sbfspot.0 (13503) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 13:45:02.062 - info: sbfspot.0 (13503) all done ... 2023-01-18 13:45:02.063 - info: sbfspot.0 (13503) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 13:45:02.581 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:00:00.018 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13522 2023-01-18 14:00:01.149 - info: sbfspot.0 (13522) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:00:01.261 - info: sbfspot.0 (13522) start with mySQL 2023-01-18 14:00:01.296 - info: sbfspot.0 (13522) got data from with ID 0 2023-01-18 14:00:01.544 - info: sbfspot.0 (13522) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:00:01.787 - info: sbfspot.0 (13522) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:00:02.050 - info: sbfspot.0 (13522) all done ... 2023-01-18 14:00:02.051 - info: sbfspot.0 (13522) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:00:02.574 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:15:00.025 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13541 2023-01-18 14:15:01.113 - info: sbfspot.0 (13541) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:15:01.216 - info: sbfspot.0 (13541) start with mySQL 2023-01-18 14:15:01.254 - info: sbfspot.0 (13541) got data from with ID 0 2023-01-18 14:15:01.493 - info: sbfspot.0 (13541) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:15:01.715 - info: sbfspot.0 (13541) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:15:01.976 - info: sbfspot.0 (13541) all done ... 2023-01-18 14:15:01.977 - info: sbfspot.0 (13541) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:15:02.497 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:30:00.027 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13565 2023-01-18 14:30:01.127 - info: sbfspot.0 (13565) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:30:01.231 - info: sbfspot.0 (13565) start with mySQL 2023-01-18 14:30:01.271 - info: sbfspot.0 (13565) got data from with ID 0 2023-01-18 14:30:01.550 - info: sbfspot.0 (13565) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:30:01.800 - info: sbfspot.0 (13565) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:30:02.037 - info: sbfspot.0 (13565) all done ... 2023-01-18 14:30:02.038 - info: sbfspot.0 (13565) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:30:02.558 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 14:45:00.021 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13584 2023-01-18 14:45:01.130 - info: sbfspot.0 (13584) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 14:45:01.233 - info: sbfspot.0 (13584) start with mySQL 2023-01-18 14:45:01.273 - info: sbfspot.0 (13584) got data from with ID 0 2023-01-18 14:45:01.491 - info: sbfspot.0 (13584) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 14:45:01.739 - info: sbfspot.0 (13584) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 14:45:01.965 - info: sbfspot.0 (13584) all done ... 2023-01-18 14:45:01.966 - info: sbfspot.0 (13584) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 14:45:02.484 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:00:00.024 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13603 2023-01-18 15:00:01.144 - info: sbfspot.0 (13603) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:00:01.249 - info: sbfspot.0 (13603) start with mySQL 2023-01-18 15:00:01.283 - info: sbfspot.0 (13603) got data from with ID 0 2023-01-18 15:00:01.554 - info: sbfspot.0 (13603) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:00:01.804 - info: sbfspot.0 (13603) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:00:02.025 - info: sbfspot.0 (13603) all done ... 2023-01-18 15:00:02.026 - info: sbfspot.0 (13603) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:00:02.544 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:08:32.588 - warn: wled.0 (11253) State attribute definition missing for : liveseg with value : -1 2023-01-18 15:08:32.634 - warn: wled.0 (11253) State attribute definition missing for : cpalcount with value : 0 2023-01-18 15:08:32.635 - warn: wled.0 (11253) State attribute definition missing for : 0 with value : 0 2023-01-18 15:08:32.717 - warn: wled.0 (11253) State attribute definition missing for : c1 with value : 128 2023-01-18 15:08:32.719 - warn: wled.0 (11253) State attribute definition missing for : c2 with value : 128 2023-01-18 15:08:32.764 - warn: wled.0 (11253) State attribute definition missing for : c3 with value : 16 2023-01-18 15:08:32.810 - warn: wled.0 (11253) State attribute definition missing for : o1 with value : false 2023-01-18 15:08:32.811 - warn: wled.0 (11253) State attribute definition missing for : o2 with value : false 2023-01-18 15:08:32.856 - warn: wled.0 (11253) State attribute definition missing for : o3 with value : false 2023-01-18 15:08:32.857 - warn: wled.0 (11253) State attribute definition missing for : si with value : 0 2023-01-18 15:08:32.901 - warn: wled.0 (11253) State attribute definition missing for : m12 with value : 0 2023-01-18 15:15:00.026 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13622 2023-01-18 15:15:01.146 - info: sbfspot.0 (13622) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:15:01.254 - info: sbfspot.0 (13622) start with mySQL 2023-01-18 15:15:01.295 - info: sbfspot.0 (13622) got data from with ID 0 2023-01-18 15:15:01.581 - info: sbfspot.0 (13622) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:15:01.805 - info: sbfspot.0 (13622) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:15:02.024 - info: sbfspot.0 (13622) all done ... 2023-01-18 15:15:02.025 - info: sbfspot.0 (13622) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:15:02.544 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:30:00.019 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13644 2023-01-18 15:30:01.186 - info: sbfspot.0 (13644) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:30:01.302 - info: sbfspot.0 (13644) start with mySQL 2023-01-18 15:30:01.350 - info: sbfspot.0 (13644) got data from with ID 0 2023-01-18 15:30:01.589 - info: sbfspot.0 (13644) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:30:01.844 - info: sbfspot.0 (13644) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:30:02.095 - info: sbfspot.0 (13644) all done ... 2023-01-18 15:30:02.096 - info: sbfspot.0 (13644) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:30:02.618 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 15:34:21.089 - warn: hmip.0 (7979) ws connection closed (0) - code: 1006 - reason: 2023-01-18 15:34:31.156 - warn: hmip.0 (7979) ws connection error (0): Error: connect ECONNREFUSED 62.113.249.105:8888 2023-01-18 15:34:31.156 - warn: hmip.0 (7979) ws connection closed (2) - code: 1006 - reason: 2023-01-18 15:34:42.457 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:34:42.543 - warn: hmip.0 (7979) ws connection closed (3) - code: 1000 - reason: 2023-01-18 15:34:53.807 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:34:53.830 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:05.089 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:05.114 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:16.482 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:16.519 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:27.845 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:27.886 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:39.393 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:39.507 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:35:50.413 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:35:50.449 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:01.347 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:01.383 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:12.284 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:12.310 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:23.160 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:23.194 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:34.012 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:34.041 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:44.803 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:44.824 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:36:55.562 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:36:55.615 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:06.260 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:06.290 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:16.847 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:16.921 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:27.525 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:27.553 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:38.103 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:38.127 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:48.683 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:48.717 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:37:59.111 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:37:59.153 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:09.571 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:09.601 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:20.572 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:20.645 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:30.809 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:30.840 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:40.957 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:41.003 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:38:51.296 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:38:51.338 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:01.772 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:01.808 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:12.196 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:12.224 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:22.582 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:22.617 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:33.411 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:33.567 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:43.701 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:43.727 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:39:53.847 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:39:53.872 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:04.128 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:40:04.197 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:14.308 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:40:14.329 - warn: hmip.0 (7979) ws connection closed (1) - code: 1000 - reason: 2023-01-18 15:40:24.462 - info: hmip.0 (7979) ws connection opened 2023-01-18 15:45:00.029 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13663 2023-01-18 15:45:01.177 - info: sbfspot.0 (13663) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 15:45:01.282 - info: sbfspot.0 (13663) start with mySQL 2023-01-18 15:45:01.322 - info: sbfspot.0 (13663) got data from with ID 0 2023-01-18 15:45:01.592 - info: sbfspot.0 (13663) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 15:45:01.870 - info: sbfspot.0 (13663) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 15:45:02.111 - info: sbfspot.0 (13663) all done ... 2023-01-18 15:45:02.112 - info: sbfspot.0 (13663) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 15:45:02.630 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:00:00.037 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13683 2023-01-18 16:00:01.211 - info: sbfspot.0 (13683) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:00:01.356 - info: sbfspot.0 (13683) start with mySQL 2023-01-18 16:00:01.398 - info: sbfspot.0 (13683) got data from with ID 0 2023-01-18 16:00:01.638 - info: sbfspot.0 (13683) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:00:01.864 - info: sbfspot.0 (13683) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:00:02.091 - info: sbfspot.0 (13683) all done ... 2023-01-18 16:00:02.092 - info: sbfspot.0 (13683) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:00:02.612 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:15:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13701 2023-01-18 16:15:01.230 - info: sbfspot.0 (13701) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:15:01.339 - info: sbfspot.0 (13701) start with mySQL 2023-01-18 16:15:01.372 - info: sbfspot.0 (13701) got data from with ID 0 2023-01-18 16:15:01.620 - info: sbfspot.0 (13701) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:15:01.851 - info: sbfspot.0 (13701) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:15:02.081 - info: sbfspot.0 (13701) all done ... 2023-01-18 16:15:02.082 - info: sbfspot.0 (13701) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:15:02.603 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:30:00.026 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13724 2023-01-18 16:30:01.197 - info: sbfspot.0 (13724) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:30:01.306 - info: sbfspot.0 (13724) start with mySQL 2023-01-18 16:30:01.342 - info: sbfspot.0 (13724) got data from with ID 0 2023-01-18 16:30:01.603 - info: sbfspot.0 (13724) got data from SB 4000TL-20 with ID 2100101691 2023-01-18 16:30:01.883 - info: sbfspot.0 (13724) got data from SB 4000TL-20 with ID 2100111075 2023-01-18 16:30:02.122 - info: sbfspot.0 (13724) all done ... 2023-01-18 16:30:02.124 - info: sbfspot.0 (13724) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:30:02.647 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:45:00.023 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13742 2023-01-18 16:45:01.138 - info: sbfspot.0 (13742) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 16:45:01.174 - info: sbfspot.0 (13742) nothing to do, because no daylight ... 2023-01-18 16:45:01.175 - info: sbfspot.0 (13742) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 16:45:01.698 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 16:51:01.900 - info: admin.0 (484) Adapter rating updated 2023-01-18 16:51:23.523 - info: admin.0 (484) Request actual repository... 2023-01-18 16:51:23.721 - info: host.196-iobroker-vm-V2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-01-18 16:51:26.156 - info: admin.0 (484) Repository received successfully. 2023-01-18 17:00:00.020 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13775 2023-01-18 17:00:01.149 - info: sbfspot.0 (13775) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 17:00:01.189 - info: sbfspot.0 (13775) nothing to do, because no daylight ... 2023-01-18 17:00:01.191 - info: sbfspot.0 (13775) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 17:00:01.711 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 17:15:00.034 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 started with pid 13795 2023-01-18 17:15:01.118 - info: sbfspot.0 (13795) starting. Version 4.1.2 in /opt/iobroker/node_modules/iobroker.sbfspot, node: v16.19.0, js-controller: 4.0.24 2023-01-18 17:15:01.156 - info: sbfspot.0 (13795) nothing to do, because no daylight ... 2023-01-18 17:15:01.157 - info: sbfspot.0 (13795) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 17:15:01.677 - info: host.196-iobroker-vm-V2 instance system.adapter.sbfspot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 18:58:04.097 - info: host.196-iobroker-vm-V2 iobroker.js-controller version 4.0.24 js-controller starting 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 hostname: 196-iobroker-vm-V2, node: v16.19.0 2023-01-18 18:58:04.101 - info: host.196-iobroker-vm-V2 ip addresses: 192.168.178.231 fe80::bcd2:16ff:fe39:8e82 2023-01-18 18:58:04.728 - info: host.196-iobroker-vm-V2 connected to Objects and States 2023-01-18 18:58:04.753 - info: host.196-iobroker-vm-V2 added notifications configuration of host 2023-01-18 18:58:05.118 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeCurrent" 2023-01-18 18:58:05.119 - info: host.196-iobroker-vm-V2 44 instances found 2023-01-18 18:58:05.149 - info: host.196-iobroker-vm-V2 starting 39 instances 2023-01-18 18:58:05.198 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeNewest" 2023-01-18 18:58:05.250 - info: host.196-iobroker-vm-V2 instance system.adapter.admin.0 started with pid 445 2023-01-18 18:58:05.258 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.nodeNewestNext" 2023-01-18 18:58:05.307 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmCurrent" 2023-01-18 18:58:05.357 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmNewest" 2023-01-18 18:58:05.412 - info: host.196-iobroker-vm-V2 Delete state "system.host.196-iobroker-vm-V2.versions.npmNewestNext" 2023-01-18 18:58:05.478 - info: host.196-iobroker-vm-V2 Some obsolete host states deleted. 2023-01-18 18:58:07.415 - error: admin.0 (445) admin.0 already running 2023-01-18 18:58:07.419 - warn: admin.0 (445) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:07.963 - error: host.196-iobroker-vm-V2 instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:07.964 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.admin.0 because enabled 2023-01-18 18:58:09.187 - info: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 started with pid 456 2023-01-18 18:58:10.347 - error: influxdb.0 (456) influxdb.0 already running 2023-01-18 18:58:10.349 - warn: influxdb.0 (456) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:10.898 - error: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:10.898 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.influxdb.0 because enabled 2023-01-18 18:58:13.268 - info: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 started with pid 467 2023-01-18 18:58:16.316 - error: javascript.0 (467) javascript.0 already running 2023-01-18 18:58:16.324 - warn: javascript.0 (467) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:16.897 - error: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:16.898 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.javascript.0 because enabled 2023-01-18 18:58:17.196 - info: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 started with pid 478 2023-01-18 18:58:18.689 - error: telegram.0 (478) telegram.0 already running 2023-01-18 18:58:18.691 - warn: telegram.0 (478) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:19.225 - error: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:19.226 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.telegram.0 because enabled 2023-01-18 18:58:20.254 - info: host.196-iobroker-vm-V2 instance system.adapter.telegram.0 started with pid 489 2023-01-18 18:58:21.208 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 496 2023-01-18 18:58:22.311 - info: telegram.0 (489) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:22.961 - error: alexa2.0 (496) alexa2.0 already running 2023-01-18 18:58:22.964 - warn: alexa2.0 (496) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:23.514 - error: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:23.515 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.alexa2.0 because enabled 2023-01-18 18:58:25.181 - info: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 started with pid 515 2023-01-18 18:58:26.061 - error: hmip.0 (515) hmip.0 already running 2023-01-18 18:58:26.063 - warn: hmip.0 (515) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:26.597 - error: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:26.597 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hmip.0 because enabled 2023-01-18 18:58:29.183 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.0 started with pid 526 2023-01-18 18:58:30.102 - error: hue.0 (526) hue.0 already running 2023-01-18 18:58:30.104 - warn: hue.0 (526) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:30.643 - error: host.196-iobroker-vm-V2 instance system.adapter.hue.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:30.643 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hue.0 because enabled 2023-01-18 18:58:33.181 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.1 started with pid 537 2023-01-18 18:58:34.203 - error: hue.1 (537) hue.1 already running 2023-01-18 18:58:34.205 - warn: hue.1 (537) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:34.758 - error: host.196-iobroker-vm-V2 instance system.adapter.hue.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:34.759 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.hue.1 because enabled 2023-01-18 18:58:37.183 - info: host.196-iobroker-vm-V2 instance system.adapter.meross.0 started with pid 548 2023-01-18 18:58:37.995 - info: host.196-iobroker-vm-V2 instance system.adapter.admin.0 started with pid 555 2023-01-18 18:58:38.366 - error: meross.0 (548) meross.0 already running 2023-01-18 18:58:38.368 - warn: meross.0 (548) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:38.902 - error: host.196-iobroker-vm-V2 instance system.adapter.meross.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:38.903 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.meross.0 because enabled 2023-01-18 18:58:39.120 - info: admin.0 (555) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:39.142 - info: admin.0 (555) requesting all states 2023-01-18 18:58:39.142 - info: admin.0 (555) requesting all objects 2023-01-18 18:58:39.590 - info: admin.0 (555) received all objects 2023-01-18 18:58:39.865 - info: admin.0 (555) Request actual repository... 2023-01-18 18:58:39.883 - info: admin.0 (555) http server listening on port 8081 2023-01-18 18:58:39.883 - info: admin.0 (555) Use link "http://localhost:8081" to configure. 2023-01-18 18:58:39.889 - info: admin.0 (555) socket.io server listening on port 8081 2023-01-18 18:58:40.076 - info: host.196-iobroker-vm-V2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-01-18 18:58:41.028 - info: host.196-iobroker-vm-V2 instance system.adapter.influxdb.0 started with pid 586 2023-01-18 18:58:41.157 - info: admin.0 (555) Repository received successfully. 2023-01-18 18:58:41.216 - info: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 started with pid 593 2023-01-18 18:58:42.025 - error: mqtt.0 (593) mqtt.0 already running 2023-01-18 18:58:42.027 - warn: mqtt.0 (593) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:42.260 - info: influxdb.0 (586) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.influxdb, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:42.277 - info: influxdb.0 (586) No stored data from last exit found 2023-01-18 18:58:42.278 - info: influxdb.0 (586) Connecting http://192.168.178.198:8086/ ... 2023-01-18 18:58:42.278 - info: influxdb.0 (586) Influx DB Version used: 1.x 2023-01-18 18:58:42.559 - error: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:42.559 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.mqtt.0 because enabled 2023-01-18 18:58:45.182 - info: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 started with pid 612 2023-01-18 18:58:46.194 - error: shelly.0 (612) shelly.0 already running 2023-01-18 18:58:46.195 - warn: shelly.0 (612) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:46.728 - error: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:46.728 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.shelly.0 because enabled 2023-01-18 18:58:46.929 - info: host.196-iobroker-vm-V2 instance system.adapter.javascript.0 started with pid 623 2023-01-18 18:58:48.435 - info: javascript.0 (623) starting. Version 6.1.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:48.773 - info: javascript.0 (623) requesting all states 2023-01-18 18:58:48.773 - info: javascript.0 (623) requesting all objects 2023-01-18 18:58:49.152 - info: javascript.0 (623) received all objects 2023-01-18 18:58:49.185 - info: javascript.0 (623) received all states 2023-01-18 18:58:49.199 - info: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 started with pid 638 2023-01-18 18:58:50.006 - error: sonoff.0 (638) sonoff.0 already running 2023-01-18 18:58:50.008 - warn: sonoff.0 (638) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:50.544 - error: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:50.544 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.sonoff.0 because enabled 2023-01-18 18:58:53.193 - info: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 started with pid 649 2023-01-18 18:58:53.543 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 656 2023-01-18 18:58:54.098 - error: sonos.0 (649) sonos.0 already running 2023-01-18 18:58:54.099 - warn: sonos.0 (649) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:54.634 - error: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:54.634 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.sonos.0 because enabled 2023-01-18 18:58:54.684 - info: alexa2.0 (656) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:54.714 - info: alexa2.0 (656) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2023-01-18 18:58:56.653 - info: host.196-iobroker-vm-V2 instance system.adapter.hmip.0 started with pid 675 2023-01-18 18:58:57.183 - info: host.196-iobroker-vm-V2 instance system.adapter.synology.0 started with pid 682 2023-01-18 18:58:57.911 - info: hmip.0 (675) starting. Version 1.20.0 in /opt/iobroker/node_modules/iobroker.hmip, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:58:58.393 - error: synology.0 (682) synology.0 already running 2023-01-18 18:58:58.395 - warn: synology.0 (682) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:58:58.414 - info: alexa2.0 (656) Update cookie in adapter configuration ... restarting ... 2023-01-18 18:58:58.474 - info: host.196-iobroker-vm-V2 stopInstance system.adapter.alexa2.0 (force=false, process=true) 2023-01-18 18:58:58.482 - info: alexa2.0 (656) Got terminate signal TERMINATE_YOURSELF 2023-01-18 18:58:58.489 - info: alexa2.0 (656) terminating 2023-01-18 18:58:58.490 - info: alexa2.0 (656) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-01-18 18:58:58.535 - info: host.196-iobroker-vm-V2 stopInstance system.adapter.alexa2.0 send kill signal 2023-01-18 18:58:58.965 - error: host.196-iobroker-vm-V2 instance system.adapter.synology.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:58:58.965 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.synology.0 because enabled 2023-01-18 18:58:59.046 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-01-18 18:59:00.683 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.0 started with pid 701 2023-01-18 18:59:01.225 - info: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 started with pid 708 2023-01-18 18:59:01.618 - info: host.196-iobroker-vm-V2 instance system.adapter.alexa2.0 started with pid 715 2023-01-18 18:59:02.246 - info: hue.0 (701) starting. Version 3.7.1 in /opt/iobroker/node_modules/iobroker.hue, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:03.036 - info: hue.0 (701) skip switch: Daylight.configured 2023-01-18 18:59:03.037 - info: hue.0 (701) skip switch: Daylight.sunriseoffset 2023-01-18 18:59:03.038 - info: hue.0 (701) skip switch: Daylight.sunsetoffset 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.alert 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.sensitivity 2023-01-18 18:59:03.042 - info: hue.0 (701) skip switch: BWM Gartenhaus.sensitivitymax 2023-01-18 18:59:03.043 - info: hue.0 (701) skip switch: BWM Gartenhaus.ledindication 2023-01-18 18:59:03.043 - info: hue.0 (701) skip switch: BWM Gartenhaus.usertest 2023-01-18 18:59:03.048 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.alert 2023-01-18 18:59:03.049 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.tholddark 2023-01-18 18:59:03.049 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.tholdoffset 2023-01-18 18:59:03.050 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.ledindication 2023-01-18 18:59:03.050 - info: hue.0 (701) skip switch: Hue outdoor light sensor 1.usertest 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.alert 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.ledindication 2023-01-18 18:59:03.054 - info: hue.0 (701) skip switch: Hue outdoor temp. sensor 1.usertest 2023-01-18 18:59:03.094 - info: hue.0 (701) created/updated 11 sensor channels 2023-01-18 18:59:03.464 - info: alexa2.0 (715) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:03.651 - info: hue.0 (701) created/updated 12 light channels 2023-01-18 18:59:03.653 - info: alexa2.0 (715) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2023-01-18 18:59:03.673 - warn: hue.0 (701) channel "Terrasse" already exists, using "Terrasse_Room" for group 4 2023-01-18 18:59:03.682 - info: hue.0 (701) created/updated 8 groups channels 2023-01-18 18:59:03.684 - info: hue.0 (701) created/updated 36 scenes 2023-01-18 18:59:03.685 - info: hue.0 (701) creating/updating bridge device 2023-01-18 18:59:03.796 - info: hmip.0 (675) ws connection opened 2023-01-18 18:59:04.777 - error: zigbee.0 (708) zigbee.0 already running 2023-01-18 18:59:04.779 - warn: zigbee.0 (708) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:04.825 - info: host.196-iobroker-vm-V2 instance system.adapter.hue.1 started with pid 742 2023-01-18 18:59:05.190 - info: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 started with pid 749 2023-01-18 18:59:05.336 - error: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:05.336 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.zigbee.0 because enabled 2023-01-18 18:59:06.817 - error: discovery.0 (749) discovery.0 already running 2023-01-18 18:59:06.818 - warn: discovery.0 (749) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:07.002 - info: hue.1 (742) starting. Version 3.7.1 in /opt/iobroker/node_modules/iobroker.hue, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:07.348 - error: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:07.348 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.discovery.0 because enabled 2023-01-18 18:59:07.658 - info: hmip.0 (675) hmip adapter connected and ready 2023-01-18 18:59:07.809 - info: hue.1 (742) skip switch: Daylight.configured 2023-01-18 18:59:07.809 - info: hue.1 (742) skip switch: Daylight.sunriseoffset 2023-01-18 18:59:07.810 - info: hue.1 (742) skip switch: Daylight.sunsetoffset 2023-01-18 18:59:07.811 - info: hue.1 (742) skip switch: BWM Hausflur oben.alert 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.sensitivity 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.sensitivitymax 2023-01-18 18:59:07.812 - info: hue.1 (742) skip switch: BWM Hausflur oben.ledindication 2023-01-18 18:59:07.813 - info: hue.1 (742) skip switch: BWM Hausflur oben.usertest 2023-01-18 18:59:07.814 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.alert 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.tholddark 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.tholdoffset 2023-01-18 18:59:07.815 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.ledindication 2023-01-18 18:59:07.816 - info: hue.1 (742) skip switch: Hue ambient light sensor 1.usertest 2023-01-18 18:59:07.817 - info: hue.1 (742) skip switch: Hue temperature sensor 1.alert 2023-01-18 18:59:07.818 - info: hue.1 (742) skip switch: Hue temperature sensor 1.ledindication 2023-01-18 18:59:07.818 - info: hue.1 (742) skip switch: Hue temperature sensor 1.usertest 2023-01-18 18:59:07.819 - info: hue.1 (742) skip switch: BWM Hausflur unten.alert 2023-01-18 18:59:07.819 - info: hue.1 (742) skip switch: BWM Hausflur unten.sensitivity 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.sensitivitymax 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.ledindication 2023-01-18 18:59:07.820 - info: hue.1 (742) skip switch: BWM Hausflur unten.usertest 2023-01-18 18:59:07.821 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.alert 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.tholddark 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.tholdoffset 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.ledindication 2023-01-18 18:59:07.822 - info: hue.1 (742) skip switch: Hue ambient light sensor 2.usertest 2023-01-18 18:59:07.823 - info: hue.1 (742) skip switch: Hue temperature sensor 2.alert 2023-01-18 18:59:07.824 - info: hue.1 (742) skip switch: Hue temperature sensor 2.ledindication 2023-01-18 18:59:07.824 - info: hue.1 (742) skip switch: Hue temperature sensor 2.usertest 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.alert 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.sensitivity 2023-01-18 18:59:07.825 - info: hue.1 (742) skip switch: BWM Kellertreppe.sensitivitymax 2023-01-18 18:59:07.826 - info: hue.1 (742) skip switch: BWM Kellertreppe.ledindication 2023-01-18 18:59:07.826 - info: hue.1 (742) skip switch: BWM Kellertreppe.usertest 2023-01-18 18:59:07.827 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.alert 2023-01-18 18:59:07.827 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.tholddark 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.tholdoffset 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.ledindication 2023-01-18 18:59:07.828 - info: hue.1 (742) skip switch: Hue ambient light sensor 3.usertest 2023-01-18 18:59:07.829 - info: hue.1 (742) skip switch: Hue temperature sensor 3.alert 2023-01-18 18:59:07.829 - info: hue.1 (742) skip switch: Hue temperature sensor 3.ledindication 2023-01-18 18:59:07.830 - info: hue.1 (742) skip switch: Hue temperature sensor 3.usertest 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.alert 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.sensitivity 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.sensitivitymax 2023-01-18 18:59:07.831 - info: hue.1 (742) skip switch: BWM Vorratskeller.ledindication 2023-01-18 18:59:07.832 - info: hue.1 (742) skip switch: BWM Vorratskeller.usertest 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.alert 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.tholddark 2023-01-18 18:59:07.833 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.tholdoffset 2023-01-18 18:59:07.834 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.ledindication 2023-01-18 18:59:07.834 - info: hue.1 (742) skip switch: Hue ambient light sensor 4.usertest 2023-01-18 18:59:07.835 - info: hue.1 (742) skip switch: Hue temperature sensor 4.alert 2023-01-18 18:59:07.836 - info: hue.1 (742) skip switch: Hue temperature sensor 4.ledindication 2023-01-18 18:59:07.836 - info: hue.1 (742) skip switch: Hue temperature sensor 4.usertest 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.alert 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.sensitivity 2023-01-18 18:59:07.837 - info: hue.1 (742) skip switch: BWM Waschkeller.sensitivitymax 2023-01-18 18:59:07.838 - info: hue.1 (742) skip switch: BWM Waschkeller.ledindication 2023-01-18 18:59:07.838 - info: hue.1 (742) skip switch: BWM Waschkeller.usertest 2023-01-18 18:59:07.839 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.alert 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.tholddark 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.tholdoffset 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.ledindication 2023-01-18 18:59:07.840 - info: hue.1 (742) skip switch: Hue ambient light sensor 5.usertest 2023-01-18 18:59:07.844 - info: hue.1 (742) skip switch: Hue temperature sensor 5.alert 2023-01-18 18:59:07.845 - info: hue.1 (742) skip switch: Hue temperature sensor 5.ledindication 2023-01-18 18:59:07.845 - info: hue.1 (742) skip switch: Hue temperature sensor 5.usertest 2023-01-18 18:59:07.846 - info: hue.1 (742) skip switch: BWM Haustür.alert 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.sensitivity 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.sensitivitymax 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.ledindication 2023-01-18 18:59:07.847 - info: hue.1 (742) skip switch: BWM Haustür.usertest 2023-01-18 18:59:07.848 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.alert 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.tholddark 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.tholdoffset 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.ledindication 2023-01-18 18:59:07.849 - info: hue.1 (742) skip switch: Hue outdoor light sensor 1.usertest 2023-01-18 18:59:07.850 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.alert 2023-01-18 18:59:07.851 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.ledindication 2023-01-18 18:59:07.851 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 1.usertest 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.alert 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.sensitivity 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.sensitivitymax 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.ledindication 2023-01-18 18:59:07.852 - info: hue.1 (742) skip switch: BWM Gartentür.usertest 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.alert 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.tholddark 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.tholdoffset 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.ledindication 2023-01-18 18:59:07.854 - info: hue.1 (742) skip switch: Hue outdoor light sensor 2.usertest 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.alert 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.ledindication 2023-01-18 18:59:07.856 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 2.usertest 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.alert 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.sensitivity 2023-01-18 18:59:07.858 - info: hue.1 (742) skip switch: BWM Flur EG.sensitivitymax 2023-01-18 18:59:07.859 - info: hue.1 (742) skip switch: BWM Flur EG.ledindication 2023-01-18 18:59:07.859 - info: hue.1 (742) skip switch: BWM Flur EG.usertest 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.alert 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.tholddark 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.tholdoffset 2023-01-18 18:59:07.860 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.ledindication 2023-01-18 18:59:07.861 - info: hue.1 (742) skip switch: Hue outdoor light sensor 3.usertest 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.alert 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.ledindication 2023-01-18 18:59:07.862 - info: hue.1 (742) skip switch: Hue outdoor temp. sensor 3.usertest 2023-01-18 18:59:07.862 - info: hue.1 (742) created/updated 25 sensor channels 2023-01-18 18:59:08.082 - info: alexa2.0 (715) Initialize all Device states ... 2023-01-18 18:59:08.212 - info: hue.1 (742) created/updated 9 light channels 2023-01-18 18:59:08.215 - warn: hue.1 (742) channel "Kellergang" already exists, using "Kellergang_Room" for group 2 2023-01-18 18:59:08.216 - warn: hue.1 (742) channel "Haustür" already exists, using "Haustür_Room" for group 3 2023-01-18 18:59:08.217 - warn: hue.1 (742) channel "Garagentür" already exists, using "Garagentür_Room" for group 4 2023-01-18 18:59:08.219 - warn: hue.1 (742) channel "Gartentür" already exists, using "Gartentür_Room" for group 5 2023-01-18 18:59:08.224 - info: hue.1 (742) created/updated 9 groups channels 2023-01-18 18:59:08.226 - info: hue.1 (742) created/updated 26 scenes 2023-01-18 18:59:08.227 - info: hue.1 (742) creating/updating bridge device 2023-01-18 18:59:08.930 - info: host.196-iobroker-vm-V2 instance system.adapter.meross.0 started with pid 768 2023-01-18 18:59:09.203 - info: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 started with pid 775 2023-01-18 18:59:11.437 - error: backitup.0 (775) backitup.0 already running 2023-01-18 18:59:11.439 - warn: backitup.0 (775) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:11.561 - info: meross.0 (768) starting. Version 1.14.0 in /opt/iobroker/node_modules/iobroker.meross, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:11.975 - error: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:11.976 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.backitup.0 because enabled 2023-01-18 18:59:12.315 - info: meross.0 (768) Device 2106164874521890852648e1e97294bd initialized 2023-01-18 18:59:12.563 - info: meross.0 (768) Device: 2106164874521890852648e1e97294bd connected 2023-01-18 18:59:12.585 - info: host.196-iobroker-vm-V2 instance system.adapter.mqtt.0 started with pid 794 2023-01-18 18:59:12.736 - info: meross.0 (768) Devices initialized 2023-01-18 18:59:13.287 - info: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 started with pid 801 2023-01-18 18:59:15.646 - info: mqtt.0 (794) starting. Version 4.0.7 in /opt/iobroker/node_modules/iobroker.mqtt, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:15.984 - info: mqtt.0 (794) Starting MQTT server on 0.0.0.0:1884 2023-01-18 18:59:16.219 - error: cloud.0 (801) cloud.0 already running 2023-01-18 18:59:16.221 - warn: cloud.0 (801) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:16.768 - error: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:16.768 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.cloud.0 because enabled 2023-01-18 18:59:16.825 - info: host.196-iobroker-vm-V2 instance system.adapter.shelly.0 started with pid 820 2023-01-18 18:59:17.186 - info: host.196-iobroker-vm-V2 instance system.adapter.web.0 started with pid 827 2023-01-18 18:59:18.576 - info: shelly.0 (820) starting. Version 6.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:18.681 - info: shelly.0 (820) Starting in MQTT mode. Listening on 0.0.0.0:1882 2023-01-18 18:59:18.707 - error: web.0 (827) web.0 already running 2023-01-18 18:59:18.709 - warn: web.0 (827) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:19.250 - error: host.196-iobroker-vm-V2 instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:19.250 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.web.0 because enabled 2023-01-18 18:59:20.568 - info: host.196-iobroker-vm-V2 instance system.adapter.sonoff.0 started with pid 846 2023-01-18 18:59:21.196 - info: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 started with pid 853 2023-01-18 18:59:21.724 - info: sonoff.0 (846) starting. Version 2.5.1 in /opt/iobroker/node_modules/iobroker.sonoff, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:21.759 - info: sonoff.0 (846) Starting MQTT authenticated server on port 1883 2023-01-18 18:59:22.351 - error: go-e.0 (853) go-e.0 already running 2023-01-18 18:59:22.353 - warn: go-e.0 (853) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:22.885 - error: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:22.886 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.go-e.0 because enabled 2023-01-18 18:59:24.656 - info: host.196-iobroker-vm-V2 instance system.adapter.sonos.0 started with pid 872 2023-01-18 18:59:25.191 - info: host.196-iobroker-vm-V2 instance system.adapter.info.0 started with pid 879 2023-01-18 18:59:25.730 - info: sonos.0 (872) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.sonos, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:26.974 - error: info.0 (879) info.0 already running 2023-01-18 18:59:26.978 - warn: info.0 (879) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:27.514 - error: host.196-iobroker-vm-V2 instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:27.515 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.info.0 because enabled 2023-01-18 18:59:28.990 - info: host.196-iobroker-vm-V2 instance system.adapter.synology.0 started with pid 910 2023-01-18 18:59:29.191 - info: host.196-iobroker-vm-V2 instance system.adapter.logparser.0 started with pid 917 2023-01-18 18:59:30.322 - error: logparser.0 (917) logparser.0 already running 2023-01-18 18:59:30.324 - warn: logparser.0 (917) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:30.876 - error: host.196-iobroker-vm-V2 instance system.adapter.logparser.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:30.877 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.logparser.0 because enabled 2023-01-18 18:59:30.913 - info: synology.0 (910) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.synology, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:30.947 - info: synology.0 (910) Connecting to Synology 192.168.178.107:5001 2023-01-18 18:59:33.540 - info: synology.0 (910) DSM 7 2023-01-18 18:59:33.541 - info: synology.0 (910) DSM 7 detected, set all to true 2023-01-18 18:59:33.986 - info: vis.0 (936) starting. Version 1.4.15 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:34.011 - error: vis.0 (936) No license found for vis. Please get one on https://iobroker.net ! 2023-01-18 18:59:35.328 - info: vis.0 (936) Terminated (NO_ERROR): Without reason 2023-01-18 18:59:35.360 - info: host.196-iobroker-vm-V2 instance system.adapter.zigbee.0 started with pid 951 2023-01-18 18:59:35.887 - info: host.196-iobroker-vm-V2 instance system.adapter.vis.0 terminated while should be started once 2023-01-18 18:59:37.327 - info: host.196-iobroker-vm-V2 instance system.adapter.vis-inventwo.0 started with pid 962 2023-01-18 18:59:37.426 - info: host.196-iobroker-vm-V2 instance system.adapter.discovery.0 started with pid 969 2023-01-18 18:59:37.586 - info: zigbee.0 (951) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:37.902 - info: zigbee.0 (951) Starting Zigbee npm ... 2023-01-18 18:59:39.290 - info: zigbee.0 (951) Installed Version: iobroker.zigbee@1.8.10 2023-01-18 18:59:40.212 - error: vis-inventwo.0 (962) vis-inventwo.0 already running 2023-01-18 18:59:40.214 - warn: vis-inventwo.0 (962) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:40.672 - info: discovery.0 (969) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:40.736 - info: zigbee.0 (951) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}} 2023-01-18 18:59:40.746 - info: zigbee.0 (951) Unable to disable LED, unsupported function. 2023-01-18 18:59:40.757 - info: zigbee.0 (951) --> transmitPower : high+ 2023-01-18 18:59:40.775 - error: host.196-iobroker-vm-V2 instance system.adapter.vis-inventwo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:40.776 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.vis-inventwo.0 because enabled 2023-01-18 18:59:40.776 - info: zigbee.0 (951) Currently no devices. 2023-01-18 18:59:40.777 - info: zigbee.0 (951) Zigbee started 2023-01-18 18:59:41.182 - info: host.196-iobroker-vm-V2 instance system.adapter.proxmox.0 started with pid 992 2023-01-18 18:59:42.012 - info: host.196-iobroker-vm-V2 instance system.adapter.backitup.0 started with pid 999 2023-01-18 18:59:42.283 - error: proxmox.0 (992) proxmox.0 already running 2023-01-18 18:59:42.285 - warn: proxmox.0 (992) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:42.852 - error: host.196-iobroker-vm-V2 instance system.adapter.proxmox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:42.852 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.proxmox.0 because enabled 2023-01-18 18:59:43.404 - info: backitup.0 (999) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:43.527 - info: backitup.0 (999) [iobroker] backup was activated at every 1 day(s) 2023-01-18 18:59:45.188 - info: host.196-iobroker-vm-V2 instance scheduled system.adapter.sbfspot.0 */15 * * * * 2023-01-18 18:59:46.794 - info: host.196-iobroker-vm-V2 instance system.adapter.cloud.0 started with pid 1018 2023-01-18 18:59:47.813 - info: cloud.0 (1018) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.cloud, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:47.847 - info: cloud.0 (1018) Connecting with https://iobroker.pro:10555 with "@pro_draci009@gmail.com_646bef80-7f06-11ed-85c5-e76fc4fe39c4" 2023-01-18 18:59:47.983 - info: cloud.0 (1018) Trying to connect as system.user.admin to cloud 2023-01-18 18:59:48.608 - info: cloud.0 (1018) Adapter redirected temporally to "https://iobroker.pro:10556" in 30 seconds. Reason: command from server 2023-01-18 18:59:48.610 - info: cloud.0 (1018) Connection changed: disconnect 2023-01-18 18:59:49.188 - info: host.196-iobroker-vm-V2 instance system.adapter.tankerkoenig.0 started with pid 1033 2023-01-18 18:59:49.285 - info: host.196-iobroker-vm-V2 instance system.adapter.web.0 started with pid 1040 2023-01-18 18:59:50.213 - error: tankerkoenig.0 (1033) tankerkoenig.0 already running 2023-01-18 18:59:50.215 - warn: tankerkoenig.0 (1033) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:50.451 - info: web.0 (1040) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:50.635 - info: web.0 (1040) socket.io server listening on port 8082 2023-01-18 18:59:50.637 - info: web.0 (1040) http server listening on port 8082 2023-01-18 18:59:50.745 - error: host.196-iobroker-vm-V2 instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:50.745 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.tankerkoenig.0 because enabled 2023-01-18 18:59:52.909 - info: host.196-iobroker-vm-V2 instance system.adapter.go-e.0 started with pid 1059 2023-01-18 18:59:53.188 - info: host.196-iobroker-vm-V2 instance system.adapter.wled.0 started with pid 1066 2023-01-18 18:59:54.666 - error: wled.0 (1066) wled.0 already running 2023-01-18 18:59:54.669 - warn: wled.0 (1066) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:55.117 - info: go-e.0 (1059) starting. Version 1.0.23 in /opt/iobroker/node_modules/iobroker.go-e, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:55.134 - info: go-e.0 (1059) Server: 192.168.178.206 2023-01-18 18:59:55.135 - info: go-e.0 (1059) Intervall: 60 2023-01-18 18:59:55.135 - warn: go-e.0 (1059) Sentry enabled. You can switch it off in settings of the adapter. 2023-01-18 18:59:55.232 - error: host.196-iobroker-vm-V2 instance system.adapter.wled.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:55.232 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.wled.0 because enabled 2023-01-18 18:59:57.170 - info: host.196-iobroker-vm-V2 instance system.adapter.yahka.0 started with pid 1085 2023-01-18 18:59:57.551 - info: host.196-iobroker-vm-V2 instance system.adapter.info.0 started with pid 1092 2023-01-18 18:59:58.580 - error: yahka.0 (1085) yahka.0 already running 2023-01-18 18:59:58.582 - warn: yahka.0 (1085) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-01-18 18:59:59.127 - error: host.196-iobroker-vm-V2 instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-01-18 18:59:59.127 - info: host.196-iobroker-vm-V2 Restart adapter system.adapter.yahka.0 because enabled 2023-01-18 18:59:59.739 - info: info.0 (1092) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v16.19.0, js-controller: 4.0.24 2023-01-18 18:59:59.791 - info: info.0 (1092) Reading/updating systemdata.@900icard sagte in Proxmox VM friert ein:
2023-01-18 18:58:04.097
ab dieser Uhrzeit startet er neu ...
aber da die Adapter schon gestartet sind kommt halt diese Meldung :
Adapter .... already running
Du hast relativ viele Fehlermeldungen / Meldungen im Bereich
sbfspot.0
hmip.0
wled.0ich würde eher sagen dein Log quillt über ..
Mehr kann ich gerade nicht erkennen ...
-
@900icard sagte in Proxmox VM friert ein:
CPU ist ein Cerleron N5105 .
der sollte mit einem Passmark von 4000 nicht zu schwach sein.
wie sieht es denn mit RAM aus
oder Plattenplatz
mehr auf die VMs verteilt, als da ist?
Auch Proxmox benötigt Ressourcen!Also 16 GB RAM davon ca. 10 GB in use bei 5 VMs
CPU Auslastung bei ca. 18% ebenfalls bei 5 VMs
local 100GB und davon 9% in use
local-lvm 360GB davon 40% in use
Scheint mir auch nicht recht auffällig zu sein aber ich tendiere irgendwie in die Richtung bzgl. Fehler weil es ja Anfangs (fast) sauber lief und seit Weihnachten nicht mehr.
Davor habe ich als letztes die 5te VM angelegt weil ich da mit PeerTube was testen will, aber noch nix gemacht.
Die VM hab ich jetzt mal runtergefahren ... mal sehn was passiert. -
Hallo Zusammen,
ich reihe mich hier mal ein in die Liste der Geplagten ein.
Bei mir läuft Proxmox (aktuell 7.3-4) mit 3 VMS.
Eine mit ioBroker (6.3.5 mit JS Controller 4.0.24), eine mit InfluxDB (1.8.6) und eine mit Grafana (9.3.5).Das ganze lief jetzt ein Jahr lang fast stabil, so aller 3-4 Monate hatte ich das Einfrierproblem und ich dachte erst, dass es (Hab jeweils Debian 11 VM mit Desktop drauf) daran liegt, dass wenn Debian sagt es wären neue Updates verfügbar, dass er dann einfriert. Die Meldung der Updates hab ich dann ausgeschalten, selbes Problem.
Seit Weihnachten haben sich die Ausfälle stark gehäuft so dass diese nun zwischen 2 und 48 Stunden auftreten.
Ich hab schon einiges ausprobiert, also diverse Adapter deaktiviert die ich in Verdacht hatte usw.Wenn "nur" die Grundinstallation von ioBroker aktiv ist, also Admin, BackitUp und Discovery läuft "scheint" es keine Probleme zu geben.
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch, dann hab ich gestern alle Adapter neu installiert und die meisten konfiguriert und zack, heute abgeschmiert.
CPU ist ein Cerleron N5105 ... keine Ahnung ob das wirklich an dem liegt, lief ja vorher auch.
Stutzig macht mich aber, dass auch die InfluxDB VM jetzt schon 2-3 mal abgeschmiert ist und auch die Grafana VM schon einmal.
Sehr, sehr strange.Das nächste was ich ausprobiere werde - wohl oder übel - ich werde mir eine AMD Kiste holen und dort Proxmox und die VMs neu aufsetzen.
Bin gespannt was dann passiert.Ich werde berichten. So richtig kann ich aber an den CPU Fehler nicht glauben.
Falls jemand schon weiter ist oder sogar das Problem schon eindeutig identifizieren konnte, gern posten ;-)Ärgerlich weil ich eigentlich an ioBroker weiter bauen will aber hilft nix, so kann ich damit nicht arbeiten.
Trotzdem einen schönen Abend an alle Geplagten.
@900icard sagte in Proxmox VM friert ein:
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch,
also dann mit einem Backup ..
aber warum danach daß !?
dann hab ich gestern alle Adapter neu installiert
-
@900icard sagte in Proxmox VM friert ein:
2023-01-18 18:58:04.097
ab dieser Uhrzeit startet er neu ...
aber da die Adapter schon gestartet sind kommt halt diese Meldung :
Adapter .... already running
Du hast relativ viele Fehlermeldungen / Meldungen im Bereich
sbfspot.0
hmip.0
wled.0ich würde eher sagen dein Log quillt über ..
Mehr kann ich gerade nicht erkennen ...
Ja, sbfspot schaut aller 5 Min. nach neuen Daten und wled meckert (warn) schon länger wegen einem value -1 der nicht sein darf.
Das ist aber nichts neues für mich, im Log.hmip konnte heute wohl mal keine Verbindung aufbauen, das ist in der tat neu.
Ich werde mal, nur damit ich das ggf. ausschließen kann, diese drei Adapter deaktivieren und schauen was passiert.
-
Ja, sbfspot schaut aller 5 Min. nach neuen Daten und wled meckert (warn) schon länger wegen einem value -1 der nicht sein darf.
Das ist aber nichts neues für mich, im Log.hmip konnte heute wohl mal keine Verbindung aufbauen, das ist in der tat neu.
Ich werde mal, nur damit ich das ggf. ausschließen kann, diese drei Adapter deaktivieren und schauen was passiert.
-
Also 16 GB RAM davon ca. 10 GB in use bei 5 VMs
CPU Auslastung bei ca. 18% ebenfalls bei 5 VMs
local 100GB und davon 9% in use
local-lvm 360GB davon 40% in use
Scheint mir auch nicht recht auffällig zu sein aber ich tendiere irgendwie in die Richtung bzgl. Fehler weil es ja Anfangs (fast) sauber lief und seit Weihnachten nicht mehr.
Davor habe ich als letztes die 5te VM angelegt weil ich da mit PeerTube was testen will, aber noch nix gemacht.
Die VM hab ich jetzt mal runtergefahren ... mal sehn was passiert.@900icard was in use ist ist irrelevant!
wenn du z.B 128GB Plattenplatz hast, darfst du nicht jeder VM mit 42GB zuweisen.
Proxmox selber braucht auch noch etwas. Auch wenn die VMs ihren Platz nicht ausschöpfen! -
@900icard sagte in Proxmox VM friert ein:
Hab eine komplett neue VM aufgesetzt, (Debian 11 ohne Desktop) und ioBroker installiert, lief 3 Tage durch,
also dann mit einem Backup ..
aber warum danach daß !?
dann hab ich gestern alle Adapter neu installiert
ich hab drei Sachen ausprobiert.
- die komplette VM geklont, gleiches Problem.
- Backup gemacht, ioB neu aufgesetzt und alles per BackItUp Adapter restored, gleiches Problem. (Davor war meine Vermutung der SourceAnalytics Adapter den ich nicht aus dem Stable hatte)
- Neue VM aufgesetzt, blanko, ioB Blanko installiert und alle Adapter von Hand neu installiert und konfiguriert.
Heute wollte ich eigentlich weitermachen mit den Javascripten, dem Vis Projekt und der Userdata Objektstruktur aber soweit bin ich nicht gekommen da war er schon wieder abgeschmiert.
Also müsste es an einem der Adapter liegen oder generell an Proxmox oder der Hardware. Vielleicht läuft ja wirklich irgendwas voll aber es ist nichts zu erkennen, weder im ioB Log noch im Proxmox Log. Da es - scheinbar zumindest - mit der Grundinstallation des ioB (also nur Admin, Backitup und Discovery läuft) ist meine Vermutung, dass mit diesen drei Adaptern das "volllaufen" nur viel länger dauert und er erst nach 2-3 Wochen oder so abschmieren würde oder es liegt wirklich an einem der Adapter.
Mein letztes Problem war das Ding mit dem Netatmo Adapter der keine Live Events mehr aktualiseren konnte. Hab dann aber den cloud Adapter installiert, mir eine Lizenz gekauft und dann lief das wieder. Aber wenn ich sowohl nur den Cloud Adapter alleine oder nur den Netatmo Adapter alleine oder auch beide zusammen deaktiviere, schmiert er trotzdem ab.
Verzwickte Sache und Suche nach der Nadel im Heuhaufen grad ...
-
@900icard sagte in Proxmox VM friert ein:
Ja, sbfspot schaut aller 5 Min.
Brauchst du diese Info´s im ioBrocker Log !?
Wenn nicht , dann stelle die Logstufe bei der Instanz auf WARN.
@glasfaser said in Proxmox VM friert ein:
@900icard sagte in Proxmox VM friert ein:
Ja, sbfspot schaut aller 5 Min.
Brauchst du diese Info´s im ioBrocker Log !?
Wenn nicht , dann stelle die Logstufe bei der Instanz auf WARN.
Stimmt, brauch ich nicht, habs auf warn gestellt. Danke für den Tip, hab ich garnicht dran gedacht, dass man damit das Log etwas cleaner bekommt.
-
ich hab drei Sachen ausprobiert.
- die komplette VM geklont, gleiches Problem.
- Backup gemacht, ioB neu aufgesetzt und alles per BackItUp Adapter restored, gleiches Problem. (Davor war meine Vermutung der SourceAnalytics Adapter den ich nicht aus dem Stable hatte)
- Neue VM aufgesetzt, blanko, ioB Blanko installiert und alle Adapter von Hand neu installiert und konfiguriert.
Heute wollte ich eigentlich weitermachen mit den Javascripten, dem Vis Projekt und der Userdata Objektstruktur aber soweit bin ich nicht gekommen da war er schon wieder abgeschmiert.
Also müsste es an einem der Adapter liegen oder generell an Proxmox oder der Hardware. Vielleicht läuft ja wirklich irgendwas voll aber es ist nichts zu erkennen, weder im ioB Log noch im Proxmox Log. Da es - scheinbar zumindest - mit der Grundinstallation des ioB (also nur Admin, Backitup und Discovery läuft) ist meine Vermutung, dass mit diesen drei Adaptern das "volllaufen" nur viel länger dauert und er erst nach 2-3 Wochen oder so abschmieren würde oder es liegt wirklich an einem der Adapter.
Mein letztes Problem war das Ding mit dem Netatmo Adapter der keine Live Events mehr aktualiseren konnte. Hab dann aber den cloud Adapter installiert, mir eine Lizenz gekauft und dann lief das wieder. Aber wenn ich sowohl nur den Cloud Adapter alleine oder nur den Netatmo Adapter alleine oder auch beide zusammen deaktiviere, schmiert er trotzdem ab.
Verzwickte Sache und Suche nach der Nadel im Heuhaufen grad ...
-
@900icard was in use ist ist irrelevant!
wenn du z.B 128GB Plattenplatz hast, darfst du nicht jeder VM mit 42GB zuweisen.
Proxmox selber braucht auch noch etwas. Auch wenn die VMs ihren Platz nicht ausschöpfen!@homoran said in Proxmox VM friert ein:
@900icard was in use ist ist irrelevant!
wenn du z.B 128GB Plattenplatz hast, darfst du nicht jeder VM mit 42GB zuweisen.
Proxmox selber braucht auch noch etwas. Auch wenn die VMs ihren Platz nicht ausschöpfen!Ok, ja das stimmt.
Blöde Frage, in Proxmox steht 100GB bei local und 363GB bei local-lvm als verfügbarer Platz.
Müssen die VMs alle mit den 100GB auskommen?
Ich hatte jeder 32 GB zugewiesen und x4 ergibt 128GB und da wäre ich ja drüber ... Hmmm, .... das könnte dann in der Tat das Problem sein.Ich hab ja nun die PeerTube VM heruntergefahren aber vermutlich muss ich die komplett killen um den Platz wieder frei zu bekommen.
Das werde ich als nächsten (aber erst morgen) mal ausprobieren.Aber Danke schon mal für den Hinweis!
-
ich würde erstmal das Log aufräumen ... das ist schon recht vollgemüllt.
Das heißt ...wie du schon selber schreibst einzelne Adapter dazu überprüfen ,
aber auch eventuell läuft ein JS Script Amok !?@glasfaser said in Proxmox VM friert ein:
ich würde erstmal das Log aufräumen ... das ist schon recht vollgemüllt.
Das heißt ...wie du schon selber schreibst einzelne Adapter dazu überprüfen ,
aber auch eventuell läuft ein JS Script Amok !?Mach ich, gute Idee. Hat ich auch schon eher mal drauf kommen können. Danke
Ein Amok JS Script würde ich mal ausschließen weil ich den JS Adapter auch schon deaktiviert hatte und er trotzdem abgeschmiert ist.Aber Danke Dir und @homoran schon mal für die Unterstützung hier, ich bin grad schon etwas optimistischer das Problem zu finden.
Morgen gehts weiter :-)
Support us
271
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge