Double attribute updates

[olavt]

Version

0.3.4

Node.js Version

N/A

Operating System

Docker

Issue Description

I'm getting double attribute updates for a specific attribute (not in general). I have verified with the chip-tool that the device only updates the attribute once.

How can I understand why this might happen when using the matterjs-server? I suspect it might be a bug somewhere.

Steps to Reproduce

Don't know how to reproduce.

server.log

Server Logs

Full log is attached. Here's an example from the log:


�[2m2026-02-03 17:47:17.370 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mSC/StandaloneAck �[0;34mid: �[35m@1:1•e69c⇵875b✉0849a1d0 �[34mtype: �[2;39m0x0/0x10 �[0;34macked: �[2;39m0a193b9e�[0m
�[2m2026-02-03 17:47:20.322 DEBUG  �[0;1;90mMessageExchange      �[0;90mNew exchange « �[35m@1:1•e69c⇵875d �[34mprotocol: �[2;39m1 �[0;34mpeerSess: �[2;39me69c �[0;34mSAT: �[2;39m4s �[0;34mSAI: �[2;39m2s �[0;34mSII: �[2;39m2s �[0;34mmaxTrans: �[2;39m5 �[0;34mMRP�[0m
�[2m2026-02-03 17:47:20.323 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mI/ReportData �[0;34mid: �[35m@1:1•e69c⇵875d✉0849a1d1 �[34mtype: �[2;39m0x1/0x5 �[0;34mreqAck size: �[2;39m43 �[0;34mpayload: �[2;39m152600de826ba83601153501260084c548bc37012402012403902404081822025885180018181824ff0c18�[0m
�[2m2026-02-03 17:47:20.326 DEBUG  �[0;1;90mMessageChannel       �[0;90mMessage » �[34mfor: �[2;39mI/StatusResponse �[0;34mstatus: �[2;39mSuccess(0x0) �[0;34msubId: �[2;39ma86b82de �[0;34mattr: �[2;39m1 �[0;34mid: �[35m@1:1•e69c✉0a193b9f �[34mtype: �[2;39m0x1/0x1 �[0;34macked: �[2;39m0849a1d1 �[0;34mreqAck size: �[2;39m8 �[0;34mpayload: �[2;39m1524000024ff0d18�[0m
�[2m2026-02-03 17:47:20.347 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1607000�[0m
�[2m2026-02-03 17:47:20.348 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1607000�[0m
�[2m2026-02-03 17:47:20.350 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1607000�[0m
�[2m2026-02-03 17:47:20.350 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1607000�[0m
�[2m2026-02-03 17:47:20.390 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mSC/StandaloneAck �[0;34mid: �[35m@1:1•e69c⇵875d✉0849a1d2 �[34mtype: �[2;39m0x0/0x10 �[0;34macked: �[2;39m0a193b9f�[0m
�[2m2026-02-03 17:47:22.339 DEBUG  �[0;1;90mMessageExchange      �[0;90mNew exchange « �[35m@1:1•e69c⇵875f �[34mprotocol: �[2;39m1 �[0;34mpeerSess: �[2;39me69c �[0;34mSAT: �[2;39m4s �[0;34mSAI: �[2;39m2s �[0;34mSII: �[2;39m2s �[0;34mmaxTrans: �[2;39m5 �[0;34mMRP�[0m
�[2m2026-02-03 17:47:22.340 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mI/ReportData �[0;34mid: �[35m@1:1•e69c⇵875f✉0849a1d3 �[34mtype: �[2;39m0x1/0x5 �[0;34mreqAck size: �[2;39m43 �[0;34mpayload: �[2;39m152600de826ba83601153501260085c548bc37012402012403902404081822021091180018181824ff0c18�[0m
�[2m2026-02-03 17:47:22.342 DEBUG  �[0;1;90mMessageChannel       �[0;90mMessage » �[34mfor: �[2;39mI/StatusResponse �[0;34mstatus: �[2;39mSuccess(0x0) �[0;34msubId: �[2;39ma86b82de �[0;34mattr: �[2;39m1 �[0;34mid: �[35m@1:1•e69c✉0a193ba0 �[34mtype: �[2;39m0x1/0x1 �[0;34macked: �[2;39m0849a1d3 �[0;34mreqAck size: �[2;39m8 �[0;34mpayload: �[2;39m1524000024ff0d18�[0m
�[2m2026-02-03 17:47:22.369 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1610000�[0m
�[2m2026-02-03 17:47:22.370 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1610000�[0m
�[2m2026-02-03 17:47:22.371 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1610000�[0m
�[2m2026-02-03 17:47:22.372 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1610000�[0m
�[2m2026-02-03 17:47:22.387 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mSC/StandaloneAck �[0;34mid: �[35m@1:1•e69c⇵875f✉0849a1d4 �[34mtype: �[2;39m0x0/0x10 �[0;34macked: �[2;39m0a193ba0�[0m
�[2m2026-02-03 17:47:24.362 DEBUG  �[0;1;90mMessageExchange      �[0;90mNew exchange « �[35m@1:1•e69c⇵8761 �[34mprotocol: �[2;39m1 �[0;34mpeerSess: �[2;39me69c �[0;34mSAT: �[2;39m4s �[0;34mSAI: �[2;39m2s �[0;34mSII: �[2;39m2s �[0;34mmaxTrans: �[2;39m5 �[0;34mMRP�[0m
�[2m2026-02-03 17:47:24.362 DEBUG  �[0;1;90mMessageExchange      �[0;90mMessage « �[34mfor: �[2;39mI/ReportData �[0;34mid: �[35m@1:1•e69c⇵8761✉0849a1d5 �[34mtype: �[2;39m0x1/0x5 �[0;34mreqAck size: �[2;39m43 �[0;34mpayload: �[2;39m152600de826ba83601153501260086c548bc37012402012403902404081822025885180018181824ff0c18�[0m
�[2m2026-02-03 17:47:24.363 DEBUG  �[0;1;90mMessageChannel       �[0;90mMessage » �[34mfor: �[2;39mI/StatusResponse �[0;34mstatus: �[2;39mSuccess(0x0) �[0;34msubId: �[2;39ma86b82de �[0;34mattr: �[2;39m1 �[0;34mid: �[35m@1:1•e69c✉0a193ba1 �[34mtype: �[2;39m0x1/0x1 �[0;34macked: �[2;39m0849a1d5 �[0;34mreqAck size: �[2;39m8 �[0;34mpayload: �[2;39m1524000024ff0d18�[0m
�[2m2026-02-03 17:47:24.380 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1607000�[0m
�[2m2026-02-03 17:47:24.380 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1607000�[0m
�[2m2026-02-03 17:47:24.381 DEBUG  �[0;1;90mPairedNode           �[0;90m@1:1 Trigger attribute update for 1.ElectricalPowerMeasurement.8 to 1607000�[0m
�[2m2026-02-03 17:47:24.381 DEBUG  �[0;1;90mWebSocketC~erHandler �[0;90mSending attribute_updated event for Node 1 1/144/8 1607000�[0m

Device Information

N/A

Additional Context

No response

Pre-submission Checklist

• I am running an Alpha/Beta version of the Matter.js server
• I have included the complete server logs (not truncated)
• I have checked existing issues to avoid duplicates

[Apollon77]

Should not happen. I will try to reproduce it