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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Adapter werden neu gestartet

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    23
    1
    1.3k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.3k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.5k

Adapter werden neu gestartet

Geplant Angeheftet Gesperrt Verschoben Error/Bug
88 Beiträge 9 Kommentatoren 8.6k Aufrufe 6 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • crunchipC crunchip

    @matrose65 nur reine Vermutung meinerseits, aber wenn ich die verschiedenen Logs betrachte, fällt mir immer zu Beginn hm-rpc auf, Zufall?
    allerdings besitze ich kein hm...

    hm-rpc.0 (147734) xmlrpc -> 192.168.178.93:2001/ init ["http://192.168.178.92:2001",""]
    hm-rpc.0 (147734) Disconnected
    
    M Offline
    M Offline
    matrose65
    schrieb am zuletzt editiert von
    #58

    @crunchip
    Guten Morgen
    Ok. Danke, das kann ich auch noch beobachten.
    Der hm-rpc läuft auf Raspberrymatic in einer eigenen VM.
    Der hat aber eigentlich noch nie Probleme gemacht

    1 Antwort Letzte Antwort
    0
    • GlasfaserG Glasfaser

      @matrose65 sagte in Adapter werden neu gestartet:

      system.adapter.netatmo-crawler.0 terminated due to SIGSEGV]

      Kannst du diesen Adapter längere Zeit mal ausschalten und das verhalten dann weiter beobachten !?

      M Offline
      M Offline
      matrose65
      schrieb am zuletzt editiert von
      #59

      @glasfaser said in Adapter werden neu gestartet:

      system.adapter.netatmo-crawler.0 terminated due to SIGSEGV]

      Kannst du diesen Adapter längere Zeit mal ausschalten und das verhalten dann weiter beobachten !?

      Hallo

      Jetzt ist der netatmo-crawler 2 Tage aus.
      Ich weiß zwar nicht mehr wie kalt es draußen ist, aber der Fehler ist noch nicht wieder aufgetreten.

      1 Antwort Letzte Antwort
      0
      • crunchipC crunchip

        @matrose65 sagte in Adapter werden neu gestartet:

        Ich habe schon den Proxmox server und auch den IOB neugestartet.

        Proxmox Server neu gestartet ohne iobroker zuvor zu beenden?
        logisch das dann Code 7 (already running) entstehen

        Meister MopperM Offline
        Meister MopperM Offline
        Meister Mopper
        schrieb am zuletzt editiert von
        #60

        @crunchip sagte in Adapter werden neu gestartet:

        Proxmox Server neu gestartet ohne iobroker zuvor zu beenden?
        logisch das dann Code 7 (already running) entstehen

        Muss mal hier zu meinem Verständnis nachhaken.

        Wenn ich auf einem Proxmox node ein reboot anstoße, werden alle LXC und VM dieses node heruntergefahren bevor ein reboot gestartet wird.
        Ich hatte bisher im Anschluss daran noch nie Probleme.

        Ist es ratsam, alle LXC und VM vor einem reboot manuell runterzufahren? Und wenn ja, warum?

        Proxmox und HA

        W 1 Antwort Letzte Antwort
        0
        • Meister MopperM Meister Mopper

          @crunchip sagte in Adapter werden neu gestartet:

          Proxmox Server neu gestartet ohne iobroker zuvor zu beenden?
          logisch das dann Code 7 (already running) entstehen

          Muss mal hier zu meinem Verständnis nachhaken.

          Wenn ich auf einem Proxmox node ein reboot anstoße, werden alle LXC und VM dieses node heruntergefahren bevor ein reboot gestartet wird.
          Ich hatte bisher im Anschluss daran noch nie Probleme.

          Ist es ratsam, alle LXC und VM vor einem reboot manuell runterzufahren? Und wenn ja, warum?

          W Online
          W Online
          Wildbill
          schrieb am zuletzt editiert von Wildbill
          #61

          @meister-mopper Nein, man muss da manuell gar nix machen. Wenn iobroker in einer VM oder einem LXC installiert ist, so wird iobroker (und die anderen Dienste) sauber beendet, bervor der Neustart erfolgt. Gleiches gilt für LXC und VM generell unter iobroker. Wird der Host heruntergefahren, so fährt Proxmox vorher alle laufenden VM und LXC runter und meldet sich erst dann ab, wenn alles steht und das System fährt dann vollständig runter.

          Voraussetzung ist aber natürlich jeweils, dass der Anwender sauber herunterfährt. Wenn man eine VM oder einen LXC unter Proxmox per "STOP" anstatt Shutdown abschiesst, so wird ein darin laufender iobroker (oder auch alles andere) natürlich nicht gestoppt. Probleme sind dann vorprogrammiert, ist quasi wie das Steckerziehen bei einem Rechner ohne Herunterfahren. Gleiches gilt für den Host. Zieht man da den Stecker ohne vorher einen shutdown zu machen, so sind alle LXC und VM natürlich auch nicht sauber runtergefahren und nehmen das unter Umständen übel.

          Wenn alles sauber konfiguriert ist und läuft, so kann man mit einem "sudo reboot" oder "sudo shutdown" , egal ob innerhalb einer VM/LXC oder direkt beim Host, auch wenn noch VM/LXC laufen, eigentlich nichts falsch machen, es sollte alles sauber beenden und gegebenenfalls neu starten.

          Gruss, Jürgen

          crunchipC 1 Antwort Letzte Antwort
          0
          • crunchipC Abwesend
            crunchipC Abwesend
            crunchip
            Forum Testing Most Active
            schrieb am zuletzt editiert von
            #62

            @meister-mopper sagte in Adapter werden neu gestartet:

            Ist es ratsam, alle LXC und VM vor einem reboot manuell runterzufahren? Und wenn ja, warum?

            nein das erledigt ja eigentlich Proxmox,
            jedoch kommt es vor, zumindest bei mir
            wenn die VM einfach nur neugestartet wird, iobroker nicht korrekt beendet wurde und dadurch noch Prozesse liefen, folglich erscheint dann bei dem ein oder anderen Adapter ein code7.
            Daher die Anmerkung
            Ich habe mir es deshalb angewöhnt, vor einem Neustart der VM, iobroker zu stoppen

            umgestiegen von Proxmox auf Unraid

            1 Antwort Letzte Antwort
            0
            • W Wildbill

              @meister-mopper Nein, man muss da manuell gar nix machen. Wenn iobroker in einer VM oder einem LXC installiert ist, so wird iobroker (und die anderen Dienste) sauber beendet, bervor der Neustart erfolgt. Gleiches gilt für LXC und VM generell unter iobroker. Wird der Host heruntergefahren, so fährt Proxmox vorher alle laufenden VM und LXC runter und meldet sich erst dann ab, wenn alles steht und das System fährt dann vollständig runter.

              Voraussetzung ist aber natürlich jeweils, dass der Anwender sauber herunterfährt. Wenn man eine VM oder einen LXC unter Proxmox per "STOP" anstatt Shutdown abschiesst, so wird ein darin laufender iobroker (oder auch alles andere) natürlich nicht gestoppt. Probleme sind dann vorprogrammiert, ist quasi wie das Steckerziehen bei einem Rechner ohne Herunterfahren. Gleiches gilt für den Host. Zieht man da den Stecker ohne vorher einen shutdown zu machen, so sind alle LXC und VM natürlich auch nicht sauber runtergefahren und nehmen das unter Umständen übel.

              Wenn alles sauber konfiguriert ist und läuft, so kann man mit einem "sudo reboot" oder "sudo shutdown" , egal ob innerhalb einer VM/LXC oder direkt beim Host, auch wenn noch VM/LXC laufen, eigentlich nichts falsch machen, es sollte alles sauber beenden und gegebenenfalls neu starten.

              Gruss, Jürgen

              crunchipC Abwesend
              crunchipC Abwesend
              crunchip
              Forum Testing Most Active
              schrieb am zuletzt editiert von
              #63

              @wildbill sagte in Adapter werden neu gestartet:

              Wenn man eine VM oder einen LXC unter Proxmox per "STOP" anstatt Shutdown

              das ist bei mir hin und wieder das Problem,
              ein "Herunterfahren" bleibt hin und wieder hängen und die VM beendet sich dann nicht mehr
              dann hilft nur ein

              qm stop <vmid>
              

              umgestiegen von Proxmox auf Unraid

              W 1 Antwort Letzte Antwort
              0
              • crunchipC crunchip

                @wildbill sagte in Adapter werden neu gestartet:

                Wenn man eine VM oder einen LXC unter Proxmox per "STOP" anstatt Shutdown

                das ist bei mir hin und wieder das Problem,
                ein "Herunterfahren" bleibt hin und wieder hängen und die VM beendet sich dann nicht mehr
                dann hilft nur ein

                qm stop <vmid>
                
                W Online
                W Online
                Wildbill
                schrieb am zuletzt editiert von
                #64

                @crunchip Hast Du in der VM den Qemu guest agent installiert und aktiviert? Wenn nicht, könnte es sein, dass es da Probleme geben könnte, wenn Befehle zum Neustart oder Herunterfahren von "aussen" vom Host zum Guest geschickt werden. Hast Du das Problem auch, wenn Du per SSH in die VM direkt gehst und dort den Shutdown auslöst?
                Gruss, Jürgen

                crunchipC 1 Antwort Letzte Antwort
                0
                • W Wildbill

                  @crunchip Hast Du in der VM den Qemu guest agent installiert und aktiviert? Wenn nicht, könnte es sein, dass es da Probleme geben könnte, wenn Befehle zum Neustart oder Herunterfahren von "aussen" vom Host zum Guest geschickt werden. Hast Du das Problem auch, wenn Du per SSH in die VM direkt gehst und dort den Shutdown auslöst?
                  Gruss, Jürgen

                  crunchipC Abwesend
                  crunchipC Abwesend
                  crunchip
                  Forum Testing Most Active
                  schrieb am zuletzt editiert von
                  #65

                  @wildbill sagte in Adapter werden neu gestartet:

                  Hast Du in der VM den Qemu guest agent installiert und aktiviert?

                  ja

                  @wildbill sagte in Adapter werden neu gestartet:

                  Hast Du das Problem auch, wenn Du per SSH in die VM direkt gehst und dort den Shutdown auslöst?

                  hab ich nicht probiert, es kommt ja auch nur ab und an mal vor

                  umgestiegen von Proxmox auf Unraid

                  W 1 Antwort Letzte Antwort
                  0
                  • crunchipC crunchip

                    @wildbill sagte in Adapter werden neu gestartet:

                    Hast Du in der VM den Qemu guest agent installiert und aktiviert?

                    ja

                    @wildbill sagte in Adapter werden neu gestartet:

                    Hast Du das Problem auch, wenn Du per SSH in die VM direkt gehst und dort den Shutdown auslöst?

                    hab ich nicht probiert, es kommt ja auch nur ab und an mal vor

                    W Online
                    W Online
                    Wildbill
                    schrieb am zuletzt editiert von
                    #66

                    @crunchip Irgendwelche Meldungen in Proxmox unten in der Leiste? Normal taucht ja dann dort was auf, wenn es irgendwo zu einem Fehler kommt.

                    Gruss, Jürgen

                    crunchipC 1 Antwort Letzte Antwort
                    0
                    • crunchipC Abwesend
                      crunchipC Abwesend
                      crunchip
                      Forum Testing Most Active
                      schrieb am zuletzt editiert von
                      #67

                      @wildbill ja logisch kommt dann ne Meldung, Wortlaut hab ich allerdings nicht im Kopf. Hatte ja schon länger nimmer den Fall.
                      Wenn ich morgen dazu komme, werde ich mal paar Maschine testen

                      umgestiegen von Proxmox auf Unraid

                      1 Antwort Letzte Antwort
                      0
                      • W Wildbill

                        @crunchip Irgendwelche Meldungen in Proxmox unten in der Leiste? Normal taucht ja dann dort was auf, wenn es irgendwo zu einem Fehler kommt.

                        Gruss, Jürgen

                        crunchipC Abwesend
                        crunchipC Abwesend
                        crunchip
                        Forum Testing Most Active
                        schrieb am zuletzt editiert von
                        #68

                        @wildbill heute mal ne VM rebootet

                        TASK ERROR: VM quit/powerdown failed - got timeout
                        

                        umgestiegen von Proxmox auf Unraid

                        W 1 Antwort Letzte Antwort
                        0
                        • crunchipC crunchip

                          @wildbill heute mal ne VM rebootet

                          TASK ERROR: VM quit/powerdown failed - got timeout
                          
                          W Online
                          W Online
                          Wildbill
                          schrieb am zuletzt editiert von
                          #69

                          @crunchip sagte in Adapter werden neu gestartet:

                          TASK ERROR: VM quit/powerdown failed - got timeout

                          Ich nehme an, das war ein Reboot über die Proxmox-Konsole und nicht aus der VM heraus?
                          Die Meldung taucht wohl immer wieder mal auf bei Proxmox. Öfters anscheinend in Verbindung mit Debian innerhalb der VM (welches Betriebssystem läuft da bei Dir?). Zudem gab es kürzlich wohl einen Bug in Proxmox selbst, deshalb sollte die aktuellste Version installiert werden, entweder die aktuellste 6.4 oder gleich der 7er-Zweig. HIER steht das auch nochmal so. Aber auch keine wirkliche Lösung.
                          Gruss, Jürgen

                          crunchipC Meister MopperM 2 Antworten Letzte Antwort
                          0
                          • GlasfaserG Glasfaser

                            @matrose65 sagte in Adapter werden neu gestartet:

                            system.adapter.netatmo-crawler.0 terminated due to SIGSEGV]

                            Kannst du diesen Adapter längere Zeit mal ausschalten und das verhalten dann weiter beobachten !?

                            M Offline
                            M Offline
                            matrose65
                            schrieb am zuletzt editiert von Homoran
                            #70

                            @glasfaser

                            Guten Morgen

                            Nach dem seit dem Ausschalten am 04.01.22 17 Uhr keine Fehler mehr waren, war es heute wieder um 08.09 Uhr soweit.

                            Vorher waren keine Fehler zu sehen. Bis 07.53 Uhr waren nur Abfragen im Zeitplan. Um 07.58 Uhr hat meine Frau den Sonos gestartet. Das auch ohne Probleme.

                            Und um 08.09.07 ging es los. Beim letzten Eintrag habe ich meine VIS auf dem Tablet aufgerufen. Da war wieder alles in Ordnung
                            Komische Sache das.

                            2022-01-08 07:53:00.016 - info: host.iobroker instance system.adapter.dwd.0 started with pid 174216
                            2022-01-08 07:53:00.504 - info: dwd.0 (174216) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 07:53:00.986 - info: dwd.0 (174216) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2022-01-08 07:53:01.505 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2022-01-08 07:58:26.455 - info: sonos.0 (173891) try to control id sonos.0.root.192_168_178_31.play with {"val":true,"ack":false,"ts":1641625106453,"q":0,"from":"system.adapter.web.0","user":"system.user.admin","lc":1640019319143}
                            2022-01-08 08:09:07.855 - info: sonos.0 (173891) terminating
                            2022-01-08 08:09:07.855 - info: fullybrowser.0 (149136) cleaned everything up...
                            2022-01-08 08:09:07.860 - info: web.0 (149597) terminated http server on port 8082
                            2022-01-08 08:09:07.853 - info: admin.0 (173066) terminating http server on port 8081
                            2022-01-08 08:09:07.856 - info: netatmo.0 (148927) cleaned everything up...
                            2022-01-08 08:09:07.859 - info: info.0 (149166) cleaned everything up...
                            2022-01-08 08:09:07.858 - info: backitup.0 (149084) cleaned everything up...
                            2022-01-08 08:09:07.862 - info: hm-rpc.0 (148860) xmlrpc -> 192.168.178.93:2001/ init ["http://192.168.178.92:2001",""]
                            2022-01-08 08:09:07.855 - info: shelly.0 (148957) Closing Adapter
                            2022-01-08 08:09:07.893 - info: hm-rpc.0 (148860) Disconnected
                            2022-01-08 08:09:07.869 - info: javascript.0 (148782) Stop script script.js.Automaten.Küche-Tablet_Screen
                            2022-01-08 08:09:07.887 - info: javascript.0 (148782) Stop script script.js.Bad.Bad-Nachtlicht
                            2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Arbeitszimmer
                            2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle
                            2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Bad
                            2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Bad_Kontrolle
                            2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Esszimmer
                            2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Esszimmer_Kontrolle
                            2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Küche
                            2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Küche_Kontrolle
                            2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Wohnzimmer
                            2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Wohnzimmer_Kontrolle
                            2022-01-08 08:09:07.891 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe
                            2022-01-08 08:09:07.892 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer
                            2022-01-08 08:09:07.892 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe-Radio
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Wohnzimmer-Lampe
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Gruppenbildung
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Gruppenbildung2
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_Ess
                            2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_Küche
                            2022-01-08 08:09:07.894 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_WZ
                            2022-01-08 08:09:07.859 - info: zigbee.0 (149043) cleaned everything up...
                            2022-01-08 08:09:07.870 - info: zigbee.0 (149043) Zigbee: disabling joining new devices.
                            2022-01-08 08:09:09.355 - info: sonoff.0 (149151) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.358 - info: fullybrowser.0 (149136) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.359 - info: web.0 (149597) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.358 - info: tankerkoenig.0 (149582) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.368 - info: sonos.0 (173891) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.371 - info: zigbee.0 (149043) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.372 - info: javascript.0 (148782) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.374 - info: admin.0 (173066) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.365 - info: tr-064.0 (157163) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.363 - info: hm-rega.0 (148834) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.364 - info: scenes.0 (148808) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.378 - info: backitup.0 (149084) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.380 - info: netatmo.0 (148927) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.382 - info: info.0 (149166) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.384 - info: shelly.0 (148957) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:09.887 - info: hm-rpc.0 (148860) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2022-01-08 08:09:12.845 - error: tankerkoenig.0 (149582) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.853 - error: netatmo.0 (148927) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.850 - warn: hm-rpc.0 (148860) get state error: DB closed
                            2022-01-08 08:09:12.853 - error: fullybrowser.0 (149136) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.851 - error: web.0 (149597) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.853 - warn: web.0 (149597) get state error: Connection is closed.
                            2022-01-08 08:09:12.853 - warn: web.0 (149597) get state error: DB closed
                            2022-01-08 08:09:12.849 - error: info.0 (149166) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.854 - warn: hm-rpc.0 (148860) get state error: DB closed
                            2022-01-08 08:09:12.856 - error: hm-rega.0 (148834) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.863 - error: sonoff.0 (149151) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.856 - error: backitup.0 (149084) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.867 - error: tr-064.0 (157163) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.868 - error: shelly.0 (148957) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.871 - error: sonos.0 (173891) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.875 - warn: hm-rega.0 (148834) get state error: Connection is closed.
                            2022-01-08 08:09:12.882 - error: admin.0 (173066) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.884 - error: zigbee.0 (149043) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.885 - error: javascript.0 (148782) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.896 - error: scenes.0 (148808) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                            2022-01-08 08:09:12.893 - warn: javascript.0 (148782) get state error: DB closed
                            2022-01-08 08:09:12.894 - warn: javascript.0 (148782) get state error: DB closed
                            2022-01-08 08:09:18.384 - info: host.iobroker iobroker.js-controller version 3.3.22 js-controller starting
                            2022-01-08 08:09:18.386 - info: host.iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                            2022-01-08 08:09:18.387 - info: host.iobroker hostname: iobroker, node: v14.18.2
                            2022-01-08 08:09:18.387 - info: host.iobroker ip addresses: 192.168.178.92 2a01:5241:24a:1600:d400:abff:fe33:1f59 fe80::d400:abff:fe33:1f59
                            2022-01-08 08:09:18.391 - debug: host.iobroker-Server Data File: /opt/iobroker/iobroker-data/objects.json
                            2022-01-08 08:09:18.500 - debug: host.iobroker-Server Redis inMem-objects listening on port 9001
                            2022-01-08 08:09:18.501 - debug: host.iobroker Redis Objects: Use Redis connection: 127.0.0.1:9001
                            2022-01-08 08:09:18.510 - debug: host.iobroker Objects client ready ... initialize now
                            2022-01-08 08:09:18.511 - debug: host.iobroker Objects create System PubSub Client
                            2022-01-08 08:09:18.512 - debug: host.iobroker Objects client initialize lua scripts
                            2022-01-08 08:09:18.520 - debug: host.iobroker Objects connected to redis: 127.0.0.1:9001
                            2022-01-08 08:09:18.521 - debug: host.iobroker-Server Data File: /opt/iobroker/iobroker-data/states.json
                            2022-01-08 08:09:18.535 - debug: host.iobroker-Server Redis inMem-states listening on port 9000
                            2022-01-08 08:09:18.536 - debug: host.iobroker Redis States: Use Redis connection: 127.0.0.1:9000
                            2022-01-08 08:09:18.539 - debug: host.iobroker States create System PubSub Client
                            2022-01-08 08:09:18.552 - debug: host.iobroker States connected to redis: 127.0.0.1:9000
                            2022-01-08 08:09:18.576 - info: host.iobroker connected to Objects and States
                            2022-01-08 08:09:18.602 - info: host.iobroker added notifications configuration of host
                            2022-01-08 08:09:18.681 - debug: host.iobroker Plugin sentry Initialize Plugin (enabled=true)
                            2022-01-08 08:09:18.781 - info: host.iobroker 29 instances found
                            2022-01-08 08:09:18.781 - debug: host.iobroker check instance "system.adapter.admin.0" for host "iobroker"
                            2022-01-08 08:09:18.783 - debug: host.iobroker check instance "system.adapter.javascript.0" for host "iobroker"
                            2022-01-08 08:09:18.785 - debug: host.iobroker check instance "system.adapter.scenes.0" for host "iobroker"
                            2022-01-08 08:09:18.786 - debug: host.iobroker check instance "system.adapter.hm-rega.0" for host "iobroker"
                            2022-01-08 08:09:18.787 - debug: host.iobroker check instance "system.adapter.hm-rpc.0" for host "iobroker"
                            2022-01-08 08:09:18.788 - debug: host.iobroker check instance "system.adapter.ical.0" for host "iobroker"
                            2022-01-08 08:09:18.789 - debug: host.iobroker check instance "system.adapter.ical.2" for host "iobroker"
                            2022-01-08 08:09:18.790 - debug: host.iobroker check instance "system.adapter.ical.3" for host "iobroker"
                            2022-01-08 08:09:18.791 - debug: host.iobroker check instance "system.adapter.netatmo.0" for host "iobroker"
                            2022-01-08 08:09:18.791 - debug: host.iobroker check instance "system.adapter.shelly.0" for host "iobroker"
                            2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker"
                            2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.tr-064.0" for host "iobroker"
                            2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker"
                            2022-01-08 08:09:18.793 - debug: host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"
                            2022-01-08 08:09:18.794 - debug: host.iobroker check instance "system.adapter.daswetter.0" for host "iobroker"
                            2022-01-08 08:09:18.794 - debug: host.iobroker check instance "system.adapter.dwd.0" for host "iobroker"
                            2022-01-08 08:09:18.795 - debug: host.iobroker check instance "system.adapter.feiertage.0" for host "iobroker"
                            2022-01-08 08:09:18.795 - debug: host.iobroker check instance "system.adapter.fullybrowser.0" for host "iobroker"
                            2022-01-08 08:09:18.796 - debug: host.iobroker check instance "system.adapter.info.0" for host "iobroker"
                            2022-01-08 08:09:18.797 - debug: host.iobroker check instance "system.adapter.netatmo-crawler.0" for host "iobroker"
                            2022-01-08 08:09:18.797 - debug: host.iobroker check instance "system.adapter.sonos.0" for host "iobroker"
                            2022-01-08 08:09:18.798 - debug: host.iobroker check instance "system.adapter.tankerkoenig.0" for host "iobroker"
                            2022-01-08 08:09:18.799 - debug: host.iobroker check instance "system.adapter.vis-hqwidgets.0" for host "iobroker"
                            2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-metro.0" for host "iobroker"
                            2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-players.0" for host "iobroker"
                            2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-timeandweather.0" for host "iobroker"
                            2022-01-08 08:09:18.801 - debug: host.iobroker check instance "system.adapter.vis.0" for host "iobroker"
                            2022-01-08 08:09:18.801 - debug: host.iobroker check instance "system.adapter.web.0" for host "iobroker"
                            2022-01-08 08:09:18.802 - info: host.iobroker starting 23 instances
                            2022-01-08 08:09:18.833 - debug: host.iobroker added notifications configuration of system.adapter.admin.0
                            2022-01-08 08:09:18.833 - debug: host.iobroker startInstance admin.0 loglevel=info, compact=false
                            2022-01-08 08:09:18.842 - info: host.iobroker instance system.adapter.admin.0 started with pid 174256
                            2022-01-08 08:09:19.307 - error: admin.0 (174256) admin.0 already running
                            2022-01-08 08:09:19.308 - warn: admin.0 (174256) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:19.841 - error: host.iobroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:19.841 - debug: host.iobroker Reset crash count of system.adapter.admin.0, because non-crash exit
                            2022-01-08 08:09:19.841 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled
                            2022-01-08 08:09:22.828 - debug: host.iobroker added notifications configuration of system.adapter.javascript.0
                            2022-01-08 08:09:22.829 - debug: host.iobroker startInstance javascript.0 loglevel=info, compact=false
                            2022-01-08 08:09:22.835 - info: host.iobroker instance system.adapter.javascript.0 started with pid 174267
                            2022-01-08 08:09:23.516 - error: javascript.0 (174267) javascript.0 already running
                            2022-01-08 08:09:23.518 - warn: javascript.0 (174267) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:24.048 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:24.048 - debug: host.iobroker Reset crash count of system.adapter.javascript.0, because non-crash exit
                            2022-01-08 08:09:24.048 - info: host.iobroker Restart adapter system.adapter.javascript.0 because enabled
                            2022-01-08 08:09:26.832 - debug: host.iobroker added notifications configuration of system.adapter.scenes.0
                            2022-01-08 08:09:26.833 - debug: host.iobroker startInstance scenes.0 loglevel=info, compact=false
                            2022-01-08 08:09:26.841 - info: host.iobroker instance system.adapter.scenes.0 started with pid 174278
                            2022-01-08 08:09:27.169 - error: scenes.0 (174278) scenes.0 already running
                            2022-01-08 08:09:27.170 - warn: scenes.0 (174278) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:27.699 - error: host.iobroker instance system.adapter.scenes.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:27.699 - debug: host.iobroker Reset crash count of system.adapter.scenes.0, because non-crash exit
                            2022-01-08 08:09:27.699 - info: host.iobroker Restart adapter system.adapter.scenes.0 because enabled
                            2022-01-08 08:09:30.823 - debug: host.iobroker added notifications configuration of system.adapter.hm-rega.0
                            2022-01-08 08:09:30.823 - debug: host.iobroker startInstance hm-rega.0 loglevel=info, compact=false
                            2022-01-08 08:09:30.830 - info: host.iobroker instance system.adapter.hm-rega.0 started with pid 174290
                            2022-01-08 08:09:31.253 - error: hm-rega.0 (174290) hm-rega.0 already running
                            2022-01-08 08:09:31.254 - warn: hm-rega.0 (174290) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:31.783 - error: host.iobroker instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:31.783 - debug: host.iobroker Reset crash count of system.adapter.hm-rega.0, because non-crash exit
                            2022-01-08 08:09:31.783 - info: host.iobroker Restart adapter system.adapter.hm-rega.0 because enabled
                            2022-01-08 08:09:34.821 - debug: host.iobroker added notifications configuration of system.adapter.hm-rpc.0
                            2022-01-08 08:09:34.822 - debug: host.iobroker startInstance hm-rpc.0 loglevel=info, compact=false
                            2022-01-08 08:09:34.828 - info: host.iobroker instance system.adapter.hm-rpc.0 started with pid 174301
                            2022-01-08 08:09:35.162 - error: hm-rpc.0 (174301) hm-rpc.0 already running
                            2022-01-08 08:09:35.163 - warn: hm-rpc.0 (174301) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:35.696 - error: host.iobroker instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:35.696 - debug: host.iobroker Reset crash count of system.adapter.hm-rpc.0, because non-crash exit
                            2022-01-08 08:09:35.696 - info: host.iobroker Restart adapter system.adapter.hm-rpc.0 because enabled
                            2022-01-08 08:09:38.838 - debug: host.iobroker added notifications configuration of system.adapter.ical.0
                            2022-01-08 08:09:38.860 - info: host.iobroker instance scheduled system.adapter.ical.0 56 0,3,6,9,12,15,18,21 * * *
                            2022-01-08 08:09:38.864 - info: host.iobroker instance system.adapter.ical.0 started with pid 174312
                            2022-01-08 08:09:39.460 - info: ical.0 (174312) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:40.023 - info: ical.0 (174312) processing URL: Familie hier ist nix
                            2022-01-08 08:09:42.822 - debug: host.iobroker added notifications configuration of system.adapter.ical.2
                            2022-01-08 08:09:42.827 - info: host.iobroker instance scheduled system.adapter.ical.2 58 3 * * *
                            2022-01-08 08:09:42.831 - info: host.iobroker instance system.adapter.ical.2 started with pid 174327
                            2022-01-08 08:09:43.423 - info: ical.2 (174327) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:43.741 - info: ical.2 (174327) processing URL: Geburtstag auch das weg
                            2022-01-08 08:09:45.143 - info: ical.0 (174312) Terminated (NO_ERROR): Without reason
                            2022-01-08 08:09:45.670 - info: host.iobroker instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                            2022-01-08 08:09:46.821 - debug: host.iobroker added notifications configuration of system.adapter.ical.3
                            2022-01-08 08:09:46.827 - info: host.iobroker instance scheduled system.adapter.ical.3 57 3 * * *
                            2022-01-08 08:09:46.831 - info: host.iobroker instance system.adapter.ical.3 started with pid 174342
                            2022-01-08 08:09:47.411 - info: ical.3 (174342) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:48.245 - info: ical.3 (174342) processing URL: Arbeit nix mehr
                            2022-01-08 08:09:48.821 - info: ical.2 (174327) Terminated (NO_ERROR): Without reason
                            2022-01-08 08:09:49.349 - info: host.iobroker instance system.adapter.ical.2 terminated with code 0 (NO_ERROR)
                            2022-01-08 08:09:49.845 - debug: host.iobroker added notifications configuration of system.adapter.admin.0
                            2022-01-08 08:09:49.845 - debug: host.iobroker startInstance admin.0 loglevel=info, compact=false
                            2022-01-08 08:09:49.851 - info: host.iobroker instance system.adapter.admin.0 started with pid 174357
                            2022-01-08 08:09:50.345 - info: admin.0 (174357) Plugin sentry Sentry Plugin disabled for this process because data reporting is disabled on instance
                            2022-01-08 08:09:50.350 - info: admin.0 (174357) starting. Version 5.2.3 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:50.367 - info: admin.0 (174357) requesting all states
                            2022-01-08 08:09:50.367 - info: admin.0 (174357) requesting all objects
                            2022-01-08 08:09:50.694 - info: admin.0 (174357) received all objects
                            2022-01-08 08:09:50.804 - debug: host.iobroker added notifications configuration of system.adapter.netatmo.0
                            2022-01-08 08:09:50.814 - info: admin.0 (174357) http server listening on port 8081
                            2022-01-08 08:09:50.804 - debug: host.iobroker startInstance netatmo.0 loglevel=info, compact=false
                            2022-01-08 08:09:50.814 - info: host.iobroker instance system.adapter.netatmo.0 started with pid 174372
                            2022-01-08 08:09:50.814 - info: admin.0 (174357) Use link "http://localhost:8081" to configure.
                            2022-01-08 08:09:51.240 - error: netatmo.0 (174372) netatmo.0 already running
                            2022-01-08 08:09:51.240 - warn: netatmo.0 (174372) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:51.771 - error: host.iobroker instance system.adapter.netatmo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:51.771 - debug: host.iobroker Reset crash count of system.adapter.netatmo.0, because non-crash exit
                            2022-01-08 08:09:51.771 - info: host.iobroker Restart adapter system.adapter.netatmo.0 because enabled
                            2022-01-08 08:09:53.456 - info: ical.3 (174342) Terminated (NO_ERROR): Without reason
                            2022-01-08 08:09:53.979 - info: host.iobroker instance system.adapter.ical.3 terminated with code 0 (NO_ERROR)
                            2022-01-08 08:09:54.050 - debug: host.iobroker added notifications configuration of system.adapter.javascript.0
                            2022-01-08 08:09:54.050 - debug: host.iobroker startInstance javascript.0 loglevel=info, compact=false
                            2022-01-08 08:09:54.056 - info: host.iobroker instance system.adapter.javascript.0 started with pid 174383
                            2022-01-08 08:09:54.830 - debug: host.iobroker added notifications configuration of system.adapter.shelly.0
                            2022-01-08 08:09:54.831 - debug: host.iobroker startInstance shelly.0 loglevel=info, compact=false
                            2022-01-08 08:09:54.838 - info: host.iobroker instance system.adapter.shelly.0 started with pid 174394
                            2022-01-08 08:09:54.874 - info: javascript.0 (174383) starting. Version 5.2.18 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:54.915 - info: javascript.0 (174383) requesting all states
                            2022-01-08 08:09:54.916 - info: javascript.0 (174383) requesting all objects
                            2022-01-08 08:09:55.241 - info: javascript.0 (174383) received all objects
                            2022-01-08 08:09:55.316 - info: javascript.0 (174383) received all states
                            2022-01-08 08:09:55.343 - info: javascript.0 (174383) Start javascript script.js.Automaten.Küche-Tablet_Screen
                            2022-01-08 08:09:55.364 - info: javascript.0 (174383) script.js.Automaten.Küche-Tablet_Screen: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.364 - info: javascript.0 (174383) Start javascript script.js.Bad.Bad-Nachtlicht
                            2022-01-08 08:09:55.366 - info: javascript.0 (174383) script.js.Bad.Bad-Nachtlicht: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.367 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Arbeitszimmer
                            2022-01-08 08:09:55.369 - info: javascript.0 (174383) script.js.Heizung.Heizung_Arbeitszimmer: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.370 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle
                            2022-01-08 08:09:55.371 - info: javascript.0 (174383) script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.421 - error: shelly.0 (174394) shelly.0 already running
                            2022-01-08 08:09:55.423 - warn: shelly.0 (174394) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:55.373 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Bad
                            2022-01-08 08:09:55.376 - info: javascript.0 (174383) script.js.Heizung.Heizung_Bad: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.376 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Bad_Kontrolle
                            2022-01-08 08:09:55.379 - info: javascript.0 (174383) script.js.Heizung.Heizung_Bad_Kontrolle: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.379 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Esszimmer
                            2022-01-08 08:09:55.381 - info: javascript.0 (174383) script.js.Heizung.Heizung_Esszimmer: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.382 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Esszimmer_Kontrolle
                            2022-01-08 08:09:55.384 - info: javascript.0 (174383) script.js.Heizung.Heizung_Esszimmer_Kontrolle: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.384 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Küche
                            2022-01-08 08:09:55.387 - info: javascript.0 (174383) script.js.Heizung.Heizung_Küche: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.387 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Küche_Kontrolle
                            2022-01-08 08:09:55.389 - info: javascript.0 (174383) script.js.Heizung.Heizung_Küche_Kontrolle: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.390 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Wohnzimmer
                            2022-01-08 08:09:55.393 - info: javascript.0 (174383) script.js.Heizung.Heizung_Wohnzimmer: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.393 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Wohnzimmer_Kontrolle
                            2022-01-08 08:09:55.395 - info: javascript.0 (174383) script.js.Heizung.Heizung_Wohnzimmer_Kontrolle: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.396 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe
                            2022-01-08 08:09:55.398 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe: registered 2 subscriptions and 0 schedules
                            2022-01-08 08:09:55.399 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer
                            2022-01-08 08:09:55.401 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer: registered 3 subscriptions and 0 schedules
                            2022-01-08 08:09:55.401 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe-Radio
                            2022-01-08 08:09:55.403 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe-Radio: registered 2 subscriptions and 0 schedules
                            2022-01-08 08:09:55.433 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer
                            2022-01-08 08:09:55.435 - info: javascript.0 (174383) script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer: registered 3 subscriptions and 0 schedules
                            2022-01-08 08:09:55.435 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Wohnzimmer-Lampe
                            2022-01-08 08:09:55.436 - info: javascript.0 (174383) script.js.Ikea-Licht.Wohnzimmer-Lampe: registered 2 subscriptions and 0 schedules
                            2022-01-08 08:09:55.437 - info: javascript.0 (174383) Start javascript script.js.Sonos.Gruppenbildung
                            2022-01-08 08:09:55.438 - info: javascript.0 (174383) script.js.Sonos.Gruppenbildung: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.438 - info: javascript.0 (174383) Start javascript script.js.Sonos.Gruppenbildung2
                            2022-01-08 08:09:55.440 - info: javascript.0 (174383) script.js.Sonos.Gruppenbildung2: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.440 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_Ess
                            2022-01-08 08:09:55.442 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_Ess: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.442 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_Küche
                            2022-01-08 08:09:55.444 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_Küche: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.444 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_WZ
                            2022-01-08 08:09:55.446 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_WZ: registered 1 subscription and 0 schedules
                            2022-01-08 08:09:55.951 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:55.951 - debug: host.iobroker Reset crash count of system.adapter.shelly.0, because non-crash exit
                            2022-01-08 08:09:55.951 - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled
                            2022-01-08 08:09:57.701 - debug: host.iobroker added notifications configuration of system.adapter.scenes.0
                            2022-01-08 08:09:57.701 - debug: host.iobroker startInstance scenes.0 loglevel=info, compact=false
                            2022-01-08 08:09:57.708 - info: host.iobroker instance system.adapter.scenes.0 started with pid 174409
                            2022-01-08 08:09:58.157 - info: scenes.0 (174409) starting. Version 2.3.8 in /opt/iobroker/node_modules/iobroker.scenes, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:09:58.820 - debug: host.iobroker added notifications configuration of system.adapter.sonoff.0
                            2022-01-08 08:09:58.820 - debug: host.iobroker startInstance sonoff.0 loglevel=info, compact=false
                            2022-01-08 08:09:58.827 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 174424
                            2022-01-08 08:09:59.185 - error: sonoff.0 (174424) sonoff.0 already running
                            2022-01-08 08:09:59.186 - warn: sonoff.0 (174424) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:09:59.715 - error: host.iobroker instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:09:59.715 - debug: host.iobroker Reset crash count of system.adapter.sonoff.0, because non-crash exit
                            2022-01-08 08:09:59.715 - info: host.iobroker Restart adapter system.adapter.sonoff.0 because enabled
                            2022-01-08 08:10:01.786 - debug: host.iobroker added notifications configuration of system.adapter.hm-rega.0
                            2022-01-08 08:10:01.786 - debug: host.iobroker startInstance hm-rega.0 loglevel=info, compact=false
                            2022-01-08 08:10:01.793 - info: host.iobroker instance system.adapter.hm-rega.0 started with pid 174435
                            2022-01-08 08:10:02.371 - info: hm-rega.0 (174435) starting. Version 3.0.33 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:02.419 - info: hm-rega.0 (174435) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
                            2022-01-08 08:10:02.436 - info: hm-rega.0 (174435) ReGaHSS 192.168.178.93 up
                            2022-01-08 08:10:02.503 - info: hm-rega.0 (174435) time difference local-ccu 1s
                            2022-01-08 08:10:02.754 - info: hm-rega.0 (174435) request state values
                            2022-01-08 08:10:02.820 - debug: host.iobroker added notifications configuration of system.adapter.tr-064.0
                            2022-01-08 08:10:02.820 - debug: host.iobroker startInstance tr-064.0 loglevel=info, compact=false
                            2022-01-08 08:10:02.828 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 174450
                            2022-01-08 08:10:02.975 - info: hm-rega.0 (174435) Updated all datapoints
                            2022-01-08 08:10:02.979 - info: hm-rega.0 (174435) got 5 variables
                            2022-01-08 08:10:03.015 - info: hm-rega.0 (174435) added/updated 5 variables
                            2022-01-08 08:10:03.015 - info: hm-rega.0 (174435) deleted 0 variables
                            2022-01-08 08:10:03.022 - info: hm-rega.0 (174435) got 0 programs
                            2022-01-08 08:10:03.025 - info: hm-rega.0 (174435) update rooms to enum.rooms
                            2022-01-08 08:10:03.029 - info: hm-rega.0 (174435) added/updated 0 programs
                            2022-01-08 08:10:03.030 - info: hm-rega.0 (174435) deleted 0 programs
                            2022-01-08 08:10:03.078 - info: hm-rega.0 (174435) update functions to enum.functions
                            2022-01-08 08:10:03.093 - info: hm-rega.0 (174435) update favorites to enum.favorites
                            2022-01-08 08:10:03.094 - error: hm-rega.0 (174435) Could not synchronize favorites of user "": Error: The id "enum.favorites." is invalid. Ids are not allowed to end in "."
                            2022-01-08 08:10:03.317 - error: tr-064.0 (174450) tr-064.0 already running
                            2022-01-08 08:10:03.318 - warn: tr-064.0 (174450) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:03.846 - error: host.iobroker instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:03.846 - debug: host.iobroker Reset crash count of system.adapter.tr-064.0, because non-crash exit
                            2022-01-08 08:10:03.846 - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled
                            2022-01-08 08:10:05.698 - debug: host.iobroker added notifications configuration of system.adapter.hm-rpc.0
                            2022-01-08 08:10:05.698 - debug: host.iobroker startInstance hm-rpc.0 loglevel=info, compact=false
                            2022-01-08 08:10:05.705 - info: host.iobroker instance system.adapter.hm-rpc.0 started with pid 174461
                            2022-01-08 08:10:06.190 - info: hm-rpc.0 (174461) starting. Version 1.15.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:06.236 - info: hm-rpc.0 (174461) xmlrpc server is trying to listen on 192.168.178.92:2001
                            2022-01-08 08:10:06.237 - info: hm-rpc.0 (174461) xmlrpc client is trying to connect to 192.168.178.93:2001/ with ["http://192.168.178.92:2001","iobroker:hm-rpc.0"]
                            2022-01-08 08:10:06.247 - info: hm-rpc.0 (174461) xmlrpc <- system.listMethods ["iobroker:hm-rpc.0"]
                            2022-01-08 08:10:06.250 - info: hm-rpc.0 (174461) xmlrpc <- listDevices ["iobroker:hm-rpc.0"]
                            2022-01-08 08:10:06.264 - info: hm-rpc.0 (174461) xmlrpc -> 92 devices
                            2022-01-08 08:10:06.272 - info: hm-rpc.0 (174461) Connected
                            2022-01-08 08:10:06.804 - debug: host.iobroker added notifications configuration of system.adapter.zigbee.0
                            2022-01-08 08:10:06.804 - debug: host.iobroker startInstance zigbee.0 loglevel=info, compact=false
                            2022-01-08 08:10:06.811 - info: host.iobroker instance system.adapter.zigbee.0 started with pid 174476
                            2022-01-08 08:10:07.595 - error: zigbee.0 (174476) zigbee.0 already running
                            2022-01-08 08:10:07.596 - warn: zigbee.0 (174476) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:08.123 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:08.123 - debug: host.iobroker Reset crash count of system.adapter.zigbee.0, because non-crash exit
                            2022-01-08 08:10:08.123 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled
                            2022-01-08 08:10:10.805 - debug: host.iobroker added notifications configuration of system.adapter.backitup.0
                            2022-01-08 08:10:10.805 - debug: host.iobroker startInstance backitup.0 loglevel=info, compact=false
                            2022-01-08 08:10:10.811 - info: host.iobroker instance system.adapter.backitup.0 started with pid 174487
                            2022-01-08 08:10:11.160 - error: backitup.0 (174487) backitup.0 already running
                            2022-01-08 08:10:11.161 - warn: backitup.0 (174487) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:11.692 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:11.692 - debug: host.iobroker Reset crash count of system.adapter.backitup.0, because non-crash exit
                            2022-01-08 08:10:11.692 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled
                            2022-01-08 08:10:14.805 - debug: host.iobroker added notifications configuration of system.adapter.daswetter.0
                            2022-01-08 08:10:14.815 - info: host.iobroker instance scheduled system.adapter.daswetter.0 55 0,3,6,9,12,15,18,21 * * *
                            2022-01-08 08:10:14.819 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 174498
                            2022-01-08 08:10:15.291 - info: daswetter.0 (174498) starting. Version 3.0.9 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:17.567 - info: daswetter.0 (174498) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                            2022-01-08 08:10:18.074 - info: daswetter.0 (174498) cleaned everything up...
                            2022-01-08 08:10:18.095 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2022-01-08 08:10:18.819 - debug: host.iobroker added notifications configuration of system.adapter.dwd.0
                            2022-01-08 08:10:18.822 - info: host.iobroker instance scheduled system.adapter.dwd.0 53 * * * *
                            2022-01-08 08:10:18.827 - info: host.iobroker instance system.adapter.dwd.0 started with pid 174513
                            2022-01-08 08:10:19.332 - info: dwd.0 (174513) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:19.844 - info: dwd.0 (174513) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2022-01-08 08:10:20.367 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2022-01-08 08:10:21.773 - debug: host.iobroker added notifications configuration of system.adapter.netatmo.0
                            2022-01-08 08:10:21.773 - debug: host.iobroker startInstance netatmo.0 loglevel=info, compact=false
                            2022-01-08 08:10:21.780 - info: host.iobroker instance system.adapter.netatmo.0 started with pid 174528
                            2022-01-08 08:10:22.246 - info: netatmo.0 (174528) starting. Version 1.4.4 in /opt/iobroker/node_modules/iobroker.netatmo, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:22.805 - debug: host.iobroker added notifications configuration of system.adapter.feiertage.0
                            2022-01-08 08:10:22.810 - info: host.iobroker instance scheduled system.adapter.feiertage.0 36 3 * * *
                            2022-01-08 08:10:22.814 - info: host.iobroker instance system.adapter.feiertage.0 started with pid 174543
                            2022-01-08 08:10:23.264 - info: feiertage.0 (174543) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.feiertage, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:23.397 - info: feiertage.0 (174543) Next holiday: Rosenmontag is in 51 days on 28.02.2022
                            2022-01-08 08:10:23.403 - info: feiertage.0 (174543) adapter feiertage objects written
                            2022-01-08 08:10:23.906 - info: feiertage.0 (174543) Terminated (NO_ERROR): Without reason
                            2022-01-08 08:10:24.432 - info: host.iobroker instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
                            2022-01-08 08:10:25.954 - debug: host.iobroker added notifications configuration of system.adapter.shelly.0
                            2022-01-08 08:10:25.954 - debug: host.iobroker startInstance shelly.0 loglevel=info, compact=false
                            2022-01-08 08:10:25.960 - info: host.iobroker instance system.adapter.shelly.0 started with pid 174558
                            2022-01-08 08:10:26.625 - info: shelly.0 (174558) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:26.637 - info: shelly.0 (174558) Starting Adapter shelly.0 in version 5.0.0
                            2022-01-08 08:10:26.712 - info: shelly.0 (174558) Starting in CoAP mode.
                            2022-01-08 08:10:26.733 - info: shelly.0 (174558) Listening for Shelly packets in the network
                            2022-01-08 08:10:26.821 - debug: host.iobroker added notifications configuration of system.adapter.fullybrowser.0
                            2022-01-08 08:10:26.821 - debug: host.iobroker startInstance fullybrowser.0 loglevel=info, compact=false
                            2022-01-08 08:10:26.827 - info: host.iobroker instance system.adapter.fullybrowser.0 started with pid 174573
                            2022-01-08 08:10:27.156 - error: fullybrowser.0 (174573) fullybrowser.0 already running
                            2022-01-08 08:10:27.157 - warn: fullybrowser.0 (174573) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:27.685 - error: host.iobroker instance system.adapter.fullybrowser.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:27.686 - debug: host.iobroker Reset crash count of system.adapter.fullybrowser.0, because non-crash exit
                            2022-01-08 08:10:27.686 - info: host.iobroker Restart adapter system.adapter.fullybrowser.0 because enabled
                            2022-01-08 08:10:29.307 - info: shelly.0 (174558) Shelly device 192.168.178.54 (shellydimmer / shellydimmer-CC50E3F3AB05 / SHDM-1#CC50E3F3AB05#1) with CoAP connected! Polltime set to 5 sec.
                            2022-01-08 08:10:29.716 - debug: host.iobroker added notifications configuration of system.adapter.sonoff.0
                            2022-01-08 08:10:29.716 - debug: host.iobroker startInstance sonoff.0 loglevel=info, compact=false
                            2022-01-08 08:10:29.723 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 174584
                            2022-01-08 08:10:30.211 - info: sonoff.0 (174584) starting. Version 2.4.7 in /opt/iobroker/node_modules/iobroker.sonoff, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:30.234 - info: sonoff.0 (174584) Starting MQTT server on port 1883
                            2022-01-08 08:10:30.501 - info: sonoff.0 (174584) Client [Küche-Tisch] connected with secret 1641625830498_9529
                            2022-01-08 08:10:30.717 - info: sonoff.0 (174584) Client [Bad2-Wanne] connected with secret 1641625830716_4062
                            2022-01-08 08:10:30.729 - info: sonoff.0 (174584) Client [Kueche-Herd] connected with secret 1641625830729_1300
                            2022-01-08 08:10:30.820 - debug: host.iobroker added notifications configuration of system.adapter.info.0
                            2022-01-08 08:10:30.820 - debug: host.iobroker startInstance info.0 loglevel=info, compact=false
                            2022-01-08 08:10:30.826 - info: host.iobroker instance system.adapter.info.0 started with pid 174599
                            2022-01-08 08:10:31.344 - error: info.0 (174599) info.0 already running
                            2022-01-08 08:10:31.345 - warn: info.0 (174599) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:31.878 - error: host.iobroker instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:31.878 - debug: host.iobroker Reset crash count of system.adapter.info.0, because non-crash exit
                            2022-01-08 08:10:31.878 - info: host.iobroker Restart adapter system.adapter.info.0 because enabled
                            2022-01-08 08:10:32.565 - info: shelly.0 (174558) Shelly device 192.168.178.53 (shellyplug-s / shellyplug-s-79F6A9 / SHPLG-S#79F6A9#1) with CoAP connected! Polltime set to 5 sec.
                            2022-01-08 08:10:33.848 - debug: host.iobroker added notifications configuration of system.adapter.tr-064.0
                            2022-01-08 08:10:33.848 - debug: host.iobroker startInstance tr-064.0 loglevel=info, compact=false
                            2022-01-08 08:10:33.855 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 174618
                            2022-01-08 08:10:34.518 - info: tr-064.0 (174618) starting. Version 4.2.15 in /opt/iobroker/node_modules/iobroker.tr-064, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:34.818 - debug: host.iobroker added notifications configuration of system.adapter.sonos.0
                            2022-01-08 08:10:34.818 - debug: host.iobroker startInstance sonos.0 loglevel=info, compact=false
                            2022-01-08 08:10:34.828 - info: host.iobroker instance system.adapter.sonos.0 started with pid 174633
                            2022-01-08 08:10:35.226 - error: sonos.0 (174633) sonos.0 already running
                            2022-01-08 08:10:35.227 - warn: sonos.0 (174633) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:35.758 - error: host.iobroker instance system.adapter.sonos.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:35.758 - debug: host.iobroker Reset crash count of system.adapter.sonos.0, because non-crash exit
                            2022-01-08 08:10:35.758 - info: host.iobroker Restart adapter system.adapter.sonos.0 because enabled
                            2022-01-08 08:10:36.118 - info: shelly.0 (174558) Shelly device 192.168.178.55 (shellycolorbulb / shellycolorbulb-E8DB84AA2596 / SHCB-1#E8DB84AA2596#1) with CoAP connected! Polltime set to 5 sec.
                            2022-01-08 08:10:36.760 - debug: host.iobroker added notifications configuration of system.adapter.sonos.0
                            2022-01-08 08:10:36.760 - debug: host.iobroker startInstance sonos.0 loglevel=info, compact=false
                            2022-01-08 08:10:36.768 - info: host.iobroker instance system.adapter.sonos.0 started with pid 174644
                            2022-01-08 08:10:37.180 - info: sonos.0 (174644) starting. Version 2.1.7 in /opt/iobroker/node_modules/iobroker.sonos, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:38.125 - debug: host.iobroker added notifications configuration of system.adapter.zigbee.0
                            2022-01-08 08:10:38.126 - debug: host.iobroker startInstance zigbee.0 loglevel=info, compact=false
                            2022-01-08 08:10:38.132 - info: host.iobroker instance system.adapter.zigbee.0 started with pid 174659
                            2022-01-08 08:10:38.805 - debug: host.iobroker added notifications configuration of system.adapter.tankerkoenig.0
                            2022-01-08 08:10:38.805 - debug: host.iobroker startInstance tankerkoenig.0 loglevel=info, compact=false
                            2022-01-08 08:10:38.812 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 174670
                            2022-01-08 08:10:39.079 - info: zigbee.0 (174659) starting. Version 1.6.8 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:39.116 - info: zigbee.0 (174659) Starting Zigbee npm ...
                            2022-01-08 08:10:39.254 - info: zigbee.0 (174659) Installed Version: iobroker.zigbee@1.6.8
                            2022-01-08 08:10:39.304 - error: tankerkoenig.0 (174670) tankerkoenig.0 already running
                            2022-01-08 08:10:39.304 - warn: tankerkoenig.0 (174670) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:39.837 - error: host.iobroker instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:39.837 - debug: host.iobroker Reset crash count of system.adapter.tankerkoenig.0, because non-crash exit
                            2022-01-08 08:10:39.837 - info: host.iobroker Restart adapter system.adapter.tankerkoenig.0 because enabled
                            2022-01-08 08:10:40.755 - info: shelly.0 (174558) Shelly device 192.168.178.52 (shelly1 / shelly1-10DCB4 / SHSW-1#10DCB4#1) with CoAP connected! Polltime set to 5 sec.
                            2022-01-08 08:10:40.766 - info: shelly.0 (174558) Shelly device 192.168.178.51 (shelly1 / shelly1-767A0F / SHSW-1#767A0F#1) with CoAP connected! Polltime set to 5 sec.
                            2022-01-08 08:10:41.013 - info: zigbee.0 (174659) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}}
                            2022-01-08 08:10:41.022 - info: zigbee.0 (174659) Unable to disable LED, unsupported function.
                            2022-01-08 08:10:41.024 - info: zigbee.0 (174659) --> transmitPower : normal
                            2022-01-08 08:10:41.046 - info: zigbee.0 (174659) Currently 17 devices are joined:
                            2022-01-08 08:10:41.063 - info: zigbee.0 (174659) 0x086bd7fffe51dbd6 (addr 64726): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
                            2022-01-08 08:10:41.064 - info: zigbee.0 (174659) 0x00158d0003faf01b (addr 62232): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                            2022-01-08 08:10:41.065 - info: zigbee.0 (174659) 0x00158d000358c678 (addr 5513): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.065 - info: zigbee.0 (174659) 0x14b457fffe732925 (addr 9173): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
                            2022-01-08 08:10:41.066 - info: zigbee.0 (174659) 0x842e14fffea1801a (addr 13524): LED1624G9 - IKEA TRADFRI LED bulb E14/E26/E27 600 lumen, dimmable, color, opal white (Router)
                            2022-01-08 08:10:41.066 - info: zigbee.0 (174659) 0x00158d000358c57a (addr 24218): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.067 - info: zigbee.0 (174659) 0x00158d00045140d3 (addr 24472): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.067 - info: zigbee.0 (174659) 0x00158d00045d46cc (addr 30298): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0x00158d00045c5d25 (addr 44319): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0xbc33acfffe158f61 (addr 45674): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
                            2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0x00158d00042d17a0 (addr 42890): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                            2022-01-08 08:10:41.069 - info: zigbee.0 (174659) 0x00158d0006f6ba34 (addr 22622): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                            2022-01-08 08:10:41.069 - info: zigbee.0 (174659) 0x5c0272fffe2c4ca3 (addr 30163): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                            2022-01-08 08:10:41.070 - info: zigbee.0 (174659) 0x60a423fffe116b9c (addr 42734): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                            2022-01-08 08:10:41.071 - info: zigbee.0 (174659) 0x60a423fffe03ce72 (addr 31923): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                            2022-01-08 08:10:41.071 - info: zigbee.0 (174659) 0xbc33acfffe47e5ef (addr 19590): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                            2022-01-08 08:10:41.072 - info: zigbee.0 (174659) 0x5c0272fffe28904b (addr 63315): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                            2022-01-08 08:10:41.072 - info: zigbee.0 (174659) Zigbee started
                            2022-01-08 08:10:41.177 - info: sonoff.0 (174584) Client [Bad1-Spiegel] connected with secret 1641625841176_4680
                            2022-01-08 08:10:41.694 - debug: host.iobroker added notifications configuration of system.adapter.backitup.0
                            2022-01-08 08:10:41.694 - debug: host.iobroker startInstance backitup.0 loglevel=info, compact=false
                            2022-01-08 08:10:41.701 - info: host.iobroker instance system.adapter.backitup.0 started with pid 174685
                            2022-01-08 08:10:42.239 - info: backitup.0 (174685) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:42.259 - info: backitup.0 (174685) [iobroker] backup was activated at 03:30 every 1 day(s)
                            2022-01-08 08:10:42.283 - info: backitup.0 (174685) [ccu] backup was activated at 01:30 every 1 day(s)
                            2022-01-08 08:10:42.820 - debug: host.iobroker added notifications configuration of system.adapter.vis.0
                            2022-01-08 08:10:42.820 - debug: host.iobroker startInstance vis.0 loglevel=info, compact=false
                            2022-01-08 08:10:43.229 - info: vis.0 (174700) starting. Version 1.4.7 in /opt/iobroker/node_modules/iobroker.vis, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:43.507 - info: vis.0 (174700) vis license is OK.
                            2022-01-08 08:10:44.121 - info: vis.0 (174700) Terminated (NO_ERROR): Without reason
                            2022-01-08 08:10:44.650 - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once
                            2022-01-08 08:10:46.816 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                            2022-01-08 08:10:46.817 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                            2022-01-08 08:10:46.823 - info: host.iobroker instance system.adapter.web.0 started with pid 174715
                            2022-01-08 08:10:47.192 - error: web.0 (174715) web.0 already running
                            2022-01-08 08:10:47.193 - warn: web.0 (174715) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                            2022-01-08 08:10:47.720 - error: host.iobroker instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                            2022-01-08 08:10:47.721 - debug: host.iobroker Reset crash count of system.adapter.web.0, because non-crash exit
                            2022-01-08 08:10:47.721 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled
                            2022-01-08 08:10:57.289 - info: sonoff.0 (174584) Client [Bad-Nachtlicht] connected with secret 1641625857288_2465
                            2022-01-08 08:10:57.687 - debug: host.iobroker added notifications configuration of system.adapter.fullybrowser.0
                            2022-01-08 08:10:57.688 - debug: host.iobroker startInstance fullybrowser.0 loglevel=info, compact=false
                            2022-01-08 08:10:57.694 - info: host.iobroker instance system.adapter.fullybrowser.0 started with pid 174726
                            2022-01-08 08:10:58.077 - info: fullybrowser.0 (174726) starting. Version 2.0.12 in /opt/iobroker/node_modules/iobroker.fullybrowser, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:10:58.088 - info: fullybrowser.0 (174726) Start with IP : 192.168.178.44
                            2022-01-08 08:11:01.881 - debug: host.iobroker added notifications configuration of system.adapter.info.0
                            2022-01-08 08:11:01.881 - debug: host.iobroker startInstance info.0 loglevel=info, compact=false
                            2022-01-08 08:11:01.888 - info: host.iobroker instance system.adapter.info.0 started with pid 174741
                            2022-01-08 08:11:02.792 - info: info.0 (174741) starting. Version 1.9.16 in /opt/iobroker/node_modules/iobroker.info, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:11:02.828 - info: info.0 (174741) Reading/updating systemdata.
                            2022-01-08 08:11:03.251 - info: info.0 (174741) cpu Temp res = {"main":null,"cores":[],"max":null,"socket":[],"chipset":null}
                            2022-01-08 08:11:09.839 - debug: host.iobroker added notifications configuration of system.adapter.tankerkoenig.0
                            2022-01-08 08:11:09.840 - debug: host.iobroker startInstance tankerkoenig.0 loglevel=info, compact=false
                            2022-01-08 08:11:09.847 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 175145
                            2022-01-08 08:11:10.754 - info: tankerkoenig.0 (175145) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:11:10.764 - info: tankerkoenig.0 (175145) Sync time set to 12 minutes or 720000 ms
                            2022-01-08 08:11:17.724 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                            2022-01-08 08:11:17.726 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                            2022-01-08 08:11:17.737 - info: host.iobroker instance system.adapter.web.0 started with pid 175160
                            2022-01-08 08:11:18.261 - info: web.0 (175160) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:11:18.367 - debug: host.iobroker-Server States 127.0.0.1:38890 Redis Socket error: Error: read ECONNRESET
                            2022-01-08 08:11:18.389 - warn: host.iobroker instance system.adapter.web.0 terminated due to SIGSEGV
                            2022-01-08 08:11:18.389 - info: host.iobroker instance system.adapter.web.0 terminated with code NaN ()
                            2022-01-08 08:11:18.390 - debug: host.iobroker Reset crash count of system.adapter.web.0, because non-crash exit
                            2022-01-08 08:11:18.390 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled
                            2022-01-08 08:11:48.392 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                            2022-01-08 08:11:48.392 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                            2022-01-08 08:11:48.398 - info: host.iobroker instance system.adapter.web.0 started with pid 175175
                            2022-01-08 08:11:48.905 - info: web.0 (175175) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.18.2, js-controller: 3.3.22
                            2022-01-08 08:11:49.028 - info: web.0 (175175) socket.io server listening on port 8082
                            2022-01-08 08:11:49.030 - info: web.0 (175175) simpleAPI server listening on port 8082
                            2022-01-08 08:11:49.030 - info: web.0 (175175) Allow states only when user is owner: false
                            2022-01-08 08:11:49.033 - info: web.0 (175175) http server listening on port 8082
                            2022-01-08 08:12:07.264 - info: web.0 (175175) ==>Connected system.user.admin from 192.168.178.44code_text
                            
                            GlasfaserG 1 Antwort Letzte Antwort
                            0
                            • M matrose65

                              @glasfaser

                              Guten Morgen

                              Nach dem seit dem Ausschalten am 04.01.22 17 Uhr keine Fehler mehr waren, war es heute wieder um 08.09 Uhr soweit.

                              Vorher waren keine Fehler zu sehen. Bis 07.53 Uhr waren nur Abfragen im Zeitplan. Um 07.58 Uhr hat meine Frau den Sonos gestartet. Das auch ohne Probleme.

                              Und um 08.09.07 ging es los. Beim letzten Eintrag habe ich meine VIS auf dem Tablet aufgerufen. Da war wieder alles in Ordnung
                              Komische Sache das.

                              2022-01-08 07:53:00.016 - info: host.iobroker instance system.adapter.dwd.0 started with pid 174216
                              2022-01-08 07:53:00.504 - info: dwd.0 (174216) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 07:53:00.986 - info: dwd.0 (174216) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2022-01-08 07:53:01.505 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2022-01-08 07:58:26.455 - info: sonos.0 (173891) try to control id sonos.0.root.192_168_178_31.play with {"val":true,"ack":false,"ts":1641625106453,"q":0,"from":"system.adapter.web.0","user":"system.user.admin","lc":1640019319143}
                              2022-01-08 08:09:07.855 - info: sonos.0 (173891) terminating
                              2022-01-08 08:09:07.855 - info: fullybrowser.0 (149136) cleaned everything up...
                              2022-01-08 08:09:07.860 - info: web.0 (149597) terminated http server on port 8082
                              2022-01-08 08:09:07.853 - info: admin.0 (173066) terminating http server on port 8081
                              2022-01-08 08:09:07.856 - info: netatmo.0 (148927) cleaned everything up...
                              2022-01-08 08:09:07.859 - info: info.0 (149166) cleaned everything up...
                              2022-01-08 08:09:07.858 - info: backitup.0 (149084) cleaned everything up...
                              2022-01-08 08:09:07.862 - info: hm-rpc.0 (148860) xmlrpc -> 192.168.178.93:2001/ init ["http://192.168.178.92:2001",""]
                              2022-01-08 08:09:07.855 - info: shelly.0 (148957) Closing Adapter
                              2022-01-08 08:09:07.893 - info: hm-rpc.0 (148860) Disconnected
                              2022-01-08 08:09:07.869 - info: javascript.0 (148782) Stop script script.js.Automaten.Küche-Tablet_Screen
                              2022-01-08 08:09:07.887 - info: javascript.0 (148782) Stop script script.js.Bad.Bad-Nachtlicht
                              2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Arbeitszimmer
                              2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle
                              2022-01-08 08:09:07.888 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Bad
                              2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Bad_Kontrolle
                              2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Esszimmer
                              2022-01-08 08:09:07.889 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Esszimmer_Kontrolle
                              2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Küche
                              2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Küche_Kontrolle
                              2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Wohnzimmer
                              2022-01-08 08:09:07.890 - info: javascript.0 (148782) Stop script script.js.Heizung.Heizung_Wohnzimmer_Kontrolle
                              2022-01-08 08:09:07.891 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe
                              2022-01-08 08:09:07.892 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer
                              2022-01-08 08:09:07.892 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Esszimmer-Lampe-Radio
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Ikea-Licht.Wohnzimmer-Lampe
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Gruppenbildung
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Gruppenbildung2
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_Ess
                              2022-01-08 08:09:07.893 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_Küche
                              2022-01-08 08:09:07.894 - info: javascript.0 (148782) Stop script script.js.Sonos.Sonos_Favoriten_WZ
                              2022-01-08 08:09:07.859 - info: zigbee.0 (149043) cleaned everything up...
                              2022-01-08 08:09:07.870 - info: zigbee.0 (149043) Zigbee: disabling joining new devices.
                              2022-01-08 08:09:09.355 - info: sonoff.0 (149151) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.358 - info: fullybrowser.0 (149136) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.359 - info: web.0 (149597) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.358 - info: tankerkoenig.0 (149582) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.368 - info: sonos.0 (173891) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.371 - info: zigbee.0 (149043) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.372 - info: javascript.0 (148782) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.374 - info: admin.0 (173066) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.365 - info: tr-064.0 (157163) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.363 - info: hm-rega.0 (148834) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.364 - info: scenes.0 (148808) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.378 - info: backitup.0 (149084) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.380 - info: netatmo.0 (148927) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.382 - info: info.0 (149166) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.384 - info: shelly.0 (148957) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:09.887 - info: hm-rpc.0 (148860) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2022-01-08 08:09:12.845 - error: tankerkoenig.0 (149582) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.853 - error: netatmo.0 (148927) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.850 - warn: hm-rpc.0 (148860) get state error: DB closed
                              2022-01-08 08:09:12.853 - error: fullybrowser.0 (149136) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.851 - error: web.0 (149597) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.853 - warn: web.0 (149597) get state error: Connection is closed.
                              2022-01-08 08:09:12.853 - warn: web.0 (149597) get state error: DB closed
                              2022-01-08 08:09:12.849 - error: info.0 (149166) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.854 - warn: hm-rpc.0 (148860) get state error: DB closed
                              2022-01-08 08:09:12.856 - error: hm-rega.0 (148834) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.863 - error: sonoff.0 (149151) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.856 - error: backitup.0 (149084) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.867 - error: tr-064.0 (157163) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.868 - error: shelly.0 (148957) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.871 - error: sonos.0 (173891) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.875 - warn: hm-rega.0 (148834) get state error: Connection is closed.
                              2022-01-08 08:09:12.882 - error: admin.0 (173066) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.884 - error: zigbee.0 (149043) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.885 - error: javascript.0 (148782) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.896 - error: scenes.0 (148808) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                              2022-01-08 08:09:12.893 - warn: javascript.0 (148782) get state error: DB closed
                              2022-01-08 08:09:12.894 - warn: javascript.0 (148782) get state error: DB closed
                              2022-01-08 08:09:18.384 - info: host.iobroker iobroker.js-controller version 3.3.22 js-controller starting
                              2022-01-08 08:09:18.386 - info: host.iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2022-01-08 08:09:18.387 - info: host.iobroker hostname: iobroker, node: v14.18.2
                              2022-01-08 08:09:18.387 - info: host.iobroker ip addresses: 192.168.178.92 2a01:5241:24a:1600:d400:abff:fe33:1f59 fe80::d400:abff:fe33:1f59
                              2022-01-08 08:09:18.391 - debug: host.iobroker-Server Data File: /opt/iobroker/iobroker-data/objects.json
                              2022-01-08 08:09:18.500 - debug: host.iobroker-Server Redis inMem-objects listening on port 9001
                              2022-01-08 08:09:18.501 - debug: host.iobroker Redis Objects: Use Redis connection: 127.0.0.1:9001
                              2022-01-08 08:09:18.510 - debug: host.iobroker Objects client ready ... initialize now
                              2022-01-08 08:09:18.511 - debug: host.iobroker Objects create System PubSub Client
                              2022-01-08 08:09:18.512 - debug: host.iobroker Objects client initialize lua scripts
                              2022-01-08 08:09:18.520 - debug: host.iobroker Objects connected to redis: 127.0.0.1:9001
                              2022-01-08 08:09:18.521 - debug: host.iobroker-Server Data File: /opt/iobroker/iobroker-data/states.json
                              2022-01-08 08:09:18.535 - debug: host.iobroker-Server Redis inMem-states listening on port 9000
                              2022-01-08 08:09:18.536 - debug: host.iobroker Redis States: Use Redis connection: 127.0.0.1:9000
                              2022-01-08 08:09:18.539 - debug: host.iobroker States create System PubSub Client
                              2022-01-08 08:09:18.552 - debug: host.iobroker States connected to redis: 127.0.0.1:9000
                              2022-01-08 08:09:18.576 - info: host.iobroker connected to Objects and States
                              2022-01-08 08:09:18.602 - info: host.iobroker added notifications configuration of host
                              2022-01-08 08:09:18.681 - debug: host.iobroker Plugin sentry Initialize Plugin (enabled=true)
                              2022-01-08 08:09:18.781 - info: host.iobroker 29 instances found
                              2022-01-08 08:09:18.781 - debug: host.iobroker check instance "system.adapter.admin.0" for host "iobroker"
                              2022-01-08 08:09:18.783 - debug: host.iobroker check instance "system.adapter.javascript.0" for host "iobroker"
                              2022-01-08 08:09:18.785 - debug: host.iobroker check instance "system.adapter.scenes.0" for host "iobroker"
                              2022-01-08 08:09:18.786 - debug: host.iobroker check instance "system.adapter.hm-rega.0" for host "iobroker"
                              2022-01-08 08:09:18.787 - debug: host.iobroker check instance "system.adapter.hm-rpc.0" for host "iobroker"
                              2022-01-08 08:09:18.788 - debug: host.iobroker check instance "system.adapter.ical.0" for host "iobroker"
                              2022-01-08 08:09:18.789 - debug: host.iobroker check instance "system.adapter.ical.2" for host "iobroker"
                              2022-01-08 08:09:18.790 - debug: host.iobroker check instance "system.adapter.ical.3" for host "iobroker"
                              2022-01-08 08:09:18.791 - debug: host.iobroker check instance "system.adapter.netatmo.0" for host "iobroker"
                              2022-01-08 08:09:18.791 - debug: host.iobroker check instance "system.adapter.shelly.0" for host "iobroker"
                              2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker"
                              2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.tr-064.0" for host "iobroker"
                              2022-01-08 08:09:18.792 - debug: host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker"
                              2022-01-08 08:09:18.793 - debug: host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"
                              2022-01-08 08:09:18.794 - debug: host.iobroker check instance "system.adapter.daswetter.0" for host "iobroker"
                              2022-01-08 08:09:18.794 - debug: host.iobroker check instance "system.adapter.dwd.0" for host "iobroker"
                              2022-01-08 08:09:18.795 - debug: host.iobroker check instance "system.adapter.feiertage.0" for host "iobroker"
                              2022-01-08 08:09:18.795 - debug: host.iobroker check instance "system.adapter.fullybrowser.0" for host "iobroker"
                              2022-01-08 08:09:18.796 - debug: host.iobroker check instance "system.adapter.info.0" for host "iobroker"
                              2022-01-08 08:09:18.797 - debug: host.iobroker check instance "system.adapter.netatmo-crawler.0" for host "iobroker"
                              2022-01-08 08:09:18.797 - debug: host.iobroker check instance "system.adapter.sonos.0" for host "iobroker"
                              2022-01-08 08:09:18.798 - debug: host.iobroker check instance "system.adapter.tankerkoenig.0" for host "iobroker"
                              2022-01-08 08:09:18.799 - debug: host.iobroker check instance "system.adapter.vis-hqwidgets.0" for host "iobroker"
                              2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-metro.0" for host "iobroker"
                              2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-players.0" for host "iobroker"
                              2022-01-08 08:09:18.800 - debug: host.iobroker check instance "system.adapter.vis-timeandweather.0" for host "iobroker"
                              2022-01-08 08:09:18.801 - debug: host.iobroker check instance "system.adapter.vis.0" for host "iobroker"
                              2022-01-08 08:09:18.801 - debug: host.iobroker check instance "system.adapter.web.0" for host "iobroker"
                              2022-01-08 08:09:18.802 - info: host.iobroker starting 23 instances
                              2022-01-08 08:09:18.833 - debug: host.iobroker added notifications configuration of system.adapter.admin.0
                              2022-01-08 08:09:18.833 - debug: host.iobroker startInstance admin.0 loglevel=info, compact=false
                              2022-01-08 08:09:18.842 - info: host.iobroker instance system.adapter.admin.0 started with pid 174256
                              2022-01-08 08:09:19.307 - error: admin.0 (174256) admin.0 already running
                              2022-01-08 08:09:19.308 - warn: admin.0 (174256) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:19.841 - error: host.iobroker instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:19.841 - debug: host.iobroker Reset crash count of system.adapter.admin.0, because non-crash exit
                              2022-01-08 08:09:19.841 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled
                              2022-01-08 08:09:22.828 - debug: host.iobroker added notifications configuration of system.adapter.javascript.0
                              2022-01-08 08:09:22.829 - debug: host.iobroker startInstance javascript.0 loglevel=info, compact=false
                              2022-01-08 08:09:22.835 - info: host.iobroker instance system.adapter.javascript.0 started with pid 174267
                              2022-01-08 08:09:23.516 - error: javascript.0 (174267) javascript.0 already running
                              2022-01-08 08:09:23.518 - warn: javascript.0 (174267) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:24.048 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:24.048 - debug: host.iobroker Reset crash count of system.adapter.javascript.0, because non-crash exit
                              2022-01-08 08:09:24.048 - info: host.iobroker Restart adapter system.adapter.javascript.0 because enabled
                              2022-01-08 08:09:26.832 - debug: host.iobroker added notifications configuration of system.adapter.scenes.0
                              2022-01-08 08:09:26.833 - debug: host.iobroker startInstance scenes.0 loglevel=info, compact=false
                              2022-01-08 08:09:26.841 - info: host.iobroker instance system.adapter.scenes.0 started with pid 174278
                              2022-01-08 08:09:27.169 - error: scenes.0 (174278) scenes.0 already running
                              2022-01-08 08:09:27.170 - warn: scenes.0 (174278) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:27.699 - error: host.iobroker instance system.adapter.scenes.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:27.699 - debug: host.iobroker Reset crash count of system.adapter.scenes.0, because non-crash exit
                              2022-01-08 08:09:27.699 - info: host.iobroker Restart adapter system.adapter.scenes.0 because enabled
                              2022-01-08 08:09:30.823 - debug: host.iobroker added notifications configuration of system.adapter.hm-rega.0
                              2022-01-08 08:09:30.823 - debug: host.iobroker startInstance hm-rega.0 loglevel=info, compact=false
                              2022-01-08 08:09:30.830 - info: host.iobroker instance system.adapter.hm-rega.0 started with pid 174290
                              2022-01-08 08:09:31.253 - error: hm-rega.0 (174290) hm-rega.0 already running
                              2022-01-08 08:09:31.254 - warn: hm-rega.0 (174290) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:31.783 - error: host.iobroker instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:31.783 - debug: host.iobroker Reset crash count of system.adapter.hm-rega.0, because non-crash exit
                              2022-01-08 08:09:31.783 - info: host.iobroker Restart adapter system.adapter.hm-rega.0 because enabled
                              2022-01-08 08:09:34.821 - debug: host.iobroker added notifications configuration of system.adapter.hm-rpc.0
                              2022-01-08 08:09:34.822 - debug: host.iobroker startInstance hm-rpc.0 loglevel=info, compact=false
                              2022-01-08 08:09:34.828 - info: host.iobroker instance system.adapter.hm-rpc.0 started with pid 174301
                              2022-01-08 08:09:35.162 - error: hm-rpc.0 (174301) hm-rpc.0 already running
                              2022-01-08 08:09:35.163 - warn: hm-rpc.0 (174301) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:35.696 - error: host.iobroker instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:35.696 - debug: host.iobroker Reset crash count of system.adapter.hm-rpc.0, because non-crash exit
                              2022-01-08 08:09:35.696 - info: host.iobroker Restart adapter system.adapter.hm-rpc.0 because enabled
                              2022-01-08 08:09:38.838 - debug: host.iobroker added notifications configuration of system.adapter.ical.0
                              2022-01-08 08:09:38.860 - info: host.iobroker instance scheduled system.adapter.ical.0 56 0,3,6,9,12,15,18,21 * * *
                              2022-01-08 08:09:38.864 - info: host.iobroker instance system.adapter.ical.0 started with pid 174312
                              2022-01-08 08:09:39.460 - info: ical.0 (174312) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:40.023 - info: ical.0 (174312) processing URL: Familie hier ist nix
                              2022-01-08 08:09:42.822 - debug: host.iobroker added notifications configuration of system.adapter.ical.2
                              2022-01-08 08:09:42.827 - info: host.iobroker instance scheduled system.adapter.ical.2 58 3 * * *
                              2022-01-08 08:09:42.831 - info: host.iobroker instance system.adapter.ical.2 started with pid 174327
                              2022-01-08 08:09:43.423 - info: ical.2 (174327) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:43.741 - info: ical.2 (174327) processing URL: Geburtstag auch das weg
                              2022-01-08 08:09:45.143 - info: ical.0 (174312) Terminated (NO_ERROR): Without reason
                              2022-01-08 08:09:45.670 - info: host.iobroker instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              2022-01-08 08:09:46.821 - debug: host.iobroker added notifications configuration of system.adapter.ical.3
                              2022-01-08 08:09:46.827 - info: host.iobroker instance scheduled system.adapter.ical.3 57 3 * * *
                              2022-01-08 08:09:46.831 - info: host.iobroker instance system.adapter.ical.3 started with pid 174342
                              2022-01-08 08:09:47.411 - info: ical.3 (174342) starting. Version 1.11.6 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:48.245 - info: ical.3 (174342) processing URL: Arbeit nix mehr
                              2022-01-08 08:09:48.821 - info: ical.2 (174327) Terminated (NO_ERROR): Without reason
                              2022-01-08 08:09:49.349 - info: host.iobroker instance system.adapter.ical.2 terminated with code 0 (NO_ERROR)
                              2022-01-08 08:09:49.845 - debug: host.iobroker added notifications configuration of system.adapter.admin.0
                              2022-01-08 08:09:49.845 - debug: host.iobroker startInstance admin.0 loglevel=info, compact=false
                              2022-01-08 08:09:49.851 - info: host.iobroker instance system.adapter.admin.0 started with pid 174357
                              2022-01-08 08:09:50.345 - info: admin.0 (174357) Plugin sentry Sentry Plugin disabled for this process because data reporting is disabled on instance
                              2022-01-08 08:09:50.350 - info: admin.0 (174357) starting. Version 5.2.3 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:50.367 - info: admin.0 (174357) requesting all states
                              2022-01-08 08:09:50.367 - info: admin.0 (174357) requesting all objects
                              2022-01-08 08:09:50.694 - info: admin.0 (174357) received all objects
                              2022-01-08 08:09:50.804 - debug: host.iobroker added notifications configuration of system.adapter.netatmo.0
                              2022-01-08 08:09:50.814 - info: admin.0 (174357) http server listening on port 8081
                              2022-01-08 08:09:50.804 - debug: host.iobroker startInstance netatmo.0 loglevel=info, compact=false
                              2022-01-08 08:09:50.814 - info: host.iobroker instance system.adapter.netatmo.0 started with pid 174372
                              2022-01-08 08:09:50.814 - info: admin.0 (174357) Use link "http://localhost:8081" to configure.
                              2022-01-08 08:09:51.240 - error: netatmo.0 (174372) netatmo.0 already running
                              2022-01-08 08:09:51.240 - warn: netatmo.0 (174372) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:51.771 - error: host.iobroker instance system.adapter.netatmo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:51.771 - debug: host.iobroker Reset crash count of system.adapter.netatmo.0, because non-crash exit
                              2022-01-08 08:09:51.771 - info: host.iobroker Restart adapter system.adapter.netatmo.0 because enabled
                              2022-01-08 08:09:53.456 - info: ical.3 (174342) Terminated (NO_ERROR): Without reason
                              2022-01-08 08:09:53.979 - info: host.iobroker instance system.adapter.ical.3 terminated with code 0 (NO_ERROR)
                              2022-01-08 08:09:54.050 - debug: host.iobroker added notifications configuration of system.adapter.javascript.0
                              2022-01-08 08:09:54.050 - debug: host.iobroker startInstance javascript.0 loglevel=info, compact=false
                              2022-01-08 08:09:54.056 - info: host.iobroker instance system.adapter.javascript.0 started with pid 174383
                              2022-01-08 08:09:54.830 - debug: host.iobroker added notifications configuration of system.adapter.shelly.0
                              2022-01-08 08:09:54.831 - debug: host.iobroker startInstance shelly.0 loglevel=info, compact=false
                              2022-01-08 08:09:54.838 - info: host.iobroker instance system.adapter.shelly.0 started with pid 174394
                              2022-01-08 08:09:54.874 - info: javascript.0 (174383) starting. Version 5.2.18 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:54.915 - info: javascript.0 (174383) requesting all states
                              2022-01-08 08:09:54.916 - info: javascript.0 (174383) requesting all objects
                              2022-01-08 08:09:55.241 - info: javascript.0 (174383) received all objects
                              2022-01-08 08:09:55.316 - info: javascript.0 (174383) received all states
                              2022-01-08 08:09:55.343 - info: javascript.0 (174383) Start javascript script.js.Automaten.Küche-Tablet_Screen
                              2022-01-08 08:09:55.364 - info: javascript.0 (174383) script.js.Automaten.Küche-Tablet_Screen: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.364 - info: javascript.0 (174383) Start javascript script.js.Bad.Bad-Nachtlicht
                              2022-01-08 08:09:55.366 - info: javascript.0 (174383) script.js.Bad.Bad-Nachtlicht: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.367 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Arbeitszimmer
                              2022-01-08 08:09:55.369 - info: javascript.0 (174383) script.js.Heizung.Heizung_Arbeitszimmer: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.370 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle
                              2022-01-08 08:09:55.371 - info: javascript.0 (174383) script.js.Heizung.Heizung_Arbeitszimmer_Kontrolle: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.421 - error: shelly.0 (174394) shelly.0 already running
                              2022-01-08 08:09:55.423 - warn: shelly.0 (174394) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:55.373 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Bad
                              2022-01-08 08:09:55.376 - info: javascript.0 (174383) script.js.Heizung.Heizung_Bad: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.376 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Bad_Kontrolle
                              2022-01-08 08:09:55.379 - info: javascript.0 (174383) script.js.Heizung.Heizung_Bad_Kontrolle: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.379 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Esszimmer
                              2022-01-08 08:09:55.381 - info: javascript.0 (174383) script.js.Heizung.Heizung_Esszimmer: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.382 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Esszimmer_Kontrolle
                              2022-01-08 08:09:55.384 - info: javascript.0 (174383) script.js.Heizung.Heizung_Esszimmer_Kontrolle: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.384 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Küche
                              2022-01-08 08:09:55.387 - info: javascript.0 (174383) script.js.Heizung.Heizung_Küche: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.387 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Küche_Kontrolle
                              2022-01-08 08:09:55.389 - info: javascript.0 (174383) script.js.Heizung.Heizung_Küche_Kontrolle: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.390 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Wohnzimmer
                              2022-01-08 08:09:55.393 - info: javascript.0 (174383) script.js.Heizung.Heizung_Wohnzimmer: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.393 - info: javascript.0 (174383) Start javascript script.js.Heizung.Heizung_Wohnzimmer_Kontrolle
                              2022-01-08 08:09:55.395 - info: javascript.0 (174383) script.js.Heizung.Heizung_Wohnzimmer_Kontrolle: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.396 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe
                              2022-01-08 08:09:55.398 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe: registered 2 subscriptions and 0 schedules
                              2022-01-08 08:09:55.399 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer
                              2022-01-08 08:09:55.401 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe-Dimmer: registered 3 subscriptions and 0 schedules
                              2022-01-08 08:09:55.401 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Esszimmer-Lampe-Radio
                              2022-01-08 08:09:55.403 - info: javascript.0 (174383) script.js.Ikea-Licht.Esszimmer-Lampe-Radio: registered 2 subscriptions and 0 schedules
                              2022-01-08 08:09:55.433 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer
                              2022-01-08 08:09:55.435 - info: javascript.0 (174383) script.js.Ikea-Licht.Lampe-Wohnzimmer-Dimmer: registered 3 subscriptions and 0 schedules
                              2022-01-08 08:09:55.435 - info: javascript.0 (174383) Start javascript script.js.Ikea-Licht.Wohnzimmer-Lampe
                              2022-01-08 08:09:55.436 - info: javascript.0 (174383) script.js.Ikea-Licht.Wohnzimmer-Lampe: registered 2 subscriptions and 0 schedules
                              2022-01-08 08:09:55.437 - info: javascript.0 (174383) Start javascript script.js.Sonos.Gruppenbildung
                              2022-01-08 08:09:55.438 - info: javascript.0 (174383) script.js.Sonos.Gruppenbildung: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.438 - info: javascript.0 (174383) Start javascript script.js.Sonos.Gruppenbildung2
                              2022-01-08 08:09:55.440 - info: javascript.0 (174383) script.js.Sonos.Gruppenbildung2: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.440 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_Ess
                              2022-01-08 08:09:55.442 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_Ess: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.442 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_Küche
                              2022-01-08 08:09:55.444 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_Küche: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.444 - info: javascript.0 (174383) Start javascript script.js.Sonos.Sonos_Favoriten_WZ
                              2022-01-08 08:09:55.446 - info: javascript.0 (174383) script.js.Sonos.Sonos_Favoriten_WZ: registered 1 subscription and 0 schedules
                              2022-01-08 08:09:55.951 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:55.951 - debug: host.iobroker Reset crash count of system.adapter.shelly.0, because non-crash exit
                              2022-01-08 08:09:55.951 - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled
                              2022-01-08 08:09:57.701 - debug: host.iobroker added notifications configuration of system.adapter.scenes.0
                              2022-01-08 08:09:57.701 - debug: host.iobroker startInstance scenes.0 loglevel=info, compact=false
                              2022-01-08 08:09:57.708 - info: host.iobroker instance system.adapter.scenes.0 started with pid 174409
                              2022-01-08 08:09:58.157 - info: scenes.0 (174409) starting. Version 2.3.8 in /opt/iobroker/node_modules/iobroker.scenes, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:09:58.820 - debug: host.iobroker added notifications configuration of system.adapter.sonoff.0
                              2022-01-08 08:09:58.820 - debug: host.iobroker startInstance sonoff.0 loglevel=info, compact=false
                              2022-01-08 08:09:58.827 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 174424
                              2022-01-08 08:09:59.185 - error: sonoff.0 (174424) sonoff.0 already running
                              2022-01-08 08:09:59.186 - warn: sonoff.0 (174424) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:09:59.715 - error: host.iobroker instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:09:59.715 - debug: host.iobroker Reset crash count of system.adapter.sonoff.0, because non-crash exit
                              2022-01-08 08:09:59.715 - info: host.iobroker Restart adapter system.adapter.sonoff.0 because enabled
                              2022-01-08 08:10:01.786 - debug: host.iobroker added notifications configuration of system.adapter.hm-rega.0
                              2022-01-08 08:10:01.786 - debug: host.iobroker startInstance hm-rega.0 loglevel=info, compact=false
                              2022-01-08 08:10:01.793 - info: host.iobroker instance system.adapter.hm-rega.0 started with pid 174435
                              2022-01-08 08:10:02.371 - info: hm-rega.0 (174435) starting. Version 3.0.33 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:02.419 - info: hm-rega.0 (174435) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
                              2022-01-08 08:10:02.436 - info: hm-rega.0 (174435) ReGaHSS 192.168.178.93 up
                              2022-01-08 08:10:02.503 - info: hm-rega.0 (174435) time difference local-ccu 1s
                              2022-01-08 08:10:02.754 - info: hm-rega.0 (174435) request state values
                              2022-01-08 08:10:02.820 - debug: host.iobroker added notifications configuration of system.adapter.tr-064.0
                              2022-01-08 08:10:02.820 - debug: host.iobroker startInstance tr-064.0 loglevel=info, compact=false
                              2022-01-08 08:10:02.828 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 174450
                              2022-01-08 08:10:02.975 - info: hm-rega.0 (174435) Updated all datapoints
                              2022-01-08 08:10:02.979 - info: hm-rega.0 (174435) got 5 variables
                              2022-01-08 08:10:03.015 - info: hm-rega.0 (174435) added/updated 5 variables
                              2022-01-08 08:10:03.015 - info: hm-rega.0 (174435) deleted 0 variables
                              2022-01-08 08:10:03.022 - info: hm-rega.0 (174435) got 0 programs
                              2022-01-08 08:10:03.025 - info: hm-rega.0 (174435) update rooms to enum.rooms
                              2022-01-08 08:10:03.029 - info: hm-rega.0 (174435) added/updated 0 programs
                              2022-01-08 08:10:03.030 - info: hm-rega.0 (174435) deleted 0 programs
                              2022-01-08 08:10:03.078 - info: hm-rega.0 (174435) update functions to enum.functions
                              2022-01-08 08:10:03.093 - info: hm-rega.0 (174435) update favorites to enum.favorites
                              2022-01-08 08:10:03.094 - error: hm-rega.0 (174435) Could not synchronize favorites of user "": Error: The id "enum.favorites." is invalid. Ids are not allowed to end in "."
                              2022-01-08 08:10:03.317 - error: tr-064.0 (174450) tr-064.0 already running
                              2022-01-08 08:10:03.318 - warn: tr-064.0 (174450) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:03.846 - error: host.iobroker instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:03.846 - debug: host.iobroker Reset crash count of system.adapter.tr-064.0, because non-crash exit
                              2022-01-08 08:10:03.846 - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled
                              2022-01-08 08:10:05.698 - debug: host.iobroker added notifications configuration of system.adapter.hm-rpc.0
                              2022-01-08 08:10:05.698 - debug: host.iobroker startInstance hm-rpc.0 loglevel=info, compact=false
                              2022-01-08 08:10:05.705 - info: host.iobroker instance system.adapter.hm-rpc.0 started with pid 174461
                              2022-01-08 08:10:06.190 - info: hm-rpc.0 (174461) starting. Version 1.15.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:06.236 - info: hm-rpc.0 (174461) xmlrpc server is trying to listen on 192.168.178.92:2001
                              2022-01-08 08:10:06.237 - info: hm-rpc.0 (174461) xmlrpc client is trying to connect to 192.168.178.93:2001/ with ["http://192.168.178.92:2001","iobroker:hm-rpc.0"]
                              2022-01-08 08:10:06.247 - info: hm-rpc.0 (174461) xmlrpc <- system.listMethods ["iobroker:hm-rpc.0"]
                              2022-01-08 08:10:06.250 - info: hm-rpc.0 (174461) xmlrpc <- listDevices ["iobroker:hm-rpc.0"]
                              2022-01-08 08:10:06.264 - info: hm-rpc.0 (174461) xmlrpc -> 92 devices
                              2022-01-08 08:10:06.272 - info: hm-rpc.0 (174461) Connected
                              2022-01-08 08:10:06.804 - debug: host.iobroker added notifications configuration of system.adapter.zigbee.0
                              2022-01-08 08:10:06.804 - debug: host.iobroker startInstance zigbee.0 loglevel=info, compact=false
                              2022-01-08 08:10:06.811 - info: host.iobroker instance system.adapter.zigbee.0 started with pid 174476
                              2022-01-08 08:10:07.595 - error: zigbee.0 (174476) zigbee.0 already running
                              2022-01-08 08:10:07.596 - warn: zigbee.0 (174476) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:08.123 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:08.123 - debug: host.iobroker Reset crash count of system.adapter.zigbee.0, because non-crash exit
                              2022-01-08 08:10:08.123 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled
                              2022-01-08 08:10:10.805 - debug: host.iobroker added notifications configuration of system.adapter.backitup.0
                              2022-01-08 08:10:10.805 - debug: host.iobroker startInstance backitup.0 loglevel=info, compact=false
                              2022-01-08 08:10:10.811 - info: host.iobroker instance system.adapter.backitup.0 started with pid 174487
                              2022-01-08 08:10:11.160 - error: backitup.0 (174487) backitup.0 already running
                              2022-01-08 08:10:11.161 - warn: backitup.0 (174487) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:11.692 - error: host.iobroker instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:11.692 - debug: host.iobroker Reset crash count of system.adapter.backitup.0, because non-crash exit
                              2022-01-08 08:10:11.692 - info: host.iobroker Restart adapter system.adapter.backitup.0 because enabled
                              2022-01-08 08:10:14.805 - debug: host.iobroker added notifications configuration of system.adapter.daswetter.0
                              2022-01-08 08:10:14.815 - info: host.iobroker instance scheduled system.adapter.daswetter.0 55 0,3,6,9,12,15,18,21 * * *
                              2022-01-08 08:10:14.819 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 174498
                              2022-01-08 08:10:15.291 - info: daswetter.0 (174498) starting. Version 3.0.9 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:17.567 - info: daswetter.0 (174498) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                              2022-01-08 08:10:18.074 - info: daswetter.0 (174498) cleaned everything up...
                              2022-01-08 08:10:18.095 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2022-01-08 08:10:18.819 - debug: host.iobroker added notifications configuration of system.adapter.dwd.0
                              2022-01-08 08:10:18.822 - info: host.iobroker instance scheduled system.adapter.dwd.0 53 * * * *
                              2022-01-08 08:10:18.827 - info: host.iobroker instance system.adapter.dwd.0 started with pid 174513
                              2022-01-08 08:10:19.332 - info: dwd.0 (174513) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:19.844 - info: dwd.0 (174513) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2022-01-08 08:10:20.367 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2022-01-08 08:10:21.773 - debug: host.iobroker added notifications configuration of system.adapter.netatmo.0
                              2022-01-08 08:10:21.773 - debug: host.iobroker startInstance netatmo.0 loglevel=info, compact=false
                              2022-01-08 08:10:21.780 - info: host.iobroker instance system.adapter.netatmo.0 started with pid 174528
                              2022-01-08 08:10:22.246 - info: netatmo.0 (174528) starting. Version 1.4.4 in /opt/iobroker/node_modules/iobroker.netatmo, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:22.805 - debug: host.iobroker added notifications configuration of system.adapter.feiertage.0
                              2022-01-08 08:10:22.810 - info: host.iobroker instance scheduled system.adapter.feiertage.0 36 3 * * *
                              2022-01-08 08:10:22.814 - info: host.iobroker instance system.adapter.feiertage.0 started with pid 174543
                              2022-01-08 08:10:23.264 - info: feiertage.0 (174543) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.feiertage, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:23.397 - info: feiertage.0 (174543) Next holiday: Rosenmontag is in 51 days on 28.02.2022
                              2022-01-08 08:10:23.403 - info: feiertage.0 (174543) adapter feiertage objects written
                              2022-01-08 08:10:23.906 - info: feiertage.0 (174543) Terminated (NO_ERROR): Without reason
                              2022-01-08 08:10:24.432 - info: host.iobroker instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
                              2022-01-08 08:10:25.954 - debug: host.iobroker added notifications configuration of system.adapter.shelly.0
                              2022-01-08 08:10:25.954 - debug: host.iobroker startInstance shelly.0 loglevel=info, compact=false
                              2022-01-08 08:10:25.960 - info: host.iobroker instance system.adapter.shelly.0 started with pid 174558
                              2022-01-08 08:10:26.625 - info: shelly.0 (174558) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:26.637 - info: shelly.0 (174558) Starting Adapter shelly.0 in version 5.0.0
                              2022-01-08 08:10:26.712 - info: shelly.0 (174558) Starting in CoAP mode.
                              2022-01-08 08:10:26.733 - info: shelly.0 (174558) Listening for Shelly packets in the network
                              2022-01-08 08:10:26.821 - debug: host.iobroker added notifications configuration of system.adapter.fullybrowser.0
                              2022-01-08 08:10:26.821 - debug: host.iobroker startInstance fullybrowser.0 loglevel=info, compact=false
                              2022-01-08 08:10:26.827 - info: host.iobroker instance system.adapter.fullybrowser.0 started with pid 174573
                              2022-01-08 08:10:27.156 - error: fullybrowser.0 (174573) fullybrowser.0 already running
                              2022-01-08 08:10:27.157 - warn: fullybrowser.0 (174573) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:27.685 - error: host.iobroker instance system.adapter.fullybrowser.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:27.686 - debug: host.iobroker Reset crash count of system.adapter.fullybrowser.0, because non-crash exit
                              2022-01-08 08:10:27.686 - info: host.iobroker Restart adapter system.adapter.fullybrowser.0 because enabled
                              2022-01-08 08:10:29.307 - info: shelly.0 (174558) Shelly device 192.168.178.54 (shellydimmer / shellydimmer-CC50E3F3AB05 / SHDM-1#CC50E3F3AB05#1) with CoAP connected! Polltime set to 5 sec.
                              2022-01-08 08:10:29.716 - debug: host.iobroker added notifications configuration of system.adapter.sonoff.0
                              2022-01-08 08:10:29.716 - debug: host.iobroker startInstance sonoff.0 loglevel=info, compact=false
                              2022-01-08 08:10:29.723 - info: host.iobroker instance system.adapter.sonoff.0 started with pid 174584
                              2022-01-08 08:10:30.211 - info: sonoff.0 (174584) starting. Version 2.4.7 in /opt/iobroker/node_modules/iobroker.sonoff, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:30.234 - info: sonoff.0 (174584) Starting MQTT server on port 1883
                              2022-01-08 08:10:30.501 - info: sonoff.0 (174584) Client [Küche-Tisch] connected with secret 1641625830498_9529
                              2022-01-08 08:10:30.717 - info: sonoff.0 (174584) Client [Bad2-Wanne] connected with secret 1641625830716_4062
                              2022-01-08 08:10:30.729 - info: sonoff.0 (174584) Client [Kueche-Herd] connected with secret 1641625830729_1300
                              2022-01-08 08:10:30.820 - debug: host.iobroker added notifications configuration of system.adapter.info.0
                              2022-01-08 08:10:30.820 - debug: host.iobroker startInstance info.0 loglevel=info, compact=false
                              2022-01-08 08:10:30.826 - info: host.iobroker instance system.adapter.info.0 started with pid 174599
                              2022-01-08 08:10:31.344 - error: info.0 (174599) info.0 already running
                              2022-01-08 08:10:31.345 - warn: info.0 (174599) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:31.878 - error: host.iobroker instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:31.878 - debug: host.iobroker Reset crash count of system.adapter.info.0, because non-crash exit
                              2022-01-08 08:10:31.878 - info: host.iobroker Restart adapter system.adapter.info.0 because enabled
                              2022-01-08 08:10:32.565 - info: shelly.0 (174558) Shelly device 192.168.178.53 (shellyplug-s / shellyplug-s-79F6A9 / SHPLG-S#79F6A9#1) with CoAP connected! Polltime set to 5 sec.
                              2022-01-08 08:10:33.848 - debug: host.iobroker added notifications configuration of system.adapter.tr-064.0
                              2022-01-08 08:10:33.848 - debug: host.iobroker startInstance tr-064.0 loglevel=info, compact=false
                              2022-01-08 08:10:33.855 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 174618
                              2022-01-08 08:10:34.518 - info: tr-064.0 (174618) starting. Version 4.2.15 in /opt/iobroker/node_modules/iobroker.tr-064, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:34.818 - debug: host.iobroker added notifications configuration of system.adapter.sonos.0
                              2022-01-08 08:10:34.818 - debug: host.iobroker startInstance sonos.0 loglevel=info, compact=false
                              2022-01-08 08:10:34.828 - info: host.iobroker instance system.adapter.sonos.0 started with pid 174633
                              2022-01-08 08:10:35.226 - error: sonos.0 (174633) sonos.0 already running
                              2022-01-08 08:10:35.227 - warn: sonos.0 (174633) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:35.758 - error: host.iobroker instance system.adapter.sonos.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:35.758 - debug: host.iobroker Reset crash count of system.adapter.sonos.0, because non-crash exit
                              2022-01-08 08:10:35.758 - info: host.iobroker Restart adapter system.adapter.sonos.0 because enabled
                              2022-01-08 08:10:36.118 - info: shelly.0 (174558) Shelly device 192.168.178.55 (shellycolorbulb / shellycolorbulb-E8DB84AA2596 / SHCB-1#E8DB84AA2596#1) with CoAP connected! Polltime set to 5 sec.
                              2022-01-08 08:10:36.760 - debug: host.iobroker added notifications configuration of system.adapter.sonos.0
                              2022-01-08 08:10:36.760 - debug: host.iobroker startInstance sonos.0 loglevel=info, compact=false
                              2022-01-08 08:10:36.768 - info: host.iobroker instance system.adapter.sonos.0 started with pid 174644
                              2022-01-08 08:10:37.180 - info: sonos.0 (174644) starting. Version 2.1.7 in /opt/iobroker/node_modules/iobroker.sonos, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:38.125 - debug: host.iobroker added notifications configuration of system.adapter.zigbee.0
                              2022-01-08 08:10:38.126 - debug: host.iobroker startInstance zigbee.0 loglevel=info, compact=false
                              2022-01-08 08:10:38.132 - info: host.iobroker instance system.adapter.zigbee.0 started with pid 174659
                              2022-01-08 08:10:38.805 - debug: host.iobroker added notifications configuration of system.adapter.tankerkoenig.0
                              2022-01-08 08:10:38.805 - debug: host.iobroker startInstance tankerkoenig.0 loglevel=info, compact=false
                              2022-01-08 08:10:38.812 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 174670
                              2022-01-08 08:10:39.079 - info: zigbee.0 (174659) starting. Version 1.6.8 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:39.116 - info: zigbee.0 (174659) Starting Zigbee npm ...
                              2022-01-08 08:10:39.254 - info: zigbee.0 (174659) Installed Version: iobroker.zigbee@1.6.8
                              2022-01-08 08:10:39.304 - error: tankerkoenig.0 (174670) tankerkoenig.0 already running
                              2022-01-08 08:10:39.304 - warn: tankerkoenig.0 (174670) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:39.837 - error: host.iobroker instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:39.837 - debug: host.iobroker Reset crash count of system.adapter.tankerkoenig.0, because non-crash exit
                              2022-01-08 08:10:39.837 - info: host.iobroker Restart adapter system.adapter.tankerkoenig.0 because enabled
                              2022-01-08 08:10:40.755 - info: shelly.0 (174558) Shelly device 192.168.178.52 (shelly1 / shelly1-10DCB4 / SHSW-1#10DCB4#1) with CoAP connected! Polltime set to 5 sec.
                              2022-01-08 08:10:40.766 - info: shelly.0 (174558) Shelly device 192.168.178.51 (shelly1 / shelly1-767A0F / SHSW-1#767A0F#1) with CoAP connected! Polltime set to 5 sec.
                              2022-01-08 08:10:41.013 - info: zigbee.0 (174659) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}}
                              2022-01-08 08:10:41.022 - info: zigbee.0 (174659) Unable to disable LED, unsupported function.
                              2022-01-08 08:10:41.024 - info: zigbee.0 (174659) --> transmitPower : normal
                              2022-01-08 08:10:41.046 - info: zigbee.0 (174659) Currently 17 devices are joined:
                              2022-01-08 08:10:41.063 - info: zigbee.0 (174659) 0x086bd7fffe51dbd6 (addr 64726): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
                              2022-01-08 08:10:41.064 - info: zigbee.0 (174659) 0x00158d0003faf01b (addr 62232): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                              2022-01-08 08:10:41.065 - info: zigbee.0 (174659) 0x00158d000358c678 (addr 5513): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.065 - info: zigbee.0 (174659) 0x14b457fffe732925 (addr 9173): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
                              2022-01-08 08:10:41.066 - info: zigbee.0 (174659) 0x842e14fffea1801a (addr 13524): LED1624G9 - IKEA TRADFRI LED bulb E14/E26/E27 600 lumen, dimmable, color, opal white (Router)
                              2022-01-08 08:10:41.066 - info: zigbee.0 (174659) 0x00158d000358c57a (addr 24218): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.067 - info: zigbee.0 (174659) 0x00158d00045140d3 (addr 24472): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.067 - info: zigbee.0 (174659) 0x00158d00045d46cc (addr 30298): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0x00158d00045c5d25 (addr 44319): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0xbc33acfffe158f61 (addr 45674): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
                              2022-01-08 08:10:41.068 - info: zigbee.0 (174659) 0x00158d00042d17a0 (addr 42890): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2022-01-08 08:10:41.069 - info: zigbee.0 (174659) 0x00158d0006f6ba34 (addr 22622): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                              2022-01-08 08:10:41.069 - info: zigbee.0 (174659) 0x5c0272fffe2c4ca3 (addr 30163): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                              2022-01-08 08:10:41.070 - info: zigbee.0 (174659) 0x60a423fffe116b9c (addr 42734): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                              2022-01-08 08:10:41.071 - info: zigbee.0 (174659) 0x60a423fffe03ce72 (addr 31923): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                              2022-01-08 08:10:41.071 - info: zigbee.0 (174659) 0xbc33acfffe47e5ef (addr 19590): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                              2022-01-08 08:10:41.072 - info: zigbee.0 (174659) 0x5c0272fffe28904b (addr 63315): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
                              2022-01-08 08:10:41.072 - info: zigbee.0 (174659) Zigbee started
                              2022-01-08 08:10:41.177 - info: sonoff.0 (174584) Client [Bad1-Spiegel] connected with secret 1641625841176_4680
                              2022-01-08 08:10:41.694 - debug: host.iobroker added notifications configuration of system.adapter.backitup.0
                              2022-01-08 08:10:41.694 - debug: host.iobroker startInstance backitup.0 loglevel=info, compact=false
                              2022-01-08 08:10:41.701 - info: host.iobroker instance system.adapter.backitup.0 started with pid 174685
                              2022-01-08 08:10:42.239 - info: backitup.0 (174685) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:42.259 - info: backitup.0 (174685) [iobroker] backup was activated at 03:30 every 1 day(s)
                              2022-01-08 08:10:42.283 - info: backitup.0 (174685) [ccu] backup was activated at 01:30 every 1 day(s)
                              2022-01-08 08:10:42.820 - debug: host.iobroker added notifications configuration of system.adapter.vis.0
                              2022-01-08 08:10:42.820 - debug: host.iobroker startInstance vis.0 loglevel=info, compact=false
                              2022-01-08 08:10:43.229 - info: vis.0 (174700) starting. Version 1.4.7 in /opt/iobroker/node_modules/iobroker.vis, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:43.507 - info: vis.0 (174700) vis license is OK.
                              2022-01-08 08:10:44.121 - info: vis.0 (174700) Terminated (NO_ERROR): Without reason
                              2022-01-08 08:10:44.650 - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once
                              2022-01-08 08:10:46.816 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                              2022-01-08 08:10:46.817 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                              2022-01-08 08:10:46.823 - info: host.iobroker instance system.adapter.web.0 started with pid 174715
                              2022-01-08 08:10:47.192 - error: web.0 (174715) web.0 already running
                              2022-01-08 08:10:47.193 - warn: web.0 (174715) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                              2022-01-08 08:10:47.720 - error: host.iobroker instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                              2022-01-08 08:10:47.721 - debug: host.iobroker Reset crash count of system.adapter.web.0, because non-crash exit
                              2022-01-08 08:10:47.721 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled
                              2022-01-08 08:10:57.289 - info: sonoff.0 (174584) Client [Bad-Nachtlicht] connected with secret 1641625857288_2465
                              2022-01-08 08:10:57.687 - debug: host.iobroker added notifications configuration of system.adapter.fullybrowser.0
                              2022-01-08 08:10:57.688 - debug: host.iobroker startInstance fullybrowser.0 loglevel=info, compact=false
                              2022-01-08 08:10:57.694 - info: host.iobroker instance system.adapter.fullybrowser.0 started with pid 174726
                              2022-01-08 08:10:58.077 - info: fullybrowser.0 (174726) starting. Version 2.0.12 in /opt/iobroker/node_modules/iobroker.fullybrowser, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:10:58.088 - info: fullybrowser.0 (174726) Start with IP : 192.168.178.44
                              2022-01-08 08:11:01.881 - debug: host.iobroker added notifications configuration of system.adapter.info.0
                              2022-01-08 08:11:01.881 - debug: host.iobroker startInstance info.0 loglevel=info, compact=false
                              2022-01-08 08:11:01.888 - info: host.iobroker instance system.adapter.info.0 started with pid 174741
                              2022-01-08 08:11:02.792 - info: info.0 (174741) starting. Version 1.9.16 in /opt/iobroker/node_modules/iobroker.info, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:11:02.828 - info: info.0 (174741) Reading/updating systemdata.
                              2022-01-08 08:11:03.251 - info: info.0 (174741) cpu Temp res = {"main":null,"cores":[],"max":null,"socket":[],"chipset":null}
                              2022-01-08 08:11:09.839 - debug: host.iobroker added notifications configuration of system.adapter.tankerkoenig.0
                              2022-01-08 08:11:09.840 - debug: host.iobroker startInstance tankerkoenig.0 loglevel=info, compact=false
                              2022-01-08 08:11:09.847 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 175145
                              2022-01-08 08:11:10.754 - info: tankerkoenig.0 (175145) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:11:10.764 - info: tankerkoenig.0 (175145) Sync time set to 12 minutes or 720000 ms
                              2022-01-08 08:11:17.724 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                              2022-01-08 08:11:17.726 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                              2022-01-08 08:11:17.737 - info: host.iobroker instance system.adapter.web.0 started with pid 175160
                              2022-01-08 08:11:18.261 - info: web.0 (175160) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:11:18.367 - debug: host.iobroker-Server States 127.0.0.1:38890 Redis Socket error: Error: read ECONNRESET
                              2022-01-08 08:11:18.389 - warn: host.iobroker instance system.adapter.web.0 terminated due to SIGSEGV
                              2022-01-08 08:11:18.389 - info: host.iobroker instance system.adapter.web.0 terminated with code NaN ()
                              2022-01-08 08:11:18.390 - debug: host.iobroker Reset crash count of system.adapter.web.0, because non-crash exit
                              2022-01-08 08:11:18.390 - info: host.iobroker Restart adapter system.adapter.web.0 because enabled
                              2022-01-08 08:11:48.392 - debug: host.iobroker added notifications configuration of system.adapter.web.0
                              2022-01-08 08:11:48.392 - debug: host.iobroker startInstance web.0 loglevel=info, compact=false
                              2022-01-08 08:11:48.398 - info: host.iobroker instance system.adapter.web.0 started with pid 175175
                              2022-01-08 08:11:48.905 - info: web.0 (175175) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.18.2, js-controller: 3.3.22
                              2022-01-08 08:11:49.028 - info: web.0 (175175) socket.io server listening on port 8082
                              2022-01-08 08:11:49.030 - info: web.0 (175175) simpleAPI server listening on port 8082
                              2022-01-08 08:11:49.030 - info: web.0 (175175) Allow states only when user is owner: false
                              2022-01-08 08:11:49.033 - info: web.0 (175175) http server listening on port 8082
                              2022-01-08 08:12:07.264 - info: web.0 (175175) ==>Connected system.user.admin from 192.168.178.44code_text
                              
                              GlasfaserG Offline
                              GlasfaserG Offline
                              Glasfaser
                              schrieb am zuletzt editiert von Glasfaser
                              #71

                              @matrose65

                              processing URL: Arbeit https: .....

                              und die anderen !!!!!!!!!!!!!

                              Lösche deine Ical URL , im Log !

                              Es kommt mir so vor als wäre es ein Speicherproblem .
                              Ich kenne Proxmox nicht wie man das Prüfen kann , aber da gibt es andere hier im Thread , die eventuell damit helfen können !?

                              @paul53 sagte in Adapter werden neu gestartet:
                              @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.

                              RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                              Eventuell ein Script ... mit einer Schleife !?

                              Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                              HomoranH M GlasfaserG 4 Antworten Letzte Antwort
                              0
                              • GlasfaserG Glasfaser

                                @matrose65

                                processing URL: Arbeit https: .....

                                und die anderen !!!!!!!!!!!!!

                                Lösche deine Ical URL , im Log !

                                Es kommt mir so vor als wäre es ein Speicherproblem .
                                Ich kenne Proxmox nicht wie man das Prüfen kann , aber da gibt es andere hier im Thread , die eventuell damit helfen können !?

                                @paul53 sagte in Adapter werden neu gestartet:
                                @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.

                                RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                                Eventuell ein Script ... mit einer Schleife !?

                                HomoranH Nicht stören
                                HomoranH Nicht stören
                                Homoran
                                Global Moderator Administrators
                                schrieb am zuletzt editiert von
                                #72

                                @glasfaser sagte in Adapter werden neu gestartet:

                                Lösche deine Ical URL , im Log !

                                Danone!

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

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

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

                                1 Antwort Letzte Antwort
                                1
                                • GlasfaserG Glasfaser

                                  @matrose65

                                  processing URL: Arbeit https: .....

                                  und die anderen !!!!!!!!!!!!!

                                  Lösche deine Ical URL , im Log !

                                  Es kommt mir so vor als wäre es ein Speicherproblem .
                                  Ich kenne Proxmox nicht wie man das Prüfen kann , aber da gibt es andere hier im Thread , die eventuell damit helfen können !?

                                  @paul53 sagte in Adapter werden neu gestartet:
                                  @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.

                                  RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                                  Eventuell ein Script ... mit einer Schleife !?

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

                                  @glasfaser

                                  Speicherproblem? Da bräuchte ich Hilfe.

                                  Jetzt sieht es erstmal so aus:

                                  Festplatte frei: 89%, Gesamte RAM-Auslastung: 1587 Mb / Frei: 85% = 6803 Mb [Server: iobroker - 17 Prozesse]

                                  Und Danke für das löschen der URL ( Homoran)

                                  GlasfaserG 1 Antwort Letzte Antwort
                                  0
                                  • GlasfaserG Glasfaser

                                    @matrose65

                                    processing URL: Arbeit https: .....

                                    und die anderen !!!!!!!!!!!!!

                                    Lösche deine Ical URL , im Log !

                                    Es kommt mir so vor als wäre es ein Speicherproblem .
                                    Ich kenne Proxmox nicht wie man das Prüfen kann , aber da gibt es andere hier im Thread , die eventuell damit helfen können !?

                                    @paul53 sagte in Adapter werden neu gestartet:
                                    @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.

                                    RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                                    Eventuell ein Script ... mit einer Schleife !?

                                    HomoranH Nicht stören
                                    HomoranH Nicht stören
                                    Homoran
                                    Global Moderator Administrators
                                    schrieb am zuletzt editiert von Homoran
                                    #74

                                    @glasfaser sagte in Adapter werden neu gestartet:

                                    Es kommt mir so vor als wäre es ein Speicherproblem .

                                    denke ich schon lange
                                    Aber warum, da sollte noch genug da sein

                                    @matrose65 sagte in Adapter werden neu gestartet:

                                    Jetzt sieht es erstmal so aus:
                                    Festplatte frei: 89%, Gesamte RAM-Auslastung: 1587 Mb / Frei: 85% = 6803 Mb [Server: iobroker - 17 Prozesse]

                                    das ist nicht unbedingt die Referenz ;-)

                                    such dir das auf der Konsole mit free -ht --mega

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

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

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

                                    1 Antwort Letzte Antwort
                                    0
                                    • GlasfaserG Glasfaser

                                      @matrose65

                                      processing URL: Arbeit https: .....

                                      und die anderen !!!!!!!!!!!!!

                                      Lösche deine Ical URL , im Log !

                                      Es kommt mir so vor als wäre es ein Speicherproblem .
                                      Ich kenne Proxmox nicht wie man das Prüfen kann , aber da gibt es andere hier im Thread , die eventuell damit helfen können !?

                                      @paul53 sagte in Adapter werden neu gestartet:
                                      @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.

                                      RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                                      Eventuell ein Script ... mit einer Schleife !?

                                      GlasfaserG Offline
                                      GlasfaserG Offline
                                      Glasfaser
                                      schrieb am zuletzt editiert von
                                      #75

                                      @paul53 sagte in Adapter werden neu gestartet:
                                      @matrose65 sagte: Es wird um diese Zeit der ical.2 aktualisiert. Danach beginnen die Fehler.
                                      RAM voll? Der Start einer Instanz benötigt kurzzeitig viel RAM.

                                      @glasfaser sagte in
                                      Eventuell ein Script ... mit einer Schleife !?

                                      Eventuell das !?

                                      Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                      1 Antwort Letzte Antwort
                                      0
                                      • M matrose65

                                        @glasfaser

                                        Speicherproblem? Da bräuchte ich Hilfe.

                                        Jetzt sieht es erstmal so aus:

                                        Festplatte frei: 89%, Gesamte RAM-Auslastung: 1587 Mb / Frei: 85% = 6803 Mb [Server: iobroker - 17 Prozesse]

                                        Und Danke für das löschen der URL ( Homoran)

                                        GlasfaserG Offline
                                        GlasfaserG Offline
                                        Glasfaser
                                        schrieb am zuletzt editiert von
                                        #76

                                        @matrose65 sagte in Adapter werden neu gestartet:

                                        Jetzt sieht es erstmal so aus:

                                        Das ist die Momentaufnahme von jetzt ....

                                        Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                        1 Antwort Letzte Antwort
                                        0
                                        • W Wildbill

                                          @crunchip sagte in Adapter werden neu gestartet:

                                          TASK ERROR: VM quit/powerdown failed - got timeout

                                          Ich nehme an, das war ein Reboot über die Proxmox-Konsole und nicht aus der VM heraus?
                                          Die Meldung taucht wohl immer wieder mal auf bei Proxmox. Öfters anscheinend in Verbindung mit Debian innerhalb der VM (welches Betriebssystem läuft da bei Dir?). Zudem gab es kürzlich wohl einen Bug in Proxmox selbst, deshalb sollte die aktuellste Version installiert werden, entweder die aktuellste 6.4 oder gleich der 7er-Zweig. HIER steht das auch nochmal so. Aber auch keine wirkliche Lösung.
                                          Gruss, Jürgen

                                          crunchipC Abwesend
                                          crunchipC Abwesend
                                          crunchip
                                          Forum Testing Most Active
                                          schrieb am zuletzt editiert von
                                          #77

                                          @wildbill sagte in Adapter werden neu gestartet:

                                          das war ein Reboot über die Proxmox-Konsole

                                          richtig

                                          @wildbill sagte in Adapter werden neu gestartet:

                                          deshalb sollte die aktuellste Version installiert werden

                                          es läuft die aktuelle 7er Version

                                          @wildbill sagte in Adapter werden neu gestartet:

                                          Öfters anscheinend in Verbindung mit Debian innerhalb der VM

                                          ja ist ne Debian Buster VM

                                          umgestiegen von Proxmox auf Unraid

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


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          577

                                          Online

                                          32.5k

                                          Benutzer

                                          81.7k

                                          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