Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IEEE802154 + BLE - Coex? #3239

Open
ivmarkov opened this issue Mar 8, 2025 · 0 comments
Open

IEEE802154 + BLE - Coex? #3239

ivmarkov opened this issue Mar 8, 2025 · 0 comments
Labels
status:needs-attention This should be prioritized

Comments

@ivmarkov
Copy link

ivmarkov commented Mar 8, 2025

Motivations

The subject is the TL;DR.

The elaboration is that when provisioning a Matter node, the node might, or might not run the BLE and the IEEE802154 (or Wifi) radios simultaneously.

While the Matter spec had taken special precautions to support devices that do not allow for BLE + "the other radio" coex (the so called "Non-concurrent Commissioning Flow"), these precautions are not always working across all Matter controllers.

For example, Alexa does not really support the non-concurrent commissioning flow.

Solution

From an API standpoint:
Something similar to what is implemented in esp-wifi in terms of the esp_wifi::init function: i.e. you initialize something once only, by passing it the RADIO_CLK periph as well as a timer periph, and then you can immutably borrow the initialized something when instantiating the BLE, the Wifi, and (in future) the Ieee802154 radio.

Of course that would mean that the Ieee80215 driver/crate would need to depend on the esp-wifi crate, or the "init" magic needs to be moved to somewhere else (esp-hal?).

From an implementation standpoint, I have no idea if the coex between BLE and IEEE802154 is feasible, but I guess it is not completely out of reach, given that ESP-IDF is implementing it.

Alternatives

Use non-concurrent commissioning with Matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-attention This should be prioritized
Projects
Status: Todo
Development

No branches or pull requests

1 participant