Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter mihome-vacuum v2.0.x

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter mihome-vacuum v2.0.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • haselchen
      haselchen Most Active @bjoegibbard last edited by

      @bjoegibbard

      Keine Fehlermeldung. Scheint alles okay zu sein?!
      Was steht jetzt im Ordner Map?

      Und wie @Thomas-Braun schrieb, bitte in Code Tags.

      B 1 Reply Last reply Reply Quote 0
      • B
        bjoegibbard @Thomas Braun last edited by

        @thomas-braun

        2021-01-24 16:23:20.048  - info: mihome-vacuum.0 (5705) terminating
        2021-01-24 16:23:20.049  - info: mihome-vacuum.0 (5705) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2021-01-24 16:23:20.721  - info: host.raspberrypi4-iob instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2021-01-24 16:23:23.077  - info: host.raspberrypi4-iob instance system.adapter.mihome-vacuum.0 started with pid 6418
        2021-01-24 16:23:24.434  - debug: mihome-vacuum.0 (6418) Redis Objects: Use Redis connection: veraendert
        2021-01-24 16:23:24.471  - debug: mihome-vacuum.0 (6418) Objects client ready ... initialize now
        2021-01-24 16:23:24.474  - debug: mihome-vacuum.0 (6418) Objects create System PubSub Client
        2021-01-24 16:23:24.475  - debug: mihome-vacuum.0 (6418) Objects create User PubSub Client
        2021-01-24 16:23:24.477  - debug: mihome-vacuum.0 (6418) Objects client initialize lua scripts
        2021-01-24 16:23:24.504  - debug: mihome-vacuum.0 (6418) Objects connected to redis: veraendert
        2021-01-24 16:23:24.513  - debug: mihome-vacuum.0 (6418) objectDB connected
        2021-01-24 16:23:24.516  - debug: mihome-vacuum.0 (6418) Redis States: Use Redis connection: veraendert
        2021-01-24 16:23:24.527  - debug: mihome-vacuum.0 (6418) States create System PubSub Client
        2021-01-24 16:23:24.528  - debug: mihome-vacuum.0 (6418) States create User PubSub Client
        2021-01-24 16:23:24.540  - debug: mihome-vacuum.0 (6418) States connected to redis: veraendert
        2021-01-24 16:23:24.541  - debug: mihome-vacuum.0 (6418) statesDB connected
        2021-01-24 16:23:25.703  - info: mihome-vacuum.0 (6418) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.18.3, js-controller: 3.2.8
        2021-01-24 16:23:25.801  - debug: mihome-vacuum.0 (6418) load Map creator... true
        2021-01-24 16:23:25.803  - debug: mihome-vacuum.0 (6418) Xiaomi Cloud: Logging in
        2021-01-24 16:23:25.812  - info: mihome-vacuum.0 (6418) Expert mode enabled, states created
        2021-01-24 16:23:25.813  - info: mihome-vacuum.0 (6418) Cloud control disabled
        2021-01-24 16:23:25.827  - debug: mihome-vacuum.0 (6418) server started on veraendert
        2021-01-24 16:23:25.899  - info: mihome-vacuum.0 (6418) change states from State control.fan_power
        2021-01-24 16:23:25.900  - info: mihome-vacuum.0 (6418) extend state mop for State control.fan_power
        2021-01-24 16:23:25.901  - info: mihome-vacuum.0 (6418) New generation or new fw(3.5.8,002034) detected, create new states goto and zoneclean
        2021-01-24 16:23:25.910  - debug: mihome-vacuum.0 (6418) Receive <<< Helo <<< veraendert
        2021-01-24 16:23:25.911  - warn: mihome-vacuum.0 (6418) Time difference between Mihome Vacuum and ioBroker: 1 sec
        2021-01-24 16:23:25.911  - info: mihome-vacuum.0 (6418) connecting, this can take up to 10 minutes ...
        2021-01-24 16:23:25.913  - debug: mihome-vacuum.0 (6418) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
        2021-01-24 16:23:25.919  - debug: mihome-vacuum.0 (6418) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
        2021-01-24 16:23:25.936  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":1,"method":"get_status"}
        2021-01-24 16:23:25.945  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[{"msg_ver":3,"msg_seq":2614,"state":8,"battery":96,"clean_time":690,"clean_area":13170000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":104,"dnd_enabled":0,"map_status":1,"lock_status":0}],"id":1}
        2021-01-24 16:23:25.948  - debug: mihome-vacuum.0 (6418) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
        2021-01-24 16:23:25.965  - info: mihome-vacuum.0 (6418) Connected
        2021-01-24 16:23:26.167  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
        2021-01-24 16:23:26.169  - debug: mihome-vacuum.0 (6418) Next WiFi check: 24.01 16:24
        2021-01-24 16:23:26.179  - debug: mihome-vacuum.0 (6418) Receive <<< {"partner_id":"","id":2,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_002034","ap":{"ssid":"veraendert","bssid":"veraendert","rssi":-23},"netif":{"localIp":"veraendert","mask":"veraendert","gw":"veraendert"},"miio_ver":"miio-client 3.5.8","model":"roborock.vacuum.s5","mac":"veraendert","token":"veraendert","life":47353}}
        2021-01-24 16:23:26.367  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":3,"method":"get_sound_volume"}
        2021-01-24 16:23:26.373  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[100],"id":3}
        2021-01-24 16:23:26.377  - info: mihome-vacuum.0 (6418) set nächster Timer: Nicht verfügbar
        2021-01-24 16:23:26.567  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
        2021-01-24 16:23:26.574  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[{"main_brush_work_time":11011,"side_brush_work_time":11011,"filter_work_time":11011,"filter_element_work_time":0,"sensor_dirty_time":11011}],"id":4}
        2021-01-24 16:23:26.768  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
        2021-01-24 16:23:26.777  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[1662944,24087925000,1159,[1611500298,1611498316,1611498123,1611497130,1611492488,1611492296,1611492277,1611492234,1611491816,1611423950,1611423782,1611422676,1611416509,1611402090,1610826971,1610824848,1610819714,1610793254,1610793182,1610793133]],"id":5}
        2021-01-24 16:23:26.782  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1611500298]}
        2021-01-24 16:23:26.795  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[[1611500298,1611501039,690,13170000,0,0,2,1]],"id":6}
        2021-01-24 16:23:26.968  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
        2021-01-24 16:23:26.970  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
        2021-01-24 16:23:26.976  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":7}
        2021-01-24 16:23:26.978  - info: mihome-vacuum.0 (6418) create state for carpet_mode
        2021-01-24 16:23:26.981  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[],"id":8}
        2021-01-24 16:23:26.982  - debug: mihome-vacuum.0 (6418) Empty array try to get from Map
        2021-01-24 16:23:26.983  - debug: mihome-vacuum.0 (6418) get rooms from map
        2021-01-24 16:23:26.984  - debug: mihome-vacuum.0 (6418) get rooms from map pending...
        2021-01-24 16:23:26.990  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":9,"method":"get_clean_record","params":[1611498316]}
        2021-01-24 16:23:26.999  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[[1611498316,1611498317,0,0,0,0,2,1]],"id":9}
        2021-01-24 16:23:27.167  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
        2021-01-24 16:23:27.173  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":["retry"],"id":10}
        2021-01-24 16:23:27.193  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":11,"method":"get_clean_record","params":[1611498123]}
        2021-01-24 16:23:27.205  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[[1611498123,1611498170,40,602500,0,0,2,1]],"id":11}
        2021-01-24 16:23:27.394  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":12,"method":"get_clean_record","params":[1611497130]}
        2021-01-24 16:23:27.404  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[[1611497130,1611497739,602,11325000,0,0,2,1]],"id":12}
        2021-01-24 16:23:27.596  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":13,"method":"get_clean_record","params":[1611492488]}
        2021-01-24 16:23:27.602  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":[[1611492488,1611492494,5,0,0,0,2,1]],"id":13}
        2021-01-24 16:23:27.675  - debug: mihome-vacuum.0 (6418) sendMsg[1] >>> {"id":14,"method":"get_map_v1"}
        2021-01-24 16:23:27.676  - debug: mihome-vacuum.0 (6418) 0. Mappointer_nomap___retry
        2021-01-24 16:23:27.688  - debug: mihome-vacuum.0 (6418) Receive <<< {"result":["robomap%veraendert"],"id":veraendert}
        2021-01-24 16:23:27.688  - debug: mihome-vacuum.0 (6418) Mappointer_updated
        
        1 Reply Last reply Reply Quote 0
        • B
          bjoegibbard @haselchen last edited by

          @haselchen

          Jo, habe es mal fix im code tag gepostet.

          75371d43-8023-4194-9c8c-322c01b9f2db-image.png

          Hat sich nicht verändert.
          Aber wie gesagt get device geht irgendwie immer noch nicht 😕

          1 Reply Last reply Reply Quote 0
          • haselchen
            haselchen Most Active last edited by haselchen

            @bjoegibbard

            Da meine Kräfte langsam schwinden, hilft es vielleicht nur noch den Entwickler zu fragen
            @Meistertr

            B 1 Reply Last reply Reply Quote 1
            • B
              bjoegibbard @haselchen last edited by

              @haselchen
              Danke euch dennoch erstmal!

              haselchen 1 Reply Last reply Reply Quote 0
              • haselchen
                haselchen Most Active @bjoegibbard last edited by

                @bjoegibbard

                Ich denke das hakt an irgendeiner Einstellung.
                Adapter Einstellungen hatte ich ja gepostet, die solltest du auch so haben.
                Bleiben nur noch die App Einstellungen.
                Da müsste man Stück für Stück alles durchgehen. Aber das kriege ich heute nicht mehr hin.

                1 Reply Last reply Reply Quote 0
                • B
                  bjoegibbard last edited by 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 Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @bjoegibbard last edited by 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 1 Reply Last reply Reply Quote 0
                    • B
                      bjoegibbard @Thomas Braun last edited by 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 Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @bjoegibbard last edited by

                        @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 1 Reply Last reply Reply Quote 0
                        • B
                          bjoegibbard @Thomas Braun last edited by

                          @thomas-braun

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

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @bjoegibbard last edited by

                            @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 1 Reply Last reply Reply Quote 0
                            • B
                              bjoegibbard @Thomas Braun last edited by 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 Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @bjoegibbard last edited by 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 1 Reply Last reply Reply Quote 1
                                • N
                                  nu_81 @Thomas Braun last edited by 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 1 Reply Last reply Reply Quote 0
                                  • D
                                    dirkhe Developer @nu_81 last edited by

                                    @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 Reply Last reply Reply Quote 0
                                    • N
                                      nu_81 @dirkhe last edited by

                                      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 Reply Last reply Reply Quote 0
                                      • D
                                        dirkhe Developer @nu_81 last edited by

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

                                        S 1 Reply Last reply Reply Quote 0
                                        • S
                                          Sweatchuck @dirkhe last edited by

                                          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 Reply Last reply Reply Quote 0
                                          • JackDaniel
                                            JackDaniel last edited by

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

                                            ? 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            442
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            map mihome-vacuum roborock xiaomi
                                            144
                                            1474
                                            445480
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo