Blog Post #1 - What is Z-Wave?

NOTE: For this first round of feedback, instead of creating a form, we are just going to have you comment in the thread to receive rewards points.

  • Specific Blog Questions = 10 points
  • General Feedback = 10 points

Please read this post if you haven’t already: Blog & Article Feedback Overview

We’d love to get your feedback on the blog below and have broken the feedback down into two sections: Blog Specific Questions & General Feedback

Specific blog questions:

  • From a high-level, does this blog answer the question, “What is Z-Wave”?
  • When you were researching Z-Wave, was there something about the technology that stood out to you as important and/or swayed your purchasing decision?
  • Similarly, why did you choose Z-Wave to power your smart home?

General Feedback:

Feel free to comment below anything you’d like to share (including spelling/punctuation errors). Does this article make sense? If you Google’d, “What is Z-Wave” and stumbled upon our blog, would you understand quickly what Z-Wave is? If not, how could we improve? Did you skim the article (it’s ok if you did) – if so, did you get what you wanted from it?


General Statement & Goal

All feedback is welcome and I promise you won’t hurt my feelings. The goal here is to pull from our community to create content that people actually want to read and will get a benefit from. There’s so many smart home blogs out there that can pump out generic content and pretend to know what they’re talking about. But that only goes so far.

We want engaging, relevant content that’s community driven so that when someone is new to the industry (like we all were at one time), they can easily digest topics to make educated decisions. In addition, we want to put out content for the people that have been around for a while and offer up more advanced blogs. To do that, we need you!

Lastly, the tone of this blog is written as if we’re talking to you. It’s not designed to be some keyword stuffy, dragged out article. It’s a little more professional than how I’d speak in the forums, but I’m also not writing a thesis, so keep that in mind :slight_smile:


Topic Data

Main Keyword: What is Z-Wave
Supplemental Keywords (ie: Long-tail): How does Z-Wave Work, Benefits of Z-Wave


Version 1

What is Z-Wave?

A beginner’s guide to understanding one of the most versatile and secure smart home protocols.

Written By: Eric H. - Founder, Inovelli

Z-Wave is one of the main smart home wireless communication protocols that power over 3,300 different products (100 million in the market) and are produced by hundreds of companies worldwide1. Known for its robust security features, mesh networking topology, interoperability (forward/backward compatible) and powerful firmware capabilities, Z-Wave has grown to be a fan favorite among smart home enthusiasts and security companies.

Below we’ll explore what Z-Wave is, how it works, and the key benefits.

What is Z-Wave?

Z-Wave is a wireless communications protocol (e.g., Bluetooth or Wi-Fi) used primarily for home automation that was originally founded as a lighting control system in 1999 by the Danish company Zensys. Today, Z-Wave is owned by Silicon Labs and over the years, Z-Wave has developed into much more than a lighting control system and the technology can be found in many smart home devices such as thermostats, light switches, wall plugs, outlets, sensors, and more.

Think of Z-Wave as the language used to connect two smart devices together. Similar to how your smart TV connects to your router to access the internet via Wi-Fi, or how your phone connects to your wireless headphones via Bluetooth to listen to music, Z-Wave connects smart home products together and allows them to communicate information, automations, and more which ultimately powers your smart home.

As with any language, there should be a set of rules and regulations as to how that language is written. For Z-Wave, those rules are set and enforced by the Z-Wave Alliance, which certifies every smart home device using the protocol, to ensure compatibility (Z-Wave calls it, “interoperability”) between the various versions of firmware. In other words, if you purchase a Z-Wave device that was developed in 2005, it should still be able to communicate properly with a device developed in 2021 and vice versa.

For more in-depth information about Z-Wave, feel free to check out the Z-Wave Alliance’s page about Z-Wave Technology.

How does Z-Wave Work?

Z-Wave primarily utilizes mesh networking technology to communicate between devices (shown in Figure 1.1). There is a new Long Range feature but we’ll discuss in a separate article.

Let’s go through the pre-requisites and a real-life example of how Z-Wave works in your home.

Before you get started, a hub or gateway that has a Z-Wave radio (e.g., SmartThings, Hubitat, etc) is required to establish this mesh and foster communication between devices. For more information about what hubs support Z-Wave and more about each of them, check out our article: (article to be released)

NOTE: Z-Wave devices will not pair directly to Amazon Alexa, Google Home, or Apple HomeKit as those gateway’s do not have a Z-Wave radio built-in.

Once you’ve acquired a hub and set it up, it’s time to add some Z-Wave devices. These devices can be any version of Z-Wave products (e.g., Z-Wave, Z-Wave Plus, 300 Series, 500 Series, 700 Series) as long as they’re certified (to check certification, please go here: Z-Wave Certified Products).

When you add a device, the terminology is called an, “inclusion” as you’re including the device to the network via the hub. As the product is being included, the hub assigns it a Node-ID, and simultaneously, the product sends information to the hub letting the hub know what type of product it is. The more products you add, the more Node-IDs are assigned. With the addition of every Node-ID, your hub creates an internal database and automatically determines the best route to take to reach one of the nodes.

For simplicity sake, all mains-powered (e.g., non-battery powered) devices will act as repeaters, which will help your mesh, whereas battery powered devices will not (to conserve battery power). So, make sure to have a good balance of mains-powered devices spread out across your house to help with the Z-Wave signal.

Figure 1.1 – Mesh Networking Examples (SmartThings User Interface Shown)

For a more in-depth look at how Z-Wave works (e.g., S2, Application Layers, Configuration parameters, associations, command classes, scenes, awake / listening node, sleepy node, OTA, mesh network, etc.), check out our article: xxxxxxxxx. Additionally, there is a great book I’d recommend, written by Dr. Christian Paetz, called, “Z-Wave Essentials” (Amazon).

What are the Benefits of Z-Wave

The three main benefits of Z-Wave are that it’s one of the most secure protocols in the market2, its radio signals operate outside of the 2.4GHz and 5GHz bands so it won’t interfere with your Wi-Fi signals, and lastly, it’s one of the more robust protocols from a firmware standpoint.

Security

Per the Z-Wave Alliance’s website, 90% of the North American security company’s (Alarm.com, Honeywell, 2GIG, ADT, Nexia) use Z-Wave’s technology in their products, allowing Z-Wave to dwarf all other technologies in this space2. Without getting too detailed, Z-Wave uses AES-128 encryption to protect data transmissions, making it so that it would take one billion years using, “brute force” via a supercomputer to crack the encryption key3. In 2017, Z-Wave introduced S2 (Security 2), which further protects devices during the inclusion process by using the Elliptic Curve Diffie-Hellman (ECDH) system to eliminate, “man-in-the-middle” attacks (i.e.: someone intercepting the authentication keys while you’re including a device).

For more detailed information about Z-Wave Security and S2, there’s a great article written by the Z-Wave Alliance here: https://z-wavealliance.org/sigma-designs-announces-advanced-iot-security-measures-for-the-smart-home/

Does Not Interfere With Wi-Fi

Today, more than ever, your Wi-Fi bandwidth is extremely important. At any given moment, you could have Netflix streaming, Amazon music playing, multiple phones/tablets surfing the net, and various other smart devices connected to your router. The last thing you want is to have is 100’s of smart home devices also connected, potentially causing traffic issues. Z-Wave is one of the only major protocols to operate outside the 2.4GHz and 5GHz bands (it operates on 908.42 MHz in North America and 868.42 MHz in Europe) allowing you to have your smart home on a completely separate frequency from your Wi-Fi devices.

Firmware Interoperability and Robustness

Regardless of the manufacturer and regardless of the year the Z-Wave enabled device was produced, Z-Wave products should work together seamlessly. This is one of the founding principles of the protocol and one of the special qualities of Z-Wave – interoperability. From a robustness standpoint, since this is a mature protocol, there is a lot manufacturers can do to give customers all sorts of customization options.

For example, our Red Series Dimmer Switch has some unique features such as allowing you to set the default level based on the time of day, adjusting min/max bulb values, multi-tap to activate a scene, LED bar notifications (e.g., lights up red if your alarm is not armed, flashes purple if severe weather is on the way, etc.), and much, much more4.

