Lumi.vibration.aq1 sensor with phantom triggers since deCONZ 2.29.5

Smanar · May 10, 2025, 10:18am

The state/vibration value is updated on Cluster 0x0101, attribute 0x0055.

05:10:11:722 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000

So the device is realy sending a request. Unfortunately we haven’t the value, it’s possible to have it if you enable APS+APS_l2, we will have the “asdu”.

Edit:
After a check, this device send only request on vibration on attribute 0x0055, value is 0x0001,0x0002 or 0x0003, so it’s deconz that “reset the detection”.

But it mean your device have probably detected something.

05:10:11:722 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000

From what I m reading the device never make norification if there is nothing.
Will be usefull the see the attribute in the report and the value.

And it’s a report, so it’s not deconz that is polling the device, it’s a “natural” notification.

hiteule · May 10, 2025, 11:49am

@Smanar , thanks for your quick reply.
I have enabled the aps logs. I also moved my sensor to be sure it will not detect something during the day.

I will monitoring it and I keep you posted.

hiteule · May 10, 2025, 1:01pm

Hi @Smanar ,

Here is 2 logs of “phantom” events:
1/ Vibration detected at 14:09:08 and “disabled” at 14:10:13

14:08:57:807 APS-DATA.request id: 195 erase from queue
14:09:08:204 APS-DATA.request id: 238, addrmode: 0x03, addr: 0xA4C138445ED92317, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:09:08:206    asdu (length: 2): 9D06
14:09:08:249 APS-DATA.confirm id: 238, status: 0x00 SUCCESS
14:09:08:265 APS-DATA.indication srcAddr: 0xC905, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -67
14:09:08:266    asdu: 9d000a0602189c06ffff2e21004a39803cdf8ccf04442c25020145189c06ffff2e2100a61527522038c1a4ab692502013c
14:09:08:267 APS-DATA.indication request id: 238 -> finished
14:09:08:268 APS-DATA.request id: 238 erase from queue
14:09:08:916 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -67
14:09:08:918    asdu: 18080a5500210100
14:09:08:920 Door lock debug 0x00158D00010FCC9D, data 0x0000000A 
14:09:08:922 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:09:748 Set sensor check interval to 100 milliseconds
14:09:14:081 APS-DATA.request id: 9, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:14:083    asdu (length: 5): 10C0000000
14:09:14:113 APS-DATA.confirm id: 9, status: 0x00 SUCCESS
14:09:14:114 APS-DATA.confirm request id: 9 -> erase from queue
14:09:14:124 aps request id: 9 finished, erase from queue
14:09:14:247 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -54
14:09:14:249    asdu: 18c0010000001000
14:09:19:248 APS-DATA.request id: 32, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:19:250    asdu (length: 5): 10C1000000
14:09:19:279 APS-DATA.confirm id: 32, status: 0x00 SUCCESS
14:09:19:281 APS-DATA.confirm request id: 32 -> erase from queue
14:09:19:296 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:09:19:298    asdu: 18c1010000001000
14:09:19:299 APS-DATA.request id: 32 erase from queue
14:09:19:302 APS-DATA.request id: 34, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:09:19:303    asdu (length: 5): 10C2005500
14:09:19:339 APS-DATA.confirm id: 34, status: 0x00 SUCCESS
14:09:19:341 APS-DATA.confirm request id: 34 -> erase from queue
14:09:19:355 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -67
14:09:19:357    asdu: 18c2015500003900000000
14:09:19:358 APS-DATA.request id: 34 erase from queue
14:09:23:564 APS-DATA.request id: 53, addrmode: 0x03, addr: 0xA4C138445ED92317, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:09:23:566    asdu (length: 2): 9E08
14:09:23:598 APS-DATA.confirm id: 53, status: 0x00 SUCCESS
14:09:23:617 APS-DATA.indication srcAddr: 0xC905, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -67
14:09:23:618    asdu: 9e000a0802189c06ffff2e210045c2070aaa3eb07c89ab2502012a189c06ffff2e2100266db5feff504b80b60a25020136
14:09:23:620 APS-DATA.indication request id: 53 -> finished
14:09:23:621 APS-DATA.request id: 53 erase from queue
14:09:28:249 APS-DATA.request id: 74, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:28:251    asdu (length: 5): 10C3000000
14:09:28:282 APS-DATA.confirm id: 74, status: 0x00 SUCCESS
14:09:28:284 APS-DATA.confirm request id: 74 -> erase from queue
14:09:28:294 aps request id: 74 finished, erase from queue
14:09:28:303 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:09:28:305    asdu: 18c3010000001000
14:09:28:306 APS-DATA.request id: 76, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:09:28:308    asdu (length: 5): 10C4005500
14:09:28:339 APS-DATA.confirm id: 76, status: 0x00 SUCCESS
14:09:28:341 APS-DATA.confirm request id: 76 -> erase from queue
14:09:28:357 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -67
14:09:28:359    asdu: 18c4015500003900000000
14:09:28:360 APS-DATA.request id: 76 erase from queue
14:09:28:413 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xFCC0, lqi: 255, rssi: -67
14:09:28:415    asdu: 1c5f11320af700413d6410000328139839000000009539873c8042963900401245973900000000052123009a20000821160107270000000000000000092100080b20009b1001
14:09:28:420 ZCL attribute report 0x04CF8CDF3C80394A for cluster: 0xFCC0, ep: 0x01, frame control: 0x1C, mfcode: 0x115F 
14:09:28:424 APS-DATA.request id: 79, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:28:426    asdu (length: 5): 10C5000000
14:09:28:456 APS-DATA.confirm id: 79, status: 0x00 SUCCESS
14:09:28:458 APS-DATA.confirm request id: 79 -> erase from queue
14:09:28:464 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:09:28:466    asdu: 18c5010000001000
14:09:28:468 APS-DATA.request id: 79 erase from queue
14:09:28:702 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -70
14:09:28:704    asdu: 18110a00001000
14:09:28:707 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:28:844 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:09:28:847    asdu: 18b20a00001000
14:09:28:849 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:29:701 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -70
14:09:29:703    asdu: 18120a0805210000
14:09:29:706 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:29:845 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -67
14:09:29:847    asdu: 18b30a0b05290000
14:09:29:850 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:30:847 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -67
14:09:30:850    asdu: 18b40a0805210000
14:09:30:852 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:09:38:924 APS-DATA.request id: 128, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:09:38:927    asdu (length: 2): 9F00
14:09:38:959 APS-DATA.confirm id: 128, status: 0x00 SUCCESS
14:09:38:984 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -70
14:09:38:985    asdu: 9f00080002189c06ffff2e21008a41dccc8a38c1a4e13505020261189c06ffff2e2100dc4b7e3cdf8ccf04ec1d05020115
14:09:38:987 APS-DATA.indication request id: 128 -> finished
14:09:38:988 APS-DATA.request id: 128 erase from queue
14:09:46:350 APS-DATA.request id: 160, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:46:352    asdu (length: 5): 10C6000000
14:09:46:382 APS-DATA.confirm id: 160, status: 0x00 SUCCESS
14:09:46:384 APS-DATA.confirm request id: 160 -> erase from queue
14:09:46:443 aps request id: 160 finished, erase from queue
14:09:47:051 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -55
14:09:47:053    asdu: 18c6010000001000
14:09:51:748 APS-DATA.request id: 184, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:51:751    asdu (length: 5): 10C7000000
14:09:51:782 APS-DATA.confirm id: 184, status: 0x00 SUCCESS
14:09:51:783 APS-DATA.confirm request id: 184 -> erase from queue
14:09:51:803 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -66
14:09:51:805    asdu: 18c7010000001000
14:09:51:806 APS-DATA.request id: 184 erase from queue
14:09:51:808 APS-DATA.request id: 186, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:09:51:809    asdu (length: 5): 10C8005500
14:09:51:844 APS-DATA.confirm id: 186, status: 0x00 SUCCESS
14:09:51:846 APS-DATA.confirm request id: 186 -> erase from queue
14:09:51:860 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -66
14:09:51:861    asdu: 18c8015500003900000000
14:09:51:862 APS-DATA.request id: 186 erase from queue
14:09:54:284 APS-DATA.request id: 198, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:09:54:286    asdu (length: 2): A002
14:09:54:330 APS-DATA.confirm id: 198, status: 0x00 SUCCESS
14:09:54:344 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -69
14:09:54:346    asdu: a000080202189c06ffff2e21001723d95e4438c1a405c925020133189c06ffff2e21004a39803cdf8ccf04442c2502012d
14:09:54:347 APS-DATA.indication request id: 198 -> finished
14:09:54:348 APS-DATA.request id: 198 erase from queue
14:09:54:844 APS-DATA.indication srcAddr: 0x0AB6, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -74
14:09:54:846    asdu: 08560a00002800
14:09:54:848 ZCL attribute report 0x804B50FFFEB56D26 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
14:09:54:851 APS-DATA.request id: 203, addrmode: 0x02, addr: 0x0AB6, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:09:54:853    asdu (length: 5): 10560B0A00
14:09:54:879 APS-DATA.confirm id: 203, status: 0x00 SUCCESS
14:09:54:880 APS-DATA.confirm request id: 203 -> erase from queue
14:09:54:924 aps request id: 203 finished, erase from queue
14:10:00:749 APS-DATA.request id: 228, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:10:00:751    asdu (length: 5): 10C9000000
14:10:00:780 APS-DATA.confirm id: 228, status: 0x00 SUCCESS
14:10:00:782 APS-DATA.confirm request id: 228 -> erase from queue
14:10:00:797 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -70
14:10:00:798    asdu: 18c9010000001000
14:10:00:800 APS-DATA.request id: 228 erase from queue
14:10:00:802 APS-DATA.request id: 230, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:10:00:803    asdu (length: 5): 10CA005500
14:10:00:836 APS-DATA.confirm id: 230, status: 0x00 SUCCESS
14:10:00:838 APS-DATA.confirm request id: 230 -> erase from queue
14:10:00:846 aps request id: 230 finished, erase from queue
14:10:00:853 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -70
14:10:00:854    asdu: 18ca015500003900000000
14:10:09:644 APS-DATA.request id: 11, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:10:09:645    asdu (length: 2): A104
14:10:09:683 APS-DATA.confirm id: 11, status: 0x00 SUCCESS
14:10:09:704 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -69
14:10:09:705    asdu: a100080402189c06ffff2e2100266db5feff504b80b60a2502012d189c06ffff2e2100a61527522038c1a4ab6925020136
14:10:09:707 APS-DATA.indication request id: 11 -> finished
14:10:09:708 APS-DATA.request id: 11 erase from queue
14:10:13:948 sensor 61 (lumi.vibration.aq1): disable vibration
14:10:14:548 Set sensor check interval to 1000 milliseconds

