You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[zephyr] Added several improvements to the BLEMgr implementation (project-chip#33189)
* [zephyr] Enabled support for bonding in the BLEManager
Currently the Zephyr BLE Manager rotates Bluetooth addresses
on every boot and it does this by creating new Bluetooth identity.
Because of that the Zephyr stack does not create default Bluetooth
ID, which is required e.g. for the bonding purposes.
Added creating two separate Bluetooth identities - for the Matter
service advertising and for the bonding purposes.
Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no>
* [zephyr] Added check to drop handling callbacks for BT central
Matter BLEManager handles all BT connect and disconnect callbacks
no matter if these are Matter related ones or not. It collides
with other not Matter-related services that trigger Matter
CHIPoBLE service advertising changes. Added role check that
allows to at least drop all callbacks related to BT central role.
Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no>
* [zephyr]: allow BLE advertising restarts
* allow BLE advertising restarts in case of failures
* which can be triggered by calling SetBLEAdvertisingEnabled(true)
ConnectivityMgr public API from the application code
* do not register CHIPoBLE GATT services when the advertising
cannot be started
* this allows the disconnection handler to filter out non-Matter
BLE connections that were terminated
* fix possible underflow of connection counters
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
---------
Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no>
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
Co-authored-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
0 commit comments