Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Performance Probleme durch Shelly Adapter?

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Performance Probleme durch Shelly Adapter?

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Schtallone @crunchip last edited by

      @crunchip

      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?

      crunchip 1 Reply Last reply Reply Quote 0
      • crunchip
        crunchip Forum Testing Most Active @Schtallone last edited by

        @schtallone ja

        1 Reply Last reply Reply Quote 0
        • S
          Schtallone @Glasfaser last edited by

          @glasfaser

          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 1 Reply Last reply Reply Quote 0
          • Glasfaser
            Glasfaser @Schtallone last edited by

            @schtallone

            Ja .. sieht gut aus .

            Liegen noch Probleme an !?

            S 1 Reply Last reply Reply Quote 0
            • S
              Schtallone @Glasfaser last edited by

              @glasfaser weiterhin Performance. Habe oft eine Minute oder so keine Rückmeldung vom iob

              Glasfaser 1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @Schtallone last edited by

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

                S 1 Reply Last reply Reply Quote 0
                • S
                  Schtallone @Glasfaser last edited by

                  @glasfaser

                  -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)
                  
                  Glasfaser DJMarc75 crunchip 4 Replies Last reply Reply Quote 0
                  • Glasfaser
                    Glasfaser @Schtallone last edited by

                    @schtallone

                    Ich selber fange gerade mit Shelly an , da ist viel zu beachten .
                    Da stimmen die Einstellungen nicht !

                    Dabei kann dir bestimmt @crunchip helfen !?

                    1 Reply Last reply Reply Quote 0
                    • Glasfaser
                      Glasfaser @Schtallone last edited by Glasfaser

                      @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

                      1 Reply Last reply Reply Quote 0
                      • DJMarc75
                        DJMarc75 @Schtallone last edited by

                        @schtallone

                        https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/protocol-mqtt.md

                        1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @Schtallone last edited by

                          @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
                          94b7b99c-7629-4338-abd7-7dbfa5359c77-image.png

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            Schtallone @crunchip last edited by

                            @crunchip ja hatte ich wohl, bei 1-3 shellys den prefix.

                            Der Prefix muss gleichh zure ID sein, richhtig?

                            Glasfaser crunchip 2 Replies Last reply Reply Quote 0
                            • Glasfaser
                              Glasfaser @Schtallone last edited by

                              @schtallone

                              ja.

                              1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @Schtallone last edited by

                                @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

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  Schtallone @crunchip last edited by

                                  @crunchip
                                  also das beides muss gleich sein

                                  Snap-2023-09-16-15-45-27.jpg

                                  also auch gleich zu der Geräte-ID?

                                  Snap-2023-09-16-15-45-58.jpg

                                  Die GeräteId hat bei mir im iob immer ein #1 am Ende angefügt....

                                  crunchip 1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active @Schtallone last edited by crunchip

                                    @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

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      Schtallone @crunchip last edited by

                                      @crunchip

                                      hier mal ein Auszug:
                                      Snap-2023-09-16-15-55-59.jpg

                                      Ich prüfe das mal alles durch bis heute abend und gebe dann mal Rückmeldung....

                                      crunchip 1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Schtallone last edited by

                                        @schtallone sollte so aussehen
                                        a0d0f618-71d0-4111-af27-de0f1a55c3e3-image.png

                                        S 2 Replies Last reply Reply Quote 0
                                        • S
                                          Schtallone @crunchip last edited by

                                          @crunchip ich melde mich später. Danke erstmal....

                                          Glasfaser 1 Reply Last reply Reply Quote 0
                                          • S
                                            Schtallone @ticaki last edited by

                                            @ticaki

                                            Unbenannt.jpg

                                            Hier jetzt mal die Info zum Device whatcher. 673MB Speicherbelegung? Ich glaube hier stimmt auch was nicht

                                            S Homoran 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            875
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            14
                                            256
                                            21895
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo