Monatsrückblick Januar/Februar 2026 ist online!

[reutli]

Hallo zusammen,

habe ziemlich neu einen Zigbee Fehler:

zigbee.0
	2026-04-01 16:40:02.829	warn	Error while processing converters DEVICE_ID: 'f4b3b1fffe52289c' cluster 'customSonoffSnzb02p' type 'attributeReport,readResponse' message: Value is not a number, got undefined (undefined)
zigbee.0
	2026-04-01 16:40:02.802	info	Device query for '0xf4b3b1fffe52289c' complete
zigbee.0
	2026-04-01 16:40:02.308	warn	Error while processing converters DEVICE_ID: 'f4b3b1fffe52289c' cluster 'customSonoffSnzb02p' type 'attributeReport,readResponse' message: Value is not a number, got undefined (undefined)
zigbee.0
	2026-04-01 16:39:58.777	info	Device query for '0xf4b3b1fffe52289c' started
zigbee.0
	2026-04-01 16:39:58.777	warn	Device '0xf4b3b1fffe52289c' announced itself, trying to read its status

Die ID ins Debug geworfen ergibt:

zigbee.0
	2026-04-01 16:42:17.897	warn	ELEVATED:I01 (c4a8) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{},"linkquality":80,"groupID":0,"cluster":"customSonoffSnzb02p","meta":{"rawData":{"type":"Buffer","data":[24,101,1,4,32,134]},"zclTransactionSequenceNumber":101,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:17.401	warn	ELEVATED:I04 (c2b7) No value published for device f4b3b1fffe52289c
zigbee.0
	2026-04-01 16:42:17.401	warn	ELEVATED:I03 (c2b7) message received '{}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:17.401	warn	ELEVATED:I02.2c (c2b7) candidates: [{},{}] => payload {}
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:I02.1b (c2b7) data: {} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:undefined
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:I02.2a (c2b7) converter 2 : Cluster customSonoffSnzb02p
zigbee.0
	2026-04-01 16:42:17.400	warn	Error while processing converters DEVICE_ID: 'f4b3b1fffe52289c' cluster 'customSonoffSnzb02p' type 'attributeReport,readResponse' message: Value is not a number, got undefined (undefined)
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:EPROC (c2b7) Error while processing converters DEVICE_ID: 'f4b3b1fffe52289c' cluster 'customSonoffSnzb02p' type 'attributeReport,readResponse' message: Value is not a number, got undefined (undefined)
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:I02.1a (c2b7) converter 1 : Cluster customSonoffSnzb02p
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:I02 (c2b7) 2 converters available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'customSonoffSnzb02p' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:17.400	warn	ELEVATED:I04 (c2b7) value generated '76' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:17.399	warn	ELEVATED:I01 (c2b7) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{},"linkquality":76,"groupID":0,"cluster":"customSonoffSnzb02p","meta":{"rawData":{"type":"Buffer","data":[24,100,1,3,32,134]},"zclTransactionSequenceNumber":100,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I04 (c0c2) value generated '27.6' from device f4b3b1fffe52289c for 'Measured relative humidity'
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I03 (c0c2) message received '{"humidity":27.6}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I02.1c (c0c2) candidates: [{"humidity":27.6}] => payload {"humidity":27.6}
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I02.0b (c0c2) data: {"measuredValue":2760} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{"humidity":27.6}
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I02.1a (c0c2) converter 1 : Cluster msRelativeHumidity
zigbee.0
	2026-04-01 16:42:16.900	warn	ELEVATED:I02 (c0c2) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'msRelativeHumidity' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:16.899	warn	ELEVATED:I04 (c0c2) value generated '76' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:16.898	warn	ELEVATED:I01 (c0c2) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{"measuredValue":2760},"linkquality":76,"groupID":0,"cluster":"msRelativeHumidity","meta":{"rawData":{"type":"Buffer","data":[24,99,1,0,0,0,33,200,10]},"zclTransactionSequenceNumber":99,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:16.297	warn	ELEVATED:I04 (be66) value generated '25.3' from device f4b3b1fffe52289c for 'Measured temperature value'
zigbee.0
	2026-04-01 16:42:16.297	warn	ELEVATED:I03 (be66) message received '{"temperature":25.3}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:16.297	warn	ELEVATED:I02.1c (be66) candidates: [{"temperature":25.3}] => payload {"temperature":25.3}
zigbee.0
	2026-04-01 16:42:16.297	warn	ELEVATED:I02.0b (be66) data: {"measuredValue":2530} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{"temperature":25.3}
zigbee.0
	2026-04-01 16:42:16.296	warn	ELEVATED:I02.1a (be66) converter 1 : Cluster msTemperatureMeasurement
zigbee.0
	2026-04-01 16:42:16.296	warn	ELEVATED:I02 (be66) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'msTemperatureMeasurement' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:16.296	warn	ELEVATED:I04 (be66) value generated '76' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:16.294	warn	ELEVATED:I01 (be66) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{"measuredValue":2530},"linkquality":76,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"rawData":{"type":"Buffer","data":[24,98,1,0,0,0,41,226,9]},"zclTransactionSequenceNumber":98,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:15.668	warn	ELEVATED:I04 (bbf2) No value published for device f4b3b1fffe52289c
zigbee.0
	2026-04-01 16:42:15.668	warn	ELEVATED:I03 (bbf2) message received '{}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:15.667	warn	ELEVATED:I02.1c (bbf2) candidates: [{}] => payload {}
zigbee.0
	2026-04-01 16:42:15.667	warn	ELEVATED:I02.0b (bbf2) data: {} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{}
zigbee.0
	2026-04-01 16:42:15.667	warn	ELEVATED:I02.1a (bbf2) converter 1 : Cluster genPowerCfg
zigbee.0
	2026-04-01 16:42:15.667	warn	ELEVATED:I02 (bbf2) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'genPowerCfg' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:15.667	warn	ELEVATED:I04 (bbf2) value generated '80' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:15.666	warn	ELEVATED:I01 (bbf2) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{},"linkquality":80,"groupID":0,"cluster":"genPowerCfg","meta":{"rawData":{"type":"Buffer","data":[24,97,1,32,0,134]},"zclTransactionSequenceNumber":97,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I04 (ba02) value generated '100' from device f4b3b1fffe52289c for 'Remaining battery in %'
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I03 (ba02) message received '{"battery":100}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I02.1c (ba02) candidates: [{"battery":100}] => payload {"battery":100}
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I02.0b (ba02) data: {"batteryPercentageRemaining":200} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{"battery":100}
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I02.1a (ba02) converter 1 : Cluster genPowerCfg
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I02 (ba02) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'genPowerCfg' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:15.172	warn	ELEVATED:I04 (ba02) value generated '80' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:15.170	warn	ELEVATED:I01 (ba02) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{"batteryPercentageRemaining":200},"linkquality":80,"groupID":0,"cluster":"genPowerCfg","meta":{"rawData":{"type":"Buffer","data":[24,96,1,33,0,0,32,200]},"zclTransactionSequenceNumber":96,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:14.667	warn	ELEVATED:I04 (b809) No value published for device f4b3b1fffe52289c
zigbee.0
	2026-04-01 16:42:14.667	warn	ELEVATED:I03 (b809) message received '{}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:14.667	warn	ELEVATED:I02.1c (b809) candidates: [{}] => payload {}
zigbee.0
	2026-04-01 16:42:14.667	warn	ELEVATED:I02.0b (b809) data: {} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{}
zigbee.0
	2026-04-01 16:42:14.667	warn	ELEVATED:I02.1a (b809) converter 1 : Cluster genPowerCfg
zigbee.0
	2026-04-01 16:42:14.666	warn	ELEVATED:I02 (b809) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'genPowerCfg' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:14.666	warn	ELEVATED:I04 (b809) value generated '80' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:14.665	warn	ELEVATED:I01 (b809) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{},"linkquality":80,"groupID":0,"cluster":"genPowerCfg","meta":{"rawData":{"type":"Buffer","data":[24,95,1,32,0,134]},"zclTransactionSequenceNumber":95,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:14.173	warn	ELEVATED:I04 (b61a) value generated '100' from device f4b3b1fffe52289c for 'Remaining battery in %'
zigbee.0
	2026-04-01 16:42:14.173	warn	ELEVATED:I03 (b61a) message received '{"battery":100}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:14.173	warn	ELEVATED:I02.1c (b61a) candidates: [{"battery":100}] => payload {"battery":100}
zigbee.0
	2026-04-01 16:42:14.173	warn	ELEVATED:I02.0b (b61a) data: {"batteryPercentageRemaining":200} options: {} meta:{"deviceIEEE":"0xf4b3b1fffe52289c","logger":"StatesController","state":{"state":""}} result:{"battery":100}
zigbee.0
	2026-04-01 16:42:14.173	warn	ELEVATED:I02.1a (b61a) converter 1 : Cluster genPowerCfg
zigbee.0
	2026-04-01 16:42:14.172	warn	ELEVATED:I02 (b61a) 1 converter available for 'SNZB-02P' 'f4b3b1fffe52289c' with cluster 'genPowerCfg' and type 'readResponse'
zigbee.0
	2026-04-01 16:42:14.172	warn	ELEVATED:I04 (b61a) value generated '80' from device f4b3b1fffe52289c for 'Link quality'
zigbee.0
	2026-04-01 16:42:14.171	warn	ELEVATED:I04 (b61b) value generated 'true' from device f4b3b1fffe52289c for 'Available'
zigbee.0
	2026-04-01 16:42:14.171	warn	ELEVATED:I03 (b61b) message received '{"available":true}' from device f4b3b1fffe52289c type 'SNZB-02P'
zigbee.0
	2026-04-01 16:42:14.171	warn	ELEVATED:I01 (b61a) Zigbee Event of Type readResponse from device 0xf4b3b1fffe52289c, incoming event: {"type":"readResponse","data":{"batteryPercentageRemaining":200},"linkquality":80,"groupID":0,"cluster":"genPowerCfg","meta":{"rawData":{"type":"Buffer","data":[24,94,1,33,0,0,32,200]},"zclTransactionSequenceNumber":94,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
zigbee.0
	2026-04-01 16:42:13.657	info	Device query for '0xf4b3b1fffe52289c' started
zigbee.0
	2026-04-01 16:42:13.657	warn	Device '0xf4b3b1fffe52289c' announced itself, trying to read its status
zigbee.0
	2026-04-01 16:42:13.656	warn	ELEVATED:Ida (b418) Device '0xf4b3b1fffe52289c' announced itself
zigbee.0
	2026-04-01 16:41:28.334	info	debug devices set to ["f4b3b1fffe52289c"]

Was könnte die Lösung sein oder wo kann ich weiter suchen?

Danke.

[arteck]

das ist schon ironisch oder

das steht in deiner Signatur und postetst die paar LOG fetzen

was soll uns das sagen ?? ausser da ist ein Fehler .. ??

adapter version zigbee coordinator firmware .. komm bissel mehr muss es sein.

axo..wenn du

wo kann ich weiter suchen

empfehle ich https://github.com/ioBroker/ioBroker.zigbee
da steht alles was du brauchst

[reutli]

@arteck sagte:

das ist schon ironisch oder

778a8cb6-54a9-4509-a119-c5a33b8e6446-image.jpeg

das steht in deiner Signatur und postetst die paar LOG fetzen

deutlich, danke.
Signatur sofort geändert, da ich selbst zu dumm bin, eine ordentliche Anfrage zu stellen.
Nichts für ungut.

[Asgothian]

@reutli sagte:

Was könnte die Lösung sein oder wo kann ich weiter suchen?

Um diese Frage zu beantworten benötigen wir Kontext:

• Welche Adapter-Version nutzt du ?
• Welche ZHC Version ist bei Dir installiert (steht auf der Koordinator Kachel)
• Was zeigt das Debug Interface zu dem Fehler, wenn du das Gerät in Debug laufen lässt (Doku dazu siehe hier: https://github.com/ioBroker/ioBroker.zigbee/wiki/Device-messaging-debug)
• Seit wann gibt es diese Meldungen
• was wurde geändert als die Meldungen aufgetaucht sind - von alleine tauchen diese Meldungen nicht auf.

Nebenbei hat @arteck genau nach diesen Informationen auch gefragt, nicht nach den anpassen Deiner Signatur.

A.

[reutli]

@Asgothian sagte:

Nebenbei hat @arteck genau nach diesen Informationen auch gefragt, nicht nach den anpassen Deiner Signatur.

Mir schon klar, diesmal war es tatsächlich gwünschte Ironie von mir.

@Asgothian sagte:

Was zeigt das Debug Interface zu dem Fehler, wenn du das Gerät in Debug laufen lässt (Doku dazu siehe hier: https://github.com/ioBroker/ioBroker.zigbee/wiki/Device-messaging-debug)

Hatte ich oben gleich mitgeliefert.

@Asgothian sagte:

was wurde geändert als die Meldungen aufgetaucht sind - von alleine tauchen diese Meldungen nicht auf.

Tatsächlich nichts (kein Neustart, keine Updates, keine Geräteveränderungen). Das war das warum ich mcih gewundert habe.

Meldungen kommen aktuell nicht mehr - deshalb schließe ich den post.

[Asgothian]

@reutli sagte:

Hatte ich oben gleich mitgeliefert.

Da muss ich widersprechen. Du hast die Einträge die durch die Aktivierung des Debug-Modus im allgemeinem Log entstehen geliefert, aber nicht das was du im Debug UI zu den einzelnen Events gesammelt bekommst - damit wird der Kontext vermischt.

Das macht die Sache Unhandlich - die interessanten Meldungen verstecken sich in der menge der Meldungen.

Aber da die Meldungen erst einmal wieder weg sind kann ich da dann auch ohne die fehlenden Informationen nichts tun.

A.