So here are some interesting tidbits from Nordic’s latest Thread SDK for the nRF52840. These are comments from various examples which are, in some case, experimental. They do demonstrate however, the possibilities:
* @brief Proximity Application and Thread CoAP Server main file.
*
* This application shows dynamic multiprotocol support for Thread and Bluetooth Low Energy.
* Thread operates on 802.15.4 radio during Bluetooth Low Energy radio's inactive time.
*
* This file contains is the source code for a sample proximity application using the
* Immediate Alert, Link Loss and Tx Power services.
*
* This application would accept pairing requests from any peer device.
*
* It demonstrates the use of fast and slow advertising intervals.
-------------------------------
* @brief Eddystone Beacon GATT Configuration Service + EID/eTLM sample application main file with Thread CoAP server dynamic multiprotocol.
*
* This file contains the source code for an Eddystone
* Beacon GATT Configuration Service + EID/eTLM sample application
* and Thread CoAP configuration and initialisation.
-------------------------------
* @brief Thread MQTT-SN Client Subscriber Example Application main file.
*
* @details This example demonstrates an MQTT-SN client subscriber application that
* provides resources to control BSP_LED_2 via MQTT-SN messages.
* It can be controlled by a board with related MQTT-SN client publisher application.
DISCLAIMER: This DOES NOT speak to how Particle will implement their Thread API 