can i connect iot sensor node nrf52 thingy to another nrf52 soc via ble or IEEE 802.15.4 and access it on cloud
can i connect iot sensor node nrf52 thingy to another nrf52 soc via ble or IEEE 802.15.4 and access it on cloud
Hello,
As Krzysztof well described above, we made a demo where we connected nRF52 Thingy to the internet via Thread network. Unfortunately, we don't have specific date on which we will release this example.
When it comes to technical side, we modified nRF52 Thingy to act as Bluetooth Central rather than Bluetooth Peripheral. The device automatically scanned for devices that advertise Nordic UART Service UUID (NUS), and connected to them.
On the Bluetooth Peripheral side, we have used Dynamic Multiprotocol CoAP Client + NUS example from nRF5 SDK for Thread. We have modified the NUS RX handler to accept all sort of different commands. Whenever nRF5 Thingy wanted to report e.g. change of the temperature, it sent data over NUS in some predefined format. Then the BLE/Thread device translated it to the CoAP Message and sent it to the cloud, using Thread Network (so it acts as a gateway/translator).
The same approach can be taken in your application. Unfortunately, there is no support for MQTT at the moment in the SDK. However we plan to add support for MQTT-SN protocol in the next release of nRF5 SDK for Thread.
Hello,
As Krzysztof well described above, we made a demo where we connected nRF52 Thingy to the internet via Thread network. Unfortunately, we don't have specific date on which we will release this example.
When it comes to technical side, we modified nRF52 Thingy to act as Bluetooth Central rather than Bluetooth Peripheral. The device automatically scanned for devices that advertise Nordic UART Service UUID (NUS), and connected to them.
On the Bluetooth Peripheral side, we have used Dynamic Multiprotocol CoAP Client + NUS example from nRF5 SDK for Thread. We have modified the NUS RX handler to accept all sort of different commands. Whenever nRF5 Thingy wanted to report e.g. change of the temperature, it sent data over NUS in some predefined format. Then the BLE/Thread device translated it to the CoAP Message and sent it to the cloud, using Thread Network (so it acts as a gateway/translator).
The same approach can be taken in your application. Unfortunately, there is no support for MQTT at the moment in the SDK. However we plan to add support for MQTT-SN protocol in the next release of nRF5 SDK for Thread.
I am wondering how hard these changes to the Thingy52 would be, to change it from a peripheral to a central. or how ineffective it would be to use thread + BLE central at the same time.
Thanks for any answer in advance.