Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 5.0.x jetzt in der BETA

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller 5.0.x jetzt in der BETA

    This topic has been deleted. Only users with topic management privileges can see it.
    • Feuersturm
      Feuersturm @foxriver76 last edited by

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

      Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.

      Braucht ihr noch ein issue dafür beim Web Adapter?

      1 Reply Last reply Reply Quote 0
      • foxriver76
        foxriver76 Developer last edited by

        @feuersturm Ja bitte gg

        1 Reply Last reply Reply Quote 0
        • Chaot
          Chaot @foxriver76 last edited by

          @foxriver76 Danke.
          Das fehlerhafte binding habe ich mittlerweile lokalisiert:

          {javascript.0.variables.dayTime.lc;momentDate(dddd)}<br>{javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}
          

          Komischerweise läuft das andere Binding in der zweiten View ohne Probleme, obwohl es (fast) gleich ist:

          {javascript.0.variables.dayTime.lc;momentDate(dd)}  {javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}
          
          mcm1957 1 Reply Last reply Reply Quote 0
          • mcm1957
            mcm1957 @Chaot last edited by

            @apollon77

            Update für Problemliste:

            linux-control scheint ein Problem zu haben:
            https://github.com/Scrounger/ioBroker.linux-control/issues/49

            Für stiebel-isg und pi-hole dürfte es Updates geben:
            Im latest verfügbar (spätestens morgen), stable pending (kurze Karenzzeit erscheint sinnvoll)
            https://github.com/ioBroker/ioBroker.repositories/pull/2367

            Strobelix80 created this issue in Scrounger/ioBroker.linux-control

            closed Error with js-controller 5.x #49

            unltdnetworx created this issue in ioBroker/ioBroker.repositories

            closed Update sources-dist-stable.json - pi-hole and stiebel-isg #2367

            1 Reply Last reply Reply Quote 1
            • skvarel
              skvarel Developer last edited by

              Moin zusammen.

              bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau 😞

              a7ef0749-2914-4b8e-8e55-187b6bd79ee4-image.png

              Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0

              skvarel 1 Reply Last reply Reply Quote 0
              • skvarel
                skvarel Developer @skvarel last edited by skvarel

                Es scheint an irgendwelchen Widgets zu liegen.

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

                Moin zusammen.

                bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau 😞

                a7ef0749-2914-4b8e-8e55-187b6bd79ee4-image.png

                Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0

                M DJMarc75 2 Replies Last reply Reply Quote 0
                • M
                  Marty56 @skvarel last edited by

                  Ich habe gerade diesen "Alias Error Burst" bekommen.
                  Schade, es scheint das js-controller 5 hier nicht geholfen hat.

                  1 Reply Last reply Reply Quote 0
                  • DJMarc75
                    DJMarc75 @skvarel last edited by

                    @skvarel Texte in Codetags packen bitte.

                    1 Reply Last reply Reply Quote 0
                    • Feuersturm
                      Feuersturm @foxriver76 last edited by

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

                      @chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.

                      @Chaot Du kannst dich mit deinem Problem mit an dieses issue hängen: https://github.com/ioBroker/ioBroker.web/issues/316

                      Feuer-sturm created this issue in ioBroker/ioBroker.web

                      closed unvalid binding in vis crashes web adapter with jjs-controller 5.0.4 #316

                      1 Reply Last reply Reply Quote 1
                      • foxriver76
                        foxriver76 Developer last edited by

                        Controller v5.0.5 wird zeitnah verfügbar sein:

                        • Probleme mit falschem Loglevel bei Beenden von Adaptern behoben
                        • UI Upgrade wird nur noch angeboten, wenn das Betriebssystem dies unterstützt (das heißt aktuell: nativ Linux oder offizielles ioBroker Docker Image)
                        • UI Upgrade für offizielles Docker Image eingebaut
                        • Probleme mit dem Aufruf von deleteState in manchen Konstellationen behoben, was zB verhindert hat Geräte in Zigbee zu löschen
                        dontobi 1 Reply Last reply Reply Quote 4
                        • Feuersturm
                          Feuersturm last edited by Feuersturm

                          @foxriver76 Ich hab gerade meinen Master erfolgreich über die Admin GUI auf 5.0.5 aktualisiert.
                          Als ich jetzt im nächsten Schritt meinen Slave über die Admin GUI aktualisiseren wollte kam folgende Fehlermeldung:
                          478a39c6-5444-4ea0-97fc-94a079ba0349-grafik.png

                          Das Update scheint aber erfolgreich gewesen zu sein. Über die Konsole meldet sich ioBroker mit der Version 5.0.5 sowie auch in der Admin UI.

                          fdada1fe-b365-4500-be3e-8f68dcc32f9c-grafik.png

                          Das steht im Log vom Slave

                          2023-06-18 16:52:15.022 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:15.134 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:20.037 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:20.140 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:25.045 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:25.147 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:30.050 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:30.153 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:35.058 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:35.158 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:40.071 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:40.163 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:45.080 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:45.170 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:50.087 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:50.180 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:52:55.092 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:52:55.187 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:53:00.102 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:53:00.194 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:53:05.116 - info: host.ioBrokerNew Objects database successfully reconnected
                          2023-06-18 16:53:05.201 - info: host.ioBrokerNew Objects database successfully reconnected
                          2023-06-18 16:53:13.922 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:53:14.033 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:53:18.929 - error: host.ioBrokerNew Objects database error: connect ECONNREFUSED 192.168.178.77:9001
                          2023-06-18 16:53:19.046 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:53:23.935 - info: host.ioBrokerNew Objects database successfully reconnected
                          2023-06-18 16:53:24.052 - error: host.ioBrokerNew States database error: connect ECONNREFUSED 192.168.178.77:9000
                          2023-06-18 16:53:29.064 - info: host.ioBrokerNew Objects database successfully reconnected
                          2023-06-18 16:58:12.225 - info: host.ioBrokerNew Controller will upgrade itself to version 5.0.5
                          2023-06-18 16:58:16.320 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Stopping controller
                          2023-06-18 16:58:16.437 - info: host.ioBrokerNew received SIGTERM
                          2023-06-18 16:58:16.443 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false)
                          2023-06-18 16:58:16.444 - info: host.ioBrokerNew stopInstance system.adapter.sql.0 (force=false, process=false)
                          2023-06-18 16:58:16.445 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false)
                          2023-06-18 16:58:16.492 - info: host.ioBrokerNew terminated
                          2023-06-18 16:58:20.638 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
                          2023-06-18 16:58:20.655 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
                          2023-06-18 16:58:57.178 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE]
                          changed 12 packages in 34s
                          81 packages are looking for funding
                          run `npm fund` for details
                          2023-06-18 16:59:07.193 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Timeout expired, initializing shutdown
                          2023-06-18 16:59:07.286 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
                          2023-06-18 16:59:09.687 - info: host.ioBrokerNew iobroker.js-controller version 5.0.5 js-controller starting
                          2023-06-18 16:59:09.699 - info: host.ioBrokerNew Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                          2023-06-18 16:59:09.702 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v18.16.0
                          2023-06-18 16:59:09.704 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1
                          2023-06-18 16:59:10.347 - info: host.ioBrokerNew connected to Objects and States
                          2023-06-18 16:59:10.391 - info: host.ioBrokerNew added notifications configuration of host
                          2023-06-18 16:59:11.478 - info: host.ioBrokerNew 61 instances found
                          2023-06-18 16:59:11.603 - warn: host.ioBrokerNew does not start any instances on this host
                          

                          Edit: Github issue: https://github.com/ioBroker/ioBroker.admin/issues/1963

                          Feuer-sturm created this issue in ioBroker/ioBroker.admin

                          closed Updating js-controller 5.x on Slave over admin "TypeError: Network Error when attempting to fetch ressource" #1963

                          foxriver76 1 Reply Last reply Reply Quote 0
                          • foxriver76
                            foxriver76 Developer @Feuersturm last edited by

                            @feuersturm danke schaue ich mir mit BF an. Läuft der Admin von dem aus das gestartet wurde auf Master oder Slave? Hat das vorher schon auf Slave mal sauber funktioniert. Logfile selbst schaut sehr gut aus.

                            Feuersturm 1 Reply Last reply Reply Quote 0
                            • Feuersturm
                              Feuersturm @foxriver76 last edited by

                              @foxriver76 der Admin läuft auf dem Master von dem das Update gestartet wurde. Den slave habe ich bisher immer über die Konsole aktualisiert und nicht über die gui.

                              foxriver76 1 Reply Last reply Reply Quote 0
                              • foxriver76
                                foxriver76 Developer @Feuersturm last edited by

                                @feuersturm danke für die Info. Ich vermute Admin fragt immer lokal an auch wenn auf anderem Host aktualisiert wird. Muss voraussichtlich in Admin gefixt werden. Schauen wir uns an. 👍🏼

                                1 Reply Last reply Reply Quote 1
                                • crunchip
                                  crunchip Forum Testing Most Active @foxriver76 last edited by crunchip

                                  @foxriver76 Update wieder per admin mit anschließendem Browser refresh
                                  sieht nun besser aus, aber bei mir hat der shelly nach wie vor Probleme, hatte ich schon mal ne zeitlang, werd ich wohl ggf issue wieder eröffnen

                                  2023-06-18 22:14:20.204 - info: host.IoBroker stopInstance system.adapter.countdown.0 send kill signal
                                  2023-06-18 22:14:20.205 - info: host.IoBroker stopInstance system.adapter.tibberconnect.0 send kill signal
                                  2023-06-18 22:14:20.205 - info: host.IoBroker stopInstance system.adapter.opendtu.0 send kill signal
                                  2023-06-18 22:14:20.420 - info: mytime.0 (1104559) terminating with timeout
                                  2023-06-18 22:14:20.423 - info: virtualpowermeter.0 (1105082) terminating
                                  2023-06-18 22:14:20.784 - warn: sonoff.0 (1103739) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                  2023-06-18 22:14:20.793 - warn: sonoff.0 (1103739) get state error: Connection is closed.
                                  2023-06-18 22:14:20.794 - warn: sonoff.0 (1103739) redis get sonoff.0.PC-Server.alive, error - DB closed
                                  2023-06-18 22:14:20.757 - warn: shelly.0 (1103714) get state error: Connection is closed.
                                  2023-06-18 22:14:20.767 - error: shelly.0 (1103714) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                  2023-06-18 22:14:20.769 - error: shelly.0 (1103714) unhandled promise rejection: DB closed
                                  2023-06-18 22:14:20.973 - error: shelly.0 (1103714) Error: DB closed
                                  at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                  at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                  at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                  at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7585:34)
                                  2023-06-18 22:14:20.974 - error: shelly.0 (1103714) DB closed
                                  2023-06-18 22:14:21.132 - warn: sonoff.0 (1103739) get state error: Connection is closed.
                                  2023-06-18 22:14:21.173 - warn: sonoff.0 (1103739) get state error: Connection is closed.
                                  2023-06-18 22:14:21.175 - warn: sonoff.0 (1103739) get state error: Connection is closed.
                                  2023-06-18 22:14:21.316 - info: host.IoBroker stopInstance system.adapter.admin.0 killing pid 1103011
                                  2023-06-18 22:14:21.349 - warn: opendtu.0 (1105739) Cannot get view: Connection is closed.
                                  2023-06-18 22:14:21.316 - info: host.IoBroker stopInstance system.adapter.javascript.0 killing pid 1103278
                                  2023-06-18 22:14:21.317 - info: host.IoBroker stopInstance system.adapter.telegram.0 killing pid 1727115
                                  .
                                  .
                                  2023-06-18 22:14:27.599 - warn: host.IoBroker instance system.adapter.net-tools.0 terminated due to SIGTERM
                                  2023-06-18 22:14:27.599 - info: host.IoBroker instance system.adapter.net-tools.0 terminated with code null ()
                                  2023-06-18 22:14:27.692 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
                                  2023-06-18 22:14:27.693 - info: host.IoBroker instance system.adapter.nut.0 terminated with code null ()
                                  2023-06-18 22:14:27.795 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                                  2023-06-18 22:14:27.796 - error: host.IoBroker Caught by controller[0]: Error: DB closed
                                  2023-06-18 22:14:27.797 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                  2023-06-18 22:14:27.798 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                  2023-06-18 22:14:27.798 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                  2023-06-18 22:14:27.799 - error: host.IoBroker Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7585:34)
                                  2023-06-18 22:14:27.799 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
                                  .
                                  .
                                  ansonsten
                                  2023-06-18 22:14:31.618 - info: host.IoBroker All instances are stopped.
                                  2023-06-18 22:14:31.652 - info: host.IoBroker terminated
                                  2023-06-18 22:14:36.282 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
                                  2023-06-18 22:14:36.290 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
                                  2023-06-18 22:15:30.526 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE]
                                  changed 12 packages in 53s
                                  226 packages are looking for funding
                                  run `npm fund` for details
                                  2023-06-18 22:15:31.506 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Final information delivered
                                  2023-06-18 22:15:39.805 - info: host.IoBroker [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
                                  2023-06-18 22:15:40.972 - info: host.IoBroker iobroker.js-controller version 5.0.5 js-controller starting
                                  2023-06-18 22:15:40.978 - info: host.IoBroker Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                                  2023-06-18 22:15:40.979 - info: host.IoBroker hostname: IoBroker, node: v18.16.0
                                  2023-06-18 22:15:40.980 - info: host.IoBroker ip addresses: 10.1.1.10 fe80::d428:e1ff:fe76:b484
                                  2023-06-18 22:15:44.891 - info: host.IoBroker connected to Objects and States
                                  2023-06-18 22:15:45.021 - info: host.IoBroker added notifications configuration of host
                                  2023-06-18 22:15:46.309 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeCurrent"
                                  2023-06-18 22:15:46.360 - info: host.IoBroker 139 instances found
                                  2023-06-18 22:15:46.490 - info: host.IoBroker starting 57 instances
                                  2023-06-18 22:15:46.764 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeNewest"
                                  2023-06-18 22:15:46.772 - info: host.IoBroker Delete state "system.host.IoBroker.versions.nodeNewestNext"
                                  2023-06-18 22:15:46.778 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmCurrent"
                                  2023-06-18 22:15:46.852 - info: host.IoBroker instance system.adapter.admin.0 started with pid 3026764
                                  2023-06-18 22:15:46.861 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmNewest"
                                  2023-06-18 22:15:46.908 - info: host.IoBroker Delete state "system.host.IoBroker.versions.npmNewestNext"
                                  2023-06-18 22:15:46.914 - info: host.IoBroker Some obsolete host states deleted.
                                  2023-06-18 22:15:49.609 - info: admin.0 (3026764) starting. Version 6.5.8 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 5.0.5
                                  2023-06-18 22:15:49.659 - info: admin.0 (3026764) requesting all states
                                  2023-06-18 22:15:49.660 - info: admin.0 (3026764) requesting all objects
                                  2023-06-18 22:15:52.077 - info: host.IoBroker instance system.adapter.history.0 started with pid 3026791
                                  2023-06-18 22:15:52.838 - info: admin.0 (3026764) received all objects
                                  2023-06-18 22:15:53.252 - info: admin.0 (3026764) Request actual repository...
                                  2023-06-18 22:15:53.281 - info: admin.0 (3026764) socket.io server listening on port 8081
                                  2023-06-18 22:15:53.284 - info: admin.0 (3026764) http server listening on port 8081
                                  2023-06-18 22:15:53.285 - info: admin.0 (3026764) Use link "http://127.0.0.1:8081" to configure.
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    Diamand2k22 last edited by

                                    seit dem Update auf 5.0.5 schmiert mir immer der Zigbee Adapter ab.

                                    2023-06-19 10:01:37.722 - error: host.pi4b Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                                    2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'Error')
                                    2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56
                                    2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Hub.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/hub.ts:340:1)
                                    2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Object.configureScope (/opt/iobroker/node_modules/@iobroker/plugin-sentry/node_modules/@sentry/src/exports.ts:76:1)
                                    2023-06-19 10:01:37.723 - error: host.pi4b Caught by controller[0]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32)
                                    2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at Zigbee.filterError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:142:18)
                                    2023-06-19 10:01:37.724 - error: host.pi4b Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:699:22
                                    2023-06-19 10:01:37.724 - error: host.pi4b instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    
                                    pi4b@pi4b:/opt/iobroker$ npm ls --depth=3 | grep zigbee
                                    └─┬ iobroker.zigbee@1.8.11 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#5add9eafb4da35eedc5655ef3c0a8a919ec873b0)
                                      ├─┬ zigbee-herdsman-converters@15.22.0
                                      │ └─┬ zigbee-herdsman@0.15.0
                                      └─┬ zigbee-herdsman@0.14.117
                                    pi4b@pi4b:/opt/iobroker$
                                    
                                    mcm1957 D 2 Replies Last reply Reply Quote 0
                                    • mcm1957
                                      mcm1957 @Diamand2k22 last edited by

                                      @apollon77

                                      Im Spoiler für Entwickler News im ersten Beitrag steht

                                      Support for Node.js 12 is dropped! Supported are Node.js 14.18.0+, 16.4.0+ and 18.x

                                      Wurde nicht node 14 enfalls gekübelt.,oder rwechsel ich das was?

                                      Thomas Braun Gaspode apollon77 3 Replies Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @mcm1957 last edited by

                                        @mcm57

                                        Schon von nodejs.org selber. nodejs14 ist EOL.

                                        mcm1957 1 Reply Last reply Reply Quote 0
                                        • mcm1957
                                          mcm1957 @Thomas Braun last edited by

                                          @thomas-braun
                                          Ja ich weiss
                                          Habs auch systematisch aus test rausgeworfen. Ist zu 99% fehler. Kann aber auch was verwechseln. EOL ist nicht zwingen not allowed 🙂

                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @mcm1957 last edited by

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

                                            EOL ist nicht zwingen not allowed

                                            Na das verbietet sich von alleine.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            873
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            71
                                            580
                                            122824
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo