Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. BruderBleistift

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    B
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 33
    • Best 0
    • Groups 1

    BruderBleistift

    @BruderBleistift

    0
    Reputation
    25
    Profile views
    33
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    BruderBleistift Follow
    Starter

    Latest posts made by BruderBleistift

    • RE: Kein Adapter Update nach NodeJS 18 Update

      @thomas-braun
      Und wie gehe ich da am besten vor?

      Ich habe IOBroker nach Anleitung installiert.
      Nach und nach sind Adapter hinzugekommen.
      Für Admin Aktualisierungen wird ab und zu eine neue NodeJS Version benötigt, die ich ebenfalls nach den Anleitungen hier installiert hatte.
      Nach der letzten Aktualisierung NodeJS Aktualisierung ließen sich dann aber keine Adapter mehr aktualisieren.

      Das Ubuntu wurde ebenfalls regelmäßig auf dem aktuellen Stand gehalten.

      @crunchip sagte in Kein Adapter Update nach NodeJS 18 Update:

      du kannst dir die VM tausend mal zurückspielen, bestehende Fehler schleifst du dadurch aber weiter mit

      Wie gesagt. In dem Fall hat das nichts gebracht, weswegen ich zweigleisig fahre.

      Dass VIS mit BackItUp BackUps Probleme hat, scheint laut diesem Forum nicht neu zu sein und nicht nur mich zu betreffen. Aber ich gebe dir recht, da scheint BackItUp nicht schuld dran zu sein.

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: Kein Adapter Update nach NodeJS 18 Update

      @crunchip sagte in Kein Adapter Update nach NodeJS 18 Update:

      weshalb?

      • Der Admin ließ sich nach dem Einspielen des Backup nicht starten und es musste u.a. NodeJS und NPM neuinstalliert werden. Irgendwas musste noch gemacht werden, bekomme ich aber nicht mehr zusammen
      • Auch VIS ließ sich nicht mehr installieren, weil die Lizenz angeblich ungültig ist, obwohl ich als Privatperson keine benötige. Die alten VIS Seiten mussten anschließend alle manuell wiederhergestellt werden, was aber auch nicht reibungslos funktioniert (siehe unten).
      • Einige Javascripte verursachten Error ohne Ende -> war nach einer Neuanlage mit neuem Namen behoben.

      was läuft denn nicht?

      • Vieles von dem oben genannten konnte ich die letzten Tage beheben. Mir fehlen aber noch einige VIS Seiten, die sich scheinbar aus dem Backup nicht wiederherstellen lassen.

      Also alles in allem bin ich mit der BackUp Funktion ziemlich unzufrieden und bestätigt mich darin weiterhin die ganze VM mit Proxmox zu sichern. Das Wiederherstellen funktioniert absolut reibungslos.
      Hat mir in dem Fall natürlich nicht weitergeholfen, weil scheinbar meine IOBroker Installation ein Ding weg hatte.
      Also ein Tipp an alle was BackUps angeht: Immer schön zweigleisig fahren 👍 😀

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: Kein Adapter Update nach NodeJS 18 Update

      Nachdem ich alles neu aufgesetzt und das Backup wiederhergestellt habe, was auch noch ziemlich viel Kopfzerbrechen verursacht hat, läuft (fast) alles wieder.

      Danke euch für eure Hilfe. Hier kann dann zu.

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: Kein Adapter Update nach NodeJS 18 Update

      @thomas-braun

      Könnte sich das mit einem BackUp das ioBroker und Neuaufsetzen beheben lassen, oder stellt er da den ganzen Müll wieder her?

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: Kein Adapter Update nach NodeJS 18 Update

      @thomas-braun sagte in Kein Adapter Update nach NodeJS 18 Update:

      mal probiert?

      Erst meckert er wieder /opt/iobroker/node_modules/pcap an, dann führte ich den Einzeiler zum Löschen aus und setzte deinen Befehl nochmal ab.

      Das Ergebnis:

      paul@iobroker:/opt/iobroker/node_modules/openzwave-shared$ npm install --omit=dev
      [sudo] password for paul: 
      npm ERR! code ENOTEMPTY
      npm ERR! syscall rename
      npm ERR! path /opt/iobroker/node_modules/pcap
      npm ERR! dest /opt/iobroker/node_modules/.pcap-xkmgBhAF
      npm ERR! errno -39
      npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/pcap' -> '/opt/iobroker/node_modules/.pcap-xkmgBhAF'
      
      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-29T21_39_48_786Z-debug-0.log
      paul@iobroker:/opt/iobroker/node_modules/openzwave-shared$ cd
      paul@iobroker:~$ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%/}; done
      paul@iobroker:~$ cd /opt/iobroker/node_modules/openzwave-shared
      paul@iobroker:/opt/iobroker/node_modules/openzwave-shared$ npm install --omit=dev
      npm WARN skipping integrity check for git dependency ssh://git@github.com/nobl/ioBroker.tesla-wallconnector3.git 
      npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
      npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
      npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
      npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
      npm WARN cleanup Failed to remove some directories [
      npm WARN cleanup   [
      npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
      npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
      npm WARN cleanup       errno: -39,
      npm WARN cleanup       code: 'ENOTEMPTY',
      npm WARN cleanup       syscall: 'rmdir',
      npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
      npm WARN cleanup     }
      npm WARN cleanup   ],
      npm WARN cleanup   [
      npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
      npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
      npm WARN cleanup       errno: -39,
      npm WARN cleanup       code: 'ENOTEMPTY',
      npm WARN cleanup       syscall: 'rmdir',
      npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
      npm WARN cleanup     }
      npm WARN cleanup   ]
      npm WARN cleanup ]
      npm ERR! code 1
      npm ERR! path /opt/iobroker/node_modules/openzwave-shared
      npm ERR! command failed
      npm ERR! command sh -c node-gyp rebuild
      npm ERR! make: Entering directory '/opt/iobroker/node_modules/openzwave-shared/build'
      npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
      npm ERR! make: Leaving directory '/opt/iobroker/node_modules/openzwave-shared/build'
      npm ERR! gyp info it worked if it ends with ok
      npm ERR! gyp info using node-gyp@9.3.1
      npm ERR! gyp info using node@18.17.1 | linux | x64
      npm ERR! gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"
      npm ERR! gyp info spawn /usr/bin/python3
      npm ERR! gyp info spawn args [
      npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
      npm ERR! gyp info spawn args   'binding.gyp',
      npm ERR! gyp info spawn args   '-f',
      npm ERR! gyp info spawn args   'make',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/openzwave-shared/build/config.gypi',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.17.1/include/node/common.gypi',
      npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
      npm ERR! gyp info spawn args   '-Dvisibility=default',
      npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.17.1',
      npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
      npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',
      npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/openzwave-shared',
      npm ERR! gyp info spawn args   '-Dnode_engine=v8',
      npm ERR! gyp info spawn args   '--depth=.',
      npm ERR! gyp info spawn args   '--no-parallel',
      npm ERR! gyp info spawn args   '--generator-output',
      npm ERR! gyp info spawn args   'build',
      npm ERR! gyp info spawn args   '-Goutput_dir=.'
      npm ERR! gyp info spawn args ]
      npm ERR! gyp info spawn make
      npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
      npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-local-handle.h:12,
      npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:12,
      npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
      npm ERR!                  from ../src/openzwave.hpp:27,
      npm ERR!                  from ../src/callbacks.cc:18:
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                      ^~~~~~~~~~~
      npm ERR!       |                                      remove_cv
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                      ^~~~~~~~~~~
      npm ERR!       |                                      remove_cv
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:50: error: template argument 2 is invalid
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                                  ^
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:63: error: ‘::Perform’ has not been declared
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                                               ^~~~~~~
      npm ERR! make: *** [openzwave_shared.target.mk:150: Release/obj.target/openzwave_shared/src/callbacks.o] Error 1
      npm ERR! gyp ERR! build error 
      npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
      npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
      npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
      npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
      npm ERR! gyp ERR! System Linux 5.15.0-82-generic
      npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
      npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
      npm ERR! gyp ERR! node -v v18.17.1
      npm ERR! gyp ERR! node-gyp -v v9.3.1
      npm ERR! gyp ERR! not ok
      
      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-29T21_44_57_811Z-debug-0.log
      
      mikeal created this issue in request/request

      open Request’s Past, Present and Future #3142

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      mikeal created this issue in request/request

      open Request’s Past, Present and Future #3142

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • Kein Adapter Update nach NodeJS 18 Update

      Hallo zusammen,

      nach einem NodeJS Update kann ich keine Adapter mehr updaten.
      Ich habe bereits alle Tipps aus dem Forum umgesetzt. NodeJS nach @Thomas-Braun Anleitung neu installiert, seinen Einzeiler zum Löschen von unnötigen Ordnern und auch den iob Fix.

      -> iob upgrade admin --debug

      Would you like to upgrade admin from @6.3.5 to @6.8.0 now? [(y)es, (n)o]: y
      Update admin from @6.3.5 to @6.8.0
      NPM version: 9.6.7
      Installing iobroker.admin@6.8.0... (System call)
      npm ERR! code ENOTEMPTY
      npm ERR! syscall rename
      npm ERR! path /opt/iobroker/node_modules/pcap
      npm ERR! dest /opt/iobroker/node_modules/.pcap-xkmgBhAF
      npm ERR! errno -39
      npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/pcap' -> '/opt/iobroker/node_modules/.pcap-xkmgBhAF'
      
      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-29T20_24_24_645Z-debug-0.log
      host.iobroker Cannot install iobroker.admin@6.8.0: 217
      

      anschließend:

      paul@iobroker:~$ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%/}; done
      

      und erneut -> iob upgrade admin --debug

      Would you like to upgrade admin from @6.3.5 to @6.8.0 now? [(y)es, (n)o]: y
      Update admin from @6.3.5 to @6.8.0
      NPM version: 9.6.7
      Installing iobroker.admin@6.8.0... (System call)
      npm WARN skipping integrity check for git dependency ssh://git@github.com/nobl/ioBroker.tesla-wallconnector3.git 
      npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
      npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
      npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
      npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
      npm WARN cleanup Failed to remove some directories [
      npm WARN cleanup   [
      npm WARN cleanup     '/opt/iobroker/node_modules/unix-dgram',
      npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/unix-dgram'] {
      npm WARN cleanup       errno: -39,
      npm WARN cleanup       code: 'ENOTEMPTY',
      npm WARN cleanup       syscall: 'rmdir',
      npm WARN cleanup       path: '/opt/iobroker/node_modules/unix-dgram'
      npm WARN cleanup     }
      npm WARN cleanup   ],
      npm WARN cleanup   [
      npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
      npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
      npm WARN cleanup       errno: -39,
      npm WARN cleanup       code: 'ENOTEMPTY',
      npm WARN cleanup       syscall: 'rmdir',
      npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
      npm WARN cleanup     }
      npm WARN cleanup   ],
      npm WARN cleanup   [
      npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
      npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
      npm WARN cleanup       errno: -39,
      npm WARN cleanup       code: 'ENOTEMPTY',
      npm WARN cleanup       syscall: 'rmdir',
      npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
      npm WARN cleanup     }
      npm WARN cleanup   ]
      npm WARN cleanup ]
      npm ERR! code 1
      npm ERR! path /opt/iobroker/node_modules/openzwave-shared
      npm ERR! command failed
      npm ERR! command sh -c node-gyp rebuild
      npm ERR! make: Entering directory '/opt/iobroker/node_modules/openzwave-shared/build'
      npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
      npm ERR! make: Leaving directory '/opt/iobroker/node_modules/openzwave-shared/build'
      npm ERR! gyp info it worked if it ends with ok
      npm ERR! gyp info using node-gyp@9.3.1
      npm ERR! gyp info using node@18.17.1 | linux | x64
      npm ERR! gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"
      npm ERR! gyp info spawn /usr/bin/python3
      npm ERR! gyp info spawn args [
      npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
      npm ERR! gyp info spawn args   'binding.gyp',
      npm ERR! gyp info spawn args   '-f',
      npm ERR! gyp info spawn args   'make',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/openzwave-shared/build/config.gypi',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
      npm ERR! gyp info spawn args   '-I',
      npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.17.1/include/node/common.gypi',
      npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
      npm ERR! gyp info spawn args   '-Dvisibility=default',
      npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.17.1',
      npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
      npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',
      npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/openzwave-shared',
      npm ERR! gyp info spawn args   '-Dnode_engine=v8',
      npm ERR! gyp info spawn args   '--depth=.',
      npm ERR! gyp info spawn args   '--no-parallel',
      npm ERR! gyp info spawn args   '--generator-output',
      npm ERR! gyp info spawn args   'build',
      npm ERR! gyp info spawn args   '-Goutput_dir=.'
      npm ERR! gyp info spawn args ]
      npm ERR! gyp info spawn make
      npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
      npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-local-handle.h:12,
      npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:12,
      npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
      npm ERR!                  from ../src/openzwave.hpp:27,
      npm ERR!                  from ../src/callbacks.cc:18:
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                      ^~~~~~~~~~~
      npm ERR!       |                                      remove_cv
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                      ^~~~~~~~~~~
      npm ERR!       |                                      remove_cv
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:50: error: template argument 2 is invalid
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                                  ^
      npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-internal.h:646:63: error: ‘::Perform’ has not been declared
      npm ERR!   646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
      npm ERR!       |                                                               ^~~~~~~
      npm ERR! make: *** [openzwave_shared.target.mk:150: Release/obj.target/openzwave_shared/src/callbacks.o] Error 1
      npm ERR! gyp ERR! build error 
      npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
      npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
      npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
      npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
      npm ERR! gyp ERR! System Linux 5.15.0-82-generic
      npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
      npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
      npm ERR! gyp ERR! node -v v18.17.1
      npm ERR! gyp ERR! node-gyp -v v9.3.1
      npm ERR! gyp ERR! not ok
      
      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-29T20_31_58_414Z-debug-0.log
      upload [52] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png
      upload [50] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/customComponents.js.map custom/customComponents.js.map application/json
      upload [40] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/i18n/zh-cn.json custom/i18n/zh-cn.json application/json
      upload [30] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/node_modules_prop-types_index_js.512eddf9.chunk.js.map custom/static/js/node_modules_prop-types_index_js.512eddf9.chunk.js.map application/json
      upload [20] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map application/json
      upload [19] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js application/javascript
      upload [18] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map application/json
      upload [17] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_styles_index_js-node_modules_mui_utils_esm_capitalize_js-node_module-19fe07.82575832.chunk.js custom/static/js/vendors-node_modules_mui_styles_index_js-node_modules_mui_utils_esm_capitalize_js-node_module-19fe07.82575832.chunk.js application/javascript
      upload [16] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_styles_index_js-node_modules_mui_utils_esm_capitalize_js-node_module-19fe07.82575832.chunk.js.map custom/static/js/vendors-node_modules_mui_styles_index_js-node_modules_mui_utils_esm_capitalize_js-node_module-19fe07.82575832.chunk.js.map application/json
      upload [15] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_styles_withStyles_withStyles_js.6d998ff2.chunk.js custom/static/js/vendors-node_modules_mui_styles_withStyles_withStyles_js.6d998ff2.chunk.js application/javascript
      upload [14] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_mui_styles_withStyles_withStyles_js.6d998ff2.chunk.js.map custom/static/js/vendors-node_modules_mui_styles_withStyles_withStyles_js.6d998ff2.chunk.js.map application/json
      upload [13] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_react-dom_index_js.51544235.chunk.js custom/static/js/vendors-node_modules_react-dom_index_js.51544235.chunk.js application/javascript
      upload [12] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/custom/static/js/vendors-node_modules_react-dom_index_js.51544235.chunk.js.map custom/static/js/vendors-node_modules_react-dom_index_js.51544235.chunk.js.map application/json
      upload [11] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/de/translations.json i18n/de/translations.json application/json
      upload [10] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/en/translations.json i18n/en/translations.json application/json
      upload [9] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/es/translations.json i18n/es/translations.json application/json
      upload [8] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
      upload [7] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/it/translations.json i18n/it/translations.json application/json
      upload [6] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
      upload [5] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
      upload [4] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
      upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
      upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/uk/translations.json i18n/uk/translations.json application/json
      upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
      upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/jsonConfig.json5 jsonConfig.json5 application/json5
      

      Der Vollständigkeit halber noch die folgenden Infos.

      paul@iobroker:~$ uname -m && type -P nodejs node npm npx corepack && nodejs -v && node -v && npm -v && npx -v && corepack -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt-get update &> /dev/null && sudo apt-get update && apt-cache policy nodejs
      x86_64
      /usr/bin/nodejs
      /usr/bin/node
      /usr/bin/npm
      /usr/bin/npx
      /usr/bin/corepack
      v18.17.1
      v18.17.1
      9.6.7
      9.6.7
      0.18.0
      4.0.24
      paul
      paul adm cdrom sudo dip plugdev lxd iobroker
      tty
      /home/paul
      OK:1 https://dl.yarnpkg.com/debian stable InRelease
      Holen:2 https://deb.nodesource.com/node_18.x jammy InRelease [4.563 B]
      OK:3 http://archive.ubuntu.com/ubuntu jammy InRelease
      OK:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
      OK:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
      OK:6 http://archive.ubuntu.com/ubuntu jammy-security InRelease
      Es wurden 4.563 B in 2 s geholt (2.823 B/s).
      Paketlisten werden gelesen… Fertig
      nodejs:
        Installiert:           18.17.1-deb-1nodesource1
        Installationskandidat: 18.17.1-deb-1nodesource1
        Versionstabelle:
       *** 18.17.1-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages
              100 /var/lib/dpkg/status
           12.22.9~dfsg-1ubuntu3 500
              500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
      

      Ich hoffe mir kann irgendjemand weiterhelfen. Ich verzweifle langsam - mittlerweile kann ich den Admin auch nicht mehr öffnen.

      Vielen Dank im Voraus und Gruß,
      Paul

      mikeal created this issue in request/request

      open Request’s Past, Present and Future #3142

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      Qix- created this issue in visionmedia/debug

      closed ReDos Vulnerability Regression Visibility Notice #797

      mikeal created this issue in request/request

      open Request’s Past, Present and Future #3142

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: IoBroker und ipodmini einbinden

      Gibt es hier mittlerweile etwas neues?
      Lässt sich der HomePod irgendwie einbinden?
      Mir geht es nicht um das abspielen von Tönen oder Musik, sondern ich hätte gern Zugriff auf den Temperatursensor.

      posted in ioBroker Allgemein
      B
      BruderBleistift
    • RE: Lay-Z-Spa Wifi Control

      Habe seit ca. 2 Wochen das Problem, dass sich das Modul scheinbar aufhängt.
      Es ist dann nicht mehr möglich den Pool über die Tasten zu bedienen und auch über das Webinterface ist es nicht mehr erreichbar.

      Beheben lässt es sich, indem ich kurz den Strom kappe. Dann startet das Modul neu und es funktioniert wieder - für 1-2 Tage.

      Hat das Problem noch jemand, oder Ideen woran es liegen könnte? Eventuell ein Überhitzungsproblem? Lässt sich auf dem ESP irgendwie ein Kühlkörper anbringen und würde das in dem geschlossenen Pumpengehäuse überhaupt etwas bringen?

      posted in Hardware
      B
      BruderBleistift
    • RE: Lay-Z-Spa Wifi Control

      Habe heute alles zusammen- und eingebaut. Vielen Dank an Marc für die Platine und an Meistertr für die Gehäusevorlage, welche ich noch um 6mm erhöht habe, weil mein Zusammenbau durch die Female Header Pins etwas höher war.

      Nun aber zu meiner Frage. Beim Zusammenbau und dem Aufsetzen des Deckels lief bei mir die Umwälzpumpe. Dabei ist mir aufgefallen, wieviel lauter es mit Deckel durch den Resonanzkörper brummt. Also habe ich das Gehäuse zum Testen mit einer dicken Decke gefüllt, was dazu führte, dass die Umwälzpumpe fast nicht mehr zu hören war.
      Die Decke kann da aus verschiedensten Gründen natürlich nicht drin bleiben, aber kann ich den Deckel anders füllen, oder führt das zu einem Hitzestau? Aktuell hat die Pumpe nur unten Lüftungsschlitze und ist oben geschlossen.

      Ich habe dabei gedacht an:

      • Bauschaum (Bringt das etwas?)
      • Noppenschaumstoff (Schimmelgefahr?)
      • Styropor (Sehr unflexibel beim Verlegen + Wirkung?)

      Habt Ihr irgendwelche Ideen, oder sollte ich das aufgrund des eventuellen Hitzestaus generell lassen?

      posted in Hardware
      B
      BruderBleistift
    • RE: Lay-Z-Spa Wifi Control

      @Marc79 @Crizz Würde euch gern eine Platine abnehmen, aber leider scheinen meine privaten Nachrichten bei euch nicht anzukommen?

      posted in Hardware
      B
      BruderBleistift
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo