Led by Nest, ‘Thread’ for Home Automation is Most Promising IoT Standard Yet

Nest, Big Ass Fans and Yale Security are the three device manufacturers behind Thread, a new smart home technology for home automation. (no, the Thread icon isn’t a crooked ampersand. It’s a needle and thread.)

It’s hard to introduce a new “standard” for home automation or Internet of Things without being laughed out of the (enlightened) media, but this new protocol called Thread is the most exciting initiative I’ve seen since Z-Wave. And I’ve been doing this for 20 years.

That’s because Thread takes the most ubiquitous networking protocol on the planet – IP – and turns it into a mesh network to optimize coverage and performance. Specifically, Thread is based on 6LoWPAN, the low-power wireless protocol that delivers IPv6 over an 802.15.4 radio – the same radio used for ZigBee.

In addition to bringing mesh to 6LoWPAN, Thread adds a layer of security, enables point-to-point communications, and provides schemes for optimizing battery life.

Not coincidentally, Thread borrows from the (previously?) proprietary Nest protocol called Weave, which also is based on 6LoWPAN and also adds “special sauce,” the likes of which can be found in Thread.

Precious little has been written about Weave. A Google search reveals that I’m pretty much the only one that has covered it, albeit briefly.

Weave allows Nest thermostats to communicate with Nest Protect smoke/CO detectors over security- and communications-enhanced 6LoWPAN without the need for a Wi-Fi network.

In an interview with Thread representatives, Chris Boross, president of the Thread Group and technical marketing exec at Nest, stopped short of saying Thread is Weave. After all, he was representing Thread on the call and wanted to deflect attention from his own company.

“This is different from Nest Weave,” he says, but Weave “does run over Thread.”

The interview also revealed there were millions of Thread-enabled products already deployed. That would be the installed base of Nest thermostats and Protect sensors.

“Certainly there’s value in that,” says Kevin Kraus, treasurer of the Thread Group and director of residential product management for lock-maker Yale. “I think people see them [Nest] as one of the benchmarks.”

About Thread Technology

First, let’s get one thing clear: Thread addresses only the network layer of a home-control ecosystem, not the applications. So, while Thread-enabled products might be compatible, they won’t interoperate unless someone writes the rules or standards for devices to actually work together. More on that later.

The answer was “yes,” with several qualifications, especially in the areas of network range and power requirements.

The main case for Wi-Fi is that IP is so ubiquitous – built into phones, tablets, TVs, computers, routers, smart devices, etc. – that devices can connect without special gateways.

Now for the challenges … and Thread’s answers.

Gateways, Points of Failure

Thread addresses only the networking part of the stack.

CHALLENGE: Of all the protocols, Wi-Fi is the one that doesn’t require a special gateway to connect to other devices in the home and to the Internet. It all can be done over the standard home network through a router. (Bluetooth also is ubiquitous but it requires either a gateway or on-premise smart phone/tablet for Internet connectivity.)

When you think about other technologies such as Z-Wave and ZigBee, you need a special hub to connect to the Internet and (usually) to other devices in the home automation ecosystem. That hub can fail.

Likewise, even in the case of Wi-Fi, the home automation system falls apart if the home network goes down.

As Boross says, “If the Internet or network goes down, it’s important that devices can still talk to each other.” Indeed, Nest does that very thing with Weave.

In fact, users can commission and control Thread products in the home even if there is no Wi-Fi connection, thanks to support for peer-to-peer communications.

Power Demands
CHALLENGE: There’s a reason you don’t see Wi-Fi in many battery-powered devices such as door locks and sensors. Who wants to change the batteries every six to 12 months?

THREAD: 6LoWPAN, operating more efficiently over 802.15.4 radios, does a much better job in the power department but could still use some help, especially when it comes to a house full of security sensors.

Thread responds with “extensive support” for power optimization, according to Boross.

“It is designed for use cases like sensors,” he says. “Nodes are often chatty. We’ve gone to great lengths to minimize the network overhead outside of interesting traffic. We minimize the up time so the radio can sleep as much as possible.”

Battery life is one reason the Thread Group invited Yale, maker of ZigBee- and Z-Wave-enabled door locks, to the party.

“We were brought in because they wanted a company that had experience supporting these protocols, but was an expert in battery-powered products,” says Kraus.

He suggests that a mesh network can extend battery life because “the network is so much more robust [efficient] when there are multiple ‘parents.’”

“There is such a robust network, the lock should finally be able to sleep like it’s supposed to,” he says.

