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 haselchen

      @bjoegibbard

      Erstmal lösch das true aus der map url.
      Dann geh in die Adaptereinstellungen.
      Drück auf get Device .
      Erscheint dann dein Gerät?

      5c0c8562-29cb-4db6-af8b-7d53a29d9f92-grafik.png

      24bf6f50-5b8d-4230-bb4d-73baf02fb01b-grafik.png

      Und wenn das alles passt, sag mir noch ob du in der App die Map hast?!
      Ansonsten lass ich mal komplett alles saugen und dann zur Ladestation zurückfahren.
      Dann sollte er eine Map deines/r Hauses/Wohnung gezeichnet haben.

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

        @haselchen
        Die map kann ich in der App sehen.
        Get Device geht nicht.
        True Wert wurde entfernt.

        Ich habe unten den token ,die IP Adresse und Ports eingegeben.
        Leider wird mir kein Device angezeigt.

        Ich habe auch bereits versucht die Emailadresse durch die User id zu ersetzen, dennoch funktioniert getDevice() nicht.

        7f7465de-555b-4a50-9d81-eefea1a78752-image.png

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

          @bjoegibbard

          Bei den Einstellungen Email und Passwort aus der Mihome App.
          Der Sauger hat auch im Router immer die gleiche IP?
          Token hast du auslesen können ?
          Den kannst du Manuell ja auch eintragen unten.

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

            @haselchen
            Ja, Email und PW aus der MiHome App.
            Der Sauger hat eine statische IP.
            Token konnte ich auslesen und habe ihn manuell eingetragen.

            Auch die App habe ich bereits neu installiert.

            Zum token auslesen habe ich eine token_extractor.exe genutzt. Ist ein kleines Programm zum Auslesen des Tokens etc..

            Thomas Braun haselchen 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @bjoegibbard last edited by

              @bjoegibbard
              Die Token kann man doch auch direkt aus dem Adapter auslesen?

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

                @bjoegibbard

                Haste ihn mal saugen lassen?
                Manchmal dauert es bis er die Map geladen hat.

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

                  @thomas-braun

                  Due meinst wahrscheinlich die ganzen manuellen Einstellung leer lassen, sich anmelden und dann kommt der token automatisch?

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

                    @haselchen

                    Ja er saugt jetzt das zweite mal.
                    (Langsam kann ich das Teil nicht mehr hören 😄 )

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

                      @bjoegibbard

                      Nein , die Anmeldedaten müssen eingetragen sein.
                      Mach mal den Adapter auf Debug und poste das Log beim Adapterstart.

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

                        @haselchen
                        69310c6d-8d95-4f4a-84bf-a9b1bdf6d25a-image.png
                        807f1684-3bda-4c5e-9b90-0c3c85d51d55-image.png
                        50712e94-2062-437d-8e50-b4381dc692f3-image.png
                        049899a0-da50-44dd-8303-4b550143d387-image.png
                        4cf168dc-7748-4ee2-a061-c92200834fed-image.png

                        Thomas Braun haselchen 2 Replies Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @bjoegibbard last edited by

                          @bjoegibbard
                          Bitte keine zerstückelten Screenshots posten sondern Log Texte auch als Text (in CodeTags) hier rein.

                          B 1 Reply Last reply Reply Quote 1
                          • 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
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            617
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            map mihome-vacuum roborock xiaomi
                                            144
                                            1474
                                            445400
                                            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