NEWS
Performance Probleme durch Shelly Adapter?
Performance Probleme durch Shelly Adapter?
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
sagt der manchmal
Das habe ich auch manchmal ... , das legt sich wieder ohne etwas am ioBroker zu machen .
Also nur das mit der " Instanz " , als Performance Problem meinst du dann !?
@glasfaser
Siehe meine CPU Auslastung weiter oben im Thread. Das meine ich mit Performance...Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
root@iobroker:/opt/iobroker# iobroker list instances + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled system.adapter.device-watcher.0 : device-watcher : iobroker - disabled system.adapter.devices.0 : devices : iobroker - disabled system.adapter.dwd.0 : dwd : iobroker - disabled system.adapter.energiefluss.0 : energiefluss : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - disabled system.adapter.ical.0 : ical : iobroker - disabled system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086 system.adapter.jarvis.0 : jarvis : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.meross.0 : meross : iobroker - disabled + system.adapter.modbus.0 : modbus : iobroker - enabled system.adapter.mqtt.0 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 system.adapter.mqtt.1 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.netatmo.0 : netatmo : iobroker - enabled + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 system.adapter.pushover.0 : pushover : iobroker - disabled system.adapter.pvforecast.0 : pvforecast : iobroker - disabled system.adapter.schoolfree.0 : schoolfree : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : iobroker - enabled system.adapter.snmp.0 : snmp : iobroker - disabled system.adapter.sonos.0 : sonos : iobroker - disabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.vw-connect.0 : vw-connect : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: adminDie Auslastung auf dem NAS sehen deutlich besser aus:
Aber eben nicht so im iobroker:
top - 19:59:10 up 6:50, 0 users, load average: 3,68, 4,47, 5,70 Tasks: 19 total, 1 running, 18 sleeping, 0 stopped, 0 zombie %Cpu(s): 39,3 us, 29,7 sy, 0,2 ni, 23,4 id, 6,4 wa, 0,0 hi, 1,0 si, 0,0 st MiB Mem : 7792,2 total, 1160,6 free, 4499,3 used, 2132,3 buff/cache MiB Swap: 23447,2 total, 23009,1 free, 438,1 used. 2514,5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 365 iobroker 20 0 861548 142888 39684 S 7,6 1,8 1:18.49 io.shelly.0 173 iobroker 20 0 11,2g 397588 47524 S 5,0 5,0 2:30.45 iobroker.js-con 523 iobroker 20 0 686396 85680 45720 S 4,7 1,1 0:04.43 io.shuttercontr 325 iobroker 20 0 21,0g 192536 49516 S 4,3 2,4 0:53.08 node-red 226 iobroker 20 0 855092 173188 39564 S 0,7 2,2 0:37.47 io.javascript.0 565 iobroker 20 0 689056 95860 39600 S 0,7 1,2 0:14.53 io.sourceanalyt 1 root 20 0 7372 3676 3336 S 0,0 0,0 0:00.06 bash 195 iobroker 20 0 1035244 182472 47132 S 0,0 2,3 0:24.22 io.admin.0 237 iobroker 20 0 684288 80756 39588 S 0,0 1,0 0:02.91 io.node-red.0 298 iobroker 20 0 686500 79628 39840 S 0,0 1,0 0:03.56 io.modbus.0 332 iobroker 20 0 950760 80840 41056 S 0,0 1,0 0:03.56 io.netatmo.0 396 iobroker 20 0 10,7g 90416 47104 S 0,0 1,1 0:03.31 io.backitup.0 403 iobroker 20 0 815984 77264 40732 S 0,0 1,0 0:03.13 io.cloud.0 596 iobroker 20 0 10,9g 91620 42448 S 0,0 1,1 0:05.85 io.vw-connect.0 607 iobroker 20 0 685236 78756 39644 S 0,0 1,0 0:02.97 io.web.0 1232 root 20 0 7504 3960 3440 S 0,0 0,0 0:00.03 bash 1275 root 20 0 10308 3684 3208 R 0,0 0,0 0:00.33 top 1288 root 20 0 7504 3936 3416 S 0,0 0,0 0:00.04 bash 1707 root 20 0 10308 3684 3212 S 0,0 0,0 0:00.01 top -
@glasfaser
Siehe meine CPU Auslastung weiter oben im Thread. Das meine ich mit Performance...Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
root@iobroker:/opt/iobroker# iobroker list instances + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled system.adapter.device-watcher.0 : device-watcher : iobroker - disabled system.adapter.devices.0 : devices : iobroker - disabled system.adapter.dwd.0 : dwd : iobroker - disabled system.adapter.energiefluss.0 : energiefluss : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - disabled system.adapter.ical.0 : ical : iobroker - disabled system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086 system.adapter.jarvis.0 : jarvis : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.meross.0 : meross : iobroker - disabled + system.adapter.modbus.0 : modbus : iobroker - enabled system.adapter.mqtt.0 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 system.adapter.mqtt.1 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.netatmo.0 : netatmo : iobroker - enabled + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 system.adapter.pushover.0 : pushover : iobroker - disabled system.adapter.pvforecast.0 : pvforecast : iobroker - disabled system.adapter.schoolfree.0 : schoolfree : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : iobroker - enabled system.adapter.snmp.0 : snmp : iobroker - disabled system.adapter.sonos.0 : sonos : iobroker - disabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.vw-connect.0 : vw-connect : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: adminDie Auslastung auf dem NAS sehen deutlich besser aus:
Aber eben nicht so im iobroker:
top - 19:59:10 up 6:50, 0 users, load average: 3,68, 4,47, 5,70 Tasks: 19 total, 1 running, 18 sleeping, 0 stopped, 0 zombie %Cpu(s): 39,3 us, 29,7 sy, 0,2 ni, 23,4 id, 6,4 wa, 0,0 hi, 1,0 si, 0,0 st MiB Mem : 7792,2 total, 1160,6 free, 4499,3 used, 2132,3 buff/cache MiB Swap: 23447,2 total, 23009,1 free, 438,1 used. 2514,5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 365 iobroker 20 0 861548 142888 39684 S 7,6 1,8 1:18.49 io.shelly.0 173 iobroker 20 0 11,2g 397588 47524 S 5,0 5,0 2:30.45 iobroker.js-con 523 iobroker 20 0 686396 85680 45720 S 4,7 1,1 0:04.43 io.shuttercontr 325 iobroker 20 0 21,0g 192536 49516 S 4,3 2,4 0:53.08 node-red 226 iobroker 20 0 855092 173188 39564 S 0,7 2,2 0:37.47 io.javascript.0 565 iobroker 20 0 689056 95860 39600 S 0,7 1,2 0:14.53 io.sourceanalyt 1 root 20 0 7372 3676 3336 S 0,0 0,0 0:00.06 bash 195 iobroker 20 0 1035244 182472 47132 S 0,0 2,3 0:24.22 io.admin.0 237 iobroker 20 0 684288 80756 39588 S 0,0 1,0 0:02.91 io.node-red.0 298 iobroker 20 0 686500 79628 39840 S 0,0 1,0 0:03.56 io.modbus.0 332 iobroker 20 0 950760 80840 41056 S 0,0 1,0 0:03.56 io.netatmo.0 396 iobroker 20 0 10,7g 90416 47104 S 0,0 1,1 0:03.31 io.backitup.0 403 iobroker 20 0 815984 77264 40732 S 0,0 1,0 0:03.13 io.cloud.0 596 iobroker 20 0 10,9g 91620 42448 S 0,0 1,1 0:05.85 io.vw-connect.0 607 iobroker 20 0 685236 78756 39644 S 0,0 1,0 0:02.97 io.web.0 1232 root 20 0 7504 3960 3440 S 0,0 0,0 0:00.03 bash 1275 root 20 0 10308 3684 3208 R 0,0 0,0 0:00.33 top 1288 root 20 0 7504 3936 3416 S 0,0 0,0 0:00.04 bash 1707 root 20 0 10308 3684 3212 S 0,0 0,0 0:00.01 top@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Das meine ich mit Performance...
Ich schreibe später was dazu ..
erstmal ...
wie bemerkst du es noch .... nur nach dieser Virtuell Ausgabe oder
funktioniert etwas außer der Instanz Anzeige ( manchmal ) nicht . -
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Das meine ich mit Performance...
Ich schreibe später was dazu ..
erstmal ...
wie bemerkst du es noch .... nur nach dieser Virtuell Ausgabe oder
funktioniert etwas außer der Instanz Anzeige ( manchmal ) nicht .@glasfaser Der iobroker ist total träge. Lässt sich nicht aufrufen. Häufig Timeout. Einige Adapter, wie z.B. Shuttercontrol haben ganrichts gesteuert mehr.
-
@glasfaser Der iobroker ist total träge. Lässt sich nicht aufrufen. Häufig Timeout. Einige Adapter, wie z.B. Shuttercontrol haben ganrichts gesteuert mehr.
-
@glasfaser said in Performance Probleme durch Shelly Adapter?:
ps auxww
root@iobroker:/opt/iobroker# ps auxww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 7372 2980 ? Ss 19:34 0:00 bash /opt/scripts/iobroker_startup.sh iobroker 173 8.3 4.4 11735692 358576 ? Sl 19:36 4:28 iobroker.js-controller iobroker 195 1.1 2.3 1038604 189012 ? Sl 19:36 0:37 io.admin.0 iobroker 226 1.6 2.2 857140 175700 ? Sl 19:36 0:53 io.javascript.0 iobroker 237 0.1 1.0 684288 82860 ? Sl 19:36 0:03 io.node-red.0 iobroker 298 0.1 1.0 689060 81324 ? Sl 19:36 0:05 io.modbus.0 iobroker 325 3.5 2.2 22020212 182608 ? Sl 19:36 1:53 node-red iobroker 332 0.1 1.0 952296 82692 ? Sl 19:36 0:04 io.netatmo.0 iobroker 365 5.2 1.9 857708 154212 ? Sl 19:36 2:45 io.shelly.0 iobroker 396 0.1 1.1 11176388 91924 ? Sl 19:37 0:04 io.backitup.0 iobroker 403 0.1 1.0 816752 80784 ? Sl 19:37 0:04 io.cloud.0 iobroker 523 0.1 1.1 689468 89564 ? Sl 19:37 0:05 io.shuttercontrol.0 iobroker 565 0.6 1.2 691616 97788 ? Sl 19:37 0:21 io.sourceanalytix.0 iobroker 596 0.2 1.0 11437464 87620 ? Sl 19:37 0:08 io.vw-connect.0 iobroker 607 0.1 1.0 686260 80708 ? Sl 19:37 0:04 io.web.0 root 1232 0.0 0.0 7504 3276 pts/0 Ss 19:49 0:00 bash root 1275 0.0 0.0 10308 3468 pts/0 S+ 19:50 0:01 top root 1288 0.0 0.0 7504 3252 pts/1 Ss 19:51 0:00 bash root 1707 0.0 0.0 10308 3484 pts/1 S+ 19:58 0:01 top root 1802 0.0 0.0 7504 3140 pts/2 Ss 20:00 0:00 bash root 1820 0.0 0.0 7240 2680 pts/2 S+ 20:00 0:00 /bin/bash /usr/bin/iob logs --watch iobroker 1821 0.1 0.9 937552 73120 pts/2 Sl+ 20:00 0:02 node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js logs --watch iobroker 3082 2.3 1.0 692332 86608 ? Sl 20:27 0:03 io.mqtt.0 root 3218 0.6 0.0 7504 3884 pts/3 Ss 20:29 0:00 bash root 3224 0.0 0.0 10100 3488 pts/3 R+ 20:29 0:00 ps auxww -
@glasfaser said in Performance Probleme durch Shelly Adapter?:
ps auxww
root@iobroker:/opt/iobroker# ps auxww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 7372 2980 ? Ss 19:34 0:00 bash /opt/scripts/iobroker_startup.sh iobroker 173 8.3 4.4 11735692 358576 ? Sl 19:36 4:28 iobroker.js-controller iobroker 195 1.1 2.3 1038604 189012 ? Sl 19:36 0:37 io.admin.0 iobroker 226 1.6 2.2 857140 175700 ? Sl 19:36 0:53 io.javascript.0 iobroker 237 0.1 1.0 684288 82860 ? Sl 19:36 0:03 io.node-red.0 iobroker 298 0.1 1.0 689060 81324 ? Sl 19:36 0:05 io.modbus.0 iobroker 325 3.5 2.2 22020212 182608 ? Sl 19:36 1:53 node-red iobroker 332 0.1 1.0 952296 82692 ? Sl 19:36 0:04 io.netatmo.0 iobroker 365 5.2 1.9 857708 154212 ? Sl 19:36 2:45 io.shelly.0 iobroker 396 0.1 1.1 11176388 91924 ? Sl 19:37 0:04 io.backitup.0 iobroker 403 0.1 1.0 816752 80784 ? Sl 19:37 0:04 io.cloud.0 iobroker 523 0.1 1.1 689468 89564 ? Sl 19:37 0:05 io.shuttercontrol.0 iobroker 565 0.6 1.2 691616 97788 ? Sl 19:37 0:21 io.sourceanalytix.0 iobroker 596 0.2 1.0 11437464 87620 ? Sl 19:37 0:08 io.vw-connect.0 iobroker 607 0.1 1.0 686260 80708 ? Sl 19:37 0:04 io.web.0 root 1232 0.0 0.0 7504 3276 pts/0 Ss 19:49 0:00 bash root 1275 0.0 0.0 10308 3468 pts/0 S+ 19:50 0:01 top root 1288 0.0 0.0 7504 3252 pts/1 Ss 19:51 0:00 bash root 1707 0.0 0.0 10308 3484 pts/1 S+ 19:58 0:01 top root 1802 0.0 0.0 7504 3140 pts/2 Ss 20:00 0:00 bash root 1820 0.0 0.0 7240 2680 pts/2 S+ 20:00 0:00 /bin/bash /usr/bin/iob logs --watch iobroker 1821 0.1 0.9 937552 73120 pts/2 Sl+ 20:00 0:02 node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js logs --watch iobroker 3082 2.3 1.0 692332 86608 ? Sl 20:27 0:03 io.mqtt.0 root 3218 0.6 0.0 7504 3884 pts/3 Ss 20:29 0:00 bash root 3224 0.0 0.0 10100 3488 pts/3 R+ 20:29 0:00 ps auxwwDeine jetzige Ausgabe und auch die von oben sehen gut aus ( Momentaufnahme )
ich kann keine Performance einbrüche erkennen , was dieses verursachen soll bzw. warum etwas nicht bei Shuttercontrol schaltet soll . -
Deine jetzige Ausgabe und auch die von oben sehen gut aus ( Momentaufnahme )
ich kann keine Performance einbrüche erkennen , was dieses verursachen soll bzw. warum etwas nicht bei Shuttercontrol schaltet soll .@glasfaser ja ich habe ja jetzt den großteil der adapter ausgestellt. siehe ein paar posts vorher.
-
@homoran
Das hier läuft alles auf dem NAS, aber ca. 30-40% der CPU Auslaustungg fällt alleine auf den iobroker
Wobei ich immer noch viele diese MQTT Themen habe.
2023-09-16 19:27:19.626 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 19:27:19.630 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 19:27:19.828 - info: shelly.0 (12041) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032ab96370 / shellyplus1pm#a8032ab96370#1) (false) 2023-09-16 19:27:19.905 - info: shelly.0 (12041) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23ecce4 / shellyplus2pm#5443b23ecce4#1) (false) 2023-09-16 19:27:20.691 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab9088" 2023-09-16 19:27:20.920 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 19:27:21.267 - info: shelly.0 (12041) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-441793acae2c / shellyplus2pm#441793acae2c#1) (false) 2023-09-16 19:27:22.083 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 19:27:24.438 - info: modbus.0 (258) Connected to slave 192.168.1.47 2023-09-16 19:27:25.819 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8bf730" 2023-09-16 19:27:26.167 - info: shelly.0 (12041) [MQTT] Device with client id "shellyplus2pm-b8d61a876248" connected! 2023-09-16 19:27:27.759 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8dbe474" 2023-09-16 19:27:28.042 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 19:27:29.201 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e1a90" 2023-09-16 19:27:29.956 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 19:27:32.418 - info: shelly.0 (12041) [MQTT] Device with client id "shellyplus1pm-7c87ce65d794" connected! 2023-09-16 19:27:32.732 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579bd34" 2023-09-16 19:27:32.732 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 19:27:33.738 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ecce4" 2023-09-16 19:27:33.738 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96370" 2023-09-16 19:27:34.029 - error: shelly.0 (12041) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 19:27:35.198 - info: shelly.0 (12041) [MQTT] Device with client id "shellyplus1pm-a8032ab96980" connected! 2023-09-16 19:27:35.209 - info: shelly.0 (12041) [MQTT] Device with client id "shellyplus1pm-3c610579df44" connected!@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Das hier läuft alles auf dem NAS,
wieviel Kameras hast du eingebunden bzw. nimmst du im Profil auf
oder ist kein Cam Plugin !? habe kein qnap -
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Das hier läuft alles auf dem NAS,
wieviel Kameras hast du eingebunden bzw. nimmst du im Profil auf
oder ist kein Cam Plugin !? habe kein qnap@glasfaser lol, keine Kamera. EInige Dinge laufen echt unnötig...
-
@glasfaser
Siehe meine CPU Auslastung weiter oben im Thread. Das meine ich mit Performance...Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
root@iobroker:/opt/iobroker# iobroker list instances + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled system.adapter.device-watcher.0 : device-watcher : iobroker - disabled system.adapter.devices.0 : devices : iobroker - disabled system.adapter.dwd.0 : dwd : iobroker - disabled system.adapter.energiefluss.0 : energiefluss : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - disabled system.adapter.ical.0 : ical : iobroker - disabled system.adapter.influxdb.0 : influxdb : iobroker - disabled, port: 8086 system.adapter.jarvis.0 : jarvis : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.meross.0 : meross : iobroker - disabled + system.adapter.modbus.0 : modbus : iobroker - enabled system.adapter.mqtt.0 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 system.adapter.mqtt.1 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.netatmo.0 : netatmo : iobroker - enabled + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 system.adapter.pushover.0 : pushover : iobroker - disabled system.adapter.pvforecast.0 : pvforecast : iobroker - disabled system.adapter.schoolfree.0 : schoolfree : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : iobroker - enabled system.adapter.snmp.0 : snmp : iobroker - disabled system.adapter.sonos.0 : sonos : iobroker - disabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.vw-connect.0 : vw-connect : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: adminDie Auslastung auf dem NAS sehen deutlich besser aus:
Aber eben nicht so im iobroker:
top - 19:59:10 up 6:50, 0 users, load average: 3,68, 4,47, 5,70 Tasks: 19 total, 1 running, 18 sleeping, 0 stopped, 0 zombie %Cpu(s): 39,3 us, 29,7 sy, 0,2 ni, 23,4 id, 6,4 wa, 0,0 hi, 1,0 si, 0,0 st MiB Mem : 7792,2 total, 1160,6 free, 4499,3 used, 2132,3 buff/cache MiB Swap: 23447,2 total, 23009,1 free, 438,1 used. 2514,5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 365 iobroker 20 0 861548 142888 39684 S 7,6 1,8 1:18.49 io.shelly.0 173 iobroker 20 0 11,2g 397588 47524 S 5,0 5,0 2:30.45 iobroker.js-con 523 iobroker 20 0 686396 85680 45720 S 4,7 1,1 0:04.43 io.shuttercontr 325 iobroker 20 0 21,0g 192536 49516 S 4,3 2,4 0:53.08 node-red 226 iobroker 20 0 855092 173188 39564 S 0,7 2,2 0:37.47 io.javascript.0 565 iobroker 20 0 689056 95860 39600 S 0,7 1,2 0:14.53 io.sourceanalyt 1 root 20 0 7372 3676 3336 S 0,0 0,0 0:00.06 bash 195 iobroker 20 0 1035244 182472 47132 S 0,0 2,3 0:24.22 io.admin.0 237 iobroker 20 0 684288 80756 39588 S 0,0 1,0 0:02.91 io.node-red.0 298 iobroker 20 0 686500 79628 39840 S 0,0 1,0 0:03.56 io.modbus.0 332 iobroker 20 0 950760 80840 41056 S 0,0 1,0 0:03.56 io.netatmo.0 396 iobroker 20 0 10,7g 90416 47104 S 0,0 1,1 0:03.31 io.backitup.0 403 iobroker 20 0 815984 77264 40732 S 0,0 1,0 0:03.13 io.cloud.0 596 iobroker 20 0 10,9g 91620 42448 S 0,0 1,1 0:05.85 io.vw-connect.0 607 iobroker 20 0 685236 78756 39644 S 0,0 1,0 0:02.97 io.web.0 1232 root 20 0 7504 3960 3440 S 0,0 0,0 0:00.03 bash 1275 root 20 0 10308 3684 3208 R 0,0 0,0 0:00.33 top 1288 root 20 0 7504 3936 3416 S 0,0 0,0 0:00.04 bash 1707 root 20 0 10308 3684 3212 S 0,0 0,0 0:00.01 top@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
Hast du danach den Container auch neu gestartet !
Was ist dann !?
-
@glasfaser lol, keine Kamera. EInige Dinge laufen echt unnötig...
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
EInige Dinge laufen echt unnötig...
ja, u.A. JDownloader2, aber das wird ja ignoriert
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
Hast du danach den Container auch neu gestartet !
Was ist dann !?
@glasfaser ne. mache ich mal.
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
EInige Dinge laufen echt unnötig...
ja, u.A. JDownloader2, aber das wird ja ignoriert
@djmarc75 Was wäre denn eine sinnvolle Alternative: Einen Rechner oder Laptop die ganze Zeit laufen lassen?
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Ich habe mal viele Adapter, welche ich nicht ganz unbedingt benötige, beendet
Hast du danach den Container auch neu gestartet !
Was ist dann !?
@glasfaser
naja, überraend nicht, aber ich kann "fließend" mit dem iobroker arbeiten.Ich arbeite gerade daran, den 2. MQTT Adapter los zu werden.
top - 21:08:30 up 7:59, 0 users, load average: 6,13, 9,00, 8,78 Tasks: 18 total, 1 running, 17 sleeping, 0 stopped, 0 zombie %Cpu(s): 40,6 us, 35,4 sy, 3,9 ni, 15,6 id, 3,9 wa, 0,0 hi, 0,7 si, 0,0 st MiB Mem : 7792,2 total, 1098,8 free, 4598,6 used, 2094,9 buff/cache MiB Swap: 23447,2 total, 23011,1 free, 436,1 used. 2406,4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 351 iobroker 20 0 21,0g 162436 12600 S 4,3 2,0 0:44.60 node-red 176 iobroker 20 0 11,1g 370920 10616 S 4,0 4,6 1:56.80 iobroker.js-con 299 iobroker 20 0 991596 133684 12548 S 2,7 1,7 1:13.42 io.shelly.0 220 iobroker 20 0 835776 142760 12076 S 1,0 1,8 0:47.05 io.javascript.0 273 iobroker 20 0 697964 68448 12140 S 0,7 0,9 0:08.00 io.mqtt.0 439 iobroker 20 0 685236 48208 10144 S 0,7 0,6 0:02.80 io.web.0 209 iobroker 20 0 1030832 141260 10600 S 0,3 1,8 0:19.40 io.admin.0 384 iobroker 20 0 689312 56892 10360 S 0,3 0,7 0:16.62 io.sourceanalyt 858 root 20 0 10308 1552 1080 R 0,3 0,0 0:00.40 top 1 root 20 0 7372 616 268 S 0,0 0,0 0:00.06 bash 233 iobroker 20 0 684032 51912 9892 S 0,0 0,7 0:02.91 io.node-red.0 246 iobroker 20 0 686756 48672 10388 S 0,0 0,6 0:03.48 io.modbus.0 292 iobroker 20 0 949224 52260 11904 S 0,0 0,7 0:03.33 io.netatmo.0 310 iobroker 20 0 10,7g 53204 10432 S 0,0 0,7 0:03.25 io.backitup.0 332 iobroker 20 0 816240 49712 10900 S 0,0 0,6 0:03.13 io.cloud.0 377 iobroker 20 0 684860 49324 10732 S 0,0 0,6 0:03.50 io.shuttercontr 425 iobroker 20 0 10,9g 80848 14236 S 0,0 1,0 0:05.88 io.vw-connect.0 852 root 20 0 7504 1516 1072 S 0,0 0,0 0:00.04 bash -
@glasfaser
naja, überraend nicht, aber ich kann "fließend" mit dem iobroker arbeiten.Ich arbeite gerade daran, den 2. MQTT Adapter los zu werden.
top - 21:08:30 up 7:59, 0 users, load average: 6,13, 9,00, 8,78 Tasks: 18 total, 1 running, 17 sleeping, 0 stopped, 0 zombie %Cpu(s): 40,6 us, 35,4 sy, 3,9 ni, 15,6 id, 3,9 wa, 0,0 hi, 0,7 si, 0,0 st MiB Mem : 7792,2 total, 1098,8 free, 4598,6 used, 2094,9 buff/cache MiB Swap: 23447,2 total, 23011,1 free, 436,1 used. 2406,4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 351 iobroker 20 0 21,0g 162436 12600 S 4,3 2,0 0:44.60 node-red 176 iobroker 20 0 11,1g 370920 10616 S 4,0 4,6 1:56.80 iobroker.js-con 299 iobroker 20 0 991596 133684 12548 S 2,7 1,7 1:13.42 io.shelly.0 220 iobroker 20 0 835776 142760 12076 S 1,0 1,8 0:47.05 io.javascript.0 273 iobroker 20 0 697964 68448 12140 S 0,7 0,9 0:08.00 io.mqtt.0 439 iobroker 20 0 685236 48208 10144 S 0,7 0,6 0:02.80 io.web.0 209 iobroker 20 0 1030832 141260 10600 S 0,3 1,8 0:19.40 io.admin.0 384 iobroker 20 0 689312 56892 10360 S 0,3 0,7 0:16.62 io.sourceanalyt 858 root 20 0 10308 1552 1080 R 0,3 0,0 0:00.40 top 1 root 20 0 7372 616 268 S 0,0 0,0 0:00.06 bash 233 iobroker 20 0 684032 51912 9892 S 0,0 0,7 0:02.91 io.node-red.0 246 iobroker 20 0 686756 48672 10388 S 0,0 0,6 0:03.48 io.modbus.0 292 iobroker 20 0 949224 52260 11904 S 0,0 0,7 0:03.33 io.netatmo.0 310 iobroker 20 0 10,7g 53204 10432 S 0,0 0,7 0:03.25 io.backitup.0 332 iobroker 20 0 816240 49712 10900 S 0,0 0,6 0:03.13 io.cloud.0 377 iobroker 20 0 684860 49324 10732 S 0,0 0,6 0:03.50 io.shuttercontr 425 iobroker 20 0 10,9g 80848 14236 S 0,0 1,0 0:05.88 io.vw-connect.0 852 root 20 0 7504 1516 1072 S 0,0 0,0 0:00.04 bashAber es gibt bisher immernoch die MQTT-Fehler aus dem Shelly adapter:
023-09-16 21:00:47.628 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1 / shellyplus1-441793a820f4 / shellyplus1#441793a820f4#1) (false) 2023-09-16 21:00:47.629 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-485519a2a5d4 / shellyplus2pm#485519a2a5d4#1) (false) 2023-09-16 21:00:47.629 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199a5d7c / shellyplus1pm#4855199a5d7c#1) (false) 2023-09-16 21:00:48.521 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 21:00:48.525 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032abc230c / shellyplus1pm#a8032abc230c#1) (false) 2023-09-16 21:00:48.525 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-4022d8da969c / shellyplus2pm#4022d8da969c#1) (false) 2023-09-16 21:00:49.022 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 21:00:49.680 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 21:00:51.658 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 21:00:51.659 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 21:00:51.660 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 21:00:51.876 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 21:00:51.878 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 21:00:52.375 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 21:00:52.375 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 21:00:52.376 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 21:00:52.788 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 21:00:53.013 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:00:53.860 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8abb7c / shellyplus2pm#b8d61a8abb7c#1) (false) 2023-09-16 21:00:57.345 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 21:01:13.014 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:01:33.016 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 -
@schtallone sollte so aussehen
Kannst Du mir auch bei einem Thema mit dem Mosquitto Broker (den ich als Docker Container laufen habe), helfen?
Um die Wallbox (openWB) als zusätzlichen MQTT Broker los zu werden, muss ich eine Bridge auf dem Mosquitto simulieren (welcher ja der Broker ist), um die Daten von dem openWB Broker abzuholen.
Ich verwende dabei eine Config des Mosquitto Brokers, welche die Bridge erzeugt:
persistence true persistence_location /mosquitto/data/ user mosquitto listener 1883 allow_anonymous true log_dest file /mosquitto/log/mosquitto.log log_dest stdout # # Brücke zur openWB # connection openwb address 192.168.1.134:1883 #http://openwb:1883 start_type automatic topic openWB/# both 2 local_clientid openwb.mosquitto try_private false cleansession trueLeider komme ich mit der IP der openWB in Probleme. DIese ist ja nicht statisch (geht nicht bei openWB), sodass ich gerne http://openwb:1883 verwenden würde. DOch dabei bekomme ich folgende Fehlermeldung im Broker:
2023-09-16T19:02:16.571989046Z 1694890838: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.571999865Z 1694890838: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572010809Z 1694890869: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.572021682Z 1694890869: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572036798Z 1694890893: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.572047831Z 1694890893: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572058606Z 1694890924: Connecting bridge openwb (http://openwb:1883)Vielen Dank.
-
Kannst Du mir auch bei einem Thema mit dem Mosquitto Broker (den ich als Docker Container laufen habe), helfen?
Um die Wallbox (openWB) als zusätzlichen MQTT Broker los zu werden, muss ich eine Bridge auf dem Mosquitto simulieren (welcher ja der Broker ist), um die Daten von dem openWB Broker abzuholen.
Ich verwende dabei eine Config des Mosquitto Brokers, welche die Bridge erzeugt:
persistence true persistence_location /mosquitto/data/ user mosquitto listener 1883 allow_anonymous true log_dest file /mosquitto/log/mosquitto.log log_dest stdout # # Brücke zur openWB # connection openwb address 192.168.1.134:1883 #http://openwb:1883 start_type automatic topic openWB/# both 2 local_clientid openwb.mosquitto try_private false cleansession trueLeider komme ich mit der IP der openWB in Probleme. DIese ist ja nicht statisch (geht nicht bei openWB), sodass ich gerne http://openwb:1883 verwenden würde. DOch dabei bekomme ich folgende Fehlermeldung im Broker:
2023-09-16T19:02:16.571989046Z 1694890838: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.571999865Z 1694890838: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572010809Z 1694890869: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.572021682Z 1694890869: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572036798Z 1694890893: Connecting bridge openwb (http://openwb:1883) 2023-09-16T19:02:16.572047831Z 1694890893: Error creating bridge: Name does not resolve. 2023-09-16T19:02:16.572058606Z 1694890924: Connecting bridge openwb (http://openwb:1883)Vielen Dank.
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Kannst Du mir auch bei einem Thema mit dem Mosquitto Broker (den ich als Docker Container laufen habe), helfen?
leider nein, das ist nicht so mein Gebiet
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Kannst Du mir auch bei einem Thema mit dem Mosquitto Broker (den ich als Docker Container laufen habe), helfen?
leider nein, das ist nicht so mein Gebiet
@crunchip
Ich hab mal was selber hinbekommen: lolman muss das http:// weg lassen.
persistence true persistence_location /mosquitto/data/ user mosquitto listener 1883 allow_anonymous true log_dest file /mosquitto/log/mosquitto.log log_dest stdout # # Brücke zur openWB # connection openwb address openwb:1883 #192.168.1.134:1883 #http://openwb:1883 start_type automatic topic openWB/# both 2 local_clientid openwb.mosquitto try_private false cleansession true -
@glasfaser Der iobroker ist total träge. Lässt sich nicht aufrufen. Häufig Timeout. Einige Adapter, wie z.B. Shuttercontrol haben ganrichts gesteuert mehr.
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Der iobroker ist total träge. Lässt sich nicht aufrufen. Häufig Timeout.
und
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Wenn ich auf die Instanzen im iobroker (WebInterface) gehen will, sagt der manchmal das er das nicht anzeigen kann, wegen timeout
ist doch kein Wunder
bei einer
@schtallone sagte in Performance Probleme durch Shelly Adapter?:load average: 6,13, 9,00, 8,78
hat dein System 3-4.5 x soviele Aufgaben zu erledigen, eie es kann.
dann kommt es zum Rückstau der Abarbeitung.Wenn die neuen Aufträge nicht weniger werden, schaukelt es sich immer weiter hoch.
ist halt genau wie auf der Autobahn.
wenn es dich nicht vollständig in der CPU Auslastung widerspiegelt sind auch I/O Vorgänge zu betrachtrn, die sich auch in der Load niederschlagen.
Wenn irgendwo eine Datenleitung zu langsam ist, staut es da.ich kenne ich nicht mit containern aus, aber kann in einem von 7 Containern der zugewiesene Ram so groß sein wie das gesamte NAS besitzt?
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Der iobroker ist total träge. Lässt sich nicht aufrufen. Häufig Timeout.
und
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Wenn ich auf die Instanzen im iobroker (WebInterface) gehen will, sagt der manchmal das er das nicht anzeigen kann, wegen timeout
ist doch kein Wunder
bei einer
@schtallone sagte in Performance Probleme durch Shelly Adapter?:load average: 6,13, 9,00, 8,78
hat dein System 3-4.5 x soviele Aufgaben zu erledigen, eie es kann.
dann kommt es zum Rückstau der Abarbeitung.Wenn die neuen Aufträge nicht weniger werden, schaukelt es sich immer weiter hoch.
ist halt genau wie auf der Autobahn.
wenn es dich nicht vollständig in der CPU Auslastung widerspiegelt sind auch I/O Vorgänge zu betrachtrn, die sich auch in der Load niederschlagen.
Wenn irgendwo eine Datenleitung zu langsam ist, staut es da.ich kenne ich nicht mit containern aus, aber kann in einem von 7 Containern der zugewiesene Ram so groß sein wie das gesamte NAS besitzt?
Ja wenn ständig, aus welchem Grund auch immer, fast 40-50% der Recourcen in den iobroker gehen, bleibt nicht viel anderes.
Ich habe ja jetzt einige Adapter deaktiviert sowie den 2. MQTT Adapter ersetzt / überflüssig gemacht.
Immerhin ist nun die Performance besser und auch der Shelly Adpater ist etwas ruhiger geworden.
Aber auf die angestrebten Werte des load average von ca. 1 ist es meilenweit entfernt. Dies Frage ist, ob dies generell bei dem NAS jetzt so ist, oder ob es an meinem Setup liegt.
2023-09-16 20:59:45.699 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8abb7c / shellyplus2pm#b8d61a8abb7c#1) (false) 2023-09-16 20:59:49.054 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 20:59:50.424 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 20:59:50.451 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 20:59:50.464 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 20:59:52.141 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 20:59:52.185 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 20:59:52.186 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 20:59:52.186 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 20:59:52.186 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 20:59:52.514 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 20:59:52.514 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 20:59:52.515 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 20:59:52.602 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 20:59:52.925 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:00:13.003 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:00:30.628 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-3c610579df44" connected! 2023-09-16 21:00:32.528 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23d6114" connected! 2023-09-16 21:00:32.622 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23fd3dc" connected! 2023-09-16 21:00:32.841 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-7c87ce65d970" connected! 2023-09-16 21:00:33.015 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:00:33.145 - error: modbus.0 (246) Can not set value: Attempt to access memory outside buffer bounds 2023-09-16 21:00:36.023 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-7c87ce65d794" connected! 2023-09-16 21:00:36.054 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-441793acae2c" connected! 2023-09-16 21:00:36.055 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-b8d61a8b94fc" connected! 2023-09-16 21:00:37.229 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-485519a2a5d4" connected! 2023-09-16 21:00:37.402 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1-441793a820f4" connected! 2023-09-16 21:00:37.421 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-4855199a5d7c" connected! 2023-09-16 21:00:38.112 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-4022d8da969c" connected! 2023-09-16 21:00:38.327 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-a8032abc230c" connected! 2023-09-16 21:00:40.312 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-3c610579df44 / shellyplus1pm#3c610579df44#1) (false) 2023-09-16 21:00:42.541 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23d6114 / shellyplus2pm#5443b23d6114#1) (false) 2023-09-16 21:00:42.607 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7c87ce65d970 / shellyplus1pm#7c87ce65d970#1) (false) 2023-09-16 21:00:42.611 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23fd3dc / shellyplus2pm#5443b23fd3dc#1) (false) 2023-09-16 21:00:43.878 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-b8d61a8abb7c" connected! 2023-09-16 21:00:44.249 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7c87ce65d794 / shellyplus1pm#7c87ce65d794#1) (false) 2023-09-16 21:00:45.857 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-441793acae2c / shellyplus2pm#441793acae2c#1) (false) 2023-09-16 21:00:46.090 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8b94fc / shellyplus2pm#b8d61a8b94fc#1) (false) 2023-09-16 21:00:47.628 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1 / shellyplus1-441793a820f4 / shellyplus1#441793a820f4#1) (false) 2023-09-16 21:00:47.629 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-485519a2a5d4 / shellyplus2pm#485519a2a5d4#1) (false) 2023-09-16 21:00:47.629 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199a5d7c / shellyplus1pm#4855199a5d7c#1) (false) 2023-09-16 21:00:48.521 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 21:00:48.525 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032abc230c / shellyplus1pm#a8032abc230c#1) (false) 2023-09-16 21:00:48.525 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-4022d8da969c / shellyplus2pm#4022d8da969c#1) (false) 2023-09-16 21:00:49.022 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 21:00:49.680 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 21:00:51.658 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 21:00:51.659 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 21:00:51.660 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 21:00:51.876 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 21:00:51.878 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 21:00:52.375 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 21:00:52.375 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 21:00:52.376 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 21:00:52.788 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 21:00:53.013 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:00:53.860 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8abb7c / shellyplus2pm#b8d61a8abb7c#1) (false) 2023-09-16 21:00:57.345 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 21:01:13.014 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:01:33.016 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:01:35.510 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-3c610579df44" connected! 2023-09-16 21:01:37.076 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-7c87ce65d970" connected! 2023-09-16 21:01:39.517 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-441793acae2c" connected! 2023-09-16 21:01:39.692 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23fd3dc" connected! 2023-09-16 21:01:40.011 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23d6114" connected! 2023-09-16 21:01:40.925 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-7c87ce65d794" connected! 2023-09-16 21:01:42.215 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-485519a2a5d4" connected! 2023-09-16 21:01:42.388 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-a8032abc230c" connected! 2023-09-16 21:01:43.321 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-b8d61a8b94fc" connected! 2023-09-16 21:01:45.253 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1-441793a820f4" connected! 2023-09-16 21:01:45.277 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-4855199a5d7c" connected! 2023-09-16 21:01:46.690 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-4022d8da969c" connected! 2023-09-16 21:01:49.449 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-b8d61a8abb7c" connected! 2023-09-16 21:01:49.517 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-441793acae2c / shellyplus2pm#441793acae2c#1) (false) 2023-09-16 21:01:49.592 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23fd3dc / shellyplus2pm#5443b23fd3dc#1) (false) 2023-09-16 21:01:49.957 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23d6114 / shellyplus2pm#5443b23d6114#1) (false) 2023-09-16 21:01:50.738 - info: shelly.0 (299) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7c87ce65d794 / shellyplus1pm#7c87ce65d794#1) (false) 2023-09-16 21:01:51.216 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 21:01:51.251 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 21:01:51.252 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 21:01:51.252 - error: shelly.0 (299) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 21:01:53.018 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:02:13.020 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:02:16.549 - info: mqtt.0 (273) Disconnected from 192.168.1.8: undefined 2023-09-16 21:02:26.552 - info: mqtt.0 (273) Reconnected to 192.168.1.8 2023-09-16 21:02:29.760 - info: mqtt.0 (273) Disconnected from 192.168.1.8: undefined 2023-09-16 21:02:33.022 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:02:39.761 - info: mqtt.0 (273) Reconnected to 192.168.1.8 2023-09-16 21:02:42.870 - info: mqtt.0 (273) Disconnected from 192.168.1.8: undefined 2023-09-16 21:02:44.027 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:02:45.169 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23fd3dc" connected! 2023-09-16 21:02:46.936 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus1pm-7c87ce65d794" connected! 2023-09-16 21:02:47.496 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-441793acae2c" connected! 2023-09-16 21:02:47.960 - info: shelly.0 (299) [MQTT] Device with client id "shellyplus2pm-5443b23d6114" connected! 2023-09-16 21:02:52.871 - info: mqtt.0 (273) Reconnected to 192.168.1.8 2023-09-16 21:02:55.927 - info: mqtt.0 (273) Disconnected from 192.168.1.8: undefined 2023-09-16 21:03:04.056 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:03:05.930 - info: mqtt.0 (273) Reconnected to 192.168.1.8 2023-09-16 21:03:05.932 - info: mqtt.0 (273) Connected to 192.168.1.8 2023-09-16 21:03:05.932 - info: mqtt.0 (273) Subscribe on "#" 2023-09-16 21:03:11.809 - info: mqtt.0 (273) Client: Changed type of "mqtt.0.openWB.config.set.SmartHome.Devices.8.device_ip" from "string" to "mixed" 2023-09-16 21:03:12.703 - info: mqtt.0 (273) All states published 2023-09-16 21:03:13.772 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhExported, feature disabled (or below threshold) processing normally) 2023-09-16 21:03:13.802 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhImported, feature disabled (or below threshold) processing normally) 2023-09-16 21:03:23.044 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:03:43.046 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:04:03.070 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:04:23.073 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:04:43.049 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:05:03.052 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:05:23.050 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:05:43.052 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:06:03.058 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:06:23.062 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:06:34.261 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:06:54.263 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:07:13.237 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:07:33.240 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:07:53.245 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:08:13.247 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:08:33.252 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:08:53.255 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:09:13.253 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:09:33.256 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:09:44.262 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:10:04.266 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:10:23.254 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:10:43.256 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:11:03.257 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:11:23.266 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:11:34.275 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:11:54.279 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:12:13.268 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:12:33.270 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:12:53.266 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:13:13.274 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:13:24.319 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:13:44.323 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:14:03.327 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:14:23.330 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:14:34.311 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:14:54.313 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:15:13.366 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:15:33.369 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:15:45.363 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:16:05.365 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:16:23.348 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:16:43.352 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:17:03.357 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:17:23.358 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:17:43.358 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:18:03.360 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:18:23.366 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:18:36.169 - info: admin.0 (209) ==> Connected system.user.admin from ::ffff:192.168.1.119 2023-09-16 21:18:43.370 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:19:02.381 - info: host.iobroker stopInstance system.adapter.mqtt.0 (force=false, process=true) 2023-09-16 21:19:02.397 - info: mqtt.0 (273) Got terminate signal TERMINATE_YOURSELF 2023-09-16 21:19:02.405 - info: mqtt.0 (273) Disconnected from 192.168.1.8: undefined 2023-09-16 21:19:02.604 - info: host.iobroker stopInstance system.adapter.mqtt.0 send kill signal 2023-09-16 21:19:02.904 - info: mqtt.0 (273) terminating 2023-09-16 21:19:02.905 - info: mqtt.0 (273) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-09-16 21:19:03.369 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:19:03.471 - info: host.iobroker instance system.adapter.mqtt.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-09-16 21:19:05.844 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 1777 2023-09-16 21:19:12.783 - info: mqtt.0 (1777) starting. Version 4.1.1 in /opt/iobroker/node_modules/iobroker.mqtt, node: v18.17.1, js-controller: 5.0.12 2023-09-16 21:19:14.615 - info: mqtt.0 (1777) Try to connect to mqtt://192.168.1.8:1883 with clientId=iobroker.mqtt.0 2023-09-16 21:19:14.827 - info: mqtt.0 (1777) Connected to 192.168.1.8 2023-09-16 21:19:14.836 - info: mqtt.0 (1777) Subscribe on "#" 2023-09-16 21:19:18.616 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhImported, feature disabled (or below threshold) processing normally) 2023-09-16 21:19:21.437 - info: admin.0 (209) ==> Connected system.user.admin from ::ffff:192.168.1.119 2023-09-16 21:19:23.372 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:19:27.906 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhExported, feature disabled (or below threshold) processing normally) 2023-09-16 21:19:27.914 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhImported, feature disabled (or below threshold) processing normally) 2023-09-16 21:19:30.570 - info: mqtt.0 (1777) All states published 2023-09-16 21:19:43.413 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:20:03.415 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:20:23.394 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:20:43.397 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:21:03.396 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:21:23.401 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:21:34.417 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:22:01.527 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:22:14.424 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:22:34.427 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:22:53.414 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:23:13.417 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:23:24.422 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:23:44.424 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:24:01.068 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:24:21.070 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:24:33.429 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:24:53.431 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:25:13.425 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:25:33.428 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:25:44.444 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:26:04.446 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:26:23.469 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:26:43.472 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:26:55.458 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:27:15.459 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:27:33.439 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:27:53.443 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:28:13.460 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:28:33.461 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:28:53.457 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:29:13.461 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:29:33.467 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:29:49.339 - info: mqtt.0 (1777) Disconnected from 192.168.1.8: undefined 2023-09-16 21:29:53.471 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:29:59.340 - info: mqtt.0 (1777) Reconnected to 192.168.1.8 2023-09-16 21:30:13.474 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:30:17.722 - info: mqtt.0 (1777) Disconnected from 192.168.1.8: undefined 2023-09-16 21:30:27.722 - info: mqtt.0 (1777) Reconnected to 192.168.1.8 2023-09-16 21:30:30.838 - info: mqtt.0 (1777) Disconnected from 192.168.1.8: undefined 2023-09-16 21:30:33.475 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:30:40.841 - info: mqtt.0 (1777) Reconnected to 192.168.1.8 2023-09-16 21:30:43.894 - info: mqtt.0 (1777) Disconnected from 192.168.1.8: undefined 2023-09-16 21:30:53.569 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:30:53.895 - info: mqtt.0 (1777) Reconnected to 192.168.1.8 2023-09-16 21:30:53.923 - info: mqtt.0 (1777) Connected to 192.168.1.8 2023-09-16 21:30:53.923 - info: mqtt.0 (1777) Subscribe on "#" 2023-09-16 21:30:57.322 - info: mqtt.0 (1777) All states published 2023-09-16 21:30:57.930 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhExported, feature disabled (or below threshold) processing normally) 2023-09-16 21:30:57.942 - info: sourceanalytix.0 (384) Device reset detected for alias.0.Netz.WhImported, feature disabled (or below threshold) processing normally) 2023-09-16 21:31:13.584 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:31:33.476 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:31:53.479 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:32:13.482 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:32:33.484 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:32:45.493 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:33:05.495 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:33:23.478 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:33:43.484 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:33:54.492 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:34:14.494 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:34:33.484 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:34:53.487 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:35:04.490 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:35:24.492 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:35:43.491 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:35:48.765 - info: mqtt.0 (1777) send2Server mqtt.0.Jalousie_Hauptschalter.online[Jalousie_Hauptschalter/online] 2023-09-16 21:35:48.799 - info: mqtt.0 (1777) Client: Changed type of "mqtt.0.Jalousie_Hauptschalter.online" from "boolean" to "mixed" 2023-09-16 21:35:48.831 - warn: mqtt.0 (1777) Object mqtt.0.Jalousie_Hauptschalter.online is invalid: obj.type has to exist 2023-09-16 21:35:48.832 - warn: mqtt.0 (1777) This object will not be created in future versions. Please report this to the developer. 2023-09-16 21:36:03.493 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:36:23.500 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:36:43.505 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:36:54.510 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:37:14.511 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:37:33.541 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:37:53.543 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:37:53.617 - error: modbus.0 (246) Can not set value: Attempt to access memory outside buffer bounds 2023-09-16 21:38:13.588 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:38:33.592 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:38:48.646 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:39:08.648 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:39:24.591 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:39:44.593 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:40:02.583 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:40:22.585 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:40:43.600 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:41:03.602 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:41:23.604 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:41:43.607 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:42:03.596 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:42:23.599 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:42:43.601 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:42:50.451 - info: sourceanalytix.0 (384) Updating SourceAnalytix configuration for : alias.0.Keller.Wasserzaehler.ACTUAL 2023-09-16 21:43:03.603 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:43:23.603 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:43:43.605 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:44:03.600 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:44:23.603 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:44:43.614 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:45:03.616 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:45:23.611 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:45:43.615 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:46:03.612 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:46:23.617 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:46:43.622 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:47:03.623 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:47:23.625 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:47:43.628 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:48:03.627 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:48:23.630 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:48:43.631 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:49:03.633 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:49:23.628 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:49:43.630 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:50:03.636 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:50:23.639 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:50:35.650 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:50:55.653 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:51:13.631 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:51:33.633 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:51:53.631 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:52:13.633 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:52:15.164 - info: admin.0 (209) <== Disconnect system.user.admin from ::ffff:192.168.1.119 admin 2023-09-16 21:52:25.249 - info: host.iobroker iobroker del mqtt.1 --debug 2023-09-16 21:52:31.413 - info: host.iobroker iobroker Delete instance "mqtt.1" 2023-09-16 21:52:31.532 - info: host.iobroker iobroker host.iobroker Counted 1 instances of mqtt.1 2023-09-16 21:52:31.605 - info: host.iobroker iobroker host.iobroker Counted 1 channels of mqtt.1 2023-09-16 21:52:31.738 - info: host.iobroker iobroker host.iobroker Counted 61 states of mqtt.1 2023-09-16 21:52:31.781 - info: host.iobroker iobroker host.iobroker Counted 15 states of system.adapter.mqtt.1 2023-09-16 21:52:31.805 - info: host.iobroker iobroker host.iobroker Counted 66 states (io.mqtt.1.*) from states 2023-09-16 21:52:32.024 - info: host.iobroker iobroker host.iobroker Counted 15 states (system.adapter.mqtt.1.*) from states 2023-09-16 21:52:33.638 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:52:34.148 - info: host.iobroker iobroker host.iobroker Counted 26 objects of mqtt.1 2023-09-16 21:52:34.155 - info: host.iobroker iobroker host.iobroker Deleting 104 object(s). 2023-09-16 21:52:34.511 - info: host.iobroker object deleted system.adapter.mqtt.1 2023-09-16 21:52:34.512 - info: host.iobroker iobroker host.iobroker Deleting 81 state(s). 2023-09-16 21:52:35.759 - info: host.iobroker iobroker exit 0 2023-09-16 21:52:53.640 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:53:13.653 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:53:33.655 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:53:53.653 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:54:13.655 - info: modbus.0 (246) Connected to slave 192.168.1.47 2023-09-16 21:54:33.660 - info: modbus.0 (246) Disconnected from slave 192.168.1.47 2023-09-16 21:54:53.666 - info: modbus.0 (246) Connected to slave 192.168.1.47
333
Online32.4k
Users81.3k
Topics1.3m
Posts