In summary, Z-Wave offers a lot of benefits such as security, robustness and is a protocol that is established, making it one of the leading choices in home automation, but it’s likely not on people’s radar as it’s not as mainstream as Wi-Fi and Bluetooth. Hopefully this article has helped bring some light (pun intended) to Z-Wave. We’ll be sure to post a more thorough article, walking through a more detailed approach to the protocol.

References:

  1. Z-Wave Alliance 2020 Ecosystem Report - https://z-wavealliance.org/wp-content/uploads/2019/06/Z-Wave-Alliance-2020-Ecosystem-Report-FINAL.pdf
  2. https://z-wavealliance.org/smart_security_with_z-wave/
  3. https://www.eetimes.com/how-secure-is-aes-against-brute-force-attacks/

Notes:

  1. Check to see if hub supports these advanced features as not all hubs do.

What is Z-Wave?

A beginner’s guide to understanding one of the most versatile and secure smart home protocols.

Eric H. - Founder, Inovelli

TO OUR FELLOW SKIMMERS: Read the TLDR below for a full article summary and/or the first italicized sentence(s) in each section for a summary of that topic.

TLDR: Z-Wave is one of the main smart home wireless communication protocols that powers over 3,300 different products (100 million in the market) and are produced by hundreds of companies worldwide1. Known for its robust security features, mesh networking topology, compatibility between manufacturers and firmware/hardware versions, as well as powerful firmware capabilities, Z-Wave has grown to be a fan favorite among smart home enthusiasts and security companies.

Below we’ll explore what Z-Wave is, how it works, and the key benefits.

What is Z-Wave?

Z-Wave is a wireless communications protocol (e.g., Bluetooth or Wi-Fi) used primarily for home automation, which is best known for its interoperability, (compatibility between multiple manufacturers, products, product versions, etc.) security, and ability to operate outside your Wi-Fi network.

Before being known as one of the main protocols in home automation, Z-Wave was created to be a lighting control system. Since then, Z-Wave has developed into much more and can be found in many smart home devices such as thermostats, light switches, wall plugs, outlets, sensors, and more.

Enabling devices to communicate, Z-Wave is a protocol that operates similar to how your smart TV connects to your router to access the internet via Wi-Fi, or how your phone connects to your wireless headphones via Bluetooth to listen to music. Z-Wave communicates information, automations, and more which ultimately power your smart home.

Large protocols require rules and regulations as to how that protocol is written. For Z-Wave, those rules are set and enforced by the Z-Wave Alliance, which certifies every smart home device using the protocol, to ensure compatibility (Z-Wave calls it, “interoperability”) between the various versions of firmware. In other words, if you purchase a Z-Wave device that was developed in 2005, it should still be able to communicate properly with a device developed in 2021 and vice versa. In addition, a Z-Wave device from Manufacturer A should work with a device from Manufacturer B and vice versa, allowing you to not be locked into one manufacturer’s ecosystem.

More Info: For more in-depth information about Z-Wave, feel free to check out the Z-Wave Alliance’s page about Z-Wave Technology.

How does Z-Wave Work?

Z-Wave works by utilizing a specialized hub/gateway (e.g., SmartThings, Hubitat, etc.) to create a mesh network of devices that communicate with each other over the lower frequency, 908.42 MHz (whereas your Wi-Fi operates on either the 2.4 GHz or 5 GHz band). Small data packets are transmitted to and from the hub across the mesh, allowing for better range and speed than its competing protocols.

Looking at one the main differences between Z-Wave and Wi-Fi, we’ll find that where your Wi-Fi signal degrades as you move further and further away from your router, Z-Wave, if built properly, can spread the signal evenly throughout your house and beyond by utilizing its mesh technology.

What is Z-Wave Long Range: We’ll explore this in another article as this new version does not use mesh technology.

Pre-req’s for Working with Z-Wave

  • Purchase a Z-Wave Hub (e.g., SmartThings, Hubitat, etc): a hub or gateway that has a Z-Wave radio (e.g., SmartThings, Hubitat, etc) is required to establish this mesh and foster communication between devices. For more information about what hubs support Z-Wave and more about each of them, check out our article: xxxxxxxxxxxx

NOTE: Z-Wave devices will not pair directly to Amazon Alexa, Google Home, or Apple HomeKit as those gateway’s do not have a Z-Wave radio built-in.

  • Z-Wave Certified Products: Make sure the device(s) you’re interested in is properly certified. This ensures it will work properly with your hub and with other Z-Wave devices. To check certification, please see this link: https://products.z-wavealliance.org/

Understanding Your Z-Wave Network

Starting with Z-Wave is actually quite simple once you understand the terminology and architecture. Each device is assigned a Node-ID from the hub when the device is initially included to the network. In addition, the device lets the hub know what kind of device it is (e.g., battery or mains powered, light switch or bulb, etc.). From there the hub creates an internal map that has the routes to/from each device optimized and every time a device is added or deleted, the hub will refresh that internal map along with refreshing at certain intervals to account for moving nodes.

Below shows how mesh networking works. As you can see, in the first example, the Z-Wave signal does not reach the switch. The way to solve this is to add an additional device to the network to relay the signal to/from the switch and hub as shown in the second example.


Figure 1.1 – Mesh Networking Examples (SmartThings User Interface Shown)
More Info: For a more in-depth look at how Z-Wave works (e.g., S2, Application Layers, Configuration parameters, associations, command classes, scenes, awake / listening node, sleepy node, OTA, mesh network, etc.), look for our article to be released in December 2021.

What are the Benefits of Z-Wave

The three main benefits of Z-Wave are that it’s one of the most secure protocols in the market2, its radio signals operate outside of the 2.4GHz and 5GHz bands (so it won’t interfere with your Wi-Fi signals), and lastly, it’s one of the more robust protocols from a firmware standpoint.

Security

Residential and commercial security providers (Alarm.com, Honeywell, 2GIG, ADT, Nexia) utilize Z-Wave technology in 90% of their products, allowing Z-Wave to dwarf all other technologies in this space2. Without getting too detailed, Z-Wave uses AES-128 encryption to protect data transmissions, making it so that it would take one billion years using, “brute force” via a supercomputer to crack the encryption key3. In 2017, Z-Wave introduced S2 (Security 2), which further protects devices during the inclusion.

More Info: For more detailed information about Z-Wave Security and S2, there’s a great article written by the Z-Wave Alliance here: https://z-wavealliance.org/sigma-designs-announces-advanced-iot-security-measures-for-the-smart-home/

Does Not Interfere With Wi-Fi

Especially today, more than ever, your Wi-Fi bandwidth is extremely important. At any given moment, you could have Netflix streaming, Amazon music playing, multiple phones/tablets surfing the net, and various other smart devices connected to your router. The last thing you want is to have is 100’s of smart home devices also connected, potentially causing traffic issues.

With Z-Wave being one of the only major protocols to operate outside the 2.4GHz and 5GHz bands (it operates on 908.42 MHz in North America and 868.42 MHz in Europe) it allows you to have your smart home on a completely separate frequency from your Wi-Fi network.

Firmware Interoperability and Robustness

Electing to make compatibility the backbone of the protocol, Z-Wave made it so that regardless of the manufacturer and regardless of the year the Z-Wave enabled device was produced, Z-Wave products should work together seamlessly. This is one of the founding principles of the protocol and one of the special qualities of Z-Wave – interoperability. Since this is a mature protocol, there is a lot manufacturers can do to give customers all sorts of customization options.

Robust products such as our Red Series Dimmer Switch have some unique features such as allowing you to set the default level based on the time of day, adjusting min/max bulb values, multi-tap to activate a scene, LED bar notifications (e.g., lights up red if your alarm is not armed, flashes purple if severe weather is on the way, etc.), and much, much more4.

You guessed it, Z-Wave offers a lot of benefits such as security, robustness and is a protocol that is established, making it one of the leading choices in home automation, but it’s likely not on people’s radar as it’s not as mainstream as Wi-Fi and Bluetooth. Hopefully this article has helped bring some light (pun intended) to Z-Wave. We’ll be sure to post a more thorough article, walking through a more detailed approach to the protocol.

References:

  1. Z-Wave Alliance 2020 Ecosystem Report - https://z-wavealliance.org/wp-content/uploads/2019/06/Z-Wave-Alliance-2020-Ecosystem-Report-FINAL.pdf
  2. https://z-wavealliance.org/smart_security_with_z-wave/
  3. https://www.eetimes.com/how-secure-is-aes-against-brute-force-attacks/

Notes:

  1. Check to see if hub supports these advanced features as not all hubs do.
1 Like

Some general feedback:

  • I don’t particularly like calling Z-Wave a language. I would use the term “protocol” instead to describe it.
  • I also didn’t feel like the “mesh” itself was particularly well described at all. Specifically, a sentence or two describing how meshing works (A device can communicate through another device to talk to it’s destination device) would have been helpful.
  • I think the section about Node-ID’s feels a little too simplified.

The more products you add, the more Node-IDs are assigned.

It seems better to just state that each device in the mesh has a unique Node-ID that other devices can use to identify and communicate with it.

Specific questions:

Yes, I think so. But it’s probably worth mentioning something about how Z-Wave is a low bandwidth protocol as well.

For me, the most important thing is that it’s low latency, low power, low bandwidth communication that is able to penetrate through walls better than Wi-Fi (because of the lower frequency) and is less prone to interference or interfere with Wi-Fi or Bluetooth.

I think I covered most of it in my previous answer, but I would also add the fact that I can choose the best devices from various manufactures and they all just work together seamlessly (unlike Zigbee where there don’t seem to be much standards) makes a huge selling point for Z-Wave.

3 Likes

:thinking: Did you leave that there for me to find? :laughing:

This was one of the biggest draws for me. I have 4 SSIDs at home with multiple access points so the 2.4 and 5GHz spectrum is busy.

Not sure if it’s worth mentioning but several vendors use QR codes to simplify inclusion. It makes it very easy.

1 Like

Wouldn’t this be ‘companies’ instead of company’s? Not much to add or note otherwise past the couple articles you’ve yet to write to link to :wink:

I’ll also echo zwave being off of the 2.4/5GHz ranges as being a motivating factor when I first started looking at products. I’ve since branched out but the vast majority of my devices are zwave.

1 Like

A few comments.

  1. Contrast with zigbee, which is clearly the other player in the mesh smarthome market.
  2. Should note that data transfer packet sizes are so small that bandwidth is not limited by lower frequency, lower frequency also gives you better range through walls/floors than 2.4ghz zigbee.
  3. Should definitely end with “Convinced? Here is a link to our z-wave line of products” unless this is solely intended to be an educational blog. Would make it easier to point people to product if you are basically trying to set apart your z-wave products from other smarthome offerings (bluetooth, wifi, zigbee, etc.)
1 Like

Z-Wave is one of the main smart home wireless communication protocols that power over 3,300 different products

I think it should be “that powers over 3,300 different products” because “power(s)” is talking about Z-wave, not the protocols mentioned in the prepositional phrase “of the main smart home wireless communication protocols”. It’s been a while since I’ve taken an English class, though, and I’m assuming the 3,300 figure is referring only to Z-wave.

Today, Z-Wave is owned by Silicon Labs and over the years, Z-Wave has developed into much more than a lighting control system and the technology can be found in many smart home devices such as thermostats, light switches, wall plugs, outlets, sensors, and more.

This feels like a bit of a run-on. Perhaps:

“Today, Z-Wave is owned by Silicon Labs and over the years, Z-Wave has developed into much more than a lighting control system. The technology can be found in many smart home devices such as thermostats, light switches, wall plugs, outlets, sensors, and more.”

When you add a device, the terminology is called an, “inclusion” as you’re including the device to the network via the hub.

The comma isn’t required before “inclusion” as the quotation marks aren’t being used for an actual quotation, but because you’re talking about the word “inclusion” in a meta way.

