Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • 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. Skripten / Logik
  4. Blockly
  5. Blockly Rolladensteuerung mit Shelly Plus 2 PM

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    453

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    378

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    970

Blockly Rolladensteuerung mit Shelly Plus 2 PM

Geplant Angeheftet Gesperrt Verschoben Blockly
36 Beiträge 6 Kommentatoren 4.8k Aufrufe 4 Beobachtet
  • Ä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.
  • A acem

    @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

    @acem
    Hast Du mal getestet, ob das Script überhaupt zum richtigen Zeitpunkt losrennt?
    Das Script ist so simpel - ich kann mir kaum vorstellen warum das dann nicht funktionieren sollte.
    ad8dc8f1-fa38-4bbd-a18c-77ceb5cd77e7-image.png

    Mein Script unten Funktioniert jetzt nach einem Neustart!
    Astro.png

    Was mich noch Interessiert, bei diesem Script unten ist kein Sonnenuntergang! und auch kein Datenpunkt enthalten! wie soll es Funktionieren?
    Script.png

    Danke

    CodierknechtC Offline
    CodierknechtC Offline
    Codierknecht
    Developer Most Active
    schrieb am zuletzt editiert von
    #16

    @acem sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

    Was mich noch Interessiert, bei diesem Script Unten ist kein Sonnenuntergang! und auch kein Datenpunkt enthalten! wie soll es Funktionieren?

    Kannst Du das mal näher erläutern? Ich stehe da gerade auf dem Schlauch und verstehe nur Bahnhof.

    "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

    Proxmox 9.1.1 LXC|8 GB|Core i7-6700
    HmIP|ZigBee|Tasmota|Unifi
    Zabbix Certified Specialist
    Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

    1 Antwort Letzte Antwort
    0
    • CodierknechtC Codierknecht

      @acem
      Hast Du mal getestet, ob das Script überhaupt zum richtigen Zeitpunkt losrennt?
      Das Script ist so simpel - ich kann mir kaum vorstellen warum das dann nicht funktionieren sollte.
      ad8dc8f1-fa38-4bbd-a18c-77ceb5cd77e7-image.png

      A Offline
      A Offline
      acem
      schrieb am zuletzt editiert von acem
      #17

      @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

      @acem
      Hast Du mal getestet, ob das Script überhaupt zum richtigen Zeitpunkt losrennt?
      Das Script ist so simpel - ich kann mir kaum vorstellen warum das dann nicht funktionieren sollte.
      ad8dc8f1-fa38-4bbd-a18c-77ceb5cd77e7-image.png

      Ich meine damit diesen Screenshot Script den du eingefügt hast

      CodierknechtC 1 Antwort Letzte Antwort
      0
      • A acem

        @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

        @acem
        Hast Du mal getestet, ob das Script überhaupt zum richtigen Zeitpunkt losrennt?
        Das Script ist so simpel - ich kann mir kaum vorstellen warum das dann nicht funktionieren sollte.
        ad8dc8f1-fa38-4bbd-a18c-77ceb5cd77e7-image.png

        Ich meine damit diesen Screenshot Script den du eingefügt hast

        CodierknechtC Offline
        CodierknechtC Offline
        Codierknecht
        Developer Most Active
        schrieb am zuletzt editiert von
        #18

        @acem
        Ach so.
        Das ist ein Beispiel, um im Log etwas auszugeben.
        Ein bisschen was sollst Du ja auch noch machen ;-)

        Aber da das ja jetzt funzt wie gewünscht: Vergiss es einfach!

        "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

        Proxmox 9.1.1 LXC|8 GB|Core i7-6700
        HmIP|ZigBee|Tasmota|Unifi
        Zabbix Certified Specialist
        Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

        A 1 Antwort Letzte Antwort
        0
        • CodierknechtC Codierknecht

          @acem
          Ach so.
          Das ist ein Beispiel, um im Log etwas auszugeben.
          Ein bisschen was sollst Du ja auch noch machen ;-)

          Aber da das ja jetzt funzt wie gewünscht: Vergiss es einfach!

          A Offline
          A Offline
          acem
          schrieb am zuletzt editiert von
          #19

          @codierknecht

          Hat mich halt interessiert, ich bin nicht so gut in der Materie Blockly, ich möchte mein Script so einfach wie möglich halten weshalb ich mir nicht Sicher war bei meinem Script und war Offen für Anregungen bzw. Optimierung.

          A 1 Antwort Letzte Antwort
          0
          • A acem

            @codierknecht

            Hat mich halt interessiert, ich bin nicht so gut in der Materie Blockly, ich möchte mein Script so einfach wie möglich halten weshalb ich mir nicht Sicher war bei meinem Script und war Offen für Anregungen bzw. Optimierung.

            A Offline
            A Offline
            acem
            schrieb am zuletzt editiert von acem
            #20

            Ich weiß nicht warum aber der Rolladen in der Küche ist heute nicht runtergefahren, gestern hat es noch Funktioniert.

            Was mir aufgefallen ist das beim DP Objekte die Position auf 0% steht!

            Astro.png

            Objekte.png

            Wenn ich bei dem DP Objekte den den Wert bei Position von 0% auf z.B. Auf 50% ändere passiert nichts, der Rolladen bewegt sich erst wenn ich über Webinterface auf den Shelly einlogge und den Wert ändere.

            Kann mir Bitte jemand Helfen was könnte das Problem sein?

            Danke

            da_WoodyD 1 Antwort Letzte Antwort
            0
            • A acem

              Ich weiß nicht warum aber der Rolladen in der Küche ist heute nicht runtergefahren, gestern hat es noch Funktioniert.

              Was mir aufgefallen ist das beim DP Objekte die Position auf 0% steht!

              Astro.png

              Objekte.png

              Wenn ich bei dem DP Objekte den den Wert bei Position von 0% auf z.B. Auf 50% ändere passiert nichts, der Rolladen bewegt sich erst wenn ich über Webinterface auf den Shelly einlogge und den Wert ändere.

              Kann mir Bitte jemand Helfen was könnte das Problem sein?

              Danke

              da_WoodyD Offline
              da_WoodyD Offline
              da_Woody
              schrieb am zuletzt editiert von
              #21

              @acem geht mich ja nicht wirklich was an, aber warum haben wir hier DEVs, die adapter für solch sachen entwickeln?
              https://github.com/simatec/ioBroker.shuttercontrol/blob/master/README.md
              hab mit den plus2 noch nichts zu tun gehabt, kann mir aber vorstellen, daß da eine adaptereinstellung nicht passt.

              gruß vom Woody
              HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

              A 1 Antwort Letzte Antwort
              0
              • da_WoodyD da_Woody

                @acem geht mich ja nicht wirklich was an, aber warum haben wir hier DEVs, die adapter für solch sachen entwickeln?
                https://github.com/simatec/ioBroker.shuttercontrol/blob/master/README.md
                hab mit den plus2 noch nichts zu tun gehabt, kann mir aber vorstellen, daß da eine adaptereinstellung nicht passt.

                A Offline
                A Offline
                acem
                schrieb am zuletzt editiert von acem
                #22

                @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                @acem geht mich ja nicht wirklich was an, aber warum haben wir hier DEVs, die adapter für solch sachen entwickeln?
                https://github.com/simatec/ioBroker.shuttercontrol/blob/master/README.md
                hab mit den plus2 noch nichts zu tun gehabt, kann mir aber vorstellen, daß da eine adaptereinstellung nicht passt.

                Heute morgen, Küchenrollo ist nicht hochgefahren.

                Ich vermute jetzt eher dass das Problem an dem Shelly Plus 2 PM liegt.

                Im Wohnzimmer habe ich 3 Rollos an einem habe ich die vorhandene Homematic-Rolladenaktor auch gegen einen Shelly Plus 2 PM ausgetauscht diese ist heute Abend auch nicht automatisch ( Astrozeit ) runtergefahren! ich habe versucht diesen über DP Objekte, Position runterzufahren in dem ich den Wert 0% auf 50% geändert habe bewegt sich leider nicht. Über die Weboberfläche hat es Manuel Funktioniert.

                Nach einem Reboot der Shelly Plus 2 PM konnte auch über DP, Objekte, Position den Rollo wieder bewegen. Das kann aber nicht die Lösung sein das ich jeden Tag den Shelly neu starte.

                Kann mir hier jemand weiterhelfen? was könnte das Problem sein?

                Zur Information, das ganze läuft bei mir auf einen Fujitsu Futro S740 mit Proxmox 16GB Ram IoBroker.

                Danke

                X 1 Antwort Letzte Antwort
                0
                • A acem

                  @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                  @acem geht mich ja nicht wirklich was an, aber warum haben wir hier DEVs, die adapter für solch sachen entwickeln?
                  https://github.com/simatec/ioBroker.shuttercontrol/blob/master/README.md
                  hab mit den plus2 noch nichts zu tun gehabt, kann mir aber vorstellen, daß da eine adaptereinstellung nicht passt.

                  Heute morgen, Küchenrollo ist nicht hochgefahren.

                  Ich vermute jetzt eher dass das Problem an dem Shelly Plus 2 PM liegt.

                  Im Wohnzimmer habe ich 3 Rollos an einem habe ich die vorhandene Homematic-Rolladenaktor auch gegen einen Shelly Plus 2 PM ausgetauscht diese ist heute Abend auch nicht automatisch ( Astrozeit ) runtergefahren! ich habe versucht diesen über DP Objekte, Position runterzufahren in dem ich den Wert 0% auf 50% geändert habe bewegt sich leider nicht. Über die Weboberfläche hat es Manuel Funktioniert.

                  Nach einem Reboot der Shelly Plus 2 PM konnte auch über DP, Objekte, Position den Rollo wieder bewegen. Das kann aber nicht die Lösung sein das ich jeden Tag den Shelly neu starte.

                  Kann mir hier jemand weiterhelfen? was könnte das Problem sein?

                  Zur Information, das ganze läuft bei mir auf einen Fujitsu Futro S740 mit Proxmox 16GB Ram IoBroker.

                  Danke

                  X Offline
                  X Offline
                  xbow42
                  schrieb am zuletzt editiert von
                  #23

                  @acem
                  ich habe auch seit einiger Zeit Probleme mit 2 meiner Shelly2.5 im Verteilerschrank. Hat vorher immer zuverlässigt funktioniert. Hab den Verdacht, dass es mit dem letzten Shelly-Updates(WLAN-Signal schwächer/Softwarebug) zusammen hängt.? Energiesparmodus ist bereits aus. Reboot hilft nur kurze Zeit dann sind die wieder sporadisch offline(auch in der ShellyApp zu sehen) :(
                  Ich werde mal einen Accesspoint nehen den Schrank hängen, mal sehen ob das hilft.

                  shuttercontol ist cool, damit kannst du auch deine Homematic-Rolladenaktor und Shelly an einer Stelle konfigurieren/steuern. ;)

                  A 1 Antwort Letzte Antwort
                  0
                  • X xbow42

                    @acem
                    ich habe auch seit einiger Zeit Probleme mit 2 meiner Shelly2.5 im Verteilerschrank. Hat vorher immer zuverlässigt funktioniert. Hab den Verdacht, dass es mit dem letzten Shelly-Updates(WLAN-Signal schwächer/Softwarebug) zusammen hängt.? Energiesparmodus ist bereits aus. Reboot hilft nur kurze Zeit dann sind die wieder sporadisch offline(auch in der ShellyApp zu sehen) :(
                    Ich werde mal einen Accesspoint nehen den Schrank hängen, mal sehen ob das hilft.

                    shuttercontol ist cool, damit kannst du auch deine Homematic-Rolladenaktor und Shelly an einer Stelle konfigurieren/steuern. ;)

                    A Offline
                    A Offline
                    acem
                    schrieb am zuletzt editiert von
                    #24

                    @xbow42 sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                    @acem
                    ich habe auch seit einiger Zeit Probleme mit 2 meiner Shelly2.5 im Verteilerschrank. Hat vorher immer zuverlässigt funktioniert. Hab den Verdacht, dass es mit dem letzten Shelly-Updates(WLAN-Signal schwächer/Softwarebug) zusammen hängt.? Energiesparmodus ist bereits aus. Reboot hilft nur kurze Zeit dann sind die wieder sporadisch offline(auch in der ShellyApp zu sehen) :(
                    Ich werde mal einen Accesspoint nehen den Schrank hängen, mal sehen ob das hilft.

                    shuttercontol ist cool, damit kannst du auch deine Homematic-Rolladenaktor und Shelly an einer Stelle konfigurieren/steuern. ;)

                    Auf dem Shelly Plus 2 PM ist die aktuelle Firmware 0.14.0 Installiert, Reboot jeden Tag ist natürlich keine Lösung!

                    Mit dem schuttercontrol habe ich mich bisher noch nicht befasst, ich habe bisher bei meinem Rollos mit dem Blockly Script gute Erfahrung gemacht, wenns richtig gemacht ist

                    A 1 Antwort Letzte Antwort
                    0
                    • A acem

                      @xbow42 sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                      @acem
                      ich habe auch seit einiger Zeit Probleme mit 2 meiner Shelly2.5 im Verteilerschrank. Hat vorher immer zuverlässigt funktioniert. Hab den Verdacht, dass es mit dem letzten Shelly-Updates(WLAN-Signal schwächer/Softwarebug) zusammen hängt.? Energiesparmodus ist bereits aus. Reboot hilft nur kurze Zeit dann sind die wieder sporadisch offline(auch in der ShellyApp zu sehen) :(
                      Ich werde mal einen Accesspoint nehen den Schrank hängen, mal sehen ob das hilft.

                      shuttercontol ist cool, damit kannst du auch deine Homematic-Rolladenaktor und Shelly an einer Stelle konfigurieren/steuern. ;)

                      Auf dem Shelly Plus 2 PM ist die aktuelle Firmware 0.14.0 Installiert, Reboot jeden Tag ist natürlich keine Lösung!

                      Mit dem schuttercontrol habe ich mich bisher noch nicht befasst, ich habe bisher bei meinem Rollos mit dem Blockly Script gute Erfahrung gemacht, wenns richtig gemacht ist

                      A Offline
                      A Offline
                      acem
                      schrieb am zuletzt editiert von
                      #25

                      Hat jemand hier vielleicht auch den Shelly Plus 2 PM zum Steuern von Rollos und ähnliche Probleme? bzw. Gibt es jemand der das Problem kennt und weiß wie ich es beheben kann.

                      Meine Homematic Rolladenaktoren arbeiten ohne Probleme, seit Ich die Shellys benutze hängt sich diese fast Täglich auf.

                      Hier mein Log Datei, vielleicht kann jemand was damit anfangen.

                      Logdatei.png

                      Danke

                      CodierknechtC 1 Antwort Letzte Antwort
                      0
                      • A acem

                        Hat jemand hier vielleicht auch den Shelly Plus 2 PM zum Steuern von Rollos und ähnliche Probleme? bzw. Gibt es jemand der das Problem kennt und weiß wie ich es beheben kann.

                        Meine Homematic Rolladenaktoren arbeiten ohne Probleme, seit Ich die Shellys benutze hängt sich diese fast Täglich auf.

                        Hier mein Log Datei, vielleicht kann jemand was damit anfangen.

                        Logdatei.png

                        Danke

                        CodierknechtC Offline
                        CodierknechtC Offline
                        Codierknecht
                        Developer Most Active
                        schrieb am zuletzt editiert von
                        #26

                        @acem
                        Logausgaben bitte als Text in Code-Tags </> posten.
                        Als Screenshot ist das kaum zu entziffern.

                        "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                        Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                        HmIP|ZigBee|Tasmota|Unifi
                        Zabbix Certified Specialist
                        Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                        A 1 Antwort Letzte Antwort
                        0
                        • CodierknechtC Codierknecht

                          @acem
                          Logausgaben bitte als Text in Code-Tags </> posten.
                          Als Screenshot ist das kaum zu entziffern.

                          A Offline
                          A Offline
                          acem
                          schrieb am zuletzt editiert von acem
                          #27

                          @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                          @acem
                          Logausgaben bitte als Text in Code-Tags </> posten.
                          Als Screenshot ist das kaum zu entziffern.

                          Alles klar hier als Text-in Code-Tags.

                          2023-03-13 00:00:00.051 - info: host.vm instance system.adapter.ical.0 started with pid 2181040
                          2023-03-13 00:00:01.414 - info: ical.0 (2181040) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                          2023-03-13 00:00:06.544 - info: ical.0 (2181040) Terminated (NO_ERROR): Without reason
                          2023-03-13 00:00:07.065 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                          2023-03-13 00:00:13.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:00:30.356 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:00:47.327 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:01:04.173 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:01:20.943 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:01:37.768 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:01:54.702 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:02:11.517 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:02:28.406 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:02:45.252 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:03:02.138 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:03:19.036 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:03:35.888 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:03:52.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:04:09.568 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:04:26.418 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:04:43.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:05:00.113 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:05:16.904 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:05:33.840 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:05:50.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:06:07.595 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:06:24.386 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:06:25.212 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 00:06:25.526 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:06:41.192 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:06:58.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:07:14.953 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:07:15.535 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 00:07:23.884 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                          2023-03-13 00:07:31.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:07:48.618 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:08:05.570 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:08:08.365 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:08:22.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:08:33.898 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                          2023-03-13 00:08:39.393 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:08:56.301 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:09:13.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:09:29.938 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:09:46.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:10:03.730 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:10:20.660 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:10:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:10:54.337 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:11:11.168 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:11:28.077 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:11:42.831 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:11:43.245 - info: zigbee.0 (1084) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"9c48732ea829ec119b5ebd9c40c9ce8d","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_9c48732ea829ec119b5ebd9c40c9ce8d-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}]
                          2023-03-13 00:11:44.978 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:11:57.472 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:12:01.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:12:18.713 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:12:35.531 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:12:50.943 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 00:12:52.328 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:12:53.699 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:13:09.178 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:13:26.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:13:42.857 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:13:59.707 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:14:16.498 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:14:33.454 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:14:36.780 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:14:39.208 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                          2023-03-13 00:14:46.541 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:14:50.240 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:15:07.536 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:15:19.454 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:15:24.447 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:15:25.456 - info: javascript.0 (928) Stop script script.js.SmartHome.Offene_und_geschlossene_Fenster.Küchenfenster_fertiges_Script
                          2023-03-13 00:15:41.289 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:15:42.483 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 javascript
                          2023-03-13 00:15:58.174 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:16:15.028 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:16:31.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:16:48.821 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:17:05.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:17:22.524 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:17:39.348 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:17:56.200 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:18:13.040 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:18:29.889 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:18:46.729 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:19:03.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:19:20.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:19:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:19:54.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:20:11.150 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:20:28.048 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:20:44.899 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:21:01.742 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:21:18.587 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:21:35.588 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:21:52.379 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:22:09.220 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:22:26.046 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:22:42.847 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:22:59.739 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:23:00.041 - info: host.vm instance system.adapter.openweathermap.0 started with pid 2214318
                          2023-03-13 00:23:01.319 - info: openweathermap.0 (2214318) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                          2023-03-13 00:23:08.547 - info: openweathermap.0 (2214318) Terminated (NO_ERROR): Without reason
                          2023-03-13 00:23:09.072 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                          2023-03-13 00:23:16.582 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:23:33.479 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:23:50.480 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:24:07.391 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:24:24.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:24:41.082 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:24:57.976 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:25:14.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:25:31.674 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:25:48.551 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:26:05.434 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:26:22.322 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:26:39.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:26:55.896 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:27:12.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:27:29.661 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:27:46.682 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:28:03.486 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:28:20.421 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:28:37.304 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:28:54.236 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:29:11.264 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:29:28.153 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:29:44.972 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 2224289
                          2023-03-13 00:30:01.417 - info: ical.0 (2224289) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                          2023-03-13 00:30:01.806 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:30:06.538 - info: ical.0 (2224289) Terminated (NO_ERROR): Without reason
                          2023-03-13 00:30:07.063 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                          2023-03-13 00:30:18.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:30:35.541 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:30:52.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:31:09.262 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:31:26.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:31:42.990 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:31:59.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:32:16.687 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:32:33.578 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:32:50.474 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:33:07.408 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:33:24.319 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:33:41.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:33:57.958 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:34:14.786 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:34:31.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:34:48.522 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:35:05.494 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:35:22.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:35:38.231 - info: admin.0 (886) Adapter rating updated
                          2023-03-13 00:35:39.120 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:35:56.030 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:36:12.995 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:36:29.815 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:36:46.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:37:03.594 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:37:20.526 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:37:38.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:37:55.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:38:12.422 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:38:29.245 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:38:46.254 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:39:03.151 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:39:20.087 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:39:36.973 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:39:53.880 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:40:10.772 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:40:11.714 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                          2023-03-13 00:40:27.658 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:40:44.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:41:01.420 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:41:18.259 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:41:21.708 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                          2023-03-13 00:41:35.133 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:41:51.964 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:42:08.908 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:42:25.787 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:42:42.622 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:42:59.502 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:43:16.387 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:43:33.274 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:43:50.126 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:44:07.000 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:44:23.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:44:40.696 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:44:57.557 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:45:14.445 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:45:31.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:45:44.446 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                          2023-03-13 00:45:48.084 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:46:05.002 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:46:21.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:46:38.693 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:46:44.562 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 00:46:54.441 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                          2023-03-13 00:46:55.538 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:47:12.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:47:29.309 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:47:46.291 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:48:03.205 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:48:20.227 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:48:37.114 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:48:53.986 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:49:10.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:49:27.583 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:49:44.477 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:50:01.312 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:50:18.195 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:50:35.054 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:50:51.940 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:51:08.879 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:51:25.760 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:51:42.667 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:51:59.459 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:52:16.338 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:52:33.191 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:52:44.370 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 00:52:50.066 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:53:07.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:53:23.890 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:53:40.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:53:57.715 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:54:14.629 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:54:31.544 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:54:48.603 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:55:05.564 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:55:22.431 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:55:39.281 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:55:55.402 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 00:55:56.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:56:12.970 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:56:29.837 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:56:46.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:57:03.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:57:20.376 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:57:33.389 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 00:57:37.263 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:57:54.166 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:58:11.031 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:58:27.873 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:58:44.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:59:01.575 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:59:18.453 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:59:35.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 00:59:39.170 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 00:59:40.530 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 00:59:52.253 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 2267252
                          2023-03-13 01:00:00.531 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 01:00:01.282 - info: ical.0 (2267252) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                          2023-03-13 01:00:06.424 - info: ical.0 (2267252) Terminated (NO_ERROR): Without reason
                          2023-03-13 01:00:06.945 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                          2023-03-13 01:00:09.183 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:00:21.971 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 01:00:26.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:00:42.979 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:00:59.822 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:01:16.718 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:01:33.571 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:01:50.411 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:02:07.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:02:24.315 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:02:41.142 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:02:57.933 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:03:14.984 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:03:31.834 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:03:48.630 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:04:05.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:04:22.359 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:04:39.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:04:56.129 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:05:12.955 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:05:29.794 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:05:46.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:06:03.503 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:06:20.365 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:06:37.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:06:54.229 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:06:55.447 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 01:07:15.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:07:32.720 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:07:49.590 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:08:04.741 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                          2023-03-13 01:08:06.493 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          2023-03-13 01:08:19.088 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                          2023-03-13 01:08:22.468 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                          2023-03-13 01:08:23.496 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                          

                          Ich würde mich sehr darüber freuen, wenn ich weiß, wie ich das Problem mit dem Shelly lösen kann, es sind 2x Shelly Plus 2 PM (Rollladenaktor mit Original Firmware) die Probleme machen sieht man auch im Logdatei und 1x Shell Plus 1 auch mit Original Firmware 0.14.1 latest Version

                          Ich habe auch mehrere Shelly 1 mit Tasmota im Einsatz, diese machen überhaupt keine Probleme.

                          Danke

                          CodierknechtC X 2 Antworten Letzte Antwort
                          0
                          • A acem

                            @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                            @acem
                            Logausgaben bitte als Text in Code-Tags </> posten.
                            Als Screenshot ist das kaum zu entziffern.

                            Alles klar hier als Text-in Code-Tags.

                            2023-03-13 00:00:00.051 - info: host.vm instance system.adapter.ical.0 started with pid 2181040
                            2023-03-13 00:00:01.414 - info: ical.0 (2181040) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                            2023-03-13 00:00:06.544 - info: ical.0 (2181040) Terminated (NO_ERROR): Without reason
                            2023-03-13 00:00:07.065 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                            2023-03-13 00:00:13.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:00:30.356 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:00:47.327 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:01:04.173 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:01:20.943 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:01:37.768 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:01:54.702 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:02:11.517 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:02:28.406 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:02:45.252 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:03:02.138 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:03:19.036 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:03:35.888 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:03:52.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:04:09.568 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:04:26.418 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:04:43.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:05:00.113 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:05:16.904 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:05:33.840 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:05:50.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:06:07.595 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:06:24.386 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:06:25.212 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 00:06:25.526 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:06:41.192 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:06:58.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:07:14.953 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:07:15.535 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 00:07:23.884 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                            2023-03-13 00:07:31.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:07:48.618 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:08:05.570 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:08:08.365 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:08:22.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:08:33.898 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                            2023-03-13 00:08:39.393 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:08:56.301 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:09:13.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:09:29.938 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:09:46.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:10:03.730 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:10:20.660 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:10:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:10:54.337 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:11:11.168 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:11:28.077 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:11:42.831 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:11:43.245 - info: zigbee.0 (1084) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"9c48732ea829ec119b5ebd9c40c9ce8d","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_9c48732ea829ec119b5ebd9c40c9ce8d-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}]
                            2023-03-13 00:11:44.978 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:11:57.472 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:12:01.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:12:18.713 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:12:35.531 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:12:50.943 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 00:12:52.328 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:12:53.699 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:13:09.178 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:13:26.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:13:42.857 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:13:59.707 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:14:16.498 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:14:33.454 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:14:36.780 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:14:39.208 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                            2023-03-13 00:14:46.541 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:14:50.240 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:15:07.536 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:15:19.454 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:15:24.447 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:15:25.456 - info: javascript.0 (928) Stop script script.js.SmartHome.Offene_und_geschlossene_Fenster.Küchenfenster_fertiges_Script
                            2023-03-13 00:15:41.289 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:15:42.483 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 javascript
                            2023-03-13 00:15:58.174 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:16:15.028 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:16:31.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:16:48.821 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:17:05.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:17:22.524 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:17:39.348 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:17:56.200 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:18:13.040 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:18:29.889 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:18:46.729 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:19:03.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:19:20.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:19:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:19:54.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:20:11.150 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:20:28.048 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:20:44.899 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:21:01.742 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:21:18.587 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:21:35.588 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:21:52.379 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:22:09.220 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:22:26.046 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:22:42.847 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:22:59.739 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:23:00.041 - info: host.vm instance system.adapter.openweathermap.0 started with pid 2214318
                            2023-03-13 00:23:01.319 - info: openweathermap.0 (2214318) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                            2023-03-13 00:23:08.547 - info: openweathermap.0 (2214318) Terminated (NO_ERROR): Without reason
                            2023-03-13 00:23:09.072 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                            2023-03-13 00:23:16.582 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:23:33.479 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:23:50.480 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:24:07.391 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:24:24.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:24:41.082 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:24:57.976 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:25:14.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:25:31.674 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:25:48.551 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:26:05.434 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:26:22.322 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:26:39.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:26:55.896 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:27:12.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:27:29.661 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:27:46.682 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:28:03.486 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:28:20.421 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:28:37.304 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:28:54.236 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:29:11.264 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:29:28.153 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:29:44.972 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 2224289
                            2023-03-13 00:30:01.417 - info: ical.0 (2224289) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                            2023-03-13 00:30:01.806 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:30:06.538 - info: ical.0 (2224289) Terminated (NO_ERROR): Without reason
                            2023-03-13 00:30:07.063 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                            2023-03-13 00:30:18.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:30:35.541 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:30:52.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:31:09.262 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:31:26.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:31:42.990 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:31:59.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:32:16.687 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:32:33.578 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:32:50.474 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:33:07.408 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:33:24.319 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:33:41.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:33:57.958 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:34:14.786 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:34:31.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:34:48.522 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:35:05.494 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:35:22.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:35:38.231 - info: admin.0 (886) Adapter rating updated
                            2023-03-13 00:35:39.120 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:35:56.030 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:36:12.995 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:36:29.815 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:36:46.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:37:03.594 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:37:20.526 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:37:38.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:37:55.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:38:12.422 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:38:29.245 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:38:46.254 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:39:03.151 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:39:20.087 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:39:36.973 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:39:53.880 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:40:10.772 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:40:11.714 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                            2023-03-13 00:40:27.658 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:40:44.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:41:01.420 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:41:18.259 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:41:21.708 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                            2023-03-13 00:41:35.133 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:41:51.964 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:42:08.908 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:42:25.787 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:42:42.622 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:42:59.502 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:43:16.387 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:43:33.274 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:43:50.126 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:44:07.000 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:44:23.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:44:40.696 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:44:57.557 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:45:14.445 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:45:31.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:45:44.446 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                            2023-03-13 00:45:48.084 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:46:05.002 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:46:21.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:46:38.693 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:46:44.562 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 00:46:54.441 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                            2023-03-13 00:46:55.538 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:47:12.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:47:29.309 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:47:46.291 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:48:03.205 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:48:20.227 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:48:37.114 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:48:53.986 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:49:10.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:49:27.583 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:49:44.477 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:50:01.312 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:50:18.195 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:50:35.054 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:50:51.940 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:51:08.879 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:51:25.760 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:51:42.667 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:51:59.459 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:52:16.338 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:52:33.191 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:52:44.370 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 00:52:50.066 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:53:07.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:53:23.890 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:53:40.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:53:57.715 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:54:14.629 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:54:31.544 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:54:48.603 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:55:05.564 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:55:22.431 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:55:39.281 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:55:55.402 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 00:55:56.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:56:12.970 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:56:29.837 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:56:46.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:57:03.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:57:20.376 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:57:33.389 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 00:57:37.263 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:57:54.166 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:58:11.031 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:58:27.873 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:58:44.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:59:01.575 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:59:18.453 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:59:35.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 00:59:39.170 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 00:59:40.530 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 00:59:52.253 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 2267252
                            2023-03-13 01:00:00.531 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 01:00:01.282 - info: ical.0 (2267252) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                            2023-03-13 01:00:06.424 - info: ical.0 (2267252) Terminated (NO_ERROR): Without reason
                            2023-03-13 01:00:06.945 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                            2023-03-13 01:00:09.183 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:00:21.971 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 01:00:26.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:00:42.979 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:00:59.822 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:01:16.718 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:01:33.571 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:01:50.411 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:02:07.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:02:24.315 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:02:41.142 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:02:57.933 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:03:14.984 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:03:31.834 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:03:48.630 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:04:05.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:04:22.359 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:04:39.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:04:56.129 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:05:12.955 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:05:29.794 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:05:46.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:06:03.503 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:06:20.365 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:06:37.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:06:54.229 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:06:55.447 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 01:07:15.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:07:32.720 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:07:49.590 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:08:04.741 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                            2023-03-13 01:08:06.493 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            2023-03-13 01:08:19.088 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                            2023-03-13 01:08:22.468 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                            2023-03-13 01:08:23.496 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                            

                            Ich würde mich sehr darüber freuen, wenn ich weiß, wie ich das Problem mit dem Shelly lösen kann, es sind 2x Shelly Plus 2 PM (Rollladenaktor mit Original Firmware) die Probleme machen sieht man auch im Logdatei und 1x Shell Plus 1 auch mit Original Firmware 0.14.1 latest Version

                            Ich habe auch mehrere Shelly 1 mit Tasmota im Einsatz, diese machen überhaupt keine Probleme.

                            Danke

                            CodierknechtC Offline
                            CodierknechtC Offline
                            Codierknecht
                            Developer Most Active
                            schrieb am zuletzt editiert von
                            #28

                            @acem
                            Von Shelly's habe ich zwar keinen blassen Schimmer, aber für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert.
                            Entweder im Adapter oder in den Geräten selbst.

                            Kannst Du die nicht auch mit Tasmota ausstatten?

                            "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                            Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                            HmIP|ZigBee|Tasmota|Unifi
                            Zabbix Certified Specialist
                            Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                            da_WoodyD A 2 Antworten Letzte Antwort
                            0
                            • A acem

                              @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                              @acem
                              Logausgaben bitte als Text in Code-Tags </> posten.
                              Als Screenshot ist das kaum zu entziffern.

                              Alles klar hier als Text-in Code-Tags.

                              2023-03-13 00:00:00.051 - info: host.vm instance system.adapter.ical.0 started with pid 2181040
                              2023-03-13 00:00:01.414 - info: ical.0 (2181040) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-13 00:00:06.544 - info: ical.0 (2181040) Terminated (NO_ERROR): Without reason
                              2023-03-13 00:00:07.065 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-13 00:00:13.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:00:30.356 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:00:47.327 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:01:04.173 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:01:20.943 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:01:37.768 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:01:54.702 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:02:11.517 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:02:28.406 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:02:45.252 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:03:02.138 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:03:19.036 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:03:35.888 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:03:52.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:04:09.568 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:04:26.418 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:04:43.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:05:00.113 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:05:16.904 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:05:33.840 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:05:50.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:06:07.595 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:06:24.386 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:06:25.212 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 00:06:25.526 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:06:41.192 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:06:58.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:07:14.953 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:07:15.535 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 00:07:23.884 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-13 00:07:31.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:07:48.618 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:08:05.570 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:08:08.365 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:08:22.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:08:33.898 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-13 00:08:39.393 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:08:56.301 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:09:13.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:09:29.938 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:09:46.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:10:03.730 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:10:20.660 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:10:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:10:54.337 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:11:11.168 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:11:28.077 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:11:42.831 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:11:43.245 - info: zigbee.0 (1084) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"9c48732ea829ec119b5ebd9c40c9ce8d","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_9c48732ea829ec119b5ebd9c40c9ce8d-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}]
                              2023-03-13 00:11:44.978 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:11:57.472 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:12:01.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:12:18.713 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:12:35.531 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:12:50.943 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 00:12:52.328 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:12:53.699 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:13:09.178 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:13:26.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:13:42.857 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:13:59.707 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:14:16.498 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:14:33.454 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:14:36.780 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:14:39.208 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                              2023-03-13 00:14:46.541 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:14:50.240 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:15:07.536 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:15:19.454 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:15:24.447 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:15:25.456 - info: javascript.0 (928) Stop script script.js.SmartHome.Offene_und_geschlossene_Fenster.Küchenfenster_fertiges_Script
                              2023-03-13 00:15:41.289 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:15:42.483 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 javascript
                              2023-03-13 00:15:58.174 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:16:15.028 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:16:31.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:16:48.821 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:17:05.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:17:22.524 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:17:39.348 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:17:56.200 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:18:13.040 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:18:29.889 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:18:46.729 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:19:03.725 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:19:20.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:19:37.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:19:54.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:20:11.150 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:20:28.048 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:20:44.899 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:21:01.742 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:21:18.587 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:21:35.588 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:21:52.379 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:22:09.220 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:22:26.046 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:22:42.847 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:22:59.739 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:23:00.041 - info: host.vm instance system.adapter.openweathermap.0 started with pid 2214318
                              2023-03-13 00:23:01.319 - info: openweathermap.0 (2214318) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-13 00:23:08.547 - info: openweathermap.0 (2214318) Terminated (NO_ERROR): Without reason
                              2023-03-13 00:23:09.072 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-13 00:23:16.582 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:23:33.479 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:23:50.480 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:24:07.391 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:24:24.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:24:41.082 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:24:57.976 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:25:14.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:25:31.674 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:25:48.551 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:26:05.434 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:26:22.322 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:26:39.106 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:26:55.896 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:27:12.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:27:29.661 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:27:46.682 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:28:03.486 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:28:20.421 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:28:37.304 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:28:54.236 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:29:11.264 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:29:28.153 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:29:44.972 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 2224289
                              2023-03-13 00:30:01.417 - info: ical.0 (2224289) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-13 00:30:01.806 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:30:06.538 - info: ical.0 (2224289) Terminated (NO_ERROR): Without reason
                              2023-03-13 00:30:07.063 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-13 00:30:18.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:30:35.541 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:30:52.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:31:09.262 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:31:26.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:31:42.990 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:31:59.816 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:32:16.687 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:32:33.578 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:32:50.474 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:33:07.408 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:33:24.319 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:33:41.108 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:33:57.958 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:34:14.786 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:34:31.626 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:34:48.522 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:35:05.494 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:35:22.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:35:38.231 - info: admin.0 (886) Adapter rating updated
                              2023-03-13 00:35:39.120 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:35:56.030 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:36:12.995 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:36:29.815 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:36:46.734 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:37:03.594 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:37:20.526 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:37:38.709 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:37:55.573 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:38:12.422 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:38:29.245 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:38:46.254 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:39:03.151 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:39:20.087 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:39:36.973 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:39:53.880 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:40:10.772 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:40:11.714 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-13 00:40:27.658 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:40:44.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:41:01.420 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:41:18.259 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:41:21.708 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-13 00:41:35.133 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:41:51.964 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:42:08.908 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:42:25.787 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:42:42.622 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:42:59.502 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:43:16.387 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:43:33.274 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:43:50.126 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:44:07.000 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:44:23.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:44:40.696 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:44:57.557 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:45:14.445 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:45:31.248 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:45:44.446 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-13 00:45:48.084 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:46:05.002 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:46:21.835 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:46:38.693 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:46:44.562 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 00:46:54.441 - info: javascript.0 (928) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-13 00:46:55.538 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:47:12.478 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:47:29.309 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:47:46.291 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:48:03.205 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:48:20.227 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:48:37.114 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:48:53.986 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:49:10.812 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:49:27.583 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:49:44.477 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:50:01.312 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:50:18.195 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:50:35.054 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:50:51.940 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:51:08.879 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:51:25.760 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:51:42.667 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:51:59.459 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:52:16.338 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:52:33.191 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:52:44.370 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 00:52:50.066 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:53:07.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:53:23.890 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:53:40.811 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:53:57.715 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:54:14.629 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:54:31.544 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:54:48.603 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:55:05.564 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:55:22.431 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:55:39.281 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:55:55.402 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 00:55:56.058 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:56:12.970 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:56:29.837 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:56:46.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:57:03.556 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:57:20.376 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:57:33.389 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 00:57:37.263 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:57:54.166 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:58:11.031 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:58:27.873 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:58:44.652 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:59:01.575 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:59:18.453 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:59:35.430 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 00:59:39.170 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 00:59:40.530 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 00:59:52.253 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 2267252
                              2023-03-13 01:00:00.531 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 01:00:01.282 - info: ical.0 (2267252) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-13 01:00:06.424 - info: ical.0 (2267252) Terminated (NO_ERROR): Without reason
                              2023-03-13 01:00:06.945 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-13 01:00:09.183 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:00:21.971 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 01:00:26.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:00:42.979 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:00:59.822 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:01:16.718 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:01:33.571 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:01:50.411 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:02:07.330 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:02:24.315 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:02:41.142 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:02:57.933 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:03:14.984 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:03:31.834 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:03:48.630 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:04:05.520 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:04:22.359 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:04:39.269 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:04:56.129 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:05:12.955 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:05:29.794 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:05:46.659 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:06:03.503 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:06:20.365 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:06:37.311 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:06:54.229 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:06:55.447 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 01:07:15.062 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:07:32.720 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:07:49.590 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:08:04.741 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-13 01:08:06.493 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-13 01:08:19.088 - info: admin.0 (886) ==> Connected system.user.admin from ::ffff:192.168.178.20
                              2023-03-13 01:08:22.468 - info: admin.0 (886) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin
                              2023-03-13 01:08:23.496 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.66 (shellyplus2pm / shellyplus2pm-441793ad7988 / shellyplus2pm#441793ad7988#1): Configured mqtt topic prefix "shellyplus2pm-441793ad7988" and actual topic prefix "undefined" do not match. Please check configuration
                              

                              Ich würde mich sehr darüber freuen, wenn ich weiß, wie ich das Problem mit dem Shelly lösen kann, es sind 2x Shelly Plus 2 PM (Rollladenaktor mit Original Firmware) die Probleme machen sieht man auch im Logdatei und 1x Shell Plus 1 auch mit Original Firmware 0.14.1 latest Version

                              Ich habe auch mehrere Shelly 1 mit Tasmota im Einsatz, diese machen überhaupt keine Probleme.

                              Danke

                              X Offline
                              X Offline
                              xbow42
                              schrieb am zuletzt editiert von
                              #29

                              @acem die Settings im Shelly hast du über den Browserzugriff gemacht?
                              https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/protocol-mqtt.md#generation-2-geräte-plus-und-pro

                              1 Antwort Letzte Antwort
                              0
                              • CodierknechtC Codierknecht

                                @acem
                                Von Shelly's habe ich zwar keinen blassen Schimmer, aber für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert.
                                Entweder im Adapter oder in den Geräten selbst.

                                Kannst Du die nicht auch mit Tasmota ausstatten?

                                da_WoodyD Offline
                                da_WoodyD Offline
                                da_Woody
                                schrieb am zuletzt editiert von
                                #30

                                @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                Kannst Du die nicht auch mit Tasmota ausstatten?

                                wozu? um gewisse funktionen vom shelly zu killen?
                                bin zwar kein linuxer, aber für mich sieht das aus, wie wenn er nicht den eingebauten shelly mqtt verwendet, sondern einen externen.

                                gruß vom Woody
                                HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                                CodierknechtC 1 Antwort Letzte Antwort
                                0
                                • da_WoodyD da_Woody

                                  @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                  Kannst Du die nicht auch mit Tasmota ausstatten?

                                  wozu? um gewisse funktionen vom shelly zu killen?
                                  bin zwar kein linuxer, aber für mich sieht das aus, wie wenn er nicht den eingebauten shelly mqtt verwendet, sondern einen externen.

                                  CodierknechtC Offline
                                  CodierknechtC Offline
                                  Codierknecht
                                  Developer Most Active
                                  schrieb am zuletzt editiert von
                                  #31

                                  @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                  wozu? um gewisse funktionen vom shelly zu killen?

                                  Wie gesagt: Ich habe von den Shelly's keinen Plan.
                                  Ich kann also auch nicht sagen, ob man sich mit Tasmota da irgend etwas verbaut.

                                  Aber er schrieb ja:

                                  @acem sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                  Ich habe auch mehrere Shelly 1 mit Tasmota im Einsatz, diese machen überhaupt keine Probleme.

                                  Mit Tasmota hat er also offenbar keine Probleme.

                                  @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                  aber für mich sieht das aus, wie wenn er nicht den eingebauten shelly mqtt verwendet, sondern einen externen

                                  Für mich ebenfalls:
                                  @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                  für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert

                                  Was da wie konfiguriert ist, kann uns nur der TE sagen ;-)

                                  "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                                  Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                                  HmIP|ZigBee|Tasmota|Unifi
                                  Zabbix Certified Specialist
                                  Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                                  1 Antwort Letzte Antwort
                                  0
                                  • CodierknechtC Codierknecht

                                    @acem
                                    Von Shelly's habe ich zwar keinen blassen Schimmer, aber für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert.
                                    Entweder im Adapter oder in den Geräten selbst.

                                    Kannst Du die nicht auch mit Tasmota ausstatten?

                                    A Offline
                                    A Offline
                                    acem
                                    schrieb am zuletzt editiert von acem
                                    #32

                                    @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                    @acem
                                    Von Shelly's habe ich zwar keinen blassen Schimmer, aber für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert.
                                    Entweder im Adapter oder in den Geräten selbst.

                                    Kannst Du die nicht auch mit Tasmota ausstatten?

                                    Ja das könnte ich auch machen, ich wollte aber gerne mit der Original Firmware benutzen, wenn möglich!

                                    @xbow42 sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                    @acem die Settings im Shelly hast du über den Browserzugriff gemacht?
                                    https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/protocol-mqtt.md#generation-2-geräte-plus-und-pro

                                    Die Settings im Shelly habe ich genau nach dieser Anleitung gemacht!

                                    @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                    @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                    Kannst Du die nicht auch mit Tasmota ausstatten?

                                    wozu? um gewisse funktionen vom shelly zu killen?
                                    bin zwar kein linuxer, aber für mich sieht das aus, wie wenn er nicht den eingebauten shelly mqtt verwendet, sondern einen externen.

                                    Ich benutze in dem Fall den eingebauten Shelly mqtt!, den MQTT Broker/Client habe ich zwar auch Installiert dieser ist aber deaktiviert!.

                                    hier ein Bild von meinem IoBroker - Instanzen

                                    IoBroker Instanzen.png

                                    Die MQTT Konfiguration von einem Shelly Plus 2 PM, die Probleme macht, die anderen zwei Shellys machen auch Probleme einer davon ist Shelly Plus 2 PM der andere Shelly Plus 1 wobei der Shelly Plus 1 nur für die Lichtschalter benutzt wird.

                                    Shelly Plus 2PM mqtt.png

                                    Instanzeinstellungen vom Shelly Adapter ( Allgemeine Einstellungen )

                                    Instanzeinstellungen shelly.0.png

                                    Instanzeinstellungen vom Shelly Adapter ( MQTT-EInstellungen )

                                    Shelly Adapter MQTT-EInstellungen.png

                                    Ich habe den MQTT Broker/Client mal gelöscht nicht das dieser Adapter sich mit dem Shelly Adapter nicht verträgt! ich weiß es eben nicht.

                                    da_WoodyD 1 Antwort Letzte Antwort
                                    0
                                    • A acem

                                      @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                      @acem
                                      Von Shelly's habe ich zwar keinen blassen Schimmer, aber für mich sieht das so aus als wäre da etwas nicht/falsch konfiguriert.
                                      Entweder im Adapter oder in den Geräten selbst.

                                      Kannst Du die nicht auch mit Tasmota ausstatten?

                                      Ja das könnte ich auch machen, ich wollte aber gerne mit der Original Firmware benutzen, wenn möglich!

                                      @xbow42 sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                      @acem die Settings im Shelly hast du über den Browserzugriff gemacht?
                                      https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/de/protocol-mqtt.md#generation-2-geräte-plus-und-pro

                                      Die Settings im Shelly habe ich genau nach dieser Anleitung gemacht!

                                      @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                      @codierknecht sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                      Kannst Du die nicht auch mit Tasmota ausstatten?

                                      wozu? um gewisse funktionen vom shelly zu killen?
                                      bin zwar kein linuxer, aber für mich sieht das aus, wie wenn er nicht den eingebauten shelly mqtt verwendet, sondern einen externen.

                                      Ich benutze in dem Fall den eingebauten Shelly mqtt!, den MQTT Broker/Client habe ich zwar auch Installiert dieser ist aber deaktiviert!.

                                      hier ein Bild von meinem IoBroker - Instanzen

                                      IoBroker Instanzen.png

                                      Die MQTT Konfiguration von einem Shelly Plus 2 PM, die Probleme macht, die anderen zwei Shellys machen auch Probleme einer davon ist Shelly Plus 2 PM der andere Shelly Plus 1 wobei der Shelly Plus 1 nur für die Lichtschalter benutzt wird.

                                      Shelly Plus 2PM mqtt.png

                                      Instanzeinstellungen vom Shelly Adapter ( Allgemeine Einstellungen )

                                      Instanzeinstellungen shelly.0.png

                                      Instanzeinstellungen vom Shelly Adapter ( MQTT-EInstellungen )

                                      Shelly Adapter MQTT-EInstellungen.png

                                      Ich habe den MQTT Broker/Client mal gelöscht nicht das dieser Adapter sich mit dem Shelly Adapter nicht verträgt! ich weiß es eben nicht.

                                      da_WoodyD Offline
                                      da_WoodyD Offline
                                      da_Woody
                                      schrieb am zuletzt editiert von
                                      #33

                                      @acem die shelly einstellung sieht ok aus.
                                      2 unterschiede sind mit in der adaptereinstellung aufgefallen:
                                      http- benutzername. da steht bei mir nichts drinnen.
                                      mqtt-listen-ip. b515356f-5af3-4c5b-8101-aabd76b368c2-grafik.png
                                      der mqtt-nutzer und passwort sind bei den shellys auch so eingerichtet?

                                      gruß vom Woody
                                      HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                                      A 1 Antwort Letzte Antwort
                                      0
                                      • da_WoodyD da_Woody

                                        @acem die shelly einstellung sieht ok aus.
                                        2 unterschiede sind mit in der adaptereinstellung aufgefallen:
                                        http- benutzername. da steht bei mir nichts drinnen.
                                        mqtt-listen-ip. b515356f-5af3-4c5b-8101-aabd76b368c2-grafik.png
                                        der mqtt-nutzer und passwort sind bei den shellys auch so eingerichtet?

                                        A Offline
                                        A Offline
                                        acem
                                        schrieb am zuletzt editiert von acem
                                        #34

                                        @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                        @acem die shelly einstellung sieht ok aus.
                                        2 unterschiede sind mit in der adaptereinstellung aufgefallen:
                                        http- benutzername. da steht bei mir nichts drinnen.
                                        mqtt-listen-ip. b515356f-5af3-4c5b-8101-aabd76b368c2-grafik.png
                                        der mqtt-nutzer und passwort sind bei den shellys auch so eingerichtet?

                                        Für die Shellys benutze ich wie bereits angegeben den Shelly Adapter! Außerdem war noch der MQTT Broker/Client Adapter installiert. Diese war zwar deaktiviert, aber anscheinend hat der Adapter die Fehlermeldungen im Log verursacht, nachdem ich gestern Abend den Adapter MQTT Broker/Client gelöscht habe, sind die Rollos, die an Shelly angeschlossen sind, alle hochgefahren und keine MQTT Fehlermeldung im Log.

                                        Benutzername bei Shelly Adapter war bei mir Admin drinnen ohne Passwort diesen habe, ich jetzt entfernt!

                                        Shelly Adapter MQTT Einstellung sieht jetzt wie hier auf dem Bild aus.

                                        Shelly.png

                                        Hier ist das Log von heute!

                                        2023-03-14 00:45:04.453 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:45:21.689 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                        2023-03-14 00:45:23.174 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20
                                        2023-03-14 00:45:47.980 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                        2023-03-14 00:46:04.971 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:46:18.361 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                        2023-03-14 00:46:26.712 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                        2023-03-14 00:46:27.252 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                        2023-03-14 00:47:05.481 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:48:06.073 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:49:06.604 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:50:07.120 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:50:59.747 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                        2023-03-14 00:51:02.514 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                                        2023-03-14 00:51:07.992 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:52:08.550 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:53:09.115 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:54:09.633 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:55:10.175 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:56:10.710 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:57:11.243 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:58:07.267 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20
                                        2023-03-14 00:58:11.542 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                        2023-03-14 00:58:11.790 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 00:59:12.299 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 90429
                                        2023-03-14 01:00:01.270 - info: ical.0 (90429) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 01:00:06.402 - info: ical.0 (90429) Terminated (NO_ERROR): Without reason
                                        2023-03-14 01:00:06.922 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 01:00:12.833 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:01:13.340 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:02:13.905 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:03:14.446 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:04:15.017 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:04:21.606 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:05:15.525 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:05:31.607 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 01:06:16.041 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:07:16.558 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:08:17.073 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:09:17.596 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:10:18.143 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:11:18.676 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:12:19.271 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:13:19.929 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:14:20.505 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:15:21.023 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:16:21.542 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:17:22.113 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:18:22.647 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:18:48.705 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:19:23.276 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:19:58.662 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 01:20:23.825 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:21:24.364 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:22:24.896 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:23:00.036 - info: host.vm instance system.adapter.openweathermap.0 started with pid 123525
                                        2023-03-14 01:23:01.255 - info: openweathermap.0 (123525) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 01:23:16.166 - info: openweathermap.0 (123525) Terminated (NO_ERROR): Without reason
                                        2023-03-14 01:23:16.686 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 01:23:25.449 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:24:25.947 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:25:26.502 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:26:27.036 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:27:27.570 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:28:28.461 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:29:28.981 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:30:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 133509
                                        2023-03-14 01:30:01.281 - info: ical.0 (133509) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 01:30:06.442 - info: ical.0 (133509) Terminated (NO_ERROR): Without reason
                                        2023-03-14 01:30:06.968 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 01:30:29.509 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:31:30.036 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:32:15.685 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:32:30.598 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:33:21.665 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:33:31.141 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:34:31.662 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 01:34:31.678 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                        2023-03-14 01:35:32.185 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - fallback to poll data: Too many failed retries. Check cookie and data
                                        2023-03-14 01:37:17.474 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:38:18.592 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 01:39:28.583 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 01:57:21.840 - info: host.vm Delete log file iobroker.2023-03-06.log.gz
                                        2023-03-14 02:00:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 176752
                                        2023-03-14 02:00:01.262 - info: ical.0 (176752) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 02:00:06.386 - info: ical.0 (176752) Terminated (NO_ERROR): Without reason
                                        2023-03-14 02:00:06.921 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 02:23:00.055 - info: host.vm instance system.adapter.openweathermap.0 started with pid 209931
                                        2023-03-14 02:23:01.280 - info: openweathermap.0 (209931) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 02:23:20.180 - info: openweathermap.0 (209931) Terminated (NO_ERROR): Without reason
                                        2023-03-14 02:23:20.701 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 02:29:58.413 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 02:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 219892
                                        2023-03-14 02:30:01.244 - info: ical.0 (219892) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 02:30:06.371 - info: ical.0 (219892) Terminated (NO_ERROR): Without reason
                                        2023-03-14 02:30:06.892 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 02:31:08.412 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 02:31:51.661 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 02:34:03.612 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 03:00:00.060 - info: host.vm instance system.adapter.ical.0 started with pid 262765
                                        2023-03-14 03:00:01.304 - info: ical.0 (262765) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 03:00:06.434 - info: ical.0 (262765) Terminated (NO_ERROR): Without reason
                                        2023-03-14 03:00:06.954 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 03:23:00.052 - info: host.vm instance system.adapter.openweathermap.0 started with pid 295773
                                        2023-03-14 03:23:01.323 - info: openweathermap.0 (295773) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 03:23:32.408 - info: openweathermap.0 (295773) Terminated (NO_ERROR): Without reason
                                        2023-03-14 03:23:32.931 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 03:30:00.044 - info: host.vm instance system.adapter.ical.0 started with pid 305712
                                        2023-03-14 03:30:01.339 - info: ical.0 (305712) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 03:30:06.456 - info: ical.0 (305712) Terminated (NO_ERROR): Without reason
                                        2023-03-14 03:30:06.979 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 04:00:00.035 - info: host.vm instance system.adapter.ical.0 started with pid 348613
                                        2023-03-14 04:00:01.289 - info: ical.0 (348613) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 04:00:06.414 - info: ical.0 (348613) Terminated (NO_ERROR): Without reason
                                        2023-03-14 04:00:06.934 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 04:23:00.075 - info: host.vm instance system.adapter.openweathermap.0 started with pid 381421
                                        2023-03-14 04:23:01.332 - info: openweathermap.0 (381421) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 04:23:16.438 - warn: telegram.0 (944) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                                        2023-03-14 04:23:19.122 - info: cloud.0 (1132) Connection changed: disconnect
                                        2023-03-14 04:23:20.133 - info: openweathermap.0 (381421) Terminated (NO_ERROR): Without reason
                                        2023-03-14 04:23:20.655 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 04:24:07.092 - info: cloud.0 (1132) Connection changed: connect
                                        2023-03-14 04:30:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 391558
                                        2023-03-14 04:30:01.251 - info: ical.0 (391558) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 04:30:06.384 - info: ical.0 (391558) Terminated (NO_ERROR): Without reason
                                        2023-03-14 04:30:06.902 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 04:51:39.495 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 04:52:49.489 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 04:57:29.419 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 04:58:39.410 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 04:58:48.391 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 04:59:58.390 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 05:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 434421
                                        2023-03-14 05:00:01.283 - info: ical.0 (434421) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 05:00:06.406 - info: ical.0 (434421) Terminated (NO_ERROR): Without reason
                                        2023-03-14 05:00:06.930 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 05:01:39.055 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 05:02:40.449 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 05:03:50.447 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 05:04:00.479 - info: telegram.0 (944) Scheduled restart.
                                        2023-03-14 05:04:00.987 - info: telegram.0 (944) terminating
                                        2023-03-14 05:04:00.989 - info: telegram.0 (944) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2023-03-14 05:04:01.560 - info: host.vm instance system.adapter.telegram.0 scheduled normal terminated and will be restarted on schedule.
                                        2023-03-14 05:04:01.560 - info: host.vm Restart adapter system.adapter.telegram.0 because enabled
                                        2023-03-14 05:04:02.621 - info: host.vm instance system.adapter.telegram.0 started with pid 440171
                                        2023-03-14 05:04:04.228 - info: telegram.0 (440171) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 05:08:21.324 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 05:09:01.298 - warn: telegram.0 (440171) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                                        2023-03-14 05:09:01.596 - info: sonoff.0 (1084) Client [WClicht] reconnected. Old secret 1678748330103_398. New secret 1678766941594_3429
                                        2023-03-14 05:09:01.922 - info: sonoff.0 (1084) Client [Badlicht] reconnected. Old secret 1678748330530_2632. New secret 1678766941918_6037
                                        2023-03-14 05:09:01.949 - info: sonoff.0 (1084) Client [Schlafzimmerlicht] reconnected. Old secret 1678748330284_5645. New secret 1678766941947_7198
                                        2023-03-14 05:09:02.043 - info: sonoff.0 (1084) Client [Flurlicht] reconnected. Old secret 1678748330520_7203. New secret 1678766942043_1413
                                        2023-03-14 05:09:02.237 - info: sonoff.0 (1084) Client [Esstisch] reconnected. Old secret 1678748330710_8237. New secret 1678766942236_3235
                                        2023-03-14 05:09:02.351 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                        2023-03-14 05:09:02.358 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                        2023-03-14 05:09:04.659 - info: sonoff.0 (1084) Client [Wohnzimmerlicht] reconnected. Old secret 1678748330529_4263. New secret 1678766944659_2555
                                        2023-03-14 05:09:08.159 - info: sonoff.0 (1084) Client [Balkonlicht] reconnected. Old secret 1678748330720_9194. New secret 1678766948159_8289
                                        2023-03-14 05:09:09.695 - info: sonoff.0 (1084) Client [Betuels_Zimmerlicht] reconnected. Old secret 1678748330751_8840. New secret 1678766949695_4496
                                        2023-03-14 05:09:12.182 - info: sonoff.0 (1084) Client [Elas_Zimmerlicht] reconnected. Old secret 1678748330528_576. New secret 1678766952182_6550
                                        2023-03-14 05:09:23.371 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 05:10:04.495 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                        2023-03-14 05:10:26.942 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 05:11:36.934 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 05:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 467238
                                        2023-03-14 05:23:01.306 - info: openweathermap.0 (467238) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 05:23:20.044 - info: openweathermap.0 (467238) Terminated (NO_ERROR): Without reason
                                        2023-03-14 05:23:20.566 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 05:30:00.048 - info: host.vm instance system.adapter.ical.0 started with pid 477327
                                        2023-03-14 05:30:01.293 - info: ical.0 (477327) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 05:30:06.410 - info: ical.0 (477327) Terminated (NO_ERROR): Without reason
                                        2023-03-14 05:30:06.929 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 06:00:00.028 - info: host.vm instance system.adapter.ical.0 started with pid 520263
                                        2023-03-14 06:00:01.287 - info: ical.0 (520263) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 06:00:06.398 - info: ical.0 (520263) Terminated (NO_ERROR): Without reason
                                        2023-03-14 06:00:06.918 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 06:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 553073
                                        2023-03-14 06:23:01.262 - info: openweathermap.0 (553073) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 06:23:12.212 - info: openweathermap.0 (553073) Terminated (NO_ERROR): Without reason
                                        2023-03-14 06:23:12.733 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 06:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 563404
                                        2023-03-14 06:30:01.348 - info: ical.0 (563404) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 06:30:06.470 - info: ical.0 (563404) Terminated (NO_ERROR): Without reason
                                        2023-03-14 06:30:07.002 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 06:43:46.176 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 06:44:56.168 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 07:00:00.032 - info: host.vm instance system.adapter.ical.0 started with pid 606465
                                        2023-03-14 07:00:01.306 - info: ical.0 (606465) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 07:00:06.427 - info: ical.0 (606465) Terminated (NO_ERROR): Without reason
                                        2023-03-14 07:00:06.946 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 07:00:16.704 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:01:26.702 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 07:03:16.497 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:04:26.499 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 07:09:24.242 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:10:34.231 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 07:10:37.535 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:11:47.438 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:12:48.734 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 07:13:58.729 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 07:23:00.044 - info: host.vm instance system.adapter.openweathermap.0 started with pid 639238
                                        2023-03-14 07:23:01.275 - info: openweathermap.0 (639238) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 07:23:06.032 - info: openweathermap.0 (639238) Terminated (NO_ERROR): Without reason
                                        2023-03-14 07:23:06.575 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 07:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 649157
                                        2023-03-14 07:30:01.288 - info: ical.0 (649157) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 07:30:06.407 - info: ical.0 (649157) Terminated (NO_ERROR): Without reason
                                        2023-03-14 07:30:06.931 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 08:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 692011
                                        2023-03-14 08:00:01.317 - info: ical.0 (692011) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 08:00:06.443 - info: ical.0 (692011) Terminated (NO_ERROR): Without reason
                                        2023-03-14 08:00:06.963 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 08:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 725038
                                        2023-03-14 08:23:01.355 - info: openweathermap.0 (725038) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 08:23:07.882 - info: openweathermap.0 (725038) Terminated (NO_ERROR): Without reason
                                        2023-03-14 08:23:08.403 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 08:30:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 734984
                                        2023-03-14 08:30:01.278 - info: ical.0 (734984) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 08:30:06.414 - info: ical.0 (734984) Terminated (NO_ERROR): Without reason
                                        2023-03-14 08:30:06.933 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 08:32:07.938 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:33:17.937 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 08:46:52.254 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:48:02.252 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 08:48:37.222 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:49:38.300 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:50:48.299 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 08:52:34.864 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:54:47.317 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 08:57:48.079 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 08:58:51.670 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 09:00:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 777833
                                        2023-03-14 09:00:01.307 - info: ical.0 (777833) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 09:00:01.658 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 09:00:06.422 - info: ical.0 (777833) Terminated (NO_ERROR): Without reason
                                        2023-03-14 09:00:06.942 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 09:01:28.468 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 09:02:38.464 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 09:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 810818
                                        2023-03-14 09:23:01.256 - info: openweathermap.0 (810818) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 09:23:09.045 - info: openweathermap.0 (810818) Terminated (NO_ERROR): Without reason
                                        2023-03-14 09:23:09.566 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 09:30:00.044 - info: host.vm instance system.adapter.ical.0 started with pid 820765
                                        2023-03-14 09:30:01.279 - info: ical.0 (820765) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 09:30:06.397 - info: ical.0 (820765) Terminated (NO_ERROR): Without reason
                                        2023-03-14 09:30:06.927 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 09:54:07.432 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 09:55:07.938 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 09:56:17.937 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 09:58:57.720 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 10:00:00.048 - info: host.vm instance system.adapter.ical.0 started with pid 863660
                                        2023-03-14 10:00:01.265 - info: ical.0 (863660) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 10:00:06.384 - info: ical.0 (863660) Terminated (NO_ERROR): Without reason
                                        2023-03-14 10:00:06.907 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 10:00:07.712 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 10:23:00.036 - info: host.vm instance system.adapter.openweathermap.0 started with pid 897248
                                        2023-03-14 10:23:01.280 - info: openweathermap.0 (897248) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 10:23:28.455 - info: openweathermap.0 (897248) Terminated (NO_ERROR): Without reason
                                        2023-03-14 10:23:28.976 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 10:25:08.048 - warn: zigbee.0 (1099) Device '0xa4c13899e33a9b60' announced itself
                                        2023-03-14 10:30:00.032 - info: host.vm instance system.adapter.ical.0 started with pid 907390
                                        2023-03-14 10:30:01.328 - info: ical.0 (907390) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 10:30:06.461 - info: ical.0 (907390) Terminated (NO_ERROR): Without reason
                                        2023-03-14 10:30:06.984 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                        2023-03-14 10:33:20.000 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 10:35:38.980 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 10:38:03.605 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                        2023-03-14 10:39:13.602 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                        2023-03-14 10:40:29.783 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                        2023-03-14 10:41:48.772 - info: host.vm stopInstance system.adapter.shelly.0 (force=false, process=true)
                                        2023-03-14 10:41:48.776 - info: shelly.0 (1069) Got terminate signal TERMINATE_YOURSELF
                                        2023-03-14 10:41:48.781 - info: shelly.0 (1069) terminating
                                        2023-03-14 10:41:48.781 - info: shelly.0 (1069) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2023-03-14 10:41:48.784 - info: host.vm stopInstance system.adapter.shelly.0 send kill signal
                                        2023-03-14 10:41:49.347 - info: host.vm instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2023-03-14 10:41:51.853 - info: host.vm instance system.adapter.shelly.0 started with pid 924356
                                        2023-03-14 10:41:53.279 - info: shelly.0 (924356) starting. Version 6.3.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 10:41:53.487 - info: shelly.0 (924356) Starting in MQTT mode. Listening on 192.168.178.64:1882 (QoS 0)
                                        2023-03-14 10:41:55.206 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                        2023-03-14 10:41:55.222 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                        2023-03-14 10:41:55.776 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                        2023-03-14 10:42:25.217 - info: host.vm stopInstance system.adapter.shelly.0 (force=false, process=true)
                                        2023-03-14 10:42:25.221 - info: shelly.0 (924356) Got terminate signal TERMINATE_YOURSELF
                                        2023-03-14 10:42:25.220 - info: host.vm stopInstance system.adapter.shelly.0 send kill signal
                                        2023-03-14 10:42:25.227 - info: shelly.0 (924356) terminating
                                        2023-03-14 10:42:25.231 - info: shelly.0 (924356) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2023-03-14 10:42:25.793 - info: host.vm instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2023-03-14 10:42:28.280 - info: host.vm instance system.adapter.shelly.0 started with pid 925295
                                        2023-03-14 10:42:29.678 - info: shelly.0 (925295) starting. Version 6.3.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.1, js-controller: 4.0.24
                                        2023-03-14 10:42:29.840 - info: shelly.0 (925295) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
                                        2023-03-14 10:42:31.024 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                        2023-03-14 10:42:31.464 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                        2023-03-14 10:42:31.525 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                        
                                        da_WoodyD 1 Antwort Letzte Antwort
                                        0
                                        • A acem

                                          @da_woody sagte in Blockly Rolladensteuerung mit Shelly Plus 2 PM:

                                          @acem die shelly einstellung sieht ok aus.
                                          2 unterschiede sind mit in der adaptereinstellung aufgefallen:
                                          http- benutzername. da steht bei mir nichts drinnen.
                                          mqtt-listen-ip. b515356f-5af3-4c5b-8101-aabd76b368c2-grafik.png
                                          der mqtt-nutzer und passwort sind bei den shellys auch so eingerichtet?

                                          Für die Shellys benutze ich wie bereits angegeben den Shelly Adapter! Außerdem war noch der MQTT Broker/Client Adapter installiert. Diese war zwar deaktiviert, aber anscheinend hat der Adapter die Fehlermeldungen im Log verursacht, nachdem ich gestern Abend den Adapter MQTT Broker/Client gelöscht habe, sind die Rollos, die an Shelly angeschlossen sind, alle hochgefahren und keine MQTT Fehlermeldung im Log.

                                          Benutzername bei Shelly Adapter war bei mir Admin drinnen ohne Passwort diesen habe, ich jetzt entfernt!

                                          Shelly Adapter MQTT Einstellung sieht jetzt wie hier auf dem Bild aus.

                                          Shelly.png

                                          Hier ist das Log von heute!

                                          2023-03-14 00:45:04.453 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:45:21.689 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                          2023-03-14 00:45:23.174 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20
                                          2023-03-14 00:45:47.980 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                          2023-03-14 00:46:04.971 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:46:18.361 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                          2023-03-14 00:46:26.712 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                          2023-03-14 00:46:27.252 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                          2023-03-14 00:47:05.481 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:48:06.073 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:49:06.604 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:50:07.120 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:50:59.747 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                          2023-03-14 00:51:02.514 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                                          2023-03-14 00:51:07.992 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:52:08.550 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:53:09.115 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:54:09.633 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:55:10.175 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:56:10.710 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:57:11.243 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:58:07.267 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20
                                          2023-03-14 00:58:11.542 - info: admin.0 (45753) <== Disconnect system.user.admin from 192.168.178.20 admin
                                          2023-03-14 00:58:11.790 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 00:59:12.299 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 90429
                                          2023-03-14 01:00:01.270 - info: ical.0 (90429) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 01:00:06.402 - info: ical.0 (90429) Terminated (NO_ERROR): Without reason
                                          2023-03-14 01:00:06.922 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 01:00:12.833 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:01:13.340 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:02:13.905 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:03:14.446 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:04:15.017 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:04:21.606 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:05:15.525 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:05:31.607 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 01:06:16.041 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:07:16.558 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:08:17.073 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:09:17.596 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:10:18.143 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:11:18.676 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:12:19.271 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:13:19.929 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:14:20.505 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:15:21.023 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:16:21.542 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:17:22.113 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:18:22.647 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:18:48.705 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:19:23.276 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:19:58.662 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 01:20:23.825 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:21:24.364 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:22:24.896 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:23:00.036 - info: host.vm instance system.adapter.openweathermap.0 started with pid 123525
                                          2023-03-14 01:23:01.255 - info: openweathermap.0 (123525) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 01:23:16.166 - info: openweathermap.0 (123525) Terminated (NO_ERROR): Without reason
                                          2023-03-14 01:23:16.686 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 01:23:25.449 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:24:25.947 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:25:26.502 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:26:27.036 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:27:27.570 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:28:28.461 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:29:28.981 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:30:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 133509
                                          2023-03-14 01:30:01.281 - info: ical.0 (133509) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 01:30:06.442 - info: ical.0 (133509) Terminated (NO_ERROR): Without reason
                                          2023-03-14 01:30:06.968 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 01:30:29.509 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:31:30.036 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:32:15.685 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:32:30.598 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:33:21.665 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:33:31.141 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:34:31.662 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 01:34:31.678 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                                          2023-03-14 01:35:32.185 - info: alexa2.0 (1000) Alexa-Push-Connection disconnected - fallback to poll data: Too many failed retries. Check cookie and data
                                          2023-03-14 01:37:17.474 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:38:18.592 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 01:39:28.583 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 01:57:21.840 - info: host.vm Delete log file iobroker.2023-03-06.log.gz
                                          2023-03-14 02:00:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 176752
                                          2023-03-14 02:00:01.262 - info: ical.0 (176752) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 02:00:06.386 - info: ical.0 (176752) Terminated (NO_ERROR): Without reason
                                          2023-03-14 02:00:06.921 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 02:23:00.055 - info: host.vm instance system.adapter.openweathermap.0 started with pid 209931
                                          2023-03-14 02:23:01.280 - info: openweathermap.0 (209931) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 02:23:20.180 - info: openweathermap.0 (209931) Terminated (NO_ERROR): Without reason
                                          2023-03-14 02:23:20.701 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 02:29:58.413 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 02:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 219892
                                          2023-03-14 02:30:01.244 - info: ical.0 (219892) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 02:30:06.371 - info: ical.0 (219892) Terminated (NO_ERROR): Without reason
                                          2023-03-14 02:30:06.892 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 02:31:08.412 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 02:31:51.661 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 02:34:03.612 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 03:00:00.060 - info: host.vm instance system.adapter.ical.0 started with pid 262765
                                          2023-03-14 03:00:01.304 - info: ical.0 (262765) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 03:00:06.434 - info: ical.0 (262765) Terminated (NO_ERROR): Without reason
                                          2023-03-14 03:00:06.954 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 03:23:00.052 - info: host.vm instance system.adapter.openweathermap.0 started with pid 295773
                                          2023-03-14 03:23:01.323 - info: openweathermap.0 (295773) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 03:23:32.408 - info: openweathermap.0 (295773) Terminated (NO_ERROR): Without reason
                                          2023-03-14 03:23:32.931 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 03:30:00.044 - info: host.vm instance system.adapter.ical.0 started with pid 305712
                                          2023-03-14 03:30:01.339 - info: ical.0 (305712) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 03:30:06.456 - info: ical.0 (305712) Terminated (NO_ERROR): Without reason
                                          2023-03-14 03:30:06.979 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 04:00:00.035 - info: host.vm instance system.adapter.ical.0 started with pid 348613
                                          2023-03-14 04:00:01.289 - info: ical.0 (348613) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 04:00:06.414 - info: ical.0 (348613) Terminated (NO_ERROR): Without reason
                                          2023-03-14 04:00:06.934 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 04:23:00.075 - info: host.vm instance system.adapter.openweathermap.0 started with pid 381421
                                          2023-03-14 04:23:01.332 - info: openweathermap.0 (381421) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 04:23:16.438 - warn: telegram.0 (944) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                                          2023-03-14 04:23:19.122 - info: cloud.0 (1132) Connection changed: disconnect
                                          2023-03-14 04:23:20.133 - info: openweathermap.0 (381421) Terminated (NO_ERROR): Without reason
                                          2023-03-14 04:23:20.655 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 04:24:07.092 - info: cloud.0 (1132) Connection changed: connect
                                          2023-03-14 04:30:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 391558
                                          2023-03-14 04:30:01.251 - info: ical.0 (391558) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 04:30:06.384 - info: ical.0 (391558) Terminated (NO_ERROR): Without reason
                                          2023-03-14 04:30:06.902 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 04:51:39.495 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 04:52:49.489 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 04:57:29.419 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 04:58:39.410 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 04:58:48.391 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 04:59:58.390 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 05:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 434421
                                          2023-03-14 05:00:01.283 - info: ical.0 (434421) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 05:00:06.406 - info: ical.0 (434421) Terminated (NO_ERROR): Without reason
                                          2023-03-14 05:00:06.930 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 05:01:39.055 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 05:02:40.449 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 05:03:50.447 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 05:04:00.479 - info: telegram.0 (944) Scheduled restart.
                                          2023-03-14 05:04:00.987 - info: telegram.0 (944) terminating
                                          2023-03-14 05:04:00.989 - info: telegram.0 (944) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2023-03-14 05:04:01.560 - info: host.vm instance system.adapter.telegram.0 scheduled normal terminated and will be restarted on schedule.
                                          2023-03-14 05:04:01.560 - info: host.vm Restart adapter system.adapter.telegram.0 because enabled
                                          2023-03-14 05:04:02.621 - info: host.vm instance system.adapter.telegram.0 started with pid 440171
                                          2023-03-14 05:04:04.228 - info: telegram.0 (440171) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 05:08:21.324 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 05:09:01.298 - warn: telegram.0 (440171) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                                          2023-03-14 05:09:01.596 - info: sonoff.0 (1084) Client [WClicht] reconnected. Old secret 1678748330103_398. New secret 1678766941594_3429
                                          2023-03-14 05:09:01.922 - info: sonoff.0 (1084) Client [Badlicht] reconnected. Old secret 1678748330530_2632. New secret 1678766941918_6037
                                          2023-03-14 05:09:01.949 - info: sonoff.0 (1084) Client [Schlafzimmerlicht] reconnected. Old secret 1678748330284_5645. New secret 1678766941947_7198
                                          2023-03-14 05:09:02.043 - info: sonoff.0 (1084) Client [Flurlicht] reconnected. Old secret 1678748330520_7203. New secret 1678766942043_1413
                                          2023-03-14 05:09:02.237 - info: sonoff.0 (1084) Client [Esstisch] reconnected. Old secret 1678748330710_8237. New secret 1678766942236_3235
                                          2023-03-14 05:09:02.351 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                          2023-03-14 05:09:02.358 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                          2023-03-14 05:09:04.659 - info: sonoff.0 (1084) Client [Wohnzimmerlicht] reconnected. Old secret 1678748330529_4263. New secret 1678766944659_2555
                                          2023-03-14 05:09:08.159 - info: sonoff.0 (1084) Client [Balkonlicht] reconnected. Old secret 1678748330720_9194. New secret 1678766948159_8289
                                          2023-03-14 05:09:09.695 - info: sonoff.0 (1084) Client [Betuels_Zimmerlicht] reconnected. Old secret 1678748330751_8840. New secret 1678766949695_4496
                                          2023-03-14 05:09:12.182 - info: sonoff.0 (1084) Client [Elas_Zimmerlicht] reconnected. Old secret 1678748330528_576. New secret 1678766952182_6550
                                          2023-03-14 05:09:23.371 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 05:10:04.495 - info: shelly.0 (1069) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                          2023-03-14 05:10:26.942 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 05:11:36.934 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 05:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 467238
                                          2023-03-14 05:23:01.306 - info: openweathermap.0 (467238) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 05:23:20.044 - info: openweathermap.0 (467238) Terminated (NO_ERROR): Without reason
                                          2023-03-14 05:23:20.566 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 05:30:00.048 - info: host.vm instance system.adapter.ical.0 started with pid 477327
                                          2023-03-14 05:30:01.293 - info: ical.0 (477327) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 05:30:06.410 - info: ical.0 (477327) Terminated (NO_ERROR): Without reason
                                          2023-03-14 05:30:06.929 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 06:00:00.028 - info: host.vm instance system.adapter.ical.0 started with pid 520263
                                          2023-03-14 06:00:01.287 - info: ical.0 (520263) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 06:00:06.398 - info: ical.0 (520263) Terminated (NO_ERROR): Without reason
                                          2023-03-14 06:00:06.918 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 06:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 553073
                                          2023-03-14 06:23:01.262 - info: openweathermap.0 (553073) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 06:23:12.212 - info: openweathermap.0 (553073) Terminated (NO_ERROR): Without reason
                                          2023-03-14 06:23:12.733 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 06:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 563404
                                          2023-03-14 06:30:01.348 - info: ical.0 (563404) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 06:30:06.470 - info: ical.0 (563404) Terminated (NO_ERROR): Without reason
                                          2023-03-14 06:30:07.002 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 06:43:46.176 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 06:44:56.168 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 07:00:00.032 - info: host.vm instance system.adapter.ical.0 started with pid 606465
                                          2023-03-14 07:00:01.306 - info: ical.0 (606465) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 07:00:06.427 - info: ical.0 (606465) Terminated (NO_ERROR): Without reason
                                          2023-03-14 07:00:06.946 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 07:00:16.704 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:01:26.702 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 07:03:16.497 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:04:26.499 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 07:09:24.242 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:10:34.231 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 07:10:37.535 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:11:47.438 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:12:48.734 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 07:13:58.729 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 07:23:00.044 - info: host.vm instance system.adapter.openweathermap.0 started with pid 639238
                                          2023-03-14 07:23:01.275 - info: openweathermap.0 (639238) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 07:23:06.032 - info: openweathermap.0 (639238) Terminated (NO_ERROR): Without reason
                                          2023-03-14 07:23:06.575 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 07:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 649157
                                          2023-03-14 07:30:01.288 - info: ical.0 (649157) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 07:30:06.407 - info: ical.0 (649157) Terminated (NO_ERROR): Without reason
                                          2023-03-14 07:30:06.931 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 08:00:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 692011
                                          2023-03-14 08:00:01.317 - info: ical.0 (692011) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 08:00:06.443 - info: ical.0 (692011) Terminated (NO_ERROR): Without reason
                                          2023-03-14 08:00:06.963 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 08:23:00.040 - info: host.vm instance system.adapter.openweathermap.0 started with pid 725038
                                          2023-03-14 08:23:01.355 - info: openweathermap.0 (725038) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 08:23:07.882 - info: openweathermap.0 (725038) Terminated (NO_ERROR): Without reason
                                          2023-03-14 08:23:08.403 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 08:30:00.040 - info: host.vm instance system.adapter.ical.0 started with pid 734984
                                          2023-03-14 08:30:01.278 - info: ical.0 (734984) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 08:30:06.414 - info: ical.0 (734984) Terminated (NO_ERROR): Without reason
                                          2023-03-14 08:30:06.933 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 08:32:07.938 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:33:17.937 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 08:46:52.254 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:48:02.252 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 08:48:37.222 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:49:38.300 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:50:48.299 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 08:52:34.864 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:54:47.317 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 08:57:48.079 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 08:58:51.670 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 09:00:00.036 - info: host.vm instance system.adapter.ical.0 started with pid 777833
                                          2023-03-14 09:00:01.307 - info: ical.0 (777833) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 09:00:01.658 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 09:00:06.422 - info: ical.0 (777833) Terminated (NO_ERROR): Without reason
                                          2023-03-14 09:00:06.942 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 09:01:28.468 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 09:02:38.464 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 09:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 810818
                                          2023-03-14 09:23:01.256 - info: openweathermap.0 (810818) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 09:23:09.045 - info: openweathermap.0 (810818) Terminated (NO_ERROR): Without reason
                                          2023-03-14 09:23:09.566 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 09:30:00.044 - info: host.vm instance system.adapter.ical.0 started with pid 820765
                                          2023-03-14 09:30:01.279 - info: ical.0 (820765) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 09:30:06.397 - info: ical.0 (820765) Terminated (NO_ERROR): Without reason
                                          2023-03-14 09:30:06.927 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 09:54:07.432 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 09:55:07.938 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 09:56:17.937 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 09:58:57.720 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 10:00:00.048 - info: host.vm instance system.adapter.ical.0 started with pid 863660
                                          2023-03-14 10:00:01.265 - info: ical.0 (863660) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 10:00:06.384 - info: ical.0 (863660) Terminated (NO_ERROR): Without reason
                                          2023-03-14 10:00:06.907 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 10:00:07.712 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 10:23:00.036 - info: host.vm instance system.adapter.openweathermap.0 started with pid 897248
                                          2023-03-14 10:23:01.280 - info: openweathermap.0 (897248) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 10:23:28.455 - info: openweathermap.0 (897248) Terminated (NO_ERROR): Without reason
                                          2023-03-14 10:23:28.976 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 10:25:08.048 - warn: zigbee.0 (1099) Device '0xa4c13899e33a9b60' announced itself
                                          2023-03-14 10:30:00.032 - info: host.vm instance system.adapter.ical.0 started with pid 907390
                                          2023-03-14 10:30:01.328 - info: ical.0 (907390) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 10:30:06.461 - info: ical.0 (907390) Terminated (NO_ERROR): Without reason
                                          2023-03-14 10:30:06.984 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                          2023-03-14 10:33:20.000 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 10:35:38.980 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 10:38:03.605 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                                          2023-03-14 10:39:13.602 - info: javascript.0 (929) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                                          2023-03-14 10:40:29.783 - info: admin.0 (45753) ==> Connected system.user.admin from 192.168.178.20
                                          2023-03-14 10:41:48.772 - info: host.vm stopInstance system.adapter.shelly.0 (force=false, process=true)
                                          2023-03-14 10:41:48.776 - info: shelly.0 (1069) Got terminate signal TERMINATE_YOURSELF
                                          2023-03-14 10:41:48.781 - info: shelly.0 (1069) terminating
                                          2023-03-14 10:41:48.781 - info: shelly.0 (1069) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2023-03-14 10:41:48.784 - info: host.vm stopInstance system.adapter.shelly.0 send kill signal
                                          2023-03-14 10:41:49.347 - info: host.vm instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2023-03-14 10:41:51.853 - info: host.vm instance system.adapter.shelly.0 started with pid 924356
                                          2023-03-14 10:41:53.279 - info: shelly.0 (924356) starting. Version 6.3.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 10:41:53.487 - info: shelly.0 (924356) Starting in MQTT mode. Listening on 192.168.178.64:1882 (QoS 0)
                                          2023-03-14 10:41:55.206 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                          2023-03-14 10:41:55.222 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                          2023-03-14 10:41:55.776 - info: shelly.0 (924356) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                          2023-03-14 10:42:25.217 - info: host.vm stopInstance system.adapter.shelly.0 (force=false, process=true)
                                          2023-03-14 10:42:25.221 - info: shelly.0 (924356) Got terminate signal TERMINATE_YOURSELF
                                          2023-03-14 10:42:25.220 - info: host.vm stopInstance system.adapter.shelly.0 send kill signal
                                          2023-03-14 10:42:25.227 - info: shelly.0 (924356) terminating
                                          2023-03-14 10:42:25.231 - info: shelly.0 (924356) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2023-03-14 10:42:25.793 - info: host.vm instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2023-03-14 10:42:28.280 - info: host.vm instance system.adapter.shelly.0 started with pid 925295
                                          2023-03-14 10:42:29.678 - info: shelly.0 (925295) starting. Version 6.3.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.1, js-controller: 4.0.24
                                          2023-03-14 10:42:29.840 - info: shelly.0 (925295) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
                                          2023-03-14 10:42:31.024 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                                          2023-03-14 10:42:31.464 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                                          2023-03-14 10:42:31.525 - info: shelly.0 (925295) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                                          
                                          da_WoodyD Offline
                                          da_WoodyD Offline
                                          da_Woody
                                          schrieb am zuletzt editiert von
                                          #35

                                          @acem der mqtt adapter war deaktiviert laut deiner aussage. sollte damit kein problem machen. ich hab das dingens auch laufen. anderer port halt. mqtt ist bei mir auf 1885 unterwegs.
                                          dein log ist ja lustig. mit info bekommst du latürnich alles rein. :)

                                          gruß vom Woody
                                          HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                                          A 1 Antwort Letzte Antwort
                                          0

                                          Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                          Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                          Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                          Registrieren Anmelden
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          613

                                          Online

                                          32.8k

                                          Benutzer

                                          82.8k

                                          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