Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Updates nicht mehr möglich wegen HAM Tato Adapter

    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

    SOLVED Updates nicht mehr möglich wegen HAM Tato Adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • Glasfaser
      Glasfaser @Atredis last edited by

      @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

      3.0.14

      Habe den Schritt noch nicht gemacht , hast du dich an die Anleitung gehalten , die
      apollon77 geschrieben hat !?
      Link Text

      A 1 Reply Last reply Reply Quote 0
      • A
        Atredis @Homoran last edited by

        @Homoran
        #Nur um zu verhindern das Ich was falsch gemacht habe.
        Was ist mit installationsverzeichniss genau gemeint.

        Iobroker

        andreas@debian64bit:/home/iobroker$ ls
        andreas@debian64bit:/home/iobroker$ npm rebuild
        andreas@debian64bit:/home/iobroker$ 
        
        
        Homoran 1 Reply Last reply Reply Quote 0
        • A
          Atredis @Glasfaser last edited by

          @Glasfaser
          Ja an Die Anleitung habe ich mich so wie ich mich erinner gehalten.
          Ist schon ein paar Tage her und aufgrund meiner geringen Kenntnisse mache ich fast alles nach Anleitung.

          Auch wenn man immer mehr das System begreift

          1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @Atredis last edited by

            @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

            /home/iobroker$

            das nicht!

            üblicherweise /opt/iobroker

            1 Reply Last reply Reply Quote 0
            • A
              Atredis last edited by

              Ok.

              Habe das Verzeichniss jetzt mal genommen.
              Komme aber auch nicht weiter

              Manuelles entfernen klappt auch nicht

              andreas@debian64bit:/opt/iobroker/node_modules$ npm uninstall homebridge-tado-platform
              npm ERR! code ENOTSUP
              npm ERR! notsup Unsupported engine for homebridge-tado-platform@5.1.6: wanted: {"homebridge":"^0.4.46","node":"^10.15.3"} (current: {"node":"12.16.2","npm":"6.14.4"})
              npm ERR! notsup Not compatible with your version of node/npm: homebridge-tado-platform@5.1.6
              npm ERR! notsup Not compatible with your version of node/npm: homebridge-tado-platform@5.1.6
              npm ERR! notsup Required: {"homebridge":"^0.4.46","node":"^10.15.3"}
              npm ERR! notsup Actual:   {"npm":"6.14.4","node":"12.16.2"}
              
              npm ERR! A complete log of this run can be found in:
              npm ERR!     /home/iobroker/.npm/_logs/2020-04-24T15_19_17_835Z-debug.log
              
              1 Reply Last reply Reply Quote 0
              • A
                Atredis last edited by

                NPM Rebuild auch erfolglos

                andreas@debian64bit:/opt/iobroker$ npm rebuild
                
                > iobroker@2.0.3 install /opt/iobroker/node_modules/iobroker
                > node lib/checkVersions.js
                
                NPM version: 6.14.4
                
                > iobroker@2.0.3 postinstall /opt/iobroker/node_modules/iobroker
                > node lib/install.js
                
                lib/install.js is not being run as part of an installation - skipping...
                
                > @abandonware/noble@1.9.2-8 install /opt/iobroker/node_modules/@abandonware/noble
                > node-gyp rebuild
                
                make: Verzeichnis „/opt/iobroker/node_modules/@abandonware/noble/build“ wird betreten
                  SOLINK_MODULE(target) Release/obj.target/noble.node
                  COPY Release/noble.node
                make: Verzeichnis „/opt/iobroker/node_modules/@abandonware/noble/build“ wird verlassen
                
                > iobroker.javascript@4.5.1 postinstall /opt/iobroker/node_modules/iobroker.javascript
                > node ./install/installTypings.js
                
                Installing NodeJS typings...
                latest @types: 13, installed node: 12
                
                > iobroker.js-controller@3.0.14 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                > node lib/preinstallCheck.js
                
                NPM version: 6.14.4
                
                > iobroker.js-controller@3.0.14 install /opt/iobroker/node_modules/iobroker.js-controller
                > node iobroker.js setup first
                
                object system.certificates updated
                
                The following notifications happened during sync: 
                - Ignoring Directory "daswetter.admin" because officially not created as meta object. Please remove directory!
                - Ignoring Directory "senec.admin" because officially not created as meta object. Please remove directory!
                
                
                > nodemailer@6.4.6 postinstall /opt/iobroker/node_modules/nodemailer
                > node -e "try{require('./postinstall')}catch(e){}"
                
                === Nodemailer 6.4.6 ===
                
                Thank you for using Nodemailer for your email sending needs! While Nodemailer
                itself is mostly meant to be a SMTP client there are other related projects in
                the Nodemailer project as well.
                
                For example:
                > IMAP API (  https://imapapi.com  ) is a server application to easily access
                IMAP accounts via REST API
                > NodemailerApp (  https://nodemailer.com/app/  ) is a cross platform GUI app to
                debug emails
                
                
                > iobroker.vis@1.2.6 install /opt/iobroker/node_modules/iobroker.vis
                > node main.js --install
                
                
                > serialport@8.0.7 postinstall /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/serialport
                > node thank-you.js
                
                Thank you for using serialport!
                If you rely on this package, please consider supporting our open collective:
                > https://opencollective.com/serialport/donate
                
                
                
                > @serialport/bindings@8.0.7 install /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                
                
                > acme-v2@1.8.6 postinstall /opt/iobroker/node_modules/acme-v2
                > node scripts/postinstall
                
                
                Greenlock and ACME.js v3 are on the way!
                Watch for updates at https://indiegogo.com/at/greenlock
                
                
                > 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:2298: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:1024: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:1024: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.16.2/include/node/v8-internal.h:14,
                                 from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
                                 from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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], long unsigned int)’
                    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                                                                     ^
                In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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.16.2/include/node/v8-internal.h:14,
                                 from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
                                 from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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], long unsigned int)’
                    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                                                                  ^
                In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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], long unsigned int)’
                  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                                                          ^
                In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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], long unsigned int)’
                  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                                                          ^
                In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                 from ../../nan/nan.h:54,
                                 from ../authenticate_pam.cc:23:
                /home/iobroker/.cache/node-gyp/12.16.2/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.16.2/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:54,
                                 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.16.2/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.16.2/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:111: 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/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                gyp ERR! stack     at ChildProcess.emit (events.js:310:20)
                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                gyp ERR! System Linux 4.19.0-6-amd64
                gyp ERR! command "/usr/local/bin/node" "/usr/local/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.16.2
                gyp ERR! node-gyp -v v5.1.0
                gyp ERR! not ok 
                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/2020-04-24T15_25_33_123Z-debug.log
                andreas@debian64bit:/opt/iobroker$ 
                
                
                Homoran 1 Reply Last reply Reply Quote 0
                • Homoran
                  Homoran Global Moderator Administrators @Atredis last edited by

                  @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

                  NPM Rebuild auch erfolglos

                  das log sagt ja auch warum:

                  @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

                  wanted: {"homebridge":"^0.4.46","node":"^10.15.3"} (current: {"node":"12.16.2","npm":"6.14.4"

                  1 Reply Last reply Reply Quote 0
                  • A
                    Atredis last edited by

                    Ja aber wie bekomme ich den Adapter gelöscht?

                    Im HAM habe ich Ihn entfernt.
                    Auch den HAM Adapter habe ich entfernt.
                    Er taucht nicht mehr auf.

                    Allerdings kam auch beim entfernen vom HAM die Fehlermeldung.

                    1 Reply Last reply Reply Quote 0
                    • A
                      Atredis last edited by

                      Ok. Gibt wohl keine einfache Lösung für das Problem.
                      Dachte mir dann einfach Node Nodejs deinstallieren und die 10´er Installieren.

                      Leider auch nicht möglich

                      andreas@debian64bit:~$ sudo apt-get --purge remove node
                      Paketlisten werden gelesen... Fertig
                      Abhängigkeitsbaum wird aufgebaut.       
                      Statusinformationen werden eingelesen.... Fertig
                      E: Paket node kann nicht gefunden werden.
                      andreas@debian64bit:~$ 
                      andreas@debian64bit:~$ node -v
                      v12.16.2
                      andreas@debian64bit:~$ which node
                      /usr/local/bin/node
                      andreas@debian64bit:~$ 
                      
                      
                      Glasfaser 1 Reply Last reply Reply Quote 0
                      • Glasfaser
                        Glasfaser @Atredis last edited by

                        @Atredis

                        Du hast doch VM ...
                        warum nimmst du kein Schnappschuss und gehst damit zurück !?

                        1 Reply Last reply Reply Quote 0
                        • A
                          Atredis last edited by

                          Das werde ich wohl machen müssen. Wenn ich nur noch wüsste wann ich das Update gemacht habe.

                          Danke aber trotzdem für die mühen.

                          Um halt besser klar zu kommen wäre mir ein anderer Lösungsweg lieber gewesen.

                          Glasfaser 1 Reply Last reply Reply Quote 0
                          • Glasfaser
                            Glasfaser @Atredis last edited by Glasfaser

                            @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

                            Wenn ich nur noch wüsste wann ich das Update gemacht habe.

                            Nach der Version JS 3.0.14 , im Bereich vom 21. Apr. 2020 + /-

                            Man kann doch in der Beschreibung vom Schnappschuss eine Notiz hinterlegen , was enthalten ist .

                            A 1 Reply Last reply Reply Quote 0
                            • A
                              Atredis @Glasfaser last edited by

                              @Glasfaser

                              Ja.
                              Jetzt bin ich da auch schlauer.
                              Mein NAS macht jeden Tag einen Snapshot.
                              Bin jetzt ein paar Tage zurück gegangen.
                              Vorher Update erstellt
                              Alles eingespielt.
                              Versucht den Adapter zu löschen.
                              Ging nicht weil er nicht da war.

                              Alles auf den neusten Stand gebracht.

                              Und es läuft wieder.

                              Mal im Auge behalten.
                              Vielleicht hat sich da auch nur irgendwas eingeschlichen.

                              Dann kann ich morgen mich ja wieder um meine Steuerung kümmern.

                              Aber danke fürs überlegen woran es gelegen haben kan

                              Dann würde ich den Beitrag hier mit gelöst schließen wenn ich das hin bekomme

                              Glasfaser 1 Reply Last reply Reply Quote 0
                              • Glasfaser
                                Glasfaser @Atredis last edited by Glasfaser

                                @Atredis sagte in Updates nicht mehr möglich wegen HAM Tato Adapter:

                                Vielleicht hat sich da auch nur irgendwas eingeschlichen.
                                Mein NAS macht jeden Tag einen Snapshot.

                                Ja ... ist keine Lösung wenn man ein Fehler hat ...

                                Aber ist besser bevor man sich alles zerschießt 😉

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                946
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                updates ham tado
                                3
                                23
                                1045
                                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