Difference between revisions of "ZWave"

From LinuxMCE
Jump to: navigation, search
Line 76: Line 76:
 
You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the  Light ([[Media:zwave_lights.png]]).
 
You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the  Light ([[Media:zwave_lights.png]]).
  
== PIR (Binary Sensor) support ==
+
== Setting associations ==
 +
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.
  
[[ACT Homepro Motion Detector]]
+
The web interface allows you to create associations between devices (I believe this requires SIS mode, not sure).
 +
Click "Show device tree" then navigate to your z-wave controller (under CORE) and select "Send command to device". A popup window will show and you can choose the "Set Association" command.
 +
Enter three parameters:
 +
* the zwave NodeID of the source device, the one that will send the command
 +
* the group in the source device that will trigger the send (typically the button number on a multi-paddle switch)
 +
* the NodeID(s) device(s)
 +
Example: 5 / 2 / 7,8  would cause devices 7 and 8 to turn on when you press button 2 of device 5
  
 
== Z-Wave API documentation ==
 
== Z-Wave API documentation ==
  
 
[[ZWave API]]
 
[[ZWave API]]

Revision as of 18:47, 12 May 2010

Version Status Date Updated Updated By
710 Unknown N/A N/A
810 Unknown N/A N/A
1004 Unknown N/A N/A
1204 Unknown N/A N/A
1404 Unknown N/A N/A
Usage Information

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

Overview

The support from LinuxMCE system is represented by an executable ZWave (it's placed in /usr/pluto/bin) which is the device implementation and a DeviceTemplate (1754) which is used to create LinuxMCE Devices for ZWave.

Look at the Z-Wave Wiki Category to see pages for different Z-Wave devices.

The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

Implementation

Open version

The new open Z-Wave driver will be included in the upcoming 0810 release.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2 Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

New Fiire driver

Fiire also provides a new Z-Wave driver, it is binary only: Fiire ZWave Patch

Old version

This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

Interfaces

Supported

UNSUPPORTED

those don't work

How to install and use ZWave

Automatic installation - Lighting Wizard

The Lighting Wizard allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions.

Setup using Tricklestar Remote

Manual setup / Download configuration

Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE (media:zwave_homepro_interface.png), you can proceed by populating the ZWave network information to LinuxMCE.

  1. Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
    • Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
  2. Go to LinuxMCE admin page ("http://192.168.80.1/pluto-admin/"), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
    1. On the device page select "Send command to device".
    2. Select command "Download Configuration" and choose "Send Message".
      • Leave the data and file fields as blank
  3. Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
    • If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
    • You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
    • Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
  4. Go to device tree (Show devices tree) and you should see (Media:zwave_devices_tree.png) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light (Media:zwave_lights.png).

Setting associations

If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

The web interface allows you to create associations between devices (I believe this requires SIS mode, not sure). Click "Show device tree" then navigate to your z-wave controller (under CORE) and select "Send command to device". A popup window will show and you can choose the "Set Association" command. Enter three parameters:

  • the zwave NodeID of the source device, the one that will send the command
  • the group in the source device that will trigger the send (typically the button number on a multi-paddle switch)
  • the NodeID(s) device(s)

Example: 5 / 2 / 7,8 would cause devices 7 and 8 to turn on when you press button 2 of device 5

Z-Wave API documentation

ZWave API