FAQ's
Z-Wave FAQ
FAQ - Frequently Asked Questions
This section discusses very general questions. For more specific information see:
FAQ - How to Setup a Simple Network
ACT is a leading designer and manufacturer of LED lighting products, lighting controls, and signal level communications modules for commercial and industrial building management systems. Established in 1987 and based in
ACT believes customers are best served by firms who are directly involved with both the design and production of cost effective products. International capabilities have conscientiously been developed, including product engineering, manufacturing facilities and parts sourcing. ACT has a breadth of expertise in control communication technologies including, LonWorks, BACnet, X-10, Z-wave, Zigbee and other network protocols.
ACT can provide custom products, specialty devices, design and manufacturing services.
While ACT warrants its products for 2 years, that warranty is for workmanship and materials of the products themselves. We cannot warrant the installer’s experience in electrical concepts, wiring practices, their knowledge of the HPW products nor their design and troubleshooting skills. Please be advised that although most Z-Wave systems work flawlessly and without incident, there are many conditions beyond ACT’s control that can greatly influence the overall performance of any system that communicates via radio signals.
If you do require support, please read through this Frequently Asked Questions (FAQ) for specific areas before seeking assistance. If the products were purchased through a dealer, local representative or distributor, please call their technical support line for assistance. ACT offers technical support only for those companies who purchase direct. If appropriate, email ACT for assistance (act_custserv@act-solutions.com). ACT charges a 25% restocking fee on all returns. All items must be returned to ACT in original condition and be accompanied by an RMA (Return Merchandise Authorization) number.
You can download our terms and conditions from our website at:
You can download ACT's RMA form at:
The section above discusses questions on ACT. See also:
FAQ – Z-Wave Basics
FAQ - How to Setup a Simple Network
FAQ – Z-Wave Basics - Back to Top
From a user’s point of view, Z-wave is simply an RF protocol that allows many different companies to design and manufacture products that will work together in a home automation (or light commercial automation) system.
Q: Will all products from all the partner companies, work together?
A: Interoperability continues to be one of the main goals of all Z-Wave manufacturers. However, “basic” interoperability is not the same as “complete” interoperability. While a controller from any Z-Wave compliant company should be able to include and therefore, control a device from any other Z-Wave compliant company, the actual method to do that may differ from company to company. Also, the concepts of “Command Classes” and “Device Classes” is often misunderstood. For instance, a wall-mount receiver from ACT (i.e. ZRW103) defaults to having its LED track its load – when the LED is “On”, the load is also “On”. An option that we build into many of our products is the ability for the installer to change the LED to “night light mode”, meaning that when the LED is “On”, the load is “Off”. The complication is that while the ACT wall-mount receiver can be controlled by any Z-Wave compliant controller, another company’s controller may not support the ability to change certain parameters within a device.
Q: Why can’t I just buy one transmitter and one receiver and have them work together?
A: All Z-Wave compliant devices come from the factory in a “blank” configuration. That means that they do not know who they are, what network they will be in, and most importantly, to whom they are allowed to communicate. A controller is needed to setup (configure) the other devices so that they will be able to communicate to each other.
Q: Why is the no computer software sold with any ACT Z-Wave computer interface units.?
A: ACT makes several different Z-Wave interface units: The USB version ZCU101, and the serial RS-232 version ZCS101 (plus versions in the Euro frequency). It is important to understand that ACT does not supply any software with our interface units. Most of our interface units are sold buy other companies and bundled with their software. There are many companies who offer software packages that are compatible with all our HomePro Z-Wave interface units (ZCU101, ZCS101, ZCU201 and ZCS201). Among them are:
HomeSeer (http://www.homeseer.com),
LinuxMCE (http://linuxmce.com and http://wiki.linuxmce.org/index.php/Z-Wave),
mControl (http://www.embeddedautomation.com)
There are more being added all the time, so your search on the internet may find many others.
Q: Why is ACT unable to give me the protocol (command structure) so I can write my own software?
A: The Z-Wave is not an “open” protocol and so can not legally be shared with non-members of the alliance. If a software developer is wanting to create custom software, the Zensys developers kit is required. The development kit will explain the command structure, the command classes, device classes, plus has all the development tools that will allow the creation of Z-Wave compliant software. Contact Zensys directly for more information on the development kit.
The section above discusses Z-Wave basics. See also:
FAQ - How to Setup a Simple Network
FAQ - How to Setup a Simple Network. - Back to Top
Once the various parts of the system are installed, the user/installer will then “included” each device into the controller’s network. Unknown to most users (and many installers) is that as each node is added, it is asked by the controller (i.e. the ZTH100) if it can communicate to every other node previously installed in the network. That is why it takes a little longer when adding the 60th node, than the 1st, or the 10th or the 20th. By the time the 60th node is added, the controller says, "Welcome to my family, here is your network home ID, and you node ID, and please try to contact units number 1 through 59 and report back to me which ones you can talk to". That way, the ZTH100 will have the information to build its routing table. It will then know "which nodes can talk to which nodes".
Here are the steps for a basic Z-Wave system setup:
1. The integrator installs all the receivers in their proper locations (that means to physically install them and wire them to power).
2. The integrator then "includes" the first one using the ZTH100. The ZTH100 will "include" (or "add") the first unit into its network, by giving the receiver its "HomeID", then its unit ID. This is often done at low power for security reasons. The actual "addressing" is done automatically and is transparent to the integrator/installer/customer.
3. Then the integrator includes (adds) the second one. The ZTH100 will include the second unit into its network, by giving the receiver its network ID, then unit ID. Then it will ask the second unit to communicate to the first unit and report its result. If it can, the ZTH100 will use that information to build its routing table.
4. Then the integrator includes (adds) the next unit, and so on, until all of the receivers, transmitter, peripheral devices, etc. have been "included".
5. The ZTH100 now has a list of all the nodes, PLUS it has a routing table knowing which units can talk to other units and therefore can be used in routing packets around RF dead spots or units which are beyond its direct range.
6. If the installer is also setting up a computer interface unit, like our ZCU101 (or a different secondary controller), he can now "copy" all the network information from the ZTH100, over to the secondary unit using the "Copy Remote Ctrl" function. ("Send" from the ZTH100, "Receive" into the secondary unit.)
7. Now the secondary unit will also have all the nodes, plus the routing table.
When all the devices (nodes) are included into the network, schedules, scenes and associations can then be done.
The section above discusses how to setup a simple network. See also:
FAQ - Controllers - Back to Top
A controller is any Z-Wave device having been manufactured with a HomeID. It is this HomeID (sometimes called a network ID) on which the network is built. No peripheral device (node) can begin communicating with any other node in the network until it is included into the network. When it is included, it is given the HomeID for the network, plus a NodeID that identifies it within the network.
The controller also interrogates each device as it is included into the network, so that it will know the capabilities of that device (its device class, its command classes, etc.). The controller also stores a routing table so that it can route command packets.
Q: Why is the no computer software sold with any ACT Z-Wave computer interface units.?
A: ACT makes several different Z-Wave interface units: The USB version ZCU101, and the serial RS-232 version ZCS101 (plus versions in the Euro frequency). It is important to understand that ACT does not supply any software with our interface units. Most of our interface units are sold buy other companies and bundled with their software. There are many companies who offer software packages that are compatible with all our HomePro Z-Wave interface units (ZCU101, ZCS101, ZCU201 and ZCS201). Among them are:
HomeSeer (http://www.homeseer.com),
LinuxMCE (http://linuxmce.com and http://wiki.linuxmce.org/index.php/Z-Wave),
mControl (http://www.embeddedautomation.com)
There are more being added all the time, so your search on the internet may find many others.
Q: Why is ACT unable to give me the protocol (command structure) so I can write my own software?
A: The Z-Wave is not an “open” protocol and so can not legally be shared with non-members of the alliance. If a software developer is wanting to create custom software, the Zensys developers kit is required. The development kit will explain the command structure, the command classes, device classes, plus has all the development tools that will allow the creation of Z-Wave compliant software. Contact Zensys directly for more information on the development kit.
The section above discusses controllers. See also:
FAQ - How to Setup a Simple Network
FAQ - Receivers - Back to Top
Although all Z-Wave devices are in actuality “transceivers” (meaning they both transmit and receive), we designate a device as being a “receiver” if its primary function is to receive a command and then control a load.
Q: If there is no neutral wire in the wall box, can I use the ground wire?
A: No. This is a violation of the National Electric Code. The ground wire is part of the safety system and is not intended to be a return path for electricity. If no neutral wire exists, and there is no alternative device that can be used, contact a licensed electrician to have a new neutral wire run to the box. (See PCC Tech Tip #1 for more information.)
Q: Why are there no code wheels on any HPW receivers?
A: Many older control systems (like X-10) had mechanical methods of setting the address on the unit. That was practical when there were only a small number of available addresses. However, since Z-Wave systems have over 4 billion possible addresses, it is obviously impractical to have code wheels or dip-switches. Instead, the controller will have embedded into it, a unique HomeID and it will then assign a sequential NodeID to each device included into its network. Every node in any given network will then have its own HomeID + NodeID so that not only will it only communicate with other nodes in its network, but any other node in its network will be able to know which node is which.
Q: What types of Z-Wave receivers are available from ACT?
A: ACT offers a variety of receivers ranging from high current, 20 amp relay receivers, isolated contact relay receivers, incandescent dimmer receivers, plus many other specialized receivers.
Q: Why does a receiver refuse to be included into a network?
A: Occasionally, a receiver will not "include" and it appears to be dead. This may not really be the case. Sometimes when the factory testing is done, the unit is not properly "reset". Therefore it "thinks" that it is already a part of another network. Under this scenario, it will not let itself be included into "your" network. (It thinks that it is in your neighbor's house.) If you cannot "include" a unit, try to do a "reset unit" (see the ZTH200 instructions on "Reset Unit", and remember this is NOT the same as "Reset Remote Ctrl"). If it resets correctly, then try again to include the unit into the network.
Q: Why are 3-way switch arrangements so hard to do?
A: Converting a standard 3-way circuit to a PCC 3-way can sometimes be difficult because the installer may not realize how many variations there are in wiring a standard 3-way. Since there are so many ways to do one, there are many ways to convert one.
Q: What is an “association” in Z-Wave?
A: The process of linking one device to another device is called an "association". It is occasionally called a "virtual" 3-way. For instance, two receivers can be associated so that each is made to transmit commands to the other. Each one will control its own load, and will (by way of association) also be able to control the other's load. This association gives one device (the source) permission to transmit commands directly to another device (the destination). This most often used when a transmitter is included into the network and then associated with a nearby receiver so that it can work like a 3-way circuit so that the load can be controlled from either location.
Almost all of our newer products have this same "transmitter" capability. That means that not only will a "dimmer receiver" (ZDW103) dim your lights, it can also control other receivers. Not only will a "switch receiver" (ZRW103) control your receptacle, it can also control other receivers.
The section above discusses receivers. See also:
FAQ - How to Setup a Simple Network
FAQ - Transmitters - Back to Top
Although all Z-Wave devices are in actuality “transceivers” (meaning they both transmit and receive), we designate a device as being a “transmitter” if its primary function is to transmit a command and does not (necessarily) control a load directly.
Q: If there is no neutral wire in the wall box, can I use the ground wire?
A: No. This is a violation of the National Electric Code. The ground wire is part of the safety system and is not intended to be a return path for electricity. If no neutral wire exists, and there is no alternative device that can be used, contact a licensed electrician to have a new neutral wire run to the box. (See PCC Tech Tip #1 for more information.)
Q: If there is no neutral wire in the wall box, can I use the ground wire?
A: No. This is a violation of the National Electric Code. The ground wire is part of the safety system and is not intended to be a return path for electricity. If no neutral wire exists, and there is no alternative device that can be used, contact a licensed electrician to have a new neutral wire run to the box.
Q: Why are there no code wheels on any HPW transmitters?
A: Many older control systems (like X-10) had mechanical methods of setting the address on the unit. That was practical when there were only a small number of available addresses. However, since Z-Wave systems have over 4 billion possible addresses, it is obviously impractical to have code wheels or dip-switches. Instead, the controller will have embedded into it, a unique HomeID and it will then assign a sequential NodeID to each device included into its network. Every node in any given network will then have its own HomeID + NodeID so that not only will it only communicate with other nodes in its network, but any other node in its network will be able to know which node is which.
Q: What types of Z-Wave transmitters are available from ACT?
A: ACT offers a variety of transmitters ranging from wall-mount, single button units and multi-button transmitters, plus many other specialized transmitters.
Q: Why does a transmitter refuse to be included into a network?
A: Occasionally, a transmitter will not "include" and it appears to be dead. This may not really be the case. Sometimes when the factory testing is done, the unit is not properly "reset". Therefore it "thinks" that it is already a part of another network. Under this scenario, it will not let itself be included into "your" network. (It thinks that it is in your neighbor's house.) If you cannot "include" a unit, try to do a "reset unit" (see the ZTH200 instructions on "Reset Unit", and remember this is NOT the same as "Reset Remote Ctrl"). If it resets correctly, then try again to include the unit into the network.
Q: What is an “association” in Z-Wave?
A: The process of linking one device to another device is called an "association". It is occasionally called a "virtual" 3-way. This association gives one device (the source, usually the transmitter) permission to transmit commands directly to another device (the destination, usually the receiver). This most often used when a transmitter is included into the network and then associated with a nearby receiver so that it can work like a 3-way circuit so that the load can be controlled from either location.
Almost all of our newer products have this same "transmitter" capability. That means that not only will a "dimmer receiver" (ZDW103) dim your lights, it can also control other receivers. Not only will a "switch receiver" (ZRW103) control your receptacle, it can also control other receivers.
The section above discusses transmitters. See also:
FAQ - How to Setup a Simple Network
What is HPW? - Back to Top
As in many industries, Advanced Control Technologies uses acronyms to abbreviate its product lines. "HPW" is merely an abbreviation for HomePro Wireless. Often, we even abbreviate "Advanced Control Technologies" as just "ACT". All of ACT’s "HPW" products operate using the Z-Wave protocol. All HPW equipment uses radio frequency signals to communicate and so it is possible that other RF systems can interfere with the operation.
While Z-Wave products are designed to be a “do-it-yourself” system, more complex installations utilizing products from many vendors, may require specific knowledge and training to properly design and install a trouble-free system. As such, it must be acknowledged that a significant amount of importance is placed on the system designer’s training and experience. The ultimate responsibility for the system’s success lies with those on site. The user acknowledges that the application of any ACT HPW equipment into any environment is unique and therefore should be performed by trained installers, adhering to all appropriate electrical codes. Nothing contained in this FAQ is intended to create any liability or engineering responsibility on behalf of Advanced Control Technologies, Inc.
The section above discusses “HPW”. See also:
FAQ - How to Setup a Simple Network
What is Mesh Networking? - Back to Top
In older control networks, all (or nearly all) commands originated from a master controller (or transmitter). This meant that the controller needed to have direct connection to all the devices that it controlled. This also meant that the controller had to be directly wired to all the devices, or if it was a wireless system, the receiving devices had to be in range of the master controller.
In a mesh networked system, the controller (or other transmitter) need not be in direct communication with its peripheral devices. It can, instead “route” its command through other nodes. Routing of command data is done automatically in the Z-Wave system and is almost always transparent to the installer and the user. It is all handled by the Zensys IC chip and its inherent firmware.
The highest number of possible "hops" is 4: Controller --> Node1 --> Node2 --> Node3 --> Intended-Node. However, you would not be able to actually see how the signal is being sent without special equipment. This is basically how it works:
1. The controller will try to send its command directly to the intended node,
2. If it fails to get an acknowledgement, it will try 2 more times (this only takes a few milliseconds),
3. If it stills fails to get an acknowledgement, it will try a simple 1-hop routed transmission,
4. If it fails to get an acknowledgement, it will try 2 more times,
5. If it stills fails to get an acknowledgement, it will try a different 1-hop routed transmission (3 times),
6. If it stills fails to get an acknowledgement, it will continue to try all other 1-hop routed transmission paths (3 times each),
7. If it stills fails to get an acknowledgement, it will try a 2-hop routed transmission (3 times),
8. If it stills fails to get an acknowledgement, it will continue to try all other 2-hop routed transmission paths (3 times each),
.... this goes on until it has tried all possible routes.
You cannot rely simply on "line-of-sight" distance. Radio waves reflect and refract off of other objects so that sometimes signals are repeated through distant nodes to get to nodes that are physically closer.
Q: Does a Z-Wave network become more reliable as nodes are added?
A: Yes. When Z-Wave is used in a very small system (say, 1 controller and only 1 or 2 receivers), then the options for routing command packets is fairly limited. When environment conditions limit the reception of the signal (physical obstructions, RF interference, etc.). the controller may not have any other route to use. However, as the Z-Wave system grows in the number of nodes, the controller will have a corresponding increase in the number of routes from which to chose.
Q: I added a new device to help signal reach an unreliable node, but it didn’t help. Why?
A: In order for a node to be included in the routing table, it must first be included into the network. Simply plugging in a Z-Wave receiver half-way between two units thinking that will automatically be used to "relay" command packets to the (previously) unreliable receiver, will not work. Without adding it to the network, the controller will not know that the new unit exists and therefore can not use it to route commands around dead spots or to receivers just beyond direct transmission range.
The section above discusses “Mesh Networking”. See also:
FAQ - How to Setup a Simple Network
What is Z-Wave? - Back to Top
“Z-Wave” was developed by the Zensys company (now owned by Sigma Designs) to be a flexible radio technology for use primarily (but not limited to) home automation. It uses a low-power wireless technology designed specifically for remote control applications. Z-Wave operates in the 900 megahertz band. For instance, 908.42MHz is designated for use in North America and 868.42MHz in
Z-Wave is currently supported by over 200 manufacturers worldwide and appears in a broad range of consumer products in the
The “Z-Wave” standard is not an “open” standard. Company’s are granted the use of the technology by way of binding agreements and adherence to set standards of operation.
This section discusses Z-Wave. See also:
FAQ - How to Setup a Simple Network
Who is Zensys? - Back to Top
Zensys, Inc. (http://www.zen-sys.com) is based in
This section discusses general questions on Z-Wave. See also:
FAQ - How to Setup a Simple Network
What is Mesh Networking?
