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.
    • 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
                • Gaspode
                  Gaspode @apollon77 last edited by

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

                  Na das verbietet sich von alleine.

                  In diesem Fall steht es außerdem sogar im ersten Beitrag:

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

                  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.

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

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

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

                    Ja, das wurde wohl vergessen zu ändern.

                    1 Reply Last reply Reply Quote 0
                    • D
                      Diamand2k22 @Diamand2k22 last edited by

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

                      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$
                      

                      Zigbee läuft wieder, eine Deinstallation und Reinstallation hat das Problem gelöst.
                      für jemanden der das selbe Problem hat.

                      cd /opt/iobroker 
                      npm uninstall zigbee-herdsman-converters
                      npm uninstall zigbee-herdsman
                      

                      danach wieder Installieren entweder über Adapter oder github.

                      bin zeitgleich wieder auf due 5.0.3 zurück, da im Java Blockly die Trigger nicht mehr funktioniert haben.

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

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

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

                        fixe ich

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

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

                          cd /opt/iobroker

                          Falsches Verzeichnis.
                          Die herdsman-Module liegen unterhalb von iobroker.zigbee

                          1 Reply Last reply Reply Quote 0
                          • ste_glei
                            ste_glei last edited by

                            Update auf 5.0.5 hat problemlos geklappt.

                            Einzig der bosch-ebike Adapter funktioniert nicht und wirft nur Fehler aus

                            host.iobroker
                            2023-06-19 12:51:36.695	info	Restart adapter system.adapter.bosch-ebike.0 because enabled
                            host.iobroker
                            2023-06-19 12:51:36.695	error	instance system.adapter.bosch-ebike.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                            host.iobroker
                            2023-06-19 12:51:36.695	error	Caught by controller[1]: at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
                            host.iobroker
                            2023-06-19 12:51:36.695	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                            host.iobroker
                            2023-06-19 12:51:36.695	error	Caught by controller[1]: at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:149:51)
                            host.iobroker
                            2023-06-19 12:51:36.695	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'replace')
                            host.iobroker
                            2023-06-19 12:51:36.694	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:
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.993	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.992	info	terminating
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.975	error	Cannot read properties of undefined (reading 'replace')
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.974	error	TypeError: Cannot read properties of undefined (reading 'replace') at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:149:51) at processTicksAndRejections (node:internal/process/task_queues:95:5) at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.972	error	unhandled promise rejection: Cannot read properties of undefined (reading 'replace')
                            
                            bosch-ebike.0
                            2023-06-19 12:51:35.971	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().
                            
                            bosch-ebike.0
                            2023-06-19 12:51:34.011	info	Login to eBike flow
                            
                            apollon77 1 Reply Last reply Reply Quote 0
                            • dontobi
                              dontobi @foxriver76 last edited by

                              @foxriver76 Ich habe eben meine Installation aktualisiert. Leider klappt danach nichts mehr. Grund hierfür sind die UI Upgrade Changes. Ich nutze nämlich einen eigenen ioBroker Docker Container. Wäre es möglich da was dran zu ändern?

                              Thomas Braun foxriver76 apollon77 4 Replies Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @dontobi last edited by

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

                                Wäre es möglich da was dran zu ändern?

                                Vermutlich müsstest du da was 'zu beißen' in Form von Logfiles abliefern.
                                Soweit ich das hier verfolgt habe funktioniert es nämlich bei anderen im Docker.

                                M dontobi 2 Replies Last reply Reply Quote 0
                                • M
                                  Marty56 @Thomas Braun last edited by Marty56

                                  Ich habe bemerkt, dass "sendToAsync" jetzt wieder Probleme macht.
                                  Folgende Funktion bricht mit Fehler ab.
                                  Die Errormeldung liefere ich nach.

                                  async function write_influxDB2(id,time,value,db) {
                                      var timestamp = new Date(new Date(time).toISOString()).getTime();
                                      try {
                                          await sendToAsync(db, 'storeState', [{ id: id, state: {ts: timestamp, val: value, ack: false}}]);
                                          log('Write DB:' + db + ' id:'+ id + " Value: " + value.toFixed(2) + " Time: " + time)
                                      } 
                                      catch (error) {
                                          log('InfluxDB Error trying to write ' + id ,error)
                                      } 
                                      return;
                                  }
                                  

                                  Update: Fehlermeldung. Ich kann damit nichts anfangen.

                                  Unknown severity level "[object Object]" by log of [InfluxDB Error trying to write 0_userdata.0.Energie.Auto.price_tibber]
                                  
                                  apollon77 1 Reply Last reply Reply Quote 0
                                  • dontobi
                                    dontobi @Thomas Braun last edited by

                                    @thomas-braun Wenn ich das eben richtig gesehen habe, wir die Version des Docker Containers abgefragt. Bei mir läuft dies ins leere und somit stürzt der Controller ab.

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

                                      @dontobi ja es wird dir in Zukunft nicht mehr angeboten. UI Upgrade nur mit offiziellem iob Image und auch erst nach 5.0.5 also das kann noch keiner testen.

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

                                        @dontobi und ja Log oder keiner kann dir helfen die Anfrage nach Version kann eigentlich nichts crashen soweit ich weiß

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

                                          @foxriver76 ich liefere das Log morgen nach.

                                          dontobi 1 Reply Last reply Reply Quote 0
                                          • dontobi
                                            dontobi @dontobi last edited by

                                            @dontobi Ich habe mir die UI Upgrade Sache mal genauer angesehen. In meinem Docker Container habe ich die Datei .thisisdocker nicht gesetzt. Habe nun kurz die Datei erzeugt und mit 8.0.0 beschrieben. Danach klappt alles wieder.

                                            Dennoch hier das Log ohne die Datei .thisisdocker:

                                            /opt/iobroker/node_modules/@iobroker/js-controller-common/node_modules/semver/classes/semver.js:38
                                                  throw new TypeError(`Invalid Version: ${version}`)
                                                  ^
                                            TypeError: Invalid Version:
                                                at new SemVer (/opt/iobroker/node_modules/@iobroker/js-controller-common/node_modules/semver/classes/semver.js:38:13)
                                                at compare (/opt/iobroker/node_modules/@iobroker/js-controller-common/node_modules/semver/functions/compare.js:3:3)
                                                at Object.lt (/opt/iobroker/node_modules/@iobroker/js-controller-common/node_modules/semver/functions/lt.js:2:29)
                                                at isControllerUiUpgradeSupported (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:364:30)
                                                at getSupportedFeatures (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/utils.js:23:53)
                                                at new AdapterClass (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:104:68)
                                                at startAdapter (/opt/iobroker/node_modules/iobroker.admin/main.js:55:15)
                                                at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/main.js:1208:5)
                                                at Module._compile (node:internal/modules/cjs/loader:1254:14)
                                                at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
                                            Node.js v18.16.0
                                            ================================== > LOG REDIRECT system.adapter.admin.0 => false
                                            
                                            foxriver76 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

                                            819
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            71
                                            580
                                            125464
                                            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