Tester wanted - Zigbee Adapter 3.1

Asgothian

@latzi sagte in Tester wanted - Zigbee Adapter 3.1:

@asgothian
ich hab auf 3.1.2 (von 3.0.5) umgestellt, folgende Meldungen kamen:

Der Moes Rauchmelder wird mit warn erwähnt:

2025-09-18 18:00:11.803 - warn: zigbee.0 (742748) DeviceConfigure:0xa4c138421ad10f21 TS0601 Failed to configure. --> ZCL command 0xa4c138421ad10f21/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: ZDO - extRouteDisc - {"dstAddr":794,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))

und folgende Meldung kommt mehrfach:
2025-09-18 18:20:33.064 - warn: zigbee.0 (742748) Resolve Entity did not manage to find a mapped device for [object Object]
Bei der Meldung
2025-09-18 18:02:37.041 - warn: zigbee.0 (742748) resolve_entity failed for {"kind":"ieee","key":"0x0x00124b0018eb432d","message":"success"}
verstehe ich die Adresse 0x0x00124b0018eb432d nicht, hab ich nicht in meinen Objekten.

Muss ich mir Gedanken darüber machen?

Die beiden Meldungen sind erst einmal egal - die Addresse ist die deines Koordinators.

Schlechter ist das Ergebnis '(0xc7: NWK_TABLE_FULL)'. es bedeutet das du zuviel traffic im Zigbee Netz hast. Lass das Netz erst einmal zur Ruhe kommen (30 Minuten) und versuch dann den Rauchmelder neu zu konfigurieren

A.

Flugschüler

Ich habe einen tuya 2CT Energiezähler. Mit ZigBee adapter 3.1.2 werden die datenpunkte power_a und power_b nicht aktualisiert.

Asgothian

@flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

Ich habe einen tuya 2CT Energiezähler. Mit ZigBee adapter 3.1.2 werden die datenpunkte power_a und power_b nicht aktualisiert.

Schritt 1: Gerät über die Kachel neu konfigurieren. Entweder es geht danach oder nicht.

Wenn nicht: Schritt 2

Bitte folgendes machen (mit der 3.0.1 installiert)

Debug für dein betroffenes Gerät aktivieren
Warten bis die gewünschten Datenpunkte aktualisiert werden.
Im Log nach 'ELEVATED (abcd)' Warn-Meldungen schauen. Diese hier Posten. Dabei bitte die Meldungen nicht rein chronologisch sondern sortiert nach der 4-Stelligen Hex Zahl in Gruppen posten (Als Text, in Code Tags, in einzelnen Gruppen mit jeweils nur einer ID)
Adapter anhalten
Adapter auf 3.1.2 aktualisieren
Adapter starten
Wieder nach den 'ELEVATED' Nachrichten schauen - Wichtig ist das dabei hinreichend Zeit vergeht das die Datenpunkte aktualisiert sein sollte. Diese wieder wie oben gruppiert als Text in Code-Tags posten.
device_query triggern
Wieder nach neuen 'ELEVATED' Nachrichten schauen.
Diese wieder wie oben gruppiert als Text in Code-Tags posten.
Gerät über die Kachel neu konfigurieren
Abwarten ob load_power aktualisiert wird.
Wieder nach neuen 'ELEVATED' Nachrichten schauen - Wichtig ist das dabei hinreichend Zeit vergeht das Load_Power aktualisiert sein sollte. Diese wieder wie oben gruppiert als Text in Code-Tags posten.

Bitte stell sicher das die Logs korrekt in Multiline Code tags gekapselt sind. Ansonsten sind sie unleserlich.

Da ich keine entsprechendes Gerät habe kann ich diesem Effekt ohne diese Daten nicht nachgehen. Ich kann den Effekt nicht nachstellen.

A.

Beispiel für korrekt formatierte und sortierte Log Meldungen:

warn: zigbee.0 (534432) ELEVATED:O01 (e57d) User state change of state zigbee.0.187a3efffe39a49e.send_payload with value { "cyclic_timed_irrigation": { "total_number": 1, "irrigation_duration": 60 } } (ack: false) from system.adapter.scenes.0
warn: zigbee.0 (534432) ELEVATED:O02 (e57d) Change state 'send_payload' at device 0x187a3efffe39a49e type 'SWV'
warn: zigbee.0 (534432) ELEVATED:O03 (e57d) Publishing to 0x187a3efffe39a49e of model SWV with send_payload

warn: zigbee.0 (534432) ELEVATED:O03 (e5a8) Publishing to 0x187a3efffe39a49e of model SWV with cyclic_timed_irrigation
warn: zigbee.0 (534432) ELEVATED:O04 (e5a8) convert cyclic_timed_irrigation, {"total_number":1,"irrigation_duration":60}, {} for device 0x187a3efffe39a49e with Endpoint cyclic_timed_irrigation
warn: zigbee.0 (534432) ELEVATED:SUCCESS (e5a8) convert result {"state":{"cyclic_timed_irrigation":{"total_number":1,"irrigation_duration":60}}} for device 0x187a3efffe39a49e

warn: zigbee.0 (534432) ELEVATED:I01 (eb01) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20489":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":125,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
warn: zigbee.0 (534432) ELEVATED:I01 (eb01) message received '{"linkquality":36}' from device 187a3efffe39a49e type 'SWV'
warn: zigbee.0 (534432) ELEVATED:I02 (eb01) value generated '36' from device 187a3efffe39a49e for 'Link quality'

warn: zigbee.0 (534432) ELEVATED:I01 (eb18) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20488":"\u0001\u0001\u0000\u0000\u0000<\u0000\u0000\u0000\u0000"},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":126,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

warn: zigbee.0 (534432) ELEVATED:I01 (eb20) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20486":0,"20487":0,"20493":1758225028,"20496":1},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

Flugschüler

ELEVATED:I01 (eb06) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb06) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (eb06) message received '{"power":0}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb06) value generated '0' from device a4c13886e50d0115 for 'Load power'

ELEVATED:I01 (eb30) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb30) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (eb30) message received '{"current_a":0}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb30) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured electrical current (phase A)'

ELEVATED:I01 (eb59) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb59) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (eb59) message received '{"current_b":0}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb59) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured electrical current (phase B)'
ELEVATED:I01 (eb59) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37120,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (eb83) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb83) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (eb83) message received '{"power_a":0}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (eb83) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured power (phase A)'
ELEVATED:I01 (eb83) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37376,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (ebad) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (ebad) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (ebad) message received '{"power_b":0}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (ebad) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured power (phase B)'
ELEVATED:I01 (ebad) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37632,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (ebd5) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (ebd5) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (ebd5) message received '{}' from device a4c13886e50d0115 type '2CT'
ELEVATED:NOVAL (ebd5) No value published for device a4c13886e50d0115
ELEVATED:I01 (ebd5) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37888,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

ELEVATED:I01 (ebff) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (ebff) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (ebff) message received '{}' from device a4c13886e50d0115 type '2CT'
ELEVATED:NOVAL (ebff) No value published for device a4c13886e50d0115
ELEVATED:I01 (ebff) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":38144,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

Flugschüler

@asgothian Ist das so richtig? Dann sende ich die daten vom neuen zigbee adapter.

ELEVATED:I01 (1430) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (1430) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (1430) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":31744,"dpValues":[{"dp":19,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (145b) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (145b) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (145b) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32000,"dpValues":[{"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (1495) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (1495) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (1495) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32256,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (14c3) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (14c3) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (14c3) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32512,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (14f4) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (14f4) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (14f4) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32768,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (151f) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (151f) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (151f) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":33024,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

ELEVATED:I01 (154a) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (154a) value generated '69' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (154a) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":33280,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

Fabio

Guten morgen @asgothian ,

weißt du was hier paasiert das hatte ich noch nie:

host.nuc
2025-09-19 07:50:54.252	info	Restart adapter system.adapter.zigbee.1 because enabled

host.nuc
2025-09-19 07:50:54.252	error	instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_hs.saturation

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_hs.hue

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.b

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.g

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.r

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_xy.y

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_xy.x

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for hex_color

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for colortemp_move

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for colortemp

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[5]: at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:647:39)

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'group_1')

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[5]: 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(). The promise rejected with the reason:

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_hs.saturation

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_hs.hue

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.b

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.g

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.r

host.nuc
2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_xy.y

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for color_xy.x

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for color

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for hex_color

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for colortemp_move

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for colortemp

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[3]: at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:649:56)

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[3]: TypeError: Cannot set properties of undefined (setting 'stateupdate')

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[3]: 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(). The promise rejected with the reason:

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[2]: [2025-09-19T05:50:51.203Z] zh:zstack:znp: Socket error Error: read ECONNRESET

host.nuc
2025-09-19 07:50:54.251	error	Caught by controller[1]: [2025-09-19T05:50:51.202Z] zh:zstack:znp: Socket error Error: read ECONNRESET

zigbee.1
2025-09-19 07:50:53.671	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining

zigbee.1
2025-09-19 07:50:52.854	error	Cannot read properties of undefined (reading 'group_1')

zigbee.1
2025-09-19 07:50:52.854	error	TypeError: Cannot read properties of undefined (reading 'group_1') at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:647:39)

zigbee.1
2025-09-19 07:50:52.854	error	unhandled promise rejection: Cannot read properties of undefined (reading 'group_1')

zigbee.1
2025-09-19 07:50:52.854	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.1
2025-09-19 07:50:52.671	info	Saved local configuration data

zigbee.1
2025-09-19 07:50:52.670	info	cleaning everything up...

zigbee.1
2025-09-19 07:50:52.670	info	Halting zigbee adapter. Restart delay is at least 30 seconds.

zigbee.1
2025-09-19 07:50:52.604	error	Cannot set properties of undefined (setting 'stateupdate')

zigbee.1
2025-09-19 07:50:52.604	error	TypeError: Cannot set properties of undefined (setting 'stateupdate') at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:649:56)

zigbee.1
2025-09-19 07:50:52.604	error	unhandled promise rejection: Cannot set properties of undefined (setting 'stateupdate')

zigbee.1
2025-09-19 07:50:52.604	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().

fabio error zigbe.txt

Asgothian

@fabio Wahrscheinlich hast du nicht beachtet das der Adapter 30 Sekunden zwischen stop und start wartet.

Wenn man

den Adapter anhält
den Adapter sofort wieder startet
und dann, weil er nicht sofort zu starten scheint das nochmal widerholt

dann passiert so etwas.

Ich hatte mal einen Issue dazu aufgemacht - den muss ich aber raus suchen. Das ist fast ein Jahr her, und es ist nichts passiert. Das Problem liegt im js-controller oder im Kern des ioBroker, der zwar zulässt das man eine Zeit definiert, diese aber auf der Oberfläche nicht visualisiert. Ebenso wartet er nicht nach dem Stop Befehl an den Adapter bis dieser auch wirklich angehalten ist. Da gibt es einen internen Timeout, der auch dann den Adapter als gestoppt anzeigt wenn dieser den Stop-Befehl noch bearbeitet.

Betroffen ist der Zigbee Adapter davon, weil es insbesondere bei den LAN Koordinatoren teilweise bis zu 30 s dauert bis der Adapter angehalten wurde, weil Daten vom Koordinator abgefragt werden.

A.

Fabio

@asgothian lieben Dank für die Info.

Aber ich habe den Adapter weder gestoppt noch gestartet das lief alles von alleine. Und das hatte ich so vor der Version 3.1.2 noch nie.

Herzliche Grüße
Fabio

Asgothian

@flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

Ist das so richtig? Dann sende ich die daten vom neuen zigbee adapter.

Fast - was ich nicht erkennen kann: welche der Meldungen sind die Reaktionen auf ein 'Device Query', insbesondere beim neuen Adapter.

A.

Asgothian

@fabio sagte in Tester wanted - Zigbee Adapter 3.1:

@asgothian lieben Dank für die Info.

Aber ich habe den Adapter weder gestoppt noch gestartet das lief alles von alleine. Und das hatte ich so vor der Version 3.1.2 noch nie.

Herzliche Grüße
Fabio

Wer den Adapter neu gestartet hat kann ich Dir nicht sagen. Das log zeigt deutlich das die Instanz zigbee.1 das Zigbee Netzwerk 2 mal startet.

Das wäre zu beobachten. So einen Effekt hatte ich bei mir bisher nie.

A.

Flugschüler

@asgothian

ELEVATED:I01 (1fea) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (1fea) value generated '76' from device a4c13886e50d0115 for 'Link quality'

ELEVATED:O01 (24b0) User state change of state zigbee.0.a4c13886e50d0115.device_query with value true (ack: false) from system.adapter.admin.0  
ELEVATED:O02 (24b0) Change state 'device_query' at device 0xa4c13886e50d0115 type '2CT'  
ELEVATED:Oqs (24b0) Device query for '0xa4c13886e50d0115/1' triggered  
ELEVATED:Oqe (24b0) ELEVATED O07: Device query for '0xa4c13886e50d0115/1' complete

ELEVATED:I01 (34df) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (34df) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (34df) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10240,"dpValues":[{"dp":20,"datatype":2,"data":{"type":"Buffer","data":[0,0,8,166]}}]}...}

ELEVATED:I01 (3516) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (3516) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (3516) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10496,"dpValues":[{"dp":19,"datatype":2,"data":{"type":"Buffer","data":[0,0,18,226]}}]}...}

ELEVATED:I01 (354e) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (354e) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (354e) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10752,"dpValues":[{"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (3587) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (3587) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (3587) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11008,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,21,89]}}]}...}

ELEVATED:I01 (35bd) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (35bd) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (35bd) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11264,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (35f2) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (35f2) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (35f2) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11520,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,18,226]}}]}...}

ELEVATED:I01 (3628) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (3628) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (3628) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11776,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

ELEVATED:I01 (365f) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (365f) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (365f) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":12032,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

Asgothian

@flugschüler wurden in diesem Fall die fraglichen Werte aktualisiert ?

Flugschüler

@asgothian Wenn du die datenpunkte meinst es wurde nichts aktuallisiert.

Codierknecht

Ich erhalte in unregelmäßigen Abständen folgende Einträge im Log:

zigbee.0    2025-09-19 12:28:54.929	warn	Resolve Entity did not manage to find a mapped device for [object Object]
zigbee.0    2025-09-19 12:24:38.716	warn	Resolve Entity did not manage to find a mapped device for [object Object]
zigbee.0    2025-09-19 12:22:01.497	warn	Resolve Entity did not manage to find a mapped device for [object Object]

Fehlt da evtl. ein JSON.stringify() ?

Und by the way: Beim "reconfigure" eines Device müsste es korrekt heißen: "Device is being reconfigured"

Asgothian

@flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

@asgothian Wenn du die datenpunkte meinst es wurde nichts aktuallisiert.

Muss eigentlich. Schau mal bitte bei dem DP current_b nach wann der das letzte mal aktualisiert wurde.

Alternativ: Installier mal bitte vom iobroker GitHub die 3.1.2 - da sind kleinere Bugfixes beim Logging enthalten- und wiederhol dann bitte die Tests mit der 3.1.2 (abwarten, sowie device query)

A.

Asgothian

@codierknecht sagte in Tester wanted - Zigbee Adapter 3.1:

Ich erhalte in unregelmäßigen Abständen folgende Einträge im Log:

zigbee.0    2025-09-19 12:28:54.929	warn	Resolve Entity did not manage to find a mapped device for [object Object]
zigbee.0    2025-09-19 12:24:38.716	warn	Resolve Entity did not manage to find a mapped device for [object Object]
zigbee.0    2025-09-19 12:22:01.497	warn	Resolve Entity did not manage to find a mapped device for [object Object]

Fehlt da evtl. ein JSON.stringify() ?

Danke für den Hinweis - ist gefixed in der 3.1.2 auf Github - die Meldung kommt nur. noch wenn sie wirklich benötigt wird.

Das sprachliche hab ich gerade lokal geändert - wird also in 3.1.3 gefixed sein

A.

Nachtrag: die Meldungen kommen weil er versucht, die device definition für den Koordinator zu finden. Der hat aber keine :). Das filter ich in der Github Version raus - also keine Meldungen mehr.

JLeg

@asgothian ...being on that... ;) - Adapter 3.1.2, bei den umgedrehten Kacheln kickt der "Raumname" bei entsprechender Länge ein Icon weg:

Ansonsten läuft 3.1.2 sehr gut bei mir, ohne Auffälligkeiten...

Flugschüler

@asgothian Ich hab jetzt geschaut was wann aktuallisiert wird und das einzige was aktuallisiert wird ist Link quality und Message from Zigbee bei Adapter 3.1.2 über git installiert. Bei Adapter 3.0.5 funktioniert alles prima.

Asgothian

@flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

@asgothian Ich hab jetzt geschaut was wann aktuallisiert wird und das einzige was aktuallisiert wird ist Link quality und Message from Zigbee bei Adapter 3.1.2 über git installiert. Bei Adapter 3.0.5 funktioniert alles prima.

Das wissen wir schon. Ich brauch die Meldungen, um zu sehen wo das hängen bleibt. Alternativ - ein Gerät damit ich das selber Debuggen kann.

Ansonsten wirst du auf 3.0.5 bleiben müssen und von der Unterstützung von neuen Geräten abgeschnitten. Die Änderung / Ursache liegt in einer Änderung der ZH/ZHC Bibliotheken. Ohne mithilfe werde ich das nicht finden, und ohne Wechsel auf diese Bibliotheken werden neue Geräte nicht funktionieren.

A.
Und nein - ich werde mir keins kaufen. Ich steck da schon reichlich Freizeit rein - ich werd jetzt nicht auch noch Geld versenken in Geräte die ich nicht gebrauchen kann.

Flugschüler

@asgothian

ELEVATED:I01 (b0bd) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b0bd) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b0bd) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":24064,"dpValues":[{"dp":20,"datatype":2,"data":{"type":"Buffer","data":[0,0,8,205]}}]}...}

ELEVATED:I01 (b0e8) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b0e8) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b0e8) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":24320,"dpValues":[{"dp":19,"datatype":2,"data":{"type":"Buffer","data":[0,0,19,161]}}]}...}

ELEVATED:I01 (b113) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b113) value generated '72' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b113) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":24576,"dpValues":[{"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (b13c) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b13c) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b13c) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":24832,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,21,196]}}]}...}

ELEVATED:I01 (b166) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b166) value generated '80' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b166) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":25088,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}

ELEVATED:I01 (b19a) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b19a) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b19a) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":25344,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,19,161]}}]}...}

ELEVATED:I01 (b1cf) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b1cf) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b1cf) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":25600,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

ELEVATED:I01 (b1f9) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (b1f9) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (b1f9) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":25856,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}

ELEVATED:I01 (9975) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (9975) value generated '72' from device a4c13886e50d0115 for 'Link quality'

ELEVATED:I01 (999e) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
ELEVATED:I02 (999e) value generated '76' from device a4c13886e50d0115 for 'Link quality'
ELEVATED:I01 (999e) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":22784,"dpValues":[{"dp":117,"datatype":2,"data":{"type":"Buffer","data":[0,0,161,211]}}]}...}

ELEVATED:O01 (a68b) User state change of state zigbee.0.a4c13886e50d0115.device_query with value true (ack: false) from system.adapter.admin.0  
ELEVATED:O02 (a68b) Change state 'device_query' at device 0xa4c13886e50d0115 type '2CT'  
ELEVATED:Oqs (a68b) Device query for '0xa4c13886e50d0115/1' triggered  
ELEVATED:Oqe (a68b) ELEVATED O07: Device query for '0xa4c13886e50d0115/1' complete

Du musst dir sicher das Gerät nicht kaufen. Ich würde mir auch nicht ein gerät kaufen das ich nicht brauche. Ich bin ja froh und dankbar wenn du mir hilfst. Aber ich bin nur ein leihe und kein programmierer ich hoffe die logs bringen dir irgend etwas. Danke!

Community Forum

NEWS

Tester wanted - Zigbee Adapter 3.1

Support us

807

32.4k

81.5k

1.3m