ivmarkov

Bluetooth (for now, the base driver and Classic BT on top but BLE is in the works too) is now exposed in `esp-idf-svc` mainline under the `experimental` feature flag. The...

@jasta I think we should first try to pull the BTP stack in `rs-matter` in a "non-trait" way so to say. I.e. with a structure that has a hard dependency...

Well, if you are a BLE expert, just go ahead, propose some traits, get some feedback and there we have it! Even better. If you can do it for Classic...

If most APIs in the wild are event driven and callback-based, shouldn't we - in the spirit of being minimalistic with the traits and allow the user to use these...

> > If most APIs in the wild are event driven and callback-based, shouldn't we - in the spirit of being minimalistic with the traits and allow the user to...

Sorry for the delay here. Completely busy with the `esp-idf-*` crates and `edge-executor` ATM. Will try to spend time on it tmr.

Maybe one early feedback I can provide still: the embedded community (especially the embassy one) is not too keen on using `alloc` where it can be avoided. Either by using...

I'm not sure I understand your difficulties with lifetimes and slices. Let's take `GattService` and [`GattCharacteristic`](https://github.com/jasta/ble-peripheral/blob/main/src/descriptors/gatt_characteristic.rs) as an example. These are just **metadata**. As such, the GATT server does not...

Forget about `vec!`. It allocates. [Here's how you should do it](https://github.com/ivmarkov/matter-rs/blob/main/rs-matter/src/data_model/cluster_on_off.rs#L51), and it works fine at least in `'static` context.

You can do it in non-static too, and yes, in that case you need to define the GATT characteristics first, and only after that the GATT service. That would be...