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. ioBroker Allgemein
  4. js-controller 5.0.x jetzt in der BETA

NEWS

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.0k

js-controller 5.0.x jetzt in der BETA

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
580 Beiträge 71 Kommentatoren 198.3k Aufrufe 67 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.
  • LausiDL Offline
    LausiDL Offline
    LausiD
    schrieb am zuletzt editiert von
    #351

    Aktualisierung von 5.0.5 auf 5.0.6 Abbruch mit Fehler.
    Jemand eine Idee?

    host.raspberrypi
    	2023-07-04 22:21:29.848	info	[CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
    host.raspberrypi
    	2023-07-04 22:21:24.686	info	[CONTROLLER_AUTO_UPGRADE] Final information delivered
    host.raspberrypi
    	2023-07-04 22:21:24.426	error	[CONTROLLER_AUTO_UPGRADE] Could not install js-controller@5.0.6
    host.raspberrypi
    	2023-07-04 22:21:24.418	error	[CONTROLLER_AUTO_UPGRADE] npm ERR! code 128npm ERR! An unknown git error occurrednpm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/iobroker-community-adapters/ioBroker.fhem.gitnpm ERR! command-line line 0: unsupported option "accept-new".npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.npm ERR! npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehennpm ERR! und das Repository existiert.npm ERR! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2023-07-04T20_20_52_309Z-debug-0.log
    host.raspberrypi
    	2023-07-04 22:20:49.887	info	[CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
    host.raspberrypi
    	2023-07-04 22:20:49.871	info	[CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
    

    Doku zum FHEM Adapter
    Aktuelles zum FHEM Adapter
    Test FHEM Adapter

    Thomas BraunT apollon77A 2 Antworten Letzte Antwort
    0
    • LausiDL LausiD

      Aktualisierung von 5.0.5 auf 5.0.6 Abbruch mit Fehler.
      Jemand eine Idee?

      host.raspberrypi
      	2023-07-04 22:21:29.848	info	[CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
      host.raspberrypi
      	2023-07-04 22:21:24.686	info	[CONTROLLER_AUTO_UPGRADE] Final information delivered
      host.raspberrypi
      	2023-07-04 22:21:24.426	error	[CONTROLLER_AUTO_UPGRADE] Could not install js-controller@5.0.6
      host.raspberrypi
      	2023-07-04 22:21:24.418	error	[CONTROLLER_AUTO_UPGRADE] npm ERR! code 128npm ERR! An unknown git error occurrednpm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/iobroker-community-adapters/ioBroker.fhem.gitnpm ERR! command-line line 0: unsupported option "accept-new".npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.npm ERR! npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehennpm ERR! und das Repository existiert.npm ERR! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2023-07-04T20_20_52_309Z-debug-0.log
      host.raspberrypi
      	2023-07-04 22:20:49.887	info	[CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
      host.raspberrypi
      	2023-07-04 22:20:49.871	info	[CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
      
      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von
      #352

      @lausid sagte in js-controller 5.0.x jetzt in der BETA:

      Jemand eine Idee?

      Auf einem raspberrypi nicht als root herumkaspern wäre die erste.
      Dann nach dem fhem-Adapter schauen, da klemmt es wohl.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      1 Antwort Letzte Antwort
      0
      • apollon77A apollon77

        Neue erkannte Probleme, die noch nicht behandelt sind:

        • stiebel-isg update nötig
        • lgtv sollte fixed sein mit 1.1.12
        • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
        • js-controller upgrade via Admin startet js-controller nicht wieder
        • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
        • km200 sollte gefixt sein mit 2.0.4
        • miio muss geprüft werden
        • fakeroku GitHub Version gefixt, release fehlt noch
        • pi-hole update nötig
        • node-red muss geprüft werden
        • enigma2.0 mindestens 1.4.0+
        • doorbird update nötig
        • linux-control update nötig
        foxriver76F Offline
        foxriver76F Offline
        foxriver76
        Developer
        schrieb am zuletzt editiert von
        #353

        @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

        Neue erkannte Probleme, die noch nicht behandelt sind:

        Ich schreibe mal meine Updates in klammern dahinter

        • stiebel-isg update nötig
        • lgtv zeigt Fehlermeldungen an (sollte fixed sein mit 1.1.12)
        • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
        • js-controller upgrade via Admin startet js-controller nicht wieder
        • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
        • km200 muss geprüft werden (sollte gefixt sein mit 2.0.4)
        • miio muss geprüft werden
        • fakeroku muss geprüft werden (git version funktioniert, benötigt publish)
        • pi-hole update nötig
        • node-red muss geprüft werden
        • enigma2.0 mindestens 1.4.0+
        • doorbird update nötig
        • linux-control update nötig

        Videotutorials & mehr

        Hier könnt ihr mich unterstützen.

        apollon77A B L 3 Antworten Letzte Antwort
        2
        • C CKassiopaia

          Jetzt melde ich mich doch mal hier zu Wort und melde einen "Fehler":

          Ich habe ein Multi-Host-System (wobei der Slave nur zu Testzwecken dabei ist) und es lässt sich leider nur der Slave auf die aktuelle JS-Controller-Version 5.0.6 installieren.

          Der Master ist ein Raspberry Pi 4 mit 8 GB. Der Slave ein alter Zotac mit 1,8 GHz Atom und 4 GB mit Debian.
          549d31bc-3178-4dcc-940b-2a5394626186-grafik.png
          Auf dem Master habe ich seit 5.0.4 kein Update mehr durchführen können. Zudem lassen sich seit dem auch keine Updates der Adapter durchführen:

          Wenn ich die Installation über Putty (direkt in Linux) durchführe kommen keine Fehlermeldungen. Die Updates der Adapter und des JS-Controller werden ohne Fehler durchgeführt... aber am Ende hat sich nichts verändert. Über die Admin-Konsole kommt folgendes:

          npm ERR! code EBADENGINE
          npm ERR! engine Unsupported engine
          npm ERR! engine Not compatible with your version of node/npm: iobroker.daikin-cloud@0.2.3
          npm ERR! notsup Not compatible with your version of node/npm: iobroker.daikin-cloud@0.2.3
          npm ERR! notsup Required: {"node":"^12.19.0 || ^14.15.0 || ^16.13.0"}
          npm ERR! notsup Actual:   {"npm":"9.5.1","node":"v18.16.1"}
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /root/.npm/_logs/2023-07-04T14_59_51_842Z-debug-0.log
          npm ERR! code EBADENGINE
          npm ERR! engine Unsupported engine
          npm ERR! engine Not compatible with your version of node/npm: iobroker.daikin-cloud@0.2.3
          npm ERR! notsup Not compatible with your version of node/npm: iobroker.daikin-cloud@0.2.3
          npm ERR! notsup Required: {"node":"^12.19.0 || ^14.15.0 || ^16.13.0"}
          npm ERR! notsup Actual:   {"npm":"9.5.1","node":"v18.16.1"}
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /root/.npm/_logs/2023-07-04T14_59_51_842Z-debug-0.log
          Could not install js-controller@5.0.6
          

          Das Problem wird also vielleicht am Daikin-Adapter liegen? Den habe ich jetzt mal deinstalliert... im Sommer ist die Wärmepumpe ohnehin aus ;)

          ... und siehe da, dann funktioniert es auch. Also nach dem Entferndn des Daikin-Adapters konnte ich den JS-Controller aktualisieren. Jetzt lassen sich auch die anderen Adapter aktualisieren.

          Also eigentlich ist dieser Post jetzt überflüssig, aber vielleicht interessiert es doch jemanden, dass via Putty keine Fehlermeldungen angezeigt wurden und der Daikin-Adapter noch nicht mit der neuen Version funktioniert.

          apollon77A Offline
          apollon77A Offline
          apollon77
          schrieb am zuletzt editiert von
          #354

          @ckassiopaia Daikin cloud von github installieren, dann ist der Fehler weg

          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
          1 Antwort Letzte Antwort
          0
          • LausiDL LausiD

            Aktualisierung von 5.0.5 auf 5.0.6 Abbruch mit Fehler.
            Jemand eine Idee?

            host.raspberrypi
            	2023-07-04 22:21:29.848	info	[CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
            host.raspberrypi
            	2023-07-04 22:21:24.686	info	[CONTROLLER_AUTO_UPGRADE] Final information delivered
            host.raspberrypi
            	2023-07-04 22:21:24.426	error	[CONTROLLER_AUTO_UPGRADE] Could not install js-controller@5.0.6
            host.raspberrypi
            	2023-07-04 22:21:24.418	error	[CONTROLLER_AUTO_UPGRADE] npm ERR! code 128npm ERR! An unknown git error occurrednpm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/iobroker-community-adapters/ioBroker.fhem.gitnpm ERR! command-line line 0: unsupported option "accept-new".npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.npm ERR! npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehennpm ERR! und das Repository existiert.npm ERR! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2023-07-04T20_20_52_309Z-debug-0.log
            host.raspberrypi
            	2023-07-04 22:20:49.887	info	[CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
            host.raspberrypi
            	2023-07-04 22:20:49.871	info	[CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
            
            apollon77A Offline
            apollon77A Offline
            apollon77
            schrieb am zuletzt editiert von
            #355

            @lausid sagte in js-controller 5.0.x jetzt in der BETA:

            unsupported option "accept-new"

            Also bei dem Fehler lande ich eher bei sowas https://serverfault.com/questions/1105812/command-line-line-0-unsupported-option-accept-new-how-to-fix-this

            Scheinbar ist da was an deiner SSH konfig verbogen? Lösungsdiskussion aber bitte in einem eigenen Thread!

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            LausiDL 1 Antwort Letzte Antwort
            0
            • foxriver76F foxriver76

              @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

              Neue erkannte Probleme, die noch nicht behandelt sind:

              Ich schreibe mal meine Updates in klammern dahinter

              • stiebel-isg update nötig
              • lgtv zeigt Fehlermeldungen an (sollte fixed sein mit 1.1.12)
              • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
              • js-controller upgrade via Admin startet js-controller nicht wieder
              • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
              • km200 muss geprüft werden (sollte gefixt sein mit 2.0.4)
              • miio muss geprüft werden
              • fakeroku muss geprüft werden (git version funktioniert, benötigt publish)
              • pi-hole update nötig
              • node-red muss geprüft werden
              • enigma2.0 mindestens 1.4.0+
              • doorbird update nötig
              • linux-control update nötig
              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #356

              @foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:

              updated

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              1 Antwort Letzte Antwort
              0
              • T ticaki

                Seit dem Update auf 5.0.x (immer aktuell) und dem installieren des Notification-Managers schickt der mir beim jedem Restart des ioBrokers freundlicherweise diese Mitteilung:

                Probleme mit der Datenbank
                
                Es liegt ein Fehler mit der Datenbank vor.
                Vielleicht hat die Datenbank interne Probleme oder ist falsch konfiguriert.
                system.host.tims-pi1:   
                s-pi1: 3.7.2023, 23:41:57
                

                Das dazu gehörige Log zeigt das es beim stoppen passiert.

                2023-07-03 23:38:26.321 - info: host.tims-pi1 instance system.adapter.influxdb.1 terminated with code 0 (NO_ERROR)
                2023-07-03 23:38:26.343 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
                2023-07-03 23:38:26.344 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at Socket.Writable.write (node:internal/streams/writable:337:10)
                2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.publish (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:817:35)
                2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: Error: DB closed
                2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Object.onceWrapper (node:events:628:26)
                2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:events:513:28)
                2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:domain:489:12)
                2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at TCP. (node:net:322:12)
                2023-07-03 23:38:26.349 - info: host.tims-pi1 instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
                2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write ECONNRESET
                2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Writable.write (node:internal/streams/writable:337:10)
                2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.evalsha (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:3105:46)
                2023-07-03 23:38:26.375 - info: host.tims-pi1 instance system.adapter.zigbee2mqtt.0 terminated with code 0 (NO_ERROR)
                2023-07-03 23:38:27.224 - info: tuya.0 (1587) terminating
                2023-07-03 23:38:27.228 - info: tuya.0 (1587) Terminated (NO_ERROR): Without reason
                2023-07-03 23:38:27.814 - info: host.tims-pi1 instance system.adapter.tuya.0 terminated with code 0 (NO_ERROR)
                2023-07-03 23:38:27.815 - info: host.tims-pi1 All instances are stopped.
                2023-07-03 23:38:27.845 - info: host.tims-pi1 terminated
                2023-07-03 23:38:31.939 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
                2023-07-03 23:38:32.123 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:443
                2023-07-03 23:39:17.791 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE]
                

                Wäre mir ohne den Manager wohl nie aufgefallen... hm vielleicht ist es auch schon immer so. :)

                EDIT: log verlängert

                apollon77A Offline
                apollon77A Offline
                apollon77
                schrieb am zuletzt editiert von
                #357

                @ticaki sagte in js-controller 5.0.x jetzt in der BETA:

                EDIT: log verlängert

                Bitte nochmal groooossszügig verlängern!! Viel zu enig - vor allem nichts vom notification adapter zu sehen dort. mach mal paar minuten inklusive kurz BEVOR du ihn restartest.

                BTW: Wie restartest du?

                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                T 1 Antwort Letzte Antwort
                0
                • apollon77A apollon77

                  @ticaki sagte in js-controller 5.0.x jetzt in der BETA:

                  EDIT: log verlängert

                  Bitte nochmal groooossszügig verlängern!! Viel zu enig - vor allem nichts vom notification adapter zu sehen dort. mach mal paar minuten inklusive kurz BEVOR du ihn restartest.

                  BTW: Wie restartest du?

                  T Nicht stören
                  T Nicht stören
                  ticaki
                  schrieb am zuletzt editiert von ticaki
                  #358

                  @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

                  @ticaki sagte in js-controller 5.0.x jetzt in der BETA:

                  EDIT: log verlängert

                  Bitte nochmal groooossszügig verlängern!! Viel zu enig - vor allem nichts vom notification adapter zu sehen dort. mach mal paar minuten inklusive kurz BEVOR du ihn restartest.

                  BTW: Wie restartest du?

                  Ich habs verlängert, weil der Fehler diesesmal durch den "Restart" der vom js-controller update erzeugt wurde. und das steht in den letzten 3 Zeilen im Log.

                  iobroker stop 
                  iobroker start
                  sudo reboot
                  

                  Das sind die üblichen Befehle. Vorhin hab ich ihn hard ausgeschaltet, weil ich blöd bin :) da kam auch die Nachricht über telegram, kann dazu aber nichts im log finden, gibts noch eine anderes log?

                  Edit: log etwas viel verlängert. 1. Eintrag ist mein Anmelden am Server

                  2023-07-03 23:37:49.026 - info: admin.0 (4902) ==> Connected system.user.admin from 192.168.178.133
                  2023-07-03 23:38:20.457 - info: host.tims-pi1 Controller will upgrade itself to version 5.0.6
                  2023-07-03 23:38:24.058 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Stopping controller
                  2023-07-03 23:38:24.169 - info: host.tims-pi1 received SIGTERM
                  2023-07-03 23:38:24.185 - info: javascript.0 (12330) Stop script script.js.common.Starte_AppleTV
                  2023-07-03 23:38:24.152 - info: yahka.0 (1673) cleaning up ...
                  2023-07-03 23:38:24.168 - info: yahka.0 (1673) cleaned up ...
                  2023-07-03 23:38:24.214 - info: yahka.0 (1673) terminating
                  2023-07-03 23:38:24.216 - info: yahka.0 (1673) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.201 - error: mihome-vacuum.0 (1609) Socket Close
                  2023-07-03 23:38:24.184 - info: admin.0 (4902) terminating https server on port 443
                  2023-07-03 23:38:24.251 - info: mihome-vacuum.0 (1609) terminating
                  2023-07-03 23:38:24.184 - info: homepilot20.0 (1818) terminating homepilot20 adapter
                  2023-07-03 23:38:24.188 - error: homepilot20.0 (1818) Adapter will be stopped
                  2023-07-03 23:38:24.262 - info: homepilot20.0 (1818) terminating
                  2023-07-03 23:38:24.227 - info: notification-manager.0 (1658) terminating
                  2023-07-03 23:38:24.230 - info: notification-manager.0 (1658) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.269 - info: mihome-vacuum.0 (1609) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.186 - info: javascript.0 (12330) Stop script script.js.common.Haustürautomatik_BWMlicht
                  2023-07-03 23:38:24.188 - info: javascript.0 (12330) Stop script script.js.common.Schlafenszeit_&_Nachmodus
                  2023-07-03 23:38:24.189 - info: javascript.0 (12330) Stop script script.js.Messages.tankerkoenig
                  2023-07-03 23:38:24.190 - info: javascript.0 (12330) Stop script script.js.common.Anyone_&_Calc_humi_&_frostig
                  2023-07-03 23:38:24.191 - info: javascript.0 (12330) Stop script script.js.common.rollandensteuerung_Schlafzimmer
                  2023-07-03 23:38:24.192 - info: javascript.0 (12330) Stop script script.js.Test.Fill_SQL
                  2023-07-03 23:38:24.203 - info: javascript.0 (12330) Stop script script.js.common.StatusLights
                  2023-07-03 23:38:24.205 - info: javascript.0 (12330) Stop script script.js.Messages.dwd_uwz_nina_script
                  2023-07-03 23:38:24.207 - info: javascript.0 (12330) script.js.Messages.dwd_uwz_nina_script: info: Skripts gestoppt: ID:3827.050695965306
                  2023-07-03 23:38:24.209 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Luftbefeuchter
                  2023-07-03 23:38:24.210 - info: javascript.0 (12330) Stop script script.js.Wohnzimmer.1_Hue_Dimmer_Switch
                  2023-07-03 23:38:24.211 - info: javascript.0 (12330) Stop script script.js.common.check_internet_connection
                  2023-07-03 23:38:24.212 - info: javascript.0 (12330) Stop script script.js.Messages.Telegramm
                  2023-07-03 23:38:24.213 - info: javascript.0 (12330) Stop script script.js.common.comingHome_&_Steckdosen
                  2023-07-03 23:38:24.221 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Treppenhausautomatik
                  2023-07-03 23:38:24.222 - info: javascript.0 (12330) Stop script script.js.Test.Solcast
                  2023-07-03 23:38:24.223 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Climacontrol
                  2023-07-03 23:38:24.224 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Shelly_Schlafzimmer_Licht
                  2023-07-03 23:38:24.225 - info: javascript.0 (12330) Stop script script.js.Test.Skript_3
                  2023-07-03 23:38:24.226 - info: javascript.0 (12330) Stop script script.js.common.Saugroboter
                  2023-07-03 23:38:24.227 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Kontrollzentrum
                  2023-07-03 23:38:24.228 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Heizung
                  2023-07-03 23:38:24.229 - info: javascript.0 (12330) Stop script script.js.common.mqtt_datentransfer
                  2023-07-03 23:38:24.230 - info: javascript.0 (12330) Stop script script.js.Messages.Battery
                  2023-07-03 23:38:24.231 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Küche-bwm
                  2023-07-03 23:38:24.231 - info: javascript.0 (12330) Stop script script.js.Wohnzimmer.calculateTempForLivingRoom
                  2023-07-03 23:38:24.232 - info: javascript.0 (12330) Stop script script.js.common.Wecker-Sunrise
                  2023-07-03 23:38:24.233 - info: javascript.0 (12330) Stop script script.js.Messages.Telegram-Handler
                  2023-07-03 23:38:24.233 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Virtuelle_Light_on-off_0%-100%_brightness
                  2023-07-03 23:38:24.234 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Flursteuerung
                  2023-07-03 23:38:24.235 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Ankleidezimmer_Beleuchtung
                  2023-07-03 23:38:24.236 - info: javascript.0 (12330) Stop script script.js.common.Solarstrom
                  2023-07-03 23:38:24.198 - info: hm-rpc.0 (1557) xmlrpc -> 192.168.178.95:42001/ init ["http://192.168.178.96:42001",""]
                  2023-07-03 23:38:24.191 - info: sma-em.0 (23059) cleaned everything up...
                  2023-07-03 23:38:24.266 - info: sma-em.0 (23059) UDP Socket closed ...
                  2023-07-03 23:38:24.298 - info: sma-em.0 (23059) terminating
                  2023-07-03 23:38:24.300 - info: sma-em.0 (23059) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.304 - info: homepilot20.0 (1818) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.308 - info: hm-rpc.0 (1557) Disconnected
                  2023-07-03 23:38:24.310 - warn: zigbee2mqtt.0 (4233) Start try again in 1 seconds...
                  2023-07-03 23:38:24.319 - info: hm-rpc.0 (1557) terminating
                  2023-07-03 23:38:24.276 - info: fritzdect.0 (1765) cleaned everything up...
                  2023-07-03 23:38:24.324 - info: hm-rpc.0 (1557) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.227 - info: email.0 (1291) terminating
                  2023-07-03 23:38:24.232 - info: email.0 (1291) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.166 - info: backitup.0 (1784) cleaned everything up...
                  2023-07-03 23:38:24.196 - info: yahka.1 (30056) cleaning up ...
                  2023-07-03 23:38:24.200 - info: yahka.1 (30056) cleaned up ...
                  2023-07-03 23:38:24.233 - info: mqtt.0 (11274) Disconnected from 192.168.178.96: undefined
                  2023-07-03 23:38:24.343 - info: yahka.1 (30056) terminating
                  2023-07-03 23:38:24.348 - info: javascript.0 (12330) terminating
                  2023-07-03 23:38:24.365 - info: admin.0 (4902) terminating
                  2023-07-03 23:38:24.368 - info: admin.0 (4902) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.393 - info: fritzdect.0 (1765) terminating
                  2023-07-03 23:38:24.395 - info: fritzdect.0 (1765) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.332 - info: backitup.0 (1784) terminating
                  2023-07-03 23:38:24.221 - info: sql.0 (1362) terminating
                  2023-07-03 23:38:24.349 - info: sql.0 (1362) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.363 - info: javascript.0 (12330) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.345 - info: yahka.1 (30056) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.405 - info: backitup.0 (1784) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.205 - info: host.tims-pi1 stopInstance system.adapter.admin.0 (force=false, process=true)
                  2023-07-03 23:38:24.206 - info: host.tims-pi1 stopInstance system.adapter.pushover.0 (force=false, process=true)
                  2023-07-03 23:38:24.207 - info: host.tims-pi1 stopInstance system.adapter.email.0 (force=false, process=true)
                  2023-07-03 23:38:24.208 - info: host.tims-pi1 stopInstance system.adapter.telegram.0 (force=false, process=true)
                  2023-07-03 23:38:24.209 - info: host.tims-pi1 stopInstance system.adapter.influxdb.1 (force=false, process=true)
                  2023-07-03 23:38:24.210 - info: host.tims-pi1 stopInstance system.adapter.javascript.0 (force=false, process=true)
                  2023-07-03 23:38:24.211 - info: host.tims-pi1 stopInstance system.adapter.sql.0 (force=false, process=true)
                  2023-07-03 23:38:24.212 - info: host.tims-pi1 stopInstance system.adapter.hm-rega.0 (force=false, process=true)
                  2023-07-03 23:38:24.213 - info: host.tims-pi1 stopInstance system.adapter.rpi2.0 (force=false, process=true)
                  2023-07-03 23:38:24.277 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 (force=false, process=true)
                  2023-07-03 23:38:24.278 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
                  2023-07-03 23:38:24.280 - info: host.tims-pi1 stopInstance system.adapter.sonoff.0 (force=false, process=true)
                  2023-07-03 23:38:24.281 - info: host.tims-pi1 stopInstance system.adapter.alexa2.0 (force=false, process=true)
                  2023-07-03 23:38:24.282 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
                  2023-07-03 23:38:24.282 - info: host.tims-pi1 stopInstance system.adapter.openweathermap.0 (force=false, process=false)
                  2023-07-03 23:38:24.331 - info: host.tims-pi1 stopInstance canceled schedule system.adapter.openweathermap.0
                  2023-07-03 23:38:24.332 - info: host.tims-pi1 stopInstance system.adapter.tuya.0 (force=false, process=true)
                  2023-07-03 23:38:24.333 - info: host.tims-pi1 stopInstance system.adapter.modbus.0 (force=false, process=false)
                  2023-07-03 23:38:24.333 - info: host.tims-pi1 stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                  2023-07-03 23:38:24.334 - info: host.tims-pi1 stopInstance system.adapter.daikin.0 (force=false, process=true)
                  2023-07-03 23:38:24.335 - info: host.tims-pi1 stopInstance system.adapter.mqtt.0 (force=false, process=true)
                  2023-07-03 23:38:24.336 - info: host.tims-pi1 stopInstance system.adapter.notification-manager.0 (force=false, process=true)
                  2023-07-03 23:38:24.337 - info: host.tims-pi1 stopInstance system.adapter.yahka.0 (force=false, process=true)
                  2023-07-03 23:38:24.337 - info: host.tims-pi1 stopInstance system.adapter.hyperion_ng.0 (force=false, process=false)
                  2023-07-03 23:38:24.338 - info: host.tims-pi1 stopInstance system.adapter.nuki.0 (force=false, process=true)
                  2023-07-03 23:38:24.339 - info: host.tims-pi1 stopInstance system.adapter.discovery.0 (force=false, process=true)
                  2023-07-03 23:38:24.354 - info: host.tims-pi1 stopInstance system.adapter.fritzdect.0 (force=false, process=true)
                  2023-07-03 23:38:24.359 - info: host.tims-pi1 stopInstance system.adapter.backitup.0 (force=false, process=true)
                  2023-07-03 23:38:24.360 - info: host.tims-pi1 stopInstance system.adapter.iot.0 (force=false, process=true)
                  2023-07-03 23:38:24.361 - info: host.tims-pi1 stopInstance system.adapter.wled.0 (force=false, process=true)
                  2023-07-03 23:38:24.362 - info: host.tims-pi1 stopInstance system.adapter.homepilot20.0 (force=false, process=true)
                  2023-07-03 23:38:24.383 - info: host.tims-pi1 stopInstance system.adapter.zigbee2mqtt.0 (force=false, process=true)
                  2023-07-03 23:38:24.384 - info: host.tims-pi1 stopInstance system.adapter.info.0 (force=false, process=true)
                  2023-07-03 23:38:24.385 - info: host.tims-pi1 stopInstance system.adapter.sma-em.0 (force=false, process=true)
                  2023-07-03 23:38:24.385 - info: host.tims-pi1 stopInstance system.adapter.web.0 (force=false, process=true)
                  2023-07-03 23:38:24.386 - info: host.tims-pi1 stopInstance system.adapter.yahka.1 (force=false, process=true)
                  2023-07-03 23:38:24.387 - info: host.tims-pi1 stopInstance system.adapter.vis.0 (force=false, process=false)
                  2023-07-03 23:38:24.440 - info: sonoff.0 (1527) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.437 - info: javascript.0 (12330) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.443 - info: hm-rpc.0 (1557) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.444 - info: fritzdect.0 (1765) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.445 - info: yahka.0 (1673) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.443 - info: backitup.0 (1784) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.447 - info: notification-manager.0 (1658) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.449 - info: mqtt.0 (11274) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.449 - info: admin.0 (4902) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.464 - info: mihome-vacuum.0 (1609) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.444 - info: email.0 (1291) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.438 - info: pushover.0 (1208) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.485 - info: host.tims-pi1 stopInstance system.adapter.admin.0 send kill signal
                  2023-07-03 23:38:24.489 - info: yahka.1 (30056) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.491 - info: zigbee2mqtt.0 (4233) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.490 - info: sma-em.0 (23059) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.492 - info: homepilot20.0 (1818) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.443 - info: telegram.0 (25742) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.451 - info: tuya.0 (1587) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.488 - info: host.tims-pi1 stopInstance system.adapter.pushover.0 send kill signal
                  2023-07-03 23:38:24.495 - info: host.tims-pi1 stopInstance system.adapter.email.0 send kill signal
                  2023-07-03 23:38:24.496 - info: host.tims-pi1 stopInstance system.adapter.telegram.0 send kill signal
                  2023-07-03 23:38:24.496 - info: host.tims-pi1 stopInstance system.adapter.javascript.0 send kill signal
                  2023-07-03 23:38:24.502 - info: host.tims-pi1 stopInstance system.adapter.hm-rega.0 send kill signal
                  2023-07-03 23:38:24.503 - info: host.tims-pi1 stopInstance system.adapter.rpi2.0 send kill signal
                  2023-07-03 23:38:24.508 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 send kill signal
                  2023-07-03 23:38:24.509 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.1 send kill signal
                  2023-07-03 23:38:24.510 - info: host.tims-pi1 stopInstance system.adapter.sonoff.0 send kill signal
                  2023-07-03 23:38:24.510 - info: host.tims-pi1 stopInstance system.adapter.alexa2.0 send kill signal
                  2023-07-03 23:38:24.511 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.0 send kill signal
                  2023-07-03 23:38:24.511 - info: host.tims-pi1 stopInstance system.adapter.tuya.0 send kill signal
                  2023-07-03 23:38:24.512 - info: host.tims-pi1 stopInstance system.adapter.mihome-vacuum.0 send kill signal
                  2023-07-03 23:38:24.512 - info: host.tims-pi1 stopInstance system.adapter.daikin.0 send kill signal
                  2023-07-03 23:38:24.513 - info: host.tims-pi1 stopInstance system.adapter.mqtt.0 send kill signal
                  2023-07-03 23:38:24.514 - info: host.tims-pi1 stopInstance system.adapter.notification-manager.0 send kill signal
                  2023-07-03 23:38:24.515 - info: host.tims-pi1 stopInstance system.adapter.yahka.0 send kill signal
                  2023-07-03 23:38:24.516 - info: host.tims-pi1 stopInstance system.adapter.nuki.0 send kill signal
                  2023-07-03 23:38:24.517 - info: host.tims-pi1 stopInstance system.adapter.discovery.0 send kill signal
                  2023-07-03 23:38:24.517 - info: host.tims-pi1 stopInstance system.adapter.fritzdect.0 send kill signal
                  2023-07-03 23:38:24.518 - info: host.tims-pi1 stopInstance system.adapter.backitup.0 send kill signal
                  2023-07-03 23:38:24.518 - info: host.tims-pi1 stopInstance system.adapter.iot.0 send kill signal
                  2023-07-03 23:38:24.519 - info: host.tims-pi1 stopInstance system.adapter.wled.0 send kill signal
                  2023-07-03 23:38:24.530 - info: host.tims-pi1 stopInstance system.adapter.homepilot20.0 send kill signal
                  2023-07-03 23:38:24.531 - info: host.tims-pi1 stopInstance system.adapter.zigbee2mqtt.0 send kill signal
                  2023-07-03 23:38:24.532 - info: host.tims-pi1 stopInstance system.adapter.info.0 send kill signal
                  2023-07-03 23:38:24.532 - info: host.tims-pi1 stopInstance system.adapter.sma-em.0 send kill signal
                  2023-07-03 23:38:24.533 - info: host.tims-pi1 stopInstance system.adapter.web.0 send kill signal
                  2023-07-03 23:38:24.533 - info: host.tims-pi1 stopInstance system.adapter.yahka.1 send kill signal
                  2023-07-03 23:38:24.419 - info: hm-rega.0 (1382) terminating
                  2023-07-03 23:38:24.433 - info: hm-rega.0 (1382) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.550 - info: hm-rega.0 (1382) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.341 - info: iot.0 (1796) Connection changed: disconnect
                  2023-07-03 23:38:24.558 - info: iot.0 (1796) Connection lost
                  2023-07-03 23:38:24.244 - info: rpi2.0 (1431) terminating
                  2023-07-03 23:38:24.493 - info: rpi2.0 (1431) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.253 - info: discovery.0 (1717) terminating
                  2023-07-03 23:38:24.465 - info: discovery.0 (1717) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.572 - info: iot.0 (1796) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.148 - info: hm-rpc.1 (1512) xmlrpc -> 192.168.178.95:42010/ init ["http://192.168.178.96:42010",""]
                  2023-07-03 23:38:24.576 - info: iot.0 (1796) terminating
                  2023-07-03 23:38:24.579 - info: iot.0 (1796) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.271 - info: alexa2.0 (1542) terminating
                  2023-07-03 23:38:24.439 - info: alexa2.0 (1542) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.162 - info: daikin.0 (1624) terminating
                  2023-07-03 23:38:24.456 - info: daikin.0 (1624) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.581 - info: rpi2.0 (1431) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.586 - info: alexa2.0 (1542) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.579 - info: hm-rpc.1 (1512) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.594 - info: discovery.0 (1717) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.591 - info: daikin.0 (1624) Got terminate signal TERMINATE_YOURSELF
                  2023-07-03 23:38:24.621 - info: hm-rpc.1 (1512) Disconnected
                  2023-07-03 23:38:24.631 - info: hm-rpc.1 (1512) terminating
                  2023-07-03 23:38:24.634 - info: hm-rpc.1 (1512) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.650 - info: email.0 (1291) terminating
                  2023-07-03 23:38:24.664 - info: daikin.0 (1624) terminating
                  2023-07-03 23:38:24.673 - info: yahka.0 (1673) terminating
                  2023-07-03 23:38:24.680 - info: telegram.0 (25742) terminating
                  2023-07-03 23:38:24.679 - warn: influxdb.1 (8576) Store data for 324 points and 0 conflicts
                  2023-07-03 23:38:24.685 - info: sonoff.0 (1527) terminating
                  2023-07-03 23:38:24.688 - info: sonoff.0 (1527) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.686 - info: iot.0 (1796) terminating
                  2023-07-03 23:38:24.688 - info: javascript.0 (12330) terminating
                  2023-07-03 23:38:24.695 - info: homepilot20.0 (1818) terminating
                  2023-07-03 23:38:24.692 - info: telegram.0 (25742) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.699 - info: mihome-vacuum.0 (1609) terminating
                  2023-07-03 23:38:24.706 - info: notification-manager.0 (1658) terminating
                  2023-07-03 23:38:24.715 - info: discovery.0 (1717) terminating
                  2023-07-03 23:38:24.717 - info: mqtt.0 (11274) terminating
                  2023-07-03 23:38:24.722 - info: hm-rega.0 (1382) terminating
                  2023-07-03 23:38:24.721 - info: mqtt.0 (11274) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.724 - info: alexa2.0 (1542) terminating
                  2023-07-03 23:38:24.720 - info: pushover.0 (1208) terminating
                  2023-07-03 23:38:24.728 - info: rpi2.0 (1431) terminating
                  2023-07-03 23:38:24.731 - info: pushover.0 (1208) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:24.767 - info: sma-em.0 (23059) terminating
                  2023-07-03 23:38:24.769 - info: yahka.1 (30056) terminating
                  2023-07-03 23:38:24.803 - info: backitup.0 (1784) terminating
                  2023-07-03 23:38:24.832 - info: fritzdect.0 (1765) terminating
                  2023-07-03 23:38:24.835 - info: admin.0 (4902) terminating
                  2023-07-03 23:38:24.929 - info: host.tims-pi1 instance system.adapter.nuki.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.173 - info: host.tims-pi1 instance system.adapter.email.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.184 - error: shelly.0 (12292) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                  2023-07-03 23:38:25.210 - error: shelly.0 (12292) unhandled promise rejection: DB closed
                  2023-07-03 23:38:25.213 - error: shelly.0 (12292) Error: DB closed
                  at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                  at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                  at Object.onceWrapper (node:events:628:26)
                  at Socket.emit (node:events:513:28)
                  at Socket.emit (node:domain:489:12)
                  at TCP. (node:net:322:12)
                  2023-07-03 23:38:25.214 - error: shelly.0 (12292) DB closed
                  2023-07-03 23:38:25.322 - info: zigbee2mqtt.0 (4233) Connect to Zigbee2MQTT over websocket connection.
                  2023-07-03 23:38:25.174 - info: host.tims-pi1 instance system.adapter.notification-manager.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.388 - info: host.tims-pi1 instance system.adapter.yahka.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.390 - info: host.tims-pi1 instance system.adapter.web.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.393 - info: host.tims-pi1 instance system.adapter.sma-em.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.544 - info: host.tims-pi1 instance system.adapter.sql.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.545 - info: host.tims-pi1 instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.546 - info: host.tims-pi1 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.548 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 killing pid 12292
                  2023-07-03 23:38:25.661 - info: zigbee2mqtt.0 (4233) terminating
                  2023-07-03 23:38:25.662 - info: zigbee2mqtt.0 (4233) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:25.674 - info: host.tims-pi1 instance system.adapter.mihome-vacuum.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.675 - info: host.tims-pi1 instance system.adapter.fritzdect.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.675 - info: host.tims-pi1 instance system.adapter.wled.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.812 - info: host.tims-pi1 instance system.adapter.homepilot20.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.813 - info: host.tims-pi1 instance system.adapter.info.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.815 - info: host.tims-pi1 instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.920 - info: host.tims-pi1 instance system.adapter.yahka.1 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.922 - info: host.tims-pi1 instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.922 - info: host.tims-pi1 instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:25.948 - info: host.tims-pi1 instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.017 - info: host.tims-pi1 instance system.adapter.pushover.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.051 - info: host.tims-pi1 instance system.adapter.hm-rega.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.116 - info: host.tims-pi1 instance system.adapter.rpi2.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.196 - info: zigbee2mqtt.0 (4233) terminating
                  2023-07-03 23:38:26.198 - warn: zigbee2mqtt.0 (4233) Cannot get view: Connection is closed.
                  2023-07-03 23:38:26.198 - warn: zigbee2mqtt.0 (4233) Cannot get view: Connection is closed.
                  2023-07-03 23:38:26.117 - info: host.tims-pi1 instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.227 - info: host.tims-pi1 instance system.adapter.sonoff.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.228 - info: host.tims-pi1 instance system.adapter.daikin.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.229 - info: host.tims-pi1 instance system.adapter.iot.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.319 - info: host.tims-pi1 instance system.adapter.mqtt.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.320 - info: host.tims-pi1 instance system.adapter.telegram.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.321 - info: host.tims-pi1 instance system.adapter.influxdb.1 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.343 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
                  2023-07-03 23:38:26.344 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                  2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                  2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                  2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                  2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                  2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                  2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at Socket.Writable.write (node:internal/streams/writable:337:10)
                  2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                  2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.publish (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:817:35)
                  2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                  2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: Error: DB closed
                  2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                  2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                  2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Object.onceWrapper (node:events:628:26)
                  2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:events:513:28)
                  2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:domain:489:12)
                  2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at TCP. (node:net:322:12)
                  2023-07-03 23:38:26.349 - info: host.tims-pi1 instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write ECONNRESET
                  2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                  2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Writable.write (node:internal/streams/writable:337:10)
                  2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                  2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.evalsha (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:3105:46)
                  2023-07-03 23:38:26.375 - info: host.tims-pi1 instance system.adapter.zigbee2mqtt.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:27.224 - info: tuya.0 (1587) terminating
                  2023-07-03 23:38:27.228 - info: tuya.0 (1587) Terminated (NO_ERROR): Without reason
                  2023-07-03 23:38:27.814 - info: host.tims-pi1 instance system.adapter.tuya.0 terminated with code 0 (NO_ERROR)
                  2023-07-03 23:38:27.815 - info: host.tims-pi1 All instances are stopped.
                  2023-07-03 23:38:27.845 - info: host.tims-pi1 terminated
                  2023-07-03 23:38:31.939 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
                  2023-07-03 23:38:32.123 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:443
                  2023-07-03 23:39:17.791 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE]
                  removed 97 packages, and changed 16 packages in 45s
                  143 packages are looking for funding
                  

                  Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                  Spenden

                  apollon77A 1 Antwort Letzte Antwort
                  0
                  • T ticaki

                    @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

                    @ticaki sagte in js-controller 5.0.x jetzt in der BETA:

                    EDIT: log verlängert

                    Bitte nochmal groooossszügig verlängern!! Viel zu enig - vor allem nichts vom notification adapter zu sehen dort. mach mal paar minuten inklusive kurz BEVOR du ihn restartest.

                    BTW: Wie restartest du?

                    Ich habs verlängert, weil der Fehler diesesmal durch den "Restart" der vom js-controller update erzeugt wurde. und das steht in den letzten 3 Zeilen im Log.

                    iobroker stop 
                    iobroker start
                    sudo reboot
                    

                    Das sind die üblichen Befehle. Vorhin hab ich ihn hard ausgeschaltet, weil ich blöd bin :) da kam auch die Nachricht über telegram, kann dazu aber nichts im log finden, gibts noch eine anderes log?

                    Edit: log etwas viel verlängert. 1. Eintrag ist mein Anmelden am Server

                    2023-07-03 23:37:49.026 - info: admin.0 (4902) ==> Connected system.user.admin from 192.168.178.133
                    2023-07-03 23:38:20.457 - info: host.tims-pi1 Controller will upgrade itself to version 5.0.6
                    2023-07-03 23:38:24.058 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Stopping controller
                    2023-07-03 23:38:24.169 - info: host.tims-pi1 received SIGTERM
                    2023-07-03 23:38:24.185 - info: javascript.0 (12330) Stop script script.js.common.Starte_AppleTV
                    2023-07-03 23:38:24.152 - info: yahka.0 (1673) cleaning up ...
                    2023-07-03 23:38:24.168 - info: yahka.0 (1673) cleaned up ...
                    2023-07-03 23:38:24.214 - info: yahka.0 (1673) terminating
                    2023-07-03 23:38:24.216 - info: yahka.0 (1673) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.201 - error: mihome-vacuum.0 (1609) Socket Close
                    2023-07-03 23:38:24.184 - info: admin.0 (4902) terminating https server on port 443
                    2023-07-03 23:38:24.251 - info: mihome-vacuum.0 (1609) terminating
                    2023-07-03 23:38:24.184 - info: homepilot20.0 (1818) terminating homepilot20 adapter
                    2023-07-03 23:38:24.188 - error: homepilot20.0 (1818) Adapter will be stopped
                    2023-07-03 23:38:24.262 - info: homepilot20.0 (1818) terminating
                    2023-07-03 23:38:24.227 - info: notification-manager.0 (1658) terminating
                    2023-07-03 23:38:24.230 - info: notification-manager.0 (1658) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.269 - info: mihome-vacuum.0 (1609) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.186 - info: javascript.0 (12330) Stop script script.js.common.Haustürautomatik_BWMlicht
                    2023-07-03 23:38:24.188 - info: javascript.0 (12330) Stop script script.js.common.Schlafenszeit_&_Nachmodus
                    2023-07-03 23:38:24.189 - info: javascript.0 (12330) Stop script script.js.Messages.tankerkoenig
                    2023-07-03 23:38:24.190 - info: javascript.0 (12330) Stop script script.js.common.Anyone_&_Calc_humi_&_frostig
                    2023-07-03 23:38:24.191 - info: javascript.0 (12330) Stop script script.js.common.rollandensteuerung_Schlafzimmer
                    2023-07-03 23:38:24.192 - info: javascript.0 (12330) Stop script script.js.Test.Fill_SQL
                    2023-07-03 23:38:24.203 - info: javascript.0 (12330) Stop script script.js.common.StatusLights
                    2023-07-03 23:38:24.205 - info: javascript.0 (12330) Stop script script.js.Messages.dwd_uwz_nina_script
                    2023-07-03 23:38:24.207 - info: javascript.0 (12330) script.js.Messages.dwd_uwz_nina_script: info: Skripts gestoppt: ID:3827.050695965306
                    2023-07-03 23:38:24.209 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Luftbefeuchter
                    2023-07-03 23:38:24.210 - info: javascript.0 (12330) Stop script script.js.Wohnzimmer.1_Hue_Dimmer_Switch
                    2023-07-03 23:38:24.211 - info: javascript.0 (12330) Stop script script.js.common.check_internet_connection
                    2023-07-03 23:38:24.212 - info: javascript.0 (12330) Stop script script.js.Messages.Telegramm
                    2023-07-03 23:38:24.213 - info: javascript.0 (12330) Stop script script.js.common.comingHome_&_Steckdosen
                    2023-07-03 23:38:24.221 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Treppenhausautomatik
                    2023-07-03 23:38:24.222 - info: javascript.0 (12330) Stop script script.js.Test.Solcast
                    2023-07-03 23:38:24.223 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Climacontrol
                    2023-07-03 23:38:24.224 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Shelly_Schlafzimmer_Licht
                    2023-07-03 23:38:24.225 - info: javascript.0 (12330) Stop script script.js.Test.Skript_3
                    2023-07-03 23:38:24.226 - info: javascript.0 (12330) Stop script script.js.common.Saugroboter
                    2023-07-03 23:38:24.227 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Kontrollzentrum
                    2023-07-03 23:38:24.228 - info: javascript.0 (12330) Stop script script.js.Verwaltung.Heizung
                    2023-07-03 23:38:24.229 - info: javascript.0 (12330) Stop script script.js.common.mqtt_datentransfer
                    2023-07-03 23:38:24.230 - info: javascript.0 (12330) Stop script script.js.Messages.Battery
                    2023-07-03 23:38:24.231 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Küche-bwm
                    2023-07-03 23:38:24.231 - info: javascript.0 (12330) Stop script script.js.Wohnzimmer.calculateTempForLivingRoom
                    2023-07-03 23:38:24.232 - info: javascript.0 (12330) Stop script script.js.common.Wecker-Sunrise
                    2023-07-03 23:38:24.233 - info: javascript.0 (12330) Stop script script.js.Messages.Telegram-Handler
                    2023-07-03 23:38:24.233 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Virtuelle_Light_on-off_0%-100%_brightness
                    2023-07-03 23:38:24.234 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Flursteuerung
                    2023-07-03 23:38:24.235 - info: javascript.0 (12330) Stop script script.js.Beleuchtung_(mehrere_Räume).Ankleidezimmer_Beleuchtung
                    2023-07-03 23:38:24.236 - info: javascript.0 (12330) Stop script script.js.common.Solarstrom
                    2023-07-03 23:38:24.198 - info: hm-rpc.0 (1557) xmlrpc -> 192.168.178.95:42001/ init ["http://192.168.178.96:42001",""]
                    2023-07-03 23:38:24.191 - info: sma-em.0 (23059) cleaned everything up...
                    2023-07-03 23:38:24.266 - info: sma-em.0 (23059) UDP Socket closed ...
                    2023-07-03 23:38:24.298 - info: sma-em.0 (23059) terminating
                    2023-07-03 23:38:24.300 - info: sma-em.0 (23059) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.304 - info: homepilot20.0 (1818) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.308 - info: hm-rpc.0 (1557) Disconnected
                    2023-07-03 23:38:24.310 - warn: zigbee2mqtt.0 (4233) Start try again in 1 seconds...
                    2023-07-03 23:38:24.319 - info: hm-rpc.0 (1557) terminating
                    2023-07-03 23:38:24.276 - info: fritzdect.0 (1765) cleaned everything up...
                    2023-07-03 23:38:24.324 - info: hm-rpc.0 (1557) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.227 - info: email.0 (1291) terminating
                    2023-07-03 23:38:24.232 - info: email.0 (1291) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.166 - info: backitup.0 (1784) cleaned everything up...
                    2023-07-03 23:38:24.196 - info: yahka.1 (30056) cleaning up ...
                    2023-07-03 23:38:24.200 - info: yahka.1 (30056) cleaned up ...
                    2023-07-03 23:38:24.233 - info: mqtt.0 (11274) Disconnected from 192.168.178.96: undefined
                    2023-07-03 23:38:24.343 - info: yahka.1 (30056) terminating
                    2023-07-03 23:38:24.348 - info: javascript.0 (12330) terminating
                    2023-07-03 23:38:24.365 - info: admin.0 (4902) terminating
                    2023-07-03 23:38:24.368 - info: admin.0 (4902) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.393 - info: fritzdect.0 (1765) terminating
                    2023-07-03 23:38:24.395 - info: fritzdect.0 (1765) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.332 - info: backitup.0 (1784) terminating
                    2023-07-03 23:38:24.221 - info: sql.0 (1362) terminating
                    2023-07-03 23:38:24.349 - info: sql.0 (1362) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.363 - info: javascript.0 (12330) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.345 - info: yahka.1 (30056) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.405 - info: backitup.0 (1784) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.205 - info: host.tims-pi1 stopInstance system.adapter.admin.0 (force=false, process=true)
                    2023-07-03 23:38:24.206 - info: host.tims-pi1 stopInstance system.adapter.pushover.0 (force=false, process=true)
                    2023-07-03 23:38:24.207 - info: host.tims-pi1 stopInstance system.adapter.email.0 (force=false, process=true)
                    2023-07-03 23:38:24.208 - info: host.tims-pi1 stopInstance system.adapter.telegram.0 (force=false, process=true)
                    2023-07-03 23:38:24.209 - info: host.tims-pi1 stopInstance system.adapter.influxdb.1 (force=false, process=true)
                    2023-07-03 23:38:24.210 - info: host.tims-pi1 stopInstance system.adapter.javascript.0 (force=false, process=true)
                    2023-07-03 23:38:24.211 - info: host.tims-pi1 stopInstance system.adapter.sql.0 (force=false, process=true)
                    2023-07-03 23:38:24.212 - info: host.tims-pi1 stopInstance system.adapter.hm-rega.0 (force=false, process=true)
                    2023-07-03 23:38:24.213 - info: host.tims-pi1 stopInstance system.adapter.rpi2.0 (force=false, process=true)
                    2023-07-03 23:38:24.277 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 (force=false, process=true)
                    2023-07-03 23:38:24.278 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
                    2023-07-03 23:38:24.280 - info: host.tims-pi1 stopInstance system.adapter.sonoff.0 (force=false, process=true)
                    2023-07-03 23:38:24.281 - info: host.tims-pi1 stopInstance system.adapter.alexa2.0 (force=false, process=true)
                    2023-07-03 23:38:24.282 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
                    2023-07-03 23:38:24.282 - info: host.tims-pi1 stopInstance system.adapter.openweathermap.0 (force=false, process=false)
                    2023-07-03 23:38:24.331 - info: host.tims-pi1 stopInstance canceled schedule system.adapter.openweathermap.0
                    2023-07-03 23:38:24.332 - info: host.tims-pi1 stopInstance system.adapter.tuya.0 (force=false, process=true)
                    2023-07-03 23:38:24.333 - info: host.tims-pi1 stopInstance system.adapter.modbus.0 (force=false, process=false)
                    2023-07-03 23:38:24.333 - info: host.tims-pi1 stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                    2023-07-03 23:38:24.334 - info: host.tims-pi1 stopInstance system.adapter.daikin.0 (force=false, process=true)
                    2023-07-03 23:38:24.335 - info: host.tims-pi1 stopInstance system.adapter.mqtt.0 (force=false, process=true)
                    2023-07-03 23:38:24.336 - info: host.tims-pi1 stopInstance system.adapter.notification-manager.0 (force=false, process=true)
                    2023-07-03 23:38:24.337 - info: host.tims-pi1 stopInstance system.adapter.yahka.0 (force=false, process=true)
                    2023-07-03 23:38:24.337 - info: host.tims-pi1 stopInstance system.adapter.hyperion_ng.0 (force=false, process=false)
                    2023-07-03 23:38:24.338 - info: host.tims-pi1 stopInstance system.adapter.nuki.0 (force=false, process=true)
                    2023-07-03 23:38:24.339 - info: host.tims-pi1 stopInstance system.adapter.discovery.0 (force=false, process=true)
                    2023-07-03 23:38:24.354 - info: host.tims-pi1 stopInstance system.adapter.fritzdect.0 (force=false, process=true)
                    2023-07-03 23:38:24.359 - info: host.tims-pi1 stopInstance system.adapter.backitup.0 (force=false, process=true)
                    2023-07-03 23:38:24.360 - info: host.tims-pi1 stopInstance system.adapter.iot.0 (force=false, process=true)
                    2023-07-03 23:38:24.361 - info: host.tims-pi1 stopInstance system.adapter.wled.0 (force=false, process=true)
                    2023-07-03 23:38:24.362 - info: host.tims-pi1 stopInstance system.adapter.homepilot20.0 (force=false, process=true)
                    2023-07-03 23:38:24.383 - info: host.tims-pi1 stopInstance system.adapter.zigbee2mqtt.0 (force=false, process=true)
                    2023-07-03 23:38:24.384 - info: host.tims-pi1 stopInstance system.adapter.info.0 (force=false, process=true)
                    2023-07-03 23:38:24.385 - info: host.tims-pi1 stopInstance system.adapter.sma-em.0 (force=false, process=true)
                    2023-07-03 23:38:24.385 - info: host.tims-pi1 stopInstance system.adapter.web.0 (force=false, process=true)
                    2023-07-03 23:38:24.386 - info: host.tims-pi1 stopInstance system.adapter.yahka.1 (force=false, process=true)
                    2023-07-03 23:38:24.387 - info: host.tims-pi1 stopInstance system.adapter.vis.0 (force=false, process=false)
                    2023-07-03 23:38:24.440 - info: sonoff.0 (1527) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.437 - info: javascript.0 (12330) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.443 - info: hm-rpc.0 (1557) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.444 - info: fritzdect.0 (1765) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.445 - info: yahka.0 (1673) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.443 - info: backitup.0 (1784) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.447 - info: notification-manager.0 (1658) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.449 - info: mqtt.0 (11274) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.449 - info: admin.0 (4902) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.464 - info: mihome-vacuum.0 (1609) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.444 - info: email.0 (1291) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.438 - info: pushover.0 (1208) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.485 - info: host.tims-pi1 stopInstance system.adapter.admin.0 send kill signal
                    2023-07-03 23:38:24.489 - info: yahka.1 (30056) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.491 - info: zigbee2mqtt.0 (4233) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.490 - info: sma-em.0 (23059) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.492 - info: homepilot20.0 (1818) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.443 - info: telegram.0 (25742) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.451 - info: tuya.0 (1587) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.488 - info: host.tims-pi1 stopInstance system.adapter.pushover.0 send kill signal
                    2023-07-03 23:38:24.495 - info: host.tims-pi1 stopInstance system.adapter.email.0 send kill signal
                    2023-07-03 23:38:24.496 - info: host.tims-pi1 stopInstance system.adapter.telegram.0 send kill signal
                    2023-07-03 23:38:24.496 - info: host.tims-pi1 stopInstance system.adapter.javascript.0 send kill signal
                    2023-07-03 23:38:24.502 - info: host.tims-pi1 stopInstance system.adapter.hm-rega.0 send kill signal
                    2023-07-03 23:38:24.503 - info: host.tims-pi1 stopInstance system.adapter.rpi2.0 send kill signal
                    2023-07-03 23:38:24.508 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 send kill signal
                    2023-07-03 23:38:24.509 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.1 send kill signal
                    2023-07-03 23:38:24.510 - info: host.tims-pi1 stopInstance system.adapter.sonoff.0 send kill signal
                    2023-07-03 23:38:24.510 - info: host.tims-pi1 stopInstance system.adapter.alexa2.0 send kill signal
                    2023-07-03 23:38:24.511 - info: host.tims-pi1 stopInstance system.adapter.hm-rpc.0 send kill signal
                    2023-07-03 23:38:24.511 - info: host.tims-pi1 stopInstance system.adapter.tuya.0 send kill signal
                    2023-07-03 23:38:24.512 - info: host.tims-pi1 stopInstance system.adapter.mihome-vacuum.0 send kill signal
                    2023-07-03 23:38:24.512 - info: host.tims-pi1 stopInstance system.adapter.daikin.0 send kill signal
                    2023-07-03 23:38:24.513 - info: host.tims-pi1 stopInstance system.adapter.mqtt.0 send kill signal
                    2023-07-03 23:38:24.514 - info: host.tims-pi1 stopInstance system.adapter.notification-manager.0 send kill signal
                    2023-07-03 23:38:24.515 - info: host.tims-pi1 stopInstance system.adapter.yahka.0 send kill signal
                    2023-07-03 23:38:24.516 - info: host.tims-pi1 stopInstance system.adapter.nuki.0 send kill signal
                    2023-07-03 23:38:24.517 - info: host.tims-pi1 stopInstance system.adapter.discovery.0 send kill signal
                    2023-07-03 23:38:24.517 - info: host.tims-pi1 stopInstance system.adapter.fritzdect.0 send kill signal
                    2023-07-03 23:38:24.518 - info: host.tims-pi1 stopInstance system.adapter.backitup.0 send kill signal
                    2023-07-03 23:38:24.518 - info: host.tims-pi1 stopInstance system.adapter.iot.0 send kill signal
                    2023-07-03 23:38:24.519 - info: host.tims-pi1 stopInstance system.adapter.wled.0 send kill signal
                    2023-07-03 23:38:24.530 - info: host.tims-pi1 stopInstance system.adapter.homepilot20.0 send kill signal
                    2023-07-03 23:38:24.531 - info: host.tims-pi1 stopInstance system.adapter.zigbee2mqtt.0 send kill signal
                    2023-07-03 23:38:24.532 - info: host.tims-pi1 stopInstance system.adapter.info.0 send kill signal
                    2023-07-03 23:38:24.532 - info: host.tims-pi1 stopInstance system.adapter.sma-em.0 send kill signal
                    2023-07-03 23:38:24.533 - info: host.tims-pi1 stopInstance system.adapter.web.0 send kill signal
                    2023-07-03 23:38:24.533 - info: host.tims-pi1 stopInstance system.adapter.yahka.1 send kill signal
                    2023-07-03 23:38:24.419 - info: hm-rega.0 (1382) terminating
                    2023-07-03 23:38:24.433 - info: hm-rega.0 (1382) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.550 - info: hm-rega.0 (1382) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.341 - info: iot.0 (1796) Connection changed: disconnect
                    2023-07-03 23:38:24.558 - info: iot.0 (1796) Connection lost
                    2023-07-03 23:38:24.244 - info: rpi2.0 (1431) terminating
                    2023-07-03 23:38:24.493 - info: rpi2.0 (1431) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.253 - info: discovery.0 (1717) terminating
                    2023-07-03 23:38:24.465 - info: discovery.0 (1717) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.572 - info: iot.0 (1796) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.148 - info: hm-rpc.1 (1512) xmlrpc -> 192.168.178.95:42010/ init ["http://192.168.178.96:42010",""]
                    2023-07-03 23:38:24.576 - info: iot.0 (1796) terminating
                    2023-07-03 23:38:24.579 - info: iot.0 (1796) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.271 - info: alexa2.0 (1542) terminating
                    2023-07-03 23:38:24.439 - info: alexa2.0 (1542) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.162 - info: daikin.0 (1624) terminating
                    2023-07-03 23:38:24.456 - info: daikin.0 (1624) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.581 - info: rpi2.0 (1431) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.586 - info: alexa2.0 (1542) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.579 - info: hm-rpc.1 (1512) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.594 - info: discovery.0 (1717) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.591 - info: daikin.0 (1624) Got terminate signal TERMINATE_YOURSELF
                    2023-07-03 23:38:24.621 - info: hm-rpc.1 (1512) Disconnected
                    2023-07-03 23:38:24.631 - info: hm-rpc.1 (1512) terminating
                    2023-07-03 23:38:24.634 - info: hm-rpc.1 (1512) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.650 - info: email.0 (1291) terminating
                    2023-07-03 23:38:24.664 - info: daikin.0 (1624) terminating
                    2023-07-03 23:38:24.673 - info: yahka.0 (1673) terminating
                    2023-07-03 23:38:24.680 - info: telegram.0 (25742) terminating
                    2023-07-03 23:38:24.679 - warn: influxdb.1 (8576) Store data for 324 points and 0 conflicts
                    2023-07-03 23:38:24.685 - info: sonoff.0 (1527) terminating
                    2023-07-03 23:38:24.688 - info: sonoff.0 (1527) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.686 - info: iot.0 (1796) terminating
                    2023-07-03 23:38:24.688 - info: javascript.0 (12330) terminating
                    2023-07-03 23:38:24.695 - info: homepilot20.0 (1818) terminating
                    2023-07-03 23:38:24.692 - info: telegram.0 (25742) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.699 - info: mihome-vacuum.0 (1609) terminating
                    2023-07-03 23:38:24.706 - info: notification-manager.0 (1658) terminating
                    2023-07-03 23:38:24.715 - info: discovery.0 (1717) terminating
                    2023-07-03 23:38:24.717 - info: mqtt.0 (11274) terminating
                    2023-07-03 23:38:24.722 - info: hm-rega.0 (1382) terminating
                    2023-07-03 23:38:24.721 - info: mqtt.0 (11274) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.724 - info: alexa2.0 (1542) terminating
                    2023-07-03 23:38:24.720 - info: pushover.0 (1208) terminating
                    2023-07-03 23:38:24.728 - info: rpi2.0 (1431) terminating
                    2023-07-03 23:38:24.731 - info: pushover.0 (1208) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:24.767 - info: sma-em.0 (23059) terminating
                    2023-07-03 23:38:24.769 - info: yahka.1 (30056) terminating
                    2023-07-03 23:38:24.803 - info: backitup.0 (1784) terminating
                    2023-07-03 23:38:24.832 - info: fritzdect.0 (1765) terminating
                    2023-07-03 23:38:24.835 - info: admin.0 (4902) terminating
                    2023-07-03 23:38:24.929 - info: host.tims-pi1 instance system.adapter.nuki.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.173 - info: host.tims-pi1 instance system.adapter.email.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.184 - error: shelly.0 (12292) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2023-07-03 23:38:25.210 - error: shelly.0 (12292) unhandled promise rejection: DB closed
                    2023-07-03 23:38:25.213 - error: shelly.0 (12292) Error: DB closed
                    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    at Object.onceWrapper (node:events:628:26)
                    at Socket.emit (node:events:513:28)
                    at Socket.emit (node:domain:489:12)
                    at TCP. (node:net:322:12)
                    2023-07-03 23:38:25.214 - error: shelly.0 (12292) DB closed
                    2023-07-03 23:38:25.322 - info: zigbee2mqtt.0 (4233) Connect to Zigbee2MQTT over websocket connection.
                    2023-07-03 23:38:25.174 - info: host.tims-pi1 instance system.adapter.notification-manager.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.388 - info: host.tims-pi1 instance system.adapter.yahka.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.390 - info: host.tims-pi1 instance system.adapter.web.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.393 - info: host.tims-pi1 instance system.adapter.sma-em.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.544 - info: host.tims-pi1 instance system.adapter.sql.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.545 - info: host.tims-pi1 instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.546 - info: host.tims-pi1 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.548 - info: host.tims-pi1 stopInstance system.adapter.shelly.0 killing pid 12292
                    2023-07-03 23:38:25.661 - info: zigbee2mqtt.0 (4233) terminating
                    2023-07-03 23:38:25.662 - info: zigbee2mqtt.0 (4233) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:25.674 - info: host.tims-pi1 instance system.adapter.mihome-vacuum.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.675 - info: host.tims-pi1 instance system.adapter.fritzdect.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.675 - info: host.tims-pi1 instance system.adapter.wled.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.812 - info: host.tims-pi1 instance system.adapter.homepilot20.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.813 - info: host.tims-pi1 instance system.adapter.info.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.815 - info: host.tims-pi1 instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.920 - info: host.tims-pi1 instance system.adapter.yahka.1 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.922 - info: host.tims-pi1 instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.922 - info: host.tims-pi1 instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:25.948 - info: host.tims-pi1 instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.017 - info: host.tims-pi1 instance system.adapter.pushover.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.051 - info: host.tims-pi1 instance system.adapter.hm-rega.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.116 - info: host.tims-pi1 instance system.adapter.rpi2.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.196 - info: zigbee2mqtt.0 (4233) terminating
                    2023-07-03 23:38:26.198 - warn: zigbee2mqtt.0 (4233) Cannot get view: Connection is closed.
                    2023-07-03 23:38:26.198 - warn: zigbee2mqtt.0 (4233) Cannot get view: Connection is closed.
                    2023-07-03 23:38:26.117 - info: host.tims-pi1 instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.227 - info: host.tims-pi1 instance system.adapter.sonoff.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.228 - info: host.tims-pi1 instance system.adapter.daikin.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.229 - info: host.tims-pi1 instance system.adapter.iot.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.319 - info: host.tims-pi1 instance system.adapter.mqtt.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.320 - info: host.tims-pi1 instance system.adapter.telegram.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.321 - info: host.tims-pi1 instance system.adapter.influxdb.1 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.343 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write EPIPE
                    2023-07-03 23:38:26.344 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                    2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                    2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                    2023-07-03 23:38:26.345 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                    2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                    2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                    2023-07-03 23:38:26.346 - error: host.tims-pi1 Caught by controller[0]: at Socket.Writable.write (node:internal/streams/writable:337:10)
                    2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                    2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at Redis.publish (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:817:35)
                    2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                    2023-07-03 23:38:26.347 - error: host.tims-pi1 Caught by controller[0]: Error: DB closed
                    2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                    2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                    2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Object.onceWrapper (node:events:628:26)
                    2023-07-03 23:38:26.348 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:events:513:28)
                    2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at Socket.emit (node:domain:489:12)
                    2023-07-03 23:38:26.349 - error: host.tims-pi1 Caught by controller[0]: at TCP. (node:net:322:12)
                    2023-07-03 23:38:26.349 - info: host.tims-pi1 instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: [ioredis] Unhandled error event: Error: write ECONNRESET
                    2023-07-03 23:38:26.373 - error: host.tims-pi1 Caught by controller[0]: at afterWriteDispatched (node:internal/stream_base_commons:160:15)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeGeneric (node:internal/stream_base_commons:151:3)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._writeGeneric (node:net:930:11)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Socket._write (node:net:942:8)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at writeOrBuffer (node:internal/streams/writable:392:12)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at _write (node:internal/streams/writable:333:10)
                    2023-07-03 23:38:26.374 - error: host.tims-pi1 Caught by controller[0]: at Writable.write (node:internal/streams/writable:337:10)
                    2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33)
                    2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at Redis.evalsha (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-07-03 23:38:26.375 - error: host.tims-pi1 Caught by controller[0]: at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:3105:46)
                    2023-07-03 23:38:26.375 - info: host.tims-pi1 instance system.adapter.zigbee2mqtt.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:27.224 - info: tuya.0 (1587) terminating
                    2023-07-03 23:38:27.228 - info: tuya.0 (1587) Terminated (NO_ERROR): Without reason
                    2023-07-03 23:38:27.814 - info: host.tims-pi1 instance system.adapter.tuya.0 terminated with code 0 (NO_ERROR)
                    2023-07-03 23:38:27.815 - info: host.tims-pi1 All instances are stopped.
                    2023-07-03 23:38:27.845 - info: host.tims-pi1 terminated
                    2023-07-03 23:38:31.939 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
                    2023-07-03 23:38:32.123 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:443
                    2023-07-03 23:39:17.791 - info: host.tims-pi1 [CONTROLLER_AUTO_UPGRADE]
                    removed 97 packages, and changed 16 packages in 45s
                    143 packages are looking for funding
                    
                    apollon77A Offline
                    apollon77A Offline
                    apollon77
                    schrieb am zuletzt editiert von
                    #359

                    @ticaki Ok

                    Ist die Befehlsreihenfolge da oben ernst? .. iobroker stoppen, dann starten, dann host rebooten (was ihn wieder stoppt und nach dem reboot startet) ??

                    Weiterhin ist da slog hioer aber ein js.controller upgrade via Admin. Passt nicht ganz zum normalen Restart ...

                    generell:
                    Das DB Closed by Shelly beim Stoppen passieren kann ist "bekannt" und glaube ein issue offen. Da wird wohl was nicht sauber beendet.

                    Der nächste Fehler tippe ich könnte von zigbee kommen der scheinbar nach dem stoppen versucht irgendwelche views zu lesen ... Bitte issue bei zigbee öffnen wenn nicht schon da ist.

                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                    T 1 Antwort Letzte Antwort
                    0
                    • apollon77A apollon77

                      @ticaki Ok

                      Ist die Befehlsreihenfolge da oben ernst? .. iobroker stoppen, dann starten, dann host rebooten (was ihn wieder stoppt und nach dem reboot startet) ??

                      Weiterhin ist da slog hioer aber ein js.controller upgrade via Admin. Passt nicht ganz zum normalen Restart ...

                      generell:
                      Das DB Closed by Shelly beim Stoppen passieren kann ist "bekannt" und glaube ein issue offen. Da wird wohl was nicht sauber beendet.

                      Der nächste Fehler tippe ich könnte von zigbee kommen der scheinbar nach dem stoppen versucht irgendwelche views zu lesen ... Bitte issue bei zigbee öffnen wenn nicht schon da ist.

                      T Nicht stören
                      T Nicht stören
                      ticaki
                      schrieb am zuletzt editiert von ticaki
                      #360

                      @apollon77
                      Nein, das ist keine Folge sondern die Befehle, die ich ich allgemein zum Restarten verwende - entweder ich restarte nur io oder aber den pi. sry unklar ausgedrückt.

                      Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                      Spenden

                      1 Antwort Letzte Antwort
                      1
                      • S Offline
                        S Offline
                        Snigga
                        schrieb am zuletzt editiert von
                        #361

                        Hallo ich habe mit der Version 5.0.6 das Problem, das mein Iobroker keine Javascripts mehr ausführt. Nur noch Blockly ohne Javascript Blockly. Wie kann ich wieder auf die Version 5.0.5 wechseln. Klappt bei mir irgendwie nicht.

                        ESP8266E Thomas BraunT 2 Antworten Letzte Antwort
                        0
                        • S Snigga

                          Hallo ich habe mit der Version 5.0.6 das Problem, das mein Iobroker keine Javascripts mehr ausführt. Nur noch Blockly ohne Javascript Blockly. Wie kann ich wieder auf die Version 5.0.5 wechseln. Klappt bei mir irgendwie nicht.

                          ESP8266E Offline
                          ESP8266E Offline
                          ESP8266
                          schrieb am zuletzt editiert von ESP8266
                          #362

                          @snigga ,kann ich nicht nachvollziehen und bestätigen, das sehe ich schon allein in der VIS. Dort werden stetig die SonnenElevation/SonnenAzimut und MondAzimut/MondElevation geändert.

                          Dein System ist wohl krum....

                          Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

                          1 Antwort Letzte Antwort
                          0
                          • S Snigga

                            Hallo ich habe mit der Version 5.0.6 das Problem, das mein Iobroker keine Javascripts mehr ausführt. Nur noch Blockly ohne Javascript Blockly. Wie kann ich wieder auf die Version 5.0.5 wechseln. Klappt bei mir irgendwie nicht.

                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #363

                            @snigga

                            Kann ich auch nicht bestätigen. Hier läuft alles an Skripten/Blocklies.

                            Linux-Werkzeugkasten:
                            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                            NodeJS Fixer Skript:
                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                            G S 2 Antworten Letzte Antwort
                            0
                            • foxriver76F foxriver76

                              @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

                              Neue erkannte Probleme, die noch nicht behandelt sind:

                              Ich schreibe mal meine Updates in klammern dahinter

                              • stiebel-isg update nötig
                              • lgtv zeigt Fehlermeldungen an (sollte fixed sein mit 1.1.12)
                              • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
                              • js-controller upgrade via Admin startet js-controller nicht wieder
                              • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
                              • km200 muss geprüft werden (sollte gefixt sein mit 2.0.4)
                              • miio muss geprüft werden
                              • fakeroku muss geprüft werden (git version funktioniert, benötigt publish)
                              • pi-hole update nötig
                              • node-red muss geprüft werden
                              • enigma2.0 mindestens 1.4.0+
                              • doorbird update nötig
                              • linux-control update nötig
                              B Nicht stören
                              B Nicht stören
                              bommel_030
                              schrieb am zuletzt editiert von
                              #364

                              @foxriver76
                              der km200 Version 2.0.4 läuft bei mir wieder mit js-controller 5.0.6, danke!

                              mcm1957M 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @snigga

                                Kann ich auch nicht bestätigen. Hier läuft alles an Skripten/Blocklies.

                                G Offline
                                G Offline
                                guergen
                                schrieb am zuletzt editiert von
                                #365

                                @thomas-braun
                                Ich habe auch Probleme mit Scripten: Hab hier ein axios.post in 2 Scripten laufen, die gingen nach dem Update auf 5.0.6 nicht mehr. Nach dem Dowgrade gehen sie wieder

                                1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @snigga

                                  Kann ich auch nicht bestätigen. Hier läuft alles an Skripten/Blocklies.

                                  S Offline
                                  S Offline
                                  Snigga
                                  schrieb am zuletzt editiert von
                                  #366

                                  @thomas-braun bei mir habe ich festgestellt, wenn ein script einen Request mit PUT oder POST ausführt, führt es dazu, das die Script Instance sich neustartet. der PUT oder POST Befehl wird nicht abgesetzt. Alle Scripte die nur GET nutzen funktionieren

                                  apollon77A 1 Antwort Letzte Antwort
                                  0
                                  • S Snigga

                                    @thomas-braun bei mir habe ich festgestellt, wenn ein script einen Request mit PUT oder POST ausführt, führt es dazu, das die Script Instance sich neustartet. der PUT oder POST Befehl wird nicht abgesetzt. Alle Scripte die nur GET nutzen funktionieren

                                    apollon77A Offline
                                    apollon77A Offline
                                    apollon77
                                    schrieb am zuletzt editiert von
                                    #367

                                    @snigga Dann würde ich sagen das es eher ein Skript Fehlert ist. AM besten in eineinm eigenen Thread im korrekten Sub Foum mal skript und Fehlermeldung posten.

                                    Ich tippe auf fehlendes Fehlerhandling und "Async" kram weil das gerade nicht sauber abfangbar ist und ggf die Instanz crasht. Fehlerhandling adden und es wird gehen.

                                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                    1 Antwort Letzte Antwort
                                    2
                                    • apollon77A apollon77

                                      Neue erkannte Probleme, die noch nicht behandelt sind:

                                      • stiebel-isg update nötig
                                      • lgtv sollte fixed sein mit 1.1.12
                                      • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
                                      • js-controller upgrade via Admin startet js-controller nicht wieder
                                      • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
                                      • km200 sollte gefixt sein mit 2.0.4
                                      • miio muss geprüft werden
                                      • fakeroku GitHub Version gefixt, release fehlt noch
                                      • pi-hole update nötig
                                      • node-red muss geprüft werden
                                      • enigma2.0 mindestens 1.4.0+
                                      • doorbird update nötig
                                      • linux-control update nötig
                                      mcm1957M Offline
                                      mcm1957M Offline
                                      mcm1957
                                      schrieb am zuletzt editiert von
                                      #368

                                      @apollon77 said in js-controller 5.0.x jetzt in der BETA:

                                      Neue erkannte Probleme, die noch nicht behandelt sind:

                                      • doorbird update nötig

                                      Doorbird ab 1.0.x sollte js-controller 5 unterstützen.
                                      https://t.me/ioBroker_development/29005

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

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

                                      LESEN - gute Forenbeitrage

                                      1 Antwort Letzte Antwort
                                      0
                                      • foxriver76F foxriver76

                                        @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

                                        Neue erkannte Probleme, die noch nicht behandelt sind:

                                        Ich schreibe mal meine Updates in klammern dahinter

                                        • stiebel-isg update nötig
                                        • lgtv zeigt Fehlermeldungen an (sollte fixed sein mit 1.1.12)
                                        • web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
                                        • js-controller upgrade via Admin startet js-controller nicht wieder
                                        • Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
                                        • km200 muss geprüft werden (sollte gefixt sein mit 2.0.4)
                                        • miio muss geprüft werden
                                        • fakeroku muss geprüft werden (git version funktioniert, benötigt publish)
                                        • pi-hole update nötig
                                        • node-red muss geprüft werden
                                        • enigma2.0 mindestens 1.4.0+
                                        • doorbird update nötig
                                        • linux-control update nötig
                                        L Online
                                        L Online
                                        looxer01
                                        schrieb am zuletzt editiert von
                                        #369

                                        @foxriver76

                                        @foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:

                                        Ich schreibe mal meine Updates in klammern dahinter

                                        stiebel-isg update nötig
                                        lgtv zeigt Fehlermeldungen an (sollte fixed sein mit 1.1.12)
                                        web kann crashen falls Widgets in vis falsch konfiguriert sind (PR in socket-classes existiert bereits)
                                        js-controller upgrade via Admin startet js-controller nicht wieder
                                        Admin zeigt falsche Log grösse an -> Fixed in Admin 6.5.8+
                                        km200 muss geprüft werden (sollte gefixt sein mit 2.0.4)
                                        miio muss geprüft werden
                                        fakeroku muss geprüft werden (git version funktioniert, benötigt publish)
                                        pi-hole update nötig
                                        node-red muss geprüft werden
                                        enigma2.0 mindestens 1.4.0+
                                        doorbird update nötig
                                        linux-control update nötig

                                        • B-Control-EM update nötig
                                          https://github.com/ioBroker/ioBroker.b-control-em

                                        vG Looxer

                                        1 Antwort Letzte Antwort
                                        0
                                        • apollon77A apollon77

                                          @lausid sagte in js-controller 5.0.x jetzt in der BETA:

                                          Läuft zB alexa2 und web und alexa2 wird beendet verliert web die Anbindung zur DB.

                                          Das sollte nicht passieren. Log Bitte posten

                                          LausiDL Offline
                                          LausiDL Offline
                                          LausiD
                                          schrieb am zuletzt editiert von
                                          #370

                                          @apollon77 sagte in js-controller 5.0.x jetzt in der BETA:

                                          @lausid sagte in js-controller 5.0.x jetzt in der BETA:

                                          Läuft zB alexa2 und web und alexa2 wird beendet verliert web die Anbindung zur DB.

                                          Das sollte nicht passieren. Log Bitte posten

                                          web.0
                                          	2023-07-09 18:12:14.764	info	(COMPACT) setState not processed because States database not connected
                                          web.0
                                          	2023-07-09 18:12:14.181	info	(COMPACT) http server listening on port 8086
                                          web.0
                                          	2023-07-09 18:12:14.180	info	(COMPACT) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          web.0
                                          	2023-07-09 18:12:14.177	error	(COMPACT) port 8082 already in use
                                          web.0
                                          	2023-07-09 18:12:13.762	info	(COMPACT) socket.io server listening on port 8082
                                          web.0
                                          	2023-07-09 18:12:13.634	warn	(COMPACT) Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                                          web.0
                                          	2023-07-09 18:12:13.129	info	(COMPACT) starting. Version 5.5.3 in /opt/iobroker/node_modules/iobroker.web, node: v16.15.1, js-controller: 5.0.6
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:12:04.840	info	instance system.adapter.web.0 started in COMPACT mode
                                          web.0
                                          	2023-07-09 18:11:31.691	warn	(COMPACT) Cannot connect/reconnect to states DB. Terminating
                                          web.0
                                          	2023-07-09 18:11:31.664	warn	(COMPACT) Cannot connect/reconnect to states DB. Terminating
                                          web.0
                                          	2023-07-09 18:11:31.632	warn	(COMPACT) Cannot connect/reconnect to states DB. Terminating
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:31.427	info	Restart adapter system.adapter.web.0 because enabled
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:31.425	info	instance system.adapter.web.0 terminated with code 0 (NO_ERROR)
                                          web.0
                                          	2023-07-09 18:11:30.820	warn	(COMPACT) Cannot connect/reconnect to objects DB. Terminating
                                          web.0
                                          	2023-07-09 18:11:30.719	warn	(COMPACT) Cannot connect/reconnect to objects DB. Terminating
                                          web.0
                                          	2023-07-09 18:11:30.707	info	(COMPACT) Terminated (NO_ERROR): Without reason
                                          web.0
                                          	2023-07-09 18:11:30.705	warn	(COMPACT) Cannot connect/reconnect to objects DB. Terminating
                                          alexa2.0
                                          	2023-07-09 18:11:27.611	info	(COMPACT) terminating with timeout
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:27.101	info	instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:27.100	warn	instance system.adapter.alexa2.0 terminated due to 11
                                          alexa2.0
                                          	2023-07-09 18:11:26.608	info	(COMPACT) terminating
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:26.574	info	stopInstance system.adapter.alexa2.0 send kill signal
                                          alexa2.0
                                          	2023-07-09 18:11:26.103	info	(COMPACT) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          alexa2.0
                                          	2023-07-09 18:11:26.099	info	(COMPACT) terminating
                                          alexa2.0
                                          	2023-07-09 18:11:26.079	info	(COMPACT) Got terminate signal TERMINATE_YOURSELF
                                          alexa2.0
                                          	2023-07-09 18:11:26.023	info	(COMPACT) Got terminate signal TERMINATE_YOURSELF
                                          host.raspberrypi
                                          	2023-07-09 18:11:25.982	info	stopInstance system.adapter.alexa2.0 (force=false, process=true)
                                          host.raspberrypi
                                          	2023-07-09 18:11:25.972	info	"system.adapter.alexa2.0" disabled
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:25.952	info	stopInstance system.adapter.alexa2.0 (force=false, process=true)
                                          host.raspberrypi.compactgroup1
                                          	2023-07-09 18:11:25.945	info	"system.adapter.alexa2.0" disabled
                                          

                                          alexa2, sql und web im compact-mode - alexa2 beendet und web keine Verbindung zur Datenbank - web und sql muss beendet werden, danch Start im Compact Mode wieder möglich.
                                          admin unf fhem im Compact Mode verlieren ebenfalls die Verbindung zur DB bei Stop einer Instanz aus compact Gruppe.

                                          Doku zum FHEM Adapter
                                          Aktuelles zum FHEM Adapter
                                          Test FHEM Adapter

                                          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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          774

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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