Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Tester Zigbee Adapter 3.x gesucht

    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

    Tester Zigbee Adapter 3.x gesucht

    This topic has been deleted. Only users with topic management privileges can see it.
    • Asgothian
      Asgothian Developer @Hadebe last edited by Asgothian

      @hadebe auf GitHub gibt es seit heute einen Branch der immer die latest ZHC nutzt. Du kannst diesen installieren - allerdings ist das aktuell nicht aktiv getestet, da ich für die kommenden 6 Wochen keine Tests durchführen kann.

      Link zur Installation ist:
      https://github.com/ioBroker/ioBroker.zigbee/tarball/ZHC_latest

      Wichtig: Die ZHC Version die installiert wird hängt davon ab zu welchem Zeitpunkt diese Version installiert wird. Ansonsten bleibt der Adapter-Code synchron zum Hauptzweig. Ich kann aber nicht garantieren das durch Anpassungen am ZHC sich etwas verändert.

      Ansonsten kannst du versuchen einen externen Konverter für das Gerät zu bauen. Das erfordert etwas wissen in JS. Der Normale Weg ist:

      • im Qelltext der ZHC den Converter finden
      • Identifizieren welche Includes / Requires dieser benötigt (alles in der gleichen Datei)
      • Aus diesen Daten eine JS Datei wie im Spoiler als Beispiel hinterlegt erzeugen

      const tuya = require('zigbee-herdsman-converters/lib/tuya');
const modernExtend = require('zigbee-herdsman-converters/lib/modernExtend');

const {deviceEndpoints, onOff} = require('zigbee-herdsman-converters/lib/modernExtend');
const exposes = require("zigbee-herdsman-converters/lib/exposes");
const ea = exposes.access;
const e = exposes.presets;

const definition = {
   zigbeeModel: ['TS000F'], // The model ID from the device.
   model: 'TS000F',
   vendor: 'inventwo',
   description: '1-Kanal-Relais mit DS18B20',
   fingerprint: [{modelID: 'TS000F', manufacturerName: '_TZ3218_7fiyo3kv'}], // This helps z2m identify the device
   fromZigbee: [tuya.fz.datapoints], // Define converters that are used to convert from Zigbee messages to MQTT messages.
   toZigbee: [], // Define converters that are used to convert from MQTT messages to Zigbee messages.
   
   extend: [
       deviceEndpoints({"endpoints":{"0":0,"1":1}}),
       onOff({"powerOnBehavior":false,"endpointNames":["1"]}),
       // tuya.modernExtend.dpTemperature({dp: 0x66, scale: 10})
       ],
   
    exposes: [
       e.temperature().withDescription('inventwo Innenraum'),
   ], // Defines what capabilities (like temperature or on/off) are exposed to MQTT
   
   meta: {
       multiEndpoint: true,
       tuyaDatapoints: [
           [102, 'temperature', tuya.valueConverter.divideBy10]
       ]
   },

   configure: async (device, coordinatorEndpoint, logger) => {
       const endpoint = device.getEndpoint(1);
       await endpoint.bind('genOnOff', coordinatorEndpoint);
       // More configurations can be added here
   },
};

module.exports = definition;

      • diese Datei im Zigbee Datenverzeichnis ablegen (/opt/iobroker/iobroker-data/zigbee_0)
      • den Dateinamen in der Adapter-Konfig unter 'external converters' ablegen.
      • Adapter neu starten, und im Log prüfen ob er geladen wird.

      A.

      H 1 Reply Last reply Reply Quote 1
      • H
        Hadebe @Eduard77 last edited by

        @edis77 Das ist ein sehr guter Tip, danke dafür. Wie bei dir 23.13.0

        Nachdem ich wie von @Asgothian vorgeschlagen von github den Adapter installiert habe, sieht die ZHC Welt besser aus:

        2025-06-29 10:50:55.502 - info: zigbee.0 (1106116) Installed Version: ioBroker/ioBroker.zigbee (Converters 23.35.0 Herdsman 4.0.0)

        Das ist zwar gut, aber noch knapp vor der von @Edis77 zitierten. Ich warte dann weiter...

        1 Reply Last reply Reply Quote 0
        • H
          Hadebe @Asgothian last edited by

          @asgothian habe deinen Link bei "Adapter installieren" > "aus eigener URL" >"benutzerdefiniert" eingegeben (so war es vermutlich gemeint). Leider wird die selbe Konverter Version angezogen wie bei Installation von github:

          2025-06-30 08:29:21.581 - info: zigbee.0 (1183192) Installed Version: ioBroker/ioBroker.zigbee#ZHC_latest (Converters 23.35.0 Herdsman 4.0.0)

          Habe ich dich richtig verstanden, dass unter deinem Link häufiger Updates erfolgen als im github Hauptzweig, d.h. ich würde die Installation in ein paar Tagen wiederholen und hätte eine höhere Version?

          Und danke für deinen Versuch meine Skills auf einen neuen Level zu heben, aber mein Wissen über JS bewegt sich nah bei Null

          Ansonsten bleibt für mich warten.

          1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer last edited by

            @hadebe da muss bei deiner Installation etwas schief gegangen sein. Eigentlich solltest du ZHC 23.66.0 bekommen haben.

            Bitte unter /opt/iobroker/node-modules prüfen welche ZHC versione(en) installiert sind.

            Eduard77 H 2 Replies Last reply Reply Quote 0
            • Eduard77
              Eduard77 @Asgothian last edited by Eduard77

              @asgothian
              ich habe jetzt von deinem Github Link installiert und bei mir sieht es jetzt so aus.

              zigbee.0 2025-06-30 09:07:29.423	info	Installed Version: ioBroker/ioBroker.zigbee#ZHC_latest (Converters 23.67.0 Herdsman 4.0.0)
              1 Reply Last reply Reply Quote 0
              • H
                Hadebe @Asgothian last edited by Hadebe

                @asgothian dein Link funktioniert offensichtlich. War mein Vorgehen korrekt?

                Bin in dem Verzeichnis, aber wie finde ich die Version - in package.json ist nur 23.35.0 eingetragen?

                Asgothian 1 Reply Last reply Reply Quote 0
                • Asgothian
                  Asgothian Developer @Hadebe last edited by

                  @hadebe du musst über npm auf der Konsole auflisten lassen welche version(en) installiert sind - es kann mehrere geben. Ich hab den Befehl nicht im Kopf und kann das auch nicht mal eben prüfen, sorry.

                  A.

                  Gaspode H 2 Replies Last reply Reply Quote 0
                  • Gaspode
                    Gaspode @Asgothian last edited by Gaspode

                    @asgothian said in Tester Zigbee Adapter 3.x gesucht:

                    du musst über npm auf der Konsole auflisten lassen welche version(en) installiert sind

                    @hadebe
                    z.B. so:

                    npm ls zigbee-herdsman-converters
                    H 1 Reply Last reply Reply Quote 0
                    • H
                      Hadebe @Asgothian last edited by

                      @Asgothian bei mir ist nur die ältere Version vorhanden:

                      pi@raspi01:/opt/iobroker/node_modules $ npm ls zigbee-herdsman-converters
iobroker.inst@3.0.0 /opt/iobroker
└─┬ iobroker.zigbee@3.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#ae472aefab7fbb3c70b56d3c477662e265e52f03)
  └── zigbee-herdsman-converters@23.35.0
                      Asgothian 1 Reply Last reply Reply Quote 0
                      • H
                        Hadebe @Gaspode last edited by

                        @gaspode danke, da hätte ich lange forschen müssen

                        1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @Hadebe last edited by

                          @hadebe bitte nochmal vom gleichen link installieren. Du solltest jetzt eine neuere Version bekommen.

                          H Eduard77 2 Replies Last reply Reply Quote 0
                          • H
                            Hadebe @Asgothian last edited by

                            @asgothian Super! So geht's.

                            pi@raspi01:/opt/iobroker/node_modules $ npm ls zigbee-herdsman-converters
iobroker.inst@3.0.0 /opt/iobroker
└─┬ iobroker.zigbee@3.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#7a9fc13062e49f8aea5b8e7b5cccfb4f90d45b3c)
  └── zigbee-herdsman-converters@23.67.0

                            Mit der neuen Version wird auch das Gerät erkannt

                            1 Reply Last reply Reply Quote 0
                            • Eduard77
                              Eduard77 @Asgothian last edited by

                              @asgothian
                              Vielen Dank für Hilfe,
                              mit Github Version konnte ich jetzt 2 Geräte einbinden, die vorher nicht funktioniert haben.
                              83770b83-9a8f-4fd5-8094-6a73c80d4211-image.png

                              1 Reply Last reply Reply Quote 0
                              • M
                                MeisterQ 0 last edited by MeisterQ 0

                                @Asgothian wie kann ich ne aktuellere Herdsman Converter Version bekommen?
                                Aktuell läuft bei mir 23.35.0.

                                Bei einem Bekannten läuft eine aktuellere Version. Ich hab den Adapter noch mal neu Installiert aus Github, aber das ändert ja leider nix. Nur wenn er im Latest ist oder?

                                Wann gibt es eine neue Version?

                                root@iobroker:/opt/iobroker/node_modules# npm ls zigbee-herdsman-converters
iobroker.inst@3.0.0 /opt/iobroker
`-- iobroker.zigbee@3.0.1 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#3da4e44dd0db1b540b35c6e54832c152b7e80408)
  `-- zigbee-herdsman-converters@23.35.0

                                Edit:

                                Ich habs mit dem https://github.com/ioBroker/ioBroker.zigbee/tarball/ZHC_latest zum laufen bekommen. Sorry. Hatte nicht weit genug hoch gescrollt und gelesen.

                                1 Reply Last reply Reply Quote 0
                                • David G.
                                  David G. last edited by

                                  Mir ist seit kurzem folgendes Verhalten aufgefallen, ich weiß nur nicht, ob das durch den Wechsel auf v3.x(oder v2.x was nur kurz lief) aufgetreten ist.
                                  Bei 1.x hatte ich es glaube noch nicht.

                                  Wenn die Verbindung zum LAN Koordinator kurz verloren geht, kommt Word der Zigbee Adapter gelb und bleibt es auch, wenn die Verbindung wieder kommt. Ich glaube, das hatte ich früher nicht.

                                  Merke das, wenn ich die Fritzbox neustarte, an der der iobroker und der Koordinator angeschlossen sind. Die Telekom bietet im Moment was instabiles Internet. Das versuche ich den reboot (der idr nichts bringt).

                                  Asgothian arteck 2 Replies Last reply Reply Quote 0
                                  • Asgothian
                                    Asgothian Developer @David G. last edited by

                                    @david-g poste bitte mal das log wenn das passiert. Es ist denkbar das der reconnect beim Wechsel auf die 3.0 nicht sauber ist - den konnte ich nur rudimentär testen.

                                    A.

                                    David G. 1 Reply Last reply Reply Quote 0
                                    • arteck
                                      arteck Developer Most Active @David G. last edited by

                                      @david-g sagte in Tester Zigbee Adapter 3.x gesucht:

                                      Ich glaube, das hatte ich früher nicht.

                                      doch war schon immer so.. wir hatten da keinen reconnect..

                                      meistens war das problem mit den coordinatoren die per WLAN angebunden waren

                                      1 Reply Last reply Reply Quote 0
                                      • David G.
                                        David G. @Asgothian last edited by

                                        @asgothian

                                        Das Log sagt nichts. Hab nur gesehen, dass er die Geräte nicht anpingen kann. Im Debug aicu nichts.

                                        Auf Debug gestellt, log gelöscht, Fritzbox neugestartet.

                                        Kommt nur das übliche:

                                        zigbee.0
2025-07-12 09:52:46.867	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35661.281' seconds ago.

zigbee.0
2025-07-12 09:52:46.866	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2381.872' seconds ago.

zigbee.0
2025-07-12 09:52:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11413.795' seconds ago.

zigbee.0
2025-07-12 09:52:46.864	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4555.594' seconds ago.

zigbee.0
2025-07-12 09:52:46.864	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1336.044' seconds ago.

zigbee.0
2025-07-12 09:52:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '1186.921' seconds ago.

zigbee.0
2025-07-12 09:52:46.860	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685737.847' seconds ago.

zigbee.0
2025-07-12 09:52:46.860	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1317.135' seconds ago.

zigbee.0
2025-07-12 09:52:46.858	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '1232.924' seconds ago.

zigbee.0
2025-07-12 09:52:46.857	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '18263.525' seconds ago.

zigbee.0
2025-07-12 09:52:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5555.001' seconds ago.

zigbee.0
2025-07-12 09:51:46.868	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35601.282' seconds ago.

zigbee.0
2025-07-12 09:51:46.866	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2321.872' seconds ago.

zigbee.0
2025-07-12 09:51:46.865	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11353.794' seconds ago.

zigbee.0
2025-07-12 09:51:46.864	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4495.594' seconds ago.

zigbee.0
2025-07-12 09:51:46.863	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1276.043' seconds ago.

zigbee.0
2025-07-12 09:51:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '1126.921' seconds ago.

zigbee.0
2025-07-12 09:51:46.860	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685677.847' seconds ago.

zigbee.0
2025-07-12 09:51:46.860	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1257.136' seconds ago.

zigbee.0
2025-07-12 09:51:46.858	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '1172.924' seconds ago.

zigbee.0
2025-07-12 09:51:46.857	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '18203.525' seconds ago.

zigbee.0
2025-07-12 09:51:46.855	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5495' seconds ago.

zigbee.0
2025-07-12 09:50:46.867	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35541.281' seconds ago.

zigbee.0
2025-07-12 09:50:46.866	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2261.872' seconds ago.

zigbee.0
2025-07-12 09:50:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11293.795' seconds ago.

zigbee.0
2025-07-12 09:50:46.863	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4435.593' seconds ago.

zigbee.0
2025-07-12 09:50:46.863	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1216.043' seconds ago.

zigbee.0
2025-07-12 09:50:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '1066.921' seconds ago.

zigbee.0
2025-07-12 09:50:46.859	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685617.846' seconds ago.

zigbee.0
2025-07-12 09:50:46.858	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1197.134' seconds ago.

zigbee.0
2025-07-12 09:50:46.857	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '1112.923' seconds ago.

zigbee.0
2025-07-12 09:50:46.857	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '18143.525' seconds ago.

zigbee.0
2025-07-12 09:50:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5435.001' seconds ago.

zigbee.0
2025-07-12 09:49:46.868	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35481.282' seconds ago.

zigbee.0
2025-07-12 09:49:46.867	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2201.873' seconds ago.

zigbee.0
2025-07-12 09:49:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11233.795' seconds ago.

zigbee.0
2025-07-12 09:49:46.863	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4375.593' seconds ago.

zigbee.0
2025-07-12 09:49:46.862	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1156.042' seconds ago.

zigbee.0
2025-07-12 09:49:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '1006.921' seconds ago.

zigbee.0
2025-07-12 09:49:46.859	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685557.846' seconds ago.

zigbee.0
2025-07-12 09:49:46.858	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1137.134' seconds ago.

zigbee.0
2025-07-12 09:49:46.857	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '1052.923' seconds ago.

zigbee.0
2025-07-12 09:49:46.856	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '18083.524' seconds ago.

zigbee.0
2025-07-12 09:49:46.855	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5375' seconds ago.

zigbee.0
2025-07-12 09:48:46.868	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35421.282' seconds ago.

zigbee.0
2025-07-12 09:48:46.867	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2141.873' seconds ago.

zigbee.0
2025-07-12 09:48:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11173.795' seconds ago.

zigbee.0
2025-07-12 09:48:46.863	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4315.593' seconds ago.

zigbee.0
2025-07-12 09:48:46.862	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1096.042' seconds ago.

zigbee.0
2025-07-12 09:48:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '946.921' seconds ago.

zigbee.0
2025-07-12 09:48:46.858	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685497.845' seconds ago.

zigbee.0
2025-07-12 09:48:46.857	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1077.133' seconds ago.

zigbee.0
2025-07-12 09:48:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '992.922' seconds ago.

zigbee.0
2025-07-12 09:48:46.855	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '18023.523' seconds ago.

zigbee.0
2025-07-12 09:48:46.854	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5314.999' seconds ago.

zigbee.0
2025-07-12 09:47:46.868	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35361.282' seconds ago.

zigbee.0
2025-07-12 09:47:46.867	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2081.873' seconds ago.

zigbee.0
2025-07-12 09:47:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11113.795' seconds ago.

zigbee.0
2025-07-12 09:47:46.863	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4255.593' seconds ago.

zigbee.0
2025-07-12 09:47:46.862	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '1036.042' seconds ago.

zigbee.0
2025-07-12 09:47:46.861	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '886.921' seconds ago.

zigbee.0
2025-07-12 09:47:46.858	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685437.845' seconds ago.

zigbee.0
2025-07-12 09:47:46.857	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '1017.133' seconds ago.

zigbee.0
2025-07-12 09:47:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '932.922' seconds ago.

zigbee.0
2025-07-12 09:47:46.855	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '17963.523' seconds ago.

zigbee.0
2025-07-12 09:47:46.854	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5254.999' seconds ago.

zigbee.0
2025-07-12 09:46:46.867	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35301.281' seconds ago.

zigbee.0
2025-07-12 09:46:46.866	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '2021.872' seconds ago.

zigbee.0
2025-07-12 09:46:46.866	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '11053.795' seconds ago.

zigbee.0
2025-07-12 09:46:46.864	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4195.594' seconds ago.

zigbee.0
2025-07-12 09:46:46.863	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '976.043' seconds ago.

zigbee.0
2025-07-12 09:46:46.860	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '826.92' seconds ago.

zigbee.0
2025-07-12 09:46:46.858	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685377.845' seconds ago.

zigbee.0
2025-07-12 09:46:46.857	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '957.133' seconds ago.

zigbee.0
2025-07-12 09:46:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '872.922' seconds ago.

zigbee.0
2025-07-12 09:46:46.855	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '17903.523' seconds ago.

zigbee.0
2025-07-12 09:46:46.854	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5194.999' seconds ago.

zigbee.0
2025-07-12 09:45:55.253	debug	No value published for device a4c13862cd091bcf

zigbee.0
2025-07-12 09:45:55.253	debug	value generated '0' from device a4c13862cd091bcf for 'Link quality'

zigbee.0
2025-07-12 09:45:55.253	debug	message received '{"linkquality":0}' from device a4c13862cd091bcf type 'TS011F_plug_1'

zigbee.0
2025-07-12 09:45:55.253	debug	No value published for device a4c13862cd091bcf

zigbee.0
2025-07-12 09:45:55.253	debug	value generated 'false' from device a4c13862cd091bcf for 'Available'

zigbee.0
2025-07-12 09:45:55.252	debug	message received '{"available":false}' from device a4c13862cd091bcf type 'TS011F_plug_1'

zigbee.0
2025-07-12 09:45:55.252	debug	DeviceAvailability:Publish LQ for 0xa4c13862cd091bcf = 0

zigbee.0
2025-07-12 09:45:55.252	debug	DeviceAvailability:Publish available for 0xa4c13862cd091bcf = false

zigbee.0
2025-07-12 09:45:55.251	debug	DeviceAvailability:Failed to ping 0xa4c13862cd091bcf TS011F on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:46.867	debug	DeviceAvailability:Non-pingable device 0x94ec32fffe024878 RODRET Dimmer was last seen '35241.281' seconds ago.

zigbee.0
2025-07-12 09:45:46.866	debug	DeviceAvailability:Non-pingable device 0x00158d000544e4b1 lumi.sensor_motion.aq2 was last seen '1961.872' seconds ago.

zigbee.0
2025-07-12 09:45:46.865	debug	DeviceAvailability:Non-pingable device 0xa4c138ebcf547772 TS0207 was last seen '10993.794' seconds ago.

zigbee.0
2025-07-12 09:45:46.863	debug	DeviceAvailability:Non-pingable device 0xa4c138932f7d376a TS0044 was last seen '4135.593' seconds ago.

zigbee.0
2025-07-12 09:45:46.862	debug	DeviceAvailability:Non-pingable device 0x00124b002519401e TH01 was last seen '916.042' seconds ago.

zigbee.0
2025-07-12 09:45:46.860	debug	DeviceAvailability:Non-pingable device 0x00124b002513bb34 TH01 was last seen '766.92' seconds ago.

zigbee.0
2025-07-12 09:45:46.857	debug	DeviceAvailability:Non-pingable device 0x00158d0009ee4112 lumi.vibration.aq1 was last seen '12685317.844' seconds ago.

zigbee.0
2025-07-12 09:45:46.856	debug	DeviceAvailability:Non-pingable device 0xa4c138744ca8c6c8 TS0202 was last seen '897.132' seconds ago.

