Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. HAM (homebridge-ewlink) seit einer Woche tot

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    HAM (homebridge-ewlink) seit einer Woche tot

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

      @thomas-braun

      Stimmt, wenn man sich die ganzen Problem Threads wegen Node16 ansieht , braucht man sich keine Sorgen deswegen machen .

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

        @haselchen

        Mit einer sauberen Grund-Installation: Kein Problem.

        Rauszögern des Upgrades bringt es auch nicht. Das wird dadurch eher komplexer.

        Und bei mittlerweile 9000 node16 basierten Installationen finde ich die Anzahl der 'Problemthreads' hier auch nicht besonders hoch.

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

          @thomas-braun

          Da beide Versionen ihren Security Support bis Mitte/Ende 2023 haben , bleib ich erstmal bei 14.
          Kann ja sowieso jeder selber entscheiden.

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

            @haselchen sagte in HAM (homebridge-ewlink) seit einer Woche tot:

            Kann ja sowieso jeder selber entscheiden.

            Für sich selber: Ja.
            Das als Rat weitergeben: Nein.

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

              @thomas-braun

              Wenn Du der Meinung bist , dass mein Rat nicht passt , fühl Dich frei dem TE bei seinem Problem zu helfen.

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

                @haselchen

                2022-07-13 18:12:49.116  - info: host.chet iobroker Installing iobroker.ham@5.0.1... (System call)