2/ Vibration detected at 14:13:11 and “disabled” at 14:14:16

14:13:10:109 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -69
14:13:10:111    asdu: 18090a05052300000700
14:13:10:114 Door lock debug 0x00158D00010FCC9D, data 0x0000000A 
14:13:10:116 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:11:211 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -70
14:13:11:214    asdu: 180a0a5500210100
14:13:11:217 Door lock debug 0x00158D00010FCC9D, data 0x0000000A 
14:13:11:219 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:11:748 Set sensor check interval to 100 milliseconds
14:13:14:748 APS-DATA.request id: 128, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:13:14:749    asdu (length: 5): 10EF000000
14:13:14:780 APS-DATA.confirm id: 128, status: 0x00 SUCCESS
14:13:14:781 APS-DATA.confirm request id: 128 -> erase from queue
14:13:14:793 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -69
14:13:14:794    asdu: 18ef010000001000
14:13:14:795 APS-DATA.request id: 128 erase from queue
14:13:14:797 APS-DATA.request id: 130, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:13:14:798    asdu (length: 5): 10F0005500
14:13:14:833 APS-DATA.confirm id: 130, status: 0x00 SUCCESS
14:13:14:836 APS-DATA.confirm request id: 130 -> erase from queue
14:13:14:844 aps request id: 130 finished, erase from queue
14:13:14:849 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -69
14:13:14:850    asdu: 18f0015500003900000000
14:13:18:718 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -69
14:13:18:720    asdu: 18140a050521e800
14:13:18:723 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:18:858 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -65
14:13:18:861    asdu: 18b50a050521e700
14:13:18:864 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:19:723 APS-DATA.request id: 153, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:13:19:726    asdu (length: 2): BF04
14:13:19:757 APS-DATA.confirm id: 153, status: 0x00 SUCCESS
14:13:19:776 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -66
14:13:19:778    asdu: bf00080402189c06ffff2e2100266db5feff504b80b60a25020146189c06ffff2e21001723d95e4438c1a405c925020142
14:13:19:780 APS-DATA.indication request id: 153 -> finished
14:13:19:781 APS-DATA.request id: 153 erase from queue
14:13:32:851 APS-DATA.request id: 208, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:13:32:853    asdu (length: 5): 10F1000000
14:13:32:883 APS-DATA.confirm id: 208, status: 0x00 SUCCESS
14:13:32:885 APS-DATA.confirm request id: 208 -> erase from queue
14:13:32:923 aps request id: 208 finished, erase from queue
14:13:32:947 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
14:13:32:949    asdu: 18f1010000001000
14:13:35:084 APS-DATA.request id: 219, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:13:35:086    asdu (length: 2): C006
14:13:35:120 APS-DATA.confirm id: 219, status: 0x00 SUCCESS
14:13:35:150 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -65
14:13:35:152    asdu: c000080602189c06ffff2e21008a41dccc8a38c1a4e1352502014c189c06ffff2e210045c2070aaa3eb07c89ab2502012f
14:13:35:154 APS-DATA.indication request id: 219 -> finished
14:13:35:156 APS-DATA.request id: 219 erase from queue
14:13:35:722 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -70
14:13:35:724    asdu: 18150a0b05290000
14:13:35:727 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:38:250 APS-DATA.request id: 235, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:13:38:253    asdu (length: 5): 10F2000000
14:13:38:282 APS-DATA.confirm id: 235, status: 0x00 SUCCESS
14:13:38:284 APS-DATA.confirm request id: 235 -> erase from queue
14:13:38:294 aps request id: 235 finished, erase from queue
14:13:38:302 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -65
14:13:38:303    asdu: 18f2010000001000
14:13:38:305 APS-DATA.request id: 237, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:13:38:306    asdu (length: 5): 10F3005500
14:13:38:336 APS-DATA.confirm id: 237, status: 0x00 SUCCESS
14:13:38:338 APS-DATA.confirm request id: 237 -> erase from queue
14:13:38:356 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -69
14:13:38:357    asdu: 18f3015500003900000000
14:13:38:358 APS-DATA.request id: 237 erase from queue
14:13:47:248 APS-DATA.request id: 19, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:13:47:251    asdu (length: 5): 10F4000000
14:13:47:283 APS-DATA.confirm id: 19, status: 0x00 SUCCESS
14:13:47:285 APS-DATA.confirm request id: 19 -> erase from queue
14:13:47:306 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -70
14:13:47:308    asdu: 18f4010000001000
14:13:47:309 APS-DATA.request id: 19 erase from queue
14:13:47:311 APS-DATA.request id: 21, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:13:47:312    asdu (length: 5): 10F5005500
14:13:47:348 APS-DATA.confirm id: 21, status: 0x00 SUCCESS
14:13:47:350 APS-DATA.confirm request id: 21 -> erase from queue
14:13:47:364 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -70
14:13:47:366    asdu: 18f5015500003900000000
14:13:47:367 APS-DATA.request id: 21 erase from queue
14:13:50:444 APS-DATA.request id: 35, addrmode: 0x03, addr: 0xA4C1388ACCDC418A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:13:50:446    asdu (length: 2): C100
14:13:50:502 APS-DATA.confirm id: 35, status: 0x00 SUCCESS
14:13:50:522 APS-DATA.indication srcAddr: 0x35E1, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -48
14:13:50:524    asdu: c1000e0002189c06ffff2e2100d0ea48acbc38c1a4b28005020100189c06ffff2e210095caef8aa538c1a40fd215020358
14:13:50:525 APS-DATA.indication request id: 35 -> finished
14:13:50:525 APS-DATA.request id: 35 erase from queue
14:13:53:874 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -65
14:13:53:876    asdu: 18b60a0000250a0400000000
14:13:53:879 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:13:54:065 APS-DATA.indication srcAddr: 0x0AB6, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -75
14:13:54:068    asdu: 08580a00002800
14:13:54:069 ZCL attribute report 0x804B50FFFEB56D26 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
14:13:54:072 APS-DATA.request id: 54, addrmode: 0x02, addr: 0x0AB6, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:13:54:074    asdu (length: 5): 10580B0A00
14:13:54:099 APS-DATA.confirm id: 54, status: 0x00 SUCCESS
14:13:54:101 APS-DATA.confirm request id: 54 -> erase from queue
14:13:54:124 aps request id: 54 finished, erase from queue
14:14:03:494 APS-DATA.indication srcAddr: 0xDFE3, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 172, rssi: -72
14:14:03:496    asdu: 185c0a00001001
14:14:03:500 ZCL attribute report 0x00158D0002A63B3F for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:14:05:274 APS-DATA.request id: 101, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:14:05:276    asdu (length: 5): 10F6000000
14:14:05:309 APS-DATA.confirm id: 101, status: 0x00 SUCCESS
14:14:05:311 APS-DATA.confirm request id: 101 -> erase from queue
14:14:05:324 aps request id: 101 finished, erase from queue
14:14:05:750 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -48
14:14:05:752    asdu: 18f6010000001000
14:14:05:804 APS-DATA.request id: 105, addrmode: 0x03, addr: 0xA4C1388ACCDC418A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:14:05:806    asdu (length: 2): C202
14:14:05:848 APS-DATA.confirm id: 105, status: 0x00 SUCCESS
14:14:05:868 APS-DATA.indication srcAddr: 0x35E1, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -48
14:14:05:869    asdu: c2000e0202189c06ffff2e21001e2541e06f38c1a4dba41202034e189c06ffff2e2100aa3eea22004b12005dc525020000
14:14:05:871 APS-DATA.indication request id: 105 -> finished
14:14:05:872 APS-DATA.request id: 105 erase from queue
14:14:08:857 APS-DATA.indication srcAddr: 0xDFE3, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 220, rssi: -74
14:14:08:860    asdu: 185d0a00001000
14:14:08:862 ZCL attribute report 0x00158D0002A63B3F for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:14:10:251 APS-DATA.request id: 126, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:14:10:254    asdu (length: 5): 10F7000000
14:14:10:284 APS-DATA.confirm id: 126, status: 0x00 SUCCESS
14:14:10:287 APS-DATA.confirm request id: 126 -> erase from queue
14:14:10:296 aps request id: 126 finished, erase from queue
14:14:10:305 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -66
14:14:10:307    asdu: 18f7010000001000
14:14:10:309 APS-DATA.request id: 128, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:14:10:310    asdu (length: 5): 10F8005500
14:14:10:345 APS-DATA.confirm id: 128, status: 0x00 SUCCESS
14:14:10:347 APS-DATA.confirm request id: 128 -> erase from queue
14:14:10:360 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -66
14:14:10:362    asdu: 18f8015500003900000000
14:14:10:363 APS-DATA.request id: 128 erase from queue
14:14:10:443 remove link for (35E1, C55D)
14:14:16:448 sensor 61 (lumi.vibration.aq1): disable vibration
14:14:17:048 Set sensor check interval to 1000 milliseconds

hiteule · May 10, 2025, 1:01pm

For comparaison, here is a log from a “real” event (I shook the sensor):

14:50:43:784 APS-DATA.request id: 9 erase from queue
14:50:45:077 APS-DATA.request id: 17, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:50:45:080    asdu (length: 5): 10C0000000
14:50:45:108 APS-DATA.confirm id: 17, status: 0x00 SUCCESS
14:50:45:110 APS-DATA.confirm request id: 17 -> erase from queue
14:50:45:144 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
14:50:45:146    asdu: 18c0010000001000
14:50:45:147 APS-DATA.request id: 17 erase from queue
14:50:45:749 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -65
14:50:45:751    asdu: 180d0a5500210100
14:50:45:755 Door lock debug 0x00158D00010FCC9D, data 0x0000000A 
14:50:45:757 ZCL attribute report 0x00158D00010FCC9D for cluster: 0x0101, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:50:46:248 Set sensor check interval to 100 milliseconds
14:50:50:248 APS-DATA.request id: 41, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:50:50:250    asdu (length: 5): 10C1000000
14:50:50:285 APS-DATA.confirm id: 41, status: 0x00 SUCCESS
14:50:50:287 APS-DATA.confirm request id: 41 -> erase from queue
14:50:50:295 aps request id: 41 finished, erase from queue
14:50:50:303 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:50:50:304    asdu: 18c1010000001000
14:50:50:306 APS-DATA.request id: 43, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:50:50:307    asdu (length: 5): 10C2005500
14:50:50:341 APS-DATA.confirm id: 43, status: 0x00 SUCCESS
14:50:50:343 APS-DATA.confirm request id: 43 -> erase from queue
14:50:50:357 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -67
14:50:50:358    asdu: 18c2015500003900000000
14:50:50:359 APS-DATA.request id: 43 erase from queue
14:50:52:262 APS-DATA.request id: 53, addrmode: 0x03, addr: 0xA4C1384D203DFAF4, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x04
14:50:52:264    asdu (length: 2): 9200
14:50:59:084 APS-DATA.request id: 81, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
14:50:59:087    asdu (length: 2): 9804
14:50:59:116 APS-DATA.confirm id: 81, status: 0x00 SUCCESS
14:50:59:138 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -67
14:50:59:139    asdu: 9800080402189c06ffff2e2100266db5feff504b80b60a25020144189c06ffff2e21001723d95e4438c1a405c92502013e
14:50:59:141 APS-DATA.indication request id: 81 -> finished
14:50:59:142 APS-DATA.request id: 81 erase from queue
14:50:59:249 APS-DATA.request id: 84, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
14:50:59:251    asdu (length: 5): 10C3000000
14:50:59:282 APS-DATA.confirm id: 84, status: 0x00 SUCCESS
14:50:59:285 APS-DATA.confirm request id: 84 -> erase from queue
14:50:59:300 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -65
14:50:59:301    asdu: 18c3010000001000
14:50:59:303 APS-DATA.request id: 84 erase from queue
14:50:59:305 APS-DATA.request id: 86, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 1 len: 5 tx.options 0x00
14:50:59:306    asdu (length: 5): 10C4005500
14:50:59:343 APS-DATA.confirm id: 86, status: 0x00 SUCCESS
14:50:59:346 APS-DATA.confirm request id: 86 -> erase from queue
14:50:59:360 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -65
14:50:59:361    asdu: 18c4015500003900000000
14:50:59:362 APS-DATA.request id: 86 erase from queue
14:51:02:668 APS-DATA.confirm id: 53, status: 0xA7 NO_ACK
14:51:02:670 max transmit errors for node 0xA4C1384D203DFAF4, last seen by neighbors 255 s
14:51:08:894 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -70
14:51:08:897    asdu: 183b0a050521e900
14:51:08:900 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:51:09:028 APS-DATA.indication srcAddr: 0x69AB, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -65
14:51:09:030    asdu: 18dd0a050521e800
14:51:09:033 ZCL attribute report 0xA4C13820522715A6 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:51:14:443 APS-DATA.request id: 150, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:51:14:446    asdu (length: 2): 9906
14:51:14:506 APS-DATA.confirm id: 150, status: 0x00 SUCCESS
14:51:14:520 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -67
14:51:14:522    asdu: 9900080602189c06ffff2e21008a41dccc8a38c1a4e1352502014b189c06ffff2e210045c2070aaa3eb07c89ab25020130
14:51:14:523 APS-DATA.indication request id: 150 -> finished
14:51:14:525 APS-DATA.request id: 150 erase from queue
14:51:17:352 APS-DATA.request id: 164, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:51:17:354    asdu (length: 5): 10C5000000
14:51:17:385 APS-DATA.confirm id: 164, status: 0x00 SUCCESS
14:51:17:388 APS-DATA.confirm request id: 164 -> erase from queue
14:51:17:404 aps request id: 164 finished, erase from queue
14:51:17:946 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
14:51:17:949    asdu: 18c5010000001000
14:51:22:748 APS-DATA.request id: 188, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:51:22:751    asdu (length: 5): 10C6000000
14:51:22:785 APS-DATA.confirm id: 188, status: 0x00 SUCCESS
14:51:22:787 APS-DATA.confirm request id: 188 -> erase from queue
14:51:22:801 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -67
14:51:22:802    asdu: 18c6010000001000
14:51:22:804 APS-DATA.request id: 188 erase from queue
14:51:22:805 APS-DATA.request id: 190, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 0 len: 5 tx.options 0x00
14:51:22:806    asdu (length: 5): 10C7005500
14:51:22:843 APS-DATA.confirm id: 190, status: 0x00 SUCCESS
14:51:22:846 APS-DATA.confirm request id: 190 -> erase from queue
14:51:22:855 aps request id: 190 finished, erase from queue
14:51:22:860 APS-DATA.indication srcAddr: 0x2C44, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -67
14:51:22:862    asdu: 18c7015500003900000000
14:51:24:750 APS-DATA.request id: 200, addrmode: 0x03, addr: 0xA4C1384D203DFAF4, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x04
14:51:24:751    asdu (length: 2): 9300
14:51:29:804 APS-DATA.request id: 221, addrmode: 0x03, addr: 0xA4C1388ACCDC418A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
14:51:29:806    asdu (length: 2): 9A00
14:51:29:837 APS-DATA.confirm id: 221, status: 0x00 SUCCESS
14:51:29:854 APS-DATA.indication srcAddr: 0x35E1, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
14:51:29:855    asdu: 9a000e0002189c06ffff2e2100d0ea48acbc38c1a4b28005020100189c06ffff2e210095caef8aa538c1a40fd215020358
14:51:29:857 APS-DATA.indication request id: 221 -> finished
14:51:29:859 APS-DATA.request id: 221 erase from queue
14:51:31:751 APS-DATA.request id: 231, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
14:51:31:753    asdu (length: 5): 10C8000000
14:51:31:792 APS-DATA.confirm id: 231, status: 0x00 SUCCESS
14:51:31:794 APS-DATA.confirm request id: 231 -> erase from queue
14:51:31:805 aps request id: 231 finished, erase from queue
14:51:31:811 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -65
14:51:31:812    asdu: 18c8010000001000
14:51:31:814 APS-DATA.request id: 233, addrmode: 0x03, addr: 0x04CF8CDF3C7E4BDC, profile: 0x0104, cluster: 0x000C, ep: 0x01 -> 0x15 queue: 1 len: 5 tx.options 0x00
14:51:31:815    asdu (length: 5): 10C9005500
14:51:31:847 APS-DATA.confirm id: 233, status: 0x00 SUCCESS
14:51:31:849 APS-DATA.confirm request id: 233 -> erase from queue
14:51:31:862 APS-DATA.indication srcAddr: 0x1DEC, srcEp: 0x15 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -64
14:51:31:864    asdu: 18c9015500003900000000
14:51:31:865 APS-DATA.request id: 233 erase from queue
14:51:31:998 APS-DATA.request id: 235, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0104, cluster: 0x0004, ep: 0x01 -> 0x01 queue: 1 len: 4 tx.options 0x00
14:51:31:000    asdu (length: 4): 11CA0200
14:51:32:037 APS-DATA.confirm id: 235, status: 0x00 SUCCESS
14:51:32:039 APS-DATA.confirm request id: 235 -> erase from queue
14:51:32:047 aps request id: 235 finished, erase from queue
14:51:32:052 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0004, lqi: 255, rssi: -69
14:51:32:054    asdu: 19ca022000
14:51:32:819 APS-DATA.request id: 241, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04
14:51:32:821    asdu (length: 2): 9400
14:51:32:865 APS-DATA.confirm id: 241, status: 0x00 SUCCESS
14:51:32:879 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8033, lqi: 255, rssi: -69
14:51:32:881    asdu: 940003000295caef8aa538c1a401060003189c06ffff2e21000195caef8aa538c1a401020703189c06ffff2e210001
14:51:32:882 APS-DATA.indication request id: 241 -> finished
14:51:32:883 APS-DATA.request id: 241 erase from queue
14:51:32:884 APS-DATA.request id: 243, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04
14:51:32:885    asdu (length: 2): 9502
14:51:32:928 APS-DATA.confirm id: 243, status: 0x00 SUCCESS
14:51:32:936 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8033, lqi: 255, rssi: -70
14:51:32:938    asdu: 950003020195caef8aa538c1a401040b03189c06ffff2e210001
14:51:32:939 APS-DATA.indication request id: 243 -> finished
14:51:32:940 APS-DATA.request id: 243 erase from queue
14:51:32:942 APS-DATA.request id: 245, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 6 tx.options 0x00
14:51:32:943    asdu (length: 6): 10CB08000000
14:51:32:977 APS-DATA.confirm id: 245, status: 0x00 SUCCESS
14:51:32:979 APS-DATA.confirm request id: 245 -> erase from queue
14:51:32:993 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -70
14:51:32:994    asdu: 18cb09000000001001002c01
14:51:32:995 APS-DATA.request id: 245 erase from queue
14:51:32:997 APS-DATA.request id: 247, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0104, cluster: 0x0702, ep: 0x01 -> 0x01 queue: 1 len: 6 tx.options 0x00
14:51:32:998    asdu (length: 6): 10CC08000000
14:51:33:033 APS-DATA.confirm id: 247, status: 0x00 SUCCESS
14:51:33:034 APS-DATA.confirm request id: 247 -> erase from queue
14:51:33:048 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -69
14:51:33:049    asdu: 18cc09000000002505002c010a0000000000
14:51:33:050 APS-DATA.request id: 247 erase from queue
14:51:33:052 APS-DATA.request id: 250, addrmode: 0x03, addr: 0xA4C138A58AEFCA95, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 12 tx.options 0x00
14:51:33:053    asdu (length: 12): 10CD08000505000805000B05
14:51:33:091 APS-DATA.confirm id: 250, status: 0x00 SUCCESS
14:51:33:093 APS-DATA.confirm request id: 250 -> erase from queue
14:51:33:109 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -70
14:51:33:110    asdu: 18cd0900000505210f00f401010000000805210f002c01010000000b052905002c010100
14:51:33:111 APS-DATA.request id: 250 erase from queue
14:51:35:154 APS-DATA.confirm id: 200, status: 0xA7 NO_ACK
14:51:35:156 max transmit errors for node 0xA4C1384D203DFAF4, last seen by neighbors 288 s
14:51:35:748 APS-DATA.request id: 6, addrmode: 0x03, addr: 0xA4C1388ACCDC418A, profile: 0x0104, cluster: 0x0004, ep: 0x01 -> 0x01 queue: 0 len: 4 tx.options 0x00
14:51:35:750    asdu (length: 4): 11CE0200
14:51:35:787 APS-DATA.confirm id: 6, status: 0x00 SUCCESS
14:51:35:789 APS-DATA.confirm request id: 6 -> erase from queue
14:51:35:803 APS-DATA.indication srcAddr: 0x35E1, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0004, lqi: 255, rssi: -49
14:51:35:805    asdu: 19ce021f01f0ff
14:51:35:806 APS-DATA.request id: 6 erase from queue
14:51:35:808 0xA4C1388ACCDC418A found group 0xFFF0
14:51:39:897 APS-DATA.indication srcAddr: 0xD20F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -70
14:51:39:899    asdu: 183c0a000025ab0000000000
14:51:39:902 ZCL attribute report 0xA4C138A58AEFCA95 for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
14:51:45:164 APS-DATA.request id: 47, addrmode: 0x03, addr: 0xA4C1388ACCDC418A, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
14:51:45:166    asdu (length: 2): 9B02
14:51:45:193 APS-DATA.confirm id: 47, status: 0x00 SUCCESS
14:51:45:212 APS-DATA.indication srcAddr: 0x35E1, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
14:51:45:214    asdu: 9b000e0202189c06ffff2e21001e2541e06f38c1a4dba41202033c189c06ffff2e2100aa3eea22004b12005dc525020000
14:51:45:215 APS-DATA.indication request id: 47 -> finished
14:51:45:216 APS-DATA.request id: 47 erase from queue
14:51:49:776 APS-DATA.request id: 68, addrmode: 0x03, addr: 0x60B647FFFE534A49, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:51:49:779    asdu (length: 5): 10CF000000
14:51:49:810 APS-DATA.confirm id: 68, status: 0x00 SUCCESS
14:51:49:812 APS-DATA.confirm request id: 68 -> erase from queue
14:51:49:884 aps request id: 68 finished, erase from queue
14:51:49:999 APS-DATA.indication srcAddr: 0x555F, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -48
14:51:49:001    asdu: 18cf010000001000
14:51:51:248 sensor 61 (lumi.vibration.aq1): disable vibration
14:51:51:848 Set sensor check interval to 1000 milliseconds
14:51:54:749 APS-DATA.request id: 90, addrmode: 0x03, addr: 0x04CF8CDF3C80394A, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
14:51:54:752    asdu (length: 5): 10D0000000

I hope it can help.

Smanar · May 11, 2025, 9:34am

Yes and not.

Ghost event

14:09:08:916 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -67
14:09:08:918    asdu: 18080a5500210100

Real event

14:50:45:749 APS-DATA.indication srcAddr: 0xFC40, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0101, lqi: 255, rssi: -65
14:50:45:751    asdu: 180d0a5500210100

180d 0a 5500 21 0100.
Command 0x0A > report.
Attribute 0x0055.
Data type 21 > U16.
Value 0x0001 > vibration.

As you can see the device realy make a report for vibration, a correct one, and the same for real and ghost event.
The problem is hardware or from setting for me. No battery issues ? have you tried to decrease the sensitivity ?

Perhaps it remake the request, waiting for a deconz answser ? But the timing is not regular …
You haven’t the problem on older version ?

But in all situation, it’s not “Ghosts” triggers, there is real ones.

manup · May 11, 2025, 11:47am

Indeed I think Smanar observation is correct, the device actually sends reports. Lowering the sensitivity should help.

The DDF default is the highest sensitivity of 2. Depending on the use case this may or may not be good. However it would be interesting to check what is the default initial value on the device.

hiteule · May 11, 2025, 12:39pm

Hi @Smanar , @manup ,

Thanks for the explanation. Indeed, this problem is a strange one.

The sensitivity was setup on 2 (high). I’ve just lowered it to 0 (low) to see if it help.

Also, the “ghost” events was not regular after a deconz log setup & restart as we can see in my previous message. Events seem a bit more regular after that but I don’t think we can deduce anything from that.
For example, since yesterday:

00:52:27
02:52:41
04:55:16
07:48:30
08:45:55
11:37:30
12:32:51
(Currently, the sensor is placed on a high shelf so that no-one can touch it.)

For me this issue appeared with the upgrade on 2.29.5 but I can’t prove it/ be sure because I don’t have a long enough history of this data.

Here’s what I plan to do in the next steps (one by one):
1/ Config the sensitivity to 0/low (done just now)
2/ Replace the CR2032 battery by a new one
3/ Downgrade deconz-rest-plugin on 2.28.1

I will keep you posted here.

BTW, since 2.29.5, I have other issue with Xiaomi device:

Xiaomi switch WXKG01LM disapears from Deconz after each reboot. I need to re-pair it every time.
Xiaomi electrical plug (ZNCZ04LM) activates itself after each reboot of Deconz.
Maybe some Xiaomi/Aqara specific workarounds has been removed/broken ?
This is just an hyppotesis, I need to test if this issues are still there with the v2.30.2.
I’ll open dedicated topics if necessary.

Anyway, thanks for your help, I really appreciate it !

manup · May 11, 2025, 12:46pm

Thanks for the input this really helps to figure this one out. Test with v2.30.2 would be appreciated. The WXKG01LM is my main switch in a room so far I haven’t seen issues but will double check.

One note for setting sensitivity. Ideally it’s set via REST-API, it may take up to one hour until it gets applied when the devices wakes up (on a hourly base) and the configuration is written.

bcutter · May 11, 2025, 1:05pm

Just a side note, as @hiteule is a lot more helpful than my own input: the behaviour definitely got introduced with the deCONZ update, as presented in Lumi.vibration.aq1 sensor with phantom triggers since deCONZ 2.29.5 e. g. with the before/after update comparison:

I just want to make sure we’re on the same page - and agree that if software changes and a change of behaviour appears, it’s rather not the hardware part.

Also for my most freaky vibration sensor, sensitivity is set to 0, as always:

{
    "capabilities": {
        "sleeper": true
    },
    "config": {
        "battery": 98,
        "duration": 65,
        "on": true,
        "reachable": true,
        "sensitivity": 0,
        "sensitivitymax": 2
    },

And still all events in the last 24 hours (with deCONZ v2.30.2) are false positives, 100 % phantom/ghost trigger events - meaning: no physical movement of the sensor has happened.

manup · May 11, 2025, 2:33pm

@bcutter how/on what does your event in HA trigger? Does it look at the vibration equals true attribute or only that any state* event from the sensor is arrived or state.lastupdated is new?

I’m asking because while looking at my sensor that the state.lastupdated is refreshed at some “random” points in time and a state event is fired on Websocket containing all attributes, but with vibration = false, which is correct so far.

This happens since the sensor sometimes sends a attribute report for the vibration strength attribute 0x0505 which then causes the state.vibrationstrength and state.lastupdated to be refreshed.

{
  "capabilities": {
    "sleeper": true
  },
  "config": {
    "battery": 100,
    "duration": 65,
    "on": true,
    "reachable": false,
    "sensitivity": 0,
    "sensitivitymax": 2
  },
  "ep": 1,
  "etag": "cb2fa554aee0f5582bab363ee1ea897d",
  "lastannounced": "2025-04-07T18:35:26Z",
  "lastseen": "2025-05-11T14:08Z",
  "manufacturername": "LUMI",
  "modelid": "lumi.vibration.aq1",
  "name": "Vibration 359",
  "nwkaddress": "0x107F",
  "state": {
    "lastupdated": "2025-05-11T14:08:22.100",
    "orientation": [
      1,
      1,
      89
    ],
    "tiltangle": 5,
    "vibration": false,
    "vibrationstrength": 6
  },
  "swversion": "0.0.0_0008",
  "type": "ZHAVibration",
  "uniqueid": "00:15:8d:00:02:af:95:f9-01-0101"
}

In the sniffer it looks like this:

The state.vibration attribute in my case stays false all the time unless I shake the sensor.

bcutter · May 11, 2025, 4:10pm

I only look at and presented the very basic binary_sensor.vibration_sensor entity state here which renders on which signals that vibration has been detected - which is obviously wrong. All the attributes don’t matter, as everything is being automated on the binary_sensor state (on|off).

Needless to say what users expect and how things should work: actual vibration → binary_sensor entity switching to on. No vibration: binary_sensor entity stays off. That’s the way it was working for years.

So I don’t know (watched/monitored the events for a while but could not catch a faulty vibration event [*]) why and tbh don’t understand that whole Websocket part which seems to have changed with the deCONZ update, I only know this behaviour has changed and the only component being changed is deCONZ

[*]

hiteule · May 11, 2025, 5:47pm

To add information, here is the payload of a “ghost event” I’ve just received from the websocket:

{
    "e": "changed",
    "id": "61",
    "r": "sensors",
    "state": {
        "lastupdated": "2025-05-11T17:31:47.041",
        "orientation": [
            1,
            0,
            89
        ],
        "tiltangle": 360,
        "vibration": true,
        "vibrationstrength": 14
    },
    "t": "event",
    "uniqueid": "00:15:8d:00:01:0f:cc:9d-01-0101"
}

Smanar · May 11, 2025, 6:01pm

And the switch is working fine ? It disconnect only if you reboot deconz ? Seem a database issue for me, device badly included, not saved.
For the plug, no idea ^^, and it’s not a zigbee setting like “state on power” as nothing is moving on the device.

About the sensor, just by curiosity, only on=true is moving ? I mean Tiltangle, orientation and VibrationStrenght not changing ?
They are not visibles on logs, not the same attribute, but it’s just to be sure.

ebaauw · May 11, 2025, 9:35pm

Did you check and double-check the battery? Aqara sensors tend to issue ghost events when the battery is low. Don’t rely on the value reported by deCONZ - this is extrapolated from the battery voltage reported by the sensor. Any value other than 100% is suspicious.

bcutter · May 11, 2025, 11:56pm

I certainly could check the batteries. But why should two vibration sensors start with ghost trigger events right after updating deCONZ. Software updates don‘t wear out sensor batteries, right.

Curious to see how things work once hiteule downgraded deCONZ.

hiteule · May 12, 2025, 8:46am

Hi,

Set the sensivity to 0 (low) via the rest api does not help.
I’ve just replaced the battery with a new one. Let’s see if it improve the situation.

In the meantime, I’m looking into how to downgrade deconz-rest-plugin to 2.28.1.
As I’m using the Home Assistant addon and I don’t have any addon backup, it sounds complicated

I’ll keep you posted.

manup · May 12, 2025, 9:54am

For a comparison I’m now running a test with v2.28.1 to see if there is any difference in sniffer or Websocket events. At least on first sight it looks identical

Out of interest which ConBee firmware versions are you running?

bcutter · May 12, 2025, 1:42pm

@hiteule without an addon backup there‘s not really a (safe) option. For sure one could access the container and manually export (backup) needed data like configs etc. (which ones?), then reinstall the addon from scratch with a forced older version (does supervisor allow this?) and try to manually restore the exported files - but I‘m not sure someone has ever done this or even succeeded in doing so. The HA deCONZ addon „is as it is“ - which is why such bugs introduced have such a huge negative impact. I‘d recommend to not play around with the addon to remain your data safe. And to create a backup (and to store it for long enough…).

hiteule · May 13, 2025, 12:45pm

Hi,

Well, since the replacement of the CR2032 battery yesterday morning… there is no more “ghost event” in the last 24h on my side.
I don’t know if it’s the fact that I “rebooted” the sensor (by changing the battery) or if the battery was “dead”.

I can’t understand why this problem appeared at the same time as the upgrade, it must be a simple coincidence.
I’m sorry to have bothered you, but I never imagined that the sensor could go “crazy”.

For the record, here is my setup:

Conbee 2
Firmware 26720700
Rest-plugin 2.30.2

bcutter · May 13, 2025, 1:17pm

Interesting. Did you measure the old battery‘s voltage externally?

Otherwise I‘ll do that for one or two of mine, even I think the battery has been replaced for one already a few months ago.

Can we make sure there‘s no monitoring bias with a battery replacement (like things happen or don’t happen within the first 24 hours)?

Still strange: same devices for several users went crazy right after a deCONZ update where the sensor‘s firmware, sensor‘s battery etc. does not change - only the connection is disconnected shortly and handled by a new deCONZ version.