Hi, I have been playing with mesh-cfgclient, and I've noticed that provisioning procedure gets stuck when node reports Public Key OOB information available' in 'Public Key Type' field of Provisioning Capabilities PDU. While digging into the code and API, I think we have a missing feature in the API between provisioner application and the daemon - while there is an API to deliver OOB keys to the daemon when *the application* is being provisioned, there doesn't seem to be a way to deliver provisioned device's public key when is the application who does the provisioning. Is my understanding correct, or is there something I've missed? regards -- Michał Lowas-Rzechonek <michal.lowas-rzechonek@xxxxxxxxxxx> Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND
