Hi,
I see the Matter CHIP integration uses BLE for commissioning, so to advertise a ble service the documentation advises to use NUS.
What about scanning for ble devices and connecting to them?
Hi,
I see the Matter CHIP integration uses BLE for commissioning, so to advertise a ble service the documentation advises to use NUS.
What about scanning for ble devices and connecting to them?
Hi,
You can use the CHIP Tool to scan and commission. See Working with the CHIP Tool.
Regards,
Amanda H.
No, I meant I need to scan for ble devices from the nrf5340 and connect to them.
So if I want to add support for different peripheral ble devices with other UUIDs I have to add a class and modify some code inside the ble_providers?
You could add into https://github.com/nrfconnect/sdk-nrf/blob/v2.5.0/applications/matter_bridge/src/app_task.cpp#L67-L72
-Amanda H.
The bridge sample uses WIFI for Matter, what about using Thread?
I've been having issues enabling it, as it causes the build to require multiprotocol_rpmsg child image so after adding the multiprotocol's .conf and CmakeLists line from the weather station sample it builds and I start getting the -5 error again. I tried to add CONFIG_BT_CENTRAL=y to the conf of multiprotocol but then it overflows the flash by 23488 bytes.
From what I can see there is no example of CHIP + Thread + BLE scan right?
Hi,
sfemat said:The bridge sample uses WIFI for Matter, what about using Thread?
The Matter Bridge features only support matter applications.
sfemat said:I've been having issues enabling it, as it causes the build to require multiprotocol_rpmsg child image so after adding the multiprotocol's .conf and CmakeLists line from the weather station sample it builds and I start getting the -5 error again. I tried to add CONFIG_BT_CENTRAL=y to the conf of multiprotocol but then it overflows the flash by 23488 bytes.
What sample are you using? What do you enable?
Are you testing the Matter bridge application? If so, it doesn't require extra configs unless you want to modify the connection numbers.
sfemat said:From what I can see there is no example of CHIP + Thread + BLE scan right?
Unfortunately, there is no such example as your requirement.
Regards,
Amanda H.
I'm testing the Matter Bridge application and trying to add Openthread as the transport of Matter instead of WIFI, but when I do it errors out with the usual uknown hci command.
Here is where I try to enable thread:
CONFIG_CHIP_WIFI=n CONFIG_NET_L2_OPENTHREAD=y CONFIG_NET_SOCKETS=y CONFIG_NET_SOCKETS_POSIX_NAMES=y CONFIG_NETWORKING=y CONFIG_OPENTHREAD_COAP=y CONFIG_OPENTHREAD_MANUAL_START=n CONFIG_OPENTHREAD_FTD=y CONFIG_OPENTHREAD_NORDIC_LIBRARY_FTD=y CONFIG_OPENTHREAD=y
I'm not sure if it means that this configuration is not yet supported or there is a bug. I suspected it could be the multiprotocol child image not having the central functionality activated, but with the overflow reducing its size by that much seems unfeasible.
I'm testing the Matter Bridge application and trying to add Openthread as the transport of Matter instead of WIFI, but when I do it errors out with the usual uknown hci command.
Here is where I try to enable thread:
CONFIG_CHIP_WIFI=n CONFIG_NET_L2_OPENTHREAD=y CONFIG_NET_SOCKETS=y CONFIG_NET_SOCKETS_POSIX_NAMES=y CONFIG_NETWORKING=y CONFIG_OPENTHREAD_COAP=y CONFIG_OPENTHREAD_MANUAL_START=n CONFIG_OPENTHREAD_FTD=y CONFIG_OPENTHREAD_NORDIC_LIBRARY_FTD=y CONFIG_OPENTHREAD=y
I'm not sure if it means that this configuration is not yet supported or there is a bug. I suspected it could be the multiprotocol child image not having the central functionality activated, but with the overflow reducing its size by that much seems unfeasible.
The Matter Bridge application doesn't support Openthread-based platforms.
The main use case for the bridge is to allow integrating the already existing network with Matter. We decided that the Wi-Fi solution covers more use cases, as Thread requires adding additional border router to the network, which was reported to be a problem for some of the existing networks.