NXP Thread Commissioning Demo with Arrayent’s Cloud Control
- Thread devices can be monitored and controlled from anywhere in the world using Arrayent Connect Cloud
- Devices are easily commissioned onto a Thread network using NXP Thread App & QR code
- Devices are secure using Arrayent Unique ID (whitelisting) and AES-128 bit encryption.

This Demo Is Probably of Interest If You:
- Want to monitor and control Thread devices that sit behind a consumer grade firewall from anywhere in the world.
- Want to commission Thread devices in a easy way.
Differentiation This Demo Highlights
- Control and monitor Thread devices that sit behind a consumer grade firewall from anywhere in the world.
- Commission Thread devices using QR code
Description
The Thread network is managed by a LS1021A IT Gateway with FRDM-KW24 Thread Border border reference design. The board supports Thread, Wi-Fi, BlueTooth and NFC too.
NXP’s Thread commissioning android App discovers the Thread border router.
NXP powered Thread “device” is a card with a NXP Kinetis® KW2xD 802.15.4 Wireless chip with an ARM Cortex M4 MCU board running the Thread protocol and the lightweight Arrayent Connect Agent.
The Thread device boards are commissioned (or “paired”) on to the Thread network by using the NXP Thread commissioning Android App takes the device’s unique ID from the QR code on the device and pushes Thread network credentials into the device. This is shown again with a second card.
Arrayent’s Connect Agent has been pre-loaded into the device boards. And once the board is connected to the Thread network, the device board starts communicates directly to the Arrayent Cloud. Essentially key attributes on the board are presented up to the Arrayent Connect Cloud web services APIs.
The final step is to use the Arrayent devkit app to monitor and control the device board from anywhere in the world. In this case the we can demonstrate three monitor/control use cases:
1. Turn on and off the device LED from the mobile app.
2. Press a button three times to update the Apps button press counter (in this case three times.)
3. Push the board temperature to the mobile app.
What this Demo is All About
Video Link : 5310
Find more information
Press release: Read on The Business Journals
Blog posts to read:
NXP and Arrayent Collaborate to Connect Thread Devices at Embedded World, Nuremberg, Germany
Thread-Enabled Smart Home Powered by Arrayent
Demo Diagram

IoT Physical Components
Gateways
- SOC: NXP i.MX6 Applications Processor, NXP Kinetis®KW24D SoC
- Software: Embedded Linux, NXP Thread Stack for border router
- End User Products: LS1021A IT Gateway with FRDM-KW24 Thread Border border reference design
Edge Devices
- SOC: NXP Kinetis®KW24D (802.15.4 Wireless chip with an ARM Cortex M4 MCU)
- Boards/Modules: NXP FRDM-KW24D Development Board
- Software: Arrayent Connect Agent ported to the KW2xD, NXP Thread Stack for router end devices
Wireless Connectivity
- SOC: NXP Kinetis®KW24D (802.15.4 Wireless chip with an ARM Cortex M4 MCU)
Sensors
- SOC: KW24D On-chip Temperature, MMA8451Q 3-axis accelerometer
Cloud Infrastructure/Services
Smart Devices/Apps
- Software: Arrayent Android DevKit sample app and SDK
- Software: NXP Android Thread provisioning app
IoT System Capabilities
Device Management
- Each device is flashed at time of manufacturing a unique Arrayent Device ID and AES key. The device ID is bound to a specific customer account at time of device commissioning.
Cloud/App Communications/Interworking
- Arrayent devkit app talks to the Arrayent Connect Cloud’s device services interface through the Arrayent Connect Agent embedded software to connect to the device boards. The App is used to monitor and control the device board from anywhere in the world. In this case the we can demonstrate three monitor/control use cases:
- Turn on and off the device LED from the mobile app.
- Press a button three times to update the Apps button press counter (in this case three times.)
- Push the board temperature to the mobile app.
Security
- Arrayent uses device ID Whitelisting, that is Arrayent issued device ID is flashed into endpoint MCU memory at time of manufacturing. The per device unique ID is reserved in the cloud.
- Arrayent ACA embedded agent and ACC cloud services support AES-128 bit end-to-end encryption with dynamic temporal key refresh.
Analytics/Data
- The Arrayent Connect Cloud support