Performance Probleme durch Shelly Adapter?
-
@glasfaser said in Performance Probleme durch Shelly Adapter?:
iob list instances | grep port
root@iobroker:/opt/iobroker# iob list instances | grep port + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.10 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 192.168.1.10 system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.terminal.0 : terminal : iobroker - enabled, port: 8088, bind: 192.168.1.10, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: adminroot@iobroker:/opt/iobroker# iob status iobroker is running on this host. Objects type: jsonl States type: jsonl@schtallone sagte in Performance Probleme durch Shelly Adapter?:
- system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.10
- system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 192.168.1.10
das ist doch die IP von deinem ioBroker im Docker ,
stelle auf 0.0.0.0 um -
@dp20eic
MQTT.0 ist von der openWB Wallbox.
MQTT.1 ist von einem Mosquitto MQTT Server, welcher unter der IP 192.168.1.8 per Docker läuft
Ich glaube ich wollte unabhängig von der Wallbox mit MQTT sein, daher habe ich dies so eingerichtet. DIe Shellys werden ja über 1882 mittels des Shelly Adapters abgerufen
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
DIe Shellys werden ja über 1882 mittels des Shelly Adapters abgerufen
da is aber ein shelly unter mqtt.1
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
- system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0
Moin,
zwei mal den gleichen Port?
+ system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0VG
Bernd@dp20eic said in Performance Probleme durch Shelly Adapter?:
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
- system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0
dieser Befehl funktioniert so nichht, muss das "iob set" davor?
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
DIe Shellys werden ja über 1882 mittels des Shelly Adapters abgerufen
da is aber ein shelly unter mqtt.1
stimmt. :anguished:
Ichh frage überhaut: Macht es Sinn, den Shelly Adapter zu nutzen, oder lieber einen MQTT Adapter. Eigentlich macht der doch auch nur MQTT, oder?
-
stimmt. :anguished:
Ichh frage überhaut: Macht es Sinn, den Shelly Adapter zu nutzen, oder lieber einen MQTT Adapter. Eigentlich macht der doch auch nur MQTT, oder?
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Macht es Sinn, den Shelly Adapter zu nutzen,
Kurz und knapp ... JA !
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Macht es Sinn, den Shelly Adapter zu nutzen,
Kurz und knapp ... JA !
@glasfaser
Wenn es nicht zu aufwändig ist, gerne auch erläutern. Ich möchte ja dazu lernen. DANKE -
@glasfaser
Wenn es nicht zu aufwändig ist, gerne auch erläutern. Ich möchte ja dazu lernen. DANKELese die DOKU davon ... da steht alles drin ... warum er besser ist !
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
- system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.10
- system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 192.168.1.10
das ist doch die IP von deinem ioBroker im Docker ,
stelle auf 0.0.0.0 um@glasfaser Und das verstehe ich auch nicht und bräuchte eine Erleuchtung?!
was passiert denn wenn man auf 0.0.0.0 umstellt? Ich denke die Adapter benötigen eine IP und Port, um die Daten zu sammeln?
-
@glasfaser Und das verstehe ich auch nicht und bräuchte eine Erleuchtung?!
was passiert denn wenn man auf 0.0.0.0 umstellt? Ich denke die Adapter benötigen eine IP und Port, um die Daten zu sammeln?
0.0.0.0 --> von allen IPs. Ah....:face_palm:
-
@glasfaser Und das verstehe ich auch nicht und bräuchte eine Erleuchtung?!
was passiert denn wenn man auf 0.0.0.0 umstellt? Ich denke die Adapter benötigen eine IP und Port, um die Daten zu sammeln?
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
was passiert denn wenn man auf 0.0.0.0 umstellt?
Das gleich war gestern mit dem Admin ... die Erklärung dazu hast du gestern schon dazu bekommen
einmal von mir
und von : -
Lese die DOKU davon ... da steht alles drin ... warum er besser ist !
@glasfaser ok, werde ich nochmals detailliert tun.
Aber einer der beiden MQTTs kann ja weg, oder? Die machen doch beide das selbe denke ich, und beißen sich vielleicht sogar dabei..
-
stimmt. :anguished:
Ichh frage überhaut: Macht es Sinn, den Shelly Adapter zu nutzen, oder lieber einen MQTT Adapter. Eigentlich macht der doch auch nur MQTT, oder?
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Eigentlich macht der doch auch nur MQTT, oder?
und bereitet dir alles auf, mit dem mqtt Adapter musst du selbst Hand anlegen, z.b deine zu steuernden Datenpunkte manuell anlegen.
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Wenn es nicht zu aufwändig ist,
ist es nicht, nur der Port 1882 im Adapter sowie in allen shelly verwenden
-
@glasfaser ok, werde ich nochmals detailliert tun.
Aber einer der beiden MQTTs kann ja weg, oder? Die machen doch beide das selbe denke ich, und beißen sich vielleicht sogar dabei..
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
und beißen sich vielleicht sogar dabei..
ja , da auch gleicher Port !
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Eigentlich macht der doch auch nur MQTT, oder?
und bereitet dir alles auf, mit dem mqtt Adapter musst du selbst Hand anlegen, z.b deine zu steuernden Datenpunkte manuell anlegen.
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
Wenn es nicht zu aufwändig ist,
ist es nicht, nur der Port 1882 im Adapter sowie in allen shelly verwenden
-
ist es nicht, nur der Port 1882 im Adapter sowie in allen shelly verwenden
Das gilt aber nur für die Shellys, alle anderen "Geräte" weiterhin über 1883 und nur einem MQTT Adapter?
@schtallone ja
-
@schtallone sagte in Performance Probleme durch Shelly Adapter?:
- system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.10
- system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 192.168.1.10
das ist doch die IP von deinem ioBroker im Docker ,
stelle auf 0.0.0.0 umroot@iobroker:/opt/iobroker# iob list instances | grep port + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 system.adapter.mqtt.0 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin root@iobroker:/opt/iobroker# -
root@iobroker:/opt/iobroker# iob list instances | grep port + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 system.adapter.mqtt.0 : mqtt : iobroker - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin root@iobroker:/opt/iobroker# -
@glasfaser weiterhin Performance. Habe oft eine Minute oder so keine Rückmeldung vom iob
-
@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 .
-
@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)
326
Online32.7k
Users82.5k
Topics1.3m
Posts