Closed ivmarkov closed 1 month ago
Update: The PR accidentally also contains a small fix for the timeout in ms after which the stack is considered busy and an incoming message is answered with a "busy" status rather than handled in a regular manner.
The fix makes the timeout a parameter, raises it from 200 to 500ms and most importantly - fixes its handling logic, as there was a weird / 2
copy-paste bug, which further lowered the timeout to 100ms, which is too small for MCUs.
Accidentally, I ended up in a noisy network setup with all the UDP extras: delayed packets, lost packets, all of it.
This uncovered a couple of bugs, fixes for which I'll be PR-ing shortly.
But first, a PR that logs extra identification for each exchange:
u16
Matter one which is shared between the local and remote session)