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?
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.