Performance Probleme durch Shelly Adapter?

Schtallone

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 true

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

crunchip

@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

@crunchip
Ich hab mal was selber hinbekommen: lol

man 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

Homoran

@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

@homoran

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

Glasfaser

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

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

Der müllt dir aber auch dein Log voll

ist der Modbus Teilnehmer im Standby !?

Schtallone · 2023-09-16 21:37:53.543 - info: modbus.0 (246) Connected to slave 192.168.1.47

@glasfaser ja Modbus. EIn weiteres Thema.

Ich habe einige Zähler über Modbus in den iobroker integriert. Die Daten kommen auch ,aber es gibt periodisch wohl Fehler bei Lesen / Schreiben der Daten. Hier kann man einiges konfiggurieren, wo ichh aber noch keine zufriedenestellende Einstellung gefunden habe.

Glasfaser

@schtallone

Sorry aber ... bei dir ist eine Dauerbaustelle .. da kommt immer mehr dazu

deshalb schon oben erwähnt zu " BETA Tester "....

Schtallone

@glasfaser naja einiges haben wir ja schon dank Eurer Hilfe verbessern können.

DJMarc75

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

einiges haben wir ja schon dank Eurer Hilfe verbessern können

aber vieles ist bis jetzt noch "geheim" - leider

Homoran

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

@glasfaser naja einiges haben wir ja schon dank Eurer Hilfe verbessern können.

aber das ist nur Flickschusterei!

wie kommt man dazu 2 MQTT Instanzen und einen weiteten MQTT Broker in Form von Mosquitto zu betreiben?
Ich kann mir vorstellen, dass hier noch einiges ebenfalls "seltsam" gestrickt ist.

Schtallone

@djmarc75 was möchtest Du bitte wissen, was geheim sein soll?

Schtallone

@homoran gut möglich, daher suche ich ja support hier im Forum. Sorry das ich Euch "arbeit mache". Wenn es nicht gewünscht ist, dann können wir an dieser stelle auch den support beenden. Ich mache das ja nicht, um irgendjemanden extra zu ärgern oder weil ich schlechtes im Sinn habe.

Glasfaser

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

dann können wir an dieser stelle auch den support beenden.

Nochmal :
Es ist erstmal ein Unterschied ob du im Beta Bereich bist ,
du möchtest bzw. ich sehe auch das du ein produktives System für dein Haus/Wohnung hast , daher ist es erstmal zu empfehlen in Stable zu bleiben ,
wenn du ein Beta Adapter brauchts dann pickst du Ihn dir raus .

Auch im anderen Thread hast du auch erstmal etwas gemacht , was man so nicht machen solllte .

Daher ... wir helfen hier gerne , aber es kommt immer nach und nach mehr was wir erst in weiteren Logs sehen !

crunchip

@schtallone dann beiß mal in den sauren Apfel und schalte von Adapterseite mal nur ein "Notprogramm", also nur das aller nötigste an Adapter laufen lassen.
und dann die Kiste mal neu durchstarten

anschließend den load beobachten

wenn du dann wieder annähernd an ein load von 1 kommst, Adapter für Adapter zuschalten und warten/beobachten

Schtallone

@glasfaser ich werde den Beta Bereich umstellen.

Homoran

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

was möchtest Du bitte wissen, was geheim sein soll?

es wurde bereits mehrfach gefragt, was sonst noch auf dem NAS läuft.
Kaneras sind es nicht.
aber 7 Container gibt es ja nicht ohne grund.

so taucht immer wieder etwas auf, was mehr Fragen aufwirft alsxes beantwortet.
Das lässt vermuten, dass wir noch lange nicht alles wissen um sinnvoll helfen zu können.

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

Wenn es nicht gewünscht ist, dann können wir an dieser stelle auch den support beenden.

nöö, kommt gar nicht in Frage!

@schtallone sagte in Performance Probleme durch Shelly Adapter?:

Ich mache das ja nicht, um irgendjemanden extra zu ärgern oder weil ich schlechtes im Sinn habe.

Das hoffe ich :grin:

Wie gesagt ist der Celeron "eigentlich" ausreichend, ebenso die 8GB RAM.

ich würde ja am liebsten sagen: leg den Container still und mach einen neuen mit einem flammneuen iobroker auf.
und bau diesen dann sukzessive neu auf.

Die massive Load ist weitestgehend nicht auf CPU Auslastung zurückzuführen.
Da muss irgendetwas massiv verkonfiguriert sein.

Schtallone

@crunchip
Werde ich morgen mal machen. Ich habe ja schon abgespeckt und einige Adpater gestoppt. Notprogramm ist dies noch nicht....

Ich habe mal überlegt, auch Nodered auszzulagern aus dem iobroker, keine Ahnung ob das am Ende sinnvoll ist.

Jetzt sieht es so aus:

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                                 - disabled
  system.adapter.device-watcher.0         : device-watcher        : iobroker                                 - disabled
  system.adapter.devices.0                : devices               : iobroker                                 - disabled
  system.adapter.dwd.0                    : dwd                   : iobroker                                 -  enabled
  system.adapter.energiefluss.0           : energiefluss          : iobroker                                 - disabled
  system.adapter.feiertage.0              : feiertage             : iobroker                                 -  enabled
  system.adapter.ical.0                   : ical                  : iobroker                                 -  enabled
  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                                 -  enabled, 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: admin

top - 22:34:01 up  9:25,  0 users,  load average: 6,13, 6,39, 6,50
Tasks:  28 total,   3 running,  25 sleeping,   0 stopped,   0 zombie
%Cpu(s): 41,4 us, 25,2 sy,  0,5 ni, 22,7 id,  9,5 wa,  0,0 hi,  0,7 si,  0,0 st
MiB Mem :   7792,2 total,   1001,4 free,   4856,3 used,   1934,5 buff/cache
MiB Swap:  23447,2 total,  23011,1 free,    436,1 used.   2173,6 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                                                                                                                                                                                                           
  299 iobroker  20   0  994924 133608  12828 R   6,0   1,7   4:51.51 io.shelly.0                                                                                                                                                                                                                                                                       
  351 iobroker  20   0   21,0g 182616  15672 R   6,0   2,3   3:58.96 node-red                                                                                                                                                                                                                                                                          
  176 iobroker  20   0   11,2g 414532  16260 S   5,6   5,2   7:46.99 iobroker.js-con                                                                                                                                                                                                                                                                   
  220 iobroker  20   0  884460 161336  13236 S   1,7   2,0   1:47.20 io.javascript.0                                                                                                                                                                                                                                                                   
  384 iobroker  20   0  718876  85080  12648 S   0,3   1,1   0:47.09 io.sourceanalyt                                                                                                                                                                                                                                                                   
 1777 iobroker  20   0  712044 108284  38892 S   0,3   1,4   0:29.56 io.mqtt.0                                                                                                                                                                                                                                                                         
    1 root      20   0    7372    616    268 S   0,0   0,0   0:00.06 bash                                                                                                                                                                                                                                                                              
  209 iobroker  20   0 1095072 182508  16248 S   0,0   2,3   1:10.26 io.admin.0                                                                                                                                                                                                                                                                        
  233 iobroker  20   0  685312  56048  11996 S   0,0   0,7   0:05.39 io.node-red.0                                                                                                                                                                                                                                                                     
  246 iobroker  20   0  692132  55916  12340 S   0,0   0,7   0:08.45 io.modbus.0                                                                                                                                                                                                                                                                       
  292 iobroker  20   0  953320  57272  13664 S   0,0   0,7   0:07.30 io.netatmo.0                                                                                                                                                                                                                                                                      
  310 iobroker  20   0   10,7g  58312  12472 S   0,0   0,7   0:05.79 io.backitup.0                                                                                                                                                                                                                                                                     
  377 iobroker  20   0  688956  54456  12660 S   0,0   0,7   0:06.58 io.shuttercontr                                                                                                                                                                                                                                                                   
  425 iobroker  20   0   10,9g  70112  15016 S   0,0   0,9   0:12.87 io.vw-connect.0                                                                                                                                                                                                                                                                   
  439 iobroker  20   0  688308  54128  12236 S   0,0   0,7   0:05.52 io.web.0                                                                                                                                                                                                                                                                          
  852 root      20   0    7504   1516   1072 S   0,0   0,0   0:00.04 bash                                                                                                                                                                                                                                                                              
  858 root      20   0   10308   1552   1080 D   0,0   0,0   0:04.43 top                                                                                                                                                                                                                                                                               
 1329 root      20   0    7504   3744   3296 S   0,0   0,0   0:00.03 bash                                                                                                                                                                                                                                                                              
 1340 root      20   0    7240   3260   3036 S   0,0   0,0   0:00.00 iob                                                                                                                                                                                                                                                                               
 1341 iobroker  20   0  938324  73012  38640 S   0,0   0,9   0:04.20 node                                                                                                                                                                                                                                                                              
 3286 root      20   0    7504   3792   3360 S   0,0   0,0   0:00.03 bash                                                                                                                                                                                                                                                                              
 3292 root      20   0   10308   3552   3084 S   0,0   0,0   0:02.23 top                                                                                                                                                                                                                                                                               
 3457 root      20   0    7504   3744   3316 S   0,0   0,0   0:00.04 bash

Schtallone

@homoran

das läuft noch in den Containern

Schtallone

@homoran said in Performance Probleme durch Shelly Adapter?:

Wie gesagt ist der Celeron "eigentlich" ausreichend, ebenso die 8GB RAM.

ich würde ja am liebsten sagen: leg den Container still und mach einen neuen mit einem flammneuen iobroker auf.
und bau diesen dann sukzessive neu auf.

Die massive Load ist weitestgehend nicht auf CPU Auslastung zurückzuführen.
Da muss irgendetwas massiv verkonfiguriert sein.

Aber die CPU Auslastung des NAS war ja oft bei 100%...

Community Forum

NEWS

Performance Probleme durch Shelly Adapter?

Support us

816

32.4k

81.5k

1.3m