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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 3.2 jetzt im Latest!

NEWS

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

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

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

js-controller 3.2 jetzt im Latest!

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
575 Beiträge 70 Kommentatoren 145.7k Aufrufe 57 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • apollon77A apollon77

    @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

    Master67M Offline
    Master67M Offline
    Master67
    schrieb am zuletzt editiert von
    #56

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

    @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

    Mache ich wenn der ioBroker wieder läuft... spiele doch grade eine Sicherung ein ;-)

    Gruß Master67

    1 Antwort Letzte Antwort
    0
    • apollon77A apollon77

      @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

      Master67M Offline
      Master67M Offline
      Master67
      schrieb am zuletzt editiert von
      #57

      @apollon77 so hier mal die Fehlermeldung die ich erhalte :-)

      Update js-controller from @3.1.6 to @3.2.7
      NPM version: 6.14.10
      npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
      In file included from ../authenticate_pam.cc:23:
      ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
      ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
       2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
            |                                                              ^
      ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
      ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
        107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
            |                                                                                       ^
      In file included from ../authenticate_pam.cc:23:
      ../../nan/nan.h:1026:46: note: declared here
       1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
            |                                              ^~~~~~~~~~~~
      ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
        107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
            |                                                                                       ^
      In file included from ../authenticate_pam.cc:23:
      ../../nan/nan.h:1026:46: note: declared here
       1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
            |                                              ^~~~~~~~~~~~
      ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
      ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
        147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
            |                                                                                   ^
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                       from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                       from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
       3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
            |                                                   ^~~
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
        328 |   declarator __attribute__((deprecated(message)))
            |   ^~~~~~~~~~
      ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
        150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
            |                           ~~~^~~~~~~~~~~
            |                              |
            |                              char [128]
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
       2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
            |                 ~~~~~~~~~^~~~~~~
      ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
        152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
            |                                                                     ^
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                       from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                       from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
       3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
            |                                                   ^~~
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
        328 |   declarator __attribute__((deprecated(message)))
            |   ^~~~~~~~~~
      ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
        155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
            |                          ~~~^~~~~~~~~~
            |                             |
            |                             char [128]
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
       2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
            |                 ~~~~~~~~~^~~~~~~
      ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
        160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
            |                      ~~~^~~~~~~~
            |                         |
            |                         char [128]
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
       2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
            |                 ~~~~~~~~~^~~~~~~
      ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
        161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
            |                      ~~~^~~~~~~~
            |                         |
            |                         char [128]
      In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                       from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
       2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
            |                 ~~~~~~~~~^~~~~~~
      ../authenticate_pam.cc: At global scope:
      ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
        170 | void init(Handle<Object> exports) {
            |           ^~~~~~
      ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
      ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
        170 | void init(Handle<Object> exports) {
            |                        ^
      ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
        170 | void init(Handle<Object> exports) {
            |                          ^~~~~~~
      In file included from ../../nan/nan.h:56,
                       from ../authenticate_pam.cc:23:
      ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
        175 | NODE_MODULE(authenticate_pam, init);
            |                               ^~~~
      /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
        737 |       (node::addon_register_func) (regfunc),                          \
            |                                    ^~~~~~~
      ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
        175 | NODE_MODULE(authenticate_pam, init);
            | ^~~~~~~~~~~
      make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 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:314:20)
      gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
      gyp ERR! System Linux 5.4.78-2-pve
      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/authenticate-pam
      gyp ERR! node -v v12.20.1
      gyp ERR! node-gyp -v v5.1.0
      gyp ERR! not ok 
      Starting node restart.js
      

      Gruß Master67

      apollon77A 1 Antwort Letzte Antwort
      0
      • Master67M Master67

        @apollon77 so hier mal die Fehlermeldung die ich erhalte :-)

        Update js-controller from @3.1.6 to @3.2.7
        NPM version: 6.14.10
        npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
        ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
         2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
              |                                                              ^
        ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
        ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
          107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
              |                                                                                       ^
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h:1026:46: note: declared here
         1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
              |                                              ^~~~~~~~~~~~
        ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
          107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
              |                                                                                       ^
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h:1026:46: note: declared here
         1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
              |                                              ^~~~~~~~~~~~
        ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
        ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
          147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
              |                                                                                   ^
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
         3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
              |                                                   ^~~
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
          328 |   declarator __attribute__((deprecated(message)))
              |   ^~~~~~~~~~
        ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
          150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
              |                           ~~~^~~~~~~~~~~
              |                              |
              |                              char [128]
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
              |                 ~~~~~~~~~^~~~~~~
        ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
          152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
              |                                                                     ^
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
         3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
              |                                                   ^~~
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
          328 |   declarator __attribute__((deprecated(message)))
              |   ^~~~~~~~~~
        ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
          155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
              |                          ~~~^~~~~~~~~~
              |                             |
              |                             char [128]
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
              |                 ~~~~~~~~~^~~~~~~
        ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
          160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
              |                      ~~~^~~~~~~~
              |                         |
              |                         char [128]
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
              |                 ~~~~~~~~~^~~~~~~
        ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
          161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
              |                      ~~~^~~~~~~~
              |                         |
              |                         char [128]
        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                         from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
              |                 ~~~~~~~~~^~~~~~~
        ../authenticate_pam.cc: At global scope:
        ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
          170 | void init(Handle<Object> exports) {
              |           ^~~~~~
        ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
        ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
          170 | void init(Handle<Object> exports) {
              |                        ^
        ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
          170 | void init(Handle<Object> exports) {
              |                          ^~~~~~~
        In file included from ../../nan/nan.h:56,
                         from ../authenticate_pam.cc:23:
        ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
          175 | NODE_MODULE(authenticate_pam, init);
              |                               ^~~~
        /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
          737 |       (node::addon_register_func) (regfunc),                          \
              |                                    ^~~~~~~
        ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
          175 | NODE_MODULE(authenticate_pam, init);
              | ^~~~~~~~~~~
        make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 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:314:20)
        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
        gyp ERR! System Linux 5.4.78-2-pve
        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/authenticate-pam
        gyp ERR! node -v v12.20.1
        gyp ERR! node-gyp -v v5.1.0
        gyp ERR! not ok 
        Starting node restart.js
        
        apollon77A Offline
        apollon77A Offline
        apollon77
        schrieb am zuletzt editiert von
        #58

        @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

        Das sind faktisch nur warnungen von einem optionalen Paket

        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
        Master67M 1 Antwort Letzte Antwort
        0
        • apollon77A apollon77

          @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

          Das sind faktisch nur warnungen von einem optionalen Paket

          Master67M Offline
          Master67M Offline
          Master67
          schrieb am zuletzt editiert von
          #59

          @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf ;-)

          Gruß Master67

          Thomas BraunT apollon77A 2 Antworten Letzte Antwort
          0
          • Master67M Master67

            @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf ;-)

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

            @master67
            Ist libpam0g-dev auf deinem System installiert?

            [Edit:] Das ist wieder so'n Container-Gesumsel, oder?

            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

            Master67M 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @master67
              Ist libpam0g-dev auf deinem System installiert?

              [Edit:] Das ist wieder so'n Container-Gesumsel, oder?

              Master67M Offline
              Master67M Offline
              Master67
              schrieb am zuletzt editiert von Master67
              #61

              @thomas-braun .... keine Ahnung!
              Da läuft nur der ioBroker unter Ubuntu 20.04.1

              Edit: japp Proxmox :-)

              Gruß Master67

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • Master67M Master67

                @thomas-braun .... keine Ahnung!
                Da läuft nur der ioBroker unter Ubuntu 20.04.1

                Edit: japp Proxmox :-)

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

                @master67

                apt policy libpam0g-dev
                

                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

                Master67M 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @master67

                  apt policy libpam0g-dev
                  
                  Master67M Offline
                  Master67M Offline
                  Master67
                  schrieb am zuletzt editiert von
                  #63

                  @thomas-braun sagte in js-controller 3.2 jetzt im Latest!:

                  apt policy libpam0g-dev

                  Ja läuft....

                  libpam0g-dev:
                    Installed: 1.3.1-5ubuntu4.1
                    Candidate: 1.3.1-5ubuntu4.1
                    Version table:
                   *** 1.3.1-5ubuntu4.1 500
                          500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
                          100 /var/lib/dpkg/status
                       1.3.1-5ubuntu4 500
                          500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
                  

                  Gruß Master67

                  1 Antwort Letzte Antwort
                  0
                  • H Offline
                    H Offline
                    homecineplexx
                    schrieb am zuletzt editiert von
                    #64

                    also mit dem js-controller 3.2.7 hab ich leuter Fehlermeldungen:

                    2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                    2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                    2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                    2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                    2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                    

                    hab auch schon geschaut, aber wonach bitte zählt der denn die Line 297? nicht so, wie sie im JavaScript ist denke ich.

                    apollon77A 1 Antwort Letzte Antwort
                    0
                    • omega235O Offline
                      omega235O Offline
                      omega235
                      Developer
                      schrieb am zuletzt editiert von omega235
                      #65

                      Die Installation von Branches über Github funktioniert nicht mehr korrekt.

                      js-controller: 3.2.7
                      os: Linux / Docker / buanet 5.1
                      architektur: x64
                      nodejs: v12.20.0
                      NPM: 6.14.8

                      über den bisher funktionierenden Link (https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0) kommt es zu einer Fehlermeldung (wird aber installiert, man muss aber manuell upload und neu starten):

                      $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                      install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                      NPM version: 6.14.8
                      npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                      + iobroker.virtualpowermeter@1.3.0
                      updated 1 package in 43.181s
                      23 packages are looking for funding  run `npm fund` for details
                      ERROR: host.IoBrokerTestSystem1 Cannot install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0: 0
                      ERROR: process exited with code 25
                      

                      Wenn man den Link von github nimmt (https://github.com/Omega236/ioBroker.virtualpowermeter/tree/1.3.0) dann installiert er die Version aus dem Master branch.

                      edit:
                      im stable (3.1.6) sieht der log gut aus:

                      $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                      install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                      NPM version: 6.14.8
                      npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                      + iobroker.virtualpowermeter@1.3.0updated 1 package in 16.663s
                      25 packages are looking for funding  run `npm fund` for details
                      upload [8] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/words.js words.js application/javascript
                      upload [7] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/virtualpowermeter.png virtualpowermeter.png image/png
                      upload [6] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/tsconfig.json tsconfig.json application/json
                      upload [5] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/style.css style.css text/css
                      upload [4] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/index_m.html index_m.html text/html
                      upload [3] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/custom_m.html custom_m.html text/html
                      upload [2] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/admin.d.ts admin.d.ts video/mp2t
                      upload [1] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/InstanceSettings.PNG InstanceSettings.PNG image/png
                      upload [0] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/DatapointSample.PNG DatapointSample.PNG image/png
                      process exited with code 0
                      
                      apollon77A 2 Antworten Letzte Antwort
                      0
                      • apollon77A apollon77

                        @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

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

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

                        @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

                        @apollon77 Bisher verhält sich mein DWD Adapter von Github unauffällig. :-)

                        1 Antwort Letzte Antwort
                        1
                        • Master67M Master67

                          @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf ;-)

                          apollon77A Offline
                          apollon77A Offline
                          apollon77
                          schrieb am zuletzt editiert von
                          #67

                          @master67 Dann muss es aber Fehler im Log geben wenn du startest ... schau mal ins Logfile

                          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
                          Master67M 1 Antwort Letzte Antwort
                          0
                          • H homecineplexx

                            also mit dem js-controller 3.2.7 hab ich leuter Fehlermeldungen:

                            2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                            2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                            2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                            2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                            2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                            

                            hab auch schon geschaut, aber wonach bitte zählt der denn die Line 297? nicht so, wie sie im JavaScript ist denke ich.

                            apollon77A Offline
                            apollon77A Offline
                            apollon77
                            schrieb am zuletzt editiert von
                            #68

                            @homecineplexx Falls du globale Scripts hast werden die ja davorgehängt. du versuchst auf irgendetwas zuzugreifen was falsch ist. von solchen Javascripts hab ich auch einiges im Sentry wo versucht wird ein state zuzugreifen mit nem "." am ende - das ist jetzt verboten. Muss im javascript adapter wohl noch abgefangen werden

                            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
                            H 2 Antworten Letzte Antwort
                            0
                            • omega235O omega235

                              Die Installation von Branches über Github funktioniert nicht mehr korrekt.

                              js-controller: 3.2.7
                              os: Linux / Docker / buanet 5.1
                              architektur: x64
                              nodejs: v12.20.0
                              NPM: 6.14.8

                              über den bisher funktionierenden Link (https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0) kommt es zu einer Fehlermeldung (wird aber installiert, man muss aber manuell upload und neu starten):

                              $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                              install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                              NPM version: 6.14.8
                              npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                              + iobroker.virtualpowermeter@1.3.0
                              updated 1 package in 43.181s
                              23 packages are looking for funding  run `npm fund` for details
                              ERROR: host.IoBrokerTestSystem1 Cannot install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0: 0
                              ERROR: process exited with code 25
                              

                              Wenn man den Link von github nimmt (https://github.com/Omega236/ioBroker.virtualpowermeter/tree/1.3.0) dann installiert er die Version aus dem Master branch.

                              edit:
                              im stable (3.1.6) sieht der log gut aus:

                              $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                              install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                              NPM version: 6.14.8
                              npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                              + iobroker.virtualpowermeter@1.3.0updated 1 package in 16.663s
                              25 packages are looking for funding  run `npm fund` for details
                              upload [8] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/words.js words.js application/javascript
                              upload [7] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/virtualpowermeter.png virtualpowermeter.png image/png
                              upload [6] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/tsconfig.json tsconfig.json application/json
                              upload [5] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/style.css style.css text/css
                              upload [4] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/index_m.html index_m.html text/html
                              upload [3] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/custom_m.html custom_m.html text/html
                              upload [2] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/admin.d.ts admin.d.ts video/mp2t
                              upload [1] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/InstanceSettings.PNG InstanceSettings.PNG image/png
                              upload [0] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/DatapointSample.PNG DatapointSample.PNG image/png
                              process exited with code 0
                              
                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von
                              #69

                              @omega235 Ok, checke

                              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
                              ChaotC 1 Antwort Letzte Antwort
                              0
                              • omega235O omega235

                                Die Installation von Branches über Github funktioniert nicht mehr korrekt.

                                js-controller: 3.2.7
                                os: Linux / Docker / buanet 5.1
                                architektur: x64
                                nodejs: v12.20.0
                                NPM: 6.14.8

                                über den bisher funktionierenden Link (https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0) kommt es zu einer Fehlermeldung (wird aber installiert, man muss aber manuell upload und neu starten):

                                $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                                install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                                NPM version: 6.14.8
                                npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                                + iobroker.virtualpowermeter@1.3.0
                                updated 1 package in 43.181s
                                23 packages are looking for funding  run `npm fund` for details
                                ERROR: host.IoBrokerTestSystem1 Cannot install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0: 0
                                ERROR: process exited with code 25
                                

                                Wenn man den Link von github nimmt (https://github.com/Omega236/ioBroker.virtualpowermeter/tree/1.3.0) dann installiert er die Version aus dem Master branch.

                                edit:
                                im stable (3.1.6) sieht der log gut aus:

                                $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                                install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                                NPM version: 6.14.8
                                npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                                + iobroker.virtualpowermeter@1.3.0updated 1 package in 16.663s
                                25 packages are looking for funding  run `npm fund` for details
                                upload [8] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/words.js words.js application/javascript
                                upload [7] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/virtualpowermeter.png virtualpowermeter.png image/png
                                upload [6] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/tsconfig.json tsconfig.json application/json
                                upload [5] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/style.css style.css text/css
                                upload [4] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/index_m.html index_m.html text/html
                                upload [3] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/custom_m.html custom_m.html text/html
                                upload [2] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/admin.d.ts admin.d.ts video/mp2t
                                upload [1] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/InstanceSettings.PNG InstanceSettings.PNG image/png
                                upload [0] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/DatapointSample.PNG DatapointSample.PNG image/png
                                process exited with code 0
                                
                                apollon77A Offline
                                apollon77A Offline
                                apollon77
                                schrieb am zuletzt editiert von
                                #70

                                @omega235 sagte in js-controller 3.2 jetzt im Latest!:

                                https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0

                                BTW: in js.controller 3.2 geht das viel einfacher :-))

                                "iobroker url Omega236/ioBroker.virtualpowermeter#1.3.0"

                                besser als das alte?

                                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
                                omega235O UncleSamU 2 Antworten Letzte Antwort
                                0
                                • apollon77A apollon77

                                  @omega235 Ok, checke

                                  ChaotC Offline
                                  ChaotC Offline
                                  Chaot
                                  schrieb am zuletzt editiert von
                                  #71

                                  @apollon77 Derzeit alles normal ohne Fehlermeldungen.
                                  Lediglich ist mir aufgefallen das scheinbar die Prozessorlast im CT leicht angestiegen ist. Ok, ein Anstieg von 9 auf 11 % ist jetzt nichts was Alarm auslösen sollte. Aber nur als Info an dich.

                                  ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.

                                  1 Antwort Letzte Antwort
                                  2
                                  • apollon77A apollon77

                                    @omega235 sagte in js-controller 3.2 jetzt im Latest!:

                                    https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0

                                    BTW: in js.controller 3.2 geht das viel einfacher :-))

                                    "iobroker url Omega236/ioBroker.virtualpowermeter#1.3.0"

                                    besser als das alte?

                                    omega235O Offline
                                    omega235O Offline
                                    omega235
                                    Developer
                                    schrieb am zuletzt editiert von
                                    #72

                                    @apollon77
                                    Super, https://github.com/Omega236/ioBroker.virtualpowermeter#1.3.0 funktioniert auch (und ohne Fehler).

                                    Merk ich mir.

                                    1 Antwort Letzte Antwort
                                    0
                                    • apollon77A apollon77

                                      @homecineplexx Falls du globale Scripts hast werden die ja davorgehängt. du versuchst auf irgendetwas zuzugreifen was falsch ist. von solchen Javascripts hab ich auch einiges im Sentry wo versucht wird ein state zuzugreifen mit nem "." am ende - das ist jetzt verboten. Muss im javascript adapter wohl noch abgefangen werden

                                      H Offline
                                      H Offline
                                      homecineplexx
                                      schrieb am zuletzt editiert von
                                      #73

                                      @apollon77 also eigentlich ist das kein globales Script. Ich kann's dir gern Mal anhängen

                                      apollon77A 1 Antwort Letzte Antwort
                                      0
                                      • H homecineplexx

                                        @apollon77 also eigentlich ist das kein globales Script. Ich kann's dir gern Mal anhängen

                                        apollon77A Offline
                                        apollon77A Offline
                                        apollon77
                                        schrieb am zuletzt editiert von
                                        #74

                                        @homecineplexx Nein ich sage i´nicht das das skript ein globales ist aber wen du ein globales skript definiert hast dann wird das vor alle anderen Skripte davor gehängt!

                                        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
                                        H 1 Antwort Letzte Antwort
                                        0
                                        • apollon77A apollon77

                                          @omega235 sagte in js-controller 3.2 jetzt im Latest!:

                                          https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0

                                          BTW: in js.controller 3.2 geht das viel einfacher :-))

                                          "iobroker url Omega236/ioBroker.virtualpowermeter#1.3.0"

                                          besser als das alte?

                                          UncleSamU Offline
                                          UncleSamU Offline
                                          UncleSam
                                          Developer
                                          schrieb am zuletzt editiert von
                                          #75

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

                                          BTW: in js.controller 3.2 geht das viel einfacher :-))
                                          "iobroker url Omega236/ioBroker.virtualpowermeter#1.3.0"
                                          besser als das alte?

                                          Das sollte aber meiner Meinung nach ganz klar in die Release Notes, dass das alte nicht mehr geht. Ist zwar nicht schlimm, aber es ist ein kleiner "breaking change".

                                          Bitte bei Problemen mit meinen Adaptern, Issue auf GitHub erfassen: Loxone | I2C | Luxtronik2
                                          ♡-lichen Dank an meine Sponsoren

                                          apollon77A 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          781

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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