Moes garage door module ZM-102-M is spamming a network

What happened?

Experiencing some slow downs in a network, probably caused by this module.

I've already set debounce to 1 and filtered out linkquality and timestamp attributes.

What did you expect to happen?

Should be a little bit more quiet. :)

How to reproduce it (minimal and precise)

Just pair it and that's it, starts spamming immediately.

Zigbee2MQTT version

2.13.0-dev

Adapter firmware version

20260310

Adapter

SLZB-MRW10U - LAN connection

Setup

Running everything as Docker containers on Synology NAS.

Device database.db entry

{"id":7,"type":"Router","ieeeAddr":"0xa4c138f7883f79b9","nwkAddr":43841,"manufId":4417,"manufName":"_TZE204_jktmrpoj","powerSource":"Mains (single phase)","modelId":"TS0601","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[4,5,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"\b�\u00032i\t�\u00032i\t�\u00032i\n�\u00032i\n�\u00032i\u000b�\u00032i\u000b�\u00032i\f�\u00032i","65506":56,"65508":0,"65534":0,"modelId":"TS0601","manufacturerName":"_TZE204_jktmrpoj","powerSource":1,"zclVersion":3,"appVersion":74,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":74,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":"0.0.0"},"lastSeen":1785997404169}

Debug log

_zigbee2mqtt_logs.txt

Notes

Exact device:

https://www.aliexpress.com/item/1005009332231436.html

This is the only Moes device I'm having issue with.

Start by examining the attached debug log and the device database.db entry for ZM-102-M, focusing on the reports emitted immediately after pairing. Trace where this device's updates are handled and compare the observed traffic with the debounce and attribute filters described in the issue. Done means pairing the module no longer causes the reported network spamming while its expected updates still work.