Boris Zbarsky

Thank you. So looking at [ThreadAccessoryToggleErrorCLI-Log.txt](https://github.com/project-chip/connectedhomeip/files/8526755/ThreadAccessoryToggleErrorCLI-Log.txt) I see: 1. `sudo ./out/debug/chip-tool pairing ble-thread 1` which fails to actually commission the device: ``` [1650490471954] [25852:6806811] CHIP: [CTL] Successfully finished commissioning step...

Looking at the first log in this issue, it has a similar thing going on. It does not include the actual pairing command that was run, but then it has:...

@phonnakasturi-apple which exact example app (i.e. which path in the tree), built from which SHA is running on the Nordic board? Is it `examples/all-clusters-app/nrfconnect` or something else? And is it...

@phonnakasturi-apple My point is this: is it possible that we are talking to the wrong device during commissioning because there are multiple devices all powered on at once using the...

@phonnakasturi-apple So specifically, during a run that shows the failure the device is logging things as we go through the commissioning flow where it tells us it is in fact...

I don't think this test plan makes sense, sorry.... This test plan is expecting a DUT to "report" things... but why would a commissioner device do that in practice? Let's...

The test failures are somewhat real in the sense that we have tests that manually remove (some but not enough) retrans table entries and then send two messages in a...

I decided to fix the tests to make it look like a response from the server had in fact been received and just ignored at the data model layer instead...

> I currently do not believe we use bridge app at all ... unsure what the path forward is here, but at least this fixes paths. The path forward is...

In practice, the only place where really fishy stuff is going on at this point is in `SecureSessionMgr::SendEncryptedMessage`. So maybe this is not worth doing.... Here's my WIP for this...