Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 3.0/3.1 jetzt im Latest!

NEWS

  • Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar
    BluefoxB
    Bluefox
    11
    2
    198

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

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

js-controller 3.0/3.1 jetzt im Latest!

js-controller 3.0/3.1 jetzt im Latest!

Scheduled Pinned Locked Moved ioBroker Allgemein
js-controller
1.3k Posts 127 Posters 493.9k Views 89 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • apollon77A apollon77

    @dslraser Issue bitte beim Adapter anlegen

    dslraserD Offline
    dslraserD Offline
    dslraser
    Forum Testing Most Active
    wrote on last edited by
    #487

    @apollon77 sagte in js-controller 3.0 jetzt im Latest!:

    @dslraser Issue bitte beim Adapter anlegen

    erledigt

    1 Reply Last reply
    0
    • DiginixD Offline
      DiginixD Offline
      Diginix
      wrote on last edited by
      #488

      @apollon77 Bin nun auch auf 3.0.19 und bisher alles grün und unauffällig. 👍 👏

      ..:: So long! Tom ::..

      NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

      1 Reply Last reply
      1
      • apollon77A apollon77

        @LJSven Naja das "iobroker upgrade" an sich kann man machen muss man nicht ... updated halt alle Adapter.

        Ja sieht sinnvoll aus ... aber hey dabei kann so viel schief gehen in jedem einzelnen Schritt .... nee das macht man besser selbst schritt für schritt

        E Online
        E Online
        e-s
        wrote on last edited by e-s
        #489

        @apollon77
        Weiß nicht ob der Fehler schon bekannt ist Mir ist klar, gehört eigentlich zum devices Adapter. aber auf die schnelle ist es hier einfacher.
        Beim deinstallieren des devices Adapter:

        host.ubuntuserver	2020-04-27 21:33:52.259	info	iobroker exit 0
        host.ubuntuserver	2020-04-27 21:33:48.951	info	iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1
        host.ubuntuserver	2020-04-27 21:33:48.942	info	iobroker npm
        host.ubuntuserver	2020-04-27 21:33:29.801	error	Cannot write files: /opt/iobroker/iobroker-data/files/devices.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/devices.admin/_data.json'
        host.ubuntuserver	2020-04-27 21:33:29.649	info	iobroker npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.npm WARN npm You can find the latest version at https://nodejs.org/
        host.ubuntuserver	2020-04-27 21:33:29.642	info	iobroker WARN npm npm does not support Node.js v14.0.0npm WARN npm You should probably upgrade to a newer version of node as wenpm WARN npm can't make any promises that npm will work with this versi
        host.ubuntuserver	2020-04-27 21:33:29.641	info	iobroker npm
        host.ubuntuserver	2020-04-27 21:33:28.975	info	iobroker npm uninstall iobroker.devices --error --prefix "/opt/iobroker" (System call)
        host.ubuntuserver	2020-04-27 21:33:28.824	info	iobroker host.ubuntuserver object devices.admin deletedhost.ubuntuserver Deleting 2 object(s).
        host.ubuntuserver	2020-04-27 21:33:28.804	info	iobroker host.ubuntuserver file devices.admin deleted
        readDir	2020-04-27 21:33:28.770	warn	will not read this directory () in future versions: devices is not an object of type "meta"
        readDir	2020-04-27 21:33:28.764	warn	will not read this directory (widgets/devices.html/) in future versions: vis is not an object of type "meta"
        readDir	2020-04-27 21:33:28.756	warn	will not read this directory (widgets/devices/) in future versions: vis is not an object of type "meta"
        host.ubuntuserver	2020-04-27 21:33:27.181	info	iobroker host.ubuntuserver Counted 1 adapter for devices
        host.ubuntuserver	2020-04-27 21:33:27.176	info	iobroker host.ubuntuserver Counted 1 meta of devices
        host.ubuntuserver	2020-04-27 21:33:27.104	info	iobroker Delete adapter "devices"
        host.ubuntuserver	2020-04-27 21:33:24.465	info	iobroker del devices
        

        Ach ja, gehört zum bosesoundtouch:

        bosesoundtouch.0	2020-04-27 21:13:19.940	info	(18695) connecting to host ws://192.168.2.128:8080/
        bosesoundtouch.0	2020-04-27 21:13:18.684	info	(18695) starting. Version 0.9.2 in /opt/iobroker/node_modules/iobroker.bosesoundtouch, node: v14.0.0, js-controller: 3.0.19
        bosesoundtouch.0	2020-04-27 21:13:18.679	error	(18695) : message handler implemented, but messagebox not enabled. Define common.messagebox in io-package.json for adapter or delete message handler.
        
        wendy2702W 2 Replies Last reply
        0
        • E e-s

          @apollon77
          Weiß nicht ob der Fehler schon bekannt ist Mir ist klar, gehört eigentlich zum devices Adapter. aber auf die schnelle ist es hier einfacher.
          Beim deinstallieren des devices Adapter:

          host.ubuntuserver	2020-04-27 21:33:52.259	info	iobroker exit 0
          host.ubuntuserver	2020-04-27 21:33:48.951	info	iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1
          host.ubuntuserver	2020-04-27 21:33:48.942	info	iobroker npm
          host.ubuntuserver	2020-04-27 21:33:29.801	error	Cannot write files: /opt/iobroker/iobroker-data/files/devices.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/devices.admin/_data.json'
          host.ubuntuserver	2020-04-27 21:33:29.649	info	iobroker npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.npm WARN npm You can find the latest version at https://nodejs.org/
          host.ubuntuserver	2020-04-27 21:33:29.642	info	iobroker WARN npm npm does not support Node.js v14.0.0npm WARN npm You should probably upgrade to a newer version of node as wenpm WARN npm can't make any promises that npm will work with this versi
          host.ubuntuserver	2020-04-27 21:33:29.641	info	iobroker npm
          host.ubuntuserver	2020-04-27 21:33:28.975	info	iobroker npm uninstall iobroker.devices --error --prefix "/opt/iobroker" (System call)
          host.ubuntuserver	2020-04-27 21:33:28.824	info	iobroker host.ubuntuserver object devices.admin deletedhost.ubuntuserver Deleting 2 object(s).
          host.ubuntuserver	2020-04-27 21:33:28.804	info	iobroker host.ubuntuserver file devices.admin deleted
          readDir	2020-04-27 21:33:28.770	warn	will not read this directory () in future versions: devices is not an object of type "meta"
          readDir	2020-04-27 21:33:28.764	warn	will not read this directory (widgets/devices.html/) in future versions: vis is not an object of type "meta"
          readDir	2020-04-27 21:33:28.756	warn	will not read this directory (widgets/devices/) in future versions: vis is not an object of type "meta"
          host.ubuntuserver	2020-04-27 21:33:27.181	info	iobroker host.ubuntuserver Counted 1 adapter for devices
          host.ubuntuserver	2020-04-27 21:33:27.176	info	iobroker host.ubuntuserver Counted 1 meta of devices
          host.ubuntuserver	2020-04-27 21:33:27.104	info	iobroker Delete adapter "devices"
          host.ubuntuserver	2020-04-27 21:33:24.465	info	iobroker del devices
          

          Ach ja, gehört zum bosesoundtouch:

          bosesoundtouch.0	2020-04-27 21:13:19.940	info	(18695) connecting to host ws://192.168.2.128:8080/
          bosesoundtouch.0	2020-04-27 21:13:18.684	info	(18695) starting. Version 0.9.2 in /opt/iobroker/node_modules/iobroker.bosesoundtouch, node: v14.0.0, js-controller: 3.0.19
          bosesoundtouch.0	2020-04-27 21:13:18.679	error	(18695) : message handler implemented, but messagebox not enabled. Define common.messagebox in io-package.json for adapter or delete message handler.
          
          wendy2702W Online
          wendy2702W Online
          wendy2702
          wrote on last edited by
          #490

          @e-s sagte in js-controller 3.0 jetzt im Latest!:

          Node.js v14.0.0

          Kann auch eher daran liegen das du scheinbar schon NODEJS 14 verwendest.

          Bitte keine Fragen per PN, die gehören ins Forum!

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

          E 1 Reply Last reply
          0
          • wendy2702W wendy2702

            @e-s sagte in js-controller 3.0 jetzt im Latest!:

            Node.js v14.0.0

            Kann auch eher daran liegen das du scheinbar schon NODEJS 14 verwendest.

            E Online
            E Online
            e-s
            wrote on last edited by
            #491

            @wendy2702
            könnte auch sein, sonst macht 14 aber scheinbar keine Probleme

            Thomas BraunT 1 Reply Last reply
            0
            • E e-s

              @apollon77
              Weiß nicht ob der Fehler schon bekannt ist Mir ist klar, gehört eigentlich zum devices Adapter. aber auf die schnelle ist es hier einfacher.
              Beim deinstallieren des devices Adapter:

              host.ubuntuserver	2020-04-27 21:33:52.259	info	iobroker exit 0
              host.ubuntuserver	2020-04-27 21:33:48.951	info	iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1
              host.ubuntuserver	2020-04-27 21:33:48.942	info	iobroker npm
              host.ubuntuserver	2020-04-27 21:33:29.801	error	Cannot write files: /opt/iobroker/iobroker-data/files/devices.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/devices.admin/_data.json'
              host.ubuntuserver	2020-04-27 21:33:29.649	info	iobroker npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.npm WARN npm You can find the latest version at https://nodejs.org/
              host.ubuntuserver	2020-04-27 21:33:29.642	info	iobroker WARN npm npm does not support Node.js v14.0.0npm WARN npm You should probably upgrade to a newer version of node as wenpm WARN npm can't make any promises that npm will work with this versi
              host.ubuntuserver	2020-04-27 21:33:29.641	info	iobroker npm
              host.ubuntuserver	2020-04-27 21:33:28.975	info	iobroker npm uninstall iobroker.devices --error --prefix "/opt/iobroker" (System call)
              host.ubuntuserver	2020-04-27 21:33:28.824	info	iobroker host.ubuntuserver object devices.admin deletedhost.ubuntuserver Deleting 2 object(s).
              host.ubuntuserver	2020-04-27 21:33:28.804	info	iobroker host.ubuntuserver file devices.admin deleted
              readDir	2020-04-27 21:33:28.770	warn	will not read this directory () in future versions: devices is not an object of type "meta"
              readDir	2020-04-27 21:33:28.764	warn	will not read this directory (widgets/devices.html/) in future versions: vis is not an object of type "meta"
              readDir	2020-04-27 21:33:28.756	warn	will not read this directory (widgets/devices/) in future versions: vis is not an object of type "meta"
              host.ubuntuserver	2020-04-27 21:33:27.181	info	iobroker host.ubuntuserver Counted 1 adapter for devices
              host.ubuntuserver	2020-04-27 21:33:27.176	info	iobroker host.ubuntuserver Counted 1 meta of devices
              host.ubuntuserver	2020-04-27 21:33:27.104	info	iobroker Delete adapter "devices"
              host.ubuntuserver	2020-04-27 21:33:24.465	info	iobroker del devices
              

              Ach ja, gehört zum bosesoundtouch:

              bosesoundtouch.0	2020-04-27 21:13:19.940	info	(18695) connecting to host ws://192.168.2.128:8080/
              bosesoundtouch.0	2020-04-27 21:13:18.684	info	(18695) starting. Version 0.9.2 in /opt/iobroker/node_modules/iobroker.bosesoundtouch, node: v14.0.0, js-controller: 3.0.19
              bosesoundtouch.0	2020-04-27 21:13:18.679	error	(18695) : message handler implemented, but messagebox not enabled. Define common.messagebox in io-package.json for adapter or delete message handler.
              
              wendy2702W Online
              wendy2702W Online
              wendy2702
              wrote on last edited by
              #492

              @e-s sagte in js-controller 3.0 jetzt im Latest!:

              iobroker WARN npm npm does not support Node.js v14.0.0npm WARN npm You should probably upgrade to a newer version of node as wenpm WARN npm can't make any promises that npm will work with this versi

              Glaube in deinem Fall ziemlich eindeutig.

              Bitte keine Fragen per PN, die gehören ins Forum!

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

              1 Reply Last reply
              0
              • E e-s

                @wendy2702
                könnte auch sein, sonst macht 14 aber scheinbar keine Probleme

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                wrote on last edited by
                #493

                @e-s Offenbar node nicht richtig installiert. Dein npm kommt aus einer anderen Version.

                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

                E 1 Reply Last reply
                0
                • Thomas BraunT Thomas Braun

                  @e-s Offenbar node nicht richtig installiert. Dein npm kommt aus einer anderen Version.

                  E Online
                  E Online
                  e-s
                  wrote on last edited by
                  #494

                  @Thomas-Braun @wendy2702

                  build@ubuntuserver:/opt/iobroker$ npm
                  npm WARN npm npm does not support Node.js v14.0.0
                  npm WARN npm You should probably upgrade to a newer version of node as we
                  npm WARN npm can't make any promises that npm will work with this version.
                  npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.
                  npm WARN npm You can find the latest version at https://nodejs.org/
                  
                  

                  Wenn ich mich recht erinnere, dann meckert npm rum wenn es nicht aktuell ist und man ein Update machen kann. So wie ich das verstehe ist npm einfach offiziell noch nicht soweit node14 zu benutzen, oder?
                  Aber ich glaube das ist nur ein Hinweis den ich ignorieren kann.

                  Thomas BraunT 1 Reply Last reply
                  0
                  • E e-s

                    @Thomas-Braun @wendy2702

                    build@ubuntuserver:/opt/iobroker$ npm
                    npm WARN npm npm does not support Node.js v14.0.0
                    npm WARN npm You should probably upgrade to a newer version of node as we
                    npm WARN npm can't make any promises that npm will work with this version.
                    npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.
                    npm WARN npm You can find the latest version at https://nodejs.org/
                    
                    

                    Wenn ich mich recht erinnere, dann meckert npm rum wenn es nicht aktuell ist und man ein Update machen kann. So wie ich das verstehe ist npm einfach offiziell noch nicht soweit node14 zu benutzen, oder?
                    Aber ich glaube das ist nur ein Hinweis den ich ignorieren kann.

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    wrote on last edited by
                    #495

                    @e-s Ein aktuelles npm funktioniert auch mit einem aktuellen node. Hier läuft auch node 14 und npm, allerdings ohne die Meldungen die du da siehst.

                    npm -v
                    6.14.4
                    

                    Ignorieren würde ich das nicht, das sorgt früher oder später für Ärger.

                    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

                    E 1 Reply Last reply
                    0
                    • Thomas BraunT Thomas Braun

                      @e-s Ein aktuelles npm funktioniert auch mit einem aktuellen node. Hier läuft auch node 14 und npm, allerdings ohne die Meldungen die du da siehst.

                      npm -v
                      6.14.4
                      

                      Ignorieren würde ich das nicht, das sorgt früher oder später für Ärger.

                      E Online
                      E Online
                      e-s
                      wrote on last edited by
                      #496

                      @Thomas-Braun
                      ok, danke erstmal. den npm Fehler habe ich jetzt weg. Dafür habe ich einen Fehler im npm rebuild vom serialport, wofür auch immer der ist.

                         V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                           ^~~
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                      ../src/serialport.cpp:331:96: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)â
                           results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));
                                                                                                                      ^
                      In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                       from ../../nan/nan.h:56,
                                       from ../src/./serialport.h:6,
                                       from ../src/serialport.cpp:1:
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                         V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                           ^~~
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                         V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                           ^~~
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                      ../src/serialport.cpp:336:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                         data->callback.Call(2, argv);
                                                    ^
                      In file included from ../src/./serialport.h:6:0,
                                       from ../src/serialport.cpp:1:
                      ../../nan/nan.h:1742:3: note: declared here
                         Call(int argc, v8::Local<v8::Value> argv[]) const {
                         ^~~~
                      ../src/serialport.cpp: In function âvoid EIO_AfterGetBaudRate(uv_work_t*)â:
                      ../src/serialport.cpp:378:106: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)â
                           results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));
                                                                                                                                ^
                      In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                       from ../../nan/nan.h:56,
                                       from ../src/./serialport.h:6,
                                       from ../src/serialport.cpp:1:
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                         V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                           ^~~
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                         V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                           ^~~
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                      ../src/serialport.cpp:383:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                         data->callback.Call(2, argv);
                                                    ^
                      In file included from ../src/./serialport.h:6:0,
                                       from ../src/serialport.cpp:1:
                      ../../nan/nan.h:1742:3: note: declared here
                         Call(int argc, v8::Local<v8::Value> argv[]) const {
                         ^~~~
                      ../src/serialport.cpp: In function âvoid EIO_AfterDrain(uv_work_t*)â:
                      ../src/serialport.cpp:424:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                         data->callback.Call(1, argv);
                                                    ^
                      In file included from ../src/./serialport.h:6:0,
                                       from ../src/serialport.cpp:1:
                      ../../nan/nan.h:1742:3: note: declared here
                         Call(int argc, v8::Local<v8::Value> argv[]) const {
                         ^~~~
                      ../src/serialport.cpp: At global scope:
                      ../src/serialport.cpp:460:17: error: variable or field âinitâ declared void
                         void init(v8::Handle<v8::Object> target) {
                                       ^~~~~~
                      ../src/serialport.cpp:460:17: error: âHandleâ is not a member of âv8â
                      ../src/serialport.cpp:460:34: error: expected primary-expression before â>â token
                         void init(v8::Handle<v8::Object> target) {
                                                        ^
                      ../src/serialport.cpp:460:36: error: âtargetâ was not declared in this scope
                         void init(v8::Handle<v8::Object> target) {
                                                          ^~~~~~
                      ../src/serialport.cpp:460:36: note: suggested alternative: âtzsetâ
                         void init(v8::Handle<v8::Object> target) {
                                                          ^~~~~~
                                                          tzset
                      In file included from ../../nan/nan.h:56:0,
                                       from ../src/./serialport.h:6,
                                       from ../src/serialport.cpp:1:
                      ../src/serialport.cpp:485:25: error: âinitâ was not declared in this scope
                       NODE_MODULE(serialport, init);
                                               ^
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                             (node::addon_register_func) (regfunc),                          \
                                                          ^~~~~~~
                      ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                       NODE_MODULE(serialport, init);
                       ^~~~~~~~~~~
                      ../src/serialport.cpp:485:25: note: suggested alternative: âintâ
                       NODE_MODULE(serialport, init);
                                               ^
                      /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                             (node::addon_register_func) (regfunc),                          \
                                                          ^~~~~~~
                      ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                       NODE_MODULE(serialport, init);
                       ^~~~~~~~~~~
                      serialport.target.mk:114: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
                      make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
                      make: Verzeichnis â/opt/iobroker/node_modules/serialport/buildâ wird verlassen
                      gyp ERR! build error
                      gyp ERR! stack Error: `make` failed with exit code: 2
                      gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                      gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                      gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                      gyp ERR! System Linux 4.15.0-96-generic
                      gyp ERR! command "/usr/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                      gyp ERR! cwd /opt/iobroker/node_modules/serialport
                      gyp ERR! node -v v14.0.0
                      gyp ERR! node-gyp -v v5.1.0
                      gyp ERR! not ok
                      npm ERR! code ELIFECYCLE
                      npm ERR! errno 1
                      npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
                      npm ERR! Exit status 1
                      npm ERR!
                      npm ERR! Failed at the serialport@6.2.2 install script.
                      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                      
                      npm ERR! A complete log of this run can be found in:
                      npm ERR!     /home/iobroker/.npm/_logs/2020-04-27T21_15_55_218Z-debug.log
                      
                      
                      apollon77A K 2 Replies Last reply
                      0
                      • E e-s

                        @Thomas-Braun
                        ok, danke erstmal. den npm Fehler habe ich jetzt weg. Dafür habe ich einen Fehler im npm rebuild vom serialport, wofür auch immer der ist.

                           V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                             ^~~
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                        ../src/serialport.cpp:331:96: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)â
                             results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));
                                                                                                                        ^
                        In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                         from ../../nan/nan.h:56,
                                         from ../src/./serialport.h:6,
                                         from ../src/serialport.cpp:1:
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                           V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                             ^~~
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                           V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                             ^~~
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                        ../src/serialport.cpp:336:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                           data->callback.Call(2, argv);
                                                      ^
                        In file included from ../src/./serialport.h:6:0,
                                         from ../src/serialport.cpp:1:
                        ../../nan/nan.h:1742:3: note: declared here
                           Call(int argc, v8::Local<v8::Value> argv[]) const {
                           ^~~~
                        ../src/serialport.cpp: In function âvoid EIO_AfterGetBaudRate(uv_work_t*)â:
                        ../src/serialport.cpp:378:106: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)â
                             results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));
                                                                                                                                  ^
                        In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                         from ../../nan/nan.h:56,
                                         from ../src/./serialport.h:6,
                                         from ../src/serialport.cpp:1:
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                           V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                             ^~~
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                           V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                             ^~~
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                        ../src/serialport.cpp:383:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                           data->callback.Call(2, argv);
                                                      ^
                        In file included from ../src/./serialport.h:6:0,
                                         from ../src/serialport.cpp:1:
                        ../../nan/nan.h:1742:3: note: declared here
                           Call(int argc, v8::Local<v8::Value> argv[]) const {
                           ^~~~
                        ../src/serialport.cpp: In function âvoid EIO_AfterDrain(uv_work_t*)â:
                        ../src/serialport.cpp:424:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                           data->callback.Call(1, argv);
                                                      ^
                        In file included from ../src/./serialport.h:6:0,
                                         from ../src/serialport.cpp:1:
                        ../../nan/nan.h:1742:3: note: declared here
                           Call(int argc, v8::Local<v8::Value> argv[]) const {
                           ^~~~
                        ../src/serialport.cpp: At global scope:
                        ../src/serialport.cpp:460:17: error: variable or field âinitâ declared void
                           void init(v8::Handle<v8::Object> target) {
                                         ^~~~~~
                        ../src/serialport.cpp:460:17: error: âHandleâ is not a member of âv8â
                        ../src/serialport.cpp:460:34: error: expected primary-expression before â>â token
                           void init(v8::Handle<v8::Object> target) {
                                                          ^
                        ../src/serialport.cpp:460:36: error: âtargetâ was not declared in this scope
                           void init(v8::Handle<v8::Object> target) {
                                                            ^~~~~~
                        ../src/serialport.cpp:460:36: note: suggested alternative: âtzsetâ
                           void init(v8::Handle<v8::Object> target) {
                                                            ^~~~~~
                                                            tzset
                        In file included from ../../nan/nan.h:56:0,
                                         from ../src/./serialport.h:6,
                                         from ../src/serialport.cpp:1:
                        ../src/serialport.cpp:485:25: error: âinitâ was not declared in this scope
                         NODE_MODULE(serialport, init);
                                                 ^
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                               (node::addon_register_func) (regfunc),                          \
                                                            ^~~~~~~
                        ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                         NODE_MODULE(serialport, init);
                         ^~~~~~~~~~~
                        ../src/serialport.cpp:485:25: note: suggested alternative: âintâ
                         NODE_MODULE(serialport, init);
                                                 ^
                        /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                               (node::addon_register_func) (regfunc),                          \
                                                            ^~~~~~~
                        ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                         NODE_MODULE(serialport, init);
                         ^~~~~~~~~~~
                        serialport.target.mk:114: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
                        make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
                        make: Verzeichnis â/opt/iobroker/node_modules/serialport/buildâ wird verlassen
                        gyp ERR! build error
                        gyp ERR! stack Error: `make` failed with exit code: 2
                        gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                        gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                        gyp ERR! System Linux 4.15.0-96-generic
                        gyp ERR! command "/usr/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                        gyp ERR! cwd /opt/iobroker/node_modules/serialport
                        gyp ERR! node -v v14.0.0
                        gyp ERR! node-gyp -v v5.1.0
                        gyp ERR! not ok
                        npm ERR! code ELIFECYCLE
                        npm ERR! errno 1
                        npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
                        npm ERR! Exit status 1
                        npm ERR!
                        npm ERR! Failed at the serialport@6.2.2 install script.
                        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                        
                        npm ERR! A complete log of this run can be found in:
                        npm ERR!     /home/iobroker/.npm/_logs/2020-04-27T21_15_55_218Z-debug.log
                        
                        
                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        wrote on last edited by
                        #497

                        @e-s Da scheint irgendeiner Deiner Adapter noch serialpot 6 zu nutzen was mit Node 12 schon nicht mehr geescheit tut. Also hier wäre der Tipp mal die Adapter zu prüfen die Seriell arbeiten ob es Updates gibt

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        E 1 Reply Last reply
                        0
                        • E e-s

                          @Thomas-Braun
                          ok, danke erstmal. den npm Fehler habe ich jetzt weg. Dafür habe ich einen Fehler im npm rebuild vom serialport, wofür auch immer der ist.

                             V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                               ^~~
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                          ../src/serialport.cpp:331:96: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)â
                               results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));
                                                                                                                          ^
                          In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                           from ../../nan/nan.h:56,
                                           from ../src/./serialport.h:6,
                                           from ../src/serialport.cpp:1:
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                             V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                               ^~~
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                             V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                               ^~~
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                          ../src/serialport.cpp:336:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                             data->callback.Call(2, argv);
                                                        ^
                          In file included from ../src/./serialport.h:6:0,
                                           from ../src/serialport.cpp:1:
                          ../../nan/nan.h:1742:3: note: declared here
                             Call(int argc, v8::Local<v8::Value> argv[]) const {
                             ^~~~
                          ../src/serialport.cpp: In function âvoid EIO_AfterGetBaudRate(uv_work_t*)â:
                          ../src/serialport.cpp:378:106: error: no matching function for call to âv8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)â
                               results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));
                                                                                                                                    ^
                          In file included from /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:67:0,
                                           from ../../nan/nan.h:56,
                                           from ../src/./serialport.h:6,
                                           from ../src/serialport.cpp:1:
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)
                             V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                                                               ^~~
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3639:37: note:   candidate expects 3 arguments, 2 provided
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)
                             V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                                                               ^~~
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/v8.h:3642:37: note:   candidate expects 3 arguments, 2 provided
                          ../src/serialport.cpp:383:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                             data->callback.Call(2, argv);
                                                        ^
                          In file included from ../src/./serialport.h:6:0,
                                           from ../src/serialport.cpp:1:
                          ../../nan/nan.h:1742:3: note: declared here
                             Call(int argc, v8::Local<v8::Value> argv[]) const {
                             ^~~~
                          ../src/serialport.cpp: In function âvoid EIO_AfterDrain(uv_work_t*)â:
                          ../src/serialport.cpp:424:30: warning: âv8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) constâ is deprecated [-Wdeprecated-declarations]
                             data->callback.Call(1, argv);
                                                        ^
                          In file included from ../src/./serialport.h:6:0,
                                           from ../src/serialport.cpp:1:
                          ../../nan/nan.h:1742:3: note: declared here
                             Call(int argc, v8::Local<v8::Value> argv[]) const {
                             ^~~~
                          ../src/serialport.cpp: At global scope:
                          ../src/serialport.cpp:460:17: error: variable or field âinitâ declared void
                             void init(v8::Handle<v8::Object> target) {
                                           ^~~~~~
                          ../src/serialport.cpp:460:17: error: âHandleâ is not a member of âv8â
                          ../src/serialport.cpp:460:34: error: expected primary-expression before â>â token
                             void init(v8::Handle<v8::Object> target) {
                                                            ^
                          ../src/serialport.cpp:460:36: error: âtargetâ was not declared in this scope
                             void init(v8::Handle<v8::Object> target) {
                                                              ^~~~~~
                          ../src/serialport.cpp:460:36: note: suggested alternative: âtzsetâ
                             void init(v8::Handle<v8::Object> target) {
                                                              ^~~~~~
                                                              tzset
                          In file included from ../../nan/nan.h:56:0,
                                           from ../src/./serialport.h:6,
                                           from ../src/serialport.cpp:1:
                          ../src/serialport.cpp:485:25: error: âinitâ was not declared in this scope
                           NODE_MODULE(serialport, init);
                                                   ^
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                                 (node::addon_register_func) (regfunc),                          \
                                                              ^~~~~~~
                          ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                           NODE_MODULE(serialport, init);
                           ^~~~~~~~~~~
                          ../src/serialport.cpp:485:25: note: suggested alternative: âintâ
                           NODE_MODULE(serialport, init);
                                                   ^
                          /home/iobroker/.cache/node-gyp/14.0.0/include/node/node.h:731:36: note: in definition of macro âNODE_MODULE_Xâ
                                 (node::addon_register_func) (regfunc),                          \
                                                              ^~~~~~~
                          ../src/serialport.cpp:485:1: note: in expansion of macro âNODE_MODULEâ
                           NODE_MODULE(serialport, init);
                           ^~~~~~~~~~~
                          serialport.target.mk:114: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
                          make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
                          make: Verzeichnis â/opt/iobroker/node_modules/serialport/buildâ wird verlassen
                          gyp ERR! build error
                          gyp ERR! stack Error: `make` failed with exit code: 2
                          gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                          gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                          gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                          gyp ERR! System Linux 4.15.0-96-generic
                          gyp ERR! command "/usr/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                          gyp ERR! cwd /opt/iobroker/node_modules/serialport
                          gyp ERR! node -v v14.0.0
                          gyp ERR! node-gyp -v v5.1.0
                          gyp ERR! not ok
                          npm ERR! code ELIFECYCLE
                          npm ERR! errno 1
                          npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
                          npm ERR! Exit status 1
                          npm ERR!
                          npm ERR! Failed at the serialport@6.2.2 install script.
                          npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                          
                          npm ERR! A complete log of this run can be found in:
                          npm ERR!     /home/iobroker/.npm/_logs/2020-04-27T21_15_55_218Z-debug.log
                          
                          
                          K Offline
                          K Offline
                          Kueppert
                          wrote on last edited by
                          #498

                          @e-s könnte zB der Zigbee-Adapter sein. Ich hab den auch drauf und auch WARN Meldungen gehabt beim Update von Node. Allerdings keine ERR-Meldungen.

                          UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+

                          1 Reply Last reply
                          0
                          • apollon77A apollon77

                            @e-s Da scheint irgendeiner Deiner Adapter noch serialpot 6 zu nutzen was mit Node 12 schon nicht mehr geescheit tut. Also hier wäre der Tipp mal die Adapter zu prüfen die Seriell arbeiten ob es Updates gibt

                            E Online
                            E Online
                            e-s
                            wrote on last edited by
                            #499

                            @apollon77
                            Einer von euch ist Schuld... 😊

                            serialport nutzt keiner meiner Adapter, aber ich habe herausgefunden, das discovery das braucht.
                            Da ich aber den Adapter gelöscht habe, wurden die Abhängigkeiten nicht mehr angepasst bzw überprüft.
                            Also hätte beim löschen des Adapters auch die zusätzlichen deps gelöscht werden müssen, das wiederum ist auch blöd wenn mehrere Adapter die Abhängigkeit brauchen.

                            Ein Teufelskreis, ich werde jetzt kurz discovery installieren und somit hoffen das serialport dann auf 8.0.7 angehoben wird, so wie es im git steht.

                            Oder habt Ihr eine bessere Idee?

                            ? 1 Reply Last reply
                            0
                            • E e-s

                              @apollon77
                              Einer von euch ist Schuld... 😊

                              serialport nutzt keiner meiner Adapter, aber ich habe herausgefunden, das discovery das braucht.
                              Da ich aber den Adapter gelöscht habe, wurden die Abhängigkeiten nicht mehr angepasst bzw überprüft.
                              Also hätte beim löschen des Adapters auch die zusätzlichen deps gelöscht werden müssen, das wiederum ist auch blöd wenn mehrere Adapter die Abhängigkeit brauchen.

                              Ein Teufelskreis, ich werde jetzt kurz discovery installieren und somit hoffen das serialport dann auf 8.0.7 angehoben wird, so wie es im git steht.

                              Oder habt Ihr eine bessere Idee?

                              ? Offline
                              ? Offline
                              A Former User
                              wrote on last edited by
                              #500

                              @e-s @apollon77

                              genau das Problem hab ich auch...
                              Der Discovery wird ja nur nach dem Einrichten gebraucht, daher gelöscht.. 2 Jahre her.. 🤦

                              E 1 Reply Last reply
                              0
                              • MiGollerM Offline
                                MiGollerM Offline
                                MiGoller
                                Developer
                                wrote on last edited by
                                #501

                                Hallo zusammen.

                                Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                $ sudo iobroker upgrade self
                                Update js-controller from @2.2.9 to @3.0.19
                                NPM version: 6.14.4
                                npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                    at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                    at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                

                                Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                Viele Grüße, MiGoller

                                ioBroker auf Intel Atom x5-Z8350 mit KNX, Gardena, Roomba, MQTT, Sonoff, Life360

                                MiGollerM B 2 Replies Last reply
                                0
                                • ? A Former User

                                  @e-s @apollon77

                                  genau das Problem hab ich auch...
                                  Der Discovery wird ja nur nach dem Einrichten gebraucht, daher gelöscht.. 2 Jahre her.. 🤦

                                  E Online
                                  E Online
                                  e-s
                                  wrote on last edited by e-s
                                  #502

                                  @ilovegym @apollon77

                                  Mach das bloß nicht manuell...
                                  discovery installíeren hat nichts gebracht, also habe ich mit

                                  npm i serialport@8.0.7

                                  aktualisiert.
                                  Dann kam aber der nächste Fehler, bluetooth -hci-socket wollte nicht, also auch den aktualiert obwohl ich den nicht benötige.

                                  npm i @abandonware/bluetooth-hci-socket@0.5.3-5

                                  jetzt kam ein Fehler von @serialport/bindings

                                  npm i @serialport/bindings@@8.0.7

                                  anschließend gab es keine Fehler mehr bei npm rebuild

                                  ? 1 Reply Last reply
                                  0
                                  • MiGollerM MiGoller

                                    Hallo zusammen.

                                    Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                    Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                    $ sudo iobroker upgrade self
                                    Update js-controller from @2.2.9 to @3.0.19
                                    NPM version: 6.14.4
                                    npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                    (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                        at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                        at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                    (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                    (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                    

                                    Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                    Viele Grüße, MiGoller

                                    MiGollerM Offline
                                    MiGollerM Offline
                                    MiGoller
                                    Developer
                                    wrote on last edited by
                                    #503

                                    @MiGoller sagte in js-controller 3.0 jetzt im Latest!:

                                    Hallo zusammen.

                                    Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                    Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                    $ sudo iobroker upgrade self
                                    Update js-controller from @2.2.9 to @3.0.19
                                    NPM version: 6.14.4
                                    npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                    (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                        at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                        at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                    (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                    (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                    

                                    Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                    Viele Grüße, MiGoller

                                    Hallo zusammen, nachdem auch die Version 3.0.18 in Verbindung mit Redis kein lauffähiges System mehr hervorgebracht hat, habe ich einen "Rücksturz" auf 2.2.9 durchgeführt. Letzt läuft es erst einmal wieder.

                                    Könnte da ein Zusammenhang mit meiner Redis-Konfiguration bestehen, die unter Version 2 des Controllers problemlos läuft?

                                    Viele Grüße, MiGoller

                                    ioBroker auf Intel Atom x5-Z8350 mit KNX, Gardena, Roomba, MQTT, Sonoff, Life360

                                    1 Reply Last reply
                                    0
                                    • MiGollerM MiGoller

                                      Hallo zusammen.

                                      Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                      Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                      $ sudo iobroker upgrade self
                                      Update js-controller from @2.2.9 to @3.0.19
                                      NPM version: 6.14.4
                                      npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                      (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                          at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                          at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                      (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                      (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                      

                                      Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                      Viele Grüße, MiGoller

                                      B Offline
                                      B Offline
                                      blackeagle998
                                      wrote on last edited by
                                      #504

                                      @MiGoller sagte in js-controller 3.0 jetzt im Latest!:

                                      Hallo zusammen.

                                      Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                      Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                      $ sudo iobroker upgrade self
                                      Update js-controller from @2.2.9 to @3.0.19
                                      NPM version: 6.14.4
                                      npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                      (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                          at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                          at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                      (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                      (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                      

                                      Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                      Viele Grüße, MiGoller

                                      Hallo, ich habe gerade exakt den gleichen Fehler, ebenfalls von Version 2.2.9 zu 3.0.19.

                                      khgK 1 Reply Last reply
                                      0
                                      • apollon77A Offline
                                        apollon77A Offline
                                        apollon77
                                        wrote on last edited by
                                        #505

                                        Der controller 3.0.20 ist auf Github - der fixt das ... sorry ...

                                        Sollte bald im Latest Repo sein, alternativ IM IOBROKER-VERZEICHNIS(!!) ein "npm install iobroker.js-controller@3.0.20" ausführen

                                        Changelog:
                                        3.0.20 (2020-04-28) Release Elena

                                        • (Apollon77) make sure disabling instances while installation is running do not crash the controller (Sentry IOBROKER-JS-CONTROLLER-Z)
                                        • (From Forum) prevent error on backup restore
                                        • (Apollon77) Make sure error handing do not throw exception
                                        • (Apollon77) Catch all errors when trying to store the File DB (Sentry IOBROKER-JS-CONTROLLER-14/15)
                                        • (Apollon77) Make sure also edge cases on start adapter are handled correctly (Sentry IOBROKER-JS-CONTROLLER-12)
                                        • (Apollon77) Use 3.3.4 of objects library to prevent an error from 3.3.3

                                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                        ? sigi234S 2 Replies Last reply
                                        4
                                        • B blackeagle998

                                          @MiGoller sagte in js-controller 3.0 jetzt im Latest!:

                                          Hallo zusammen.

                                          Vielen Dank für die gute Arbeit! Das möchte ich erst einmal loswerden.

                                          Beim Upgrade des js-controllers von 2.2.9 auf 3.0.19 auf meiner Prod-Umgebung habe ich allerdings folgende Meldung bei der Installation gesehen.

                                          $ sudo iobroker upgrade self
                                          Update js-controller from @2.2.9 to @3.0.19
                                          NPM version: 6.14.4
                                          npm install iobroker.js-controller@3.0.19 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                          (node:14431) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                              at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                              at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                          (node:14431) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                          (node:14431) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                          

                                          Müsste da nicht wahrscheinlich callback statt allback stehen? Habe mir den Code noch nicht angeschaut.

                                          Viele Grüße, MiGoller

                                          Hallo, ich habe gerade exakt den gleichen Fehler, ebenfalls von Version 2.2.9 zu 3.0.19.

                                          khgK Offline
                                          khgK Offline
                                          khg
                                          wrote on last edited by
                                          #506

                                          update js-controller 3.0.18 --> 30.19 nicht möglich.
                                          Node.js v12.16.2
                                          NPM 6.14.4

                                          Detail:
                                          int err = epoll->Modify(info[0]->Int32Value(), info[1]->Int32Value());
                                          ^
                                          In file included from ../src/epoll.cc:11:
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2709:40: note: candidate: ‘v8::Maybe<int> v8::Value::Int32Value(v8::Localv8::Context) const’
                                          V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                          ^~~~~~~~~~
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2709:40: note: candidate expects 1 argument, 0 provided
                                          ../src/epoll.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE Epoll::Remove(Nan::NAN_METHOD_ARGS_TYPE)’:
                                          ../src/epoll.cc:247:47: error: no matching function for call to ‘v8::Value::Int32Value()’
                                          int err = epoll->Remove(info[0]->Int32Value());
                                          ^
                                          In file included from ../src/epoll.cc:11:
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2709:40: note: candidate: ‘v8::Maybe<int> v8::Value::Int32Value(v8::Localv8::Context) const’
                                          V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
                                          ^~~~~~~~~~
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2709:40: note: candidate expects 1 argument, 0 provided
                                          In file included from ../src/epoll.cc:12:
                                          ../src/epoll.cc: At global scope:
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:608:43: warning: cast between incompatible function types from ‘void ()(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void ()(v8::Localv8::Object)’} to ‘node::addon_register_func’ {aka ‘void ()(v8::Localv8::Object, v8::Localv8::Value, void)’} [-Wcast-function-type]
                                          (node::addon_register_func) (regfunc),
                                          ^
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:642:3: note: in expansion of macro ‘NODE_MODULE_X’
                                          NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)
                                          ^~~~~~~~~~~~~
                                          ../src/epoll.cc:381:1: note: in expansion of macro ‘NODE_MODULE’
                                          NODE_MODULE(epoll, Epoll::Init)
                                          ^~~~~~~~~~~
                                          In file included from ../src/epoll.cc:11:
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/node_object_wrap.h:85:78: required from here
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:10226:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void (
                                          )(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                          reinterpret_cast<Callback>(callback), type);
                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P
                                          , typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
                                          ../../nan/nan_object_wrap.h:66:61: required from here
                                          /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:10226:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void (
                                          )(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                                          make: *** [epoll.target.mk:111: Release/obj.target/epoll/src/epoll.o] Fehler 1
                                          gyp ERR! build error
                                          gyp ERR! stack Error: make failed with exit code: 2
                                          gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                                          gyp ERR! stack at ChildProcess.emit (events.js:310:20)
                                          gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                                          gyp ERR! System Linux 5.4.28-rockchip
                                          gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                          gyp ERR! cwd /opt/iobroker/node_modules/rpi-gpio/node_modules/epoll
                                          gyp ERR! node -v v12.16.2
                                          gyp ERR! node-gyp -v v5.1.0
                                          gyp ERR! not ok
                                          (node:19963) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                          at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                          at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                          (node:19963) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                          (node:19963) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code

                                          bleibt hier händen und Abbruch mit Ctrl-C.

                                          iobroker start
                                          iobroker status

                                          (node:26663) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                          at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                          at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                          (node:26663) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                          (node:26663) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

                                          sigi234S 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

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

                                          165

                                          Online

                                          32.4k

                                          Users

                                          81.3k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe