LinuxMCE - User contributions [en]

Submitting a Patch

2010-11-08T18:18:16Z

Attunezero:

LinuxMCE uses the [http://subversion.apache.org subversion] revision control system (similar to CVS) to manage changes to the code base. This guide provides a few basic subversion commands that will help the user to post their first patches, without having to read the [http://svnbook.red-bean.com/ subversion handbook].

We'll assume that the user has already installed subversion. For more information about installation read [[Source Code (SVN Repository)]].

==Updating Source==

Before submitting your patch to the repository, update your local copy of the source code to reflect any changes that might have occurred since your initial svn checkout. Your patch will not be accepted if your local code conflicts with the most recent version on the repository.
svn update

If you receive the message
Skipped '.'
that means you aren't currently in the directory where you checked out the source.

==Add your changes==

Place any new code files into the proper directories on your system and add them individually:
svn add filename.cpp
svn add scriptname.sh

You can review the additions that you have made to the tree by typing
svn status
The letter 'A' indicates additions, a '?' indicates unknown files that have not been added.

==Create a Diff File==

Create a .diff file, which lists the files that have been changed or added to the source. This way the developers who audit your work can easily find the changes you have made.
svn diff > ../patchname.diff
It is good practice to place the .diff file outside of the source tree or else it will show up itself as an addition to the code base. Finally, look at the .diff file to make sure it only has the changes you intended.

==Submit a Patch==

At this point, if you have been given an svn account by the devs, type
svn commit
However, the LinuxMCE developers are busy so until you have submitted your first few patches, you won't be given an account. Instead, submit your .diff file and the new or altered code files as attachments to a [http://svn.linuxmce.org/trac.cgi/report trac ticket]. Make sure to read the rules about [[Bug Reporting]] as well, if this is your first time.

[[Category:Programmer's Guide]]

Express Controls EZmotion (HSM 100)

2010-11-06T22:59:35Z

Attunezero: /* Configuration */

[[Category: Hardware]]
{{Versioninfo|810Status=Working,PnP as 3 multilevel sensors|810UpdatedDate=4th May 2010|810UpdatedBy=sambuca}}
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: ZWave_security]]
[[Category: ZWave_motion_sensor]]
[[Category: ZWave_light_sensor]]
[[Category: ZWave_temperature_sensor]]
[[Category: Security]]
[[Category: 0810]]

= 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 =
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.

= 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:

48 Value (int) : <the time in minutes can only be 6 or any increment of 6> <br>
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 =
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

[http://www.expresscontrols.com/ideas.htm Which type of AAA battery to use in EZMotion?]

Express Controls EZmotion (HSM 100)

2010-11-06T22:56:40Z

Attunezero: /* Configuration */

[[Category: Hardware]]
{{Versioninfo|810Status=Working,PnP as 3 multilevel sensors|810UpdatedDate=4th May 2010|810UpdatedBy=sambuca}}
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: ZWave_security]]
[[Category: ZWave_motion_sensor]]
[[Category: ZWave_light_sensor]]
[[Category: ZWave_temperature_sensor]]
[[Category: Security]]
[[Category: 0810]]

= 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 =
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.

= 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:

48 Value (int) : <the time in minutes can only be 6 or any increment of 6> <br>
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 before you 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

[http://www.expresscontrols.com/ideas.htm Which type of AAA battery to use in EZMotion?]