Received general error status for protocol 0

[olavt]

Version

0.5.13

Node.js Version

N/A

Operating System

Docker

Issue Description

After updating to 0.5.13, I observed one device that does not seem to be responding seen from matterjs-server. The device main fabric / thread network is Apple Home and the device is working / responding as expected seen from Apple Home.

In the output of the docker logs command for the matterjs-server container, I see a lot of these on the console:

5540 Peer error (retry in 5m): [channel-status-response] (Failure (1) / InvalidParam (2)) Received general error status for protocol 0 (Sigma2(Resume))
2026-04-03 07:28:54.443 ERROR PeerConnection @1:4 udp://[fddc:995a:e204:0:b9d3:84eb:b1d:e7c]:5540 Peer error (retry in 5m): [channel-status-response] (Failure (1) / InvalidParam (2)) Received general error status for protocol 0 (Sigma2(Resume))

Steps to Reproduce

Not sure how to reproduce.

Server Logs

The server log file is attached.

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]

Please add more log, ideally use the matter server dashboard upper right to temproarily enable debug log and then let it run some time and post this as log.

"InvalidParam" retuend from devices should normally mean that they are not happy with the data we send for our fabric on a Session resumption ...

[olavt]

The attached log should be with the --log-level debug option. I always run with it.

[olavt]

For some reason I get "Failed to upload server.log", when trying to attach it.

[Apollon77]

try again? Or if too big zip it

[olavt]

server.log.zip

[Apollon77]

There is indeed something strange ... fixing it

[Apollon77]

@olavt could it be that the above log is filtered? I miss many loglines, especially EROR OR WARN that are usually there?

Otherwise I verified anything here and i can not find any bug on our side. The Sigma 1 message is valid and there is also in the chip SDK nothing that should cause an InvalidParam for our message we send. So something happened with that device. I would recommission it. nothing I can do