Difference between revisions of "Express Controls EZmotion (HSM 100)"

From LinuxMCE
Jump to: navigation, search
(→‎Configuration)
(Added necessary reload info and check for association)
 
(15 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
{{Versioninfo|810Status=Working,PnP as 3 multilevel sensors|810UpdatedDate=4th May 2010|810UpdatedBy=sambuca}}
+
[[Category: Hardware]]
 +
{{Versioninfo|810Status=Working,PnP as 3 multilevel sensors|810UpdatedDate=4th May 2010|810UpdatedBy=sambuca|1204Status=Working,PnP with editing as 3 multilevel sensors|1204UpdatedDate=22th Feb 2014|1204UpdatedBy=RayBe}}
 
[[Category: RF Control]]
 
[[Category: RF Control]]
 
[[Category: ZWave]]
 
[[Category: ZWave]]
Line 7: Line 8:
 
[[Category: ZWave_temperature_sensor]]
 
[[Category: ZWave_temperature_sensor]]
 
[[Category: Security]]
 
[[Category: Security]]
−
[[Category: 0810]]
 
−
= Status =
 
−
Received sample from dianemo.co.uk (those guys rock)
 
  
 
= About =  
 
= About =  
Line 22: Line 20:
  
 
= Setup =
 
= Setup =
 +
== 1004 ==
 
If you use SIS mode in your ZWave setup, this device should automatically be added as three multilevel sensors.
 
If you use SIS mode in your ZWave setup, this device should automatically be added as three multilevel sensors.
 
If not, it is possible to set it up manually. If you are running SIS mode, you can delete the main device and re-add it as a motion detector, see below for details.
 
If not, it is possible to set it up manually. If you are running SIS mode, you can delete the main device and re-add it as a motion detector, see below for details.
Line 40: Line 39:
 
Reload router and you should receive events from all three sensors.
 
Reload router and you should receive events from all three sensors.
 
The motion detector will also report a values(which is not sent to LMCE atm.). This value if the number of minutes since last motion was detected, and 0 if no motion was detected. See the manual for more information.
 
The motion detector will also report a values(which is not sent to LMCE atm.). This value if the number of minutes since last motion was detected, and 0 if no motion was detected. See the manual for more information.
 +
 +
Note: when using Homepro ZCU010 USB computer interface you will have to send a "Set Association" command hooking up the controller and the HSM 100. If not done the HSM100 will not report back to LinuxMCE.
 +
Node ID of controller can be found in the Zwave log file; ''Home id: 0x0000e95d, our node id: 239 <0xb6d59b70>''.
 +
 +
== 1204 and later(OpenZwave)==
 +
If you use SIS mode in your ZWave setup, this device should automatically be added as three sensors.
 +
For example:
 +
* Port/Channel Number = 7, dt = 1946 (Multilevel Sensor)
 +
* Port/Channel Number = 7/1, dt = 1745 (Brightness Sensor)
 +
* Port/Channel Number = 7/2, dt = 1744 (Temperature Sensor)
 +
(The Port/Channel Number 7 in the above example may vary in your setup, but for explanation use, we will use it here)
 +
 +
To get the motion sensor setup, you must do the following:
 +
* In webadmin, click on Advanced -> Configuration -> Devices, which shows your device tree on the left
 +
* In this tree find your Zwave device and expand it completely
 +
* Delete the Multilevel Sensor with Port/Channel Number 7
 +
* Click on ZWave Embedded Security Interface
 +
* On the right pane, click on Create Child Device
 +
* Add Device Template #54, Motion Detector
 +
* In the Port/Channel Number field of this DT, fill in 7, corresponding with the Port/Channel Number you deleted above
 +
* Do a router reload
 +
* Open a terminal and login to your core, give the command: sudo killall ZWave
 +
Let your Zwave device startup (you can follow its progress in the follow log of your main Zwave device)
 +
On a active Orbiter you should get asked to regen, do it and the new motion sensor gets added to the security section
 +
* Go to the advanced ZWave page in webadmin, click on node 7 and check in the Associations tab if Motion is associated with node 1 (the controller). Only when set, the controller gets motion events from this node.
  
 
= Configuration =
 
= Configuration =
  
 
To change the interval temperature and light is reported go to Home > My Devices > CORE > ZWave and chose "Send command to device". Select "SetWakeUp" and set parameters as follows:
 
To change the interval temperature and light is reported go to Home > My Devices > CORE > ZWave and chose "Send command to device". Select "SetWakeUp" and set parameters as follows:
 +
For 1204, you should instead use the [[Advanced ZWave]] page to set configuration options.
  
 
48 Value (int) : <the time in minutes can only be 6 or any increment of 6> <br>
 
48 Value (int) : <the time in minutes can only be 6 or any increment of 6> <br>
−
239 NodeID (int) : <the zwave nodeid>
+
239 NodeID (int) : <the zwave nodeid> <br>
 +
 
 +
Send Message
 +
 
 +
Then push the button on the EZmotion (HSM 100)
 +
 
 +
 
 +
 
 +
By default it seems that the HSM 100 has a motion timeout of 20 minutes. That means that it will not send any motion detection events for 20 minutes after it is first tripped. This is a useful setting for saving batteries but not a useful setting for an occupancy sensor controlling lights. To set the motion timeout of the HSM 100:
 +
 
 +
#Select the ZWave device in the advanced web config devices section.
 +
#Select send command to device.
 +
#Select "Set Config Param" as the command to send.
 +
#48 Value (int) = Your desired timeout in minutes
 +
#239 NodeID (int) = The ZWave node ID of the HSM 100 to configure
 +
#248 Parameter ID (int) = 2
 +
#Press the blue button on the side of the HSM 100 you are trying to configure
 +
#Click "Send Message"
  
 
= Command classes =
 
= Command classes =
Line 65: Line 107:
  
 
http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf
 
http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf
 +
 +
[http://www.expresscontrols.com/ideas.htm Which type of AAA battery to use in EZMotion?]

Latest revision as of 15:14, 7 April 2016

Version Status Date Updated Updated By
710 Unknown N/A N/A
810 Working,PnP as 3 multilevel sensors 4th May 2010 sambuca
1004 Unknown N/A N/A
1204 Working,PnP with editing as 3 multilevel sensors 22th Feb 2014 RayBe
1404 Unknown N/A N/A
Usage Information

About

The EZMotion is a 3-in-1 Z-Wave sensor. This is also sold by Innovus and Homeseer (HSM100)

Manuf ID1: 0x0 ID2: 0x1e, Prod Typ1: 0x0 Typ2: 0x2, Prod ID1: 0x0 ID2: 0x1

Features

  • Motion detection
  • Light sensor
  • Temperature sensor.

Setup

1004

If you use SIS mode in your ZWave setup, this device should automatically be added as three multilevel sensors. If not, it is possible to set it up manually. If you are running SIS mode, you can delete the main device and re-add it as a motion detector, see below for details.

You will have one multilevel sensor added for the EZMotion. Find and open this from the device tree. We will change this to be the thermometer instance. Find the Port/Channel number. This is the node ID. Change the Port/Channel number to <node id>/3 (for instance 4/3 if your node id is 4), type to Thermometer, insert 49 in Capabilities, and save.

Add a new device below the ZWave Embedded Climate Interface using the same device template (Multilevel sensor). Insert <node id>/2 in Port/Channel number, insert 49 in Capabilities and save. This will be the brightness sensor. Please notice that the values returned from this sensor ranges from 0 to 100% and is relative to the light measured since X (see the manual).

Then we add the Motion detector. This will not be added automatically even when running the SIS mode. Open the ZWave Embedded Security Interface and click Create New Child. Select the Motion Detector template. Insert <node id> in Port/Channel number, Motion Detector in type, 133,96,49,112,132,128,114,119,134 in Capabilities, and save.

Reload router and you should receive events from all three sensors. The motion detector will also report a values(which is not sent to LMCE atm.). This value if the number of minutes since last motion was detected, and 0 if no motion was detected. See the manual for more information.

Note: when using Homepro ZCU010 USB computer interface you will have to send a "Set Association" command hooking up the controller and the HSM 100. If not done the HSM100 will not report back to LinuxMCE. Node ID of controller can be found in the Zwave log file; Home id: 0x0000e95d, our node id: 239 <0xb6d59b70>.

1204 and later(OpenZwave)

If you use SIS mode in your ZWave setup, this device should automatically be added as three sensors. For example:

  • Port/Channel Number = 7, dt = 1946 (Multilevel Sensor)
  • Port/Channel Number = 7/1, dt = 1745 (Brightness Sensor)
  • Port/Channel Number = 7/2, dt = 1744 (Temperature Sensor)

(The Port/Channel Number 7 in the above example may vary in your setup, but for explanation use, we will use it here)

To get the motion sensor setup, you must do the following:

  • In webadmin, click on Advanced -> Configuration -> Devices, which shows your device tree on the left
  • In this tree find your Zwave device and expand it completely
  • Delete the Multilevel Sensor with Port/Channel Number 7
  • Click on ZWave Embedded Security Interface
  • On the right pane, click on Create Child Device
  • Add Device Template #54, Motion Detector
  • In the Port/Channel Number field of this DT, fill in 7, corresponding with the Port/Channel Number you deleted above
  • Do a router reload
  • Open a terminal and login to your core, give the command: sudo killall ZWave

Let your Zwave device startup (you can follow its progress in the follow log of your main Zwave device) On a active Orbiter you should get asked to regen, do it and the new motion sensor gets added to the security section

  • Go to the advanced ZWave page in webadmin, click on node 7 and check in the Associations tab if Motion is associated with node 1 (the controller). Only when set, the controller gets motion events from this node.

Configuration

To change the interval temperature and light is reported go to Home > My Devices > CORE > ZWave and chose "Send command to device". Select "SetWakeUp" and set parameters as follows: For 1204, you should instead use the Advanced ZWave page to set configuration options.

48 Value (int) : <the time in minutes can only be 6 or any increment of 6>
239 NodeID (int) : <the zwave nodeid>

Send Message

Then push the button on the EZmotion (HSM 100)


By default it seems that the HSM 100 has a motion timeout of 20 minutes. That means that it will not send any motion detection events for 20 minutes after it is first tripped. This is a useful setting for saving batteries but not a useful setting for an occupancy sensor controlling lights. To set the motion timeout of the HSM 100:

  1. Select the ZWave device in the advanced web config devices section.
  2. Select send command to device.
  3. Select "Set Config Param" as the command to send.
  4. 48 Value (int) = Your desired timeout in minutes
  5. 239 NodeID (int) = The ZWave node ID of the HSM 100 to configure
  6. 248 Parameter ID (int) = 2
  7. Press the blue button on the side of the HSM 100 you are trying to configure
  8. Click "Send Message"

Command classes

0x4 0x21 0x1

  • COMMAND_CLASS_MULTI_INSTANCE
  • COMMAND_CLASS_SENSOR_MULTILEVEL
  • COMMAND_CLASS_CONFIGURATION
  • COMMAND_CLASS_WAKE_UP
  • COMMAND_CLASS_ASSOCIATION
  • COMMAND_CLASS_BATTERY
  • COMMAND_CLASS_MANUFACTURER_SPECIFIC
  • COMMAND_CLASS_NODE_NAMING
  • COMMAND_CLASS_VERSION

Links

http://www.expresscontrols.com

http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf

Which type of AAA battery to use in EZMotion?

Retrieved from "http://wiki.linuxmce.org/index.php?title=Express_Controls_EZmotion_(HSM_100)&oldid=36714"