For a more in-depth look at how Z-Wave works…

Quite frankly, I can’t wait for this forthcoming article to arrive so I don’t need to buy a book to learn it. I consider myself a pretty technical person, and when I first got into Z-wave stuff (December 2020) I found myself lost in a lot of this terminology because I couldn’t find anything that laid it out in a straight-forward manner. Over the months I’ve gotten much more comfortable with it as I’ve read forums (such as this one) and dug into openzwave and zwavejs source code, but I don’t expect many people to do that. At least, that may be a barrier to entry for people who aren’t as technical as I am. Honestly, I’m still pretty foggy on Z-wave-native scenes. All of my “scenes” are managed by Home Assistant and I feel like there’s some native concept of scenes that Z-wave supports that I’m completely missing. Another thing I would have liked spelled out when I first got started was the relationship between the chip series and the protocol versions, and the benefits/features that came with those technology generations. Again, it’s something I picked up along the way, but only after a fair amount of digging because I was motivated to learn about it. A less motivated person might just throw their hands up and move on to something else.

its radio signals operate outside of the 2.4GHz and 5GHz bands so it won’t interfere with your Wi-Fi signals

Also in 2.4 GHz is Bluetooth and Zigbee, of course. And I imagine that a lot of people have more Zigbee around them than they realize, even though it’s in a proprietary manner they can’t control. For example, my Comcast cable box remote runs on Zigbee, as does my smart electric meter. So much stuff is on 2.4 GHz, it’s insane.

Here is my take on this. This is great if you are submitting a book report for school. On the web full of people with short attention spans and who rarely read much deeper than headlines, you are going to lose interest VERY quickly. It is overly technical and needlessly long.

The general breakdown of the sections are good, but I would cut at least 2/3’s of the words out of each section. Make is concise and laser-focused on why Z-wave is a benefit to the consumer without all the technical jargon they don’t care about. You can always link to the more in-depth data from your summary article (“click here to find out more details about Z-wave Security.”)

Given the hype around Matter, it might not hurt put some of this into context for beginners (potential series alert…). Something like this?

There can be an overwhelming amount information about starting a new smart home. You know the articles “Revolutionize your home with these five devices” or “Tech companies collaborate to create Matter”. What these articles fail to discuss is how everything connects, and why some things may work better than others. Let’s talk about some of these connections, and what may work best for your use case.

I would say yes, although I’d echo what someone else above said that both the intended audience and the level of detail appropriate to that audience might not match: if you’re just now learning that Z-Wave is a wireless communications protocol and the intent is to teach someone enough about it to make them feel comfortable purchasing such a device for their new smart home, perhaps the detailed history of the protocol and a reference to a book by a (I assume) Ph.D on the nitty-gritty of the protocol itself isn’t quite fitting. I do think this is good content — maybe it should be split out into an “advanced” article? It looks like there may already be plans for more detail on other topics.

Honestly, not much aside from the fact that it was one of two main protocols that my hub at the the time supported, and there were devices available for a reasonable-ish price that worked with it. (The hub was SmartThings v1, and the protocols were, of course, Z-Wave and Zigbee.)

Pretty much just the above. :slight_smile: And I didn’t really choose it, at least not it alone — it’s one of two major protocols I use, the other again being Zigbee. I actually decided to try to “standardize” on Zigbee first (no idea why other than perhaps that the ST sensors I bought with my hub bundle were Zigbee). I thought ST was special by supporting multiple protocols, and I only wanted to worry about one if I decided to ditch hubs. I figured most others would pick one protocol, which turned out not to be entirely accurate, but when I eventually did try to switch, I wish I had picked Z-Wave — as the article notes, this is much more interoperable, and the state of various Zigbee implementations were not as mature at the time, at least not until Hubitat came around. Home Assistant (ZHA and the libraries it relies on have matured greatly since then, plus things like Zigbee2MQTT and DeCONZ have been introduced and also work better now than anything did back then, and Vera/Ezlo supports more now than the dozen or so devices it used to … not sure about HomeSeer … but Z-Wave would still probably be a better luck; now I just happen to have Zigbee devices I prefer for other reasons, like the speed of motion detection, and my current home is a mix of both).

Here’s one I noticed:

Should be “For simplicity’s sake” (see: For simplicity's sake Definition & Meaning - Merriam-Webster).

Awesome, thanks everyone so far for the feedback – a good start and a lot of great ideas.

This is great feedback – I’ll expand a bit!

Excellent point, hadn’t thought about this tbh.

This is actually huge – and thinking back it’s one of the main reasons I went Z-Wave too. Thanks for sharing!

LOL, no for you to write!

Yeah that’s a good call-out. I’m not sure if this is prevalent in other protocols. QR Codes + SmartStart is pretty cool.

English was honestly my worst subject lol. Not kidding when I had to be put in a special tutoring class bc my mom was afraid I’d fail the writing portion of the SAT. I remember as a kid being so frustrated after writing reports for school only to have my mom redline the entire thing (she was great at English).

I’ll take your word for it and change it to companies lol!

I like these points, thanks Kevin!

Thanks :slight_smile: – you’re probably correct, as noted my proper English is terrible haha.

Love that version better, thank you!

Interesting, I never knew that. I’ve always put commas before quotes, even outside of actual quotations. Today I learned!

Yeah for sure – the book referenced in the blog is definitely heavy. I did learn a lot, but there’s also only so much you can understand when your background isn’t in coding and computer systems. Fundamentally, it makes sense, but having to explain it so that the masses can understand is a tough task. I’m looking forward to it though and will likely need a lot of help from Eric M and the community!

Oooo – that’s actually a great idea. Building on this, it would be nice to understand S0, S2, SmartStart, etc. I feel like they’re thrown around a lot in marketing material, but quite frankly, no one knows what they actually do (except for the power users who do their research).

@anon88759745 – can you add this to the list?

Very true – I have a report that I purchased a while ago that shows the percentage marketshare of the various protocols and ZigBee was #1 in the smart home market:

This was absolutely surprising to me – especially seeing Z-Wave so far down the list.

Thank you for saying this – it was the feedback I needed. Seriously.

I started to look at my reading habits and noticed that I skim everything. I typically read the first sentence of the section and if it captures my attention, I keep going… but even then, I skim. This is true on the blogs I read and even on social media when someone posts something that’s long, I either ignore it bc it’s too long, or skim it. Very rarely do I ever read an entire post or article and when I do read something in depth, it’s a book.

However, I know that there are people out there that like to read something to fully understand the concepts, which leads me to my point on this comment:

How would you feel if we did something like this:

  • At the top of the article is a TLDR (too long didn’t read for all you non-Reddit ppl), which is a summary of the article. 3-4 sentences tops.
  • Then under that is a disclaimer that each section will be summarized by the first 1-2 sentences that will be either bolded or italicized – the disclaimer will say something like, “for all you skimmers out there, look for the first 1-2 sentences in the various sections to get a summary”

This way we can target the skimmers like myself but also have enough content for the people who do want a more in depth idea of where the summary came from.

I do agree that I could cut out some more though.

Thanks a ton for having the guts to give some hard feedback – I really appreciate it!

Yeah I like this for sure – great idea!

Great feedback, I agree, we can tone it down a bit :slight_smile:

See, I knew we had some marketers in the community – always know your audience lol

What made you purchase SmartThings (or any hub for that matter)? Is that where you started (ie: dove directly into the hub route vs non-hub route)?

This is interesting too – I’ve always wondered how people land on a certain protocol or even understand there are protocols. When you purchased ST, did you know about the various protocols? What made you want to standardize on a protocol?

Sorry for the 3rd degree lol

I’m curious on this bc when I bought Wink (RIP) I didn’t even know about the protocols, I just purchased products that they advertised on their page bc I knew those products worked with the hub I bought. It wasn’t until I had such a crappy experience with lag times and called customer support (which was actually amazing during their prime) and the guy was like, “holy crap, you have 70+ devices? I’ve never seen that” and then explained to me the reason why I had issues was because my mesh was not great and I had mixed protocols. It was then that I realized there were various protocols and ultimately ripped out all my ZigBee stuff (nothing against it – the Quirky Tapts just sucked) and replaced with Z-Wave.

Thank you lol

1 Like

EnOcean! I remember reading about that years ago because a device manufacturer from my home town got onboard with EnOcean pretty early. I hadn’t really heard anything about it since the initial announcements, so I figured it just fizzled out. I’m super surprised to see it above Z-wave on that table. I guess it is mostly used in commercial applications?

Ha, yeah no clue – I’ve never heard of it either. This report is from January 2018 though, so who knows!

Oh, I just remembered a huge reason why I choose anything but Wi-Fi for as many smart home devices I can:

Having Internet-connected devices that don’t receive constant, timely security updates is a Bad Idea™ that’s bitten a lot of people.

https://westoahu.hawaii.edu/cyber/vulnerability-research/vulnerabilities-weekly-summaries/homehack-hacking-lg-smart-appliances/

https://www.ibm.com/downloads/cas/6MLEALKV

And many IP connected IoT manufactures don’t commit to providing security updates.

So, the more IoT-y stuff I can keep off of IP the better. Unfortunately, this probably means I’m going to steer clear of Matter, too.

1 Like

Thank you for the detailed write up. I’ve been using ZWave for years with ST and now HA without knowing how it worked. Please do more of these long format posts. As for why I use what I use - our house has ZWave, Zigbee and wifi-based smart devices. I favor the "Z"s for their isolation from wifi and the internet, but I’m not too selective about which “Z” I use. I have enough devices to support a robust mesh network within the house for both protocols.
\\Greg

You might also mention that a mesh network is improved by adding nodes, as opposed to the general sentiment that more devices means more network congestion.

3 Likes

Apparently, I tricked you. :rofl: I actually used to teach (at the college level; I’m not sure I would have survived to tell the story if the age group was any younger…), so I was just thinking of the background knowledge one might need, if any, and what gaps this is intending to fill. I’m sure your marketing people (person?) would have better ideas than me!

I guess I skipped a step: Philips Hue was my first smart home product, but at the time they had limited to no automation capabilities (still somewhat true, but at least they have remote control devices, motion sensors, and voice control — none of which existed back then, except maybe the schedules feature that they also now have). I wanted some way to automate this, and tried a couple ideas before landing on SmartThings since they had an integration and what I’d read about them suggested I could do motion lighting. (And I indeed could, but using the cloud became problematic…)

I really can’t remember but suspect it was reading the ST docs. (I know, I know: NERD! But Z-Wave and Zigbee were mostly what ST did at that time — way before Samsung bought them and convinced you that you wanted a smart fridge or whatever.) Some of them seemed similar in goal to the above: telling you at a high level how the protocols worked and how to build a mesh.

Specific Blog Questions

  • From a high-level, does this blog answer the question, “What is Z-Wave”?

Yes

  • When you were researching Z-Wave, was there something about the technology that stood out to you as important and/or swayed your purchasing decision?

What swayed me to Z-Wave over Zigbee or WiFi was lower frequency / high range and no interferance with WiFi benefits.

  • Similarly, why did you choose Z-Wave to power your smart home?

Same answer.

Feedback

In the “What is Z-Wave?” section, the parenthetical for interoperability is after the comma when it should be before. Also I appreciate the use of the oxford comma.

In the “How does Z-Wave Work?” section, I expected to see a note about the EU frequency. You did mention this further along in the article. I do feel that it would be an import caveat to the interoperability benefit though that the technology is not interoperable between US and EU.

In the “What are the Benefits of Z-Wave” section you have a stray integer.

in the market2

You can also mention that lower frequencies, like 908 Mhz have longer range using less energy than higher frequencies.
Fun fact: Cordless phones (Remember house phones?), some of them also use, in part, that frequency (Digital cordless phones that are not DECT, that is).

Another key advantage of Z-Wave is direct association: A switch can talk directly to an outlet or light bulb without the hub, once programmed that way.

2 Likes