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. ioBroker Allgemein
  4. js-controller 5.0.x jetzt für alle User im STABLE!

NEWS

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

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

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

js-controller 5.0.x jetzt für alle User im STABLE!

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
js-controllerstableupgrade
509 Beiträge 82 Kommentatoren 139.7k Aufrufe 65 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.
  • DuffyD Duffy

    @thomas-braun

    Hallo thomas-braun,

    ich habe mir das jetzt alles mal durchgelesen und mir raucht jetzt echt der Kopf, ich habe da einfach zu wenig Ahnung von der Materie.
    Deshalb meine Frage an dich, du warst mir schon oft eine grosse hilfe ob man das Update durch klicken auf den Update Button starten soll, muss, kann. (Siehe Bild)

    Screenshot 2023-09-15 153256.png

    Die ganzen Adapter die heute neu als Stable angeboten wurden habe ich gemacht und meine Node.js ist v18.17.1
    Aktuell habe ich auf meinem Raspberry Pi noch Bullseye laufen.
    Backup ist mit Backitup gemacht.

    Kann ich unter den Voraussetzungen ein Update wagen? Ich frage lieber vorher bevor ich Tage lang versuchen muss alles neu aufzusetzen.

    Viele Grüße Duffy

    Edit:

    Habe bei meinem Test Pi auf den "Knopf" gedrückt und es kam eine Installationsanleitung:

    cd /opt/iobroker/
    sudo iobroker stop
    sudo iobroker upgrade
    sudo iobroker upgrade self
    sudo iobroker start

    Sollte es also mit den Befehlen, die ja vergleichbar sind zum ersten Post, klappen?

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

    @duffy sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

    klappen?

    Mit sudo klappt da nix. Nur alles zusammen.

    Kann ich unter den Voraussetzungen ein Update wagen?

    Vermutlich. Ist aber auch kein Thema für diesen Thread.

    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

    DuffyD 1 Antwort Letzte Antwort
    0
    • DuffyD Duffy

      @djmarc75

      Die u.A die Befehle kamen als ich auf den "Knopf" bgedrückt habe aus meinem Post.

      Anwesisung.png

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

      @duffy sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

      Die u.A die Befehle kamen als ich auf den "Knopf" bgedrückt habe aus meinem Post.

      Du hast aber vermutlich keine manuelle Installation als root gemacht sondern das Skript verwendet.

      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
      • Thomas BraunT Thomas Braun

        @duffy sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

        klappen?

        Mit sudo klappt da nix. Nur alles zusammen.

        Kann ich unter den Voraussetzungen ein Update wagen?

        Vermutlich. Ist aber auch kein Thema für diesen Thread.

        DuffyD Offline
        DuffyD Offline
        Duffy
        schrieb am zuletzt editiert von
        #79

        @thomas-braun

        Sorry, hate nur hier gefragt weil es hier ja um das Update geht.

        Gruß Duffy

        Nix besonderes; iob auf Respberry pi 4 (8GB) mit 32 GB SSD
        Node.js: v22.21.0
        NPM: 10.9.4
        js-controller 7.0.7
        Linux: Trixie

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • DuffyD Duffy

          @thomas-braun

          Sorry, hate nur hier gefragt weil es hier ja um das Update geht.

          Gruß Duffy

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

          @duffy

          Die Befehle, aber ohne sudo vorweg.

          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

          DuffyD 1 Antwort Letzte Antwort
          0
          • wendy2702W wendy2702

            @x4n70 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

            Hat jemand den linux-control mal getestet? Er scheint ja nicht mehr gepflegt zu werden, sieht für mich in GitHub ziemlich eindeutig aus. Aber funktioniert er denn unter 5.x?

            Läuft bei mir auch noch

            S Offline
            S Offline
            sunny9999
            schrieb am zuletzt editiert von
            #81

            @wendy2702 @x4N70 @Latzi

            bei mir leider nicht mehr haut folgende Fehler raus :

            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	info	Restart adapter system.adapter.linux-control.0 because enabled
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[22]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[22]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[22]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[22]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[22]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[21]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[21]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[21]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[21]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[20]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[19]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[19]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[19]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[19]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[19]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[18]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[18]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[18]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[18]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[18]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[17]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.354	error	Caught by controller[17]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[17]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[17]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[17]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[16]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[16]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[16]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[16]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[15]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[14]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[14]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[13]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[12]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[12]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.353	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[11]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[10]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[10]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.350	error	Caught by controller[10]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[9]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[9]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[9]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[8]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[8]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[8]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[7]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[7]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[7]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[6]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[6]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[6]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[6]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[5]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[5]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[5]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[4]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[4]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[4]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[3]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[3]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[3]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[2]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.349	error	Caught by controller[2]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[2]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[2]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[1]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[1]: 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:
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[0]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	Caught by controller[0]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            host.IOBROKER-MASTER
            2023-09-15 16:16:45.348	error	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:
            
            linux-control.0
            2023-09-15 16:16:44.899	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.899	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.899	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.898	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.897	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.897	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.896	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.896	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.888	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.888	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.888	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.887	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.885	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.885	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.885	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.885	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.875	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.875	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.875	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.874	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.872	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.872	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.872	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.872	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.857	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.857	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.857	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.857	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.854	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.854	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.854	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.854	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.795	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.795	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.794	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.794	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.792	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.792	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.791	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.791	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.773	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.772	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.772	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.772	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.770	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.770	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.769	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.769	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.677	error	The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.677	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.677	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.677	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.670	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.670	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.670	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.669	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.667	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.667	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.666	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.666	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.636	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.635	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.635	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.635	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.633	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.632	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.632	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.632	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.611	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.611	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.610	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.610	error	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().
            
            linux-control.0
            2023-09-15 16:16:44.576	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
            
            linux-control.0
            2023-09-15 16:16:44.575	info	terminating
            
            linux-control.0
            2023-09-15 16:16:44.575	info	cleaned everything up...
            
            linux-control.0
            2023-09-15 16:16:44.558	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.558	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
            
            linux-control.0
            2023-09-15 16:16:44.481	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
            
            linux-control.0
            2023-09-15 16:16:44.480	error	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().
            
            linux-control.0
            2023-09-15 16:16:38.470	info	getting data from Monitor-PI (192.168.10.25:22, Adapter start)
            
            linux-control.0
            2023-09-15 16:16:38.469	info	getting data from IO-SLAVE (192.168.10.17:22, Adapter start)
            
            linux-control.0
            2023-09-15 16:16:38.469	info	getting data from RDP-PI (192.168.10.65:22, Adapter start)
            
            linux-control.0
            2023-09-15 16:16:38.468	info	getting data from LABEL-PI (192.168.10.66:22, Adapter start)
            
            linux-control.0
            2023-09-15 16:16:38.431	info	starting. Version 1.1.6 (non-npm: Scrounger/ioBroker.linux-control#59f578f3402850684ba8767a24a9ff288b05a3f0) in /opt/iobroker/node_modules/iobroker.linux-control, node: v18.16.1, js-controller: 5.0.12
            

            Schon deinstalliert und neu installiert.

            Hab auch noch Probleme mit email und samsung_tizen adaptern..... Rest rennt
            Jemand noch nen Tip ?
            Grüße

            Sunny

            mcm1957M Thomas BraunT 2 Antworten Letzte Antwort
            0
            • S sunny9999

              @wendy2702 @x4N70 @Latzi

              bei mir leider nicht mehr haut folgende Fehler raus :

              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	info	Restart adapter system.adapter.linux-control.0 because enabled
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[22]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[22]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[22]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[22]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[22]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[21]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[21]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[21]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[21]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[20]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[19]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[19]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[19]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[19]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[19]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[18]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[18]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[18]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[18]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[18]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[17]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.354	error	Caught by controller[17]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[17]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[17]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[17]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[16]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[16]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[16]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[16]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[15]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[14]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[14]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[13]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[12]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[12]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.353	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[11]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[10]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[10]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.350	error	Caught by controller[10]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[9]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[9]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[9]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[8]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[8]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[8]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[7]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[7]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[7]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[6]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[6]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[6]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[6]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[5]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[5]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[5]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[4]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[4]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[4]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[3]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[3]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[3]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[2]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.349	error	Caught by controller[2]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[2]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[2]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[1]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[1]: 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:
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[0]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	Caught by controller[0]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              host.IOBROKER-MASTER
              2023-09-15 16:16:45.348	error	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:
              
              linux-control.0
              2023-09-15 16:16:44.899	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.899	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.899	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.898	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.897	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.897	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.896	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.896	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.888	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.888	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.888	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.887	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.885	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.885	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.885	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.885	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.875	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.875	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.875	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.874	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.872	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.872	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.872	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.872	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.857	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.857	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.857	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.857	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.854	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.854	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.854	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.854	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.795	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.795	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.794	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.794	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.792	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.792	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.791	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.791	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.773	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.772	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.772	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.772	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.770	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.770	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.769	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.769	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.677	error	The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.677	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.677	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.677	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.670	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.670	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.670	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.669	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.667	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.667	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.666	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.666	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.636	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.635	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.635	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.635	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.633	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.632	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.632	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.632	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.611	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.611	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.610	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.610	error	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().
              
              linux-control.0
              2023-09-15 16:16:44.576	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
              
              linux-control.0
              2023-09-15 16:16:44.575	info	terminating
              
              linux-control.0
              2023-09-15 16:16:44.575	info	cleaned everything up...
              
              linux-control.0
              2023-09-15 16:16:44.558	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.558	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
              
              linux-control.0
              2023-09-15 16:16:44.481	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
              
              linux-control.0
              2023-09-15 16:16:44.480	error	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().
              
              linux-control.0
              2023-09-15 16:16:38.470	info	getting data from Monitor-PI (192.168.10.25:22, Adapter start)
              
              linux-control.0
              2023-09-15 16:16:38.469	info	getting data from IO-SLAVE (192.168.10.17:22, Adapter start)
              
              linux-control.0
              2023-09-15 16:16:38.469	info	getting data from RDP-PI (192.168.10.65:22, Adapter start)
              
              linux-control.0
              2023-09-15 16:16:38.468	info	getting data from LABEL-PI (192.168.10.66:22, Adapter start)
              
              linux-control.0
              2023-09-15 16:16:38.431	info	starting. Version 1.1.6 (non-npm: Scrounger/ioBroker.linux-control#59f578f3402850684ba8767a24a9ff288b05a3f0) in /opt/iobroker/node_modules/iobroker.linux-control, node: v18.16.1, js-controller: 5.0.12
              

              Schon deinstalliert und neu installiert.

              Hab auch noch Probleme mit email und samsung_tizen adaptern..... Rest rennt
              Jemand noch nen Tip ?
              Grüße

              Sunny

              mcm1957M Offline
              mcm1957M Offline
              mcm1957
              schrieb am zuletzt editiert von
              #82

              Es gab da ein issue beim linux control

              https://github.com/Scrounger/ioBroker.linux-control/issues/49

              Keine Ahnung ob relevant für dein Problem. Abercschau mal rein.

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

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

              LESEN - gute Forenbeitrage

              1 Antwort Letzte Antwort
              0
              • S sunny9999

                @wendy2702 @x4N70 @Latzi

                bei mir leider nicht mehr haut folgende Fehler raus :

                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	info	Restart adapter system.adapter.linux-control.0 because enabled
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[22]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[22]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[22]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[22]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[22]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[21]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[21]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[21]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[21]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[20]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[19]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[19]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[19]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[19]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[19]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[18]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[18]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[18]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[18]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[18]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[17]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.354	error	Caught by controller[17]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[17]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[17]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[17]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[16]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[16]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[16]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[16]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[15]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[14]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[14]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[13]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[12]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[12]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.353	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[11]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[10]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[10]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.350	error	Caught by controller[10]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[9]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[9]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[9]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[8]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[8]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[8]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[7]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[7]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[7]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[6]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[6]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[6]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[6]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[5]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[5]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[5]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[4]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[4]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[4]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[3]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[3]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[3]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[2]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.349	error	Caught by controller[2]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[2]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[2]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[1]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[1]: 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:
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[0]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15)
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	Caught by controller[0]: Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                host.IOBROKER-MASTER
                2023-09-15 16:16:45.348	error	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:
                
                linux-control.0
                2023-09-15 16:16:44.899	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.899	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.899	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.898	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.897	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.897	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.896	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.896	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.888	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.888	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.888	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.887	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.885	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.885	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.885	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.885	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.875	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.875	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.875	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.874	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.872	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.872	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.872	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.872	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.857	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.857	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.857	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.857	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.854	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.854	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.854	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.854	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.795	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.795	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.794	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.794	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.792	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.792	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.791	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.791	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.773	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.772	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.772	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.772	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.770	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.770	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.769	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.769	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.677	error	The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.677	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.677	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.start" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.677	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.670	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.670	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.670	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.669	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.667	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.667	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.666	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.666	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.636	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.635	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.635	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.635	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.633	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.632	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.632	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.632	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.611	error	The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.611	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.610	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.stop" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.610	error	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().
                
                linux-control.0
                2023-09-15 16:16:44.576	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                
                linux-control.0
                2023-09-15 16:16:44.575	info	terminating
                
                linux-control.0
                2023-09-15 16:16:44.575	info	cleaned everything up...
                
                linux-control.0
                2023-09-15 16:16:44.558	error	The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.558	error	Error: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2497:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1108:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2023-09-15 16:16:44.481	error	unhandled promise rejection: The pattern "io.linux-control.0.Monitor-PI.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2023-09-15 16:16:44.480	error	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().
                
                linux-control.0
                2023-09-15 16:16:38.470	info	getting data from Monitor-PI (192.168.10.25:22, Adapter start)
                
                linux-control.0
                2023-09-15 16:16:38.469	info	getting data from IO-SLAVE (192.168.10.17:22, Adapter start)
                
                linux-control.0
                2023-09-15 16:16:38.469	info	getting data from RDP-PI (192.168.10.65:22, Adapter start)
                
                linux-control.0
                2023-09-15 16:16:38.468	info	getting data from LABEL-PI (192.168.10.66:22, Adapter start)
                
                linux-control.0
                2023-09-15 16:16:38.431	info	starting. Version 1.1.6 (non-npm: Scrounger/ioBroker.linux-control#59f578f3402850684ba8767a24a9ff288b05a3f0) in /opt/iobroker/node_modules/iobroker.linux-control, node: v18.16.1, js-controller: 5.0.12
                

                Schon deinstalliert und neu installiert.

                Hab auch noch Probleme mit email und samsung_tizen adaptern..... Rest rennt
                Jemand noch nen Tip ?
                Grüße

                Sunny

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

                @sunny9999 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                ices.●.rest

                Dürfte ein illegales Zeichen an der Stelle sein.

                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
                • foxriver76F foxriver76

                  Hallo ioBroker-Community,

                  Heute möchten wir Euch den js-controller 5.0 endlich auch im STABLE Repository zur Verfügung stellen. Dieser Post enthält alle wichtigen Infos. Bitte unbedingt lesen!!
                  Wir bedanken uns bei allen Usern die bisher die neue Version bereits als Alpha oder Beta getestet und Feedback gegeben haben.

                  Node.js Versions-Anforderungen
                  In diesem Release entfällt Node.js 12.x welches seit April letztem Jahr nicht mehr gepflegt wird und Node.js 14.x welches seit April diesem Jahres EOL ist. Node.js 18.x ist dazugekommen. Die unterstützten Node.js Versionen sind: 16.4.0+ und 18.x und nach aktuellem Stand Node.js 20.x, wobei hier noch erfahrungen fehlen. Die empfohlene Node.js Version für ioBroker haben wir vor kurzem auf 18.x angehoben.
                  Bitte beachtet weiterhin bei Node.js Updates die Anleitung im Forum unter https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-14-16-und-18 !

                  Informationen zur Version
                  Es gibt EINIGE Adapter die aktualisiert werden müssen!! Bitte weiter unten lesen!

                  In dieser Version wurde die Umstellung des Quellcodes auf TypeScript sehr stark vorangetrieben (inzwischen bei 88%), wodurch am Ende die Stabilität weiter steigt weil viele Code-Fehler nicht mehr auftreten können. Natürlich sind neben Optimierungen und Fehlerbehebungen auch ein paar neue Features hinzugekommen. Auch wenn mit dieser Version keine neuen Prüfungen hinzukommen, die zu Log-Ausgaben bei Adaptern führen, meldet aktuelle Logausgaben bitte weiterhin bei den Adaptern.

                  Detailliertere Informationen zu allen Änderungen und Features findet Ihr weiter unten und im Changelog.

                  Für die aktive Mitarbeit an dieser Version des js-controller bedanke mich diesmal wieder besonders bei Apollon77, AlCalzone und natürlich Bluefox und auch ein paar weiteren Entwicklern!

                  ACHTUNG backups inkompatibel bei Downgrades!!

                  Neben der Node.js Version gibt es eine wichtige Inkompatibilität: Backups die mit der 5.0 des js-controller erstellt wurden lassen sich nicht mit einem js-controller 4 oder kleiner wieder restoren!

                  Darüber hinaus ist der js-controller 5.0 generell kompatibel mit allen bestehenden ioBroker-Systemen. Ein Update von der 2.0/2.1/2.2/3.x ist problemlos möglich. Wir empfehlen allerings vor dem Update auf die 5.0 idealerweise ein Update auf die 4.0 und vorher auf 3.3.x durchzuführen, da ein Downgrade nach einem erfolgten Update nur auf eine 3.3.x möglich ist (siehe FAQ)! Nur die Node.js Version muss weiterhin mindestens 16.x sein, wie oben bereits ausgeführt. Wer überlegt die Node.js Version anzuheben bitte weiter unten im Abschnitt "Was ist zu testen" lesen 🙂

                  Aufgrund einiger internen Umstellungen brauchen wieder einige Adapter Updates. Diese sollten am besten VOR dem Update installiert werden!
                  Bitte dazu die Informationen weiter unten beachten!


                  Installation


                  VOR der Installation

                  Wie bei jedem Upgrade dieser Art: Bitte macht ein Backup! iobroker backup bzw kopieren des iobroker-data Verzeichnisses reichen an sich aus. Bitte nicht das node_modules Verzeichnis einfach kopieren, da sonst symbolische Links kaputt gehen können, was zu größeren Problemen danach führt. Eine alte 4.0.x-Version des js-controller kann im Notfall einfach wieder per npm install iobroker.js-controller@version ("version" durch die gewünschte Versionsnummer ersetzen) installiert werden und sollte alles wieder herstellen (Vorheriger Stable Stand ist die 4.0.24)

                  Nötige Adapter-Aktualisierungen

                  Am besten dennoch VOR dem js-controller Update alle verfügbaren Adapter-Updates prüfen und alle Updates installieren, die im Changelog auf Optimierungen oder Anpassungen für den js-controller 4.0 oder höher hinweisen.

                  Diesmal sind doch einige Adapter auf der Liste die man updaten muss -falls installiert! Siehe Spoiler!

                  • ✅ acme - required: none / 0.1.0 - released
                  • ✅ admin - required: 6.8.0 - released
                  • ✅ anelhut - required: 1.0.15 - released
                  • ✅b-control-em - required: 0.3.1 - released
                  • ⚪ bosch-ebike - required: none
                  • ✅ cul - required: 2.2.0 - released (no change)
                  • ✅ daikin-cloud - required: 0.3.0 - released
                  • ✅ doorbird - required: 0.1.7 - newer released
                  • ✅ ds18b20 - required: 2.0.4 - released
                  • ✅ energymanager - required: 1.4.2 - released
                  • ⚪ enigma2 - required: none - not at stable yet
                  • ✅ fakeroku - required: 0.2.2+ - released
                  • ✅ fhem - required: 2.0.5 - released
                  • ✅ history - required: 2.2.6 - released
                  • ✅ iqontrol - required: 2.3.0 - released
                  • ⚪ javascript - required: none
                  • 🚫 km200 - deprecated - Ersatz: ems-esp
                  • ✅ lgtv - required: 1.1.12 - released
                  • ❗linux-control - required: ???
                  • ✅ maxcul - required: 1.3.1 (no change)
                  • ⚪ miio - required: none - not at stable
                  • ✅ mydlink - required: 1.3.4 - released
                  • ✅ nanoleaf-lightpanales - required: 1.4.0 - released
                  • ✅ node-red - required: 4.03+ (no change)
                  • ✅ notification.manager - required: 0.1.1 - released
                  • ✅ pi-hole - required: 1.3.6+ - released
                  • ✅ ping - required: 1.6.2 - released
                  • ✅ pushbullet - required: 1.0.1 - released
                  • 🚫 samsung_tyzen - stale repo - deprecated with js-controller 5
                  • ✅ socketio - required: 6.5.2 - released
                  • ✅ stiebel-isg - required: 1.7.6+ - newer released
                  • ✅ systeminfo - required: 1.0.0 - released
                  • ✅ viessmann - required: 1.4.4+ - released
                  • ✅ web - required: 6.1.0 - released
                  • ✅ ws - required: 2.5.3 - released
                  • ✅yahka - required: 1.0.1 - newer version released
                  • ✅ zigbee - required: 1.8.23 - released
                  Achtung: MASTER-Systeme Reihenfolgen beachten!

                  Bei einem Multi-Host-System, welches auf js-controller 2.2, 3.x oder 4.0.x läuft, ist es beim Update auf Version 5.0 empfohlen, zuerst das Master-System zu aktualisieren. Der Master muss dann wieder gestartet werden. Die Slaves werden danach aktualisiert!

                  Bei Updates von Master/Slave-Systemen mit js-controller 1.5 oder früher Bitte die jeweiligen Update Threads der empfohlenen Zwischenversionen prüfen.

                  Windows
                  Generell muss das Update manuell via npm installiert werden.

                  Hierzu im ioBroker-Verzeichnis nach stoppen des ioBroker den Befehl iob upgrade self ausführen.

                  Linux

                  • ioBroker stoppen (iobroker stop)
                  • Prüfen das keine Prozesse (Adapter, Backups) mehr laufen (ps auxww|grep io und auch ps auxww|grep backup ). Es passiert manchmal das trotz dem Stoppen noch Zombies zurückbleiben
                  • cd /opt/iobroker
                  • Das Update erfolgt via iob upgrade self
                  • ioBroker starten (iobroker start)

                  Bei Fehlern:
                  Wenn bei der Installation Fehler wegen fehlender Zugriffsrechte auftreten, am besten den Installation-Fixer (iobroker fix wer schon einen js-controller 2.x oder höher hat, alternativ weiterhin manuell via curl -sL https://iobroker.net/fix.sh | bash -) nutzen und die Installation wiederholen.
                  Falls es auch danach noch Fehler gibt, bitte die Installation erneut mittels sudo -H -u iobroker npm install iobroker.js-controller versuchen. Bitte berichtet solche Fälle hier im Thread.

                  NACH der Installation

                  Wenn alles klappt merkt Ihr ausser der höheren Versionsnummer in der Host-Ansicht im Admin keinen Unterschied. Alles funktioniert weiterhin wie vorher. Alle Adapterinstanzen starten und funktionieren. Wenn das so ist hat alles geklappt.

                  Falls im Log Warn-Meldungen auftauchen mit dem Hinweis diese an den Entwickler zu senden, dann bitte schauen welcher Adapter es ist und entsprechend dort Issues bitte anlegen!


                  Was hat sich geändert, was besonders ansehen/beachten?


                  Neben einiger weiterer Bugfixes gibt es folgende Änderungen und Fixes zu erwähnen:

                  • generell siehe Changelog, speziell auch für die Features
                  • generell bitte im CLI und auch sonst überall drüber schauen. Die Typescript Umstellungen haben sehr viel Code angefasst.
                  • Falls jemand sporadisch Alias Fehler im Log hatte bitte versuchen diese mit der neuen version wieder zu provoziere und rückmelden

                  Speziell die Entwickler sollten bitte die genannten Deprecations und neuen Features anschauen und beachten.

                  Wie bereits gesagt, viele Änderungen fanden hinter den Kulissen statt. Hier für Interessierte als Spoiler eine Zusammenfassung:

                  5.0. Release Jana

                  BREAKING CHANGES

                  • Support for Node.js 12 and 14 is dropped! Supported are Node.js 16.4.0+ and 18.x and hopefully 20.x
                  • Backups created with the new js-controller version cannot be restored on hosts with lower js-controller version!
                  • Update recommended npm version to 8
                  • Deprecate binary states, Adapters will change to use Files instead!

                  Features

                  • (foxriver76) Show npm error message on failing adapter installations and update also without debug parameter
                  • (foxriver76) Introduce iobroker setting (dnsResolution) to choose between verbatim and ipv4 first dns resolution order
                  • (foxriver76) Add support for windows for iob fix
                  • (bluefox) Added CLI option to restart/start/stop all instances of an adapter (e.g. iob stop admin now also works)
                  • (foxriver76) Allow to use iob host oldname command when new host already exists but has no instances
                  • (foxriver76) Added an admin notification if redis is misconfigured and info how to fix it
                  • (foxriver76) Enable upgrade of js-controller via Admin UI (Linux only)

                  Optimizations and Fixes

                  • (foxriver76) Speedup "getStates" calls with many IDs often used by visualizations: JSONL 17 times faster, Redis 23 times faster
                  • (foxriver76) significantly reduce backup size
                  • (foxriver76) Enhance CLI help for list command to show all possible types to list
                  • (foxriver76) Also stop instances before updating from GitHub
                  • (foxriver76) Conversion of big parts of the js-controller codebase to typeScript and address all found issues
                  • (Apollon77) Only log error on "enable/disable via .alive" if there is an error
                  • (foxriver76) Optimize adapter unload and stop handling for edge cases
                  • (AlCalzone) Carefully normalize jsonlOptions
                  • (bluefox) Do not show warning on a requested adapter stop/termination
                  • (bluefox) Make sure that the first log line is not missing in Admin
                  • (foxriver76) Fix wrong formatting of cli get binary state if no encoding is passed
                  • (foxriver76) Fix restoring backups from pre js-controller 4.x which were created without config.system
                  • (foxriver76) Preserve tier setting on adapter upload
                  • (foxriver76) update apt sources before installing os dependencies
                  • (foxriver76) Only skip erase on upload if opted out explicitly to always cleanup unneeded files
                  • (foxriver76) Try to fix strange alias errors, inform us if it happens again!
                  • (foxriver76) Remove windows bat files completely, installer will create them when needed
                  • (AlCalzone/Apollon77) Update jsonl db to prevent locking issues
                  • (foxriver76) Fixes iob file sync not working for jsonl
                  • (foxriver76) Do not crash if we cannot initialize db backup directory on start
                  • (foxriver76) Fixed issue with certificate validity on leap years
                  • (Apollon77/foxriver76) Make sure that all relevant files are removed when eraseOnUpload is used
                  • (foxriver76) fix wrong hostname after backup restore
                  • (bluefox) allow CLI vendor update without explicitly specifying vendor file (default file is used)
                  • (Apollon77, foxriver76, bluefox, AlCalzone) Several fixes and refactorings to prevent potential crash cases reported by Sentry and other sources

                  Developer relevant DEPRECATIONS/WARNINGS

                  • Deprecate binary states, Migrate your adapters to use Files instead!
                  • If you need to access special js-controller common tools please use adapter-core instead of js-controller directly - see https://github.com/ioBroker/adapter-core#commontools
                  • Parameter that contain patterns (e.g. mqtt.*) are now checked for allowed characters and general correctness!

                  Developer relevant new Features

                  • (bluefox) Added options to subscribe to file changes: subscribeForeignFiles, unsubscribeForeignFiles, onAdapterFileChanged (event contains id, fileName, size and not the whole content of the file!)

                  • (foxriver76) Introduce on("install") handler for adapter which is automatically called when adapter process is started with --install

                  • (foxriver76) Introduce io-package flag common.nodeProcessParams to allow to pass adapter specific nodejs process parameters (disables compact mode for the adapter!)

                  • (foxriver76) Respect dns resolution (ipv4/ipv6 first) from config internally and provide relevant methods via adapter-core

                  • (foxriver76) Add JSON-Schema for iobroker.json

                  • (bluefox) Allowed export of password.js (to be used with adapter-core)

                  • (bluefox) Added _design/chart to the system designs

                  • (foxriver76) Automatically generated Code-Docs for Adapter class https://github.com/ioBroker/ioBroker.js-controller/tree/master/packages/controller/doc

                  • (foxriver76) Added (foreign)objectExists to adapter methods

                  • (bluefox) Extend getSuitableLicenses to look for other licenses

                  • (buefox/foxriver76) Added new category for notifications: blocked and respect js-controller common.blockedVersions to block versions from starting

                  • (bluefox) Added new system view "custom-full" to return the full objects for objects with a custom part and not only the custom details

                  • (foxriver76) Added support for getForeignObjects with an array of strings as pattern

                  • (AlCalzone) Preparations to allow js-controller Dev version to be used with dev-server

                  • (foxriver76) Validate max timeout value (max 32bit max number) on setTimeout/setInterval and throw on error to prevent issues

                  • (foxriver76) new io-package flag common.supportedMessages to replace messagebox and other messagebox-related properties

                  • (foxriver76) adapter.sendTo now accepts an optional timeout argument

                  • Developer relevant Optimizations and Fixes

                  • (foxriver76) Ensure setObjectNotExists returns id on success

                  • (foxriver76) Fix Typings for sendTo/sendToHost

                  • (Bluefox) Add User permission check to requireLog

                  • (foxriver76) added nonEdit property of objects to types and document functionality

                  • (foxriver76) introduced constants for state quality

                  • (foxriver76) subscribeStates now also accepts an array of ids

                  • general dependency updates

                  • code style optimizations and streamline code

                  Generell ist zu testen, ob alles noch so funktioniert wie vorher auch. Das ist das wichtigste!


                  Wie Fehler melden?


                  Wer sich unsicher ist, ob ein Fehler vorliegt, sollte am besten hier im Thread das Problem beschreiben. So können wir alle versuchen, das Problem nachzuvollziehen und ggf. einzugrenzen.

                  Sobald ein Fehler auftritt der in einer Fehlermeldung oder einen Crash mit Fehlerdetails im Log oder auf Kommandozeile endet, dann dazu am besten direkt ein GitHub-Issue im js-controller Projekt öffnen und zusätzlich hier im Thread posten. Je detaillierter die Angaben im Issue sind (genaue Fehlermeldungen/Logs, Infos zur OS- und Node.js-Umgebung sowie genaue Schritte zur Reproduktion des Problems), umso schneller können wir Fehler einkreisen und beheben.

                  Bitte postet auch die Ausgabe von iob diag mit rein.

                  Wir wünschen allen viel Spaß mit dem neuen Controller und vielen Dank für Eure Unterstützung!

                  fox

                  FabioF Offline
                  FabioF Offline
                  Fabio
                  schrieb am zuletzt editiert von Fabio
                  #84

                  @foxriver76 @Bluefox eben kam das Update vom Javasript 7.1.4
                  Das Exportieren der Scripte funktioniert wieder. Vielen Dank euch.....:+1:

                  Grüße
                  Fabio

                  Iobroker:

                  • Für mich persöhnlich, gibt es nichts besseres, ich liebe es.

                  • Das hat unser Smarthome erst zu Smarthome gemacht.

                  • Du wächst mit ioBroker und ioBroker wächst mit dir.

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

                  1 Antwort Letzte Antwort
                  0
                  • liv-in-skyL liv-in-sky

                    @foxriver76

                    also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

                    das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

                    diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

                    bleibt n nur noch diese warnung:

                    	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                    
                    MartinPM Online
                    MartinPM Online
                    MartinP
                    schrieb am zuletzt editiert von
                    #85

                    @liv-in-sky said in js-controller 5.0.x jetzt für alle User im STABLE!:

                    @foxriver76

                    also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

                    das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

                    diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

                    bleibt n nur noch diese warnung:

                    	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                    

                    Diese Warnung habe ich auch von simple-api.0 ... keine Antwort auf Deine Frage im Thread gefunden

                    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

                    liv-in-skyL foxriver76F mcm1957M 3 Antworten Letzte Antwort
                    0
                    • mcm1957M mcm1957

                      Aktualisierung der Liste erforderlicher Adapterupdates:

                      javascript 7.1.4 - stable verfügbar ab 15.9. nachmittags
                      enigma2 2.0.3 - nur via latest repository verfügbar
                      plenticore 2.3.0 - z.Z. nur im latest, stable in Planung (mit Vorbehalt, siehe untern)

                      Weitere Adapter mit Problemen:

                      • Adapter PLENTICORE ist (zumindest in der im stable verfügbaren Version 2.2.0) mit js-controller inkompatibel.

                        https://forum.iobroker.net/topic/68313/plenticore-adapter-startet-nicht-nach-aktualisierung

                      • Adapter FITBIT-FITNESS ist mit js-controlelr 5 inkompatibel. Dev hat auf Issue aus April bisher nicht reagiert. Eine Meldung über Probleme, eine Meldung dass alles OK ...

                        https://forum.iobroker.net/topic/68328/fitbit-app-läuft-mit-js-controller-5-0-12-nicht-mehr
                        https://forum.iobroker.net/topic/68290/js-controller-5-0-x-jetzt-für-alle-user-im-stable/86

                      ? Offline
                      ? Offline
                      Ein ehemaliger Benutzer
                      schrieb am zuletzt editiert von
                      #86

                      @mcm57 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                      Aktualisierung der Liste erforderlicher Adapterupdates:

                      Weitere Adapter mit Problemen:

                      • Adapter FITBIT-FITNESS ist mit js-controlelr 5 inkompatibel. Dev hat auf Issue aus April bisher nicht reagiert.

                        https://forum.iobroker.net/topic/68328/fitbit-app-läuft-mit-js-controller-5-0-12-nicht-mehr

                      Das war bei mir am Anfang mit den Alpha 5.x, seit der 5.0.10 läuft der Fitbit Adapter einwandfrei.
                      Node 18.17.0, NPM 9.6, Debian bookworm im lxc.

                      1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @duffy

                        Die Befehle, aber ohne sudo vorweg.

                        DuffyD Offline
                        DuffyD Offline
                        Duffy
                        schrieb am zuletzt editiert von
                        #87

                        @thomas-braun sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                        @duffy

                        Die Befehle, aber ohne sudo vorweg.

                        Danke dir vielmals.

                        Liebe Grüsse Duffy

                        Nix besonderes; iob auf Respberry pi 4 (8GB) mit 32 GB SSD
                        Node.js: v22.21.0
                        NPM: 10.9.4
                        js-controller 7.0.7
                        Linux: Trixie

                        1 Antwort Letzte Antwort
                        0
                        • FredFF Offline
                          FredFF Offline
                          FredF
                          Most Active Forum Testing
                          schrieb am zuletzt editiert von
                          #88

                          Master im Docker Container, sowie 2 Slaves ohne Probleme aktualisiert :+1:

                          Danke für euren unermüdlichen Einsatz

                          1 Antwort Letzte Antwort
                          1
                          • MartinPM MartinP

                            @liv-in-sky said in js-controller 5.0.x jetzt für alle User im STABLE!:

                            @foxriver76

                            also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

                            das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

                            diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

                            bleibt n nur noch diese warnung:

                            	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                            

                            Diese Warnung habe ich auch von simple-api.0 ... keine Antwort auf Deine Frage im Thread gefunden

                            liv-in-skyL Offline
                            liv-in-skyL Offline
                            liv-in-sky
                            schrieb am zuletzt editiert von
                            #89

                            @martinp das liegt daran, dass ich auch keine antwort habe :-(

                            nach einem gelösten Thread wäre es sinnvoll dies in der Überschrift des ersten Posts einzutragen [gelöst]-... Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat. Forum-Tools: PicPick https://picpick.app/en/download/ und ScreenToGif https://www.screentogif.com/downloads.html

                            1 Antwort Letzte Antwort
                            0
                            • MartinPM MartinP

                              @liv-in-sky said in js-controller 5.0.x jetzt für alle User im STABLE!:

                              @foxriver76

                              also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

                              das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

                              diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

                              bleibt n nur noch diese warnung:

                              	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                              

                              Diese Warnung habe ich auch von simple-api.0 ... keine Antwort auf Deine Frage im Thread gefunden

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

                              @martinp ist nur ne Warnung, gerne issues beim adapter erstellen

                              Videotutorials & mehr

                              Hier könnt ihr mich unterstützen.

                              O 1 Antwort Letzte Antwort
                              0
                              • MartinPM MartinP

                                @liv-in-sky said in js-controller 5.0.x jetzt für alle User im STABLE!:

                                @foxriver76

                                also sayit hat sich erledigt - neu installiert und jetzt kommt kein fehler

                                das mit ws.5 ist etwas seltsam - habe nur ws.0 und ws.1 aktiv und ws.5 - habe jetzt ws5 abgeschaltet und in ws.2 definiert - dann startet alles ohne fehler und die vis ist wieder da

                                diese ganzen ws.x hatte ich mal installiert und getestet, ob meine tablets die vis stabiler anzeigen, wenn jedes tablet eigene instanzen hat

                                bleibt n nur noch diese warnung:

                                	Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                                

                                Diese Warnung habe ich auch von simple-api.0 ... keine Antwort auf Deine Frage im Thread gefunden

                                mcm1957M Offline
                                mcm1957M Offline
                                mcm1957
                                schrieb am zuletzt editiert von mcm1957
                                #91

                                @martinp said in js-controller 5.0.x jetzt für alle User im STABLE!:

                                Diese Warnung habe ich auch von simple-api.0 ... keine Antwort auf Deine Frage im Thread gefunden

                                Siehe offenes Issue https://github.com/ioBroker/ioBroker.simple-api/issues/168

                                @foxriver76 FYI

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

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

                                LESEN - gute Forenbeitrage

                                1 Antwort Letzte Antwort
                                1
                                • E Offline
                                  E Offline
                                  emil70
                                  schrieb am zuletzt editiert von emil70
                                  #92

                                  Habe gerade upgedatet und bekomme bei Aufruf von iobrocker Info unter Übersicht im Webif von iobroker folgende Fehlermeldung

                                  Screenshot 2023-09-15 at 20-44-43 intro - iobroker.png

                                  im Konsolenlog steht das

                                  Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7BisDocker%2C%20isOfficial%2C%20officialVersion%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
                                      React 17
                                      value IntroCard.jsx:289
                                      onClick IntroCard.jsx:411
                                      React 11
                                      o helpers.ts:98
                                  instrument.ts:132
                                  

                                  Bin auf Github nicht angemeldet, daher poste ich das mal hier

                                  Wo liegt da der Fehler??

                                  Edit:

                                  
                                  ======== Start marking the full check here =========
                                  
                                  
                                  Skript v.2023-05-28-4
                                  
                                  *** BASE SYSTEM ***
                                  Hardware Vendor : Synology
                                  Kernel          : x86_64
                                  Userland        : amd64
                                  Docker          : v7.0.0
                                  
                                  model name      : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
                                  Virtualization  : Unknown (buanet/Synology?)
                                  Kernel          : x86_64
                                  Userland        : amd64
                                  
                                  Systemuptime and Load:
                                   20:56:17 up 4 days,  4:25,  0 users,  load average: 2.23, 1.44, 1.02
                                  CPU threads: 4
                                  
                                  
                                  *** Time and Time Zones ***
                                  Fri Sep 15 18:56:17 UTC 2023
                                  Fri Sep 15 20:56:17 CEST 2023
                                  CEST +0200
                                  Etc/UTC
                                  
                                  *** User and Groups ***
                                  root
                                  /root
                                  root
                                  
                                  *** X-Server-Setup ***
                                  X-Server:       false
                                  Desktop: 
                                  Terminal: 
                                  
                                  
                                  *** MEMORY ***
                                                 total        used        free      shared  buff/cache   available
                                  Mem:             11G        3.0G        2.3G        154M        6.5G        8.2G
                                  Swap:           9.1G         12M        9.1G
                                  Total:           20G        3.1G         11G
                                  
                                          11822 M total memory
                                           3041 M used memory
                                           4722 M active memory
                                           2930 M inactive memory
                                           2315 M free memory
                                            891 M buffer memory
                                           5573 M swap cache
                                           9143 M total swap
                                             12 M used swap
                                           9131 M free swap
                                  
                                  *** FILESYSTEM ***
                                  Filesystem             Type   Size  Used Avail Use% Mounted on
                                  /dev/mapper/cachedev_1 btrfs  3.5T  1.3T  2.3T  36% /
                                  tmpfs                  tmpfs   64M     0   64M   0% /dev
                                  tmpfs                  tmpfs  5.8G     0  5.8G   0% /sys/fs/cgroup
                                  shm                    tmpfs   64M     0   64M   0% /dev/shm
                                  /dev/mapper/cachedev_1 btrfs  3.5T  1.3T  2.3T  36% /opt/iobroker
                                  /dev/mapper/cachedev_1 btrfs  3.5T  1.3T  2.3T  36% /etc/hosts
                                  tmpfs                  tmpfs  5.8G     0  5.8G   0% /proc/acpi
                                  tmpfs                  tmpfs  5.8G     0  5.8G   0% /proc/scsi
                                  tmpfs                  tmpfs  5.8G     0  5.8G   0% /sys/firmware
                                  
                                  Messages concerning ext4 filesystem in dmesg:
                                  
                                  Show mounted filesystems (real ones only):
                                  TARGET  SOURCE                                                                                                              FSTYPE OPTIONS
                                  /       /dev/mapper/cachedev_1[/@syno/@docker/btrfs/subvolumes/c9399b5c2c4c3ea75f19f1b7ac5a4265f4d5f18b3ada27d2f19bd08e781cf109]
                                  |                                                                                                                           btrfs  rw,node
                                  |-/opt/iobroker
                                  |       /dev/mapper/cachedev_1[/@syno/docker/iobroker_data]                                                                 btrfs  rw,node
                                  |-/etc/resolv.conf
                                  |       /dev/mapper/cachedev_1[/@syno/@docker/containers/5ea90685692b9aca72f0ab85e42da8cde040aae7fd4746bc1ffeb9c0ef253114/resolv.conf]
                                  |                                                                                                                           btrfs  rw,node
                                  |-/etc/hostname
                                  |       /dev/mapper/cachedev_1[/@syno/@docker/containers/5ea90685692b9aca72f0ab85e42da8cde040aae7fd4746bc1ffeb9c0ef253114/hostname]
                                  |                                                                                                                           btrfs  rw,node
                                  `-/etc/hosts
                                          /dev/mapper/cachedev_1[/@syno/@docker/containers/5ea90685692b9aca72f0ab85e42da8cde040aae7fd4746bc1ffeb9c0ef253114/hosts]
                                                                                                                                                              btrfs  rw,node
                                  
                                  Files in neuralgic directories:
                                  
                                  /var:
                                  16M     /var/
                                  13M     /var/lib/dpkg/info
                                  13M     /var/lib/dpkg
                                  13M     /var/lib
                                  1.9M    /var/cache/debconf
                                  
                                  
                                  
                                  /opt/iobroker/backups:
                                  106M    /opt/iobroker/backups/
                                  
                                  /opt/iobroker/iobroker-data:
                                  1.1G    /opt/iobroker/iobroker-data/
                                  986M    /opt/iobroker/iobroker-data/files
                                  231M    /opt/iobroker/iobroker-data/files/vis-2-beta
                                  143M    /opt/iobroker/iobroker-data/files/vis-2-beta/static
                                  142M    /opt/iobroker/iobroker-data/files/vis-2-beta/static/js
                                  
                                  The five largest files in iobroker-data are:
                                  35M     /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map
                                  31M     /opt/iobroker/iobroker-data/states.jsonl
                                  24M     /opt/iobroker/iobroker-data/objects.jsonl
                                  21M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map
                                  20M     /opt/iobroker/iobroker-data/files/eventlist/static/js/main.eafc8c95.js.map
                                  
                                  *** NodeJS-Installation ***
                                  
                                  /usr/bin/nodejs         v18.17.1
                                  /usr/bin/node           v18.17.1
                                  /usr/bin/npm            9.6.7
                                  /usr/bin/npx            9.6.7
                                  
                                  
                                  nodejs:
                                    Installed: 18.17.1-1nodesource1
                                    Candidate: 18.17.1-1nodesource1
                                    Version table:
                                   *** 18.17.1-1nodesource1 100
                                          100 /var/lib/dpkg/status
                                  
                                  Temp directories causing npm8 problem: 0
                                  No problems detected
                                  
                                  *** ioBroker-Installation ***
                                  
                                  ioBroker Status
                                  iobroker is running on this host.
                                  
                                  
                                  Objects type: jsonl
                                  States  type: jsonl
                                  
                                  No configuration change needed.
                                  
                                  
                                  Multihost discovery server: disabled
                                  Discovery authentication:   enabled
                                  Persistent activation:      disabled
                                  Objects:                    jsonl on 127.0.0.1
                                  States:                     jsonl on 127.0.0.1
                                  
                                  Core adapters versions
                                  js-controller:  5.0.12
                                  admin:          6.8.0
                                  javascript:     7.1.4
                                  
                                  Adapters from github:   15
                                  
                                  Adapter State
                                  + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                  + system.adapter.alexa2.0                 : alexa2                : iobroker                                 -  enabled
                                    system.adapter.alias-manager.0          : alias-manager         : iobroker                                 - disabled
                                  + system.adapter.backitup.0               : backitup              : iobroker                                 -  enabled
                                    system.adapter.birthdays.0              : birthdays             : iobroker                                 -  enabled
                                    system.adapter.daswetter.0              : daswetter             : iobroker                                 -  enabled
                                  + system.adapter.denon.0                  : denon                 : iobroker                                 -  enabled
                                    system.adapter.devices.0                : devices               : iobroker                                 - disabled
                                  + system.adapter.discovery.0              : discovery             : iobroker                                 -  enabled
                                    system.adapter.dwd.0                    : dwd                   : iobroker                                 -  enabled
                                  + system.adapter.enigma2.0                : enigma2               : iobroker                                 -  enabled
                                  + system.adapter.fully-tablet-control.0   : fully-tablet-control  : iobroker                                 -  enabled
                                    system.adapter.fullybrowser.0           : fullybrowser          : iobroker                                 - disabled
                                    system.adapter.gartenbewaesserung.0     : gartenbewaesserung    : iobroker                                 - disabled
                                  + system.adapter.hm-rega.0                : hm-rega               : iobroker                                 -  enabled
                                  + system.adapter.hm-rpc.0                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.1                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.2                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.3                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                    system.adapter.hue.0                    : hue                   : iobroker                                 - disabled, port: 80
                                    system.adapter.ical.0                   : ical                  : iobroker                                 -  enabled
                                    system.adapter.icons-icons8.0           : icons-icons8          : iobroker                                 - disabled
                                    system.adapter.icons-mfd-png.0          : icons-mfd-png         : iobroker                                 - disabled
                                    system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : iobroker                                 - disabled
                                    system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: iobroker                                 - disabled
                                  + system.adapter.influxdb.0               : influxdb              : iobroker                                 -  enabled, port: 8086
                                  + system.adapter.info.0                   : info                  : iobroker                                 -  enabled
                                  + system.adapter.iot.0                    : iot                   : iobroker                                 -  enabled
                                  + system.adapter.iqontrol.0               : iqontrol              : iobroker                                 -  enabled
                                  + system.adapter.javascript.0             : javascript            : iobroker                                 -  enabled
                                  + system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 125.123.8.49
                                    system.adapter.openweathermap.0         : openweathermap        : iobroker                                 - disabled
                                  + system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: iobroker                                 -  enabled
                                    system.adapter.ping.0                   : ping                  : iobroker                                 - disabled
                                    system.adapter.scenes.0                 : scenes                : iobroker                                 - disabled
                                    system.adapter.shuttercontrol.0         : shuttercontrol        : iobroker                                 - disabled
                                    system.adapter.socketio.0               : socketio              : iobroker                                 - disabled, port: 8085, bind: 0.0.0.0, run as: admin
                                    system.adapter.tankerkoenig.0           : tankerkoenig          : iobroker                                 - disabled
                                  + system.adapter.telegram.0               : telegram              : iobroker                                 -  enabled, port: 8443, bind: 0.0.0.0
                                  + system.adapter.tr-064.0                 : tr-064                : iobroker                                 -  enabled
                                  + system.adapter.trashschedule.0          : trashschedule         : iobroker                                 -  enabled
                                  + system.adapter.unifi.0                  : unifi                 : iobroker                                 -  enabled
                                    system.adapter.vis-bars.0               : vis-bars              : iobroker                                 - disabled
                                    system.adapter.vis-fancyswitch.0        : vis-fancyswitch       : iobroker                                 - disabled
                                    system.adapter.vis-google-fonts.0       : vis-google-fonts      : iobroker                                 -  enabled
                                    system.adapter.vis-history.0            : vis-history           : iobroker                                 - disabled
                                    system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : iobroker                                 - disabled
                                    system.adapter.vis-icontwo.0            : vis-icontwo           : iobroker                                 - disabled
                                  + system.adapter.vis-inventwo.0           : vis-inventwo          : iobroker                                 -  enabled
                                    system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : iobroker                                 - disabled
                                    system.adapter.vis-justgage.0           : vis-justgage          : iobroker                                 - disabled
                                    system.adapter.vis-lcars.0              : vis-lcars             : iobroker                                 - disabled
                                    system.adapter.vis-map.0                : vis-map               : iobroker                                 - disabled
                                    system.adapter.vis-material-advanced.0  : vis-material-advanced : iobroker                                 - disabled
                                    system.adapter.vis-materialdesign.0     : vis-materialdesign    : iobroker                                 -  enabled
                                    system.adapter.vis-metro.0              : vis-metro             : iobroker                                 - disabled
                                    system.adapter.vis-plumb.0              : vis-plumb             : iobroker                                 - disabled
                                    system.adapter.vis-timeandweather.0     : vis-timeandweather    : iobroker                                 - disabled
                                    system.adapter.vis-weather.0            : vis-weather           : iobroker                                 - disabled
                                    system.adapter.vis.0                    : vis                   : iobroker                                 -  enabled
                                  + system.adapter.vr200.0                  : vr200                 : iobroker                                 -  enabled
                                    system.adapter.weatherunderground.0     : weatherunderground    : iobroker                                 - disabled
                                  + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                  + system.adapter.weishaupt-wem.0          : weishaupt-wem         : iobroker                                 -  enabled
                                  + system.adapter.worx.0                   : worx                  : iobroker                                 -  enabled
                                  + system.adapter.ws.0                     : ws                    : iobroker                                 -  enabled, port: 8084, bind: 0.0.0.0, run as: admin
                                    system.adapter.yr.0                     : yr                    : iobroker                                 - disabled
                                  
                                  + instance is alive
                                  
                                  Enabled adapters with bindings
                                  + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                  + system.adapter.hm-rpc.0                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.1                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.2                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.hm-rpc.3                 : hm-rpc                : iobroker                                 -  enabled, port: 0
                                  + system.adapter.influxdb.0               : influxdb              : iobroker                                 -  enabled, port: 8086
                                  + system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 125.123.8.49
                                  + system.adapter.telegram.0               : telegram              : iobroker                                 -  enabled, port: 8443, bind: 0.0.0.0
                                  + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                  + system.adapter.ws.0                     : ws                    : iobroker                                 -  enabled, port: 8084, bind: 0.0.0.0, run as: admin
                                  
                                  ioBroker-Repositories
                                  Stable (default): http://download.iobroker.net/sources-dist.json
                                  Beta (latest) : http://download.iobroker.net/sources-dist-latest.json
                                  
                                  Active repo(s): Stable (default)
                                  
                                  Installed ioBroker-Instances
                                  Used repository: Stable (default)
                                  Adapter    "admin"        : 6.8.0    , installed 6.8.0
                                  Adapter    "alarm"        : 3.3.12   , installed 3.3.12
                                  Adapter    "alexa2"       : 3.24.1   , installed 3.24.1
                                  Adapter    "alias-manager": 1.2.4    , installed 1.2.4
                                  Adapter    "backitup"     : 2.6.23   , installed 2.6.23
                                  Adapter    "birthdays"    : 2.3.1    , installed 2.3.1
                                  Adapter    "daswetter"    : 3.1.10   , installed 3.1.10
                                  Adapter    "denon"        : 1.15.4   , installed 1.15.4
                                  Adapter    "device-watcher": 2.9.3   , installed 2.9.3
                                  Adapter    "devices"      : 1.1.5    , installed 1.1.5
                                  Adapter    "discovery"    : 3.1.0    , installed 3.1.0
                                  Adapter    "dwd"          : 2.8.5    , installed 2.8.5
                                  Adapter    "egigeozone"   : 0.1.2    , installed 0.1.2
                                  Adapter    "eventlist"    : 1.2.3    , installed 1.2.3
                                  Adapter    "fb-checkpresence": 1.2.2 , installed 1.2.2
                                  Adapter    "fullybrowser" : 2.1.2    , installed 2.1.2
                                  Adapter    "hm-rega"      : 3.0.47   , installed 3.0.47
                                  Adapter    "hm-rpc"       : 1.15.19  , installed 1.15.19
                                  Adapter    "hue"          : 3.9.5    , installed 3.9.5
                                  Adapter    "ical"         : 1.13.3   , installed 1.13.3
                                  Adapter    "icons-icons8" : 0.0.1    , installed 0.0.1
                                  Adapter    "icons-mfd-png": 1.1.0    , installed 1.1.0
                                  Adapter    "icons-mfd-svg": 1.1.0    , installed 1.1.0
                                  Adapter    "icons-open-icon-library-png": 0.1.2, installed 0.1.3
                                  Adapter    "influxdb"     : 3.2.0    , installed 3.2.0
                                  Adapter    "info"         : 1.9.26   , installed 1.9.26
                                  Adapter    "iot"          : 1.14.5   , installed 1.14.5
                                  Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
                                  Adapter    "javascript"   : 7.1.4    , installed 7.1.4
                                  Controller "js-controller": 5.0.12   , installed 5.0.12
                                  Adapter    "luftdaten"    : 3.0.0    , installed 3.0.0
                                  Adapter    "mqtt"         : 4.1.1    , installed 4.1.1
                                  Adapter    "openweathermap": 0.3.9   , installed 0.3.9
                                  Adapter    "panasonic-comfort-cloud": 2.2.0, installed 2.2.0
                                  Adapter    "ping"         : 1.6.2    , installed 1.6.2
                                  Adapter    "radar2"       : 2.0.7    , installed 2.0.7
                                  Adapter    "scenes"       : 2.3.9    , installed 2.3.9
                                  Adapter    "shuttercontrol": 1.6.1   , installed 1.6.1
                                  Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
                                  Adapter    "snmp"         : 2.4.11   , installed 2.4.11
                                  Adapter    "socketio"     : 6.5.5    , installed 6.5.5
                                  Adapter    "sprinklecontrol": 0.2.13 , installed 0.2.13
                                  Adapter    "synology"     : 2.1.13   , installed 2.1.13
                                  Adapter    "tankerkoenig" : 3.3.7    , installed 3.3.7
                                  Adapter    "telegram"     : 1.16.0   , installed 1.16.0
                                  Adapter    "tr-064"       : 4.2.18   , installed 4.2.18
                                  Adapter    "trashschedule": 2.2.0    , installed 2.2.0
                                  Adapter    "tvspielfilm"  : 2.0.4    , installed 2.0.5
                                  Adapter    "unifi"        : 0.6.6    , installed 0.6.6
                                  Adapter    "vis"          : 1.4.16   , installed 1.4.16
                                  Adapter    "vis-bars"     : 0.1.4    , installed 0.1.4
                                  Adapter    "vis-fancyswitch": 1.1.0  , installed 1.1.0
                                  Adapter    "vis-google-fonts": 1.0.4 , installed 1.0.4
                                  Adapter    "vis-history"  : 1.0.0    , installed 1.0.0
                                  Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
                                  Adapter    "vis-icontwo"  : 0.96.0   , installed 0.96.0
                                  Adapter    "vis-inventwo" : 3.3.3    , installed 3.3.3
                                  Adapter    "vis-jqui-mfd" : 1.0.12   , installed 1.0.12
                                  Adapter    "vis-justgage" : 1.0.2    , installed 1.0.2
                                  Adapter    "vis-lcars"    : 1.1.1    , installed 1.1.1
                                  Adapter    "vis-map"      : 1.0.4    , installed 1.0.4
                                  Adapter    "vis-material-advanced": 1.7.2, installed 1.7.2
                                  Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
                                  Adapter    "vis-plumb"    : 1.0.2    , installed 1.0.2
                                  Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
                                  Adapter    "vis-weather"  : 2.5.6    , installed 2.5.6
                                  Adapter    "vr200"        : 1.0.0    , installed 1.1.0
                                  Adapter    "weatherunderground": 3.4.2, installed 3.4.2
                                  Adapter    "web"          : 6.1.2    , installed 6.1.2
                                  Adapter    "weishaupt-wem": 0.0.15   , installed 0.0.16
                                  Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
                                  Adapter    "worx"         : 2.3.2    , installed 2.3.2
                                  Adapter    "ws"           : 2.5.5    , installed 2.5.5
                                  Adapter    "yahoo-stock-market": 0.0.5, installed 0.0.5
                                  Adapter    "yr"           : 5.3.0    , installed 5.3.0
                                  
                                  Objects and States
                                  Please stand by - This may take a while
                                  Objects:        24150
                                  States:         28305
                                  
                                  *** OS-Repositories and Updates ***
                                  Hit:1 http://deb.debian.org/debian bullseye InRelease
                                  Hit:2 http://security.debian.org/debian-security bullseye-security InRelease                  
                                  Hit:3 http://deb.debian.org/debian bullseye-updates InRelease                                 
                                  Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease           
                                  Reading package lists... Done                     
                                  Pending Updates: 9
                                  
                                  *** Listening Ports ***
                                  Active Internet connections (only servers)
                                  Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
                                  tcp        0      0 125.123.8.49:2010       0.0.0.0:*               LISTEN      1000       62065376   -                   
                                  tcp        0      0 125.123.8.49:1883       0.0.0.0:*               LISTEN      1000       62067513   -                   
                                  tcp        0      0 125.123.8.49:1884       0.0.0.0:*               LISTEN      1000       62067514   -                   
                                  tcp        0      0 125.123.8.49:8701       0.0.0.0:*               LISTEN      1000       62065148   -                   
                                  tcp        0      0 127.0.0.11:35749        0.0.0.0:*               LISTEN      0          47415874   -                   
                                  tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1000       62059118   -                   
                                  tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1000       62059105   -                   
                                  tcp        0      0 125.123.8.49:9292       0.0.0.0:*               LISTEN      1000       62067785   -                   
                                  tcp        0      0 125.123.8.49:2001       0.0.0.0:*               LISTEN      1000       62066798   -                   
                                  tcp6       0      0 :::8081                 :::*                    LISTEN      1000       62062684   -                   
                                  tcp6       0      0 :::8082                 :::*                    LISTEN      1000       62078963   -                   
                                  tcp6       0      0 :::8084                 :::*                    LISTEN      1000       62081022   -                   
                                  udp        0      0 127.0.0.11:37225        0.0.0.0:*                           0          47415873   -                   
                                  
                                  *** Log File - Last 25 Lines ***
                                  
                                  2023-09-15 20:55:39.783  - info: worx.0 (10532) Start MQTT connection
                                  2023-09-15 20:55:40.290  - info: worx.0 (10532) MQTT connected to: iot.eu-west-1.worxlandroid.com
                                  2023-09-15 20:55:40.355  - info: worx.0 (10532) Request Counter: 1
                                  2023-09-15 20:55:40.490  - info: host.iobroker instance system.adapter.iqontrol.0 started with pid 10693
                                  2023-09-15 20:55:43.343  - info: iqontrol.0 (10693) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                                  2023-09-15 20:55:43.377  - info: iqontrol.0 (10693) starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v18.17.1, js-controller: 5.0.12
                                  2023-09-15 20:55:43.504  - info: iqontrol.0 (10693) systemLanguage = de
                                  2023-09-15 20:55:43.506  - info: iqontrol.0 (10693) Creating Passphrase...
                                  2023-09-15 20:55:43.565  - info: iqontrol.0 (10693) Creating Popup States...
                                  2023-09-15 20:55:44.433  - info: iqontrol.0 (10693) Creating Widget States...
                                  2023-09-15 20:55:44.434  - info: iqontrol.0 (10693) Lists deactivated.
                                  2023-09-15 20:55:44.434  - info: iqontrol.0 (10693) Deleting unused Objects...
                                  2023-09-15 20:55:44.436  - info: iqontrol.0 (10693) Subscribing to states...
                                  2023-09-15 20:55:44.439  - info: iqontrol.0 (10693) iQontrol ready.
                                  2023-09-15 20:55:44.488  - info: web.0 (10374) ==> Connected system.user.admin from ::ffff:125.123.8.88
                                  2023-09-15 20:55:47.120  - info: vis-google-fonts.0 (10745) starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.vis-google-fonts, node: v18.17.1, js-controller: 5.0.12
                                  2023-09-15 20:55:47.825  - info: vis-google-fonts.0 (10745) Terminated (NO_ERROR): Without reason
                                  2023-09-15 20:55:48.140  - info: host.iobroker instance system.adapter.fully-tablet-control.0 started with pid 10837
                                  2023-09-15 20:55:48.630  - info: host.iobroker instance system.adapter.vis-google-fonts.0 terminated while should be started once
                                  2023-09-15 20:55:50.864  - info: fully-tablet-control.0 (10837) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                                  2023-09-15 20:55:51.124  - info: fully-tablet-control.0 (10837) starting. Version 0.3.8 (non-npm: xXBJXx/ioBroker.fully-tablet-control#af138797fc2ddeb067b46b3248da63083d4b5a46) in /opt/iobroker/node_modules/iobroker.fully-tablet-control, node: v18.17.1, js-controller: 5.0.12
                                  2023-09-15 20:55:57.250  - info: mqtt.0 (9561) Client [] connection closed: disconnected
                                  2023-09-15 20:55:57.504  - info: mqtt.0 (9561) Client [] connected with secret 1694804157503_5368
                                  2023-09-15 20:56:55.601  - info: mqtt.0 (9561) Client [] connection closed: disconnected
                                  2023-09-15 20:56:57.867  - info: mqtt.0 (9561) Client [] connected with secret 1694804217866_6830
                                  
                                  
                                  ============ Mark until here for C&P =============
                                  
                                  ======================= SUMMARY =======================
                                                       v.2023-05-28-4
                                  
                                  
                                  model name      : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
                                  Kernel          : x86_64
                                  Userland        : amd64
                                  Docker          : v7.0.0
                                  
                                  Installation:           Docker
                                  Kernel:                 x86_64
                                  Userland:               amd64
                                  Timezone:               Etc/UTC
                                  User-ID:                0
                                  X-Server:               false
                                  
                                  
                                  Pending OS-Updates:     9
                                  Pending iob updates:    0
                                  
                                  Nodejs-Installation:    /usr/bin/nodejs         v18.17.1
                                                          /usr/bin/node           v18.17.1
                                                          /usr/bin/npm            9.6.7
                                                          /usr/bin/npx            9.6.7
                                  
                                  Recommended versions are nodejs 18.x.y and npm 9.x.y
                                  Your nodejs installation is correct
                                  
                                  MEMORY: 
                                                 total        used        free      shared  buff/cache   available
                                  Mem:             11G        3.0G        2.4G        154M        6.5G        8.3G
                                  Swap:           9.1G         12M        9.1G
                                  Total:           20G        3.0G         11G
                                  
                                  Active iob-Instances:   30
                                  Active repo(s): Stable (default)
                                  
                                  ioBroker Core:          js-controller           5.0.12
                                                          admin                   6.8.0
                                  
                                  ioBroker Status:        iobroker is running on this host.
                                  
                                  
                                  Objects type: jsonl
                                  States  type: jsonl
                                  
                                  Status admin and web instance:
                                  + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                  + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                  
                                  Objects:                24150
                                  States:                 28305
                                  
                                  Size of iob-Database:
                                  
                                  24M     /opt/iobroker/iobroker-data/objects.jsonl
                                  32M     /opt/iobroker/iobroker-data/states.jsonl
                                  
                                  
                                  
                                  =================== END OF SUMMARY ====================
                                  

                                  gruss emil70

                                  iobroker(V9) und Pi-hole läuft über docker (js-controller 6.0.11 und admin v7.1.15) auf einem synology DS918+ mit DSM 7.1.1-42962 Update 6

                                  1 Antwort Letzte Antwort
                                  0
                                  • Walter WhiteW Offline
                                    Walter WhiteW Offline
                                    Walter White
                                    schrieb am zuletzt editiert von Walter White
                                    #93

                                    Heute waren ja auch Updates für JS Adapter und so, und seitdem hat mich der Fritzbox Präsenz Adapter zusammen mit meiner Frau schon das zweite Mal abgemeldet, und meldet uns nicht wieder an.
                                    Jetzt verfolgt uns die sicherheitskamera hier die ganze Zeit, weil die natürlich bei Abwesenheit scharf schaltet.

                                    fb-checkpresence.0
                                    2023-09-15 20:39:11.708 info newActive HeisenbergHandy false

                                    Steht in den log files, unsere Handys sind selbstverständlich die ganze Zeit zu Hause und im WLAN.
                                    Betrifft anscheinend aber nur die Handys welche direkt an der 7590 sind, kinderhandys sind weiterhin eingebucht aber sind jedoch auch am AVM 3000 welcher hier als Access Point läuft.

                                    PS: WLAN im Handy aus und wieder anmachen meldet uns wieder an, aber ich habe in den logs auch keine rote oder gelbe Meldung dazu.

                                    mcm1957M 1 Antwort Letzte Antwort
                                    0
                                    • Walter WhiteW Walter White

                                      Heute waren ja auch Updates für JS Adapter und so, und seitdem hat mich der Fritzbox Präsenz Adapter zusammen mit meiner Frau schon das zweite Mal abgemeldet, und meldet uns nicht wieder an.
                                      Jetzt verfolgt uns die sicherheitskamera hier die ganze Zeit, weil die natürlich bei Abwesenheit scharf schaltet.

                                      fb-checkpresence.0
                                      2023-09-15 20:39:11.708 info newActive HeisenbergHandy false

                                      Steht in den log files, unsere Handys sind selbstverständlich die ganze Zeit zu Hause und im WLAN.
                                      Betrifft anscheinend aber nur die Handys welche direkt an der 7590 sind, kinderhandys sind weiterhin eingebucht aber sind jedoch auch am AVM 3000 welcher hier als Access Point läuft.

                                      PS: WLAN im Handy aus und wieder anmachen meldet uns wieder an, aber ich habe in den logs auch keine rote oder gelbe Meldung dazu.

                                      mcm1957M Offline
                                      mcm1957M Offline
                                      mcm1957
                                      schrieb am zuletzt editiert von mcm1957
                                      #94

                                      @walter-white said in js-controller 5.0.x jetzt für alle User im STABLE!:

                                      Heute waren ja auch Updates für JS Adapter und so, und seitdem hat mich der Fritzbox Präsenz Adapter zusammen mit meiner Frau schon das zweite Mal abgemeldet, und meldet uns nicht wieder an.
                                      Jetzt verfolgt uns die sicherheitskamera hier die ganze Zeit, weil die natürlich bei Abwesenheit scharf schaltet.

                                      fb-checkpresence.0
                                      2023-09-15 20:39:11.708 info newActive HeisenbergHandy false

                                      Steht in den log files, unsere Handys sind selbstverständlich die ganze Zeit zu Hause und im WLAN.
                                      Betrifft anscheinend aber nur die Handys welche direkt an der 7590 sind, kinderhandys sind weiterhin eingebucht aber sind jedoch auch am AVM 3000 welcher hier als Access Point läuft.

                                      PS: WLAN im Handy aus und wieder anmachen meldet uns wieder an, aber ich habe in den logs auch keine rote oder gelbe Meldung dazu.

                                      Sorry, aber mit den Infos können wir nur plaudern ...
                                      Bitte um

                                      • Versionen der betreffenden Adapter
                                      • Fehler im Logfile bzw. Log Auszug

                                      Warum ein Update des "und so" Adapters oder des "js" Adapters etwas am Adapter fb-presence bewirken soll, kann ich nicht sagen. Prüfe mal die logs des fb-presence adapters um den es offensichtlich geht. Falls kein erkennbarere oder zumindest zu vermutender Zusammenhang mit js-controller 5 existiert, itte neues Topic eröffnen und dort diskutieren.

                                      Und natürlich - bitte adie Versionen der beteiligten Adapter angeben-

                                      DANKE

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

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

                                      LESEN - gute Forenbeitrage

                                      1 Antwort Letzte Antwort
                                      1
                                      • JohGreJ JohGre

                                        @mcm57 Zur Info
                                        Habe gerade einen fork des community-Adapters gefunden der funktioniert. Vielleicht könnt ihr das zusammenlegen.

                                        https://github.com/PeterVoronov/ioBroker.botvac/tree/patch-1

                                        zugehöriger Thread:
                                        https://forum.iobroker.net/topic/44822/neato-botvac-adapter-further-development/45?_=1694772899628

                                        mcm1957M Offline
                                        mcm1957M Offline
                                        mcm1957
                                        schrieb am zuletzt editiert von
                                        #95

                                        @johgre said in js-controller 5.0.x jetzt für alle User im STABLE!:

                                        @mcm57 Zur Info
                                        Habe gerade einen fork des community-Adapters gefunden der funktioniert. Vielleicht könnt ihr das zusammenlegen.

                                        https://github.com/PeterVoronov/ioBroker.botvac/tree/patch-1

                                        zugehöriger Thread:
                                        https://forum.iobroker.net/topic/44822/neato-botvac-adapter-further-development/45?_=1694772899628

                                        Ich habe nun die Infrastruktur des Adapter s so halbwegs auf den aktuellen Stand gebracht und ALPHA Version eingezogen. (2.0.0.alpha.1) Diese enthält auch den PR von PeterVoronov.
                                        Diese alpha Version ist vi github und via npm installierbar aber nicht in den Repositories gelistet.

                                        Über Feedback würde ich mich freuen.

                                        Um dieses Topic zu entpasten bitte die Diskussion incl. Feedback im oben genannten botvac topic https://forum.iobroker.net/topic/44822/neato-botvac-adapter-further-development/45?_=1694772899628 fortführen. Hier würde ich nur eine Notiz posten sobald eine offozielle mit js-controller 5 kompatible Version im Repository verfügbar ist.

                                        Danke

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

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

                                        LESEN - gute Forenbeitrage

                                        1 Antwort Letzte Antwort
                                        0
                                        • Ben1983B Offline
                                          Ben1983B Offline
                                          Ben1983
                                          schrieb am zuletzt editiert von
                                          #96

                                          Hallo,
                                          habe auf den 5.0.12 geupdatet.
                                          Bei Start des ioBrokers kam das hier: (Habe leider nur den Screenshot)
                                          4bca2cdb-797e-47fc-9e42-86ed636b9cae-image.png

                                          dann habe ich noch:

                                          6a79a967-6b13-4413-9f55-4ae6eeff00a2-image.png

                                          erst erschien immer dies hier:

                                          fitbit-fitness.0 2023-09-15 15:07:19.211	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                          
                                          fitbit-fitness.0 2023-09-15 15:07:19.206	error	undefined is not a valid state value
                                          
                                          fitbit-fitness.0 2023-09-15 15:07:19.205	error	Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at FitBit._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at FitBit.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at FitBit.setActivityStates (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:321:9) at FitBit.getActivityRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:305:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async FitBit.getFitbitRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:87:5)
                                          
                                          fitbit-fitness.0 2023-09-15 15:07:19.199	error	unhandled promise rejection: undefined is not a valid state value
                                          
                                          fitbit-fitness.0 2023-09-15 15:07:19.197	error	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().
                                          

                                          seit heute morgen erscheint bei Adapterstart das hier:

                                          fitbit-fitness.0
                                          2023-09-16 07:43:24.360	error	Adapter Connection: Error: Error: Request failed with status code 401
                                          
                                          Samson71S mcm1957M 2 Antworten Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          167

                                          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