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

    @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
                            • da_WoodyD da_Woody

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

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

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

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

                              Info war beim IoBroker von Anfang an Installiert!

                              Mit dem Shelly Plus 1 für die Küchenlampe habe ich immer noch Probleme mit MQTT laut dem Log.

                              2023-03-14 11:40:26.661 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 11:40:26.736 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 30s
                              2023-03-14 11:40:27.341 - info: cloud.0 (1116) Trying to connect as system.user.admin to cloud
                              2023-03-14 11:40:27.517 - info: cloud.0 (1116) Connection changed: connect
                              2023-03-14 11:40:29.109 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                              2023-03-14 11:40:50.988 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20
                              2023-03-14 11:40:57.287 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 35s
                              2023-03-14 11:41:32.799 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 40s
                              2023-03-14 11:42:13.326 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 45s
                              2023-03-14 11:42:58.895 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 50s
                              2023-03-14 11:43:49.462 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 55s
                              2023-03-14 11:44:44.990 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:45:45.542 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:46:46.074 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:47:46.620 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:48:47.144 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:49:47.662 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:50:48.226 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:51:48.772 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:52:49.304 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:53:49.861 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:54:50.379 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:55:50.915 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:56:51.484 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:57:52.002 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:58:52.524 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 11:59:53.045 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:00:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 30884
                              2023-03-14 12:00:01.329 - info: ical.0 (30884) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 12:00:06.459 - info: ical.0 (30884) Terminated (NO_ERROR): Without reason
                              2023-03-14 12:00:06.978 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 12:00:53.613 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:01:54.150 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:02:54.708 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:03:55.238 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:04:55.766 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:05:56.345 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:06:47.545 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 12:06:51.828 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                              2023-03-14 12:06:57.093 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:07:57.638 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:08:58.189 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:09:45.070 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20
                              2023-03-14 12:09:58.779 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:10:21.479 - error: host.vm Invalid request getRepository. "callback" or "from" is null
                              2023-03-14 12:10:59.320 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:11:59.856 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:13:00.414 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:14:00.928 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:15:01.449 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:16:01.973 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:17:02.489 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:18:03.039 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:19:03.590 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:20:04.110 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:21:04.628 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:22:05.179 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:23:00.037 - info: host.vm instance system.adapter.openweathermap.0 started with pid 63494
                              2023-03-14 12:23:01.224 - info: openweathermap.0 (63494) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 12:23:05.759 - info: alexa2.0 (963) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:23:09.984 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 12:23:14.175 - info: openweathermap.0 (63494) Terminated (NO_ERROR): Without reason
                              2023-03-14 12:23:14.692 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 12:23:27.687 - info: host.vm stopInstance system.adapter.alexa2.0 (force=false, process=true)
                              2023-03-14 12:23:27.695 - info: alexa2.0 (963) Got terminate signal TERMINATE_YOURSELF
                              2023-03-14 12:23:27.697 - info: alexa2.0 (963) terminating
                              2023-03-14 12:23:27.698 - info: alexa2.0 (963) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2023-03-14 12:23:27.777 - info: host.vm stopInstance system.adapter.alexa2.0 send kill signal
                              2023-03-14 12:23:28.304 - info: host.vm instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2023-03-14 12:23:30.838 - info: host.vm instance system.adapter.alexa2.0 started with pid 64262
                              2023-03-14 12:23:31.992 - info: alexa2.0 (64262) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 12:23:32.047 - info: alexa2.0 (64262) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
                              2023-03-14 12:23:32.050 - info: alexa2.0 (64262) Proxy IP not set, use first network interface (192.168.178.64) instead
                              2023-03-14 12:23:36.231 - info: alexa2.0 (64262) Initialize all Device states ...
                              2023-03-14 12:23:37.808 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20
                              2023-03-14 12:23:50.879 - info: alexa2.0 (64262) No smart home devices to query
                              2023-03-14 12:23:51.895 - info: alexa2.0 (64262) Subscribing to states...
                              2023-03-14 12:23:53.381 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 10s
                              2023-03-14 12:23:58.797 - info: alexa2.0 (64262) Initialization Done ...
                              2023-03-14 12:24:03.890 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 15s
                              2023-03-14 12:24:19.394 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 20s
                              2023-03-14 12:24:39.915 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 25s
                              2023-03-14 12:24:45.525 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20 admin
                              2023-03-14 12:25:05.424 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 30s
                              2023-03-14 12:25:11.319 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:25:35.972 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 35s
                              2023-03-14 12:26:11.504 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 40s
                              2023-03-14 12:26:21.311 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 12:26:52.026 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 45s
                              2023-03-14 12:27:18.445 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:27:37.546 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 50s
                              2023-03-14 12:28:22.667 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:28:28.151 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 55s
                              2023-03-14 12:29:23.720 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:29:32.657 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 12:30:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 73594
                              2023-03-14 12:30:01.305 - info: ical.0 (73594) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 12:30:06.421 - info: ical.0 (73594) Terminated (NO_ERROR): Without reason
                              2023-03-14 12:30:06.945 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 12:30:24.332 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:30:50.767 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:31:24.847 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:32:00.761 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 12:32:25.366 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:32:26.727 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:33:25.879 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:33:36.726 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 12:34:26.405 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:35:26.996 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:36:27.610 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:37:02.599 - error: cloud.0 (1116) Ping timeout
                              2023-03-14 12:37:02.866 - warn: telegram.0 (936) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                              2023-03-14 12:37:04.091 - info: sonoff.0 (1069) Client [Schlafzimmerlicht] reconnected. Old secret 1678790356005_7181. New secret 1678793824089_5261
                              2023-03-14 12:37:04.094 - info: sonoff.0 (1069) Client [Esstisch] reconnected. Old secret 1678790355994_8545. New secret 1678793824090_8107
                              2023-03-14 12:37:04.619 - info: sonoff.0 (1069) Client [Betuels_Zimmerlicht] reconnected. Old secret 1678790356394_4916. New secret 1678793824618_5979
                              2023-03-14 12:37:07.484 - info: sonoff.0 (1069) Client [Elas_Zimmerlicht] reconnected. Old secret 1678790356325_7112. New secret 1678793827483_3487
                              2023-03-14 12:37:28.126 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:37:35.686 - info: sonoff.0 (1069) Client [WClicht] reconnected. Old secret 1678790356507_5065. New secret 1678793855685_3994
                              2023-03-14 12:37:35.799 - info: sonoff.0 (1069) Client [Badlicht] reconnected. Old secret 1678790356731_9333. New secret 1678793855799_2575
                              2023-03-14 12:38:00.930 - info: sonoff.0 (1069) Client [Balkonlicht] reconnected. Old secret 1678790355887_6961. New secret 1678793880929_8885
                              2023-03-14 12:38:02.612 - info: cloud.0 (1116) Trying to connect as system.user.admin to cloud
                              2023-03-14 12:38:02.790 - info: cloud.0 (1116) Connection changed: connect
                              2023-03-14 12:38:05.248 - info: sonoff.0 (1069) Client [Wohnzimmerlicht] reconnected. Old secret 1678790356195_7710. New secret 1678793885247_5523
                              2023-03-14 12:38:05.810 - info: sonoff.0 (1069) Client [Flurlicht] reconnected. Old secret 1678790355807_555. New secret 1678793885809_9908
                              2023-03-14 12:38:06.215 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-14 12:38:06.311 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                              2023-03-14 12:38:06.681 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                              2023-03-14 12:38:28.631 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:39:29.168 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:40:29.677 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:41:30.203 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:42:30.730 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:43:31.263 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:44:31.792 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:45:32.325 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:46:32.828 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:47:33.320 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:48:33.849 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:49:34.365 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:50:34.885 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:51:35.379 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:52:35.914 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:53:05.892 - info: sonoff.0 (1069) Client [Balkonlicht] reconnected. Old secret 1678793880929_8885. New secret 1678794785891_9058
                              2023-03-14 12:53:07.810 - error: cloud.0 (1116) Ping timeout
                              2023-03-14 12:53:07.811 - info: cloud.0 (1116) Connection changed: Ping timeout
                              2023-03-14 12:53:07.811 - info: cloud.0 (1116) Connection lost
                              2023-03-14 12:53:35.637 - info: sonoff.0 (1069) Client [Esstisch] connection closed: closed
                              2023-03-14 12:53:35.648 - info: sonoff.0 (1069) Client [Schlafzimmerlicht] connection closed: closed
                              2023-03-14 12:53:36.235 - info: sonoff.0 (1069) Client [Betuels_Zimmerlicht] connection closed: closed
                              2023-03-14 12:53:36.617 - info: sonoff.0 (1069) Client [Wohnzimmerlicht] connection closed: closed
                              2023-03-14 12:53:36.851 - info: sonoff.0 (1069) Client [Badlicht] connection closed: closed
                              2023-03-14 12:53:36.998 - info: sonoff.0 (1069) Client [WClicht] connection closed: closed
                              2023-03-14 12:53:37.395 - info: sonoff.0 (1069) Client [Flurlicht] connection closed: closed
                              2023-03-14 12:53:38.992 - info: sonoff.0 (1069) Client [Elas_Zimmerlicht] connection closed: closed
                              2023-03-14 12:54:05.923 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:54:05.924 - info: alexa2.0 (64262) Alexa-Push-Connection Error: WebSocket was closed before the connection was established
                              2023-03-14 12:54:05.924 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:54:07.821 - info: cloud.0 (1116) Trying to connect as system.user.admin to cloud
                              2023-03-14 12:54:15.364 - info: cloud.0 (1116) Connection changed: connect
                              2023-03-14 12:54:27.771 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 12:54:27.775 - warn: sonoff.0 (1069) Client "Flurlicht" not connected
                              2023-03-14 12:54:39.032 - info: sonoff.0 (1069) Client [Esstisch] connected with secret 1678794879031_1867
                              2023-03-14 12:54:39.344 - info: sonoff.0 (1069) Client [Schlafzimmerlicht] connected with secret 1678794879343_6045
                              2023-03-14 12:54:39.568 - info: sonoff.0 (1069) Client [Betuels_Zimmerlicht] connected with secret 1678794879568_8479
                              2023-03-14 12:54:40.063 - info: sonoff.0 (1069) Client [Badlicht] connected with secret 1678794880061_4663
                              2023-03-14 12:54:40.263 - info: sonoff.0 (1069) Client [Wohnzimmerlicht] connected with secret 1678794880259_6792
                              2023-03-14 12:54:40.661 - info: sonoff.0 (1069) Client [WClicht] connected with secret 1678794880661_7292
                              2023-03-14 12:54:41.080 - info: sonoff.0 (1069) Client [Flurlicht] connected with secret 1678794881078_8829
                              2023-03-14 12:54:42.720 - info: sonoff.0 (1069) Client [Elas_Zimmerlicht] connected with secret 1678794882719_355
                              2023-03-14 12:55:06.515 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:55:37.769 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 12:56:07.041 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:57:07.558 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:58:08.052 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 12:59:08.590 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 116292
                              2023-03-14 13:00:01.394 - info: ical.0 (116292) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 13:00:06.513 - info: ical.0 (116292) Terminated (NO_ERROR): Without reason
                              2023-03-14 13:00:07.039 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 13:00:09.110 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:01:09.654 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:02:10.149 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:03:10.660 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:04:11.166 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:05:11.713 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:06:12.237 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:07:12.734 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:08:13.250 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:09:13.803 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:10:14.326 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:11:14.896 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:12:15.432 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:13:15.972 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:14:16.519 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:15:17.039 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:16:17.579 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:17:18.180 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:18:18.731 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:19:19.268 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:20:19.803 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:21:20.309 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:22:20.854 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 148932
                              2023-03-14 13:23:01.308 - info: openweathermap.0 (148932) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 13:23:10.770 - info: openweathermap.0 (148932) Terminated (NO_ERROR): Without reason
                              2023-03-14 13:23:11.289 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 13:23:21.359 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:24:21.907 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:25:22.445 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:26:22.990 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:27:23.507 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:28:24.023 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:29:24.575 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:30:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 158964
                              2023-03-14 13:30:01.284 - info: ical.0 (158964) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 13:30:06.405 - info: ical.0 (158964) Terminated (NO_ERROR): Without reason
                              2023-03-14 13:30:06.927 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 13:30:25.237 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:31:25.767 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:31:30.764 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 13:31:57.826 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 13:32:00.576 - info: host.vm Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                              2023-03-14 13:32:20.141 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20
                              2023-03-14 13:32:20.143 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20 admin
                              2023-03-14 13:32:26.309 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:32:38.346 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 13:33:26.854 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:33:48.342 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 13:33:52.498 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 13:34:27.389 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:35:02.474 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 13:35:23.494 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 13:35:27.934 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:36:24.308 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 13:36:28.491 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:37:29.039 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:37:34.303 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 13:38:29.596 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:39:30.121 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:40:30.662 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:41:31.151 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:42:31.691 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:43:32.253 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:44:32.775 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:45:33.334 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:46:33.867 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:47:34.420 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:48:34.969 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:49:35.619 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:50:36.171 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:51:36.792 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:52:37.331 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:53:37.899 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:54:38.413 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:55:38.951 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:56:39.442 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:57:40.004 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:58:40.510 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 13:59:41.060 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - retry: Retry Connection in 60s
                              2023-03-14 14:00:00.041 - info: host.vm instance system.adapter.ical.0 started with pid 201644
                              2023-03-14 14:00:01.309 - info: ical.0 (201644) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 14:00:06.434 - info: ical.0 (201644) Terminated (NO_ERROR): Without reason
                              2023-03-14 14:00:06.955 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 14:00:41.611 - info: alexa2.0 (64262) Alexa-Push-Connection disconnected - fallback to poll data: Too many failed retries. Check cookie and data
                              2023-03-14 14:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 234371
                              2023-03-14 14:23:01.302 - info: openweathermap.0 (234371) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 14:23:16.110 - info: openweathermap.0 (234371) Terminated (NO_ERROR): Without reason
                              2023-03-14 14:23:16.631 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 14:30:00.041 - info: host.vm instance system.adapter.ical.0 started with pid 244353
                              2023-03-14 14:30:01.292 - info: ical.0 (244353) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 14:30:06.417 - info: ical.0 (244353) Terminated (NO_ERROR): Without reason
                              2023-03-14 14:30:06.951 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 15:00:00.041 - info: host.vm instance system.adapter.ical.0 started with pid 286993
                              2023-03-14 15:00:01.291 - info: ical.0 (286993) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 15:00:06.427 - info: ical.0 (286993) Terminated (NO_ERROR): Without reason
                              2023-03-14 15:00:06.952 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 15:23:00.034 - info: host.vm instance system.adapter.openweathermap.0 started with pid 319739
                              2023-03-14 15:23:01.292 - info: openweathermap.0 (319739) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 15:23:14.812 - info: openweathermap.0 (319739) Terminated (NO_ERROR): Without reason
                              2023-03-14 15:23:15.330 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 15:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 329669
                              2023-03-14 15:30:01.346 - info: ical.0 (329669) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 15:30:06.465 - info: ical.0 (329669) Terminated (NO_ERROR): Without reason
                              2023-03-14 15:30:06.982 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 16:00:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 372360
                              2023-03-14 16:00:01.332 - info: ical.0 (372360) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 16:00:06.467 - info: ical.0 (372360) Terminated (NO_ERROR): Without reason
                              2023-03-14 16:00:06.987 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 16:02:29.852 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 16:03:39.850 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 16:04:52.359 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 16:06:02.350 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 16:06:54.819 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 16:08:04.818 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 16:19:27.941 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 16:20:37.941 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 16:23:00.045 - info: host.vm instance system.adapter.openweathermap.0 started with pid 405229
                              2023-03-14 16:23:01.261 - info: openweathermap.0 (405229) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 16:23:05.437 - info: openweathermap.0 (405229) Terminated (NO_ERROR): Without reason
                              2023-03-14 16:23:05.958 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 16:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 415169
                              2023-03-14 16:30:01.266 - info: ical.0 (415169) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 16:30:06.390 - info: ical.0 (415169) Terminated (NO_ERROR): Without reason
                              2023-03-14 16:30:06.910 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 17:00:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 457858
                              2023-03-14 17:00:01.305 - info: ical.0 (457858) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 17:00:06.428 - info: ical.0 (457858) Terminated (NO_ERROR): Without reason
                              2023-03-14 17:00:06.948 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 17:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 490654
                              2023-03-14 17:23:01.257 - info: openweathermap.0 (490654) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 17:23:12.263 - info: openweathermap.0 (490654) Terminated (NO_ERROR): Without reason
                              2023-03-14 17:23:12.779 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 17:26:45.683 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:27:55.674 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 500523
                              2023-03-14 17:30:01.275 - info: ical.0 (500523) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 17:30:06.390 - info: ical.0 (500523) Terminated (NO_ERROR): Without reason
                              2023-03-14 17:30:06.913 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 17:35:55.860 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:37:05.858 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:37:36.078 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:38:46.080 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:48:04.802 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:49:14.805 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:50:25.842 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:51:35.840 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:51:48.414 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:52:58.413 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:53:40.055 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 17:54:50.052 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 17:56:48.767 - warn: telegram.0 (936) polling_error: EFATAL, EFATAL: Error: socket hang up
                              2023-03-14 18:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 543155
                              2023-03-14 18:00:01.261 - info: ical.0 (543155) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 18:00:06.390 - info: ical.0 (543155) Terminated (NO_ERROR): Without reason
                              2023-03-14 18:00:06.909 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 18:02:43.561 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:03:53.560 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:05:19.871 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:06:29.869 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:09:27.077 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:10:37.075 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:18:23.659 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:19:33.616 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 575914
                              2023-03-14 18:23:01.249 - info: openweathermap.0 (575914) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 18:23:33.596 - info: openweathermap.0 (575914) Terminated (NO_ERROR): Without reason
                              2023-03-14 18:23:34.114 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 18:30:00.041 - info: host.vm instance system.adapter.ical.0 started with pid 585829
                              2023-03-14 18:30:01.261 - info: ical.0 (585829) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 18:30:06.377 - info: ical.0 (585829) Terminated (NO_ERROR): Without reason
                              2023-03-14 18:30:06.899 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 18:35:55.725 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:37:05.717 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:37:47.211 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:38:57.213 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:39:19.138 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:40:26.869 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:41:36.866 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:42:15.603 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:43:25.602 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 18:54:31.944 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 18:55:41.944 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 19:00:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 628497
                              2023-03-14 19:00:01.303 - info: ical.0 (628497) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 19:00:06.435 - info: ical.0 (628497) Terminated (NO_ERROR): Without reason
                              2023-03-14 19:00:06.974 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 19:23:00.037 - info: host.vm instance system.adapter.openweathermap.0 started with pid 661169
                              2023-03-14 19:23:01.279 - info: openweathermap.0 (661169) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 19:23:09.100 - info: openweathermap.0 (661169) Terminated (NO_ERROR): Without reason
                              2023-03-14 19:23:09.619 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 19:29:09.031 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 19:30:00.033 - info: host.vm instance system.adapter.ical.0 started with pid 671173
                              2023-03-14 19:30:01.264 - info: ical.0 (671173) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 19:30:06.390 - info: ical.0 (671173) Terminated (NO_ERROR): Without reason
                              2023-03-14 19:30:06.946 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 19:30:19.028 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 19:31:45.667 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 19:32:55.621 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 19:34:19.660 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 19:35:29.606 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 20:00:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 713789
                              2023-03-14 20:00:01.291 - info: ical.0 (713789) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 20:00:06.408 - info: ical.0 (713789) Terminated (NO_ERROR): Without reason
                              2023-03-14 20:00:06.930 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 20:15:59.239 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:17:05.914 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:18:15.681 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:19:25.676 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 20:19:40.347 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:20:50.342 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 20:21:36.545 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:22:46.543 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 20:23:00.054 - info: host.vm instance system.adapter.openweathermap.0 started with pid 746367
                              2023-03-14 20:23:01.290 - info: openweathermap.0 (746367) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 20:23:11.170 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 20:23:23.608 - info: openweathermap.0 (746367) Terminated (NO_ERROR): Without reason
                              2023-03-14 20:23:24.126 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 20:30:00.041 - info: host.vm instance system.adapter.ical.0 started with pid 756411
                              2023-03-14 20:30:01.310 - info: ical.0 (756411) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 20:30:06.429 - info: ical.0 (756411) Terminated (NO_ERROR): Without reason
                              2023-03-14 20:30:06.952 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 21:00:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 799041
                              2023-03-14 21:00:01.266 - info: ical.0 (799041) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 21:00:06.393 - info: ical.0 (799041) Terminated (NO_ERROR): Without reason
                              2023-03-14 21:00:06.913 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 21:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 831622
                              2023-03-14 21:23:01.277 - info: openweathermap.0 (831622) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 21:23:18.198 - info: openweathermap.0 (831622) Terminated (NO_ERROR): Without reason
                              2023-03-14 21:23:18.719 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 21:30:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 841669
                              2023-03-14 21:30:01.321 - info: ical.0 (841669) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 21:30:06.450 - info: ical.0 (841669) Terminated (NO_ERROR): Without reason
                              2023-03-14 21:30:06.976 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 21:34:22.815 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 21:35:25.482 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 21:36:35.480 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 22:00:00.029 - info: host.vm instance system.adapter.ical.0 started with pid 884432
                              2023-03-14 22:00:01.307 - info: ical.0 (884432) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 22:00:06.425 - info: ical.0 (884432) Terminated (NO_ERROR): Without reason
                              2023-03-14 22:00:06.955 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 22:00:18.816 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 22:01:28.815 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 22:01:50.755 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 22:03:00.745 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 22:07:20.359 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 22:08:30.357 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 22:23:00.029 - info: host.vm instance system.adapter.openweathermap.0 started with pid 917039
                              2023-03-14 22:23:01.250 - info: openweathermap.0 (917039) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 22:23:27.926 - info: openweathermap.0 (917039) Terminated (NO_ERROR): Without reason
                              2023-03-14 22:23:28.445 - info: host.vm instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 22:28:08.813 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 22:29:18.812 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 22:30:00.037 - info: host.vm instance system.adapter.ical.0 started with pid 927092
                              2023-03-14 22:30:01.274 - info: ical.0 (927092) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 22:30:06.399 - info: ical.0 (927092) Terminated (NO_ERROR): Without reason
                              2023-03-14 22:30:06.924 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 23:00:00.043 - info: host.vm instance system.adapter.ical.0 started with pid 970171
                              2023-03-14 23:00:01.344 - info: ical.0 (970171) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 23:00:06.460 - info: ical.0 (970171) Terminated (NO_ERROR): Without reason
                              2023-03-14 23:00:06.982 - info: host.vm instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2023-03-14 23:09:29.390 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 23:10:39.251 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 23:11:49.244 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 23:11:53.672 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 23:13:03.667 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 23:14:06.157 - warn: telegram.0 (936) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
                              2023-03-14 23:14:07.174 - info: sonoff.0 (1069) Client [WClicht] reconnected. Old secret 1678794880661_7292. New secret 1678832047173_2248
                              2023-03-14 23:14:07.189 - info: sonoff.0 (1069) Client [Flurlicht] reconnected. Old secret 1678794881078_8829. New secret 1678832047187_4368
                              2023-03-14 23:14:07.491 - info: sonoff.0 (1069) Client [Elas_Zimmerlicht] reconnected. Old secret 1678794882719_355. New secret 1678832047491_3681
                              2023-03-14 23:14:07.693 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                              2023-03-14 23:14:08.321 - error: shelly.0 (1054) [MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a3a148"
                              2023-03-14 23:14:08.378 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-441793ad7988" connected!
                              2023-03-14 23:14:08.965 - info: sonoff.0 (1069) Client [Balkonlicht] reconnected. Old secret 1678794785891_9058. New secret 1678832048963_3744
                              2023-03-14 23:14:16.967 - info: sonoff.0 (1069) Client [Betuels_Zimmerlicht] reconnected. Old secret 1678794879568_8479. New secret 1678832056966_4941
                              2023-03-14 23:14:16.978 - info: sonoff.0 (1069) Client [Schlafzimmerlicht] reconnected. Old secret 1678794879343_6045. New secret 1678832056977_282
                              2023-03-14 23:14:16.986 - info: sonoff.0 (1069) Client [Badlicht] reconnected. Old secret 1678794880061_4663. New secret 1678832056986_4360
                              2023-03-14 23:14:17.047 - info: sonoff.0 (1069) Client [Esstisch] reconnected. Old secret 1678794879031_1867. New secret 1678832057047_3807
                              2023-03-14 23:14:18.112 - info: sonoff.0 (1069) Client [Wohnzimmerlicht] reconnected. Old secret 1678794880259_6792. New secret 1678832058111_5259
                              2023-03-14 23:14:22.092 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 23:14:26.865 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:14:44.986 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:15:03.847 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:15:09.795 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus2pm-b8d61a890fc8" connected!
                              2023-03-14 23:15:22.951 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:15:32.078 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 23:15:41.613 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:16:00.160 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:16:19.857 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:16:38.840 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:16:56.853 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:17:14.853 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:17:32.855 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:17:50.081 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:18:03.761 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 23:18:07.857 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:18:25.852 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:18:44.892 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:19:02.873 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:19:20.872 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:19:38.877 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:19:57.866 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:20:15.860 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:20:33.869 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:20:51.422 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:21:11.001 - warn: shelly.0 (1054) [Mqtt.topicPrefix] 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1): Configured mqtt topic prefix "shellyplus1-441793a3a148" and actual topic prefix "undefined" do not match. Please check configuration
                              2023-03-14 23:21:19.896 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht an
                              2023-03-14 23:21:26.445 - info: shelly.0 (1054) [MQTT] Client Disconnect: 192.168.178.77 (shellyplus1 / shellyplus1-441793a3a148 / shellyplus1#441793a3a148#1)
                              2023-03-14 23:21:31.331 - info: shelly.0 (1054) [MQTT] Device with client id "shellyplus1-441793a3a148" connected!
                              2023-03-14 23:22:29.894 - info: javascript.0 (921) script.js.SmartHome.Aqara_Bewegungsmelder.Bewegungsmelder: Flurlicht aus
                              2023-03-14 23:22:52.477 - info: admin.0 (876) ==> Connected system.user.admin from 192.168.178.20
                              2023-03-14 23:23:00.033 - info: host.vm instance system.adapter.openweathermap.0 started with pid 1003247
                              2023-03-14 23:23:01.243 - info: openweathermap.0 (1003247) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.19.1, js-controller: 4.0.24
                              2023-03-14 23:23:07.734 - info: admin.0 (876) <== Disconnect system.user.admin from 192.168.178.20
                              

                              Firmware war auf 0.14 ich habe mal auf die neueste 0.14.1 Aktualisiert. Kann ich den auch löschen! wird mir dann im Log nichts mehr angezeigt?

                              Was könnte das Problem verursachen? mit der Meldung im Log?

                              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

                              607

                              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