Krzysztof Kopyściński

@rymanluk @sjanc Rebased onto master, it's still required to pass these 4 tests. Retested and these are passing (SM/CEN/KDU/BI-02-C, SM/CEN/KDU/BI-03-C, SM/PER/KDU/BI-02-C, SM/PER/KDU/BI-03-C)

I guess it's not connection, but pairing request. Please take a look on `auth-passkey` command, in `btshell` app. It allows to reply to passkey request, so you can check how...

I created an issue to track problem with GAP/PADV/PASE/BV-01-C: https://github.com/apache/mynewt-nimble/issues/1512

this was superseded by https://github.com/apache/mynewt-nimble/pull/1549

this is WIP until EATT is merged

This was added to https://github.com/apache/mynewt-nimble/pull/1549

In current state it seems like we must do this, but maybe it's worth to add some flexibility as test groups? It would future proof overlay, as more test cases...

I think that if we want to check first bytes, from 0 to MTU-1, we could just check that in hdl_wid_52() i.e. using find() like so: ``` if value_read.find(MMI.args[1], 0,...

ok, makes sense

Maybe we should save flag if address is resolved:`LeAddress = namedtuple('LeAddress', 'addr_type addr', 'resolved')`, then by default: PTS_BD_ADDR = LeAddress(addr_type=0, addr='000000000000', resolved=False). And add flag to `set_pts_addr`, which may default...