2022-07-13 18:13:02.151  - info: host.chet iobroker
2022-07-13 18:13:02.153  - info: host.chet iobroker added 16 packages, removed 193 packages, and changed 1 package in 12s71 packages are looking for funding  run `npm fund` for details
2022-07-13 18:13:02.213  - info: host.chet iobroker host.chet install adapter ham
2022-07-13 18:13:02.273  - info: host.chet iobroker upload [27] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/admin.d.ts admin.d.ts video/mp2t
2022-07-13 18:13:04.425  - info: host.chet iobroker upload [20] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/config-dialog.jsx src/config-dialog.jsx text/jsx
2022-07-13 18:13:04.440  - info: host.chet iobroker upload [19] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/de.json src/i18n/de.json application/json
2022-07-13 18:13:04.455  - info: host.chet iobroker upload [18] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/en.json src/i18n/en.json application/json
2022-07-13 18:13:04.471  - info: host.chet iobroker upload [17] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/es.json src/i18n/es.json application/json
2022-07-13 18:13:04.487  - info: host.chet iobroker upload [16] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/fr.json src/i18n/fr.json application/json
2022-07-13 18:13:04.503  - info: host.chet iobroker upload [15] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/i18n.d.ts src/i18n/i18n.d.ts video/mp2t
2022-07-13 18:13:04.541  - info: host.chet iobroker upload [14] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/it.json src/i18n/it.json application/json
2022-07-13 18:13:04.555  - info: host.chet iobroker upload [13] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/nl.json src/i18n/nl.json application/json
2022-07-13 18:13:04.567  - info: host.chet iobroker upload [12] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/pl.json src/i18n/pl.json application/json
2022-07-13 18:13:04.579  - info: host.chet iobroker upload [11] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/pt.json src/i18n/pt.json application/json
2022-07-13 18:13:04.590  - info: host.chet iobroker upload [10] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/ru.json src/i18n/ru.json application/json
2022-07-13 18:13:04.605  - info: host.chet iobroker upload [9] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/i18n/zh-cn.json src/i18n/zh-cn.json application/json
2022-07-13 18:13:04.871  - info: host.chet iobroker upload [8] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/plugins-table.jsx src/plugins-table.jsx text/jsx
2022-07-13 18:13:04.898  - info: host.chet iobroker upload [7] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/search-field.jsx src/search-field.jsx text/jsx
2022-07-13 18:13:04.909  - info: host.chet iobroker upload [6] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/tab-app.jsx src/tab-app.jsx text/jsx
2022-07-13 18:13:04.919  - info: host.chet iobroker upload [5] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/tab-cache.js src/tab-cache.js application/javascript
2022-07-13 18:13:04.932  - info: host.chet iobroker upload [4] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/tab.jsx src/tab.jsx text/jsx
2022-07-13 18:13:04.953  - info: host.chet iobroker upload [3] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/src/tooltip-button.jsx src/tooltip-button.jsx text/jsx
2022-07-13 18:13:04.963  - info: host.chet iobroker upload [2] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/tab_m.html tab_m.html text/html
2022-07-13 18:13:04.973  - info: host.chet iobroker upload [1] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/tsconfig.json tsconfig.json application/json
2022-07-13 18:13:04.983  - info: host.chet iobroker upload [0] ham.admin /opt/iobroker/node_modules/iobroker.ham/admin/words.js words.js application/javascript
2022-07-13 18:13:05.136  - info: host.chet iobroker host.chet object system.adapter.ham created/updated
2022-07-13 18:13:05.251  - info: host.chet iobroker host.chet create instance ham
2022-07-13 18:13:05.270  - info: host.chet iobroker host.chet object system.adapter.ham.0.alive created
2022-07-13 18:13:05.289  - info: host.chet iobroker host.chet object system.adapter.ham.0.connected created
2022-07-13 18:13:05.309  - info: host.chet iobroker host.chet object system.adapter.ham.0.compactMode created
2022-07-13 18:13:05.326  - info: host.chet iobroker host.chet object system.adapter.ham.0.cpu created
2022-07-13 18:13:05.373  - info: host.chet iobroker host.chet object system.adapter.ham.0.cputime created
2022-07-13 18:13:05.386  - info: host.chet iobroker host.chet object system.adapter.ham.0.memHeapUsed created
2022-07-13 18:13:05.403  - info: host.chet iobroker host.chet object system.adapter.ham.0.memHeapTotal created
2022-07-13 18:13:05.471  - info: host.chet iobroker host.chet object system.adapter.ham.0.memRss created
2022-07-13 18:13:05.495  - info: host.chet iobroker host.chet object system.adapter.ham.0.uptime created
2022-07-13 18:13:05.510  - info: host.chet iobroker host.chet object system.adapter.ham.0.inputCount created
2022-07-13 18:13:05.527  - info: host.chet iobroker host.chet object system.adapter.ham.0.outputCount created
2022-07-13 18:13:05.544  - info: host.chet iobroker host.chet object system.adapter.ham.0.eventLoopLag created
2022-07-13 18:13:05.563  - info: host.chet iobroker host.chet object system.adapter.ham.0.sigKill created
2022-07-13 18:13:05.576  - info: host.chet iobroker host.chet object system.adapter.ham.0.logLevel created
2022-07-13 18:13:05.610  - info: host.chet iobroker host.chet object system.adapter.ham.0 created
2022-07-13 18:13:06.661  - info: host.chet iobroker exit 0
2022-07-13 18:14:01.629  - info: host.chet "system.adapter.ham.0" enabled
2022-07-13 18:14:01.903  - info: host.chet instance system.adapter.ham.0 started with pid 168175
2022-07-13 18:14:03.674  - info: ham.0 (168175) starting. Version 5.0.1 in /opt/iobroker/node_modules/iobroker.ham, node: v16.16.0, js-controller: 4.0.23
2022-07-13 18:14:03.713  - info: ham.0 (168175) Install/Update the following Libraries: homebridge-ewelink
2022-07-13 18:14:03.715  - info: ham.0 (168175) Install/Update homebridge-ewelink
2022-07-13 18:14:03.718  - info: ham.0 (168175) npm install homebridge-ewelink --production  --loglevel error (System call)
2022-07-13 18:15:57.963  - info: ham.0 (168175)
added 92 packages, and audited 93 packages in 2m
2022-07-13 18:15:57.967  - info: ham.0 (168175)
38 packages are looking for funding
  run `npm fund` for details
2022-07-13 18:15:57.969  - info: ham.0 (168175)
found 0 vulnerabilities
2022-07-13 18:15:58.044  - info: ham.0 (168175) All Libraries installed/updated
2022-07-13 18:15:58.045  - info: ham.0 (168175) Adapter uses Wrapper mode

                echad@chet:/opt/iobroker $ npm ls homebridge-ewelink
iobroker.inst@3.0.0 /opt/iobroker
└─┬ iobroker.ham@5.0.1
  └── homebridge-ewelink@10.0.0

                Soweit offenbar kein Problem mit node16.
                Auf welcher node-Version der TE unterwegs ist sehe ich nicht.
                Nur ist halt die Empfehlung 'hüben wie drüben' die node v16.

                Ein Thema könnte die Version aus Stable sein, da gebe ich dir sogar Recht:

                latest:	5.0.1 for 15 days
stable:	4.0.2 for 14 months

                Dann würde ich hier mal gezielt die 5.0.1 aus latest/beta picken, offenbar wird da ja gerade dran gearbeitet.

                1 Reply Last reply Reply Quote 0
                • W
                  WolfgangFB last edited by

                  @thomas-braun
                  Meine IO-Broker Konfiguration:

                  Node.js: v14.19.1
                  NPM: 6.14.16

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

                    @wolfgangfb

                    Ja, dann wäre meine Empfehlung und auch die der beiden involierten Projekte:
                    Node16.
                    Wenn die Laufzeitumgebung sauber installiert ist und es dann noch hakt kann man auf der stabilen Basis weiterschauen.

                    1 Reply Last reply Reply Quote 0
                    • W
                      WolfgangFB @haselchen last edited by

                      @haselchen sagte in HAM (homebridge-ewlink) seit einer Woche tot:

                      @wolfgangfb

                      Ja, mit eWeLink habe ich auch ordentlich gekämpft.
                      Ich hatte auf die V5 vom HAM upgedatet. Dann ging nix mehr .
                      Also alles gelöscht und komplett neu installiert.
                      Wichtig ist homebridge-eWeLink als Version 9.1.5 im Adapter eintragen .

                      Wo trage ich denn da die Version ein? Ich habe bei zusätzliche NPM-Module "homebridge-ewlink" einetragen.

                      Alles darüber braucht Node16.
                      Und Wichtig ist natürlich die Konfigurationsdatei. Da kann ich Dir leider nicht helfen.

                      Die Konfigurationsdatei sollte stimmen, da habe ich nichts dran geändert und es hat ja vor einer Woche noch funktioniert.
                      In den Logfiles sehe ich ja auch, dass die Geräte (hauptsächlich Sonoff) gefunden werden, nur die Werte werden nicht übermittelt.

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

                        @wolfgangfb

                        Wie sieht deine Einstellung im Adapter aus?

                        Hast du das Log vom Adapterstart und kannst es hier mal bitte zeigen?

                        W 1 Reply Last reply Reply Quote 0
                        • W
                          WolfgangFB last edited by

                          @thomas-braun sagte in HAM (homebridge-ewlink) seit einer Woche tot:

                          @wolfgangfb

                          Ja, dann wäre meine Empfehlung und auch die der beiden involierten Projekte:
                          Node16.

                          Ist die HowTo

                          https://forum.iobroker.net/topic/22867/how-to-node-js-f%C3%BCr-iobroker-richtig-updaten

                          noch aktuelle (letzter Eintrag vom Februar) oder gibt es etwas neueres zu Node 16?

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

                            @wolfgangfb

                            Ich bevorzuge diese:
                            https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
                            Aber da bin ich auch etwas voreingenommen.
                            Jedenfalls steht da auch was bzgl. node16 drin.

                            1 Reply Last reply Reply Quote 0
                            • W
                              WolfgangFB @haselchen last edited by

                              @haselchen sagte in HAM (homebridge-ewlink) seit einer Woche tot:

                              @wolfgangfb

                              Wie sieht deine Einstellung im Adapter aus?

                              Wrapper-Modus
                              Unsicheren Homebridge Modus verwenden in inaktiv.
                              Zusaätzliche npm Module: homebridge-ewlink

                              Konfiguration:

                              {
  "description": "Add configuration for your accessories or platforms according to the docs of the plugins.",
  "accessories": [
    {}
  ],
  "platforms": [
    {
      "platform": "eWeLink",
      "name": "eWeLink",
      "countryCode": "49",
      "username": "xxx@yyyy",
      "password": "xxxxxxxxx"
    }
  ]
}

                              Hast du das Log vom Adapterstart und kannst es hier mal bitte zeigen?

                              2022-07-13 19:43:34.369  - info: ham.0 (13082) Got terminate signal TERMINATE_YOURSELF