Range
CHALLENGE: Not being a mesh network, Wi-Fi (and 6LoWPAN) can be limited in range based on the strength of a home network and certain obstacles such as metal, mirrors and other unforgiving building materials.

THREAD: Not only does Thread add potentially unlimited range to a network through its mesh topology, it also includes self-healing and self-managing capabilities so that signals are delivered through the most efficient route at any given time.

Boross notes that a mesh network can get confused with so many nodes, but Thread allows users to remove and re-position devices at their whim, without the system skipping a beat.

Evolution of Thread

My personal opinion? Nest created Weave with every intention of turning it into an open standard that would work with its own devices and, eventually, millions of others. It’s good to have a standard when you lead the effort by a couple of years and millions of deployed devices.

In developing the “new” technology, Boross says of Thread, “It needs to be a low-power mesh network. Wi-Fi is great, but it should be a mesh to augment W-Fi.”

In addition, users should always have direct access to devices in the home, even if the network goes down.

The technology should be self-healing, secure and user friendly.

And, key to the success of the technology, it must be painless to implement.

“Thread amazingly does it all,” Boross says, with just a hint of sarcasm.

Indeed, Thread should enable fast time-to-market because it uses existing radio silicon (802.15.4) of which tens or hundreds of millions have already shipped. ABI Research estimates 850 million of the 2.5 GHz chipsets from multiple vendors will ship in 2016.

“We didn’t want to have to develop whole new hardware platforms or silicon to support a new mesh network,” Boross says. “Product development can start right now.”

In fact, for 802.15.4 products already deployed, a software update could render these devices Thread-friendly.

Another advantage of Thread is that it is “legacy-free,” Boross notes. “We had a clean sheet of paper. It only had to support itself. It does not require backward compatibility, except for IPv6.”

He says the group would have liked to use an existing home automation technology, but all of them had shortcomings.

Behind every successful custom installation is a CE Pro

And CEPro magazine is there keeping you up-to-date on the latest products, techniques, designs and business practices. From HDBaseT 2.0 to cat5e wiring, from UHDTV to wireless lighting control, CEPro explains how they work and how best to use them. Each issue delivers constructive, real-time content to help you find innovative ways to successfully build and maintain your business.

Discover how to make smart use of today's current technologies...and those that are emerging...subscribe today!

Article Topics

About the Author

Julie Jacobson, Co-Founder, EH Publishing / Editor-at-large, CE Pro

Julie Jacobson, recipient of the 2014 CEA TechHome Leadership Award, is co-founder of EH Publishing, producer of CE Pro, Electronic House, Commercial Integrator, Security Sales and other leading technology publications. She currently spends most of her time writing for CE Pro in the areas of home automation, security, networked A/V and the business of home systems integration. Julie majored in Economics at the University of Michigan, spent a year abroad at Cambridge University, earned an MBA from the University of Texas at Austin, and has never taken a journalism class in her life. She's a washed-up Ultimate Frisbee player currently residing in Carlsbad, Calif. Follow her on Twitter @juliejacobson. [More by Julie Jacobson]

4
Comments
(displayed in order by date/time)

Posted by Jeff Apcar on 07/16 at 02:04 AM

” but this new protocol called Thread is the most exciting initiative I’ve seen since Z-Wave. And I’ve been doing this for 20 years.”

You’ve not heard of RPL aka RFC 6550? A Low Power Lossy IP Routing Protocol that runs over 6LOWPAN and IEEE 802.15.4 for sensor networks?

Posted by Jim Hunter on 07/17 at 09:31 PM

It’s great to have a network stack that will be friendlier to battery life and mesh…but the biggest challenge still lies ahead..or above..at the application layer. IoT needs a language (grammar + dictionary) that is universally secure and interoperable…and lightweight enough for a simple sensor to speak.
Seems IoT should be Interoperable Things ... would speak more to the value proposition.

-Jim

Posted by Chris Raab on 07/25 at 02:24 PM

Nice to hear that IPV6LoWPAN has been announced by the “thread group”. At Loxone we implemented this technology and we have it available retail now! We call it Loxone Air and you can intelligently control everything under your roof with a single ap using Loxone.

Posted by Julie Jacobson on 07/30 at 11:08 AM

Other John—That is not really the case. They are already doing in-home communications via their own Weave protocol (6LoWPAN over 802.15.4), which I suspect is the exact same thing as Thread. The initiative, then, would be to add more in-home communicating devices to the ecosystem so no cloud is (necessarily) required.