UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Fabio]

Hallo @asgothian ich habe ein kleines Problem.

ZigBee Adapter übergibt Geräte an den Matter Adapter über die Bridge Funktion.
Die ZigBee Geräte werden dann in der Apple Home App angezeigt und können von dort geschaltet werden etc.
Seid der Version 3.2.5 passiert folgendes. Geräte werden auf einmal als An in der App angezeigt, sie sind es aber nicht. Die Datenpunkte stehen auf falsch. Es betrifft auch nicht alle Geräte. Ich habe dann im Zigbee Adapter ein Gerät auf Debug gestellt.
Und in dem Moment wo das im Log auftauchte wurde das Gerät als an AN in der App angezeigt siehe bitte hier:

zigbee.1
2025-11-03 10:35:37.988	warn	ELEVATED:I04 (7600) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:35:37.988	warn	ELEVATED:I03 (7600) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:35:37.988	warn	ELEVATED:NOCONV (7600) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:35:37.987	warn	ELEVATED:I02 (7600) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:35:37.985	warn	ELEVATED:I04 (7601) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:35:37.985	warn	ELEVATED:I03 (7601) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:35:37.984	warn	ELEVATED:I01 (7600) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,7,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":7,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:34:11.352	info	debug devices set to ["a4c1389893367f90"]

als ich dann in der App geschaltet habe kommt das Log und ich denke das ist so richtig:

zigbee.1
2025-11-03 10:46:27.174	warn	ELEVATED:I04 (5de4) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:46:27.174	warn	ELEVATED:I03 (5de4) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:46:27.174	warn	ELEVATED:NOCONV (5de4) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:46:27.174	warn	ELEVATED:I02 (5de4) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:46:27.173	warn	ELEVATED:I04 (5de5) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:46:27.173	warn	ELEVATED:I03 (5de5) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:46:27.172	warn	ELEVATED:I01 (5de4) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,15,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":15,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:45:09.660	warn	ELEVATED:I04 (2f19) value generated 'false' from device a4c1389893367f90 for 'On/off state of the switch'

zigbee.1
2025-11-03 10:45:09.660	warn	ELEVATED:I03 (2f19) message received '{"state":"OFF"}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:09.660	warn	ELEVATED:I02.2c (2f19) candidates: [{"state":"OFF"},{}] => payload {"state":"OFF"}

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I02.1b (2f19) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:undefined

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I02.2a (2f19) converter 2 : Cluster genOnOff

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I02.0b (2f19) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:{"state":"OFF"}

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I02.1a (2f19) converter 1 : Cluster genOnOff

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I04 (2f19) value generated '131' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I03 (2f19) message received '{"linkquality":131}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:09.659	warn	ELEVATED:I02 (2f19) 2 converters available for 'B1Z' 'a4c1389893367f90' with cluster 'genOnOff' and type 'attributeReport'

zigbee.1
2025-11-03 10:45:09.657	warn	ELEVATED:I01 (2f19) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"onOff":0},"linkquality":131,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[8,14,10,0,0,16,0]},"zclTransactionSequenceNumber":14,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I04 (2362) value generated 'false' from device a4c1389893367f90 for 'On/off state of the switch'

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I03 (2362) message received '{"state":"OFF"}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I02.2c (2362) candidates: [{"state":"OFF"},{}] => payload {"state":"OFF"}

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I02.1b (2362) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:undefined

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I02.2a (2362) converter 2 : Cluster genOnOff

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I02.0b (2362) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:{"state":"OFF"}

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I02.1a (2362) converter 1 : Cluster genOnOff

zigbee.1
2025-11-03 10:45:06.660	warn	ELEVATED:I04 (2362) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:45:06.659	warn	ELEVATED:I03 (2362) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:06.659	warn	ELEVATED:I02 (2362) 2 converters available for 'B1Z' 'a4c1389893367f90' with cluster 'genOnOff' and type 'attributeReport'

zigbee.1
2025-11-03 10:45:06.658	warn	ELEVATED:I04 (2362) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:45:06.658	warn	ELEVATED:I03 (2362) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:06.658	warn	ELEVATED:I01 (2362) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"onOff":0},"linkquality":127,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[24,13,10,0,0,16,0]},"zclTransactionSequenceNumber":13,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:45:06.658	warn	ELEVATED:SUCCESS (232f) convert result {"state":{"state":"OFF"}} for device 0xa4c1389893367f90

zigbee.1
2025-11-03 10:45:06.609	warn	ELEVATED:O04 (232f) convert state with value "OFF" and options {} for device 0xa4c1389893367f90 with Endpoint state

zigbee.1
2025-11-03 10:45:06.608	warn	ELEVATED:O03 (232f) Publishing to 0xa4c1389893367f90 of model B1Z with state

zigbee.1
2025-11-03 10:45:06.608	warn	ELEVATED:O02 (232f) Change state 'state' at device 0xa4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:45:06.607	warn	ELEVATED:O01 (232f) User state change of state zigbee.1.a4c1389893367f90.state with value false (ack: false) from system.adapter.matter.0

zigbee.1
2025-11-03 10:43:50.368	warn	ELEVATED:I04 (f95f) value generated '131' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:43:50.368	warn	ELEVATED:I03 (f95f) message received '{"linkquality":131}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:43:50.368	warn	ELEVATED:NOCONV (f95f) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:43:50.368	warn	ELEVATED:I02 (f95f) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:43:50.367	warn	ELEVATED:I04 (f95f) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:43:50.367	warn	ELEVATED:I03 (f95f) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:43:50.367	warn	ELEVATED:I01 (f95f) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":131,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,12,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":12,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:41:15.338	warn	ELEVATED:I04 (9bc7) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:41:15.338	warn	ELEVATED:I03 (9bc7) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:41:15.338	warn	ELEVATED:NOCONV (9bc7) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:41:15.338	warn	ELEVATED:I02 (9bc7) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:41:15.336	warn	ELEVATED:I04 (9bc8) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:41:15.336	warn	ELEVATED:I03 (9bc8) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:41:15.335	warn	ELEVATED:I01 (9bc7) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,11,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":11,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:38:25.884	warn	ELEVATED:I04 (05d7) value generated '131' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:38:25.883	warn	ELEVATED:I03 (05d7) message received '{"linkquality":131}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:38:25.883	warn	ELEVATED:NOCONV (05d7) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:38:25.883	warn	ELEVATED:I02 (05d7) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:38:25.880	warn	ELEVATED:I04 (05d8) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:38:25.880	warn	ELEVATED:I03 (05d8) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:38:25.879	warn	ELEVATED:I01 (05d7) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":131,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,10,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":10,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I04 (bb3d) value generated 'false' from device a4c1389893367f90 for 'On/off state of the switch'

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I03 (bb3d) message received '{"state":"OFF"}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I02.2c (bb3d) candidates: [{"state":"OFF"},{}] => payload {"state":"OFF"}

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I02.1b (bb3d) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:undefined

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I02.2a (bb3d) converter 2 : Cluster genOnOff

zigbee.1
2025-11-03 10:37:01.247	warn	ELEVATED:I02.0b (bb3d) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:{"state":"OFF"}

zigbee.1
2025-11-03 10:37:01.246	warn	ELEVATED:I02.1a (bb3d) converter 1 : Cluster genOnOff

zigbee.1
2025-11-03 10:37:01.246	warn	ELEVATED:I04 (bb3d) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:37:01.246	warn	ELEVATED:I03 (bb3d) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:37:01.246	warn	ELEVATED:I02 (bb3d) 2 converters available for 'B1Z' 'a4c1389893367f90' with cluster 'genOnOff' and type 'attributeReport'

zigbee.1
2025-11-03 10:37:01.245	warn	ELEVATED:I01 (bb3d) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"onOff":0},"linkquality":127,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[8,9,10,0,0,16,0]},"zclTransactionSequenceNumber":9,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:36:58.251	warn	ELEVATED:I04 (af87) value generated 'false' from device a4c1389893367f90 for 'On/off state of the switch'

zigbee.1
2025-11-03 10:36:58.251	warn	ELEVATED:I03 (af87) message received '{"state":"OFF"}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:36:58.251	warn	ELEVATED:I02.2c (af87) candidates: [{"state":"OFF"},{}] => payload {"state":"OFF"}

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I02.1b (af87) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:undefined

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I02.2a (af87) converter 2 : Cluster genOnOff

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I02.0b (af87) data: {"onOff":0} options: {} meta:{"deviceIEEE":"0xa4c1389893367f90","logger":"StatesController","state":{"state":""}} result:{"state":"OFF"}

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I02.1a (af87) converter 1 : Cluster genOnOff

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I04 (af87) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I03 (af87) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:36:58.250	warn	ELEVATED:I02 (af87) 2 converters available for 'B1Z' 'a4c1389893367f90' with cluster 'genOnOff' and type 'attributeReport'

zigbee.1
2025-11-03 10:36:58.248	warn	ELEVATED:I04 (af88) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:36:58.248	warn	ELEVATED:I03 (af88) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:36:58.247	warn	ELEVATED:I01 (af87) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"onOff":0},"linkquality":127,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[24,8,10,0,0,16,0]},"zclTransactionSequenceNumber":8,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:36:58.246	warn	ELEVATED:SUCCESS (af52) convert result {"state":{"state":"OFF"}} for device 0xa4c1389893367f90

zigbee.1
2025-11-03 10:36:58.198	warn	ELEVATED:O04 (af52) convert state with value "OFF" and options {} for device 0xa4c1389893367f90 with Endpoint state

zigbee.1
2025-11-03 10:36:58.197	warn	ELEVATED:O03 (af52) Publishing to 0xa4c1389893367f90 of model B1Z with state

zigbee.1
2025-11-03 10:36:58.197	warn	ELEVATED:O02 (af52) Change state 'state' at device 0xa4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:36:58.194	warn	ELEVATED:O01 (af52) User state change of state zigbee.1.a4c1389893367f90.state with value false (ack: false) from system.adapter.matter.0

und hier dann wenn es sich wieder von alleine meldet. Dann wird auch wieder in der App angezeigt das es An ist was es aber nicht ist:

zigbee.1
2025-11-03 10:55:02.181	warn	ELEVATED:I04 (39a1) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:55:02.181	warn	ELEVATED:I03 (39a1) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:55:02.181	warn	ELEVATED:NOCONV (39a1) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:55:02.180	warn	ELEVATED:I02 (39a1) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:55:02.178	warn	ELEVATED:I04 (39a2) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:55:02.178	warn	ELEVATED:I03 (39a2) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:55:02.177	warn	ELEVATED:I01 (39a1) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,18,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":18,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:52:14.444	warn	ELEVATED:I04 (aa6a) value generated '131' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:52:14.444	warn	ELEVATED:I03 (aa6a) message received '{"linkquality":131}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:52:14.444	warn	ELEVATED:NOCONV (aa6a) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:52:14.444	warn	ELEVATED:I02 (aa6a) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:52:14.443	warn	ELEVATED:I04 (aa6b) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:52:14.443	warn	ELEVATED:I03 (aa6b) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:52:14.442	warn	ELEVATED:I01 (aa6a) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":131,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,17,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":17,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.1
2025-11-03 10:49:18.831	warn	ELEVATED:I04 (fc6c) value generated '127' from device a4c1389893367f90 for 'Link quality'

zigbee.1
2025-11-03 10:49:18.831	warn	ELEVATED:I03 (fc6c) message received '{"linkquality":127}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:49:18.831	warn	ELEVATED:NOCONV (fc6c) No converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:49:18.831	warn	ELEVATED:I02 (fc6c) 0 converter available for 'B1Z' 'a4c1389893367f90' with cluster 'genBasic' and type 'attributeReport'

zigbee.1
2025-11-03 10:49:18.829	warn	ELEVATED:I04 (fc6d) value generated 'true' from device a4c1389893367f90 for 'Available'

zigbee.1
2025-11-03 10:49:18.829	warn	ELEVATED:I03 (fc6d) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zigbee.1
2025-11-03 10:49:18.828	warn	ELEVATED:I01 (fc6c) Zigbee Event of Type attributeReport from device 0xa4c1389893367f90, incoming event: {"type":"attributeReport","data":{"65506":56,"65508":0,"appVersion":72},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"rawData":{"type":"Buffer","data":[8,16,10,1,0,32,72,226,255,32,56,228,255,32,0]},"zclTransactionSequenceNumber":16,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1

Hast du evtl. eine Idee was da schief läuft?
Kann es mit diese Zeilen

zigbee.1
2025-11-03 11:03:18.295 warn ELEVATED:I04 (cb97) value generated 'true' from device a4c1389893367f90 for 'Available'
zigbee.1
2025-11-03 11:03:18.295 warn ELEVATED:I03 (cb97) message received '{"available":true}' from device a4c1389893367f90 type 'B1Z'

zusammenhängen die ja eigentich nur da sind um zu zeigen ob da Gerät vorhanden Online ist. Nur komisch das die App dann in diesen Moment anzeigt das das Gerät AN ist.

Herzliche Grüße
Fabio

[Asgothian]

@fabio Du müsstest im Matter adapter mal schauen ob er den 'available' state als Status der Lampe weiter gibt. Zusätzlich bitte die 'role' des 'available' state im Objektbaum anschauen - und ob der Matter Adapter diesen als 'ist Status der Lampe' weiter gibt - er sollte den eigentlich ignorieren.

Was du zu testzwecken tun kannst ist die role auf indicator.reachable ändern - und dann den Matter Adapter neu starten - schauen ob er dann die Lichter anders ansteuert.

A.

[Fabio]

@asgothian der Matter Adapter muss das ja wohl weitergeben ansonten würde ja in der App es nicht angezeigt, meinst du den role ändern im Zigbee Adapter beim Gerät?
Das komische ist das ich ja 2 (jetzt sogar 3) Instanzen laufen habe und es nicht bei allen Geräten ist.

Im Matter Adapter sieht das Gerät so aus.

  Endpoint 115 (DimmableLight / a4c3b9ac-4359-4c72-aab4-3eff6f0d9526):
    Cluster-Servers:
      Cluster-Server "identify" (0x3) 
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 5
          "featureMap" (0xfffc): value = {}
          "attributeList" (0xfffb): value = [ 0, 1, 65533, 65532, 65531, 65529, 65528 ]
          "acceptedCommandList" (0xfff9): value = [ 0, 64 ]
          "generatedCommandList" (0xfff8): value = []
        Attributes:
          "identifyTime" (0x0): value = 0
          "identifyType" (0x1): value = 1
        Commands:
          "identify" (0x0)
          "triggerEffect" (0x40)
        Events:

      Cluster-Server "groups" (0x4) (Features: groupNames)
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 4
          "featureMap" (0xfffc): value = { groupNames: true }
          "attributeList" (0xfffb): value = [ 0, 65533, 65532, 65531, 65529, 65528 ]
          "acceptedCommandList" (0xfff9): value = [ 0, 1, 2, 3, 4, 5 ]
          "generatedCommandList" (0xfff8): value = [ 0, 1, 2, 3 ]
        Attributes:
          "nameSupport" (0x0): value = { nameSupport: false, groupNames: true }
        Commands:
          "addGroup" (0x0/0x0)
          "viewGroup" (0x1/0x1)
          "getGroupMembership" (0x2/0x2)
          "removeGroup" (0x3/0x3)
          "removeAllGroups" (0x4)
          "addGroupIfIdentifying" (0x5)
        Events:

      Cluster-Server "onOff" (0x6) (Features: lighting)
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 6
          "featureMap" (0xfffc): value = { lighting: true, deadFrontBehavior: false, offOnly: false }
          "attributeList" (0xfffb): value = [ 0, 65533, 65532, 65531, 65529, 65528, 16384, 16385, 16386, 16387 ]
          "acceptedCommandList" (0xfff9): value = [ 0, 64, 65, 66, 1, 2 ]
          "generatedCommandList" (0xfff8): value = []
        Attributes:
          "onOff" (0x0): value = true
          "globalSceneControl" (0x4000): value = true
          "onTime" (0x4001): value = 0
          "offWaitTime" (0x4002): value = 0
          "startUpOnOff" (0x4003): value = null
        Commands:
          "off" (0x0)
          "offWithEffect" (0x40)
          "onWithRecallGlobalScene" (0x41)
          "onWithTimedOff" (0x42)
          "on" (0x1)
          "toggle" (0x2)
        Events:

      Cluster-Server "levelControl" (0x8) (Features: onOff, lighting)
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 6
          "featureMap" (0xfffc): value = { onOff: true, lighting: true, frequency: false }
          "attributeList" (0xfffb): value = [ 0, 15, 17, 65533, 65532, 65531, 65529, 65528, 1, 16384 ]
          "acceptedCommandList" (0xfff9): value = [ 0, 1, 2, 3, 4, 5, 6, 7 ]
          "generatedCommandList" (0xfff8): value = []
        Attributes:
          "currentLevel" (0x0): value = 203
          "options" (0xf): value = { executeIfOff: false, coupleColorTempToLevel: false }
          "onLevel" (0x11): value = null
          "remainingTime" (0x1): value = 0
          "startUpCurrentLevel" (0x4000): value = null
        Commands:
          "moveToLevel" (0x0)
          "move" (0x1)
          "step" (0x2)
          "stop" (0x3)
          "moveToLevelWithOnOff" (0x4)
          "moveWithOnOff" (0x5)
          "stepWithOnOff" (0x6)
          "stopWithOnOff" (0x7)
        Events:

      Cluster-Server "bridgedDeviceBasicInformation" (0x39) 
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 4
          "featureMap" (0xfffc): value = { bridgedIcdSupport: false }
          "attributeList" (0xfffb): value = [ 3, 5, 14, 15, 17, 18, 65533, 65532, 65531, 65529, 65528 ]
          "acceptedCommandList" (0xfff9): value = []
          "generatedCommandList" (0xfff8): value = []
        Attributes:
          "productName" (0x3): value = "Kaffeebar"
          "nodeLabel" (0x5): value = "Kaffeebar"
          "productLabel" (0xe): value = "Kaffeebar"
          "serialNumber" (0xf): value = "a4c3b9ac43594c72aab43eff6f0d9526"
          "reachable" (0x11): value = true
          "uniqueId" (0x12): value = "e20f77882f6d22c1fcfd14b015f69ab3"
        Commands:

        Events:
          "reachableChanged" (0x3)
      Cluster-Server "descriptor" (0x1d) 
        Global-Attributes:
          "clusterRevision" (0xfffd): value = 2
          "featureMap" (0xfffc): value = { tagList: false }
          "attributeList" (0xfffb): value = [ 0, 1, 2, 3, 65533, 65532, 65531, 65529, 65528 ]
          "acceptedCommandList" (0xfff9): value = []
          "generatedCommandList" (0xfff8): value = []
        Attributes:
          "deviceTypeList" (0x0): value = [ { deviceType: 257, revision: 3 }, { deviceType: 19, revision: 3 } ]
          "serverList" (0x1): value = [ 3, 4, 6, 8, 57, 29 ]
          "clientList" (0x2): value = []
          "partsList" (0x3): value = []
        Commands:

        Events:

    Child-Endpoints:

[Asgothian]

@fabio sagte in Tester gesucht: Zigbee 3.2.x:

role ändern im Zigbee Adapter beim Gerät?

• im Objektbaum des Zigbee Adapters, bei einem der Geräte den DP available (im Expertenmodus) anschauen: Welche role hat der
• im Matter Adapter vom gleichen Gerät die Geräteerkennung anschauen - welche DP nutzt er für die Steuerung des Gerätes (geht aus den Daten oben nicht hervor)

Sollte da der available State mit dabei sein, dann muss der da weg. Da ich Matter aktuell nicht nutze, kann ich nicht sagen was da der beste Weg ist.

Daher der Versuch die role des oben angeschauten states auf indicator.reachable anzupassen und dann den Matter Adapter neu zu starten - in der Hoffnung das er das Gerät neu versucht zu erkennen.

A.

nachtrag: Nutzt du Alias Datenpunkte ? Wenn ja, wie erzeugst du die ? Über den 'devices' Adapter - dann ist auch da nochmal eine Mögliche Fehlerquelle.

[Fabio]

@asgothian nein kein Alias und im Matter Adapter gibt es keine Datenpunkte wie beim ZigBee Adapter und du kannst da nachträglich nichts ändern da bleibt nur das Gerät löschen und wieder neu übergeben.

.... so sieht das aus:

{
  "type": "state",
  "common": {
    "name": "Available",
    "color": null,
    "type": "boolean",
    "read": true,
    "write": false,
    "role": "state"
  },
  "native": {},
  "from": "system.adapter.zigbee.1",
  "user": "system.user.admin",
  "ts": 1750057449953,
  "_id": "zigbee.1.04cf8cdf3c7c2a0e.available",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

[Asgothian]

@fabio dann mal mit dem Experten Modus aus dem das machen:

{
  "type": "state",
  "common": {
    "name": "Available",
    "color": null,
    "type": "boolean",
    "read": true,
    "write": false,
    "role": "indicator.reachable"
  },
  "native": {},
  "from": "system.adapter.zigbee.1",
  "user": "system.user.admin",
  "ts": 1750057449953,
  "_id": "zigbee.1.04cf8cdf3c7c2a0e.available",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

und dann im Matter Adapter rauswerfen und neu hinzufügen.

Wobei mir dann nicht klar wird warum der Matter adapter sich anders verhält wenn du den Zigbee Adapter anpasst. Der Available State wurde auch sonst immer mal wieder aktualisiert.

A.

[Fabio]

@asgothian ich hoffe ich hab es richtig gemacht die role geändert.

Dann das Gerät im Matter Adapter gelöscht. Gewartet bis es bei Apple raus war und dann wieder neu hinzugefügt. Jetzt heißt es warten und schauen was passiert.

[Fabio]

@Asgothian so Test beendet. Ich bestätige das dieser Fehler durch deinen Workaround behoben ist. Hab jetzt alle Geräte wo das war umgestellt, blöd nur das ich sie dann auch erst löschen musste im Matter Adapter.
Sollte man apollon77 das evtl. mitteilen? Ist das überhaupt ein Bug? Erst mal herzlichen Dank melde dich wenn du Zeit hast.👌
Grüße Fabio

[Asgothian]

@fabio sagte in Tester gesucht: Zigbee 3.2.x:

@Asgothian so Test beendet. Ich bestätige das dieser Fehler durch deinen Workaround behoben ist. Hab jetzt alle Geräte wo das war umgestellt, blöd nur das ich sie dann auch erst löschen musste im Matter Adapter.
Sollte man apollon77 das evtl. mitteilen? Ist das überhaupt ein Bug? Erst mal herzlichen Dank melde dich wenn du Zeit hast.👌
Grüße Fabio

• das der Type detektor den available state als 'SET_ACTUAL` deklariert ist unglücklich. Das der Matter Adapter den einfach so übernimmt auch.
• Das der Matter Adapter nicht von sich aus auf geänderte Rollen reagiert ist meiner Meinung nach ein Bug - allerdings kann es sein das @apollon77 das absichtlich so umgesetzt hat.

Nen Issue ist das auf aber jeden Fall wert - dann kann geschaut werden ob das absicht, versehen oder bug ist.

Zum Thema Type Detektor (das ist denk ich nicht apollons direkte Baustelle) - das was da gemacht wird ist denkbar unschön:

Lt. der Rollen definition soll ein Datenpunkt dessen Role nicht zu den vordefinierten passt die Role state bekommen:

• state - very common purpose. If you don't know which role the state has, use this one.

Die Doku zum Type-Detector für lights sagt in der Tabelle das der Wert für ON_ACTUAL ein Boolean mit der Role sensor.light sein soll. Leider sagt das Match-Muster das daneben auch Boolean states mit der Role state oder switch als ON_ACTUAL genommen werden.

In der Kombination muss das eigentlich schief gehen. Ob das ein Fehler im Matter Adapter, im Type Detektor oder in der Role Definition ist weiss ich nicht.
Ich kenne verschiedene Zigbee Devices die als Light erkannt werden sollen, die aber weitere boolean States beinhalten - nicht nur available. Bei einigen davon gibt es sogar mehrere read only boolean states.

In der 3.2.6 wird jedenfalls zumindest der state available eine andere Role bekommen: indicator.reachable

Trotzdem ist die Kombination von Role definition, Device-Detektor und Matter Adapter in der Form mindestens mal unglücklich.

A.

[Fabio]

@asgothian
Type detektor available wird als state als 'SET_ACTUAL` deklariert
https://github.com/ioBroker/ioBroker.matter/issues/618

[apollon77]

Hey. Ja das an einigen stellen im type detector auch generische „state“ rollen genutzt werden sind der vergangenheit geschuldet. Kann ich leider so einfach nicht ändern. Alternative sind aliase oder Rollen korrigieren. Aber ja man kann gern type detector issue mit Beispiel Objekt Export anlegen dann kann man das diskutieren.

Das der matter Adapter (oder auch iot) nicht auf sich ändernde Rollen reagiert ohne restart bzw neustarten der Bridge liegt einfach daran das sich Rollen im Normalfall nicht einfach so ändern. Also für so einen Sonderfall Logik zu bauen empfinde ich daher als eher unnötig um ehrlich zu sein.

[Fabio]

@apollon77 ich bin nur ein einfacher Nutzer und kein Developer und verstehe auch nicht immer die Zusammenhänge.
Aber, ich persöhnlich finde das sehr merkwürdig, das An sich ändert wenn der State dafür aber nicht geschaltet wurde, sondern nur weil value generated 'true' from device a4c1389893367f90 for 'Available' geändert sprich abgefragt wurde, so weiß man letztendlich nicht wie in der Apple Home App, ist das Gerät nun wirklich An oder Aus. Und das finde ich ist ne Dikussion oder Änderung alle mal wert. ;-)

Herzliche Grüße
Fabio

[Asgothian]

@apollon77

Das der matter Adapter (oder auch iot) nicht auf sich ändernde Rollen reagiert ohne restart bzw >neustarten der Bridge liegt einfach daran das sich Rollen im Normalfall nicht einfach so ändern. Also für so einen Sonderfall Logik zu bauen empfinde ich daher als eher unnötig um ehrlich zu sein

Nur als Klarstellung - beim Neustart des matter Adapters werden die Änderungen der Role erkannt ?

A.

[apollon77]

@asgothian Sogar beim "Nur neustarten (einmal aus und an) der Bridge" weil dann wird alles eingelesen und gemappt. Ja

[apollon77]

Ich hab mal https://github.com/ioBroker/ioBroker.type-detector/issues/155 angelegt. Gern dort Meinungen rein hauen

[Flaterick]

Hab da ein Problem weis aber nicht Obs hier rein Passt.
Zumindest ist es die Testversion die ansonsten zuverlässig geht.
Hab angefangen zu Basteln, dazu wollte ich einen Externen Converter einbinden. Denke er wird auch gefunden nur der zugriff wird verweigert.

Das ganze läuft auf aktuellem Ubuntu unter Docker, ioBroker ist auch aktuell.

[Asgothian]

Bitte posten:

• den externen konverter den du nutzt
• die Einträge zum externen Konverter beim Start des Adapters. Da muss so etwas (o.a.) stehen

2025-11-23 20:12:40.755 - info: zigbee.0 (983320) Adding code from './../zigbee-herdsman-converters/dist/lib/modernExtend' as 'm' to sandbox -- success
2025-11-23 20:12:40.756 - info: zigbee.0 (983320) Adding code from './../zigbee-herdsman-converters/dist/lib/types' as 'type {DefinitionWithExtend}' to sandbox -- success
2025-11-23 20:12:40.757 - warn: zigbee.0 (983320) Trying to run sandbox for /opt/iobroker/iobroker-data/zigbee_0/shelly.js
2025-11-23 20:12:40.759 - info: zigbee.0 (983320) Model S4SW-001X8EU defined in external converter /opt/iobroker/iobroker-data/zigbee_0/shelly.js
2025-11-23 20:12:40.759 - info: zigbee.0 (983320) added external converter using addExternalDefinition (0 ms)
2025-11-23 20:12:40.760 - warn: zigbee.0 (983320) Trying to run sandbox for /opt/iobroker/iobroker-data/zigbee_0/esp.js
2025-11-23 20:12:40.763 - info: zigbee.0 (983320) Model ZBColorLightBulb defined in external converter /opt/iobroker/iobroker-data/zigbee_0/esp.js
2025-11-23 20:12:40.763 - info: zigbee.0 (983320) added external converter using addExternalDefinition (0 ms)

A.

[Flaterick]

Das ist schon mal der Konverter wurde von PTVO erzeugt.

const zigbeeHerdsmanConverters = require('zigbee-herdsman-converters');
const zigbeeHerdsmanUtils = require('zigbee-herdsman-converters/lib/utils');


const exposes = zigbeeHerdsmanConverters['exposes'] || require("zigbee-herdsman-converters/lib/exposes");
const ea = exposes.access;
const e = exposes.presets;
const modernExposes = (e.hasOwnProperty('illuminance_lux'))? false: true;

const fz = zigbeeHerdsmanConverters.fromZigbeeConverters || zigbeeHerdsmanConverters.fromZigbee;
const tz = zigbeeHerdsmanConverters.toZigbeeConverters || zigbeeHerdsmanConverters.toZigbee;

const ptvo_switch = (zigbeeHerdsmanConverters.findByModel)?zigbeeHerdsmanConverters.findByModel('ptvo.switch'):zigbeeHerdsmanConverters.findByDevice({modelID: 'ptvo.switch'});
fz.ptvo_on_off = {
  cluster: 'genOnOff',
  type: ['attributeReport', 'readResponse'],
  convert: (model, msg, publish, options, meta) => {
      if (msg.data.hasOwnProperty('onOff')) {
          const channel = msg.endpoint.ID;
          const endpointName = `l${channel}`;
          const binaryEndpoint = model.meta && model.meta.binaryEndpoints && model.meta.binaryEndpoints[endpointName];
          const prefix = (binaryEndpoint) ? model.meta.binaryEndpoints[endpointName] : 'state';
          const property = `${prefix}_${endpointName}`;
	  if (binaryEndpoint) {
            return {[property]: msg.data['onOff'] === 1};
          }
          return {[property]: msg.data['onOff'] === 1 ? 'ON' : 'OFF'};
      }
  },
};


const switchTypesList = {
    'switch': 0x00,
    'single click': 0x01,
    'multi-click': 0x02,
    'reset to defaults': 0xff,
};

const switchActionsList = {
    on: 0x00,
    off: 0x01,
    toggle: 0x02,
};

const inputLinkList = {
    no: 0x00,
    yes: 0x01,
};

const bindCommandList = {
    'on/off': 0x00,
    'toggle': 0x01,
    'change level up': 0x02,
    'change level down': 0x03,
    'change level up with off': 0x04,
    'change level down with off': 0x05,
    'recall scene 0': 0x06,
    'recall scene 1': 0x07,
    'recall scene 2': 0x08,
    'recall scene 3': 0x09,
    'recall scene 4': 0x0A,
    'recall scene 5': 0x0B,
    'dimmer': 0x0C,
    'dimmer (hue)': 0x0D,
    'dimmer (saturation)': 0x0E,
    'dimmer (color temperature)': 0x0F,
    'intruder alarm systems (ias)': 0x20,
};

function getSortedList(source) {
    const keysSorted = [];
    for (const key in source) {
        keysSorted.push([key, source[key]]);
    }

    keysSorted.sort(function(a, b) {
        return a[1] - b[1];
    });

    const result = [];
    keysSorted.forEach((item) => {
        result.push(item[0]);
    });
    return result;
}

function getListValueByKey(source, value) {
    const intVal = parseInt(value, 10);
    return source.hasOwnProperty(value) ? source[value] : intVal;
}

const getKey = (object, value) => {
    for (const key in object) {
        if (object[key] == value) return key;
    }
};

tz.ptvo_on_off_config = {
    key: ['switch_type', 'switch_actions', 'link_to_output', 'bind_command'],
    convertGet: async (entity, key, meta) => {
        await entity.read('genOnOffSwitchCfg', ['switchType', 'switchActions', 0x4001, 0x4002]);
    },
    convertSet: async (entity, key, value, meta) => {
        let payload;
        let data;
        switch (key) {
        case 'switch_type':
            data = getListValueByKey(switchTypesList, value);
            payload = {switchType: data};
            break;
        case 'switch_actions':
            data = getListValueByKey(switchActionsList, value);
            payload = {switchActions: data};
            break;
        case 'link_to_output':
            data = getListValueByKey(inputLinkList, value);
            payload = {0x4001: {value: data, type: 32 /* uint8 */}};
            break;
        case 'bind_command':
            data = getListValueByKey(bindCommandList, value);
            payload = {0x4002: {value: data, type: 32 /* uint8 */}};
            break;
        }
        await entity.write('genOnOffSwitchCfg', payload);
    },
};

fz.ptvo_on_off_config = {
    cluster: 'genOnOffSwitchCfg',
    type: ['readResponse', 'attributeReport'],
    convert: (model, msg, publish, options, meta) => {
        const channel = getKey(model.endpoint(msg.device), msg.endpoint.ID);
        const {switchActions, switchType} = msg.data;
        const inputLink = msg.data[0x4001];
        const bindCommand = msg.data[0x4002];
        return {
            [`switch_type_${channel}`]: getKey(switchTypesList, switchType),
            [`switch_actions_${channel}`]: getKey(switchActionsList, switchActions),
            [`link_to_output_${channel}`]: getKey(inputLinkList, inputLink),
            [`bind_command_${channel}`]: getKey(bindCommandList, bindCommand),
        };
    },
};

function ptvo_on_off_config_exposes(epName) {
    const features = [];
    features.push(exposes.enum('switch_type', exposes.access.ALL,
        getSortedList(switchTypesList)).withEndpoint(epName));
    features.push(exposes.enum('switch_actions', exposes.access.ALL,
        getSortedList(switchActionsList)).withEndpoint(epName));
    features.push(exposes.enum('link_to_output', exposes.access.ALL,
        getSortedList(inputLinkList)).withEndpoint(epName));
    features.push(exposes.enum('bind_command', exposes.access.ALL,
        getSortedList(bindCommandList)).withEndpoint(epName));
    return features;
}




const device = {
    zigbeeModel: ['Mat-LED'],
    model: 'Mat-LED',
    vendor: 'Mat',
    description: '[Configurable firmware](https://ptvo.info/zigbee-configurable-firmware-features/)',
    fromZigbee: [fz.ignore_basic_report, fz.ptvo_on_off, fz.ptvo_multistate_action, fz.ptvo_on_off_config, fz.electrical_measurement,],
    toZigbee: [tz.ptvo_switch_trigger, tz.on_off, tz.ptvo_on_off_config,],
    exposes: [e.switch().withDescription('Impulsschalter').withEndpoint('l1'),
      e.action(['single', 'double', 'triple', 'hold', 'release']),
      ...ptvo_on_off_config_exposes('l1'),
      e.voltage().withAccess(ea.STATE).withEndpoint('l3'),
],
    meta: {
        multiEndpoint: true,
        
    },
    endpoint: (device) => {
        return {
            l1: 1, l3: 3,
        };
    },
    configure: async (device, coordinatorEndpoint, logger) => {
      const endpoint = device.getEndpoint(1);
      await endpoint.read('genBasic', ['modelId', 'swBuildId', 'powerSource']);
    for (const endpoint of device.endpoints) {
        if (endpoint.supportsInputCluster('haElectricalMeasurement')) {
            endpoint.saveClusterAttributeKeyValue('haElectricalMeasurement', {dcCurrentDivisor: 1000, dcCurrentMultiplier: 1,
                dcPowerDivisor: 10, dcPowerMultiplier: 1, dcVoltageDivisor: 100, dcVoltageMultiplier: 1,
                acVoltageDivisor: 100, acVoltageMultiplier: 1, acCurrentDivisor: 1000, acCurrentMultiplier: 1,
                acPowerDivisor: 1, acPowerMultiplier: 1});
        }
        if (endpoint.supportsInputCluster('seMetering')) {
            endpoint.saveClusterAttributeKeyValue('seMetering', {divisor: 1000, multiplier: 1});
        }
    }
    },

};

module.exports = device;

[Flaterick]

Hat leider etwas gedauert.
Ich Finde keine Entsprechenden Einträge.
Unter zigbee2mqtt funktioniert es.

[Flaterick]

Habs Hinbekommen, Hatte in der Konfiguration in der Zigbeeinstanz einen Schreibfehler.
Danke