Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Alpha Test js-controller Kiera (v6.0)

NEWS

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

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

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

Alpha Test js-controller Kiera (v6.0)

Geplant Angeheftet Gesperrt Verschoben Tester
alphajs-controllerkieratest
234 Beiträge 20 Kommentatoren 45.0k Aufrufe 25 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.
  • foxriver76F foxriver76

    Ansonsten bitte nochmal updaten und log von update zeigen

    F Offline
    F Offline
    Fortune95
    schrieb am zuletzt editiert von
    #126

    @foxriver76
    Habs versucht geht aber immer noch nicht.
    Update hat auch nichhts gefunden...

    iobroker@iobroker:/opt/iobroker$ npm update
    
    up to date in 2m
    
    207 packages are looking for funding
      run `npm fund` for details
    iobroker@iobroker:/opt/iobroker$
    
    
    1 Antwort Letzte Antwort
    0
    • foxriver76F foxriver76

      Ansonsten bitte nochmal updaten und log von update zeigen

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

      @foxriver76
      Hier sind die Meldungen bzgl. letsencrypt wieder zurück.
      Exemplarisch:

      2024-05-24 18:58:01.008  - error: host.chet Caught by controller[0]: /opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94
      2024-05-24 18:58:01.010  - error: host.chet Caught by controller[0]:     throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
      2024-05-24 18:58:01.010  - error: host.chet Caught by controller[0]:     ^
      2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
      2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]:     at resolveNamedModule (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:11)
      2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:137:18)
      2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1434:14)
      2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._extensions..js (node:internal/modules/cjs/loader:1518:10)
      2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1249:32)
      2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:1065:12)
      2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1271:19)
      2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at require (node:internal/modules/helpers:123:16)
      2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/index.js:19:27)
      2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1434:14)
      2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]: Node.js v22.2.0
      2024-05-24 18:58:01.013  - error: host.chet instance system.adapter.whatsapp-cmb.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
      2024-05-24 18:58:01.008  - error: host.chet Caught by controller[0]: /opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94
      
      

      Betrifft aber auch weitere Adapter, mit gleichen Meldungen.

      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

      foxriver76F 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @foxriver76
        Hier sind die Meldungen bzgl. letsencrypt wieder zurück.
        Exemplarisch:

        2024-05-24 18:58:01.008  - error: host.chet Caught by controller[0]: /opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94
        2024-05-24 18:58:01.010  - error: host.chet Caught by controller[0]:     throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
        2024-05-24 18:58:01.010  - error: host.chet Caught by controller[0]:     ^
        2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
        2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]:     at resolveNamedModule (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:11)
        2024-05-24 18:58:01.011  - error: host.chet Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:137:18)
        2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1434:14)
        2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._extensions..js (node:internal/modules/cjs/loader:1518:10)
        2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1249:32)
        2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:1065:12)
        2024-05-24 18:58:01.012  - error: host.chet Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1271:19)
        2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at require (node:internal/modules/helpers:123:16)
        2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/index.js:19:27)
        2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1434:14)
        2024-05-24 18:58:01.013  - error: host.chet Caught by controller[0]: Node.js v22.2.0
        2024-05-24 18:58:01.013  - error: host.chet instance system.adapter.whatsapp-cmb.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
        2024-05-24 18:58:01.008  - error: host.chet Caught by controller[0]: /opt/iobroker/node_modules/iobroker.whatsapp-cmb/node_modules/@iobroker/adapter-core/build/controllerTools.js:94
        
        

        Betrifft aber auch weitere Adapter, mit gleichen Meldungen.

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

        @thomas-braun hast du zufällig das log von der Installation parat?

        Videotutorials & mehr

        Hier könnt ihr mich unterstützen.

        mcm1957M Thomas BraunT 2 Antworten Letzte Antwort
        0
        • foxriver76F foxriver76

          @thomas-braun hast du zufällig das log von der Installation parat?

          mcm1957M Online
          mcm1957M Online
          mcm1957
          schrieb am zuletzt editiert von mcm1957
          #129

          @foxriver76
          Ich kann das Update noch starten (allerdings windows) (via npm i ...)
          Wie erstelle ich das beste log ?
          Nur den Screen loggen?

          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

          foxriver76F 1 Antwort Letzte Antwort
          0
          • foxriver76F foxriver76

            @thomas-braun hast du zufällig das log von der Installation parat?

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

            @foxriver76
            Nee, aber da stand auch nix drin. Das ist offenbar bei npm 10.7.0 radikal gekürzt worden. Jedenfalls das nach STDOUT geschriebene. Muss mal schauen wo das ganze Ding genau landet.

            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
            • mcm1957M mcm1957

              @foxriver76
              Ich kann das Update noch starten (allerdings windows) (via npm i ...)
              Wie erstelle ich das beste log ?
              Nur den Screen loggen?

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

              @mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

              Videotutorials & mehr

              Hier könnt ihr mich unterstützen.

              mcm1957M Thomas BraunT 2 Antworten Letzte Antwort
              0
              • foxriver76F foxriver76

                @mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

                mcm1957M Online
                mcm1957M Online
                mcm1957
                schrieb am zuletzt editiert von
                #132

                @foxriver76

                Soda:
                Mal Snapshot während er mit npm rumnuckelt ...
                a8c6efb5-92f4-47f1-bb83-623d65f405f9-image.png

                Ansonsten ist er seht schweigsam:

                **********************************************************
                ***               Welcome to ioBroker.                 ***
                ***                                                    ***
                ***     Type 'iob help' for list of instructions.      ***
                ***                For more help see                   ***
                ***     https://github.com/ioBroker/ioBroker.docs      ***
                **********************************************************
                
                Your environment has been set up for using Node.js 20.13.1 (x64) and npm.
                
                C:\ioBroker>npm i iobroker.js-controller@next --omit=dev
                
                changed 12 packages, and audited 619 packages in 2m
                
                72 packages are looking for funding
                  run `npm fund` for details
                
                26 vulnerabilities (21 moderate, 5 high)
                
                To address issues that do not require attention, run:
                  npm audit fix
                
                To address all issues possible (including breaking changes), run:
                  npm audit fix --force
                
                Some issues need review, and may require choosing
                a different dependency.
                
                Run `npm audit` for details.
                
                C:\ioBroker>
                

                Im Log nix auffälligs, system läuft soweit (mal grob gechecked)

                
                ical.1
                2024-05-24 19:18:16.241	warn	Error reading from URL "http://11111.ics"
                
                ical.1
                2024-05-24 19:18:15.892	info	starting. Version 1.15.0 in C:/ioBroker/node_modules/iobroker.ical, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240524-14a872375
                host.Envy
                2024-05-24 19:18:14.133	info	instance system.adapter.ical.1 started with pid 1604
                host.Envy
                2024-05-24 19:18:14.125	info	instance scheduled system.adapter.ical.1 0,4 0,30 * * * *
                host.Envy
                2024-05-24 19:18:11.929	info	Restart adapter system.adapter.notification-manager.0 because enabled
                host.Envy
                2024-05-24 19:18:11.928	error	instance system.adapter.notification-manager.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                
                notification-manager.0
                2024-05-24 19:18:11.379	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                
                notification-manager.0
                2024-05-24 19:18:11.377	error	notification-manager.0 already running
                host.Envy
                2024-05-24 19:18:10.032	info	instance system.adapter.notification-manager.0 started with pid 17028
                host.Envy
                2024-05-24 19:18:07.928	info	Restart adapter system.adapter.backitup.0 because enabled
                host.Envy
                2024-05-24 19:18:07.928	error	instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                backitup.0
                2024-05-24 19:18:07.378	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                backitup.0
                2024-05-24 19:18:07.377	error	backitup.0 already running
                host.Envy
                2024-05-24 19:18:06.016	info	instance system.adapter.backitup.0 started with pid 1772
                host.Envy
                2024-05-24 19:18:04.960	info	Restart adapter system.adapter.admin.0 because enabled
                host.Envy
                2024-05-24 19:18:04.960	error	instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                
                admin.0
                2024-05-24 19:18:04.388	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                
                admin.0
                2024-05-24 19:18:04.386	error	admin.0 already running
                host.Envy
                2024-05-24 19:18:02.125	info	Some obsolete host states deleted.
                host.Envy
                2024-05-24 19:18:02.123	info	Delete state "system.host.Envy.versions.npmNewestNext"
                host.Envy
                2024-05-24 19:18:02.121	info	Delete state "system.host.Envy.versions.npmNewest"
                host.Envy
                2024-05-24 19:18:02.118	info	Delete state "system.host.Envy.versions.npmCurrent"
                host.Envy
                2024-05-24 19:18:02.112	info	Delete state "system.host.Envy.versions.nodeNewestNext"
                host.Envy
                2024-05-24 19:18:02.111	info	instance system.adapter.admin.0 started with pid 17072
                host.Envy
                2024-05-24 19:18:02.098	info	Delete state "system.host.Envy.versions.nodeNewest"
                host.Envy
                2024-05-24 19:18:02.086	info	Delete state "system.host.Envy.versions.nodeCurrent"
                host.Envy
                2024-05-24 19:18:01.693	info	starting 5 instances
                host.Envy
                2024-05-24 19:18:01.675	info	17 instances found
                host.Envy
                2024-05-24 19:18:01.188	info	added notifications configuration of host
                host.Envy
                2024-05-24 19:18:01.174	info	connected to Objects and States
                host.Envy
                2024-05-24 19:18:00.523	info	ip addresses: 10.17.2.100 fe80::3089:3ca1:e684:7494 10.17.2.16
                host.Envy
                2024-05-24 19:18:00.522	info	hostname: Envy, node: v20.13.1
                host.Envy
                2024-05-24 19:18:00.522	info	Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                host.Envy
                2024-05-24 19:18:00.518	info	iobroker.js-controller version 6.0.1 js-controller starting
                

                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

                mcm1957M 1 Antwort Letzte Antwort
                0
                • mcm1957M mcm1957

                  @foxriver76

                  Soda:
                  Mal Snapshot während er mit npm rumnuckelt ...
                  a8c6efb5-92f4-47f1-bb83-623d65f405f9-image.png

                  Ansonsten ist er seht schweigsam:

                  **********************************************************
                  ***               Welcome to ioBroker.                 ***
                  ***                                                    ***
                  ***     Type 'iob help' for list of instructions.      ***
                  ***                For more help see                   ***
                  ***     https://github.com/ioBroker/ioBroker.docs      ***
                  **********************************************************
                  
                  Your environment has been set up for using Node.js 20.13.1 (x64) and npm.
                  
                  C:\ioBroker>npm i iobroker.js-controller@next --omit=dev
                  
                  changed 12 packages, and audited 619 packages in 2m
                  
                  72 packages are looking for funding
                    run `npm fund` for details
                  
                  26 vulnerabilities (21 moderate, 5 high)
                  
                  To address issues that do not require attention, run:
                    npm audit fix
                  
                  To address all issues possible (including breaking changes), run:
                    npm audit fix --force
                  
                  Some issues need review, and may require choosing
                  a different dependency.
                  
                  Run `npm audit` for details.
                  
                  C:\ioBroker>
                  

                  Im Log nix auffälligs, system läuft soweit (mal grob gechecked)

                  
                  ical.1
                  2024-05-24 19:18:16.241	warn	Error reading from URL "http://11111.ics"
                  
                  ical.1
                  2024-05-24 19:18:15.892	info	starting. Version 1.15.0 in C:/ioBroker/node_modules/iobroker.ical, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240524-14a872375
                  host.Envy
                  2024-05-24 19:18:14.133	info	instance system.adapter.ical.1 started with pid 1604
                  host.Envy
                  2024-05-24 19:18:14.125	info	instance scheduled system.adapter.ical.1 0,4 0,30 * * * *
                  host.Envy
                  2024-05-24 19:18:11.929	info	Restart adapter system.adapter.notification-manager.0 because enabled
                  host.Envy
                  2024-05-24 19:18:11.928	error	instance system.adapter.notification-manager.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                  
                  notification-manager.0
                  2024-05-24 19:18:11.379	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                  
                  notification-manager.0
                  2024-05-24 19:18:11.377	error	notification-manager.0 already running
                  host.Envy
                  2024-05-24 19:18:10.032	info	instance system.adapter.notification-manager.0 started with pid 17028
                  host.Envy
                  2024-05-24 19:18:07.928	info	Restart adapter system.adapter.backitup.0 because enabled
                  host.Envy
                  2024-05-24 19:18:07.928	error	instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                  backitup.0
                  2024-05-24 19:18:07.378	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                  backitup.0
                  2024-05-24 19:18:07.377	error	backitup.0 already running
                  host.Envy
                  2024-05-24 19:18:06.016	info	instance system.adapter.backitup.0 started with pid 1772
                  host.Envy
                  2024-05-24 19:18:04.960	info	Restart adapter system.adapter.admin.0 because enabled
                  host.Envy
                  2024-05-24 19:18:04.960	error	instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                  
                  admin.0
                  2024-05-24 19:18:04.388	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                  
                  admin.0
                  2024-05-24 19:18:04.386	error	admin.0 already running
                  host.Envy
                  2024-05-24 19:18:02.125	info	Some obsolete host states deleted.
                  host.Envy
                  2024-05-24 19:18:02.123	info	Delete state "system.host.Envy.versions.npmNewestNext"
                  host.Envy
                  2024-05-24 19:18:02.121	info	Delete state "system.host.Envy.versions.npmNewest"
                  host.Envy
                  2024-05-24 19:18:02.118	info	Delete state "system.host.Envy.versions.npmCurrent"
                  host.Envy
                  2024-05-24 19:18:02.112	info	Delete state "system.host.Envy.versions.nodeNewestNext"
                  host.Envy
                  2024-05-24 19:18:02.111	info	instance system.adapter.admin.0 started with pid 17072
                  host.Envy
                  2024-05-24 19:18:02.098	info	Delete state "system.host.Envy.versions.nodeNewest"
                  host.Envy
                  2024-05-24 19:18:02.086	info	Delete state "system.host.Envy.versions.nodeCurrent"
                  host.Envy
                  2024-05-24 19:18:01.693	info	starting 5 instances
                  host.Envy
                  2024-05-24 19:18:01.675	info	17 instances found
                  host.Envy
                  2024-05-24 19:18:01.188	info	added notifications configuration of host
                  host.Envy
                  2024-05-24 19:18:01.174	info	connected to Objects and States
                  host.Envy
                  2024-05-24 19:18:00.523	info	ip addresses: 10.17.2.100 fe80::3089:3ca1:e684:7494 10.17.2.16
                  host.Envy
                  2024-05-24 19:18:00.522	info	hostname: Envy, node: v20.13.1
                  host.Envy
                  2024-05-24 19:18:00.522	info	Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                  host.Envy
                  2024-05-24 19:18:00.518	info	iobroker.js-controller version 6.0.1 js-controller starting
                  
                  mcm1957M Online
                  mcm1957M Online
                  mcm1957
                  schrieb am zuletzt editiert von
                  #133

                  Wurde im js-controller nicht was mit npm update eingebaut?
                  Wann sollte das denn laufen? npm wird das ja kaum triggern. Sollte da unter windows noch der fixer gestartet werden?

                  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

                  mcm1957M 1 Antwort Letzte Antwort
                  0
                  • mcm1957M mcm1957

                    Wurde im js-controller nicht was mit npm update eingebaut?
                    Wann sollte das denn laufen? npm wird das ja kaum triggern. Sollte da unter windows noch der fixer gestartet werden?

                    mcm1957M Online
                    mcm1957M Online
                    mcm1957
                    schrieb am zuletzt editiert von
                    #134

                    Das Ganze noch mal mit verbose

                    npm verb cli C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
                    npm info using npm@10.5.2
                    npm info using node@v20.13.1
                    npm verb title npm i iobroker.js-controller@next
                    npm verb argv "i" "iobroker.js-controller@next" "--omit" "dev" "--loglevel" "verbose"
                    npm verb logfile logs-max:10 dir:C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-
                    npm verb logfile C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-debug-0.log
                    npm http fetch GET 200 https://registry.npmjs.org/iobroker.js-controller 993ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-redis 30ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-redis 51ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-file 73ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-jsonl 92ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-file 120ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-jsonl 145ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-adapter 163ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-base 88ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-cli 153ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common 154ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-sentry 93ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/deep-clone 82ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common-db 156ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/jsonwebtoken 80ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/pidusage 72ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/readline-sync 41ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/promisify-child-process 73ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fjsonl-db 28ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/node.extend 20ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-base 41ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/ioredis 59ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fpak 70ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/event-stream 60ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/readline 75ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/chokidar 83ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/ci-info 52ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/debug 96ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/winston-daily-rotate-file 46ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/triple-beam 63ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/node-forge 74ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/winston-transport 60ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/winston 79ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@datalust%2fwinston-seq 68ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/diskusage 63ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/winston-seq-updated 49ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/winston-syslog 58ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fnode 54ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fintegrations 75ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/jws 85ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/source-map-support 94ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.includes 111ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isboolean 112ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isinteger 116ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isnumber 81ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isplainobject 69ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isstring 65ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.once 58ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/ms 30ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 26ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/respjs 8ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fproper-lockfile 14ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/alcalzone-shared 15ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/fs-extra 17ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/retry 19ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/signal-exit 21ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.defaults 21ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/cluster-key-slot 26ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/denque 29ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.flatten 41ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lodash.isarguments 46ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/p-map 48ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/redis-commands 51ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/redis-parser 41ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/redis-errors 46ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/standard-as-callback 39ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is 30ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/axios 15ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/execa 29ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/npm-run-path 26ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/merge-stream 29ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/human-signals 32ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/strip-final-newline 32ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/onetime 34ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/glob-parent 33ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is-binary-path 37ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/anymatch 42ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/braces 45ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is-glob 50ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/readdirp 54ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/fsevents 57ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/duplexer 45ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/split 31ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/from 51ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/pause-stream 44ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/map-stream 55ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/stream-combiner 39ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/through 38ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@dabh%2fdiagnostics 29ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/seq-logging 36ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/one-time 38ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/logform 42ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@colors%2fcolors 47ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/safe-stable-stringify 50ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/readable-stream 56ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/es6-promise 60ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/nan 59ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/object-hash 56ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/glossy 52ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/file-stream-rotator 66ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/unix-dgram 53ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/localforage 32ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 44ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 65ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 83ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry-internal%2ftracing 106ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 112ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 141ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/source-map 119ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 155ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/lie 8ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/fill-range 26ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/binary-extensions 29ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/picomatch 36ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is-extglob 34ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/picomatch 35ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/to-regex-range 8ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/mimic-fn 12ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is-number 10ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/jwa 9ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/kuler 34ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/enabled 40ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/fecha 33ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/@types%2ftriple-beam 40ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/fn.name 34ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/colorspace 52ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/text-hex 11ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/color 15ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/color-convert 11ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/color-string 13ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 18ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/color-name 22ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/color-name 24ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 9ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/bindings 9ms (cache hit)
                    npm http fetch GET 200 https://registry.npmjs.org/file-uri-to-path 10ms (cache hit)
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\fsevents
                    npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 254ms
                    npm http fetch GET 200 https://registry.npmjs.org/follow-redirects 97ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/request 182ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/ip 191ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/tough-cookie 210ms (cache revalidated)
                    npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall node_modules/iobroker.js-controller node build/esm/lib/preinstallCheck.js
                    npm http fetch GET 200 https://registry.npmjs.org/iobroker.broadlink2 626ms (cache revalidated)
                    npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall { code: 0, signal: null }
                    npm info run diskusage@1.2.0 install node_modules/diskusage node-gyp rebuild
                    npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install node_modules/iobroker.js-controller node iobroker.js setup first
                    npm info run unix-dgram@2.0.6 install node_modules/unix-dgram node-gyp rebuild
                    npm http fetch GET 200 https://registry.npmjs.org/mdns-discovery 642ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/dns-packet 58ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/node-ssdp 889ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/iobroker.kecontact 619ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/dropbox-v2-api 627ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/iobroker.discovery 255ms (cache revalidated)
                    npm http fetch GET 200 https://registry.npmjs.org/iobroker.backitup 586ms (cache revalidated)
                    npm info run unix-dgram@2.0.6 install { code: 1, signal: null }
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\unix-dgram
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\bindings
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\file-uri-to-path
                    npm info run diskusage@1.2.0 install { code: 1, signal: null }
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\diskusage
                    npm verb reify failed optional dependency C:\ioBroker\node_modules\es6-promise
                    npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install { code: 0, signal: null }
                    
                    removed 32 packages, changed 14 packages, and audited 619 packages in 1m
                    
                    72 packages are looking for funding
                      run `npm fund` for details
                    
                    26 vulnerabilities (21 moderate, 5 high)
                    
                    To address issues that do not require attention, run:
                      npm audit fix
                    
                    To address all issues possible (including breaking changes), run:
                      npm audit fix --force
                    
                    Some issues need review, and may require choosing
                    a different dependency.
                    
                    Run `npm audit` for details.
                    npm verb exit 0
                    npm info ok
                    

                    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

                    mcm1957M 1 Antwort Letzte Antwort
                    0
                    • mcm1957M mcm1957

                      Das Ganze noch mal mit verbose

                      npm verb cli C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
                      npm info using npm@10.5.2
                      npm info using node@v20.13.1
                      npm verb title npm i iobroker.js-controller@next
                      npm verb argv "i" "iobroker.js-controller@next" "--omit" "dev" "--loglevel" "verbose"
                      npm verb logfile logs-max:10 dir:C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-
                      npm verb logfile C:\Users\MartinAdmin\AppData\Local\npm-cache\_logs\2024-05-24T17_27_06_077Z-debug-0.log
                      npm http fetch GET 200 https://registry.npmjs.org/iobroker.js-controller 993ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-redis 30ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-redis 51ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-file 73ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-objects-jsonl 92ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-file 120ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-states-jsonl 145ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-adapter 163ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-base 88ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-cli 153ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common 154ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fplugin-sentry 93ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/deep-clone 82ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fjs-controller-common-db 156ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/jsonwebtoken 80ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/pidusage 72ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/readline-sync 41ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/promisify-child-process 73ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fjsonl-db 28ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/node.extend 20ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@iobroker%2fdb-base 41ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/ioredis 59ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fpak 70ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/event-stream 60ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/readline 75ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/chokidar 83ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/ci-info 52ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/debug 96ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/winston-daily-rotate-file 46ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/triple-beam 63ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/node-forge 74ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/winston-transport 60ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/winston 79ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@datalust%2fwinston-seq 68ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/diskusage 63ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/winston-seq-updated 49ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/winston-syslog 58ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fnode 54ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fintegrations 75ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/jws 85ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/source-map-support 94ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.includes 111ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isboolean 112ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isinteger 116ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isnumber 81ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isplainobject 69ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isstring 65ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.once 58ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/ms 30ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 26ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/respjs 8ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@alcalzone%2fproper-lockfile 14ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/alcalzone-shared 15ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/fs-extra 17ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/retry 19ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/signal-exit 21ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.defaults 21ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/cluster-key-slot 26ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/denque 29ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.flatten 41ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lodash.isarguments 46ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/p-map 48ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/redis-commands 51ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/redis-parser 41ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/redis-errors 46ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/standard-as-callback 39ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is 30ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/axios 15ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/execa 29ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/npm-run-path 26ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/merge-stream 29ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/human-signals 32ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/strip-final-newline 32ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/onetime 34ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/glob-parent 33ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is-binary-path 37ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/anymatch 42ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/braces 45ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is-glob 50ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/readdirp 54ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/fsevents 57ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/duplexer 45ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/split 31ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/from 51ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/pause-stream 44ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/map-stream 55ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/stream-combiner 39ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/through 38ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@dabh%2fdiagnostics 29ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/seq-logging 36ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/one-time 38ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/logform 42ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@colors%2fcolors 47ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/safe-stable-stringify 50ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/readable-stream 56ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/es6-promise 60ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/nan 59ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/object-hash 56ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/glossy 52ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/file-stream-rotator 66ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/unix-dgram 53ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/localforage 32ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 44ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 65ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 83ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry-internal%2ftracing 106ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 112ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 141ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/source-map 119ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 155ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/lie 8ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/fill-range 26ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/binary-extensions 29ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/picomatch 36ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is-extglob 34ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/picomatch 35ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/to-regex-range 8ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/mimic-fn 12ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is-number 10ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/jwa 9ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/kuler 34ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/enabled 40ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/fecha 33ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/@types%2ftriple-beam 40ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/fn.name 34ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/colorspace 52ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/text-hex 11ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/color 15ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/color-convert 11ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/color-string 13ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 18ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/color-name 22ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/color-name 24ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 9ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/bindings 9ms (cache hit)
                      npm http fetch GET 200 https://registry.npmjs.org/file-uri-to-path 10ms (cache hit)
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\fsevents
                      npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 254ms
                      npm http fetch GET 200 https://registry.npmjs.org/follow-redirects 97ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/request 182ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/ip 191ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/tough-cookie 210ms (cache revalidated)
                      npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall node_modules/iobroker.js-controller node build/esm/lib/preinstallCheck.js
                      npm http fetch GET 200 https://registry.npmjs.org/iobroker.broadlink2 626ms (cache revalidated)
                      npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 preinstall { code: 0, signal: null }
                      npm info run diskusage@1.2.0 install node_modules/diskusage node-gyp rebuild
                      npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install node_modules/iobroker.js-controller node iobroker.js setup first
                      npm info run unix-dgram@2.0.6 install node_modules/unix-dgram node-gyp rebuild
                      npm http fetch GET 200 https://registry.npmjs.org/mdns-discovery 642ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/dns-packet 58ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/node-ssdp 889ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/iobroker.kecontact 619ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/dropbox-v2-api 627ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/iobroker.discovery 255ms (cache revalidated)
                      npm http fetch GET 200 https://registry.npmjs.org/iobroker.backitup 586ms (cache revalidated)
                      npm info run unix-dgram@2.0.6 install { code: 1, signal: null }
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\unix-dgram
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\bindings
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\file-uri-to-path
                      npm info run diskusage@1.2.0 install { code: 1, signal: null }
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\diskusage
                      npm verb reify failed optional dependency C:\ioBroker\node_modules\es6-promise
                      npm info run iobroker.js-controller@6.0.1-alpha.0-20240524-14a872375 install { code: 0, signal: null }
                      
                      removed 32 packages, changed 14 packages, and audited 619 packages in 1m
                      
                      72 packages are looking for funding
                        run `npm fund` for details
                      
                      26 vulnerabilities (21 moderate, 5 high)
                      
                      To address issues that do not require attention, run:
                        npm audit fix
                      
                      To address all issues possible (including breaking changes), run:
                        npm audit fix --force
                      
                      Some issues need review, and may require choosing
                      a different dependency.
                      
                      Run `npm audit` for details.
                      npm verb exit 0
                      npm info ok
                      
                      mcm1957M Online
                      mcm1957M Online
                      mcm1957
                      schrieb am zuletzt editiert von
                      #135

                      Und der iob fix

                      C:\ioBroker>
                      C:\ioBroker>del iobroker.bat
                      
                      C:\ioBroker>iob fix
                      Windows installation starting... (fixing = true)
                      NPM version: 10.5.2
                      No path given, using C:\ioBroker\iobroker-data
                      Compressing C:\ioBroker\iobroker-data\states.jsonl
                      Compressing C:\ioBroker\iobroker-data\objects.jsonl
                      Compressed 2 JSONL files. Done
                      NPM version: 10.5.2
                      Write "iobroker start" to start the ioBroker
                      npm install node-windows@1.0.0-beta.8 --force --loglevel error --production --save --prefix "C:/ioBroker"
                      
                      up to date, audited 619 packages in 9s
                      
                      72 packages are looking for funding
                        run `npm fund` for details
                      
                      26 vulnerabilities (21 moderate, 5 high)
                      
                      To address issues that do not require attention, run:
                        npm audit fix
                      
                      To address all issues possible (including breaking changes), run:
                        npm audit fix --force
                      
                      Some issues need review, and may require choosing
                      a different dependency.
                      
                      Run `npm audit` for details.
                      npm install dotenv@^16.3.1 --force --loglevel error --production --save --prefix "C:/ioBroker"
                      
                      up to date, audited 619 packages in 7s
                      
                      72 packages are looking for funding
                        run `npm fund` for details
                      
                      26 vulnerabilities (21 moderate, 5 high)
                      
                      To address issues that do not require attention, run:
                        npm audit fix
                      
                      To address all issues possible (including breaking changes), run:
                        npm audit fix --force
                      
                      Some issues need review, and may require choosing
                      a different dependency.
                      
                      Run `npm audit` for details.
                      npm install windows-shortcuts@^0.1.6 --force --loglevel error --production --save --prefix "C:/ioBroker"
                      
                      up to date, audited 619 packages in 7s
                      
                      72 packages are looking for funding
                        run `npm fund` for details
                      
                      26 vulnerabilities (21 moderate, 5 high)
                      
                      To address issues that do not require attention, run:
                        npm audit fix
                      
                      To address all issues possible (including breaking changes), run:
                        npm audit fix --force
                      
                      Some issues need review, and may require choosing
                      a different dependency.
                      
                      Run `npm audit` for details.
                      
                      =============================
                      Running Admin shell
                      =============================
                      ioBroker service name: ioBroker
                      ioBroker ist nicht gestartet.
                      
                      Sie erhalten weitere Hilfe, wenn Sie NET HELPMSG 3521 eingeben.
                      
                      Written iobnodevars.bat successfully.
                      ioBroker service is already installed.
                      Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Stop ioBroker Service.lnk" created with Admin flag!
                      Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Start ioBroker Service.lnk" created with Admin flag!
                      Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\Restart ioBroker Service.lnk" created with Admin flag!
                      Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Command line.lnk" created with Admin flag!
                      Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ioBroker automation platform\ioBroker Admin.lnk" created!
                      
                      =============================
                      Running Admin shell
                      =============================
                      ioBroker service name: ioBroker
                      ioBroker wird gestartet.
                      ioBroker wurde erfolgreich gestartet.
                      
                      ioBroker service installed and started. Go to http://localhost:8081 to open the admin UI.
                      To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller"
                      
                      C:\ioBroker>
                      

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

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

                      LESEN - gute Forenbeitrage

                      1 Antwort Letzte Antwort
                      0
                      • foxriver76F foxriver76

                        @mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

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

                        @foxriver76 sagte in Alpha Test js-controller Kiera (v6.0):

                        @mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

                        Ich hab das volle Log. Aber das sind 4300 Zeilen. Krieg ich nirgends hochgeladen.

                        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

                        HomoranH 1 Antwort Letzte Antwort
                        0
                        • Thomas BraunT Thomas Braun

                          @foxriver76 sagte in Alpha Test js-controller Kiera (v6.0):

                          @mcm1957 ja sollte reichen, Windows bin ich sowieso gespannt

                          Ich hab das volle Log. Aber das sind 4300 Zeilen. Krieg ich nirgends hochgeladen.

                          HomoranH Nicht stören
                          HomoranH Nicht stören
                          Homoran
                          Global Moderator Administrators
                          schrieb am zuletzt editiert von
                          #137

                          @thomas-braun .txt

                          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

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

                          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                          1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #138

                            @foxriver76 js-controller-inst-log.txt

                            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
                            • haus-automatisierungH haus-automatisierung

                              @tt-tom sagte in Alpha Test js-controller Kiera (v6.0):

                              Wollen wir damit in dein Test Thread wechseln??

                              Bitte als Issue auf GitHub öffnen. Sonst laufen da zig Themen durcheinander.

                              FeuersturmF Online
                              FeuersturmF Online
                              Feuersturm
                              schrieb am zuletzt editiert von
                              #139

                              @haus-automatisierung sagte in Alpha Test js-controller Kiera (v6.0):

                              Bitte als Issue auf GitHub öffnen. Sonst laufen da zig Themen durcheinander.

                              erledigt https://github.com/ioBroker/ioBroker.javascript/issues/1576
                              @TT-Tom fyi

                              1 Antwort Letzte Antwort
                              1
                              • foxriver76F foxriver76

                                Ansonsten bitte nochmal updaten und log von update zeigen

                                FeuersturmF Online
                                FeuersturmF Online
                                Feuersturm
                                schrieb am zuletzt editiert von
                                #140

                                @foxriver76
                                Update js-controller auf 6.0.1-alpha.0-20240524-14a872375

                                proxmox@ioBrokerTestsystem:~$ iob stop
                                proxmox@ioBrokerTestsystem:~$ cd /opt/iobroker/
                                proxmox@ioBrokerTestsystem:/opt/iobroker$ npm i iobroker.js-controller@next --om                                                                                                 it=dev
                                [sudo] password for proxmox:
                                npm warn ERESOLVE overriding peer dependency
                                npm warn While resolving: @mui/x-date-pickers@7.5.1
                                npm warn Found: @mui/material@5.14.14
                                npm warn node_modules/@iobroker/adapter-react-v5/node_modules/@mui/material
                                npm warn   @mui/material@"5.14.14" from @iobroker/adapter-react-v5@4.13.22
                                npm warn   node_modules/@iobroker/adapter-react-v5
                                npm warn     @iobroker/adapter-react-v5@"^4.13.13" from @iobroker/json-config@6.                                                                                                 17.13
                                npm warn     node_modules/@iobroker/json-config
                                npm warn     1 more (iobroker.radar-trap)
                                npm warn
                                npm warn Could not resolve dependency:
                                npm warn peer @mui/material@"^5.15.14" from @mui/x-date-pickers@7.5.1
                                npm warn node_modules/@iobroker/adapter-react-v5/node_modules/@mui/x-date-picker                                                                                                 s
                                npm warn   @mui/x-date-pickers@"^7.5.0" from @iobroker/adapter-react-v5@4.13.22
                                npm warn   node_modules/@iobroker/adapter-react-v5
                                npm warn
                                npm warn Conflicting peer dependency: @mui/material@5.15.18
                                npm warn node_modules/@mui/material
                                npm warn   peer @mui/material@"^5.15.14" from @mui/x-date-pickers@7.5.1
                                npm warn   node_modules/@iobroker/adapter-react-v5/node_modules/@mui/x-date-pick                                                                                                 ers
                                npm warn     @mui/x-date-pickers@"^7.5.0" from @iobroker/adapter-react-v5@4.13.2                                                                                                 2
                                npm warn     node_modules/@iobroker/adapter-react-v5
                                npm warn reify invalid or damaged lockfile detected
                                npm warn reify please re-try this operation once it completes
                                npm warn reify so that the damage can be corrected, or perform
                                npm warn reify a fresh install with no lockfile if the problem persists.
                                
                                changed 12 packages in 6m
                                
                                397 packages are looking for funding
                                  run `npm fund` for details
                                
                                

                                iobroker log vom start des Systems enthält keine relevanten Fehler

                                1 Antwort Letzte Antwort
                                0
                                • mcm1957M Online
                                  mcm1957M Online
                                  mcm1957
                                  schrieb am zuletzt editiert von
                                  #141

                                  @foxriver76

                                  Bitte samsung 0.6.0 in die Liste der zu aktualisierenden Adapter eintragen.

                                  Release ist im Latest.
                                  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
                                  • D Offline
                                    D Offline
                                    DLehmann
                                    schrieb am zuletzt editiert von
                                    #142

                                    update gemacht - das Testsystem startet.

                                    hier meine Instanzen

                                    root@iobroker-test:/opt/iobroker# iobroker list instances
                                    + system.adapter.adguard.0                : adguard               : iobroker-test                            -  enabled
                                    + system.adapter.admin.0                  : admin                 : iobroker-test                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                    + system.adapter.alexa2.0                 : alexa2                : iobroker-test                            -  enabled
                                      system.adapter.alias-manager.0          : alias-manager         : iobroker-test                            -  enabled
                                      system.adapter.backitup.0               : backitup              : iobroker-test                            - disabled
                                    + system.adapter.cloud.0                  : cloud                 : iobroker-test                            -  enabled
                                      system.adapter.daswetter.0              : daswetter             : iobroker-test                            -  enabled
                                      system.adapter.devices.0                : devices               : iobroker-test                            -  enabled
                                      system.adapter.discovery.0              : discovery             : iobroker-test                            - disabled
                                      system.adapter.dwd.0                    : dwd                   : iobroker-test                            -  enabled
                                      system.adapter.ecovacs-deebot.0         : ecovacs-deebot        : iobroker-test                            -  enabled
                                    + system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: iobroker-test                            -  enabled
                                      system.adapter.feiertage.0              : feiertage             : iobroker-test                            -  enabled
                                    + system.adapter.gotify.0                 : gotify                : iobroker-test                            -  enabled
                                      system.adapter.heatingcontrol.0         : heatingcontrol        : iobroker-test                            -  enabled
                                    + system.adapter.history.0                : history               : iobroker-test                            -  enabled
                                    + system.adapter.hm-rpc.0                 : hm-rpc                : iobroker-test                            -  enabled, port: 0
                                    + system.adapter.hm-rpc.1                 : hm-rpc                : iobroker-test                            -  enabled, port: 0
                                    + system.adapter.hue.0                    : hue                   : iobroker-test                            -  enabled, port: 443
                                    + system.adapter.iot.0                    : iot                   : iobroker-test                            -  enabled
                                    + system.adapter.iqontrol.0               : iqontrol              : iobroker-test                            -  enabled
                                      system.adapter.jarvis.0                 : jarvis                : iobroker-test                            -  enabled
                                    + system.adapter.javascript.0             : javascript            : iobroker-test                            -  enabled
                                    + system.adapter.ping.0                   : ping                  : iobroker-test                            -  enabled
                                    + system.adapter.pvforecast.0             : pvforecast            : iobroker-test                            -  enabled
                                      system.adapter.ring.0                   : ring                  : iobroker-test                            - disabled
                                    + system.adapter.scenes.0                 : scenes                : iobroker-test                            -  enabled
                                    + system.adapter.scheduler.0              : scheduler             : iobroker-test                            -  enabled
                                    + system.adapter.smartcontrol.0           : smartcontrol          : iobroker-test                            -  enabled
                                    + system.adapter.sonnen.0                 : sonnen                : iobroker-test                            -  enabled
                                    + system.adapter.tesla-motors.0           : tesla-motors          : iobroker-test                            -  enabled
                                    + system.adapter.teslamateapi.0           : teslamateapi          : iobroker-test                            -  enabled
                                      system.adapter.vis-materialdesign.0     : vis-materialdesign    : iobroker-test                            -  enabled
                                      system.adapter.vis.0                    : vis                   : iobroker-test                            -  enabled
                                    + system.adapter.web.0                    : web                   : iobroker-test                            -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                    
                                    + instance is alive
                                    

                                    Beim npm update kam folgende Meldung

                                    root@iobroker-test:/opt/iobroker# npm update
                                    npm WARN ERESOLVE overriding peer dependency
                                    npm WARN While resolving: @iobroker/adapter-core@3.1.4
                                    npm WARN Found: @iobroker/types@5.0.20-alpha.0-20240522-9b71d3242
                                    npm WARN node_modules/@iobroker/types
                                    npm WARN   @iobroker/types@"5.0.20-alpha.0-20240522-9b71d3242" from iobroker.admin@6.17.13
                                    npm WARN   node_modules/iobroker.admin
                                    npm WARN     iobroker.admin@"6.17.13" from the root project
                                    npm WARN 
                                    npm WARN Could not resolve dependency:
                                    npm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4
                                    npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-core
                                    npm WARN   @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13
                                    npm WARN   node_modules/iobroker.admin
                                    npm WARN 
                                    npm WARN Conflicting peer dependency: @iobroker/types@5.0.19
                                    npm WARN node_modules/@iobroker/types
                                    npm WARN   peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4
                                    npm WARN   node_modules/iobroker.admin/node_modules/@iobroker/adapter-core
                                    npm WARN     @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13
                                    npm WARN     node_modules/iobroker.admin
                                    
                                    up to date in 2m
                                    
                                    137 packages are looking for funding
                                      run `npm fund` for details
                                    

                                    Die drei Instanzen wollen nicht starten
                                    ecovacs-deebot
                                    heatingcontrol
                                    jarvis

                                    Folgende Fehlermeldungen kommen hierzu

                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	instance system.adapter.jarvis.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: Node.js v20.13.1
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/index.js:19:27)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:126:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: ^
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
                                    host.iobroker-test
                                    2024-05-24 20:39:36.517	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.jarvis/node_modules/@iobroker/adapter-core/build/controllerTools.js:83
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	instance system.adapter.heatingcontrol.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: Node.js v20.13.1
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/index.js:19:27)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:157:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: ^
                                    host.iobroker-test
                                    2024-05-24 20:39:33.235	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
                                    host.iobroker-test
                                    2024-05-24 20:39:33.234	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-core/build/controllerTools.js:83
                                    host.iobroker-test
                                    2024-05-24 20:39:30.682	error	instance system.adapter.ecovacs-deebot.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.682	error	Caught by controller[0]: Node.js v20.13.1
                                    host.iobroker-test
                                    2024-05-24 20:39:30.682	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.682	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/index.js:19:27)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at require (node:internal/modules/helpers:179:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:157:18)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:83:11)
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: ^
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`);
                                    host.iobroker-test
                                    2024-05-24 20:39:30.681	error	Caught by controller[0]: /opt/iobroker/node_modules/iobroker.ecovacs-deebot/node_modules/@iobroker/adapter-core/build/controllerTools.js:83
                                    
                                    1 Antwort Letzte Antwort
                                    0
                                    • foxriver76F foxriver76

                                      An alle: bitte nochmal updaten

                                      T Offline
                                      T Offline
                                      TT-Tom
                                      schrieb am zuletzt editiert von
                                      #143

                                      @foxriver76
                                      habe das Update eingespielt, lief ohne Probleme durch. Es sind auch alle Instanzen gestartet ohne Probleme. Da npm update mit der ersten Version von Hand ausgeführt wurde, kann ich nicht genau bestätigen, ob es jetzt funktioniert.
                                      schönes WE noch

                                      Gruß Tom
                                      https://github.com/tt-tom17
                                      Wenn meine Hilfe erfolgreich war, benutze bitte das Voting unten rechts im Beitrag

                                      NSPanel Script Wiki
                                      https://github.com/joBr99/nspanel-lovelace-ui/wiki

                                      NSPanel Adapter Wiki
                                      https://github.com/ticaki/ioBroker.nspanel-lovelace-ui/wiki

                                      1 Antwort Letzte Antwort
                                      0
                                      • foxriver76F Offline
                                        foxriver76F Offline
                                        foxriver76
                                        Developer
                                        schrieb am zuletzt editiert von
                                        #144

                                        Gerne nochmal updaten.

                                        Das Problem, dass er sich über invalide Instanz Objekte vom Typ device beschwert wurde behoben und nochmal ein anderer Versuch für die alten Adapter-Core Versionen wird ausprobiert.

                                        Videotutorials & mehr

                                        Hier könnt ihr mich unterstützen.

                                        Thomas BraunT FeuersturmF 3 Antworten Letzte Antwort
                                        1
                                        • foxriver76F foxriver76

                                          Gerne nochmal updaten.

                                          Das Problem, dass er sich über invalide Instanz Objekte vom Typ device beschwert wurde behoben und nochmal ein anderer Versuch für die alten Adapter-Core Versionen wird ausprobiert.

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

                                          @foxriver76

                                          echad@chet:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller@next --omit=dev
                                          npm WARN ERESOLVE overriding peer dependency
                                          npm WARN While resolving: @iobroker/adapter-core@3.1.4
                                          npm WARN Found: @iobroker/types@5.0.20-alpha.0-20240522-9b71d3242
                                          npm WARN node_modules/iobroker.admin/node_modules/@iobroker/types
                                          npm WARN   @iobroker/types@"5.0.20-alpha.0-20240522-9b71d3242" from iobroker.admin@6.17.13
                                          npm WARN   node_modules/iobroker.admin
                                          npm WARN     iobroker.admin@"6.17.13" from the root project
                                          npm WARN 
                                          npm WARN Could not resolve dependency:
                                          npm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4
                                          npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-core
                                          npm WARN   @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13
                                          npm WARN   node_modules/iobroker.admin
                                          npm WARN 
                                          npm WARN Conflicting peer dependency: @iobroker/types@5.0.19
                                          npm WARN node_modules/@iobroker/types
                                          npm WARN   peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4
                                          npm WARN   node_modules/iobroker.admin/node_modules/@iobroker/adapter-core
                                          npm WARN     @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.13
                                          npm WARN     node_modules/iobroker.admin
                                          
                                          added 35 packages, removed 196 packages, and changed 16 packages in 59s
                                          
                                          189 packages are looking for funding
                                            run `npm fund` for details
                                          echad@chet:/opt/iobroker $
                                          

                                          Die Meldungen zum Build mit letsencrypt sind weg, das Log ist soweit ruhig.

                                          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
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          757

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe