Josh Guilfoyle

I think I might want to rework this a bit so that there's only one struct, EspDppBootstrapped, and that the borrow of EspWifi only occurs during the constructor. This way...

Actually I just realized that if I do this so that EspWifi isn't borrowed for the lifetime of the object that handles esp_supp_dpp_init/deinit then we could end up unsafely accessing...

Ackd, I think the right compromise here is to have a member of EspWifi that you can borrow to access esp_supp_dpp_*. I'll still keep the code in wifi_dpp.rs so it's...

Oh and I'd like some advice on the example I originally had. Can't get it to compile because it needs sdkconfig values and some other project weirdness. Is it preferable...

Thanks, I'll iterate a bit on my end and update the PR when it's ready for you to look again. FWIW, the DPP lifecycle is pretty mysterious from the documentation...

@ivmarkov, updated as an RFC with a few caveats: 1. Turns out the feature is very flaky upstream and requires https://github.com/espressif/esp-idf/pull/10865 to be reliable at a minimum. The code "works"...

@ivmarkov i think your above comment was from a different issue I filed. On my mobile now and can't find the link easily but it relates to building esp idf...

No worries, I understand the need to take this slow on new APIs, especially since it's not cut and dry how exactly to port C APIs to Rust idioms. Also...

> - I am not sure whether Bluetooth provisioning is optional or a core requirement of the Matter specification. Bluetooth on ESP32 is supported, but uses an extreme amount of...

This feels important for rs-matter as we'll need a generic way to talk about BLE to support BTP in a reusable way. If there's sufficient interest in helping get the...