zigbee.0
2025-07-12 09:45:46.855	debug	DeviceAvailability:Non-pingable device 0xa4c13876d17ec059 TS0202 was last seen '812.921' seconds ago.

zigbee.0
2025-07-12 09:45:46.855	debug	DeviceAvailability:Non-pingable device 0x804b50fffefb471f TRADFRI on/off switch was last seen '17843.523' seconds ago.

zigbee.0
2025-07-12 09:45:46.853	debug	DeviceAvailability:Non-pingable device 0xa4c138757132f69d TS0207 was last seen '5134.998' seconds ago.

zigbee.0
2025-07-12 09:45:31.955	debug	DeviceAvailability:Failed to ping 0xf0d1b8000013d3a8 Panel TW Z3 on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:27.410	debug	DeviceAvailability:Failed to ping 0xf0d1b800001c4c80 Plug Value on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:26.016	debug	No value published for device 403059fffe4d2fdc

zigbee.0
2025-07-12 09:45:26.016	debug	value generated '0' from device 403059fffe4d2fdc for 'Link quality'

zigbee.0
2025-07-12 09:45:26.016	debug	message received '{"linkquality":0}' from device 403059fffe4d2fdc type 'ICPSHC24-30-IL44-1'

zigbee.0
2025-07-12 09:45:26.016	debug	No value published for device 403059fffe4d2fdc

zigbee.0
2025-07-12 09:45:26.016	debug	value generated 'false' from device 403059fffe4d2fdc for 'Available'

zigbee.0
2025-07-12 09:45:26.016	debug	message received '{"available":false}' from device 403059fffe4d2fdc type 'ICPSHC24-30-IL44-1'

zigbee.0
2025-07-12 09:45:26.015	debug	DeviceAvailability:Publish LQ for 0x403059fffe4d2fdc = 0

zigbee.0
2025-07-12 09:45:26.015	debug	DeviceAvailability:Publish available for 0x403059fffe4d2fdc = false

zigbee.0
2025-07-12 09:45:26.014	info	Failed to ping 0x403059fffe4d2fdc SILVERGLANS IP44 LED driver

zigbee.0
2025-07-12 09:45:25.642	debug	DeviceAvailability:Failed to ping 0x7cb03eaa0a081585 Plug 01 on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:25.006	debug	No value published for device 142d41fffe4b7b58

zigbee.0
2025-07-12 09:45:25.006	debug	value generated '0' from device 142d41fffe4b7b58 for 'Link quality'

zigbee.0
2025-07-12 09:45:25.006	debug	message received '{"linkquality":0}' from device 142d41fffe4b7b58 type 'LED2005R5/LED2106R3'

zigbee.0
2025-07-12 09:45:25.006	debug	No value published for device 142d41fffe4b7b58

zigbee.0
2025-07-12 09:45:25.006	debug	value generated 'false' from device 142d41fffe4b7b58 for 'Available'

zigbee.0
2025-07-12 09:45:25.006	debug	message received '{"available":false}' from device 142d41fffe4b7b58 type 'LED2005R5/LED2106R3'

zigbee.0
2025-07-12 09:45:25.006	debug	DeviceAvailability:Publish LQ for 0x142d41fffe4b7b58 = 0

zigbee.0
2025-07-12 09:45:25.005	debug	DeviceAvailability:Publish available for 0x142d41fffe4b7b58 = false

zigbee.0
2025-07-12 09:45:25.005	info	Failed to ping 0x142d41fffe4b7b58 TRADFRI bulb GU10 WS 345lm

zigbee.0
2025-07-12 09:45:24.491	debug	No value published for device bc33acfffeb20bf5

zigbee.0
2025-07-12 09:45:24.491	debug	value generated '0' from device bc33acfffeb20bf5 for 'Link quality'

zigbee.0
2025-07-12 09:45:24.491	debug	message received '{"linkquality":0}' from device bc33acfffeb20bf5 type 'LED1837R5'

zigbee.0
2025-07-12 09:45:24.491	debug	No value published for device bc33acfffeb20bf5

zigbee.0
2025-07-12 09:45:24.491	debug	value generated 'false' from device bc33acfffeb20bf5 for 'Available'

