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

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. js-controller Lucy (Version 7.0) jetzt im Beta Repository

NEWS

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

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

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

js-controller Lucy (Version 7.0) jetzt im Beta Repository

Geplant Angeheftet Gesperrt Verschoben Tester
testjs-controllerbetalucydynamic notificationsbackup
146 Beiträge 28 Kommentatoren 25.6k Aufrufe 30 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.
  • Dr. BakteriusD Dr. Bakterius

    @thomas-braun sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

    Dürfte dann so quttiert werden

    Genau so. :smiley:

    MartinPM Online
    MartinPM Online
    MartinP
    schrieb am zuletzt editiert von
    #73

    Wann ist eigentlich der Wechsel der 7.x Codelinie ins Stable Repository zu erwarten?

    Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
    Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.13)
    kernel Linux pve 6.8.12-15-pve
    6 GByte RAM für den Container
    Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
    Remote-Access über Wireguard der Fritzbox

    foxriver76F 1 Antwort Letzte Antwort
    0
    • JB_SullivanJ Offline
      JB_SullivanJ Offline
      JB_Sullivan
      schrieb am zuletzt editiert von
      #74

      Wie sieht es mit dem Fixer für den Windows Installer aus? Von dem Problem nicht betroffen, da ein ganz anderes BS?

      ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • JB_SullivanJ JB_Sullivan

        Wie sieht es mit dem Fixer für den Windows Installer aus? Von dem Problem nicht betroffen, da ein ganz anderes BS?

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

        @jb_sullivan sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

        Wie sieht es mit dem Fixer für den Windows Installer aus? Von dem Problem nicht betroffen, da ein ganz anderes BS?

        Die Änderungen bei den Rechten betreffen nur Linux-Systeme, die systemd verwenden. Also primär Debian (inkl LXCs) und RaspberryOS, aber nicht den Docker.

        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
        • MartinPM MartinP

          Wann ist eigentlich der Wechsel der 7.x Codelinie ins Stable Repository zu erwarten?

          foxriver76F Offline
          foxriver76F Offline
          foxriver76
          Developer
          schrieb am zuletzt editiert von
          #76

          @martinp naja es sind gestern frische Probleme gemeldet worden die noch nicht mal im Beta gefixt sind. 2 Wochen stabil im Beta ca dann stable

          Videotutorials & mehr

          Hier könnt ihr mich unterstützen.

          1 Antwort Letzte Antwort
          0
          • H Offline
            H Offline
            hahne
            schrieb am zuletzt editiert von
            #77

            Moin ,
            hab das selbe Problem wie @DLehmann .
            Redis Installation läuft sauber durch aber beim migrieren von jsonl zu redis gibt es einen Fehler.

            Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y                                                                                                             /N]: y
            
            Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y
            
            Connecting to previous DB "jsonl/jsonl"...
            Creating backup ...
            This can take some time ... please be patient!
            host.ioBroker 16568 objects saved
            host.ioBroker 13082 states saved
            host.ioBroker Validating backup ...
            host.ioBroker The backup is valid!
            Backup created: /opt/iobroker/backups/2024_10_25-08_42_09_backupiobroker-migration.tar.gz
            updating conf/iobroker.json
            
            Connecting to new DB "redis/redis" (can take up to 20s) ...
             Cannot read system.config: null (OK when migrating or restoring)
            Restore backup ...
            This can take some time ... please be patient!
            host.ioBroker Cannot find extracted file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json" or "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json"
            Error happened during restore. Exit-Code: 26
            
            restoring conf/iobroker.json
            
            
            foxriver76F 1 Antwort Letzte Antwort
            0
            • H hahne

              Moin ,
              hab das selbe Problem wie @DLehmann .
              Redis Installation läuft sauber durch aber beim migrieren von jsonl zu redis gibt es einen Fehler.

              Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y                                                                                                             /N]: y
              
              Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y
              
              Connecting to previous DB "jsonl/jsonl"...
              Creating backup ...
              This can take some time ... please be patient!
              host.ioBroker 16568 objects saved
              host.ioBroker 13082 states saved
              host.ioBroker Validating backup ...
              host.ioBroker The backup is valid!
              Backup created: /opt/iobroker/backups/2024_10_25-08_42_09_backupiobroker-migration.tar.gz
              updating conf/iobroker.json
              
              Connecting to new DB "redis/redis" (can take up to 20s) ...
               Cannot read system.config: null (OK when migrating or restoring)
              Restore backup ...
              This can take some time ... please be patient!
              host.ioBroker Cannot find extracted file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json" or "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json"
              Error happened during restore. Exit-Code: 26
              
              restoring conf/iobroker.json
              
              
              foxriver76F Offline
              foxriver76F Offline
              foxriver76
              Developer
              schrieb am zuletzt editiert von
              #78

              @hahne wird mit der nächsten Beta Version gefixt sein

              Videotutorials & mehr

              Hier könnt ihr mich unterstützen.

              H 1 Antwort Letzte Antwort
              0
              • foxriver76F foxriver76

                @hahne wird mit der nächsten Beta Version gefixt sein

                H Offline
                H Offline
                hahne
                schrieb am zuletzt editiert von
                #79

                @foxriver76 super danke

                1 Antwort Letzte Antwort
                0
                • foxriver76F foxriver76

                  @DLehmann @crunchip eure beiden issues sollten mit Controller 7.0.1 behoben sein.

                  crunchipC Offline
                  crunchipC Offline
                  crunchip
                  Forum Testing Most Active
                  schrieb am zuletzt editiert von crunchip
                  #80

                  @foxriver76 sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                  eure beiden issues sollten mit Controller 7.0.1 behoben sein

                  habe gestern abend erst die neu Version aufgespielt, mittels Maintenance-Scripts(docker), jedoch erzeugte mir das upgrade ein 10mb log,
                  Grund war wohl der frigate Adapter und die Folgefehler weiß ich nicht ob diese davon kamen.
                  anbei ein eingekürzter Logauszug

                  
                  2024-10-24 19:15:10.618  - info: host.IoBroker received SIGTERM
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.admin.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.email.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.history.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.influxdb.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.influxdb.1 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.influxdb.2 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.influxdb.3 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.javascript.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.javascript.1 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.scenes.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.scheduler.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.seq.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.telegram.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.telegram.1 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.whatsapp-cmb.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.backitup.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.alarm.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.alexa2.0 (force=false, process=true)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.broadlink2.0 (force=false, process=false)
                  2024-10-24 19:15:10.619  - info: host.IoBroker stopInstance system.adapter.chromecast.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.countdown.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.device-watcher.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.feiertage.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance canceled schedule system.adapter.feiertage.0
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.firetv.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.govee-local.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.ical.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance canceled schedule system.adapter.ical.0
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.ical.1 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance canceled schedule system.adapter.ical.1
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.mihome.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.mqtt.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.notificationforandroidtv.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.nut.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.onkyo.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.opendtu.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.operating-hours.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.ping.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.pollenflug.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.proxmox.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.puppeteer.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.radar2.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.roadtraffic.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.schoolfree.0 (force=false, process=false)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance canceled schedule system.adapter.schoolfree.0
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.shelly.0 (force=false, process=true)
                  2024-10-24 19:15:10.620  - info: host.IoBroker stopInstance system.adapter.shuttercontrol.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.snmp.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.sonoff.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.spotify-premium.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.tibberlink.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.tr-064.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.tuya.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.unifi.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.weatherunderground.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.wireguard.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.worx.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.yeelight-2.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.zigbee.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.zigbee2mqtt.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.openweathermap.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.gotify-ws.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.notification-manager.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.ble.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.daswetter.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.device-reminder.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.dwd.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.echarts.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.esphome.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.eventlist.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.frigate.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.fullcalendar.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.fully-tablet-control.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.fullybrowser.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.govee-app.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.hyperion.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.hyperion_ng.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.imap.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.iot.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.jarvis.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.lightcontrol.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.linux-control.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.logparser.0 (force=false, process=true)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.milight-smart-light.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.mobile.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.mytime.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.onvif.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.parcel.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.parser.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.phantomjs.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.rssfeed.0 (force=false, process=false)
                  2024-10-24 19:15:10.621  - info: host.IoBroker stopInstance system.adapter.sayit.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.signal-cmb.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.simple-api.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.slideshow.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.smartcontrol.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.sourceanalytix.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.statistics.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.text2command.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.tibberconnect.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.traccar.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.trashschedule.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.upnp.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.valuetrackerovertime.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.virtualpowermeter.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-2-widgets-energy.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-2-widgets-gauges.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-2-widgets-material.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-bars.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-colorpicker.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-google-fonts.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-history.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-inventwo.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-justgage.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-keyboard.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-lcars.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-map.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-material-webfont.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-material.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-metro.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-players.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-plumb.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-rgraph.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-weather.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.wallpanel.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.web.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.wiffi-wz.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.wiobrowser.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.wled.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.ws.0 (force=false, process=true)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.awtrix-light.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.vis-2.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.rest-api.0 (force=false, process=false)
                  2024-10-24 19:15:10.622  - info: host.IoBroker stopInstance system.adapter.weather-warnings.0 (force=false, process=true)
                  2024-10-24 19:15:10.636  - warn: influxdb.0 (195) Store data for 91 points and 0 conflicts
                  2024-10-24 19:15:10.639  - warn: influxdb.1 (216) Store data for 43 points and 0 conflicts
                  2024-10-24 19:15:10.742  - info: admin.0 (149) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.742  - info: javascript.0 (237) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.743  - info: telegram.0 (231) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.743  - info: admin.0 (149) terminating http server on port 8081
                  2024-10-24 19:15:10.744  - info: admin.0 (149) terminating
                  2024-10-24 19:15:10.744  - info: admin.0 (149) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.744  - info: telegram.1 (244) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.745  - info: mihome.0 (389) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.746  - info: mihome.0 (389) terminating
                  2024-10-24 19:15:10.746  - info: mihome.0 (389) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.743  - info: javascript.0 (237) Stopping script ......
                  2024-10-24 19:15:10.747  - info: opendtu.0 (469) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.748  - info: radar2.0 (509) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.749  - info: shuttercontrol.0 (650) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.749  - info: opendtu.0 (469) terminating
                  2024-10-24 19:15:10.750  - info: opendtu.0 (469) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.750  - info: javascript.0 (237) terminating
                  2024-10-24 19:15:10.750  - info: javascript.0 (237) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.750  - info: shuttercontrol.0 (650) cleaned everything up...
                  2024-10-24 19:15:10.750  - info: shuttercontrol.0 (650) terminating
                  2024-10-24 19:15:10.750  - info: shuttercontrol.0 (650) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) Unload adapter now with null
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) Adapter disconnected and stopped with dostop(null) and callback(true)
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) terminating
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) terminating
                  2024-10-24 19:15:10.750  - info: radar2.0 (509) terminating
                  2024-10-24 19:15:10.751  - info: tibberlink.0 (736) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.752  - info: tr-064.0 (780) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.753  - info: tibberlink.0 (736) terminating
                  2024-10-24 19:15:10.753  - info: tibberlink.0 (736) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.754  - info: yeelight-2.0 (865) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.754  - info: tr-064.0 (780) terminating
                  2024-10-24 19:15:10.755  - info: tr-064.0 (780) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.756  - info: zigbee2mqtt.0 (894) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.756  - info: yeelight-2.0 (865) cleaned everything up...
                  2024-10-24 19:15:10.756  - info: yeelight-2.0 (865) terminating
                  2024-10-24 19:15:10.756  - info: yeelight-2.0 (865) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.757  - info: notification-manager.0 (909) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.757  - info: notification-manager.0 (909) terminating
                  2024-10-24 19:15:10.758  - info: notification-manager.0 (909) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.758  - info: frigate.0 (2496) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.759  - info: govee-app.0 (13532) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.759  - info: iot.0 (954) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.759  - info: frigate.0 (2496) terminating
                  2024-10-24 19:15:10.760  - info: frigate.0 (2496) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.760  - info: govee-app.0 (13532) terminating
                  2024-10-24 19:15:10.760  - info: govee-app.0 (13532) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.760  - info: iot.0 (954) terminating
                  2024-10-24 19:15:10.761  - info: iot.0 (954) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.760  - info: jarvis.0 (969) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.762  - info: jarvis.0 (969) Adapter stopped und unloaded.
                  2024-10-24 19:15:10.762  - info: jarvis.0 (969) terminating
                  2024-10-24 19:15:10.762  - info: jarvis.0 (969) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.762  - info: logparser.0 (999) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.763  - info: logparser.0 (999) cleaned everything up...
                  2024-10-24 19:15:10.763  - info: logparser.0 (999) terminating
                  2024-10-24 19:15:10.764  - info: logparser.0 (999) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.763  - info: smartcontrol.0 (1013) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.765  - info: text2command.0 (1072) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.766  - info: trashschedule.0 (1127) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.765  - info: smartcontrol.0 (1013) (1) timers were active and have been cleared...
                  2024-10-24 19:15:10.766  - info: smartcontrol.0 (1013) (7) schedules cleared...
                  2024-10-24 19:15:10.766  - info: smartcontrol.0 (1013) Stopping adapter instance successfully proceeded...
                  2024-10-24 19:15:10.766  - info: smartcontrol.0 (1013) terminating
                  2024-10-24 19:15:10.766  - info: smartcontrol.0 (1013) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.766  - info: traccar.0 (1112) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.767  - info: virtualpowermeter.0 (1142) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.767  - info: trashschedule.0 (1127) cleaned everything up...
                  2024-10-24 19:15:10.767  - info: trashschedule.0 (1127) terminating
                  2024-10-24 19:15:10.767  - info: trashschedule.0 (1127) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.767  - info: traccar.0 (1112) terminating
                  2024-10-24 19:15:10.767  - info: traccar.0 (1112) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.768  - info: virtualpowermeter.0 (1142) cleaned everything up...
                  2024-10-24 19:15:10.768  - info: wiffi-wz.0 (1206) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.768  - warn: web.0 (1187) setTimeout called, but adapter is shutting down
                  2024-10-24 19:15:10.769  - info: wiobrowser.0 (1223) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.769  - info: wiffi-wz.0 (1206) Stopping adapter ...
                  2024-10-24 19:15:10.769  - info: wiffi-wz.0 (1206) Adapter stopped.
                  2024-10-24 19:15:10.769  - info: wiffi-wz.0 (1206) terminating
                  2024-10-24 19:15:10.770  - info: wiffi-wz.0 (1206) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.770  - info: wiobrowser.0 (1223) terminating
                  2024-10-24 19:15:10.770  - info: wiobrowser.0 (1223) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.770  - info: wiobrowser.0 (1223) Disconnected from 10.1.1.129
                  2024-10-24 19:15:10.771  - info: weather-warnings.0 (1269) Got terminate signal TERMINATE_YOURSELF
                  2024-10-24 19:15:10.772  - info: weather-warnings.0 (1269) terminating
                  2024-10-24 19:15:10.772  - info: weather-warnings.0 (1269) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:10.804  - info: iot.0 (954) Connection changed: disconnect
                  2024-10-24 19:15:10.804  - info: iot.0 (954) Connection lost
                  2024-10-24 19:15:10.865  - info: history.0 (160) Terminated (NO_ERROR): Without reason
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.admin.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.javascript.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.telegram.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.telegram.1 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.alexa2.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.chromecast.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.mihome.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.mqtt.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.opendtu.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.radar2.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.shelly.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.shuttercontrol.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.sonoff.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.tibberlink.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.tr-064.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.unifi.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.yeelight-2.0 send kill signal
                  2024-10-24 19:15:10.958  - info: host.IoBroker stopInstance system.adapter.zigbee2mqtt.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.notification-manager.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.frigate.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.govee-app.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.iot.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.jarvis.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.linux-control.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.logparser.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.simple-api.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.smartcontrol.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.sourceanalytix.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.tankerkoenig.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.text2command.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.traccar.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.trashschedule.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.virtualpowermeter.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.web.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.wiffi-wz.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.wiobrowser.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.wled.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.ws.0 send kill signal
                  2024-10-24 19:15:10.959  - info: host.IoBroker stopInstance system.adapter.weather-warnings.0 send kill signal
                  2024-10-24 19:15:10.960  - warn: wiffi-wz.0 (1206) Read-only state "wiffi-wz.0.info.connection" has been written without ack-flag with value "false"
                  2024-10-24 19:15:10.960  - info: virtualpowermeter.0 (1142) terminating
                  2024-10-24 19:15:10.960  - info: virtualpowermeter.0 (1142) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:11.000  - warn: wiffi-wz.0 (1206) Read-only state "wiffi-wz.0.info.connection" has been written without ack-flag with value "false"
                  2024-10-24 19:15:11.243  - info: javascript.0 (237) terminating
                  2024-10-24 19:15:11.245  - info: admin.0 (149) terminating
                  2024-10-24 19:15:11.245  - info: telegram.0 (231) terminating
                  2024-10-24 19:15:11.246  - info: telegram.0 (231) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:11.246  - info: telegram.1 (244) terminating
                  2024-10-24 19:15:11.246  - info: telegram.1 (244) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:11.247  - info: mihome.0 (389) terminating
                  2024-10-24 19:15:11.249  - info: radar2.0 (509) terminating
                  2024-10-24 19:15:11.250  - info: opendtu.0 (469) terminating
                  2024-10-24 19:15:11.251  - info: shuttercontrol.0 (650) terminating
                  2024-10-24 19:15:11.254  - info: tibberlink.0 (736) terminating
                  2024-10-24 19:15:11.256  - info: tr-064.0 (780) terminating
                  2024-10-24 19:15:11.257  - info: yeelight-2.0 (865) terminating
                  2024-10-24 19:15:11.257  - info: notification-manager.0 (909) terminating
                  2024-10-24 19:15:11.260  - info: frigate.0 (2496) terminating
                  2024-10-24 19:15:11.260  - info: govee-app.0 (13532) terminating
                  2024-10-24 19:15:11.260  - info: iot.0 (954) terminating
                  2024-10-24 19:15:11.262  - info: jarvis.0 (969) terminating
                  2024-10-24 19:15:11.264  - info: logparser.0 (999) terminating
                  2024-10-24 19:15:11.265  - info: text2command.0 (1072) terminating
                  2024-10-24 19:15:11.266  - info: text2command.0 (1072) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:11.267  - info: smartcontrol.0 (1013) terminating
                  2024-10-24 19:15:11.268  - info: traccar.0 (1112) terminating
                  2024-10-24 19:15:11.268  - info: trashschedule.0 (1127) terminating
                  2024-10-24 19:15:11.269  - info: virtualpowermeter.0 (1142) terminating
                  2024-10-24 19:15:11.271  - info: wiobrowser.0 (1223) terminating
                  2024-10-24 19:15:11.273  - info: weather-warnings.0 (1269) terminating
                  2024-10-24 19:15:11.300  - warn: opendtu.0 (469) redis get opendtu.0.114180126869.available, error - Connection is closed.
                  2024-10-24 19:15:11.301  - warn: opendtu.0 (469) redis get opendtu.0.dtu.available, error - Connection is closed.
                  2024-10-24 19:15:11.318  - warn: frigate.0 (2496) get state error: DB closed
                  .
                  .
                  
                  2024-10-24 19:15:11.319  - warn: frigate.0 (2496) get state error: DB closed
                  2024-10-24 19:15:11.335  - warn: frigate.0 (2496) get state error: Connection is closed.
                  .
                  .
                  .
                  2024-10-24 19:15:11.338  - warn: frigate.0 (2496) get state error: Connection is closed.
                  2024-10-24 19:15:11.338  - warn: sourceanalytix.0 (1027) redis get sourceanalytix.0.sonoff__0__Brunnen__ENERGY_Total.2024.consumed.months.10_October, error - Connection is closed.
                  2024-10-24 19:15:11.342  - warn: opendtu.0 (469) get state error: Connection is closed.
                  2024-10-24 19:15:11.344  - warn: opendtu.0 (469) get state error: Connection is closed.
                  2024-10-24 19:15:11.344  - warn: opendtu.0 (469) redis get opendtu.0.1141801xxxxx.available, error - Connection is closed.
                  2024-10-24 19:15:11.344  - warn: opendtu.0 (469) redis get opendtu.0.dtu.available, error - Connection is closed.
                  2024-10-24 19:15:11.345  - error: unifi.0 (11760) Cannot find view "system" for search "state" : Connection is closed.
                  2024-10-24 19:15:11.347  - warn: frigate.0 (2496) get state error: Connection is closed.
                  2024-10-24 19:15:11.348  - error: chromecast.0 (265) Google_Home_mini - Could not get 20dfb9c72a61.player.currentTime:Error: DB closed
                  2024-10-24 19:15:11.349  - warn: opendtu.0 (469) Could not perform strict object check of state opendtu.0.114180126869.available: DB closed
                  2024-10-24 19:15:11.349  - error: shelly.0 (602) 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().
                  2024-10-24 19:15:11.350  - warn: opendtu.0 (469) get state error: Connection is closed.
                  2024-10-24 19:15:11.350  - warn: opendtu.0 (469) Could not perform strict object check of state opendtu.0.dtu.available: DB closed
                  2024-10-24 19:15:11.350  - warn: opendtu.0 (469) get state error: Connection is closed.
                  2024-10-24 19:15:11.352  - warn: sourceanalytix.0 (1027) get state error: Connection is closed.
                  2024-10-24 19:15:11.355  - warn: weather-warnings.0 (1269) Could not perform strict object check of state weather-warnings.0.info.connection: DB closed
                  2024-10-24 19:15:11.350  - error: chromecast.0 (265) 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().
                  2024-10-24 19:15:11.350  - error: chromecast.0 (265) unhandled promise rejection: DB closed
                  2024-10-24 19:15:11.351  - error: chromecast.0 (265) Error: DB closed
                     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                     at Object.onceWrapper (node:events:634:26)
                     at Socket.emit (node:events:519:28)
                     at Socket.emit (node:domain:488:12)
                     at TCP.<anonymous> (node:net:339:12)
                  2024-10-24 19:15:11.351  - error: chromecast.0 (265) DB closed
                  2024-10-24 19:15:11.355  - warn: weather-warnings.0 (1269) get state error: Connection is closed.
                  2024-10-24 19:15:11.357  - error: chromecast.0 (265) 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().
                  2024-10-24 19:15:11.350  - error: shelly.0 (602) unhandled promise rejection: DB closed
                  2024-10-24 19:15:11.351  - error: shelly.0 (602) Error: DB closed
                     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                     at Object.onceWrapper (node:events:634:26)
                     at Socket.emit (node:events:519:28)
                     at Socket.emit (node:domain:488:12)
                     at TCP.<anonymous> (node:net:339:12)
                  2024-10-24 19:15:11.351  - error: shelly.0 (602) DB closed
                  2024-10-24 19:15:11.361  - warn: frigate.0 (2496) get state error: Connection is closed.
                  .
                  .
                  .
                  2024-10-24 19:15:11.374  - warn: frigate.0 (2496) get state error: Connection is closed.
                  2024-10-24 19:15:11.393  - warn: frigate.0 (2496) Could not perform strict object check of state frigate.0.terrasse.history.02.data.box01: DB closed
                  2024-10-24 19:15:11.393  - warn: frigate.0 (2496) get state error: Connection is closed.
                  2024-10-24 19:15:11.393  - warn: frigate.0 (2496) Could not perform strict object check of state frigate.0.buero.history.05.end_time: DB closed
                  2024-10-24 19:15:11.393  - warn: frigate.0 (2496) get state error: Connection is closed.
                  2024-10-24 19:15:11.394  - error: frigate.0 (2496) Error extract keys: terrasse.history.03.data {"attributes":[],"box":[0.5099431818181818,0.11284722222222222,0.14914772727272727,0.6649305555555556],"region":[0.2159090909090909,0.017361111111111112,0.7840909090909091,0.9583333333333334],"score":0.83203125,"top_score":0.84375,"type":"object"}
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error extract keys: events.before.box01 182
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error: DB closed
                  2024-10-24 19:15:11.395  - error: frigate.0 (2496) Error extract keys: haustuer.history.03 2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.admin.0 killing pid 149
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.javascript.0 killing pid 237
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.telegram.0 killing pid 231
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.telegram.1 killing pid 244
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.chromecast.0 killing pid 265
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.shelly.0 killing pid 602
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.sonoff.0 killing pid 693
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.unifi.0 killing pid 11760
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.yeelight-2.0 killing pid 865
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.frigate.0 killing pid 2496
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.govee-app.0 killing pid 13532
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.iot.0 killing pid 954
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.jarvis.0 killing pid 969
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.logparser.0 killing pid 999
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.simple-api.0 killing pid 1019
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.smartcontrol.0 killing pid 1013
                  2024-10-24 19:15:11.961  - info: host.IoBroker stopInstance timeout system.adapter.sourceanalytix.0 killing pid 1027
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.tankerkoenig.0 killing pid 1034
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.text2command.0 killing pid 1072
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.traccar.0 killing pid 1112
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.trashschedule.0 killing pid 1127
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.virtualpowermeter.0 killing pid 1142
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.web.0 killing pid 1187
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.wiobrowser.0 killing pid 1223
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.wled.0 killing pid 1239
                  2024-10-24 19:15:11.962  - info: host.IoBroker stopInstance timeout system.adapter.weather-warnings.0 killing pid 1269
                  2024-10-24 19:15:12.012  - info: host.IoBroker instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.040  - info: host.IoBroker instance system.adapter.mihome.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.062  - info: host.IoBroker instance system.adapter.mqtt.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.085  - info: host.IoBroker instance system.adapter.opendtu.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.106  - info: host.IoBroker instance system.adapter.radar2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.142  - info: host.IoBroker instance system.adapter.shuttercontrol.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.172  - info: host.IoBroker instance system.adapter.tibberlink.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.188  - info: host.IoBroker instance system.adapter.tr-064.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.218  - info: host.IoBroker instance system.adapter.notification-manager.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.236  - info: host.IoBroker instance system.adapter.linux-control.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:12.756  - info: zigbee2mqtt.0 (894) terminating
                  2024-10-24 19:15:12.757  - info: zigbee2mqtt.0 (894) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-10-24 19:15:13.757  - info: zigbee2mqtt.0 (894) terminating with timeout
                  2024-10-24 19:15:13.799  - info: host.IoBroker stopInstance timeout system.adapter.zigbee2mqtt.0 killing pid 894
                  2024-10-24 19:15:13.825  - info: host.IoBroker instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.851  - info: host.IoBroker instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.873  - info: host.IoBroker instance system.adapter.javascript.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.895  - info: host.IoBroker instance system.adapter.chromecast.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.918  - info: host.IoBroker instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.945  - info: host.IoBroker instance system.adapter.yeelight-2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.976  - info: host.IoBroker instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:13.995  - info: host.IoBroker instance system.adapter.jarvis.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.027  - info: host.IoBroker instance system.adapter.logparser.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.051  - info: host.IoBroker instance system.adapter.smartcontrol.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.080  - info: host.IoBroker instance system.adapter.simple-api.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.110  - info: host.IoBroker instance system.adapter.sourceanalytix.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.130  - info: host.IoBroker instance system.adapter.tankerkoenig.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.161  - info: host.IoBroker instance system.adapter.traccar.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.178  - info: host.IoBroker instance system.adapter.trashschedule.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.235  - info: host.IoBroker instance system.adapter.wiffi-wz.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.287  - info: host.IoBroker instance system.adapter.wiobrowser.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.312  - info: host.IoBroker instance system.adapter.wled.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.328  - info: host.IoBroker instance system.adapter.ws.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.351  - info: host.IoBroker instance system.adapter.weather-warnings.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.369  - info: host.IoBroker instance system.adapter.govee-app.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.393  - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.393  - info: host.IoBroker instance system.adapter.telegram.0 terminated with code null ()
                  2024-10-24 19:15:14.411  - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGKILL
                  2024-10-24 19:15:14.411  - info: host.IoBroker instance system.adapter.telegram.1 terminated with code null ()
                  2024-10-24 19:15:14.438  - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.438  - info: host.IoBroker instance system.adapter.sonoff.0 terminated with code null ()
                  2024-10-24 19:15:14.455  - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.455  - info: host.IoBroker instance system.adapter.sayit.0 terminated with code null ()
                  2024-10-24 19:15:14.482  - warn: host.IoBroker instance system.adapter.text2command.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.482  - info: host.IoBroker instance system.adapter.text2command.0 terminated with code null ()
                  2024-10-24 19:15:14.501  - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.501  - info: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated with code null ()
                  2024-10-24 19:15:14.525  - warn: host.IoBroker instance system.adapter.web.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.525  - info: host.IoBroker instance system.adapter.web.0 terminated with code null ()
                  2024-10-24 19:15:14.553  - error: host.IoBroker 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:
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]: Error: DB closed
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:2998:37)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3057:29)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at processImmediate (node:internal/timers:485:21)
                  2024-10-24 19:15:14.553  - error: host.IoBroker 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:
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]: Error: DB closed
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:2998:37)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3057:29)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at processImmediate (node:internal/timers:485:21)
                  2024-10-24 19:15:14.553  - error: host.IoBroker 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:
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]: Error: DB closed
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:2998:37)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3057:29)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at processImmediate (node:internal/timers:485:21)
                  2024-10-24 19:15:14.553  - error: host.IoBroker 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:
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]: Error: DB closed
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:2998:37)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3057:29)
                  2024-10-24 19:15:14.553  - error: host.IoBroker Caught by controller[0]:     at processImmediate (node:internal/timers:485:21)
                  2024-10-24 19:15:14.553  - warn: host.IoBroker instance system.adapter.frigate.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.553  - info: host.IoBroker instance system.adapter.frigate.0 terminated with code null ()
                  2024-10-24 19:15:14.570  - warn: host.IoBroker instance system.adapter.unifi.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.570  - info: host.IoBroker instance system.adapter.unifi.0 terminated with code null ()
                  2024-10-24 19:15:14.598  - info: host.IoBroker instance system.adapter.influxdb.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-10-24 19:15:14.616  - info: host.IoBroker instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                  2024-10-24 19:15:14.698  - warn: host.IoBroker instance system.adapter.zigbee2mqtt.0 terminated due to SIGKILL
                  2024-10-24 19:15:14.698  - info: host.IoBroker instance system.adapter.zigbee2mqtt.0 terminated with code null ()
                  2024-10-24 19:15:21.795  - info: host.IoBroker instance system.adapter.vis-inventwo.0 terminated while should be started once
                  2024-10-24 19:15:25.639  - info: host.IoBroker force terminating
                  2024-10-24 19:18:58.906  - info: host.IoBroker iobroker.js-controller version 7.0.1 js-controller starting
                  2024-10-24 19:18:58.908  - info: host.IoBroker Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
                  2024-10-24 19:18:58.908  - info: host.IoBroker hostname: IoBroker, node: v20.18.0
                  2024-10-24 19:18:58.909  - info: host.IoBroker ip addresses: 10.1.1.10
                  2024-10-24 19:19:00.808  - info: host.IoBroker connected to Objects and States
                  2024-10-24 19:19:00.821  - info: host.IoBroker added notifications configuration of host
                  2024-10-24 19:19:01.785  - info: host.IoBroker 146 instances found
                  2024-10-24 19:19:01.859  - info: host.IoBroker starting 49 instances
                  

                  umgestiegen von Proxmox auf Unraid

                  1 Antwort Letzte Antwort
                  0
                  • FeuersturmF Online
                    FeuersturmF Online
                    Feuersturm
                    schrieb am zuletzt editiert von
                    #81

                    @foxriver76 update auf js-controller 7.0.2 lief ohne Probleme durch und System startet erfolgreich :-) Danke.

                    1 Antwort Letzte Antwort
                    0
                    • T Offline
                      T Offline
                      ticaki
                      schrieb am zuletzt editiert von ticaki
                      #82

                      Keine Ahnung ob das ein Fehler im jscontroller ist:

                      Vorwegnahme: läuft bei mir alles so wie es soll.

                      Problem:
                      Bin aus einer iobroker Proxmox VM in einen LXC umgezogen (priviligiert ohne nesting - das deaktivierte Nesting war falsch hab es später aktiviert, als dieses Problem schon behoben war).
                      Nachdem Rückspielen des Backups haben alle Adapter ausser admin, backup und noch einem auf "aus" gestanden. Beim Aktivieren kam dann:

                      2024-11-01 09:40:27.524 - info: host.iobroker-lxc "system.adapter.alexa2.0" enabled
                      2024-11-01 09:40:27.786 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 2907
                      2024-11-01 09:40:28.349 - error: alexa2.0 (2907) alexa2.0 already running
                      2024-11-01 09:40:28.350 - warn: alexa2.0 (2907) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                      2024-11-01 09:40:28.872 - error: host.iobroker-lxc instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                      2024-11-01 09:40:28.872 - info: host.iobroker-lxc Restart adapter system.adapter.alexa2.0 because enabled
                      

                      Wenn man jetzt nicht sofort deaktiviert und Fehler sucht kommt dann nach 20 sekunden das:

                      2024-11-01 09:40:58.982 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 3043
                      2024-11-01 09:40:59.705 - info: alexa2.0 (3043) starting. Version 3.26.7 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.0, js-controller: 7.0.2
                      2024-11-01 09:40:59.722 - info: alexa2.0 (3043) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
                      

                      Es kann am fehlenden Nesting gelegen haben, kenne mich damit aber nicht aus, wollte es aber zumindest beschreiben.

                      EDIT: hab "Nesting" klarer formuliert.

                      Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                      Spenden

                      Dr. BakteriusD foxriver76F 2 Antworten Letzte Antwort
                      0
                      • T ticaki

                        Keine Ahnung ob das ein Fehler im jscontroller ist:

                        Vorwegnahme: läuft bei mir alles so wie es soll.

                        Problem:
                        Bin aus einer iobroker Proxmox VM in einen LXC umgezogen (priviligiert ohne nesting - das deaktivierte Nesting war falsch hab es später aktiviert, als dieses Problem schon behoben war).
                        Nachdem Rückspielen des Backups haben alle Adapter ausser admin, backup und noch einem auf "aus" gestanden. Beim Aktivieren kam dann:

                        2024-11-01 09:40:27.524 - info: host.iobroker-lxc "system.adapter.alexa2.0" enabled
                        2024-11-01 09:40:27.786 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 2907
                        2024-11-01 09:40:28.349 - error: alexa2.0 (2907) alexa2.0 already running
                        2024-11-01 09:40:28.350 - warn: alexa2.0 (2907) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                        2024-11-01 09:40:28.872 - error: host.iobroker-lxc instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                        2024-11-01 09:40:28.872 - info: host.iobroker-lxc Restart adapter system.adapter.alexa2.0 because enabled
                        

                        Wenn man jetzt nicht sofort deaktiviert und Fehler sucht kommt dann nach 20 sekunden das:

                        2024-11-01 09:40:58.982 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 3043
                        2024-11-01 09:40:59.705 - info: alexa2.0 (3043) starting. Version 3.26.7 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.0, js-controller: 7.0.2
                        2024-11-01 09:40:59.722 - info: alexa2.0 (3043) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
                        

                        Es kann am fehlenden Nesting gelegen haben, kenne mich damit aber nicht aus, wollte es aber zumindest beschreiben.

                        EDIT: hab "Nesting" klarer formuliert.

                        Dr. BakteriusD Offline
                        Dr. BakteriusD Offline
                        Dr. Bakterius
                        Most Active
                        schrieb am zuletzt editiert von
                        #83

                        @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                        Und was soll das mit dem Controller zu tun haben? Offenbar läuft der Alexa2.0 Adapter ja schon. Du musst ihm nur mehr Zeit geben.

                        Es kann am Nesting gelegen haben

                        Ich habe bei mir Nesting aktiv - kein Problem. Und mein Container ist nur wegen dem rflink-Adapter privilegiert, weil der sonst nicht funktioniert.

                        T 1 Antwort Letzte Antwort
                        0
                        • Dr. BakteriusD Dr. Bakterius

                          @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                          Und was soll das mit dem Controller zu tun haben? Offenbar läuft der Alexa2.0 Adapter ja schon. Du musst ihm nur mehr Zeit geben.

                          Es kann am Nesting gelegen haben

                          Ich habe bei mir Nesting aktiv - kein Problem. Und mein Container ist nur wegen dem rflink-Adapter privilegiert, weil der sonst nicht funktioniert.

                          T Offline
                          T Offline
                          ticaki
                          schrieb am zuletzt editiert von
                          #84

                          @dr-bakterius sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                          @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                          Und was soll das mit dem Controller zu tun haben? Offenbar läuft der Alexa2.0 Adapter ja schon. Du musst ihm nur mehr Zeit geben.

                          Was soll das für eine Bemerkung sein, der Controller überwacht doppelt laufende Adapter und schreibt die Warnung ins Log.

                          Es kann am Nesting gelegen haben

                          Ich habe bei mir Nesting aktiv - kein Problem. Und mein Container ist nur wegen dem rflink-Adapter privilegiert, weil der sonst nicht funktioniert.

                          Ganz lesen, ich hatte es nicht aktiviert was zu anderen Problemen geführt hat, die mir erst später aufgefallen sind. Dann hab ich es aktiviert und diese Probleme waren dann behoben. Könnte sein, dass das fehlende Nesting auch zu der doppelt laufende Adaptermeldung geführt hat. Dafür kenn ich mich damit aber nicht genung aus. Meiner ist priviligiert damit ich mit smb arbeiten kann.

                          Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                          Spenden

                          Dr. BakteriusD 1 Antwort Letzte Antwort
                          0
                          • T ticaki

                            @dr-bakterius sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                            @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                            Und was soll das mit dem Controller zu tun haben? Offenbar läuft der Alexa2.0 Adapter ja schon. Du musst ihm nur mehr Zeit geben.

                            Was soll das für eine Bemerkung sein, der Controller überwacht doppelt laufende Adapter und schreibt die Warnung ins Log.

                            Es kann am Nesting gelegen haben

                            Ich habe bei mir Nesting aktiv - kein Problem. Und mein Container ist nur wegen dem rflink-Adapter privilegiert, weil der sonst nicht funktioniert.

                            Ganz lesen, ich hatte es nicht aktiviert was zu anderen Problemen geführt hat, die mir erst später aufgefallen sind. Dann hab ich es aktiviert und diese Probleme waren dann behoben. Könnte sein, dass das fehlende Nesting auch zu der doppelt laufende Adaptermeldung geführt hat. Dafür kenn ich mich damit aber nicht genung aus. Meiner ist priviligiert damit ich mit smb arbeiten kann.

                            Dr. BakteriusD Offline
                            Dr. BakteriusD Offline
                            Dr. Bakterius
                            Most Active
                            schrieb am zuletzt editiert von
                            #85

                            @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                            Ganz lesen, ich hatte es nicht aktiviert was zu anderen Problemen geführt hat

                            Naja, aus

                            @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                            priviligiert ohne nesting - ohne nesting war falsch

                            bin zumindest ich nicht schlau geworden. :thinking_face:

                            T 1 Antwort Letzte Antwort
                            0
                            • Dr. BakteriusD Dr. Bakterius

                              @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                              Ganz lesen, ich hatte es nicht aktiviert was zu anderen Problemen geführt hat

                              Naja, aus

                              @ticaki sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:

                              priviligiert ohne nesting - ohne nesting war falsch

                              bin zumindest ich nicht schlau geworden. :thinking_face:

                              T Offline
                              T Offline
                              ticaki
                              schrieb am zuletzt editiert von ticaki
                              #86

                              @dr-bakterius
                              so besser: (priviligiert ohne nesting - das deaktivierte Nesting war falsch hab es später aktiviert, als dieses Problem schon behoben war). ?

                              EDIT: und um das klarer zu beschreiben, die Adapter waren alle auf deaktiviert und eine Aktivierung hat die Warnung vor doppelt laufenden Adaptern erzeugt.

                              Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                              Spenden

                              1 Antwort Letzte Antwort
                              0
                              • T ticaki

                                Keine Ahnung ob das ein Fehler im jscontroller ist:

                                Vorwegnahme: läuft bei mir alles so wie es soll.

                                Problem:
                                Bin aus einer iobroker Proxmox VM in einen LXC umgezogen (priviligiert ohne nesting - das deaktivierte Nesting war falsch hab es später aktiviert, als dieses Problem schon behoben war).
                                Nachdem Rückspielen des Backups haben alle Adapter ausser admin, backup und noch einem auf "aus" gestanden. Beim Aktivieren kam dann:

                                2024-11-01 09:40:27.524 - info: host.iobroker-lxc "system.adapter.alexa2.0" enabled
                                2024-11-01 09:40:27.786 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 2907
                                2024-11-01 09:40:28.349 - error: alexa2.0 (2907) alexa2.0 already running
                                2024-11-01 09:40:28.350 - warn: alexa2.0 (2907) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                2024-11-01 09:40:28.872 - error: host.iobroker-lxc instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                2024-11-01 09:40:28.872 - info: host.iobroker-lxc Restart adapter system.adapter.alexa2.0 because enabled
                                

                                Wenn man jetzt nicht sofort deaktiviert und Fehler sucht kommt dann nach 20 sekunden das:

                                2024-11-01 09:40:58.982 - info: host.iobroker-lxc instance system.adapter.alexa2.0 in version "3.26.7" started with pid 3043
                                2024-11-01 09:40:59.705 - info: alexa2.0 (3043) starting. Version 3.26.7 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.18.0, js-controller: 7.0.2
                                2024-11-01 09:40:59.722 - info: alexa2.0 (3043) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
                                

                                Es kann am fehlenden Nesting gelegen haben, kenne mich damit aber nicht aus, wollte es aber zumindest beschreiben.

                                EDIT: hab "Nesting" klarer formuliert.

                                foxriver76F Offline
                                foxriver76F Offline
                                foxriver76
                                Developer
                                schrieb am zuletzt editiert von
                                #87

                                @ticaki Rückspielen eines Backups .. Proxmox Backup oder ioBroker Backup

                                Videotutorials & mehr

                                Hier könnt ihr mich unterstützen.

                                T 1 Antwort Letzte Antwort
                                0
                                • foxriver76F foxriver76

                                  @ticaki Rückspielen eines Backups .. Proxmox Backup oder ioBroker Backup

                                  T Offline
                                  T Offline
                                  ticaki
                                  schrieb am zuletzt editiert von ticaki
                                  #88

                                  @foxriver76

                                  iobroker backup

                                  hergang:

                                  • lxc erzeugt debian bookworm
                                  • sudo user erzeugt
                                  • curl installiert
                                  • iobroker installiert
                                  • iob fix ausgeführt
                                  • redis eingestellt (iob setup custom) Das ist aber nicht nötig, hat den redis-server aus dem backup genommen.
                                  • iobroker backup eingespielt

                                  Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                                  Spenden

                                  ? 1 Antwort Letzte Antwort
                                  0
                                  • T ticaki

                                    @foxriver76

                                    iobroker backup

                                    hergang:

                                    • lxc erzeugt debian bookworm
                                    • sudo user erzeugt
                                    • curl installiert
                                    • iobroker installiert
                                    • iob fix ausgeführt
                                    • redis eingestellt (iob setup custom) Das ist aber nicht nötig, hat den redis-server aus dem backup genommen.
                                    • iobroker backup eingespielt
                                    ? Offline
                                    ? Offline
                                    Ein ehemaliger Benutzer
                                    schrieb am zuletzt editiert von
                                    #89

                                    @ticaki @foxriver76

                                    Bin vor 2 Wochen vom Docker auf einen LXC Bookworm umgezogen, mit Js-Controller 7.0.1.
                                    Gleiches vorgehen, hat alles einwandfrei funktioniert, den iob fix hab ich mir aber gespart - ich hab immer noch in mir, dass man das nur bei Problemen machen soll :)
                                    Nach dem Restore, das erstaunlich schnell ging (68 Adapter, knapp 60000 Objects and States), liefen nach und nach die Adapter, wurden im Admin aber als disabled angezeigt.
                                    Einmal Reboot des LXC, und seitdem ist alles gut..

                                    Ich finds immer wieder schoen, wie einfach man iobroker installieren und umziehen kann.. ich glaub, in den letzten Jahren gabs nix, worauf ich iobroker nicht hatte.. :)
                                    Das upgrade auf js-controller 7.0.2 hab ich gewohnter Weise in der Console gemacht.. lief einwandfrei durch.

                                    T 1 Antwort Letzte Antwort
                                    0
                                    • ? Ein ehemaliger Benutzer

                                      @ticaki @foxriver76

                                      Bin vor 2 Wochen vom Docker auf einen LXC Bookworm umgezogen, mit Js-Controller 7.0.1.
                                      Gleiches vorgehen, hat alles einwandfrei funktioniert, den iob fix hab ich mir aber gespart - ich hab immer noch in mir, dass man das nur bei Problemen machen soll :)
                                      Nach dem Restore, das erstaunlich schnell ging (68 Adapter, knapp 60000 Objects and States), liefen nach und nach die Adapter, wurden im Admin aber als disabled angezeigt.
                                      Einmal Reboot des LXC, und seitdem ist alles gut..

                                      Ich finds immer wieder schoen, wie einfach man iobroker installieren und umziehen kann.. ich glaub, in den letzten Jahren gabs nix, worauf ich iobroker nicht hatte.. :)
                                      Das upgrade auf js-controller 7.0.2 hab ich gewohnter Weise in der Console gemacht.. lief einwandfrei durch.

                                      T Offline
                                      T Offline
                                      ticaki
                                      schrieb am zuletzt editiert von
                                      #90

                                      @ilovegym
                                      Bei mir sind sie nicht gestartet ansonsten wie gesagt alles gut. Hab jedoch den lcx im Backup prozess (nach einn paar minuten) neu gestartet da ich keinen zugriff auf die Oberfläche bekommen habe. Das kann aber ein Nutzerfehler gewesen sein. Hab ihn auch neu gestartet als ich gesehen habe das da nix an ist und im Log auch nichts startet.

                                      Scheint aber anscheinend ein Einzelfall gewesen zu sein. Danke für die Klarstellung.

                                      Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                                      Spenden

                                      1 Antwort Letzte Antwort
                                      0
                                      • D DLehmann

                                        @foxriver76

                                        Leider noch nicht. Der Fehler sieht jetzt aber anders aus. Eine Umstellung erfolgt aber nicht. iobroker ist gestoppt und der neue iob fix lief auch erfolgreich drüber.

                                        dirk@iobroker:~$ iob setup custom
                                        Current configuration:
                                        - Objects database:
                                          - Type: jsonl
                                          - Host/Unix Socket: 127.0.0.1
                                          - Port: 9001
                                        - States database:
                                          - Type: jsonl
                                          - Host/Unix Socket: 127.0.0.1
                                          - Port: 9000
                                        - Data Directory: ../../iobroker-data/
                                        
                                        Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]: r
                                        
                                        When Objects and Files are stored in a Redis database please consider the following:
                                        1. All data will be stored in RAM, make sure to have enough free RAM available!
                                        2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss!
                                        3. The Redis persistence files can get big, make sure not to use an SD card to store them.
                                        
                                        Host / Unix Socket of objects DB(redis), default[127.0.0.1]: 
                                        Port of objects DB(redis), default[6379]: 
                                        Do you use a TLS connection for your "objects" redis-server? [y/N]:
                                        Type of states DB [(j)sonl, (f)file, (r)edis, ...], default [redis]: 
                                        Host / Unix Socket of states DB (redis), default[127.0.0.1]: 
                                        Port of states DB (redis), default[6379]: 
                                        Do you use a TLS connection for your "states" redis-server? [y/N]:
                                        Host name of this machine [iobroker]: 
                                        Please choose if this is a Master/single host (enter "m") or a Slave host (enter "S") you are about to edit. For Slave hosts the data migration will be skipped. [S/m]: m
                                        
                                        Important: Using redis for the Objects database is only supported
                                        with js-controller 2.0 or higher!
                                        When your system consists of multiple hosts please make sure to have
                                        js-controller 2.0 or higher installed on ALL hosts *before* continuing!
                                        
                                        
                                        Important #2: If you already did the migration on an other host
                                        please *do not* migrate again! This can destroy your system!
                                        
                                        
                                        Important #3: The process will migrate all files that were officially
                                        uploaded into the ioBroker system. If you have manually copied files into
                                        iobroker-data/files/... into own directories then these files will NOT be
                                        migrated! Make sure all files are in adapter directories inside the files
                                        directory!
                                        
                                        
                                        Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y/N]: y
                                        
                                        Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y
                                        
                                        Connecting to previous DB "jsonl/jsonl"...
                                        Creating backup ...
                                        This can take some time ... please be patient!
                                        host.iobroker 15138 objects saved
                                        host.iobroker 12349 states saved
                                        host.iobroker Validating backup ...
                                        host.iobroker The backup is valid!
                                        Backup created: /opt/iobroker/backups/2024_10_22-17_58_59_backupiobroker-migration.tar.gz
                                        updating conf/iobroker.json
                                        
                                        Connecting to new DB "redis/redis" (can take up to 20s) ...
                                         Cannot read system.config: null (OK when migrating or restoring)
                                        Restore backup ...
                                        This can take some time ... please be patient!
                                        host.iobroker Cannot find extracted file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json" or "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json"
                                        Error happened during restore. Exit-Code: 26
                                        
                                        restoring conf/iobroker.json
                                        
                                        D Online
                                        D Online
                                        DLehmann
                                        schrieb am zuletzt editiert von
                                        #91

                                        @dlehmann

                                        Hier noch eine Rückmeldung zu meinem Thema mit der Umstellung auf redis.

                                        Ich hatte jetzt Zeit, das Update auf 7.0.2 zu machen. Danach lief die Umstellung auf redis erfolgreich durch und iobroker läuft jetzt mit redis Datenbank.

                                        1 Antwort Letzte Antwort
                                        1
                                        • FeuersturmF Online
                                          FeuersturmF Online
                                          Feuersturm
                                          schrieb am zuletzt editiert von Feuersturm
                                          #92

                                          @foxriver76
                                          Update von js-controller 7.0.2 auf 7.0.3 über admin ui v7.2.6 mit vorherigem iob fix lief ohne Probleme :)

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


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          500

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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