Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Other How To

Introduction

ELK M1 Gold Cross Platform Control

One of the most valuable characteristics of building your own home automation system is the ability to personalize it by picking and choosing the devices that meet your needs. However, there are times when you require a product to perform a certain function and that product may not exist for the protocol of your choice.

The history of the X10 protocol dates back to the mid 1970s and X10 devices are still in production today. Throughout the lifetime of X10, engineers and hobbyists have created a large variety of device types from wall modules to light switches, motion sensors, water leak detectors, drive way sensors, and much more.

Eventually, we will probably see similar devices available that utilize the Z-Wave protocol. But until then, we can use existing X10 devices to meet our needs. How can we allow the different protocols to interact with each other? We do this by bridging the communication gap between the two protocols using a home automation controller.

The X10 protocol is known as a power line carrier (PLC) protocol and how it works is straightforward. In the United States, home-based power alternates current direction 60 times a second. Each time it changes direction the voltage at the point of change is zero. X10 sends data over the home's power lines as close to this point as possible.

By contrast, the Z-Wave protocol is known as a wireless mesh network protocol and it does not rely on the home's power lines to transmit data. Everything is transmitted using a radio frequency (RF) signal in the 908 MHz signal band.

So there is an obvious communications barrier between Z-Wave and X10! They not only speak different languages but they also use two very different methods of transportation. So how do we cross this barrier? By building a bridge using software or hardware. Basically we need something that speaks both protocol languages and provides a logic engine.

The inexpensive solution to this problem is to use a software product such as HomeZix or HomeSeer. You would then use a X10 PC controller such as the W800RF wireless X10 receiver or SmartHome PowerLinc PLC. Both of these X10 controllers communicate with the software using the computer's serial port.

You would also need a Z-Wave PC controller, which comes in many varieties including USB, serial, and Ethernet. HomeZix and HomeSeer both support speaking the X10 and Z-Wave language and they both have built-in logic engines.

More Stuff

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Featured Sponsors



Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I have forcedly installed merlinwrt on DSL edition of AC68U (don't judge me for bad purchase choices), of course I lost DSL functionality but that's o...
Go http://barwice.phorum.pl/viewtopic.php?p=13994#13994 to topSealy Posturepedic Citadel Hill Ultra Plush Euro Pillow case Top MattressAnother top sel...
All,I love AsusWRT Merlin and have used it for years. At present I would like to utilize AI Mesh. Unfortunately I have grown accustomed to having the ...
The short version of the story is that I have an OpenVPN client/server setup where the client is on cellular Internet (private IP) and the server has ...
Hello I am looking at two NAS Servers.The QNAP TS 251+ It Has the HDMI port and upgradable memory plus a lot of features. I was fixing to buy it when...

Don't Miss These

  • 1
  • 2
  • 3