Thread

[Yossi_Boran]

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

[Dmitry]

Hi,

1. Thread is based on IEEE802.15.4 network layer, nRF52832 doesn't support IEEE802.15.4

2. here adn here are good comparisons between Thread, Mesh and Zigbee

[Yossi_Boran]

Hi

But IEEE802.15.4 network layer I`ts just software, isn`t it? or it is also Hardware?

Thanks

[Dmitry]

It uses different type of modulation, that requires hardware support

[Yossi_Boran]

Thanks

[Rob C]

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.