2022-07-13 19:43:34.377  - info: ham.0 (13082) cleaned everything up...
2022-07-13 19:43:34.458  - info: ham.0 (13082) terminating
2022-07-13 19:43:34.460  - info: ham.0 (13082) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-07-13 19:43:35.179  - info: host.raspberrypi instance system.adapter.ham.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-07-13 19:43:51.341  - info: ham.0 (27203) starting. Version 4.0.2 in /opt/iobroker/node_modules/iobroker.ham, node: v14.19.1, js-controller: 4.0.21
2022-07-13 19:43:51.383  - info: ham.0 (27203) Install/Update the following Libraries: homebridge-ewelink
2022-07-13 19:43:51.384  - info: ham.0 (27203) Install/Update homebridge-ewelink
2022-07-13 19:43:51.385  - info: ham.0 (27203) All Libraries installed/updated
2022-07-13 19:43:54.236  - info: ham.0 (27203) updateDev Zaehler-1: name = Zaehler-1 /type= 1
2022-07-13 19:43:54.239  - info: ham.0 (27203) updateChannel Zaehler-1.Accessory-Information: name = 
2022-07-13 19:43:54.242  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Identify: value = true /common= {"type":"boolean","read":false,"write":true,"role":"button","name":"Identify","unit":""}
2022-07-13 19:43:54.243  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Manufacturer: value = coolkit /common= {"type":"string","read":true,"write":false,"role":"text","name":"Manufacturer","unit":""}
2022-07-13 19:43:54.243  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Model: value = PSF-X67 (PSF-B67-GL) /common= {"type":"string","read":true,"write":false,"role":"text","name":"Model","unit":""}
2022-07-13 19:43:54.244  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Name: value = Zaehler-1 /common= {"type":"string","read":true,"write":false,"role":"text","name":"Name","unit":""}
2022-07-13 19:43:54.246  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Serial-Number: value = 1001553941SWX /common= {"type":"string","read":true,"write":false,"role":"text","name":"Serial Number","unit":""}
2022-07-13 19:43:54.247  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Firmware-Revision: value = 3.5.0 /common= {"type":"string","read":true,"write":false,"role":"text","name":"Firmware Revision","unit":""}
2022-07-13 19:43:54.248  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Configured-Name: value = Zaehler-1 /common= {"type":"string","read":true,"write":true,"role":"text","name":"Configured Name","unit":""}
2022-07-13 19:43:54.250  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Accessory-Flags: value = 0 /common= {"type":"number","min":0,"max":4294967295,"read":true,"write":false,"role":"value","name":"Accessory Flags","unit":""}
2022-07-13 19:43:54.251  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.App-Matching-Identifier: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"App Matching Identifier","unit":""}
2022-07-13 19:43:54.253  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Configured-Name: value =  /common= {"type":"string","read":true,"write":true,"role":"text","name":"Configured Name","unit":""}
2022-07-13 19:43:54.254  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Hardware-Finish: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Hardware Finish","unit":""}
2022-07-13 19:43:54.255  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Hardware-Revision: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Hardware Revision","unit":""}
2022-07-13 19:43:54.256  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Product-Data: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Product Data","unit":""}
2022-07-13 19:43:54.257  - info: ham.0 (27203) updateState Zaehler-1.Accessory-Information.Software-Revision: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Software Revision","unit":""}
2022-07-13 19:43:54.258  - info: ham.0 (27203) updateChannel Zaehler-1.Switch: name = 
2022-07-13 19:43:54.259  - info: ham.0 (27203) updateState Zaehler-1.Switch.On: value = false /common= {"type":"boolean","read":true,"write":true,"role":"switch","name":"On","unit":""}
2022-07-13 19:43:54.259  - info: ham.0 (27203) updateState Zaehler-1.Switch.Outlet-In-Use: value = false /common= {"type":"boolean","read":true,"write":false,"role":"sensor","name":"Outlet In Use","unit":""}
2022-07-13 19:43:54.260  - info: ham.0 (27203) updateState Zaehler-1.Switch.Current-Consumption: value = 0 /common= {"type":"number","unit":"W","min":0,"max":65535,"read":true,"write":false,"role":"value","name":"Current Consumption"}
2022-07-13 19:43:54.261  - info: ham.0 (27203) updateState Zaehler-1.Switch.Electric-Current: value = 0 /common= {"type":"number","unit":"A","min":0,"max":100000000000,"read":true,"write":false,"role":"value","name":"Electric Current"}
2022-07-13 19:43:54.261  - info: ham.0 (27203) updateState Zaehler-1.Switch.Voltage: value = 235 /common= {"type":"number","unit":"V","min":0,"max":100000000000,"read":true,"write":false,"role":"value","name":"Voltage"}
2022-07-13 19:43:54.262  - info: ham.0 (27203) updateState Zaehler-1.Switch.Name: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Name","unit":""}
2022-07-13 19:43:54.263  - info: ham.0 (27203) updateChannel Zaehler-1.Zaehler-1-History: name = Zaehler-1 History
2022-07-13 19:43:54.264  - info: ham.0 (27203) updateState Zaehler-1.Zaehler-1-History.Name: value = Zaehler-1 History /common= {"type":"string","read":true,"write":false,"role":"text","name":"Name","unit":""}
2022-07-13 19:43:54.264  - info: ham.0 (27203) updateState Zaehler-1.Zaehler-1-History.S2R1: value = 2zcSAAAAAAAf5WQoAQ4B3wfADwAAAAAAAAAAAQE= /common= {"type":"string","read":true,"write":false,"role":"text","name":"S2R1","unit":""}
2022-07-13 19:43:54.265  - info: ham.0 (27203) updateState Zaehler-1.Zaehler-1-History.S2R2: value = null /common= {"type":"string","read":true,"write":false,"role":"text","name":"S2R2","unit":""}
2022-07-13 19:43:54.265  - info: ham.0 (27203) updateState Zaehler-1.Zaehler-1-History.S2W1: value = null /common= {"type":"string","read":false,"write":true,"role":"text","name":"S2W1","unit":""}
2022-07-13 19:43:54.266  - info: ham.0 (27203) updateState Zaehler-1.Zaehler-1-History.S2W2: value = null /common= {"type":"string","read":false,"write":true,"role":"text","name":"S2W2","unit":""}
2022-07-13 19:43:54.274  - info: ham.0 (27203) updateDev DUALR3-2: name = DUALR3-2 /type= 1
2022-07-13 19:43:54.275  - info: ham.0 (27203) updateChannel DUALR3-2.Accessory-Information: name = 
2022-07-13 19:43:54.276  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Identify: value = true /common= {"type":"boolean","read":false,"write":true,"role":"button","name":"Identify","unit":""}
2022-07-13 19:43:54.277  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Manufacturer: value = SONOFF /common= {"type":"string","read":true,"write":false,"role":"text","name":"Manufacturer","unit":""}
2022-07-13 19:43:54.277  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Model: value = DUALR3 (E32-2SW-P0) /common= {"type":"string","read":true,"write":false,"role":"text","name":"Model","unit":""}
2022-07-13 19:43:54.279  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Name: value = DUALR3-2 /common= {"type":"string","read":true,"write":false,"role":"text","name":"Name","unit":""}
2022-07-13 19:43:54.279  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Serial-Number: value = 10014aa094SW0 /common= {"type":"string","read":true,"write":false,"role":"text","name":"Serial Number","unit":""}
2022-07-13 19:43:54.280  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Firmware-Revision: value = 1.4.0 /common= {"type":"string","read":true,"write":false,"role":"text","name":"Firmware Revision","unit":""}
2022-07-13 19:43:54.281  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Configured-Name: value = DUALR3-2 /common= {"type":"string","read":true,"write":true,"role":"text","name":"Configured Name","unit":""}
2022-07-13 19:43:54.282  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Accessory-Flags: value = 0 /common= {"type":"number","min":0,"max":4294967295,"read":true,"write":false,"role":"value","name":"Accessory Flags","unit":""}
2022-07-13 19:43:54.282  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.App-Matching-Identifier: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"App Matching Identifier","unit":""}
2022-07-13 19:43:54.283  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Configured-Name: value =  /common= {"type":"string","read":true,"write":true,"role":"text","name":"Configured Name","unit":""}
2022-07-13 19:43:54.284  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Hardware-Finish: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Hardware Finish","unit":""}
2022-07-13 19:43:54.284  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Hardware-Revision: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Hardware Revision","unit":""}
2022-07-13 19:43:54.285  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Product-Data: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Product Data","unit":""}
2022-07-13 19:43:54.286  - info: ham.0 (27203) updateState DUALR3-2.Accessory-Information.Software-Revision: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Software Revision","unit":""}
2022-07-13 19:43:54.286  - info: ham.0 (27203) updateChannel DUALR3-2.Switch: name = 
2022-07-13 19:43:54.287  - info: ham.0 (27203) updateState DUALR3-2.Switch.On: value = true /common= {"type":"boolean","read":true,"write":true,"role":"switch","name":"On","unit":""}
2022-07-13 19:43:54.288  - info: ham.0 (27203) updateState DUALR3-2.Switch.Name: value =  /common= {"type":"string","read":true,"write":false,"role":"text","name":"Name","unit":""}
2022-07-13 19:43:54.289  - info: ham.0 (27203) updateChannel DUALR3-2.DUALR3-2-History: name = DUALR3-2 History

                              Das geht dann noch ewig so weiter, es kommt aber kein Fehler.

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

                                @wolfgangfb

                                Okay, da würde jetzt von meiner Seite aus gesehen ne Menge Arbeit drinstecken.
                                Angefangen von der Adapter Version (aktuell bei Dir 4.0.2) bis zum JS Controller 4.0.21 und dann noch die NodeVersion (entweder hochziehen auf 14.20 oder 16.16.)
                                Davon hängt dann z.B. die Installation später ab, welche homebridge-ewelink Version.
                                Dann müsste man deine Konfig modifizieren.
                                Wie gesagt, aus meiner Sicht. Ich hab mich x Tage damit beschäftigt wegen unserer Beregnungsanlage.

                                W 1 Reply Last reply Reply Quote 0
                                • W
                                  WolfgangFB @haselchen last edited by

                                  @haselchen
                                  Ich habe jetzt mal eben auf einem zweiten Raspi mit IO-Broker Bastelinstallation den HAM Adapter (in Version 5.0.1) installiert. Hat auf den ersten Blick auch sofort alles geklappt. Nur kommen auch da keine Werte an und was mich stutzig macht ist, dass ein Sonoff, Relais, das ich letzte Woche hinzugefügt habe, in den Geräten überhaupt nicht auftaucht. Für mich sieht das so aus, als ob die Cloud permanent einen Stand von vor einer Woche senden würde.

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

                                    @wolfgangfb

                                    Deswegen sage ich ja, müsste man alles mal auf links drehen.
                                    Deine Konfig z.B.
                                    Die müsste eigentlich noch die Spezifikationen Deines/Deiner Geräte beinhalten.
                                    Die Zeile mit 49, der Länderkennung, kannste löschen.

                                    Hier ist die Anleitung für eine vernünftige Konfig

                                    https://github.com/bwp91/homebridge-ewelink/wiki/Configuration.

                                    Meine sieht so aus, für ein Sonoff 4ch Pro2

                                    {
  "description": "Add configuration for your accessories or platforms according to the docs of the plugins.",
  "accessories": [],
  "platforms": [
    {
      "name": "eWeLink",
      "mode": "auto",
      "username": "XXXXXX",
      "password": "XXXXXXX",
      "platform": "eWeLink",
      "multiDevices": [
        {
          "deviceId": "1000bacfb4",
          "deviceModel": "4ch",
          "showAs": "default"
        }
      ]
    }
  ]
}
                                    W 1 Reply Last reply Reply Quote 0
                                    • W
                                      WolfgangFB @haselchen last edited by

                                      @haselchen

                                      Nur mal blöd nachgefragt: Bei Dir kannst Du die ewlink Devices über IO-Broker steuern und bekommst auch die richtigen Zustände angezeigt?

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

                                        @wolfgangfb

                                        Ja, läuft alles .
                                        Ist zwar bis dahin, wie du selber siehst, erstmal nen gebastel, aber das Ergebnis ist klasse.
                                        Hatte das vorher über Node Red und das war ne Katastrophe , weil jedes Node in den Account musste und irgendwann geblockt wurde.

                                        W 1 Reply Last reply Reply Quote 0
                                        • W
                                          WolfgangFB @haselchen last edited by

                                          @haselchen
                                          Ich habe jetzt nochmal alles wie im Video von elzershark gemacht und ich bekomme einen Fehler:

                                          ERR! 404 Not Found - GET https://registry.npmjs.org/homebridge-ewlink - Not found npm ERR! 404 npm ERR! 404 'homebridge-ewlink@latest' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

                                          Wie kann ich das beheben?

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

                                            @wolfgangfb

                                            Guter Rat: Vergiss dem Mumpitz den der Elstertyp da immer verzapft. Das ist fast durchweg Grütze.
                                            Den zusätzlichen Adapter trägt man im ham-Adapter ein, ich würde das auch ohne Versionsangabe frei laufen lassen.

                                            Dir fehlt auch ein e im Adapternamen. Mit ewElink funktioniert das auch

                                            Hast du mal mit dem supertollen Elsterfrickel-Mega-Tool auf dein System eingedroschen? Das Ding ist Murks im Quadrat.

                                            W 1 Reply Last reply Reply Quote 2
                                            • First post
                                              Last post

                                            Support us

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

                                            829
                                            Online

                                            32.1k
                                            Users

                                            80.7k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            48
                                            1730
                                            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