zigbee.0
2025-07-12 09:45:24.491	debug	message received '{"available":false}' from device bc33acfffeb20bf5 type 'LED1837R5'

zigbee.0
2025-07-12 09:45:24.491	debug	DeviceAvailability:Publish LQ for 0xbc33acfffeb20bf5 = 0

zigbee.0
2025-07-12 09:45:24.490	debug	DeviceAvailability:Publish available for 0xbc33acfffeb20bf5 = false

zigbee.0
2025-07-12 09:45:24.490	info	Failed to ping 0xbc33acfffeb20bf5 TRADFRI bulb GU10 WW 400lm

zigbee.0
2025-07-12 09:45:23.991	debug	DeviceAvailability:Failed to ping 0xa4c1385864ba12d4 TS011F on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:23.988	debug	No value published for device 60a423fffef0ff05

zigbee.0
2025-07-12 09:45:23.988	debug	value generated '0' from device 60a423fffef0ff05 for 'Link quality'

zigbee.0
2025-07-12 09:45:23.988	debug	message received '{"linkquality":0}' from device 60a423fffef0ff05 type 'LED1837R5'

zigbee.0
2025-07-12 09:45:23.988	debug	No value published for device 60a423fffef0ff05

zigbee.0
2025-07-12 09:45:23.988	debug	value generated 'false' from device 60a423fffef0ff05 for 'Available'

zigbee.0
2025-07-12 09:45:23.988	debug	message received '{"available":false}' from device 60a423fffef0ff05 type 'LED1837R5'

zigbee.0
2025-07-12 09:45:23.988	debug	DeviceAvailability:Publish LQ for 0x60a423fffef0ff05 = 0

zigbee.0
2025-07-12 09:45:23.987	debug	DeviceAvailability:Publish available for 0x60a423fffef0ff05 = false

zigbee.0
2025-07-12 09:45:23.987	info	Failed to ping 0x60a423fffef0ff05 TRADFRI bulb GU10 WW 400lm

zigbee.0
2025-07-12 09:45:23.642	debug	DeviceAvailability:Failed to ping 0xbc33acfffe9b50d6 TRADFRI bulb GU10 WW 400lm on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:21.697	debug	DeviceAvailability:Failed to ping 0xbc33acfffea94381 TRADFRI bulb GU10 WW 400lm on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:21.202	debug	DeviceAvailability:Failed to ping 0xbc33acfffec026df TRADFRI bulb GU10 WW 400lm on [object Object] consecutive attempts

zigbee.0
2025-07-12 09:45:20.574	debug	No value published for device bc33acfffe5f8ea0

zigbee.0
2025-07-12 09:45:20.574	debug	value generated '0' from device bc33acfffe5f8ea0 for 'Link quality'

zigbee.0
2025-07-12 09:45:20.574	debug	message received '{"linkquality":0}' from device bc33acfffe5f8ea0 type 'LED1733G7'

zigbee.0
2025-07-12 09:45:20.574	debug	No value published for device bc33acfffe5f8ea0

zigbee.0
2025-07-12 09:45:20.574	debug	value generated 'false' from device bc33acfffe5f8ea0 for 'Available'

zigbee.0
2025-07-12 09:45:20.574	debug	message received '{"available":false}' from device bc33acfffe5f8ea0 type 'LED1733G7'

zigbee.0
2025-07-12 09:45:20.574	debug	DeviceAvailability:Publish LQ for 0xbc33acfffe5f8ea0 = 0

zigbee.0
2025-07-12 09:45:20.574	debug	DeviceAvailability:Publish available for 0xbc33acfffe5f8ea0 = false

zigbee.0
2025-07-12 09:45:20.574	info	Failed to ping 0xbc33acfffe5f8ea0 TRADFRI bulb E14 WS opal 600lm

zigbee.0
2025-07-12 09:45:19.998	debug	No value published for device cc86ecfffe952a0e

zigbee.0
2025-07-12 09:45:19.997	debug	value generated '0' from device cc86ecfffe952a0e for 'Link quality'

zigbee.0
2025-07-12 09:45:19.997	debug	message received '{"linkquality":0}' from device cc86ecfffe952a0e type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:19.997	debug	No value published for device cc86ecfffe952a0e

zigbee.0
2025-07-12 09:45:19.997	debug	value generated 'false' from device cc86ecfffe952a0e for 'Available'

