Hi,
Question 1: Why nRF52832 not supporting Thread? Is it because Memory? Hardware?
Question 2: Can you advise what is the advantages or applications to use BLE+Thread and when BLE Mesh?
Thanks
Hi,
Question 1: Why nRF52832 not supporting Thread? Is it because Memory? Hardware?
Question 2: Can you advise what is the advantages or applications to use BLE+Thread and when BLE Mesh?
Thanks
Regarding Question 2, which I'll translate as "why would anyone want to use BLE+Thread when they could just use BLE mesh". . .
The Russian IoT article linked above does a good job of demonstrating the benefits of a true, IPv6, routing mesh (Thread) over a flooding approach (BLE mesh). Using both technologies concurrently gives you the best of both worlds -- the power, speed, robustness of Thread with the ubiquity of BLE for smartphone interoperability.
Certain applications where some of the network devices are mobile might also benefit from novel combinations of BLE and Thread -- most routing mesh networks aren't designed for constantly-changing topologies.
Regarding Question 2, which I'll translate as "why would anyone want to use BLE+Thread when they could just use BLE mesh". . .
The Russian IoT article linked above does a good job of demonstrating the benefits of a true, IPv6, routing mesh (Thread) over a flooding approach (BLE mesh). Using both technologies concurrently gives you the best of both worlds -- the power, speed, robustness of Thread with the ubiquity of BLE for smartphone interoperability.
Certain applications where some of the network devices are mobile might also benefit from novel combinations of BLE and Thread -- most routing mesh networks aren't designed for constantly-changing topologies.