Performance Probleme durch Shelly Adapter?
-
@glasfaser weiterhin Performance. Habe oft eine Minute oder so keine Rückmeldung vom iob
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Habe oft eine Minute oder so keine Rückmeldung vom iob
ioBroker Log zeigen , laut deinem Screenshot´s hast du errors vorhanden .
-
-09-16 15:26:54.769 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-a8032abc230c" connected! 2023-09-16 15:26:55.563 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-b8d61a8b94fc" connected! 2023-09-16 15:26:57.221 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-5443b23e5f74" connected! 2023-09-16 15:26:57.330 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-5443b23e1a90" connected! 2023-09-16 15:26:57.580 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032ab96980 / shellyplus1pm#a8032ab96980#1) (false) 2023-09-16 15:26:58.601 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab94e10" 2023-09-16 15:26:58.602 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ecce4" 2023-09-16 15:26:58.602 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8dbe474" 2023-09-16 15:26:58.602 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 15:26:58.603 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 15:26:58.603 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 15:26:58.603 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 15:26:58.603 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96370" 2023-09-16 15:26:58.604 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab9088" 2023-09-16 15:26:58.604 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579bd34" 2023-09-16 15:26:58.604 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8bf730" 2023-09-16 15:26:59.530 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96980" 2023-09-16 15:26:59.531 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96370" 2023-09-16 15:26:59.532 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 15:26:59.532 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 15:26:59.532 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 15:26:59.532 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96980" 2023-09-16 15:26:59.532 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 15:26:59.533 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579bd34" 2023-09-16 15:26:59.575 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a876248" 2023-09-16 15:26:59.590 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 15:26:59.606 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8bf730" 2023-09-16 15:26:59.610 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 15:26:59.853 - info: cloud.0 (358) Trying to connect as system.user.admin to cloud 2023-09-16 15:27:00.342 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-4855199a5d7c" connected! 2023-09-16 15:27:00.610 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-b8d61a876248" connected! 2023-09-16 15:27:01.605 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-3c610579bd34" connected! 2023-09-16 15:27:02.529 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-3c610579df44 / shellyplus1pm#3c610579df44#1) (false) 2023-09-16 15:27:02.676 - error: shelly.0 (2171) [MQTT] (Shelly?) device unknown, configuration for client with id "nodered_078fd4157ed96545" does not exist! 2023-09-16 15:27:02.676 - error: shelly.0 (2171) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2023-09-16 15:27:02.676 - info: shelly.0 (2171) [MQTT] Client Error: (nodered_078fd4157ed96545 / nodered_078fd4157ed96545 / undefined) (Error: Invalid return code) 2023-09-16 15:27:06.668 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032abc230c / shellyplus1pm#a8032abc230c#1) (false) 2023-09-16 15:27:07.506 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a863524" 2023-09-16 15:27:07.507 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 15:27:07.508 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8b94fc / shellyplus2pm#b8d61a8b94fc#1) (false) 2023-09-16 15:27:07.509 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-4022d8da969c" connected! 2023-09-16 15:27:07.510 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-b8d61a863524" connected! 2023-09-16 15:27:07.510 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-b8d61a8bf730" connected! 2023-09-16 15:27:07.535 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23e1a90 / shellyplus2pm#5443b23e1a90#1) (false) 2023-09-16 15:27:07.536 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23e5f74 / shellyplus2pm#5443b23e5f74#1) (false) 2023-09-16 15:27:08.625 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-5443b23ecce4" connected! 2023-09-16 15:27:09.698 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 15:27:09.699 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 15:27:09.699 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 15:27:09.700 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a876248" 2023-09-16 15:27:09.701 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e1a90" 2023-09-16 15:27:09.701 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplusi4-c049ef89b85c" 2023-09-16 15:27:09.701 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 15:27:09.707 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e5f74" 2023-09-16 15:27:09.708 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 15:27:09.708 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8dbe474" 2023-09-16 15:27:09.708 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 15:27:09.806 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab94e10" 2023-09-16 15:27:09.978 - info: modbus.0 (258) Connected to slave 192.168.1.47 2023-09-16 15:27:10.718 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-4855199a5d7c / shellyplus1pm#4855199a5d7c#1) (false) 2023-09-16 15:27:10.728 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a876248 / shellyplus2pm#b8d61a876248#1) (false) 2023-09-16 15:27:11.120 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-4022d8dbe474" connected! 2023-09-16 15:27:11.152 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1-441793ab9088" connected! 2023-09-16 15:27:11.447 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 15:27:11.454 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e1a90" 2023-09-16 15:27:11.455 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 15:27:11.455 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 15:27:11.455 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e5f74" 2023-09-16 15:27:11.458 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 15:27:11.458 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 15:27:11.458 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 15:27:11.459 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:11.459 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab9088" 2023-09-16 15:27:11.459 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:11.464 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ecce4" 2023-09-16 15:27:11.465 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-3c610579bd34 / shellyplus1pm#3c610579bd34#1) (false) 2023-09-16 15:27:11.787 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-5443b23d6114" connected! 2023-09-16 15:27:12.169 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 15:27:12.170 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:12.171 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8dbe474" 2023-09-16 15:27:12.172 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:12.172 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23d6114" 2023-09-16 15:27:12.450 - error: shelly.0 (2171) [MQTT] (Shelly?) device unknown, configuration for client with id "nodered_696cdea6606d1eef" does not exist! 2023-09-16 15:27:12.450 - error: shelly.0 (2171) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2023-09-16 15:27:12.451 - info: shelly.0 (2171) [MQTT] Client Error: (nodered_696cdea6606d1eef / nodered_696cdea6606d1eef / undefined) (Error: Invalid return code) 2023-09-16 15:27:13.032 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-485519a2a5d4" connected! 2023-09-16 15:27:14.150 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 15:27:14.186 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a863524" 2023-09-16 15:27:14.187 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-485519a2a5d4" 2023-09-16 15:27:14.187 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 15:27:14.187 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e1a90" 2023-09-16 15:27:14.218 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplusi4-c049ef89b85c" 2023-09-16 15:27:14.702 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-4022d8da969c / shellyplus2pm#4022d8da969c#1) (false) 2023-09-16 15:27:15.127 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplusi4-c049ef89b85c" connected! 2023-09-16 15:27:15.752 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a863524 / shellyplus2pm#b8d61a863524#1) (false) 2023-09-16 15:27:15.973 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8bf730 / shellyplus2pm#b8d61a8bf730#1) (false) 2023-09-16 15:27:17.589 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 15:27:17.621 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8bf730" 2023-09-16 15:27:17.628 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a876248" 2023-09-16 15:27:17.628 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579bd34" 2023-09-16 15:27:17.628 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab94e10" 2023-09-16 15:27:17.628 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a863524" 2023-09-16 15:27:17.784 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 15:27:17.794 - warn: shelly.0 (2171) [mqtt controlFunction] Unable to perform request - device 192.168.1.26 (undefined / undefined / undefined) is offline 2023-09-16 15:27:18.088 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 15:27:18.092 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ecce4" 2023-09-16 15:27:18.093 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplusi4-c049ef89b85c" 2023-09-16 15:27:18.098 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab9088" 2023-09-16 15:27:18.614 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23ecce4 / shellyplus2pm#5443b23ecce4#1) (false) 2023-09-16 15:27:19.078 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-441793acae2c" connected! 2023-09-16 15:27:19.376 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:19.376 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-441793acae2c" 2023-09-16 15:27:21.107 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-4022d8dbe474 / shellyplus2pm#4022d8dbe474#1) (false) 2023-09-16 15:27:21.141 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab9088 / shellyplus1#441793ab9088#1) (false) 2023-09-16 15:27:21.793 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23d6114 / shellyplus2pm#5443b23d6114#1) (false) 2023-09-16 15:27:21.793 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-5443b23d6114 / shellyplus2pm#5443b23d6114#1) (false) 2023-09-16 15:27:23.033 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-485519a2a5d4 / shellyplus2pm#485519a2a5d4#1) (false) 2023-09-16 15:27:25.111 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplusi4 / shellyplusi4-c049ef89b85c / shellyplusi4#c049ef89b85c#1) (false) 2023-09-16 15:27:26.755 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-b8d61a8abb7c" connected! 2023-09-16 15:27:27.334 - info: modbus.0 (258) Disconnected from slave 192.168.1.47 2023-09-16 15:27:28.126 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d794" 2023-09-16 15:27:28.134 - error: shelly.0 (2171) [MQTT] (Shelly?) device unknown, configuration for client with id "nodered_696cdea6606d1eef" does not exist! 2023-09-16 15:27:28.137 - error: shelly.0 (2171) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2023-09-16 15:27:28.138 - info: shelly.0 (2171) [MQTT] Client Error: (nodered_696cdea6606d1eef / nodered_696cdea6606d1eef / undefined) (Error: Invalid return code) 2023-09-16 15:27:28.659 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e5f74" 2023-09-16 15:27:28.661 - error: shelly.0 (2171) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2023-09-16 15:27:28.662 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8abb7c" 2023-09-16 15:27:28.662 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96370" 2023-09-16 15:27:29.754 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-7c87ce65d794" connected! 2023-09-16 15:27:30.403 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-441793acae2c / shellyplus2pm#441793acae2c#1) (false) 2023-09-16 15:27:30.423 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce65d970" 2023-09-16 15:27:30.432 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96980" 2023-09-16 15:27:30.432 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23fd3dc" 2023-09-16 15:27:30.452 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-a8032ab96370" connected! 2023-09-16 15:27:31.220 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a820f4" 2023-09-16 15:27:35.035 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab94e10" 2023-09-16 15:27:35.080 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96980" 2023-09-16 15:27:35.084 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus1pm-7c87ce65d970" connected! 2023-09-16 15:27:35.468 - warn: shelly.0 (2171) [mqtt controlFunction] Unable to perform request - device 192.168.1.26 (undefined / undefined / undefined) is offline 2023-09-16 15:27:38.285 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-b8d61a8abb7c / shellyplus2pm#b8d61a8abb7c#1) (false) 2023-09-16 15:27:38.763 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7c87ce65d794 / shellyplus1pm#7c87ce65d794#1) (false) 2023-09-16 15:27:39.616 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579df44" 2023-09-16 15:27:39.617 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032abc230c" 2023-09-16 15:27:39.631 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8b94fc" 2023-09-16 15:27:39.632 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e5f74" 2023-09-16 15:27:39.646 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23e1a90" 2023-09-16 15:27:39.951 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032ab96370 / shellyplus1pm#a8032ab96370#1) (false) 2023-09-16 15:27:39.981 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199a5d7c" 2023-09-16 15:27:40.884 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a876248" 2023-09-16 15:27:40.885 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c610579bd34" 2023-09-16 15:27:42.564 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-4022d8da969c" 2023-09-16 15:27:42.565 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a863524" 2023-09-16 15:27:42.565 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-b8d61a8bf730" 2023-09-16 15:27:42.566 - error: shelly.0 (2171) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ecce4" 2023-09-16 15:27:42.568 - info: shelly.0 (2171) [MQTT] Device with client id "shellyplus2pm-5443b23fd3dc" connected! 2023-09-16 15:27:43.141 - error: shelly.0 (2171) [MQTT] (Shelly?) device unknown, configuration for client with id "nodered_696cdea6606d1eef" does not exist! 2023-09-16 15:27:43.141 - error: shelly.0 (2171) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2023-09-16 15:27:43.142 - info: shelly.0 (2171) [MQTT] Client Error: (nodered_696cdea6606d1eef / nodered_696cdea6606d1eef / undefined) (Error: Invalid return code) 2023-09-16 15:27:43.708 - info: shelly.0 (2171) [MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7c87ce65d970 / shellyplus1pm#7c87ce65d970#1) (false) -
Ich selber fange gerade mit Shelly an , da ist viel zu beachten .
Da stimmen die Einstellungen nicht !Dabei kann dir bestimmt @crunchip helfen !?
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
2023-09-16 15:27:28.137 - error: shelly.0 (2171) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details)
Ahh .. man sollte auch alles lesen
Du hast den Namen verändert
-
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Unable to get mqttprefix
hast du etwas im shelly geändert?
prefix und id dürfen nicht verändert werden
-
@crunchip ja hatte ich wohl, bei 1-3 shellys den prefix.
Der Prefix muss gleichh zure ID sein, richhtig?
-
ja.
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
ja hatte ich wohl, bei 1-3 shellys den prefix.
da werden aber einige mehr angekreidet als 1-3
überprüfe jeden einzelnen
-
@crunchip
also das beides muss gleich sein
also auch gleich zu der Geräte-ID?
Die GeräteId hat bei mir im iob immer ein #1 am Ende angefügt....
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
also das beides muss gleich sein
ja
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Die GeräteId hat bei mir im iob immer ein #1 am Ende angefügt
ist auch so korrekt
-
hier mal ein Auszug:
Ich prüfe das mal alles durch bis heute abend und gebe dann mal Rückmeldung....
-
@schtallone sollte so aussehen
-
@crunchip ich melde mich später. Danke erstmal....
-
Hier jetzt mal die Info zum Device whatcher. 673MB Speicherbelegung? Ich glaube hier stimmt auch was nicht
-
und noch mal "TOP"
top - 18:36:53 up 5:28, 0 users, load average: 4,87, 5,41, 5,76 Tasks: 28 total, 2 running, 26 sleeping, 0 stopped, 0 zombie %Cpu(s): 75,8 us, 16,7 sy, 0,0 ni, 4,8 id, 1,2 wa, 0,0 hi, 1,5 si, 0,0 st MiB Mem : 7792,2 total, 294,1 free, 5540,5 used, 1957,6 buff/cache MiB Swap: 23447,2 total, 22941,3 free, 505,9 used. 1495,6 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 143 iobroker 20 0 11,2g 418092 40864 R 69,5 5,2 133:10.42 iobroker.js-con 377 iobroker 20 0 1259660 693016 40476 R 14,6 8,7 93:42.22 io.device-watch 12041 iobroker 20 0 999532 164860 39756 S 5,0 2,1 1:20.02 io.shelly.0 2571 iobroker 20 0 21,0g 194208 41544 S 3,3 2,4 6:27.46 node-red 194 iobroker 20 0 839708 149044 36796 S 1,7 1,9 6:19.56 io.javascript.0 467 iobroker 20 0 695588 117832 40592 S 0,7 1,5 3:41.85 io.jarvis.0 176 iobroker 20 0 1052704 179200 41612 S 0,3 2,2 2:01.76 io.admin.0 183 iobroker 20 0 702152 82444 36928 S 0,3 1,0 0:38.00 io.influxdb.0 2414 iobroker 20 0 688244 82604 36480 S 0,3 1,0 0:09.54 io.node-red.0 3196 iobroker 20 0 946508 77544 36472 S 0,3 1,0 1:07.46 node 1 root 20 0 7372 1488 1484 S 0,0 0,0 0:00.06 bash 240 iobroker 20 0 753896 58000 37476 S 0,0 0,7 0:09.90 io.pushover.0 258 iobroker 20 0 695460 71552 36600 S 0,0 0,9 0:19.49 io.modbus.0 312 iobroker 20 0 956392 76856 37724 S 0,0 1,0 0:15.46 io.netatmo.0 334 iobroker 20 0 10,7g 86764 40972 S 0,0 1,1 0:10.41 io.backitup.0 358 iobroker 20 0 826224 85140 37544 S 0,0 1,1 0:32.15 io.cloud.0 448 iobroker 20 0 686096 79952 36492 S 0,0 1,0 0:14.93 io.energiefluss 537 iobroker 20 0 690236 83904 40868 S 0,0 1,1 0:12.22 io.shuttercontr 544 iobroker 20 0 689352 79328 36776 S 0,0 1,0 0:20.95 io.snmp.0 551 iobroker 20 0 689824 80864 36600 S 0,0 1,0 0:18.66 io.sourceanalyt 565 iobroker 20 0 10,9g 105788 37700 S 0,0 1,3 0:31.35 io.vw-connect.0 572 iobroker 20 0 688308 76404 36808 S 0,0 1,0 0:10.88 io.web.0 667 root 20 0 7504 1976 1468 S 0,0 0,0 0:00.06 bash -
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
die Info zum Device whatcher. 673MB Speicherbelegung?
liegt auch hier ganz vorne!
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
377 iobroker 20 0 1259660 693016 40476 R 14,6 8,7 93:42.22 io.device-watch8.7% von 8GB sind erwa 690MB, passt also
aber immer noch viel zu viel Load
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
load average: 4,87, 5,41, 5,76
bei 2 Kernen bremst alles über 2 das System aus.
dein Celeron ist wohl zu schwach, oder da läuft zu viel
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Hier mal nach 1 Std laufzeit die Messungen:
zeigt 97% CPU
7 Container und dann noch die eigentlichen Aufgaben des NAS, womöglich noch weiteres, wozu du immer noch nichts gesagt hast, ist einfach zu viel
und die Ausgabe von
topbezieht sich ausschließlich auf den iob Container -
@homoran Mal eine Frage zu den MQTT Adaptern: Als ich Lovelace UI für das NSPanel an den Start gebracht, hatte ich nach einigen rumprobieren dann doch den MQTT Adapter, anstelle des Sonoff Adapters installiert. Direkt danach ging auch bei mir die Last sofort in die Höhe, trotz unterschiedlicher Ports. Nicht so extrem wie hier, aber bei meinem Raspi sofort negativer Effekt (wie im anderen Post beschrieben). Jedenfalls habe ich dann den Sonoff Adapter rausgeworfen und alles über eine MQTT Instanz angebunden. Sofort war wieder Ruhe im Karton. Ich nutze den Shelly Adapter parallel, scheint aber keine Probleme zu machen.
Jetzt die Frage: Ist das bekannt, dass sich verschiedene MQTT Adapter im Weg stehen, selbst bei unterschiedlichen Ports, oder war das bei mir nur Zufall, oder vielleicht der Tropfen, der das System am Ende überlastet hat? -
@frederik-buss sagte in Performance Probleme durch Shelly Adapter?:
Ist das bekannt, dass sich verschiedene MQTT Adapter im Weg stehen, selbst bei unterschiedlichen Ports
nein!