zigbee.0
2025-07-12 09:45:19.997	debug	message received '{"available":false}' from device cc86ecfffe952a0e type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:19.997	debug	DeviceAvailability:Publish LQ for 0xcc86ecfffe952a0e = 0

zigbee.0
2025-07-12 09:45:19.996	debug	DeviceAvailability:Publish available for 0xcc86ecfffe952a0e = false

zigbee.0
2025-07-12 09:45:19.995	info	Failed to ping 0xcc86ecfffe952a0e TRADFRI bulb GU10 WS 400lm

zigbee.0
2025-07-12 09:45:19.497	debug	No value published for device 84fd27fffed0858b

zigbee.0
2025-07-12 09:45:19.497	debug	value generated '0' from device 84fd27fffed0858b for 'Link quality'

zigbee.0
2025-07-12 09:45:19.496	debug	message received '{"linkquality":0}' from device 84fd27fffed0858b type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:19.495	debug	No value published for device 84fd27fffed0858b

zigbee.0
2025-07-12 09:45:19.495	debug	value generated 'false' from device 84fd27fffed0858b for 'Available'

zigbee.0
2025-07-12 09:45:19.494	debug	message received '{"available":false}' from device 84fd27fffed0858b type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:19.494	debug	DeviceAvailability:Publish LQ for 0x84fd27fffed0858b = 0

zigbee.0
2025-07-12 09:45:19.494	debug	DeviceAvailability:Publish available for 0x84fd27fffed0858b = false

zigbee.0
2025-07-12 09:45:19.493	info	Failed to ping 0x84fd27fffed0858b TRADFRI bulb GU10 WS 400lm

zigbee.0
2025-07-12 09:45:18.985	debug	No value published for device 804b50fffea8bebd

zigbee.0
2025-07-12 09:45:18.985	debug	value generated '0' from device 804b50fffea8bebd for 'Link quality'

zigbee.0
2025-07-12 09:45:18.985	debug	message received '{"linkquality":0}' from device 804b50fffea8bebd type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:18.985	debug	No value published for device 804b50fffea8bebd

zigbee.0
2025-07-12 09:45:18.985	debug	value generated 'false' from device 804b50fffea8bebd for 'Available'

zigbee.0
2025-07-12 09:45:18.985	debug	message received '{"available":false}' from device 804b50fffea8bebd type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:18.985	debug	DeviceAvailability:Publish LQ for 0x804b50fffea8bebd = 0

zigbee.0
2025-07-12 09:45:18.985	debug	DeviceAvailability:Publish available for 0x804b50fffea8bebd = false

zigbee.0
2025-07-12 09:45:18.984	info	Failed to ping 0x804b50fffea8bebd TRADFRI bulb GU10 WS 400lm

zigbee.0
2025-07-12 09:45:18.532	debug	No value published for device d0cf5efffeeedcb2

zigbee.0
2025-07-12 09:45:18.531	debug	value generated '0' from device d0cf5efffeeedcb2 for 'Link quality'

zigbee.0
2025-07-12 09:45:18.530	debug	message received '{"linkquality":0}' from device d0cf5efffeeedcb2 type 'LED1537R6/LED1739R5'

zigbee.0
2025-07-12 09:45:18.530	debug	No value published for device d0cf5efffeeedcb2

                                        @arteck sagte in Tester Zigbee Adapter 3.x gesucht:

                                        doch war schon immer so.. wir hatten da keinen reconnect..
                                        meistens war das problem mit den coordinatoren die per WLAN angebunden waren

                                        Wäre falls man das erkennen kann eine praktische Sache.

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          MeisterQ 0 last edited by

                                          @Asgothian

                                          Kannst du mir einen groben Überblick geben, wo sich der Zigbee Adapter und zigbee2mqtt unterscheiden? Ist es nur die Visualisierung, ist es das Managen vom Netzwerk? etc?

                                          Danke.

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

                                            @meisterq-0 auch wenn ich nicht @Asgothian bin

                                            Beim Zigbee Adapter brauchst du nicht noch eine weitere Ebene in Form eibes MQTT Brokers (und eines MQTT Clients.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            852
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            zigbee zigbee adapter
                                            25
                                            222
                                            11856
                                            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