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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter mihome-vacuum v2.0.x

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    11
    1
    535

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.7k

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

Test Adapter mihome-vacuum v2.0.x

Geplant Angeheftet Gesperrt Verschoben Tester
xiaomiroborockmihome-vacuummap
1.5k Beiträge 144 Kommentatoren 514.6k Aufrufe 118 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.
  • B Offline
    B Offline
    bjoegibbard
    schrieb am zuletzt editiert von bjoegibbard
    #1348

    @haselchen
    Mir ist gerade noch ein Fehler aufgefallen.
    Egal welchen adapter ich update. Ich bekomme immer eine sehr ähnliche Fehlermeldung:

    Update web from @3.0.12 to @3.2.3
    host.raspberrypi4-iob Adapter "system.adapter.web.0" is stopped.
    NPM version: 6.14.6npm install iobroker.web@3.2.3 --loglevel error --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]     , 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]   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   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]   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   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]   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());                                                                                   ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);                                                                  ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’  username->WriteUtf8(m->username, sizeof(m->username) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’  password->WriteUtf8(m->password, sizeof(m->password) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc: At global scope:../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void void init(Handle<Object> exports) {           ^~~~~~../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
    ../authenticate_pam.cc:170:11: note: suggested alternative: ‘rand_r’ void init(Handle<Object> exports) {           ^~~~~~           rand_r../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token void init(Handle<Object> exports) {                        ^../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope 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 NODE_MODULE(authenticate_pam, init);                               ^~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’       (node::addon_register_func) (regfunc),                          \                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(authenticate_pam, init); ^~~~~~~~~~~
    ../authenticate_pam.cc:175:31: note: suggested alternative: ‘int’ NODE_MODULE(authenticate_pam, init);                               ^~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’       (node::addon_register_func) (regfunc),                          \                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(authenticate_pam, init); ^~~~~~~~~~~
    make: *** [authenticate_pam.target.mk:109: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
    gyp ERR! build error 
    gyp ERR! stack Error: `make` failed with exit code: 2gyp 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:315:20)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
    gyp ERR! System Linux 5.4.51-v7l+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-pamgyp ERR! node -v v12.18.3gyp ERR! node-gyp -v v5.1.0gyp ERR! not ok 
    
    

    Könnte es auch daran liegen?
    Hier habe ich als beispiel mal den web adapter geupdated.

    Die Anleitung habe ich jetzt auch noch ausprobiert, ohne Erfolg:
    https://gitmemory.com/issue/iobroker-community-adapters/ioBroker.mihome-vacuum/206/752936194

    Ich bin auch noch durch die App gegangen. Da scheint mir alles richtig :(

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • B bjoegibbard

      @haselchen
      Mir ist gerade noch ein Fehler aufgefallen.
      Egal welchen adapter ich update. Ich bekomme immer eine sehr ähnliche Fehlermeldung:

      Update web from @3.0.12 to @3.2.3
      host.raspberrypi4-iob Adapter "system.adapter.web.0" is stopped.
      NPM version: 6.14.6npm install iobroker.web@3.2.3 --loglevel error --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]     , 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]   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   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]   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   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]   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());                                                                                   ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);                                                                  ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’  username->WriteUtf8(m->username, sizeof(m->username) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’  password->WriteUtf8(m->password, sizeof(m->password) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc: At global scope:../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void void init(Handle<Object> exports) {           ^~~~~~../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
      ../authenticate_pam.cc:170:11: note: suggested alternative: ‘rand_r’ void init(Handle<Object> exports) {           ^~~~~~           rand_r../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token void init(Handle<Object> exports) {                        ^../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope 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 NODE_MODULE(authenticate_pam, init);                               ^~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’       (node::addon_register_func) (regfunc),                          \                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(authenticate_pam, init); ^~~~~~~~~~~
      ../authenticate_pam.cc:175:31: note: suggested alternative: ‘int’ NODE_MODULE(authenticate_pam, init);                               ^~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’       (node::addon_register_func) (regfunc),                          \                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(authenticate_pam, init); ^~~~~~~~~~~
      make: *** [authenticate_pam.target.mk:109: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
      gyp ERR! build error 
      gyp ERR! stack Error: `make` failed with exit code: 2gyp 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:315:20)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
      gyp ERR! System Linux 5.4.51-v7l+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-pamgyp ERR! node -v v12.18.3gyp ERR! node-gyp -v v5.1.0gyp ERR! not ok 
      
      

      Könnte es auch daran liegen?
      Hier habe ich als beispiel mal den web adapter geupdated.

      Die Anleitung habe ich jetzt auch noch ausprobiert, ohne Erfolg:
      https://gitmemory.com/issue/iobroker-community-adapters/ioBroker.mihome-vacuum/206/752936194

      Ich bin auch noch durch die App gegangen. Da scheint mir alles richtig :(

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

      @bjoegibbard sagte in Test Adapter mihome-vacuum v2.0.x:

      authenticate_pam

      Schau mal ob libpam0g-dev und/oder libreadline-dev installiert ist:

      apt policy libpam0g-dev libreadline-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

      B 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @bjoegibbard sagte in Test Adapter mihome-vacuum v2.0.x:

        authenticate_pam

        Schau mal ob libpam0g-dev und/oder libreadline-dev installiert ist:

        apt policy libpam0g-dev libreadline-dev
        
        B Offline
        B Offline
        bjoegibbard
        schrieb am zuletzt editiert von bjoegibbard
        #1350

        @thomas-braun

        libpam0g-dev:
          Installiert:           1.3.1-5+rpt2
          Installationskandidat: 1.3.1-5+rpt2
          Versionstabelle:
         *** 1.3.1-5+rpt2 500
                500 http://archive.raspberrypi.org/debian buster/main armhf Packages
                100 /var/lib/dpkg/status
             1.3.1-5 500
                500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        libreadline-dev:
          Installiert:           (keine)
          Installationskandidat: 7.0-5
          Versionstabelle:
             7.0-5 500
                500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        
        

        libreadline-dev scheint zu fehlen?

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • B bjoegibbard

          @thomas-braun

          libpam0g-dev:
            Installiert:           1.3.1-5+rpt2
            Installationskandidat: 1.3.1-5+rpt2
            Versionstabelle:
           *** 1.3.1-5+rpt2 500
                  500 http://archive.raspberrypi.org/debian buster/main armhf Packages
                  100 /var/lib/dpkg/status
               1.3.1-5 500
                  500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
          libreadline-dev:
            Installiert:           (keine)
            Installationskandidat: 7.0-5
            Versionstabelle:
               7.0-5 500
                  500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
          
          

          libreadline-dev scheint zu fehlen?

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

          @bjoegibbard Nicht unbedingt.
          Kannst du aber mal nachinstallieren.
          Und ich würde node auf Stand bringen.

          sudo apt update
          sudo apt dist-upgrade
          sudo reboot
          

          (Wenn es schon sauber installiert war...)

          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

          B 1 Antwort Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @bjoegibbard Nicht unbedingt.
            Kannst du aber mal nachinstallieren.
            Und ich würde node auf Stand bringen.

            sudo apt update
            sudo apt dist-upgrade
            sudo reboot
            

            (Wenn es schon sauber installiert war...)

            B Offline
            B Offline
            bjoegibbard
            schrieb am zuletzt editiert von
            #1352

            @thomas-braun

            danke, habe alles ausgeführt. Aber leider keine Besserung.

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • B bjoegibbard

              @thomas-braun

              danke, habe alles ausgeführt. Aber leider keine Besserung.

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

              @bjoegibbard

              which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
              
              cd /opt/iobroker
              npm cache clean --force
              npm install authenticate-pam
              

              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

              B 1 Antwort Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @bjoegibbard

                which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                
                cd /opt/iobroker
                npm cache clean --force
                npm install authenticate-pam
                
                B Offline
                B Offline
                bjoegibbard
                schrieb am zuletzt editiert von bjoegibbard
                #1354

                @thomas-braun

                /usr/bin/nodejs
                v12.20.1
                /usr/bin/node
                v12.20.1
                /usr/bin/npm
                6.14.10
                nodejs:
                  Installiert:           12.20.1-1nodesource1
                  Installationskandidat: 12.20.1-1nodesource1
                  Versionstabelle:
                 *** 12.20.1-1nodesource1 500
                        500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
                        100 /var/lib/dpkg/status
                     10.23.1~dfsg-1~deb10u1 500
                        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                
                
                /opt/iobroker $ npm cache clean --force
                npm WARN using --force I sure hope you know what you are doing.
                
                npm install authenticate-pam
                
                > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
                > node-gyp rebuild
                
                make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
                  CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
                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]
                     , 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]
                 keCallback(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
                   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]
                 keCallback(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
                   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]
                 al<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
                   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’
                   declarator __attribute__((deprecated(message)))
                   ^~~~~~~~~~
                ../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                                                                     ^
                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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                       ^~~~~~~~~
                /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                ../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                   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
                   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’
                   declarator __attribute__((deprecated(message)))
                   ^~~~~~~~~~
                ../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                                                                  ^
                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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                       ^~~~~~~~~
                /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                ../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                                                          ^
                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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                       ^~~~~~~~~
                /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                ../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                                                          ^
                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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                       ^~~~~~~~~
                /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                ../authenticate_pam.cc: At global scope:
                ../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void
                 void init(Handle<Object> exports) {
                           ^~~~~~
                ../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
                ../authenticate_pam.cc:170:11: note: suggested alternative: ‘rand_r’
                 void init(Handle<Object> exports) {
                           ^~~~~~
                           rand_r
                ../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token
                 void init(Handle<Object> exports) {
                                        ^
                ../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope
                 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
                 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’
                       (node::addon_register_func) (regfunc),                          \
                                                    ^~~~~~~
                ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
                 NODE_MODULE(authenticate_pam, init);
                 ^~~~~~~~~~~
                ../authenticate_pam.cc:175:31: note: suggested alternative: ‘int’
                 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’
                       (node::addon_register_func) (regfunc),                          \
                                                    ^~~~~~~
                ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
                 NODE_MODULE(authenticate_pam, init);
                 ^~~~~~~~~~~
                make: *** [authenticate_pam.target.mk:109: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
                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.83-v7l+
                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
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman/node_modules/chokidar/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/zigbee-herdsman/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                
                npm ERR! code ELIFECYCLE
                npm ERR! errno 1
                npm ERR! authenticate-pam@1.0.2 install: `node-gyp rebuild`
                npm ERR! Exit status 1
                npm ERR!
                npm ERR! Failed at the authenticate-pam@1.0.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/2021-01-24T16_44_12_411Z-debug.log
                pi@raspberrypi4-iob:/opt/iobroker $
                
                

                da ist wieder dieser doofe gyp ERR! -.-

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • B bjoegibbard

                  @thomas-braun

                  /usr/bin/nodejs
                  v12.20.1
                  /usr/bin/node
                  v12.20.1
                  /usr/bin/npm
                  6.14.10
                  nodejs:
                    Installiert:           12.20.1-1nodesource1
                    Installationskandidat: 12.20.1-1nodesource1
                    Versionstabelle:
                   *** 12.20.1-1nodesource1 500
                          500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
                          100 /var/lib/dpkg/status
                       10.23.1~dfsg-1~deb10u1 500
                          500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                  
                  
                  /opt/iobroker $ npm cache clean --force
                  npm WARN using --force I sure hope you know what you are doing.
                  
                  npm install authenticate-pam
                  
                  > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
                  > node-gyp rebuild
                  
                  make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
                    CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
                  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]
                       , 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]
                   keCallback(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
                     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]
                   keCallback(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
                     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]
                   al<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
                     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’
                     declarator __attribute__((deprecated(message)))
                     ^~~~~~~~~~
                  ../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                      serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                                                                       ^
                  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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                     int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                         ^~~~~~~~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
                     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
                     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’
                     declarator __attribute__((deprecated(message)))
                     ^~~~~~~~~~
                  ../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                      remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                                                                    ^
                  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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                     int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                         ^~~~~~~~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                    username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                                                            ^
                  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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                     int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                         ^~~~~~~~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
                    password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                                                            ^
                  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:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
                     int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                         ^~~~~~~~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc: At global scope:
                  ../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void
                   void init(Handle<Object> exports) {
                             ^~~~~~
                  ../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
                  ../authenticate_pam.cc:170:11: note: suggested alternative: ‘rand_r’
                   void init(Handle<Object> exports) {
                             ^~~~~~
                             rand_r
                  ../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token
                   void init(Handle<Object> exports) {
                                          ^
                  ../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope
                   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
                   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’
                         (node::addon_register_func) (regfunc),                          \
                                                      ^~~~~~~
                  ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
                   NODE_MODULE(authenticate_pam, init);
                   ^~~~~~~~~~~
                  ../authenticate_pam.cc:175:31: note: suggested alternative: ‘int’
                   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’
                         (node::addon_register_func) (regfunc),                          \
                                                      ^~~~~~~
                  ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
                   NODE_MODULE(authenticate_pam, init);
                   ^~~~~~~~~~~
                  make: *** [authenticate_pam.target.mk:109: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                  make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
                  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.83-v7l+
                  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
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman/node_modules/chokidar/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/zigbee-herdsman/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  
                  npm ERR! code ELIFECYCLE
                  npm ERR! errno 1
                  npm ERR! authenticate-pam@1.0.2 install: `node-gyp rebuild`
                  npm ERR! Exit status 1
                  npm ERR!
                  npm ERR! Failed at the authenticate-pam@1.0.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/2021-01-24T16_44_12_411Z-debug.log
                  pi@raspberrypi4-iob:/opt/iobroker $
                  
                  

                  da ist wieder dieser doofe gyp ERR! -.-

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

                  @bjoegibbard

                  authenticate_pam

                  Keine Ahnung. Vielleicht baut das Modul nicht mehr gegen aktuelle node-Versionen. Das ist ja schon über ein Jahr nicht mehr angefasst worden.
                  Welcher Adapter braucht das Ding eigentlich?

                  npm list authenticate-pam
                  

                  Dürfte der terminal-Adapter sein. Braucht eh keiner.

                  iobroker del terminal
                  cd /opt/iobroker 
                  npm cache clean --force
                  

                  Danach sollte Ruhe von der Seite sein.

                  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

                  N 1 Antwort Letzte Antwort
                  1
                  • Thomas BraunT Thomas Braun

                    @bjoegibbard

                    authenticate_pam

                    Keine Ahnung. Vielleicht baut das Modul nicht mehr gegen aktuelle node-Versionen. Das ist ja schon über ein Jahr nicht mehr angefasst worden.
                    Welcher Adapter braucht das Ding eigentlich?

                    npm list authenticate-pam
                    

                    Dürfte der terminal-Adapter sein. Braucht eh keiner.

                    iobroker del terminal
                    cd /opt/iobroker 
                    npm cache clean --force
                    

                    Danach sollte Ruhe von der Seite sein.

                    N Offline
                    N Offline
                    nu_81
                    schrieb am zuletzt editiert von nu_81
                    #1356

                    Hatte lange Zeit ein ioBroker (mit altem Stand ohne Updates einzuspielen) auf einem Igel laufen
                    mit dem ich meinen S50 per Szene gesteuert habe.

                    Konkret hatte ich eine Szene "MAP_EG_Laden" erstellt.
                    Hierin wurde per SSH auf dem Roborock die Map Dateien getauscht und anschließend kurz gestartet und pausiert um die Karten auch wirklich zu laden.
                    ac383753-3e6f-4041-a4ea-961db2a6dbd8-image.png

                    Diese Szene habe ich dann vor jede andere Szene gepackt um dann die einzelnen Zonen anzufahren:
                    d7351236-12f3-4385-b020-cfb8b00b22cb-image.png

                    Das hat auch immer zuverlässig funktioniert.

                    Habe nun auf einen Raspberry mit aktueller Version gewechselt und da klappt es leider nicht mehr.
                    Immer wieder erscheint die Meldung
                    "should trigger cleaning all , but is currently active(5). Add to queue"
                    Der S50 reagiert dann auch überhaupt nicht, wenn ich z.B. Start auf true setze.

                    Muss ich z.B. den Pause Befehl manuell wieder auf false setzten um z.B. die Zonenreinigung zu starten?
                    Manchmal funktioniert es wieder wenn ich vor den Befehlen den "Home" Befehl mit rein nehme.

                    Es scheint eine neue Funktion der Queue zu geben, die ich hier scheinbar falsch bediene.

                    Das hier funktioniert z.B. manchmal:
                    2d440c48-bc88-4053-b1c7-4c2889d467f0-image.png

                    Hier noch der obere Teil im aufgeklappten Zustand:
                    3b35a682-d222-4f5f-9414-d13b653067f4-image.png

                    Aber auch hier kommt manchmal die Meldung mit der Queue.

                    Habe auch schon mal versucht "clearQueue" auf true zwischendurch einzusetzen. Aber auch das hilft nicht.
                    Leider verstehe ich da das Konzept der Queue auch nicht so recht.

                    Kann man die Queue Funktion irgendwie abschalten?
                    Wie kann ich die Queue eventuell löschen um den S50 zu "befreien" sodass er wieder Befehle annimmt?
                    Wie sollte ich hier am besten vorgehen um es wieder wie vorher zum laufen zu bekommen?

                    Gruß Nu

                    D 1 Antwort Letzte Antwort
                    0
                    • N nu_81

                      Hatte lange Zeit ein ioBroker (mit altem Stand ohne Updates einzuspielen) auf einem Igel laufen
                      mit dem ich meinen S50 per Szene gesteuert habe.

                      Konkret hatte ich eine Szene "MAP_EG_Laden" erstellt.
                      Hierin wurde per SSH auf dem Roborock die Map Dateien getauscht und anschließend kurz gestartet und pausiert um die Karten auch wirklich zu laden.
                      ac383753-3e6f-4041-a4ea-961db2a6dbd8-image.png

                      Diese Szene habe ich dann vor jede andere Szene gepackt um dann die einzelnen Zonen anzufahren:
                      d7351236-12f3-4385-b020-cfb8b00b22cb-image.png

                      Das hat auch immer zuverlässig funktioniert.

                      Habe nun auf einen Raspberry mit aktueller Version gewechselt und da klappt es leider nicht mehr.
                      Immer wieder erscheint die Meldung
                      "should trigger cleaning all , but is currently active(5). Add to queue"
                      Der S50 reagiert dann auch überhaupt nicht, wenn ich z.B. Start auf true setze.

                      Muss ich z.B. den Pause Befehl manuell wieder auf false setzten um z.B. die Zonenreinigung zu starten?
                      Manchmal funktioniert es wieder wenn ich vor den Befehlen den "Home" Befehl mit rein nehme.

                      Es scheint eine neue Funktion der Queue zu geben, die ich hier scheinbar falsch bediene.

                      Das hier funktioniert z.B. manchmal:
                      2d440c48-bc88-4053-b1c7-4c2889d467f0-image.png

                      Hier noch der obere Teil im aufgeklappten Zustand:
                      3b35a682-d222-4f5f-9414-d13b653067f4-image.png

                      Aber auch hier kommt manchmal die Meldung mit der Queue.

                      Habe auch schon mal versucht "clearQueue" auf true zwischendurch einzusetzen. Aber auch das hilft nicht.
                      Leider verstehe ich da das Konzept der Queue auch nicht so recht.

                      Kann man die Queue Funktion irgendwie abschalten?
                      Wie kann ich die Queue eventuell löschen um den S50 zu "befreien" sodass er wieder Befehle annimmt?
                      Wie sollte ich hier am besten vorgehen um es wieder wie vorher zum laufen zu bekommen?

                      Gruß Nu

                      D Nicht stören
                      D Nicht stören
                      dirkhe
                      Developer
                      schrieb am zuletzt editiert von
                      #1357

                      @nu_81 die queue ist dafür da, dass du einfach mehrere Räume starten kannst unser die dann nacheinander abarbeitet.
                      Wenn er nicht startet hat er eher verbindindungsprobleme. Sobald er wieder verbunden ist, sollte er starten.

                      N 1 Antwort Letzte Antwort
                      0
                      • D dirkhe

                        @nu_81 die queue ist dafür da, dass du einfach mehrere Räume starten kannst unser die dann nacheinander abarbeitet.
                        Wenn er nicht startet hat er eher verbindindungsprobleme. Sobald er wieder verbunden ist, sollte er starten.

                        N Offline
                        N Offline
                        nu_81
                        schrieb am zuletzt editiert von
                        #1358

                        Glaube nicht dass es Verbindungsprobleme sind.
                        Er reagiert z.B. überhaupt nicht auf start, gibt stattdessen die Meldung ins Log.
                        Auf z.B. auf Home oder "Wo bist du" reagiert er sofort.

                        D 1 Antwort Letzte Antwort
                        0
                        • N nu_81

                          Glaube nicht dass es Verbindungsprobleme sind.
                          Er reagiert z.B. überhaupt nicht auf start, gibt stattdessen die Meldung ins Log.
                          Auf z.B. auf Home oder "Wo bist du" reagiert er sofort.

                          D Nicht stören
                          D Nicht stören
                          dirkhe
                          Developer
                          schrieb am zuletzt editiert von
                          #1359

                          @nu_81 dann stell den adapter mal auf debug und poste das Log hier.

                          S 1 Antwort Letzte Antwort
                          0
                          • D dirkhe

                            @nu_81 dann stell den adapter mal auf debug und poste das Log hier.

                            S Offline
                            S Offline
                            Sweatchuck
                            schrieb am zuletzt editiert von
                            #1360

                            Hallo,

                            kurze Frage...

                            Meine beiden Robrock (S5 und S6) wollen ein Firmware-Update durchführen.
                            Von Version 3.5.8_2076 auf 3.5.8_2652 beim S6 bzw. 3.5.7_002008 auf 3.5.8_002034.

                            Da momentan aber alles super funktioniert will ich nicht einfach ein Update fahren und deshalb mal nachfragen ob jemand von euch Erfahrungen dies bzgl. hat. Angeblich handelt es sich dabei nur ein Bugfix?!

                            Beste Grüße

                            ? 1 Antwort Letzte Antwort
                            0
                            • JackDanielJ Offline
                              JackDanielJ Offline
                              JackDaniel
                              schrieb am zuletzt editiert von
                              #1361

                              keine probleme hier
                              2021-02-03 16_19_34-objects - ioBroker.jpg

                              Carpe diem

                              ? 1 Antwort Letzte Antwort
                              0
                              • S Sweatchuck

                                Hallo,

                                kurze Frage...

                                Meine beiden Robrock (S5 und S6) wollen ein Firmware-Update durchführen.
                                Von Version 3.5.8_2076 auf 3.5.8_2652 beim S6 bzw. 3.5.7_002008 auf 3.5.8_002034.

                                Da momentan aber alles super funktioniert will ich nicht einfach ein Update fahren und deshalb mal nachfragen ob jemand von euch Erfahrungen dies bzgl. hat. Angeblich handelt es sich dabei nur ein Bugfix?!

                                Beste Grüße

                                ? Offline
                                ? Offline
                                Ein ehemaliger Benutzer
                                schrieb am zuletzt editiert von
                                #1362

                                @sweatchuck
                                nee, meine 4 auch, mach doch mal, dann wissen wir ja, obs dann noch geht.. :-)

                                1 Antwort Letzte Antwort
                                0
                                • JackDanielJ JackDaniel

                                  keine probleme hier
                                  2021-02-03 16_19_34-objects - ioBroker.jpg

                                  ? Offline
                                  ? Offline
                                  Ein ehemaliger Benutzer
                                  schrieb am zuletzt editiert von
                                  #1363

                                  @jackdaniel mit Adapter Version ..??

                                  1 Antwort Letzte Antwort
                                  0
                                  • JackDanielJ Offline
                                    JackDanielJ Offline
                                    JackDaniel
                                    schrieb am zuletzt editiert von
                                    #1364

                                    bei mir läuft die 2.2.4

                                    Carpe diem

                                    1 Antwort Letzte Antwort
                                    0
                                    • S Offline
                                      S Offline
                                      Snapergy
                                      schrieb am zuletzt editiert von Snapergy
                                      #1365

                                      Puh, bin gerade echt am verzweifeln. Ich habe nichts weiter gemacht (zumindest nicht, dass ich wüsste), aber die Map lädt nicht mehr und es kommt immer folgender Fehler:

                                      answer map_slot is currently not supported!
                                      

                                      Was kann ich machen?

                                      EDIT: Hab die Lösung gefunden. Für alle, die das gleiche Problem haben:

                                      https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/119

                                      Lag am Update von NodeJS...

                                      1 Antwort Letzte Antwort
                                      1
                                      • S Offline
                                        S Offline
                                        Schwabe
                                        schrieb am zuletzt editiert von Schwabe
                                        #1366

                                        DANKE erstmal für diesen tollen Adapter und die kontinuierliche Arbeit daran.

                                        Wegen einem bevorstehenden Wechsel von einem ASUS TinkerBoard S auf ein Windows10 Ubunto-System habe ich aktuell 2 Versionen von dem Adapter laufen.
                                        Auf dem TinkerBoard S habe ich die Version 1.1.5 installiert und kann nicht auf die Version 2.1.1 updaten. Das Update wird stets mit einem Fehler beendet und der Adpater ist dann auch aus der VIS verschwunden. Ansonsten läuft diese Version zu meiner vollen Zufriedenheit.

                                        Mein Hauptproblem ist jedoch das der Adapter auf dem Ubuntu in der Version 2.1.1 bei "Gelb" bleibt. Ich kann zwar den Server (Germany) abfragen und den S6 übernehmen, doch der Adapter bleibt "Gelb".

                                        Die Konfigurationen sind gleich, wie auf den Screenshots zu sehen.
                                        Ich freue mich über jede Hilfe.

                                        ioBroker 2.png ioBroker 1.png
                                        Der LOG von dem Ubuntu-System ist folgender:

                                        2021-02-18 14:02:03.591 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                                        2021-02-18 14:02:03.593 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 send kill signal
                                        2021-02-18 14:02:03.594 - info: mihome-vacuum.0 (915) Got terminate signal TERMINATE_YOURSELF
                                        2021-02-18 14:02:03.595 - info: mihome-vacuum.0 (915) terminating
                                        2021-02-18 14:02:03.595 - info: mihome-vacuum.0 (915) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2021-02-18 14:02:04.111 - info: host.Server instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2021-02-18 14:02:06.615 - info: host.Server instance system.adapter.mihome-vacuum.0 started with pid 1020
                                        2021-02-18 14:02:07.105 - info: mihome-vacuum.0 (1020) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:02:07.146 - info: mihome-vacuum.0 (1020) Expert mode enabled, states created
                                        2021-02-18 14:02:07.146 - info: mihome-vacuum.0 (1020) Create state clean_home for controlling by cloud adapter
                                        2021-02-18 14:02:07.671 - info: mihome-vacuum.0 (1020) set nächster Timer: Nicht verfügbar
                                        2021-02-18 14:02:08.330 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:03:09.810 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:04:11.431 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:05:00.020 - info: host.Server instance system.adapter.dwd.0 started with pid 1035
                                        2021-02-18 14:05:00.580 - info: dwd.0 (1035) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:05:00.940 - info: dwd.0 (1035) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2021-02-18 14:05:01.450 - info: host.Server instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2021-02-18 14:05:13.192 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:06:14.647 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:07:16.150 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:08:01.090 - info: hm-rpc.0 (536) xmlrpc <- listDevices ["hm-rpc.0"]
                                        2021-02-18 14:08:01.117 - info: hm-rpc.0 (536) xmlrpc -> 0 devices
                                        2021-02-18 14:08:01.223 - info: hm-rpc.0 (536) xmlrpc <- newDevices 170
                                        2021-02-18 14:08:01.246 - info: hm-rpc.0 (536) new HMIP devices/channels after filter: 0
                                        2021-02-18 14:08:17.620 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:09:19.121 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:10:00.023 - info: host.Server instance system.adapter.dwd.0 started with pid 1050
                                        2021-02-18 14:10:00.597 - info: dwd.0 (1050) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:10:00.983 - info: dwd.0 (1050) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2021-02-18 14:10:01.493 - info: host.Server instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2021-02-18 14:10:20.475 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:11:22.013 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                        2021-02-18 14:11:55.186 - info: host.Server "system.adapter.mihome-vacuum.0" disabled
                                        2021-02-18 14:11:55.188 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                                        2021-02-18 14:11:55.188 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 send kill signal
                                        2021-02-18 14:11:55.190 - info: mihome-vacuum.0 (1020) Got terminate signal TERMINATE_YOURSELF
                                        2021-02-18 14:11:55.191 - info: mihome-vacuum.0 (1020) terminating
                                        2021-02-18 14:11:55.191 - info: mihome-vacuum.0 (1020) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2021-02-18 14:11:55.707 - info: host.Server instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2021-02-18 14:11:57.923 - info: host.Server "system.adapter.mihome-vacuum.0" enabled
                                        2021-02-18 14:11:57.941 - info: host.Server instance system.adapter.mihome-vacuum.0 started with pid 1065
                                        2021-02-18 14:11:58.436 - info: mihome-vacuum.0 (1065) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:11:58.478 - info: mihome-vacuum.0 (1065) Expert mode enabled, states created
                                        2021-02-18 14:11:58.478 - info: mihome-vacuum.0 (1065) Create state clean_home for controlling by cloud adapter
                                        2021-02-18 14:11:59.004 - info: mihome-vacuum.0 (1065) set nächster Timer: Nicht verfügbar
                                        2021-02-18 14:12:00.045 - info: host.Server instance system.adapter.weatherunderground.1 started with pid 1080
                                        2021-02-18 14:12:00.519 - info: weatherunderground.1 (1080) starting. Version 3.2.1 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:12:03.888 - info: weatherunderground.1 (1080) Terminated (NO_ERROR): Without reason
                                        2021-02-18 14:12:04.068 - info: host.Server instance system.adapter.weatherunderground.0 started with pid 1095
                                        2021-02-18 14:12:04.393 - info: host.Server instance system.adapter.weatherunderground.1 terminated with code 0 (NO_ERROR)
                                        2021-02-18 14:12:04.544 - info: weatherunderground.0 (1095) starting. Version 3.2.1 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v12.20.2, js-controller: 3.1.6
                                        2021-02-18 14:12:08.195 - info: weatherunderground.0 (1095) Terminated (NO_ERROR): Without reason
                                        2021-02-18 14:12:08.705 - info: host.Server instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR)
                                        
                                        haselchenH 1 Antwort Letzte Antwort
                                        0
                                        • S Schwabe

                                          DANKE erstmal für diesen tollen Adapter und die kontinuierliche Arbeit daran.

                                          Wegen einem bevorstehenden Wechsel von einem ASUS TinkerBoard S auf ein Windows10 Ubunto-System habe ich aktuell 2 Versionen von dem Adapter laufen.
                                          Auf dem TinkerBoard S habe ich die Version 1.1.5 installiert und kann nicht auf die Version 2.1.1 updaten. Das Update wird stets mit einem Fehler beendet und der Adpater ist dann auch aus der VIS verschwunden. Ansonsten läuft diese Version zu meiner vollen Zufriedenheit.

                                          Mein Hauptproblem ist jedoch das der Adapter auf dem Ubuntu in der Version 2.1.1 bei "Gelb" bleibt. Ich kann zwar den Server (Germany) abfragen und den S6 übernehmen, doch der Adapter bleibt "Gelb".

                                          Die Konfigurationen sind gleich, wie auf den Screenshots zu sehen.
                                          Ich freue mich über jede Hilfe.

                                          ioBroker 2.png ioBroker 1.png
                                          Der LOG von dem Ubuntu-System ist folgender:

                                          2021-02-18 14:02:03.591 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                                          2021-02-18 14:02:03.593 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 send kill signal
                                          2021-02-18 14:02:03.594 - info: mihome-vacuum.0 (915) Got terminate signal TERMINATE_YOURSELF
                                          2021-02-18 14:02:03.595 - info: mihome-vacuum.0 (915) terminating
                                          2021-02-18 14:02:03.595 - info: mihome-vacuum.0 (915) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2021-02-18 14:02:04.111 - info: host.Server instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2021-02-18 14:02:06.615 - info: host.Server instance system.adapter.mihome-vacuum.0 started with pid 1020
                                          2021-02-18 14:02:07.105 - info: mihome-vacuum.0 (1020) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:02:07.146 - info: mihome-vacuum.0 (1020) Expert mode enabled, states created
                                          2021-02-18 14:02:07.146 - info: mihome-vacuum.0 (1020) Create state clean_home for controlling by cloud adapter
                                          2021-02-18 14:02:07.671 - info: mihome-vacuum.0 (1020) set nächster Timer: Nicht verfügbar
                                          2021-02-18 14:02:08.330 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:03:09.810 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:04:11.431 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:05:00.020 - info: host.Server instance system.adapter.dwd.0 started with pid 1035
                                          2021-02-18 14:05:00.580 - info: dwd.0 (1035) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:05:00.940 - info: dwd.0 (1035) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2021-02-18 14:05:01.450 - info: host.Server instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2021-02-18 14:05:13.192 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:06:14.647 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:07:16.150 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:08:01.090 - info: hm-rpc.0 (536) xmlrpc <- listDevices ["hm-rpc.0"]
                                          2021-02-18 14:08:01.117 - info: hm-rpc.0 (536) xmlrpc -> 0 devices
                                          2021-02-18 14:08:01.223 - info: hm-rpc.0 (536) xmlrpc <- newDevices 170
                                          2021-02-18 14:08:01.246 - info: hm-rpc.0 (536) new HMIP devices/channels after filter: 0
                                          2021-02-18 14:08:17.620 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:09:19.121 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:10:00.023 - info: host.Server instance system.adapter.dwd.0 started with pid 1050
                                          2021-02-18 14:10:00.597 - info: dwd.0 (1050) starting. Version 2.5.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:10:00.983 - info: dwd.0 (1050) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2021-02-18 14:10:01.493 - info: host.Server instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2021-02-18 14:10:20.475 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:11:22.013 - info: tr-064.0 (726) forEachConfiguredDevice: in GetSpecificHostEntry 1(Mandy/ A8:DB:03:65:DB:6F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500}
                                          2021-02-18 14:11:55.186 - info: host.Server "system.adapter.mihome-vacuum.0" disabled
                                          2021-02-18 14:11:55.188 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
                                          2021-02-18 14:11:55.188 - info: host.Server stopInstance system.adapter.mihome-vacuum.0 send kill signal
                                          2021-02-18 14:11:55.190 - info: mihome-vacuum.0 (1020) Got terminate signal TERMINATE_YOURSELF
                                          2021-02-18 14:11:55.191 - info: mihome-vacuum.0 (1020) terminating
                                          2021-02-18 14:11:55.191 - info: mihome-vacuum.0 (1020) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2021-02-18 14:11:55.707 - info: host.Server instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2021-02-18 14:11:57.923 - info: host.Server "system.adapter.mihome-vacuum.0" enabled
                                          2021-02-18 14:11:57.941 - info: host.Server instance system.adapter.mihome-vacuum.0 started with pid 1065
                                          2021-02-18 14:11:58.436 - info: mihome-vacuum.0 (1065) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:11:58.478 - info: mihome-vacuum.0 (1065) Expert mode enabled, states created
                                          2021-02-18 14:11:58.478 - info: mihome-vacuum.0 (1065) Create state clean_home for controlling by cloud adapter
                                          2021-02-18 14:11:59.004 - info: mihome-vacuum.0 (1065) set nächster Timer: Nicht verfügbar
                                          2021-02-18 14:12:00.045 - info: host.Server instance system.adapter.weatherunderground.1 started with pid 1080
                                          2021-02-18 14:12:00.519 - info: weatherunderground.1 (1080) starting. Version 3.2.1 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:12:03.888 - info: weatherunderground.1 (1080) Terminated (NO_ERROR): Without reason
                                          2021-02-18 14:12:04.068 - info: host.Server instance system.adapter.weatherunderground.0 started with pid 1095
                                          2021-02-18 14:12:04.393 - info: host.Server instance system.adapter.weatherunderground.1 terminated with code 0 (NO_ERROR)
                                          2021-02-18 14:12:04.544 - info: weatherunderground.0 (1095) starting. Version 3.2.1 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v12.20.2, js-controller: 3.1.6
                                          2021-02-18 14:12:08.195 - info: weatherunderground.0 (1095) Terminated (NO_ERROR): Without reason
                                          2021-02-18 14:12:08.705 - info: host.Server instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR)
                                          
                                          haselchenH Offline
                                          haselchenH Offline
                                          haselchen
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #1367

                                          @schwabe

                                          Ich kann nur raten, aber im rechten Screenshot steht für V1 und S5 und Du hast einen S6.....

                                          Synology DS218+ & 2 x Fujitsu Esprimo (VM/Container) + FritzBox7590 + 2 AVM 3000 Repeater & Homematic & HUE & Osram & Xiaomi, NPM 10.9.4, Nodejs 22.21.0 ,JS Controller 7.0.7 ,Admin 7.7.19

                                          S 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

                                          372

                                          Online

                                          32.5k

                                          Benutzer

                                          81.8k

                                          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