Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Shelly 10.5.x (LATEST / BETA)

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.7k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    870

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Test Adapter Shelly 10.5.x (LATEST / BETA)

Geplant Angeheftet Gesperrt Verschoben Tester
mcm1957shelly
90 Beiträge 15 Kommentatoren 7.5k Aufrufe 17 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • mcm1957M mcm1957

    @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

    Allerdings bekomme ich beim 3em Pro keine Leistungswerte per mqtt übertragen. Alle DP stehen dauerhaft auf 0.

    triphase oder monophase Profil?

    Bekommst du gar keine Werte (also auch keine Spannunge, Stromstärke, etc.) angezeigt oder werden nur die Leistungswerte nicht angezeigt?

    Hast du ALLE Häkchen gesetzt wie in der Doku angegeben:
    https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/img/shelly_mqtt-gen2.png

    Ist der Pro 3EM neu oder war er schon mit früheren Releases eingebunden? Hat es dort funktioniert?

    Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

    M Offline
    M Offline
    martinschm
    schrieb am zuletzt editiert von martinschm
    #73

    @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

    triphase oder monophase Profil?

    Monophase.

    Bekommst du gar keine Werte (also auch keine Spannunge, Stromstärke, etc.) angezeigt oder werden nur die Leistungswerte nicht angezeigt?

    So sieht das bei mir aus. Alles in orange
    9b46de84-e5d2-4a3a-b83e-6c0b777e9c33-image.png

    Allerdings empfange ich andere Daten zum Gerät selber per MQTT. Es muß also irgendwie funktionieren
    cd72f539-4213-4803-86fb-71e9c7348b74-image.png

    Hast du ALLE Häkchen gesetzt wie in der Doku angegeben:
    https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/img/shelly_mqtt-gen2.png

    b40df0b6-6b12-4631-b7de-3620958a0948-image.png

    Ist der Pro 3EM neu oder war er schon mit früheren Releases eingebunden? Hat es dort funktioniert?

    War bereits früher eingebunden, da hatte ich immer das mqtt prefix Problem, das ihr jetzt gefixt habt.

    Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

    haus-automatisierungH mcm1957M 2 Antworten Letzte Antwort
    0
    • M martinschm

      @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

      triphase oder monophase Profil?

      Monophase.

      Bekommst du gar keine Werte (also auch keine Spannunge, Stromstärke, etc.) angezeigt oder werden nur die Leistungswerte nicht angezeigt?

      So sieht das bei mir aus. Alles in orange
      9b46de84-e5d2-4a3a-b83e-6c0b777e9c33-image.png

      Allerdings empfange ich andere Daten zum Gerät selber per MQTT. Es muß also irgendwie funktionieren
      cd72f539-4213-4803-86fb-71e9c7348b74-image.png

      Hast du ALLE Häkchen gesetzt wie in der Doku angegeben:
      https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/img/shelly_mqtt-gen2.png

      b40df0b6-6b12-4631-b7de-3620958a0948-image.png

      Ist der Pro 3EM neu oder war er schon mit früheren Releases eingebunden? Hat es dort funktioniert?

      War bereits früher eingebunden, da hatte ich immer das mqtt prefix Problem, das ihr jetzt gefixt habt.

      Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

      haus-automatisierungH Offline
      haus-automatisierungH Offline
      haus-automatisierung
      Developer Most Active
      schrieb am zuletzt editiert von
      #74

      @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

      Allerdings empfange ich andere Daten zum Gerät selber per MQTT.

      Wie soll das gehen? Der Shelly kann ja nur mit einem MQTT-Broker verbunden sein. Entweder mit deinem eigenen, oder mit dem Shelly-Adapter.

      🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
      🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
      📚 Meine inoffizielle ioBroker Dokumentation

      M 1 Antwort Letzte Antwort
      2
      • haus-automatisierungH haus-automatisierung

        @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

        Allerdings empfange ich andere Daten zum Gerät selber per MQTT.

        Wie soll das gehen? Der Shelly kann ja nur mit einem MQTT-Broker verbunden sein. Entweder mit deinem eigenen, oder mit dem Shelly-Adapter.

        M Offline
        M Offline
        martinschm
        schrieb am zuletzt editiert von
        #75

        @haus-automatisierung sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

        @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

        Allerdings empfange ich andere Daten zum Gerät selber per MQTT.

        Wie soll das gehen? Der Shelly kann ja nur mit einem MQTT-Broker verbunden sein. Entweder mit deinem eigenen, oder mit dem Shelly-Adapter.

        Ich meinte, das Infos zum Gerät per MQTT kommen - und im Objektbaum unter dem Shelly Adapter angezeigt werden - aber keine Leistungsdaten angezeigt werden. Wenn aber Infos zum Gerät, also welches Model, Firmware etc ankommen, dann scheint ja irgendwas zu funktionieren. Ich poste gleich noch das Log, das sieht so aus als kämen da auch Leistungsdaten an

        1 Antwort Letzte Antwort
        1
        • M martinschm

          @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

          triphase oder monophase Profil?

          Monophase.

          Bekommst du gar keine Werte (also auch keine Spannunge, Stromstärke, etc.) angezeigt oder werden nur die Leistungswerte nicht angezeigt?

          So sieht das bei mir aus. Alles in orange
          9b46de84-e5d2-4a3a-b83e-6c0b777e9c33-image.png

          Allerdings empfange ich andere Daten zum Gerät selber per MQTT. Es muß also irgendwie funktionieren
          cd72f539-4213-4803-86fb-71e9c7348b74-image.png

          Hast du ALLE Häkchen gesetzt wie in der Doku angegeben:
          https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/img/shelly_mqtt-gen2.png

          b40df0b6-6b12-4631-b7de-3620958a0948-image.png

          Ist der Pro 3EM neu oder war er schon mit früheren Releases eingebunden? Hat es dort funktioniert?

          War bereits früher eingebunden, da hatte ich immer das mqtt prefix Problem, das ihr jetzt gefixt habt.

          Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

          mcm1957M Offline
          mcm1957M Offline
          mcm1957
          schrieb am zuletzt editiert von mcm1957
          #76

          @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

          Allerdings empfange ich andere Daten zum Gerät selber per MQTT. Es muß also irgendwie funktionieren
          cd72f539-4213-4803-86fb-71e9c7348b74-image.png

          DIESE Daten holt sich der Adapter per HTTPS.

          Das Fehlerbild sieht für mich so aus als ob die mqtt Einstellungen nicht passen. Ist der Port (1884 ist am Shelly eingestellt) und die IP sicher richtig?

          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
          Support Repositoryverwaltung.

          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

          LESEN - gute Forenbeitrage

          1 Antwort Letzte Antwort
          0
          • mcm1957M mcm1957

            @martinschm sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

            Allerdings bekomme ich beim 3em Pro keine Leistungswerte per mqtt übertragen. Alle DP stehen dauerhaft auf 0.

            triphase oder monophase Profil?

            Bekommst du gar keine Werte (also auch keine Spannunge, Stromstärke, etc.) angezeigt oder werden nur die Leistungswerte nicht angezeigt?

            Hast du ALLE Häkchen gesetzt wie in der Doku angegeben:
            https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/img/shelly_mqtt-gen2.png

            Ist der Pro 3EM neu oder war er schon mit früheren Releases eingebunden? Hat es dort funktioniert?

            Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

            M Offline
            M Offline
            martinschm
            schrieb am zuletzt editiert von
            #77

            @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

            Bitte poste ein log mit Level DEBUG für eine weitere Analyse.

            shelly.0
            2025-12-28 18:30:18.789	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:1, qos: 1, payload: {"id":1,"voltage":235.3,"current":0.038,"act_power":-3.0,"aprt_power":9.0,"pf":0.33,"freq":50.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:30:18.769	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942889.78,"em1:1":{"act_power":-3.0,"aprt_power":9.0,"current":0.038,"freq":50.0,"pf":0.33,"voltage":235.3}}}
            
            shelly.0
            2025-12-28 18:30:17.589	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -79
            
            shelly.0
            2025-12-28 18:30:17.588	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833160
            
            shelly.0
            2025-12-28 18:30:13.231	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -45
            
            shelly.0
            2025-12-28 18:30:13.230	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424714
            
            shelly.0
            2025-12-28 18:30:07.032	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -80
            
            shelly.0
            2025-12-28 18:30:07.032	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833149
            
            shelly.0
            2025-12-28 18:30:04.776	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:0, qos: 1, payload: {"id":0,"voltage":0.0,"current":0.028,"act_power":0.0,"aprt_power":0.0,"pf":0.00,"freq":0.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:30:04.768	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942976.71,"em1:0":{"act_power":0.0,"aprt_power":0.0,"current":0.028,"freq":0.0,"pf":0.00,"voltage":0.0}}}
            
            shelly.0
            2025-12-28 18:30:03.143	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/energy, qos: 0, payload: 604872
            
            shelly.0
            2025-12-28 18:30:02.065	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -47
            
            shelly.0
            2025-12-28 18:30:02.064	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424703
            
            shelly.0
            2025-12-28 18:30:01.197	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766943001.00,"events":[{"component":"em1data:2","id":2,"event":"data","ts":1766942940.00,"data":{"ts": 1766942940,"period": 60,"values":[[45.4091,0.0000,0.0000,0.0000,2737.5,2718.5,2751.8,2733.0,220.890,212.003,217.742,12.962,12.376,12.587 ]]}}]}}
            
            shelly.0
            2025-12-28 18:30:01.194	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766943001.00,"em1data:2":{"total_act_energy":3196404.65,"total_act_ret_energy":0.00}}}
            
            shelly.0
            2025-12-28 18:30:01.192	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766943000.88,"events":[{"component":"em1data:1","id":1,"event":"data","ts":1766942940.00,"data":{"ts": 1766942940,"period": 60,"values":[[0.0000,0.0501,0.0000,0.0000,-2.6,-3.4,9.6,8.6,239.025,233.935,236.231,0.040,0.037,0.038 ]]}}]}}
            
            shelly.0
            2025-12-28 18:30:01.190	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766943000.88,"em1data:1":{"total_act_energy":396254.82,"total_act_ret_energy":3245.78}}}
            
            shelly.0
            2025-12-28 18:30:01.169	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766943000.78,"events":[{"component":"em1data:0","id":0,"event":"data","ts":1766942940.00,"data":{"ts": 1766942940,"period": 60,"values":[[0.0000,0.0000,0.0000,0.0000,0.0,0.0,0.0,0.0,0.000,0.000,0.000,0.030,0.027,0.028 ]]}}]}}
            
            shelly.0
            2025-12-28 18:30:01.162	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:2, qos: 1, payload: {"id":2,"total_act_energy":3196404.65,"total_act_ret_energy":0.00}
            
            shelly.0
            2025-12-28 18:30:01.160	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:1, qos: 1, payload: {"id":1,"total_act_energy":396254.82,"total_act_ret_energy":3245.78}
            
            shelly.0
            2025-12-28 18:30:01.157	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:0, qos: 1, payload: {"id":0,"total_act_energy":11.73,"total_act_ret_energy":22.33}
            
            shelly.0
            2025-12-28 18:30:01.147	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766943000.78,"em1data:0":{"total_act_energy":11.73,"total_act_ret_energy":22.33}}}
            
            shelly.0
            2025-12-28 18:30:01.048	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/voltage, qos: 0, payload: 222.44
            
            shelly.0
            2025-12-28 18:30:01.046	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:30:01.045	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:01.043	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_f, qos: 0, payload: 123.72
            
            shelly.0
            2025-12-28 18:30:01.042	debug	[MQTT] State change 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1): shellies/shelly-Spielzimmer/temperature -> state: SHSW-25#8CAAB5059C65#1.temperatureC, value: 50.96
            
            shelly.0
            2025-12-28 18:30:01.041	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature, qos: 0, payload: 50.96
            
            shelly.0
            2025-12-28 18:30:01.039	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:01.036	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/0, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:30:01.035	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/energy, qos: 0, payload: 88628
            
            shelly.0
            2025-12-28 18:30:01.033	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:30:01.032	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:30:01.030	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/energy, qos: 0, payload: 9671
            
            shelly.0
            2025-12-28 18:30:01.029	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:30:01.026	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:30:00.418	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/voltage, qos: 0, payload: 215.24
            
            shelly.0
            2025-12-28 18:30:00.417	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:30:00.415	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.414	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_f, qos: 0, payload: 132.54
            
            shelly.0
            2025-12-28 18:30:00.413	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/temperature -> state: SHSW-25#8CAAB5059C66#1.temperatureC, value: 55.85
            
            shelly.0
            2025-12-28 18:30:00.412	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature, qos: 0, payload: 55.85
            
            shelly.0
            2025-12-28 18:30:00.411	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/1, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:30:00.408	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.407	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/energy, qos: 0, payload: 377855
            
            shelly.0
            2025-12-28 18:30:00.405	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:30:00.404	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:30:00.403	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/relay/0/energy -> state: SHSW-25#8CAAB5059C66#1.Relay0.Energy, value: 10081.2
            
            shelly.0
            2025-12-28 18:30:00.402	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/energy, qos: 0, payload: 604872
            
            shelly.0
            2025-12-28 18:30:00.401	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/relay/0/power -> state: SHSW-25#8CAAB5059C66#1.Relay0.Power, value: 44.52
            
            shelly.0
            2025-12-28 18:30:00.400	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/power, qos: 0, payload: 44.52
            
            shelly.0
            2025-12-28 18:30:00.397	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0, qos: 0, payload: on
            
            shelly.0
            2025-12-28 18:30:00.205	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/voltage, qos: 0, payload: 234.78
            
            shelly.0
            2025-12-28 18:30:00.203	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:30:00.201	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.200	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_f, qos: 0, payload: 81.31
            
            shelly.0
            2025-12-28 18:30:00.199	debug	[MQTT] State change 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1): shellies/shelly-Garten-Pool-SH04/temperature -> state: SHSW-25#10521C0706C8#1.temperatureC, value: 27.39
            
            shelly.0
            2025-12-28 18:30:00.198	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature, qos: 0, payload: 27.39
            
            shelly.0
            2025-12-28 18:30:00.196	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.194	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.193	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.190	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:30:00.188	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:30:00.187	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:30:00.185	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:30:00.182	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:59.766	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/voltage, qos: 0, payload: 238.90
            
            shelly.0
            2025-12-28 18:29:59.764	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:59.762	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:59.761	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_f, qos: 0, payload: 71.07
            
            shelly.0
            2025-12-28 18:29:59.760	debug	[MQTT] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): shellies/shelly-Garten-PoolSteckdosen/temperature -> state: SHSW-25#10521C074C71#1.temperatureC, value: 21.71
            
            shelly.0
            2025-12-28 18:29:59.759	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature, qos: 0, payload: 21.71
            
            shelly.0
            2025-12-28 18:29:59.757	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:59.756	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:59.754	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/energy, qos: 0, payload: 1638
            
            shelly.0
            2025-12-28 18:29:59.753	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:59.750	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:59.748	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/energy, qos: 0, payload: 21570
            
            shelly.0
            2025-12-28 18:29:59.746	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:59.744	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:56.390	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -79
            
            shelly.0
            2025-12-28 18:29:56.390	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833139
            
            shelly.0
            2025-12-28 18:29:51.500	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -46
            
            shelly.0
            2025-12-28 18:29:51.499	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424692
            
            shelly.0
            2025-12-28 18:29:49.807	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:2, qos: 1, payload: {"id":2,"voltage":212.4,"current":12.933,"act_power":2734.7,"aprt_power":2748.5,"pf":1.00,"freq":50.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:29:49.796	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942961.74,"em1:2":{"act_power":2734.7,"aprt_power":2748.5,"current":12.933,"freq":50.0,"pf":1.00,"voltage":212.4}}}
            
            admin.0
            2025-12-28 18:29:46.329	info	==> Connected system.user.admin from ::ffff:192.168.1.34
            
            shelly.0
            2025-12-28 18:29:45.905	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -78
            
            shelly.0
            2025-12-28 18:29:45.904	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833128
            
            shelly.0
            2025-12-28 18:29:45.816	debug	[httpIoBrokerState] HTTP request error for 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:29:45.648	debug	[httpIoBrokerState] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): state: SHSW-25#10521C074C71#1.uptime, value: 5960681
            
            shelly.0
            2025-12-28 18:29:44.314	debug	[httpIoBrokerState] HTTP request error for 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:29:44.116	debug	[httpIoBrokerState] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): state: SHSW-25#8CAAB5059C66#1.uptime, value: 4052385
            
            shelly.0
            2025-12-28 18:29:43.554	debug	[httpIoBrokerState] HTTP request error for 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:29:43.392	debug	[httpIoBrokerState] State change 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1): state: SHSW-25#10521C0706C8#1.uptime, value: 2643254
            
            shelly.0
            2025-12-28 18:29:43.344	debug	[httpIoBrokerState] HTTP request error for 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:29:43.144	debug	[httpIoBrokerState] State change 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1): state: SHSW-25#8CAAB5059C65#1.uptime, value: 4085847
            
            shelly.0
            2025-12-28 18:29:42.243	debug	[httpIoBrokerState] HTTP request error for 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) "/rpc/EM.GetConfig?id=0": 404 Not Found - this can happen if the current device configuration doesn't support this feature.
            
            shelly.0
            2025-12-28 18:29:41.822	debug	[httpIoBrokerState] State change 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1): state: shellypro3em#08f9e0eb331c#1.rssi, value: -66
            
            shelly.0
            2025-12-28 18:29:41.822	debug	[httpIoBrokerState] State change 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1): state: shellypro3em#08f9e0eb331c#1.uptime, value: 219
            
            shelly.0
            2025-12-28 18:29:40.962	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -48
            
            shelly.0
            2025-12-28 18:29:40.961	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424682
            
            shelly.0
            2025-12-28 18:29:35.792	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:0, qos: 1, payload: {"id":0,"voltage":0.0,"current":0.028,"act_power":0.0,"aprt_power":0.0,"pf":0.00,"freq":0.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:29:35.783	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942947.73,"em1:0":{"act_power":0.0,"aprt_power":0.0,"current":0.028,"freq":0.0,"pf":0.00,"voltage":0.0}}}
            
            shelly.0
            2025-12-28 18:29:35.416	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833118
            
            shelly.0
            2025-12-28 18:29:32.371	debug	[deviceStatusUpdate] SHSW-25#10521C079516#1: false
            
            shelly.0
            2025-12-28 18:29:31.038	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/voltage, qos: 0, payload: 222.44
            
            shelly.0
            2025-12-28 18:29:31.035	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:31.034	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:31.032	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_f, qos: 0, payload: 124.05
            
            shelly.0
            2025-12-28 18:29:31.032	debug	[MQTT] State change 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1): shellies/shelly-Spielzimmer/temperature -> state: SHSW-25#8CAAB5059C65#1.temperatureC, value: 51.14
            
            shelly.0
            2025-12-28 18:29:31.031	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature, qos: 0, payload: 51.14
            
            shelly.0
            2025-12-28 18:29:31.029	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:31.028	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/0, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:29:31.026	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/energy, qos: 0, payload: 88628
            
            shelly.0
            2025-12-28 18:29:31.023	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:31.022	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:31.020	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/energy, qos: 0, payload: 9671
            
            shelly.0
            2025-12-28 18:29:31.019	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:31.016	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:30.413	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/voltage, qos: 0, payload: 223.09
            
            shelly.0
            2025-12-28 18:29:30.412	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:30.410	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.408	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_f, qos: 0, payload: 133.91
            
            shelly.0
            2025-12-28 18:29:30.407	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/temperature -> state: SHSW-25#8CAAB5059C66#1.temperatureC, value: 56.62
            
            shelly.0
            2025-12-28 18:29:30.406	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature, qos: 0, payload: 56.62
            
            shelly.0
            2025-12-28 18:29:30.404	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/1, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:29:30.403	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.400	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/energy, qos: 0, payload: 377855
            
            shelly.0
            2025-12-28 18:29:30.399	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:30.397	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:30.395	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/energy, qos: 0, payload: 604827
            
            shelly.0
            2025-12-28 18:29:30.394	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/relay/0/power -> state: SHSW-25#8CAAB5059C66#1.Relay0.Power, value: 44.59
            
            shelly.0
            2025-12-28 18:29:30.393	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/power, qos: 0, payload: 44.59
            
            shelly.0
            2025-12-28 18:29:30.390	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0, qos: 0, payload: on
            
            shelly.0
            2025-12-28 18:29:30.197	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/voltage, qos: 0, payload: 234.78
            
            shelly.0
            2025-12-28 18:29:30.196	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:30.194	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.192	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_f, qos: 0, payload: 81.06
            
            shelly.0
            2025-12-28 18:29:30.191	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature, qos: 0, payload: 27.26
            
            shelly.0
            2025-12-28 18:29:30.189	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.187	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.186	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.183	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:30.181	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:30.179	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:30.177	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:30.174	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:29.979	debug	[deviceStatusUpdate] shellypro3em#08f9e0eb331c#1: true
            
            shelly.0
            2025-12-28 18:29:29.969	debug	[onlineCheck] Checking shellypro3em#08f9e0eb331c#1 on 192.168.1.132:80
            
            shelly.0
            2025-12-28 18:29:29.849	debug	[deviceStatusUpdate] shellyplus1#441793a4619c#1: true
            
            shelly.0
            2025-12-28 18:29:29.841	debug	[onlineCheck] Checking shellyplus1#441793a4619c#1 on 192.168.1.131:80
            
            shelly.0
            2025-12-28 18:29:29.763	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/voltage, qos: 0, payload: 238.90
            
            shelly.0
            2025-12-28 18:29:29.761	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:29.760	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:29.758	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_f, qos: 0, payload: 70.93
            
            shelly.0
            2025-12-28 18:29:29.757	debug	[MQTT] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): shellies/shelly-Garten-PoolSteckdosen/temperature -> state: SHSW-25#10521C074C71#1.temperatureC, value: 21.63
            
            shelly.0
            2025-12-28 18:29:29.754	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature, qos: 0, payload: 21.63
            
            shelly.0
            2025-12-28 18:29:29.752	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:29.750	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:29.748	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/energy, qos: 0, payload: 1638
            
            shelly.0
            2025-12-28 18:29:29.746	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:29.744	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:29.742	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/energy, qos: 0, payload: 21570
            
            shelly.0
            2025-12-28 18:29:29.738	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:29.734	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:29.633	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424670
            
            shelly.0
            2025-12-28 18:29:29.424	debug	[deviceStatusUpdate] shelly1minig3#34b7dac6d3e0#1: true
            
            shelly.0
            2025-12-28 18:29:29.403	debug	[onlineCheck] Checking shelly1minig3#34b7dac6d3e0#1 on 192.168.1.135:80
            
            shelly.0
            2025-12-28 18:29:29.334	debug	[deviceStatusUpdate] SHSW-25#10521C07AA5D#1: true
            
            shelly.0
            2025-12-28 18:29:29.332	debug	[deviceStatusUpdate] SHSW-25#8CAAB5059C66#1: true
            
            shelly.0
            2025-12-28 18:29:29.330	debug	[deviceStatusUpdate] SHSW-25#34945469E66B#1: true
            
            shelly.0
            2025-12-28 18:29:29.329	debug	[deviceStatusUpdate] SHSW-25#10521C0706C8#1: true
            
            shelly.0
            2025-12-28 18:29:29.328	debug	[deviceStatusUpdate] SHSW-25#10521C074C71#1: true
            
            shelly.0
            2025-12-28 18:29:29.324	debug	[deviceStatusUpdate] shelly1minig3#34B7DA8CAF20#1: true
            
            shelly.0
            2025-12-28 18:29:29.299	debug	[onlineCheck] Checking shelly1minig3#34B7DA8CAF20#1 on 192.168.1.133:80
            
            shelly.0
            2025-12-28 18:29:29.297	debug	[deviceStatusUpdate] SHSW-25#8CAAB5059C65#1: true
            
            shelly.0
            2025-12-28 18:29:29.294	debug	[onlineCheck] Checking SHSW-25#8CAAB5059C66#1 on 192.168.1.120:80
            
            shelly.0
            2025-12-28 18:29:29.290	debug	[onlineCheck] Checking SHSW-25#8CAAB5059C65#1 on 192.168.1.121:80
            
            shelly.0
            2025-12-28 18:29:29.287	debug	[onlineCheck] Checking SHSW-25#34945469E66B#1 on 192.168.1.124:80
            
            shelly.0
            2025-12-28 18:29:29.283	debug	[onlineCheck] Checking SHSW-25#10521C07AA5D#1 on 192.168.1.126:80
            
            shelly.0
            2025-12-28 18:29:29.278	debug	[onlineCheck] Checking SHSW-25#10521C079516#1 on 192.168.1.123:80
            
            shelly.0
            2025-12-28 18:29:29.275	debug	[onlineCheck] Checking SHSW-25#10521C074C71#1 on 192.168.1.125:80
            
            shelly.0
            2025-12-28 18:29:29.271	debug	[onlineCheck] Checking SHSW-25#10521C0706C8#1 on 192.168.1.127:80
            
            shelly.0
            2025-12-28 18:29:24.923	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833107
            
            zigbee.0
            2025-12-28 18:29:23.951	warn	Resolve Entity did not manage to find a mapped device for 0x00158d0001b7b499 of type undefined
            
            shelly.0
            2025-12-28 18:29:20.821	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:2, qos: 1, payload: {"id":2,"voltage":220.5,"current":12.414,"act_power":2722.8,"aprt_power":2738.0,"pf":1.00,"freq":50.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:29:20.812	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942932.76,"em1:2":{"act_power":2722.8,"aprt_power":2738.0,"current":12.414,"freq":50.0,"pf":1.00,"voltage":220.5}}}
            
            shelly.0
            2025-12-28 18:29:19.094	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -47
            
            shelly.0
            2025-12-28 18:29:19.093	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424660
            
            shelly.0
            2025-12-28 18:29:14.466	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833097
            
            shelly.0
            2025-12-28 18:29:08.593	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424649
            
            shelly.0
            2025-12-28 18:29:06.811	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:0, qos: 1, payload: {"id":0,"voltage":0.0,"current":0.029,"act_power":0.0,"aprt_power":0.0,"pf":0.00,"freq":0.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:29:06.802	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942918.75,"em1:0":{"act_power":0.0,"aprt_power":0.0,"current":0.029,"freq":0.0,"pf":0.00,"voltage":0.0}}}
            
            shelly.0
            2025-12-28 18:29:05.271	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/energy, qos: 0, payload: 604827
            
            shelly.0
            2025-12-28 18:29:04.001	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -79
            
            shelly.0
            2025-12-28 18:29:04.000	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833086
            
            shelly.0
            2025-12-28 18:29:01.241	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766942941.04,"events":[{"component":"em1data:2","id":2,"event":"data","ts":1766942880.00,"data":{"ts": 1766942880,"period": 60,"values":[[45.3197,0.0000,0.0000,0.0000,2734.7,2715.7,2748.5,2729.9,220.624,210.353,219.421,13.060,12.381,12.465 ]]}}]}}
            
            shelly.0
            2025-12-28 18:29:01.241	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766942941.04,"events":[{"component":"em1data:2","id":2,"event":"data","ts":1766942880.00,"data":{"ts": 1766942880,"period": 60,"values":[[45.3197,0.0000,0.0000,0.0000,2734.7,2715.7,2748.5,2729.9,220.624,210.353,219.421,13.060,12.381,12.465 ]]}}]}}
            
            shelly.0
            2025-12-28 18:29:01.235	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942941.04,"em1data:2":{"total_act_energy":3196359.24,"total_act_ret_energy":0.00}}}
            
            shelly.0
            2025-12-28 18:29:01.233	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766942940.92,"events":[{"component":"em1data:1","id":1,"event":"data","ts":1766942880.00,"data":{"ts": 1766942880,"period": 60,"values":[[0.0000,0.0490,0.0000,0.0000,-2.5,-3.4,9.4,8.7,239.638,234.824,235.574,0.039,0.037,0.038 ]]}}]}}
            
            shelly.0
            2025-12-28 18:29:01.229	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942940.92,"em1data:1":{"total_act_energy":396254.82,"total_act_ret_energy":3245.73}}}
            
            shelly.0
            2025-12-28 18:29:01.219	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyEvent","params":{"ts":1766942940.82,"events":[{"component":"em1data:0","id":0,"event":"data","ts":1766942880.00,"data":{"ts": 1766942880,"period": 60,"values":[[0.0000,0.0000,0.0000,0.0000,0.0,0.0,0.0,0.0,0.000,0.000,0.000,0.029,0.028,0.028 ]]}}]}}
            
            shelly.0
            2025-12-28 18:29:01.207	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:2, qos: 1, payload: {"id":2,"total_act_energy":3196359.24,"total_act_ret_energy":0.00}
            
            shelly.0
            2025-12-28 18:29:01.205	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:1, qos: 1, payload: {"id":1,"total_act_energy":396254.82,"total_act_ret_energy":3245.73}
            
            shelly.0
            2025-12-28 18:29:01.202	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1data:0, qos: 1, payload: {"id":0,"total_act_energy":11.73,"total_act_ret_energy":22.33}
            
            shelly.0
            2025-12-28 18:29:01.191	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942940.82,"em1data:0":{"total_act_energy":11.73,"total_act_ret_energy":22.33}}}
            
            shelly.0
            2025-12-28 18:29:01.036	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/voltage, qos: 0, payload: 221.60
            
            shelly.0
            2025-12-28 18:29:01.033	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:01.032	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:01.031	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_f, qos: 0, payload: 123.72
            
            shelly.0
            2025-12-28 18:29:01.030	debug	[MQTT] State change 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1): shellies/shelly-Spielzimmer/temperature -> state: SHSW-25#8CAAB5059C65#1.temperatureC, value: 50.96
            
            shelly.0
            2025-12-28 18:29:01.029	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature, qos: 0, payload: 50.96
            
            shelly.0
            2025-12-28 18:29:01.027	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:01.026	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/0, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:29:01.024	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/energy, qos: 0, payload: 88628
            
            shelly.0
            2025-12-28 18:29:01.022	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:01.020	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:01.018	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/energy, qos: 0, payload: 9671
            
            shelly.0
            2025-12-28 18:29:01.017	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:01.014	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:00.410	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/voltage, qos: 0, payload: 223.09
            
            shelly.0
            2025-12-28 18:29:00.408	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:00.406	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.404	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_f, qos: 0, payload: 133.52
            
            shelly.0
            2025-12-28 18:29:00.404	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/temperature -> state: SHSW-25#8CAAB5059C66#1.temperatureC, value: 56.4
            
            shelly.0
            2025-12-28 18:29:00.403	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature, qos: 0, payload: 56.40
            
            shelly.0
            2025-12-28 18:29:00.401	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/1, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:29:00.399	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.398	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/energy, qos: 0, payload: 377855
            
            shelly.0
            2025-12-28 18:29:00.396	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:00.395	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:00.392	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/relay/0/energy -> state: SHSW-25#8CAAB5059C66#1.Relay0.Energy, value: 10080.45
            
            shelly.0
            2025-12-28 18:29:00.392	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/energy, qos: 0, payload: 604827
            
            shelly.0
            2025-12-28 18:29:00.390	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/relay/0/power -> state: SHSW-25#8CAAB5059C66#1.Relay0.Power, value: 44.56
            
            shelly.0
            2025-12-28 18:29:00.389	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0/power, qos: 0, payload: 44.56
            
            shelly.0
            2025-12-28 18:29:00.387	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/relay/0, qos: 0, payload: on
            
            shelly.0
            2025-12-28 18:29:00.189	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/voltage, qos: 0, payload: 235.05
            
            shelly.0
            2025-12-28 18:29:00.187	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:29:00.185	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.183	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature_f, qos: 0, payload: 81.06
            
            shelly.0
            2025-12-28 18:29:00.182	debug	[MQTT] State change 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1): shellies/shelly-Garten-Pool-SH04/temperature -> state: SHSW-25#10521C0706C8#1.temperatureC, value: 27.26
            
            shelly.0
            2025-12-28 18:29:00.181	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/temperature, qos: 0, payload: 27.26
            
            shelly.0
            2025-12-28 18:29:00.179	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.177	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.176	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.174	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:00.172	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:29:00.171	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/energy, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:29:00.168	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:29:00.165	debug	[MQTT] Publish: 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) - topic: shellies/shelly-Garten-Pool-SH04/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:28:59.755	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/voltage, qos: 0, payload: 239.11
            
            shelly.0
            2025-12-28 18:28:59.754	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:28:59.752	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:59.750	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature_f, qos: 0, payload: 71.86
            
            shelly.0
            2025-12-28 18:28:59.750	debug	[MQTT] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): shellies/shelly-Garten-PoolSteckdosen/temperature -> state: SHSW-25#10521C074C71#1.temperatureC, value: 22.15
            
            shelly.0
            2025-12-28 18:28:59.747	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/temperature, qos: 0, payload: 22.15
            
            shelly.0
            2025-12-28 18:28:59.745	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:59.743	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/input/0, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:59.742	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/energy, qos: 0, payload: 1638
            
            shelly.0
            2025-12-28 18:28:59.740	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:28:59.738	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:28:59.736	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/energy, qos: 0, payload: 21570
            
            shelly.0
            2025-12-28 18:28:59.733	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:28:59.730	debug	[MQTT] Publish: 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) - topic: shellies/shelly-Garten-PoolSteckdosen/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:28:58.062	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.rssi, value: -46
            
            shelly.0
            2025-12-28 18:28:58.061	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424639
            
            shelly.0
            2025-12-28 18:28:53.512	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833076
            
            shelly.0
            2025-12-28 18:28:51.848	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:2, qos: 1, payload: {"id":2,"voltage":220.2,"current":12.418,"act_power":2720.4,"aprt_power":2736.0,"pf":1.00,"freq":50.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:28:51.837	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942903.78,"em1:2":{"act_power":2720.4,"aprt_power":2736.0,"current":12.418,"freq":50.0,"pf":1.00,"voltage":220.2}}}
            
            shelly.0
            2025-12-28 18:28:46.790	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424627
            
            shelly.0
            2025-12-28 18:28:44.523	debug	[httpIoBrokerState] HTTP request error for 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:28:44.342	debug	[httpIoBrokerState] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): state: SHSW-25#10521C074C71#1.rssi, value: -79
            
            shelly.0
            2025-12-28 18:28:44.342	debug	[httpIoBrokerState] State change 192.168.1.125 (shellyswitch25 / shellyswitch25-10521C074C71 / SHSW-25#10521C074C71#1): state: SHSW-25#10521C074C71#1.uptime, value: 5960619
            
            shelly.0
            2025-12-28 18:28:44.061	debug	[httpIoBrokerState] HTTP request error for 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:28:43.843	debug	[httpIoBrokerState] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): state: SHSW-25#8CAAB5059C66#1.rssi, value: -79
            
            shelly.0
            2025-12-28 18:28:43.842	debug	[httpIoBrokerState] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): state: SHSW-25#8CAAB5059C66#1.uptime, value: 4052324
            
            shelly.0
            2025-12-28 18:28:43.285	debug	[httpIoBrokerState] HTTP request error for 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:28:43.087	debug	[httpIoBrokerState] State change 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1): state: SHSW-25#10521C0706C8#1.rssi, value: -80
            
            shelly.0
            2025-12-28 18:28:43.086	debug	[httpIoBrokerState] State change 192.168.1.127 (shellyswitch25 / shellyswitch25-10521C0706C8 / SHSW-25#10521C0706C8#1): state: SHSW-25#10521C0706C8#1.uptime, value: 2643193
            
            shelly.0
            2025-12-28 18:28:43.083	debug	[httpIoBrokerState] HTTP request error for 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) "/roller/0": AxiosError: Request failed with status code 400
            
            shelly.0
            2025-12-28 18:28:42.770	debug	[httpIoBrokerState] State change 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1): state: SHSW-25#8CAAB5059C65#1.uptime, value: 4085787
            
            shelly.0
            2025-12-28 18:28:42.056	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.rssi, value: -80
            
            shelly.0
            2025-12-28 18:28:42.055	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833064
            
            shelly.0
            2025-12-28 18:28:41.699	debug	[httpIoBrokerState] HTTP request error for 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) "/rpc/EM.GetConfig?id=0": 404 Not Found - this can happen if the current device configuration doesn't support this feature.
            
            shelly.0
            2025-12-28 18:28:41.317	debug	[httpIoBrokerState] State change 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1): state: shellypro3em#08f9e0eb331c#1.rssi, value: -67
            
            shelly.0
            2025-12-28 18:28:41.316	debug	[httpIoBrokerState] State change 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1): state: shellypro3em#08f9e0eb331c#1.uptime, value: 159
            
            shelly.0
            2025-12-28 18:28:37.839	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:0, qos: 1, payload: {"id":0,"voltage":0.0,"current":0.028,"act_power":0.0,"aprt_power":0.0,"pf":0.00,"freq":0.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:28:37.829	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942875.78,"em1:0":{"act_power":0.0,"aprt_power":0.0,"current":0.028,"freq":0.0,"pf":0.00,"voltage":0.0}}}
            
            shelly.0
            2025-12-28 18:28:35.739	debug	[httpIoBrokerState] State change 192.168.1.131 (shellyplus1 / shellyplus1-441793a4619c / shellyplus1#441793a4619c#1): state: shellyplus1#441793a4619c#1.uptime, value: 424616
            
            shelly.0
            2025-12-28 18:28:31.571	debug	[deviceStatusUpdate] SHSW-25#10521C079516#1: false
            
            shelly.0
            2025-12-28 18:28:31.558	debug	[httpIoBrokerState] State change 192.168.1.135 (shelly1minig3 / shelly1minig3-34b7dac6d3e0 / shelly1minig3#34b7dac6d3e0#1): state: shelly1minig3#34b7dac6d3e0#1.uptime, value: 6833054
            
            shelly.0
            2025-12-28 18:28:31.019	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/voltage, qos: 0, payload: 221.60
            
            shelly.0
            2025-12-28 18:28:31.018	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:28:31.016	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:31.015	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature_f, qos: 0, payload: 123.89
            
            shelly.0
            2025-12-28 18:28:31.013	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/temperature, qos: 0, payload: 51.05
            
            shelly.0
            2025-12-28 18:28:31.012	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/1, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:31.010	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/input/0, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:28:31.008	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/energy, qos: 0, payload: 88628
            
            shelly.0
            2025-12-28 18:28:31.006	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:28:31.005	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/1, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:28:31.003	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/energy, qos: 0, payload: 9671
            
            shelly.0
            2025-12-28 18:28:31.002	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0/power, qos: 0, payload: 0.00
            
            shelly.0
            2025-12-28 18:28:30.999	debug	[MQTT] Publish: 192.168.1.121 (shellyswitch25 / shellyswitch25-8CAAB5059C65 / SHSW-25#8CAAB5059C65#1) - topic: shellies/shelly-Spielzimmer/relay/0, qos: 0, payload: off
            
            shelly.0
            2025-12-28 18:28:30.401	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/voltage, qos: 0, payload: 213.40
            
            shelly.0
            2025-12-28 18:28:30.399	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_status, qos: 0, payload: Normal
            
            shelly.0
            2025-12-28 18:28:30.398	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/overtemperature, qos: 0, payload: 0
            
            shelly.0
            2025-12-28 18:28:30.396	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature_f, qos: 0, payload: 133.91
            
            shelly.0
            2025-12-28 18:28:30.395	debug	[MQTT] State change 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1): shellies/shelly-gaestezimmer/temperature -> state: SHSW-25#8CAAB5059C66#1.temperatureC, value: 56.62
            
            shelly.0
            2025-12-28 18:28:30.394	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/temperature, qos: 0, payload: 56.62
            
            shelly.0
            2025-12-28 18:28:30.392	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/1, qos: 0, payload: 1
            
            shelly.0
            2025-12-28 18:28:30.390	debug	[MQTT] Publish: 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) - topic: shellies/shelly-gaestezimmer/input/0, qos: 0, payload: 0
            

            Mir sind diese Einträge zum 3EM aufgefallen

            shelly.0
            2025-12-28 18:28:41.699	debug	[httpIoBrokerState] HTTP request error for 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) "/rpc/EM.GetConfig?id=0": 404 Not Found - this can happen if the current device configuration doesn't support this feature.
            
            shelly.0
            2025-12-28 18:28:51.848	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/status/em1:2, qos: 1, payload: {"id":2,"voltage":220.2,"current":12.418,"act_power":2720.4,"aprt_power":2736.0,"pf":1.00,"freq":50.0,"calibration":"factory"}
            
            shelly.0
            2025-12-28 18:28:51.837	debug	[MQTT] Publish: 192.168.1.132 (shellypro3em / shellypro3em-08f9e0eb331c / shellypro3em#08f9e0eb331c#1) - topic: shellypro3em/events/rpc, qos: 1, payload: {"src":"shellypro3em-08f9e0eb331c","dst":"shellypro3em/events","method":"NotifyStatus","params":{"ts":1766942903.78,"em1:2":{"act_power":2720.4,"aprt_power":2736.0,"current":12.418,"freq":50.0,"pf":1.00,"voltage":220.2}}}
            

            Zusätzlich noch - unabhängig vom 3EM

            shelly.0
            2025-12-28 18:28:44.061	debug	[httpIoBrokerState] HTTP request error for 192.168.1.120 (shellyswitch25 / shellyswitch25-8CAAB5059C66 / SHSW-25#8CAAB5059C66#1) "/roller/0": AxiosError: Request failed with status code 400
            
            1 Antwort Letzte Antwort
            0
            • mcm1957M Offline
              mcm1957M Offline
              mcm1957
              schrieb am zuletzt editiert von
              #78

              Danke alles klar - ist ein BUG.

              Der Objektbaum passt zum threephase mode - du verwendest aber monophase.

              Ich hab mit dem shelly pro 3EM G63 getestet (den hab ich verfügbar). Beim Clonen hab ich die mode Abfrage beim 3EM (ohne g63) vergessen. Ist beim Alpha Test offensichtlich niemand aufgefallen. Na ja - kann ja nicht kjeder alle Geräte haben und dann noch alpha SW drauf lassen.

              Fix kommt asap.

              Soryr.

              Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
              Support Repositoryverwaltung.

              Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

              LESEN - gute Forenbeitrage

              M 1 Antwort Letzte Antwort
              1
              • mcm1957M Offline
                mcm1957M Offline
                mcm1957
                schrieb am zuletzt editiert von mcm1957
                #79

                Release 10.5.2 steht ab spätestens morgen im LATEST zum Testen zur Verfügung.

                • monophase mode für pro3em und pro3em400 wurde (hoffentlich) gefixed.

                Vollständigen Changelog gibts da: https://github.com/iobroker-community-adapters/ioBroker.shelly?tab=readme-ov-file#1052-2025-12-28 oder im ersten Posting hier.

                Wie immer bitte um Feedback (sowohl "geht" als auch "hab das Problem" sind gern gesehen.

                @martinschm

                Du kannst - wenn du Zeit und Lust hast - die 10.5.2 ab sofort VON npm (nicht MIT npm) installieren. Im Repo sollte sie ab morgen sein.

                Bitte um feedback ob's jetzt geht.

                Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                Support Repositoryverwaltung.

                Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                LESEN - gute Forenbeitrage

                1 Antwort Letzte Antwort
                2
                • mcm1957M mcm1957

                  Danke alles klar - ist ein BUG.

                  Der Objektbaum passt zum threephase mode - du verwendest aber monophase.

                  Ich hab mit dem shelly pro 3EM G63 getestet (den hab ich verfügbar). Beim Clonen hab ich die mode Abfrage beim 3EM (ohne g63) vergessen. Ist beim Alpha Test offensichtlich niemand aufgefallen. Na ja - kann ja nicht kjeder alle Geräte haben und dann noch alpha SW drauf lassen.

                  Fix kommt asap.

                  Soryr.

                  M Offline
                  M Offline
                  martinschm
                  schrieb am zuletzt editiert von
                  #80

                  @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                  Danke alles klar - ist ein BUG.

                  Der Objektbaum passt zum threephase mode - du verwendest aber monophase.

                  Ich hab mit dem shelly pro 3EM G63 getestet (den hab ich verfügbar). Beim Clonen hab ich die mode Abfrage beim 3EM (ohne g63) vergessen. Ist beim Alpha Test offensichtlich niemand aufgefallen. Na ja - kann ja nicht kjeder alle Geräte haben und dann noch alpha SW drauf lassen.

                  Fix kommt asap.

                  Soryr.

                  Hi @mcm1957 ,
                  mega Dank für den schnellen Fix. Absolut kein Grund sich zu entschuldigen, ist Open Source und ihr entwickelt das in eurer Freizeit. Ich bin happy, das durch eure Arbeit mein Smart Home so viel kann. Kaffee Spende ist unterwegs

                  Fix hat für mich funktioniert. Daten sind jetzt endlich sichtbar.

                  6294f0f4-43d6-4560-bb81-e5c8059db13c-image.png

                  1 Antwort Letzte Antwort
                  2
                  • mcm1957M mcm1957

                    @Shadowhunter23 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                    Für mich ist #931 nicht gelöst:

                    Ist aber seit langem immer das selbe Gerät. Mit allen anderen Shellys im Netzwerk gibt es keine Probleme.

                    Wenn du das Problem mit genau einem Gerät hast, kannst du ev versuchen diese an eigene eigene Instanz zu verbinden (ACHTUNG - musst nen anderen Port verwenden!) und wenn das Problem dort auch auftritt ein Log mit Level SILLY erzeugen ? Ev. sieht man / ich dann mehr. Kannst auch gern ein eigenes Issue eröffnen, wenn es länger dauert das zu klären und es heir ggF unterzugehen droht. Werden auch das Problem noch finden oder zumindest erklären können.

                    S Abwesend
                    S Abwesend
                    Shadowhunter23
                    schrieb am zuletzt editiert von
                    #81

                    @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                    Wenn du das Problem mit genau einem Gerät hast, kannst du ev versuchen diese an eigene eigene Instanz zu verbinden (ACHTUNG - musst nen anderen Port verwenden!) und wenn das Problem dort auch auftritt ein Log mit Level SILLY erzeugen ? Ev. sieht man / ich dann mehr. Kannst auch gern ein eigenes Issue eröffnen, wenn es länger dauert das zu klären und es heir ggF unterzugehen droht. Werden auch das Problem noch finden oder zumindest erklären können.

                    Eine neue Instanz ist angelegt und das Gerät ist verbunden, Log kommt ( muss nur warten bis der Fehler auftritt ).

                    Proxmox 9 HA-Cluster mit 3x HP prodesk 400 G6 i5
                    Bei einem downvote bitte melden, es könnte sein, dass dieser ungewollt ist!

                    1 Antwort Letzte Antwort
                    0
                    • mcm1957M Offline
                      mcm1957M Offline
                      mcm1957
                      schrieb am zuletzt editiert von
                      #82

                      Release 10.5.2 wurde ins STABLE Repository entlassen.

                      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                      Support Repositoryverwaltung.

                      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                      LESEN - gute Forenbeitrage

                      S 1 Antwort Letzte Antwort
                      1
                      • mcm1957M mcm1957

                        Release 10.5.2 wurde ins STABLE Repository entlassen.

                        S Abwesend
                        S Abwesend
                        Shadowhunter23
                        schrieb am zuletzt editiert von
                        #83

                        @mcm1957
                        Durch das Loglevel silly werden die Fehler trotzdem sichtbar? Durch das umstellen der Shelly Instanz 2 zeigt das Log viel weniger an als vorher im Info Modus.

                        Proxmox 9 HA-Cluster mit 3x HP prodesk 400 G6 i5
                        Bei einem downvote bitte melden, es könnte sein, dass dieser ungewollt ist!

                        mcm1957M 1 Antwort Letzte Antwort
                        0
                        • S Shadowhunter23

                          @mcm1957
                          Durch das Loglevel silly werden die Fehler trotzdem sichtbar? Durch das umstellen der Shelly Instanz 2 zeigt das Log viel weniger an als vorher im Info Modus.

                          mcm1957M Offline
                          mcm1957M Offline
                          mcm1957
                          schrieb am zuletzt editiert von mcm1957
                          #84

                          @Shadowhunter23 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                          @mcm1957
                          Durch das Loglevel silly werden die Fehler trotzdem sichtbar? Durch das umstellen der Shelly Instanz 2 zeigt das Log viel weniger an als vorher im Info Modus.

                          Das versteh ich nicht. Bei Loglevel SILLY wird definitiv viel mehr gelogged als im Mode info. Silly beinhaltet sille, debug, info, warn und error logs. Debug beinhaltet debug, info, warn und error log - schaltet also silly logs aus. usw.

                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                          Support Repositoryverwaltung.

                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                          LESEN - gute Forenbeitrage

                          1 Antwort Letzte Antwort
                          0
                          • S Abwesend
                            S Abwesend
                            Shadowhunter23
                            schrieb am zuletzt editiert von Shadowhunter23
                            #85

                            Dieses Log entsteht wenn der shelly.2 auf info Log steht, es kommen ein paar Meldungen:

                            admin.0
                            2026-01-19 15:42:02.091	info	==> Connected system.user.admin from ::ffff:192.168.0.177
                            fullybrowser.0
                            2026-01-19 15:37:52.168	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            fullybrowser.0
                            2026-01-19 15:37:52.158	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:36:22.119	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:36:22.119	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            fullybrowser.0
                            2026-01-19 15:36:21.516	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:36:21.516	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            host.iobroker
                            2026-01-19 15:30:10.894	info	instance system.adapter.ical.0 having pid 113926 terminated with code 0 (NO_ERROR)
                            ical.0
                            2026-01-19 15:30:10.384	info	Terminated (NO_ERROR): Without reason
                            host.iobroker
                            2026-01-19 15:30:08.570	info	instance system.adapter.ical.1 having pid 113910 terminated with code 0 (NO_ERROR)
                            ical.1
                            2026-01-19 15:30:08.057	info	Terminated (NO_ERROR): Without reason
                            ical.0
                            2026-01-19 15:30:04.916	info	starting. Version 1.19.2 in /opt/iobroker/node_modules/iobroker.ical, node: v22.22.0, js-controller: 7.1.0
                            host.iobroker
                            2026-01-19 15:30:04.021	info	instance system.adapter.ical.0 in version "1.19.2" started with pid 113926
                            ical.1
                            2026-01-19 15:30:00.920	info	starting. Version 1.19.2 in /opt/iobroker/node_modules/iobroker.ical, node: v22.22.0, js-controller: 7.1.0
                            host.iobroker
                            2026-01-19 15:30:00.015	info	instance system.adapter.ical.1 in version "1.19.2" started with pid 113910
                            fullybrowser.0
                            2026-01-19 15:28:11.946	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            fullybrowser.0
                            2026-01-19 15:28:11.946	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:26:42.679	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:26:42.679	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            fullybrowser.0
                            2026-01-19 15:26:41.952	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            fullybrowser.0
                            2026-01-19 15:26:41.944	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:24:22.059	info	🗸 192.168.0.77: Command stopScreensaver successfully set to true
                            fullybrowser.0
                            2026-01-19 15:24:22.058	info	🗸 192.168.0.77: Command screenOn successfully set to true
                            admin.0
                            2026-01-19 15:23:32.809	info	<== Disconnect system.user.admin from ::ffff:192.168.0.187 admin
                            

                            Stelle ich den shelly.2 auf silly Log dann sehe ich von diesen Einträgen nichts mehr.

                            Proxmox 9 HA-Cluster mit 3x HP prodesk 400 G6 i5
                            Bei einem downvote bitte melden, es könnte sein, dass dieser ungewollt ist!

                            1 Antwort Letzte Antwort
                            0
                            • mcm1957M Offline
                              mcm1957M Offline
                              mcm1957
                              schrieb am zuletzt editiert von
                              #86

                              Ähmm - die gezeigten Meldung stammen aber nicht vom Shelly adapter sondern von fullybrowser. Zu dem Adapter kann ich nichts sagen.
                              Änderungen an den Einstellungen des Shelly Adapters sollten aber keinen EInfluss auf andere Adapter haben.

                              Schau zuerst mal warum da absolut nichts vom Shelly gelogged wird. Hast du ev. bei der Anzeige der Logs einen Filter aktiv?

                              Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                              Support Repositoryverwaltung.

                              Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                              LESEN - gute Forenbeitrage

                              1 Antwort Letzte Antwort
                              0
                              • S Abwesend
                                S Abwesend
                                Shadowhunter23
                                schrieb am zuletzt editiert von
                                #87

                                Sobald ich den shelly.2 auf silly stelle ist von den info Meldungen der anderen Adapter nichts mehr zu sehen im Log:
                                aee051b5-0b69-4d27-8eab-4e8bf7ca93d1-image.png

                                Das Log ist sozusagen leer von allen anderen Instanzen:
                                d6bcf970-ea38-418e-8fa7-305bc2144b6b-image.png

                                Proxmox 9 HA-Cluster mit 3x HP prodesk 400 G6 i5
                                Bei einem downvote bitte melden, es könnte sein, dass dieser ungewollt ist!

                                HomoranH 1 Antwort Letzte Antwort
                                0
                                • S Shadowhunter23

                                  Sobald ich den shelly.2 auf silly stelle ist von den info Meldungen der anderen Adapter nichts mehr zu sehen im Log:
                                  aee051b5-0b69-4d27-8eab-4e8bf7ca93d1-image.png

                                  Das Log ist sozusagen leer von allen anderen Instanzen:
                                  d6bcf970-ea38-418e-8fa7-305bc2144b6b-image.png

                                  HomoranH Offline
                                  HomoranH Offline
                                  Homoran
                                  Global Moderator Administrators
                                  schrieb am zuletzt editiert von
                                  #88

                                  @Shadowhunter23 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                                  Das Log ist sozusagen leer von allen anderen Instanzen:

                                  nein!
                                  nur die dort angezeigten letzten x Meldungen enthalten nichts anderes mehr.
                                  im log (herunterladen! ) steht da noch was.

                                  Deswegen soll man das log auch nicht routinemäßig mit debug und erst recht nicht mit silly fluten.

                                  kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                  mcm1957M 1 Antwort Letzte Antwort
                                  2
                                  • HomoranH Homoran

                                    @Shadowhunter23 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                                    Das Log ist sozusagen leer von allen anderen Instanzen:

                                    nein!
                                    nur die dort angezeigten letzten x Meldungen enthalten nichts anderes mehr.
                                    im log (herunterladen! ) steht da noch was.

                                    Deswegen soll man das log auch nicht routinemäßig mit debug und erst recht nicht mit silly fluten.

                                    mcm1957M Offline
                                    mcm1957M Offline
                                    mcm1957
                                    schrieb am zuletzt editiert von
                                    #89

                                    @Homoran sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                                    Deswegen soll man das log auch nicht routinemäßig mit debug und erst recht nicht mit silly fluten.

                                    Der silly Log ist an sich schon OK, es geht um die Suche warum bei ihm der Fehler lt. Beitrag 69 noch auftritt.

                                    https://forum.iobroker.net/topic/80722/test-adapter-shelly-10.5.x-latest-beta/69

                                    Wenn ich den Screenshot richtig gesehn habe, filterst du aber bei der Anzeige nach info (Tab Leiste) damit blendest du die Silly logs bei der Anzeige wieder aus :-)

                                    Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                    Support Repositoryverwaltung.

                                    Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                    LESEN - gute Forenbeitrage

                                    HomoranH 1 Antwort Letzte Antwort
                                    1
                                    • mcm1957M mcm1957

                                      @Homoran sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                                      Deswegen soll man das log auch nicht routinemäßig mit debug und erst recht nicht mit silly fluten.

                                      Der silly Log ist an sich schon OK, es geht um die Suche warum bei ihm der Fehler lt. Beitrag 69 noch auftritt.

                                      https://forum.iobroker.net/topic/80722/test-adapter-shelly-10.5.x-latest-beta/69

                                      Wenn ich den Screenshot richtig gesehn habe, filterst du aber bei der Anzeige nach info (Tab Leiste) damit blendest du die Silly logs bei der Anzeige wieder aus :-)

                                      HomoranH Offline
                                      HomoranH Offline
                                      Homoran
                                      Global Moderator Administrators
                                      schrieb am zuletzt editiert von
                                      #90

                                      @mcm1957 sagte in Test Adapter Shelly 10.5.x (LATEST / BETA):

                                      Der silly Log ist an sich schon OK,

                                      Natürlich! Für die Fehlersuche!

                                      Deswegen schrieb ich ja routinemäßig 😉

                                      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                      1 Antwort Letzte Antwort
                                      1
                                      Antworten
                                      • In einem neuen Thema antworten
                                      Anmelden zum Antworten
                                      • Älteste zuerst
                                      • Neuste zuerst
                                      • Meiste Stimmen


                                      Support us

                                      ioBroker
                                      Community Adapters
                                      Donate

                                      326

                                      Online

                                      32.6k

                                      Benutzer

                                      82.1k

                                      Themen

                                      1.3m

                                      Beiträge
                                      Community
                                      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                      ioBroker Community 2014-2025
                                      logo
                                      • Anmelden

                                      • Du hast noch kein Konto? Registrieren

                                      • Anmelden oder registrieren, um zu suchen
                                      • Erster Beitrag
                                        Letzter Beitrag
                                      0
                                      • Home
                                      • Aktuell
                                      • Tags
                                      • Ungelesen 0
                                      • Kategorien
                                      • Unreplied
                                      • Beliebt
                                      • GitHub
                                      • Docu
                                      • Hilfe