The device responds with a PairRandomSend before PublicKeySend. Due to accepting PairRandomSend the implementation moves to a faulty state of the implementation where it is not able to complete pairing.

The specification clearly shows the protocol flow in the standards but it does not explicitly state how to handle out-of-order protocol messages. Hence, this behavior can be attributed to under specification of the standards.