Tester Zigbee Adapter 3.x gesucht

Asgothian

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

Hadebe

@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

Eduard77

@asgothian
Vielen Dank für Hilfe,
mit Github Version konnte ich jetzt 2 Geräte einbinden, die vorher nicht funktioniert haben.

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.

David G.

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

@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.

arteck

@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

David G.

@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.

MeisterQ 0

@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

@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.

MeisterQ 0

@homoran Danke.

Wer übernimmt in dem Fall das Managen des Netzwerks? Der Zigbee Adapter, Zigbee2Mqtt oder der Koordinator, sodass die "Qualität" und die "Stabilität" des Netzwerkes von der Software auf dem Stick abhängen? Visualisieren die Adapter nur das, was die Software auf dem Stick macht?

Die Zusammenhänge sind mir nicht ganz klar.

Asgothian

@meisterq-0 die Steuerung des Netzwerkes ist grundsätzlich immer vom Koordinator geleistet. Die Abbildung der Geräte in der Client Software wird generell immer über die bibliotheken zigbee-herdsman (ZH) und Zigbee-Herdsman-converters (ZHC) geregelt. Das ist sowohl beim zigbee Adapter als auch bei zigbee2mqtt der Fall.
Einzig die Anbindung an den Kontokorrent läuft unterschiedlich, beim ZigbeeAdapter geht das direkt bei zigbee2mqtt muss entweder mqtt oder ein weiterer Adapter diese Anbindung machen.
Aus technischen Gründen ist der Zigbee Adapter bei neuen Geräten oft etwas langsamer was die Unterstützung angeht, da die ZHC erst auf Kompatibilität geprüft werden müssen.

A.

MeisterQ 0

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

@meisterq-0 die Steuerung des Netzwerkes ist grundsätzlich immer vom Koordinator geleistet. Die Abbildung der Geräte in der Client Software wird generell immer über die bibliotheken zigbee-herdsman (ZH) und Zigbee-Herdsman-converters (ZHC) geregelt. Das ist sowohl beim zigbee Adapter als auch bei zigbee2mqtt der Fall.
Aus technischen Gründen ist der Zigbee Adapter bei neuen Geräten oft etwas langsamer was die Unterstützung angeht, da die ZHC erst auf Kompatibilität geprüft werden müssen.

A.

Also läuft der Zigbee Adapter auch auf Basis des zigbee-herdsman von koenkk habe ich so verstanden?

Einzig die Anbindung an den Kontokorrent läuft unterschiedlich, beim ZigbeeAdapter geht das direkt bei zigbee2mqtt muss entweder mqtt oder ein weiterer Adapter diese Anbindung machen.

Der Zigbee Adapter "wandelt" also die Daten vom Zigbee Stick "direkt" um und schreibt sie in Datenpunkte? Er übernimmt da keinerlei "Steuerung" vom Netzwerk oder ähnliches?

Und z2m macht diese Umwandlung der Daten erst "in MQTT Nachrichten" welche dann wieder verarbeitet werden müssen?

Homoran

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

Also läuft der Zigbee Adapter auch auf Basis des zigbee-herdsman von koenkk

ja!

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

Der Zigbee Adapter "wandelt" also die Daten vom Zigbee Stick "direkt" um und schreibt sie in Datenpunkte?

ja!

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

Und z2m macht diese Umwandlung der Daten erst "in MQTT Nachrichten" welche dann wieder verarbeitet werden müssen?

ja

Asgothian

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

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

Und z2m macht diese Umwandlung der Daten erst "in MQTT Nachrichten" welche dann wieder verarbeitet werden müssen?

ja

Jein.

Bei z2m gibt es 2 Optionen:

Umwandlung in MQTT - die dann im iobroker über einen MQTT Client / Broker in datenpunkte umwandeln (fast alle steuernden datenpunkte müssen da manuell angelegt werden, nur die meldenden datenpunkte erzeugt MQTT selbstständig!!)
Nutzung des Adapters iobroker.zigbee2mqtt. Dieser kommuniziert direkt (ohne MQTT) mit z2m und erzeugt die Datenpunkte für die Geräte automatisch.

MeisterQ 0

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

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

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

Und z2m macht diese Umwandlung der Daten erst "in MQTT Nachrichten" welche dann wieder verarbeitet werden müssen?

ja

Jein.

Bei z2m gibt es 2 Optionen:

Umwandlung in MQTT - die dann im iobroker über einen MQTT Client / Broker in datenpunkte umwandeln (fast alle steuernden datenpunkte müssen da manuell angelegt werden, nur die meldenden datenpunkte erzeugt MQTT selbstständig!!)

Nutzung des Adapters iobroker.zigbee2mqtt. Dieser kommuniziert direkt (ohne MQTT) mit z2m und erzeugt die Datenpunkte für die Geräte automatisch.

Das bestärkt mich noch mals, direkt beim Zigbee Adapter zu bleiben und nicht auf zigbee2mqtt (Und dem Adapter) zu wechseln, weil ich da (durch deinen Latest_ZHC Link) aktuell keine Nachteile sehe, AUSSER, dass ich selber keine Konfigurationsdatei von unbekannten Geräten erzeugen kann. Danke!

Homoran

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

AUSSER, dass ich selber keine Konfigurationsdatei von unbekannten Geräten erzeugen kann

wieso nicht?
du kannst zusätzliche Konverter einbinden

MeisterQ 0

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

@meisterq-0 sagte in Tester Zigbee Adapter 3.x gesucht:

AUSSER, dass ich selber keine Konfigurationsdatei von unbekannten Geräten erzeugen kann

wieso nicht?
du kannst zusätzliche Konverter einbinden

Ja ich weiß. Das ist ja mit Version 3.x auch sehr gut geworden.

Ich meine aber, dass du bei z2m ein Unbekanntes Gerät koppeln kannst, dann kannst du davon eine Datei erzeugen mit den Clustern, mit dieser ein Issue bei ZHC aufmachen, und dann können sie eingepflegt werden.

Beim Adapter kannst du klar einfach einen externen Konverter erstellen und hast den Support sofort.

MeisterQ 0

@Asgothian

zigbee.0
	2025-07-16 22:28:20.222	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0
	2025-07-16 22:28:19.606	info	Closing Zigbee network, 0 seconds remaining
zigbee.0
	2025-07-16 22:28:19.223	info	Saved local configuration data
zigbee.0
	2025-07-16 22:28:19.222	info	cleaning everything up...
zigbee.0
	2025-07-16 22:28:19.222	info	Halting zigbee adapter. Restart delay is at least 30 seconds.
zigbee.0
	2025-07-16 22:28:19.219	error	Cannot read properties of undefined (reading 'icon')
zigbee.0
	2025-07-16 22:28:19.219	error	TypeError: Cannot read properties of undefined (reading 'icon') at StatesController.AddModelFromHerdsman (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:97:43) at processTicksAndRejections (node:internal/process/task_queues:95:5)
zigbee.0
	2025-07-16 22:28:19.218	error	unhandled promise rejection: Cannot read properties of undefined (reading 'icon')
zigbee.0
	2025-07-16 22:28:19.218	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
zigbee.0
	2025-07-16 22:28:19.211	error	Cannot read properties of undefined (reading 'icon')
zigbee.0
	2025-07-16 22:28:19.211	error	TypeError: Cannot read properties of undefined (reading 'icon') at StatesController.AddModelFromHerdsman (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:97:43) at processTicksAndRejections (node:internal/process/task_queues:95:5)
zigbee.0
	2025-07-16 22:28:19.210	error	unhandled promise rejection: Cannot read properties of undefined (reading 'icon')
zigbee.0
	2025-07-16 22:28:19.210	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
zigbee.0
	2025-07-16 22:28:19.210	warn	New device: '0x744dbdfffe61ce69' does not have a known model. please provide an external converter for 'ZBColorLightBulb'.
zigbee.0
	2025-07-16 22:28:19.209	info	Device '0x744dbdfffe61ce69' announced itself

Wenn ich mit 3.0.2 Geräte anlerne die er nicht kennt, crashed der Adapter.

haselchen

@Asgothian
@arteck

Kurioses Ding:
Also, in einem Thread von mir haben wir über BWM aus China philosophiert.

Die gibt es bei Ali ja zuhauf.
Hab zig davon bestellt und eingebunden.
Nun habe ich , wo ich auch vorher bestellt habe, noch 2 nachgeordert.

Und die weigern sich auf merkwürdige Art und Weise.
Wenn ich das richtig verglichen habe , unterscheiden sie sich im "Manufactur" Teil.

Eingebunden:

Bei den Neuen steht bei manufacturer HOBEIAN

Bei Zigbee2MQTT wird er unterstützt (von der Seite habe ich den Screenshot)

Klar kann man nun auch sagen, dass die Bezeichnung abweicht.
ZG-204ZL und der Andere ZG-204ZL.

Der Zigbee Adapter erkennt im 2. Anlauf den BWM als ZG-204ZL.
Erscheint auch als Kachel.

Aber er reagiert nicht. Es aktualisiert sich nichts.
Im Log steht "Interview failed".
Trotzdem erscheint die Kachel.

Von gestern:

2025-07-16 23:51:51.010 - info: zigbee.0 (645) Zigbee: allowing new devices to join.
2025-07-16 23:52:00.417 - info: zigbee.0 (645) Starting interview of '0xa4c1382e027c309b'
2025-07-16 23:52:00.929 - info: zigbee.0 (645) Device '0xa4c1382e027c309b' announced itself
2025-07-16 23:52:22.076 - info: zigbee.0 (645) Device '0xa4c1382e027c309b' announced itself
2025-07-16 23:52:34.478 - error: zigbee.0 (645) Failed to interview '0xa4c1382e027c309b', device has not successfully been paired. Try again !!!!!!!!!!
2025-07-16 23:52:52.234 - info: zigbee.0 (645) Zigbee: stop joining

Aktuell:

New device joined '0xa4c1382e027c309b' model ZG-204ZL
Device '0xa4c1382e027c309b' announced itself
Pairing time left: 57
Interview started: 0xa4c1382e027c309b

Trotzdem kommt dann diese Meldung am Ende:

Interview failed: 0xa4c1382e027c309b
Error: Failed to interview '0xa4c1382e027c309b', device has not successfully been paired. Try again !!!!!!!!!! . undefined

zigbee.0 2025-07-17 13:49:08.629	info	Device 0xa4c1382e027c309b "undefined" not present in statesMapping - relying on exposes for device definition.

Lange Rede und Unsinn, wie bekomme ich den nun integriert?

NEWS

Tester Zigbee Adapter 3.x gesucht

Support us

737

32.4k

81.4k

1.3m