Our Thread protocol products offer seamless Internet Protocol (IP)-based, mesh networking from sensor to cloud. They can be found in a variety of residential and commercial IoT applications such as:
- Low-powered smart home and building sensors
- Energy management (e.g., smart thermostats)
- Robust, wireless mesh or hybrid (wired/wireless) lighting solutions
As a Thread Group member, we are building solutions based on OpenThread, the proven, open-source implementation of the latest Thread specifications. The OpenThread stack sits on top of our 802.15.4 PHY drivers.
PIC32CX-BZ2 and WBZ45 Thread Early Access
To get started with Thread before the official release, simply add the early access software to your PIC32CX-BZ2 or WBZ45 device through our MPLAB® Harmony software development framework. The peripheral-rich, multi-protocol PIC32CX-BZ2 and WBZ451 MCUs already support Bluetooth® Low Energy 5.2, Zigbee® 3.0 and proprietary protocols, with Thread 1.3.0 coming soon. This early access program provides:
- A Thread stack (certification in progress) based on OpenThread
- Building Blocks: step-by-step instructions for creating the components of a Thread network
- Thread Software Development Kit (SDK) Reference Guide
Getting Started With Thread
Step 1
Get the WBZ451 Curiosity Board and any necessary third-party hardware.
Step 2
Set up your development environment.
Step 3
Explore the Thread documentation.
Step 4
Build and run your Thread network demo.
Thread’s low power consumption and mesh architecture make it a great choice for industrial automation, smart building and smart home applications.
Industrial Equipment
- Handheld equipment
- Pump and motor connectivity
- Meters
- Solar farms
- Electric Vehicle (EV) chargers
Building and Refrigeration Systems Control
- Compressor groups
- Condensers
- Walk-ins
- HVAC units
Home Automation
- Windows, doors and motion and temperature sensors
- System control and user interface panels
- Pool and spa controls
- Introduction
- Benefits
- Versus Zigbee®
What Is Thread?
With so many wireless connectivity protocols already available, you may wonder why Thread is necessary. Although there are many to choose from, none of them offer a solution that meets the unique demands of IoT design.
When working with most protocols, IoT projects are complex and riddled with challenges like interoperability, range, security, reliability and power usage. Because it is built on open and proven standards, Thread strives to solve these challenges and reduce the complexity of IoT development.
Built on open standards and IPv6 technology with the IEEE® 802.15.4 standard as its foundation, Thread is a mesh networking technology that offers many advantages over other protocols. Thread networks are secure, reliable, scalable and flexible.
With Thread, IoT developers can easily create applications that support large networks with many devices that need cloud access.
Benefits of Thread Networks
Interoperability
Thread strives to solve the interconnectivity challenges present in current IoT solutions. It is based on Internet Protocol (IP), which is the underlying technology that allows devices to talk to each other over the Internet. Because it uses an established and universal standard, Thread devices can connect to each other and the Internet quickly without the need for complex configuration.
Scalability and Reliability
Thread operates using a scalable mesh architecture (supporting up to 250 devices), which means that each device in the network can act as a router to forward messages to other devices. This allows the network to cover a large area and enables devices to communicate even if they are not within range of a direct connection.
Security
In addition to IP-addressable and mesh capabilities, Thread is known for offering security at every layer of the stack. These strong security measures protect against unauthorized access and tampering, ensuring that IoT devices and the data they transmit are secure.
Thread Versus Zigbee
When looking at capability, Thread and Zigbee appear to be interchangeable. They are both 802.15.4-based protocols that support a scalable mesh network architecture. Looking deeper at the underlying technology, you’ll find significant differences.
Open Standards Offer Seamless Interconnectivity
The primary difference between Thread and Zigbee is that Thread is IP based. Thread’s native IPv6 addressing simplifies the connection with other IP interfaces such as Wi-Fi® or Ethernet. Unlike Zigbee, Thread doesn’t require an additional “translator” device to communicate with other networks—Thread is built for effortless Internet connectivity.
Application Independence Future-Proofs Your Design
Thread’s independent application layer sets it apart from Zigbee and other 802.15.4-based protocols. Because Thread is application layer agnostic, IoT developers have the flexibility to change applications and cloud services without a major redesign.
User-Friendly Setup Makes It Easy to Add Security
Although both Zigbee and Thread offer robust security, Thread’s authentication and commissioning can be smartphone based, making it much easier and more user friendly than Zigbee for onboarding a new device.
