MiOS - User contributions [en]

ExpressControls3in1

2011-02-21T06:15:41Z

Jgc94131: /* Configure */

[[Category:Hardware]]
[[Category:Plugins]]
[[Category:3rd Party]]

== Overview ==
The EZMotion Wireless 3-in-1 sensor is functionally identical to the HomeSeer HSM100 device. The user's manual is here: http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf

=== Features ===

This unit is a contains three sensors that report values to the Vera:
* '''Motion Sensor''' with adjustable sensitivity and timeout
* '''Temperature Sensor'''
* '''Luminosity (Light Level) Sensor''' reporting level of light as a percentage between the brightest and darkest levels it has encountered since being switched on for the first time

The unit has a red LED which indicates when motion is detected and it can be disabled. It can also report its battery level as a percentage to the Vera.

== Basic Configuration ==
=== Wake Up interval ===
The unit sleeps for the duration of the Wake Up interval, which defaults to 1800 seconds or 30 minutes. When the interval expires, it wakes up and reports Temperature and Luminosity to the Vera. Note that while all 4 devices in the Vera MIOS screen can be configured for Wake Up intervals, only the setting for the '3-in-1 Sensor' has any effect and controls both Temperature and Luminosity intervals. The Motion Sensor is unaffected by the Wakeup Interval (see On Time below)

To set the Wake Up Interval, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Setting and set Wakeup Interval to the desired interval.

=== On Time ===
When the Motion Sensor is tripped, it transmits a tripped command and changes its state to Tripped=1 for the duration of the ON TIME variable. After this time has expired, it sends an Untripped command to the Vera and resets it state to Tripped=0. While the device is in a tripped state, any motion detected resets the interval timer but doesn't report a new trip event to the Vera. During the wait time the Motion Sensor device in the Vera will show Tripped=1 in the Advanced tab.

To set the ON TIME, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 5 (or the desired interval in minutes)

'''Direct Association:''' The unit can be associated directly with another device such as a light. If you've done this, the unit will turn the light on when motion is sensed, then turn it off after the ON TIME. According to the sensor's manual up to four associated devices are supported, but associating more than one device does not work (as of Vera's firmware 1.0.900, see http://bugs.micasaverde.com/view.php?id=705).

Leave Parameter #6, "OnValue", at the default if you want the sensor tripped events in Vera.

=== Polling Frequency ===
The unit can only be polled when it is either in Test mode or within 3 seconds after waking up (see Wake Up Interval above). Polling at any other time will fail since the unit will not respond. Also, every time the unit wakes up, it updates Vera with the temperature and luminosity. This means that polling is unnecessary and the polling frequency should be set to 0 (disabled) or a long interval to avoid unnecessary traffic on Vera, which could cause updates to be missed.

An exception to this rule is when Vera is set to Always Awake (see AC Power below). In that case, the unit never wakes up, so never reports its values and must be polled at regular intervals.

=== Example ===
Consider the following example of how to configure the sensor and the Vera for a common application. Suppose you want to install a motion sensor in your garage to turn the lights on when you enter, keep them on for as long as you move around in the garage, then turn them off 5 minutes after you've left.
# Put the unit in Test mode by pressing the button on the side
# Configure the On Time to 5 minutes
# Create two scenes in Vera:
## Turn on the light when the unit has tripped (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=Yes)
## Turn off the light when the unit sends an untrip command which happens after the On Time interval. (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=No)

== Advanced Configuration ==
=== Running from AC Power ===
==== Overview ====
It is possible to run the unit from AC power instead of batteries, which will have the following benefits:
* Allow you to keep the unit awake permanently, allowing you to poll it and customise it without being in Test mode
* Report continuously every time motion is sensed, as opposed to waiting for the ON TIME duration in between trips
* Set the unit to report temperature and light levels at higher frequencies up to 1 minute
* Let the unit act as a Z-Wave repeater, increasing the span of your network
* Never worry about running down batteries. All of the above options are possible on battery power, but will run your batteries down within a few days
==== Configure ====
To do this, you will need to connect a AC to DC transformer that supplies 4.5v to 5.5v at up to 1amp to the battery terminals directly. Ensure that you measure that actual output voltage of the transformer using a multi/voltage meter (don't rely on its advertised rating). Any over-voltage may fry the unit. Also make sure that the polarity is correct. It may be helpful to add a diode in series with the positive terminal to prevent accidentally frying the unit if the polarity is incorrect. It will drop the voltage by 0.6v though.

'''Setting ''Stay Awake'' to On'''
By default, the unit is constantly asleep and only wakes up at regular intervals to report the luminosity and temperature, before sleeping again. This is to save batteries. While asleep, the unit cannot be programmed from the Vera and cannot be polled for information. To get around this, one normally activates the Test mode by pressing the button on the side of the unit, which keeps it awake for 10 minutes so that it can be programmed. By setting the unit to stay awake constantly, you can program, poll or configure it at any time. It also has the side effect of enabling the unit to become a repeater of Z Wave signals throughout the network.

To set it, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 5 (Stay Awake) to 1 or any number greater than 0.

'''Setting ''On Time'' to ''Always Fire'''''
When the unit detects motion, it reports it by sending a Tripped command to the Vera. It then waits for the duration of the On Time and then sends un Untripped command to the Vera and waits for the next motion. Since battery life is not a consideration while on AC power, you can set it to 'Always Fire', which sends a Tripped command whenever motion is detected with no waiting period. Note, this will also prevent an Untripped command from being sent.

To set it, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 0.

'''Excluding and Reincluding the unit'''
To activate these new settings, you will need to exclude and reinclude the unit using the standard Vera process. Remember to save your settings first.

''' Setting Poll frequency'''
The unit usually only reports temperate and luminosity every time it wakes up, but since the unit is now constantly awake, you will have to configure a poll frequency to gather that information.

To set it, click on the spanner (wrench) icon for the "Motion Sensor" device, click on Settings and set "Poll this node at most every" to the required update frequency. The Wakeup interval setting on this same screen has no effect since it's been overridden by Always Awake setting.

== Known issues ==

ExpressControls3in1

2011-02-21T06:15:02Z

Jgc94131: /* Wake Up interval */

[[Category:Hardware]]
[[Category:Plugins]]
[[Category:3rd Party]]

== Overview ==
The EZMotion Wireless 3-in-1 sensor is functionally identical to the HomeSeer HSM100 device. The user's manual is here: http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf

=== Features ===

This unit is a contains three sensors that report values to the Vera:
* '''Motion Sensor''' with adjustable sensitivity and timeout
* '''Temperature Sensor'''
* '''Luminosity (Light Level) Sensor''' reporting level of light as a percentage between the brightest and darkest levels it has encountered since being switched on for the first time

The unit has a red LED which indicates when motion is detected and it can be disabled. It can also report its battery level as a percentage to the Vera.

== Basic Configuration ==
=== Wake Up interval ===
The unit sleeps for the duration of the Wake Up interval, which defaults to 1800 seconds or 30 minutes. When the interval expires, it wakes up and reports Temperature and Luminosity to the Vera. Note that while all 4 devices in the Vera MIOS screen can be configured for Wake Up intervals, only the setting for the '3-in-1 Sensor' has any effect and controls both Temperature and Luminosity intervals. The Motion Sensor is unaffected by the Wakeup Interval (see On Time below)

To set the Wake Up Interval, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Setting and set Wakeup Interval to the desired interval.

=== On Time ===
When the Motion Sensor is tripped, it transmits a tripped command and changes its state to Tripped=1 for the duration of the ON TIME variable. After this time has expired, it sends an Untripped command to the Vera and resets it state to Tripped=0. While the device is in a tripped state, any motion detected resets the interval timer but doesn't report a new trip event to the Vera. During the wait time the Motion Sensor device in the Vera will show Tripped=1 in the Advanced tab.

To set the ON TIME, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 5 (or the desired interval in minutes)

'''Direct Association:''' The unit can be associated directly with another device such as a light. If you've done this, the unit will turn the light on when motion is sensed, then turn it off after the ON TIME. According to the sensor's manual up to four associated devices are supported, but associating more than one device does not work (as of Vera's firmware 1.0.900, see http://bugs.micasaverde.com/view.php?id=705).

Leave Parameter #6, "OnValue", at the default if you want the sensor tripped events in Vera.

=== Polling Frequency ===
The unit can only be polled when it is either in Test mode or within 3 seconds after waking up (see Wake Up Interval above). Polling at any other time will fail since the unit will not respond. Also, every time the unit wakes up, it updates Vera with the temperature and luminosity. This means that polling is unnecessary and the polling frequency should be set to 0 (disabled) or a long interval to avoid unnecessary traffic on Vera, which could cause updates to be missed.

An exception to this rule is when Vera is set to Always Awake (see AC Power below). In that case, the unit never wakes up, so never reports its values and must be polled at regular intervals.

=== Example ===
Consider the following example of how to configure the sensor and the Vera for a common application. Suppose you want to install a motion sensor in your garage to turn the lights on when you enter, keep them on for as long as you move around in the garage, then turn them off 5 minutes after you've left.
# Put the unit in Test mode by pressing the button on the side
# Configure the On Time to 5 minutes
# Create two scenes in Vera:
## Turn on the light when the unit has tripped (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=Yes)
## Turn off the light when the unit sends an untrip command which happens after the On Time interval. (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=No)

== Advanced Configuration ==
=== Running from AC Power ===
==== Overview ====
It is possible to run the unit from AC power instead of batteries, which will have the following benefits:
* Allow you to keep the unit awake permanently, allowing you to poll it and customise it without being in Test mode
* Report continuously every time motion is sensed, as opposed to waiting for the ON TIME duration in between trips
* Set the unit to report temperature and light levels at higher frequencies up to 1 minute
* Let the unit act as a Z-Wave repeater, increasing the span of your network
* Never worry about running down batteries. All of the above options are possible on battery power, but will run your batteries down within a few days
==== Configure ====
To do this, you will need to connect a AC to DC transformer that supplies 4.5v to 5.5v at up to 1amp to the battery terminals directly. Ensure that you measure that actual output voltage of the transformer using a multi/voltage meter (don't rely on its advertised rating). Any over-voltage may fry the unit. Also make sure that the polarity is correct. It may be helpful to add a diode in series with the positive terminal to prevent accidentally frying the unit if the polarity is incorrect. It will drop the voltage by 0.6v though.

'''Setting ''Stay Awake'' to On'''
By default, the unit is constantly asleep and only wakes up at regular intervals to report the luminosity and temperature, before sleeping again. This is to save batteries. While asleep, the unit cannot be programmed from the Vera and cannot be polled for information. To get around this, one normally activates the Test mode by pressing the button on the side of the unit, which keeps it awake for 10 minutes so that it can be programmed. By setting the unit to stay awake constantly, you can program, poll or configure it at any time. It also has the side effect of enabling the unit to become a repeater of Z Wave signals throughout the network.

To set it, click on the spanner for the "3-in-1 sensor" device, click on Device Options and set variable 5 (Stay Awake) to 1 or any number greater than 0.

'''Setting ''On Time'' to ''Always Fire'''''
When the unit detects motion, it reports it by sending a Tripped command to the Vera. It then waits for the duration of the On Time and then sends un Untripped command to the Vera and waits for the next motion. Since battery life is not a consideration while on AC power, you can set it to 'Always Fire', which sends a Tripped command whenever motion is detected with no waiting period. Note, this will also prevent an Untripped command from being sent.

To set it, click on the spanner for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 0.

'''Excluding and Reincluding the unit'''
To activate these new settings, you will need to exclude and reinclude the unit using the standard Vera process. Remember to save your settings first.

''' Setting Poll frequency'''
The unit usually only reports temperate and luminosity every time it wakes up, but since the unit is now constantly awake, you will have to configure a poll frequency to gather that information.

To set it, click on the spanner for the "Motion Sensor" device, click on Settings and set "Poll this node at most every" to the required update frequency. The Wakeup interval setting on this same screen has no effect since it's been overridden by Always Awake setting.

== Known issues ==

ExpressControls3in1

2011-02-21T06:13:10Z

Jgc94131: /* On Time */

[[Category:Hardware]]
[[Category:Plugins]]
[[Category:3rd Party]]

== Overview ==
The EZMotion Wireless 3-in-1 sensor is functionally identical to the HomeSeer HSM100 device. The user's manual is here: http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdf

=== Features ===

This unit is a contains three sensors that report values to the Vera:
* '''Motion Sensor''' with adjustable sensitivity and timeout
* '''Temperature Sensor'''
* '''Luminosity (Light Level) Sensor''' reporting level of light as a percentage between the brightest and darkest levels it has encountered since being switched on for the first time

The unit has a red LED which indicates when motion is detected and it can be disabled. It can also report its battery level as a percentage to the Vera.

== Basic Configuration ==
=== Wake Up interval ===
The unit sleeps for the duration of the Wake Up interval, which defaults to 1800 seconds or 30 minutes. When the interval expires, it wakes up and reports Temperature and Luminosity to the Vera. Note that while all 4 devices in the Vera MIOS screen can be configured for Wake Up intervals, only the setting for the '3-in-1 Sensor' has any effect and controls both Temperature and Luminosity intervals. The Motion Sensor is unaffected by the Wakeup Interval (see On Time below)

To set the Wake Up Interval, click on the spanner for the "3-in-1 sensor" device, click on Setting and set Wakeup Interval to the desired interval.

=== On Time ===
When the Motion Sensor is tripped, it transmits a tripped command and changes its state to Tripped=1 for the duration of the ON TIME variable. After this time has expired, it sends an Untripped command to the Vera and resets it state to Tripped=0. While the device is in a tripped state, any motion detected resets the interval timer but doesn't report a new trip event to the Vera. During the wait time the Motion Sensor device in the Vera will show Tripped=1 in the Advanced tab.

To set the ON TIME, click on the spanner (wrench) icon for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 5 (or the desired interval in minutes)

'''Direct Association:''' The unit can be associated directly with another device such as a light. If you've done this, the unit will turn the light on when motion is sensed, then turn it off after the ON TIME. According to the sensor's manual up to four associated devices are supported, but associating more than one device does not work (as of Vera's firmware 1.0.900, see http://bugs.micasaverde.com/view.php?id=705).

Leave Parameter #6, "OnValue", at the default if you want the sensor tripped events in Vera.

=== Polling Frequency ===
The unit can only be polled when it is either in Test mode or within 3 seconds after waking up (see Wake Up Interval above). Polling at any other time will fail since the unit will not respond. Also, every time the unit wakes up, it updates Vera with the temperature and luminosity. This means that polling is unnecessary and the polling frequency should be set to 0 (disabled) or a long interval to avoid unnecessary traffic on Vera, which could cause updates to be missed.

An exception to this rule is when Vera is set to Always Awake (see AC Power below). In that case, the unit never wakes up, so never reports its values and must be polled at regular intervals.

=== Example ===
Consider the following example of how to configure the sensor and the Vera for a common application. Suppose you want to install a motion sensor in your garage to turn the lights on when you enter, keep them on for as long as you move around in the garage, then turn them off 5 minutes after you've left.
# Put the unit in Test mode by pressing the button on the side
# Configure the On Time to 5 minutes
# Create two scenes in Vera:
## Turn on the light when the unit has tripped (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=Yes)
## Turn off the light when the unit sends an untrip command which happens after the On Time interval. (New Scene, Events tab, Add Event, Device=Motion sensor, Type of Event=Armed sensor has tripped, Name=whatever, Tripped=No)

== Advanced Configuration ==
=== Running from AC Power ===
==== Overview ====
It is possible to run the unit from AC power instead of batteries, which will have the following benefits:
* Allow you to keep the unit awake permanently, allowing you to poll it and customise it without being in Test mode
* Report continuously every time motion is sensed, as opposed to waiting for the ON TIME duration in between trips
* Set the unit to report temperature and light levels at higher frequencies up to 1 minute
* Let the unit act as a Z-Wave repeater, increasing the span of your network
* Never worry about running down batteries. All of the above options are possible on battery power, but will run your batteries down within a few days
==== Configure ====
To do this, you will need to connect a AC to DC transformer that supplies 4.5v to 5.5v at up to 1amp to the battery terminals directly. Ensure that you measure that actual output voltage of the transformer using a multi/voltage meter (don't rely on its advertised rating). Any over-voltage may fry the unit. Also make sure that the polarity is correct. It may be helpful to add a diode in series with the positive terminal to prevent accidentally frying the unit if the polarity is incorrect. It will drop the voltage by 0.6v though.

'''Setting ''Stay Awake'' to On'''
By default, the unit is constantly asleep and only wakes up at regular intervals to report the luminosity and temperature, before sleeping again. This is to save batteries. While asleep, the unit cannot be programmed from the Vera and cannot be polled for information. To get around this, one normally activates the Test mode by pressing the button on the side of the unit, which keeps it awake for 10 minutes so that it can be programmed. By setting the unit to stay awake constantly, you can program, poll or configure it at any time. It also has the side effect of enabling the unit to become a repeater of Z Wave signals throughout the network.

To set it, click on the spanner for the "3-in-1 sensor" device, click on Device Options and set variable 5 (Stay Awake) to 1 or any number greater than 0.

'''Setting ''On Time'' to ''Always Fire'''''
When the unit detects motion, it reports it by sending a Tripped command to the Vera. It then waits for the duration of the On Time and then sends un Untripped command to the Vera and waits for the next motion. Since battery life is not a consideration while on AC power, you can set it to 'Always Fire', which sends a Tripped command whenever motion is detected with no waiting period. Note, this will also prevent an Untripped command from being sent.

To set it, click on the spanner for the "3-in-1 sensor" device, click on Device Options and set variable 2 (On Time) to 0.

'''Excluding and Reincluding the unit'''
To activate these new settings, you will need to exclude and reinclude the unit using the standard Vera process. Remember to save your settings first.

''' Setting Poll frequency'''
The unit usually only reports temperate and luminosity every time it wakes up, but since the unit is now constantly awake, you will have to configure a poll frequency to gather that information.

To set it, click on the spanner for the "Motion Sensor" device, click on Settings and set "Poll this node at most every" to the required update frequency. The Wakeup interval setting on this same screen has no effect since it's been overridden by Always Awake setting.

== Known issues ==

ZWave Debugging

2010-12-29T15:47:56Z

Jgc94131: /* Custom device types or names based on Z-Wave ID's */

[[Category:Development]]

== Custom device types or names based on Z-Wave ID's ==

In the configuration directory (normally /etc/cmh) is a file called zwave_products_sys.xml. This contains a list of hardcoded settings for various ZWave devices. The file is a series of values separated by tabs, with one entry on each line. The format is:

Manufacturer, Basic, Generic, Specific, ChildNumber, ProductType, ProductID, Devicefilename, ZWaveClass, Default name, Custom variables

When a Z-Wave device is added it is compared against this file. If the device's manufacturer ID, Basic ZWave device class, Generic device class, Specific device class, Product Type and Product ID match what's in the file, then rather than using the default device information, the device will use the UPnP XML device file in Devicefilename, and the ZWave class ZWaveClass, and will have the Default name, and the UPnP variables in "Custom variables". If any of Manufacturer, Basic, Generic, Specific, ChildNumber, ProductType, ProductID are not specified, it's considered a match. If any of Devicefilename, ZWaveClass, Default name, Custom variables are not specified, the default values are used. ChildNumber is when there's a multi-channel or multi-instance, this is what the child device will use.

For example, for the Express controls 3-in-1 sensor which has manufacturer 001E and Product Type/ID are 2 and 1, the 3 embedded children are forced to be a motion sensor, light sensor, temperature sensor.

001E 1 2 1 D_MotionSensor1.xml
001E 2 2 1 D_LightSensor1.xml
001E 3 2 1 D_TemperatureSensor1.xml

zwave_products_sys.xml is distributed with each MIOS release, so any changes you make to it are lost on upgrade. However, you can add your own rows in the file: zwave_products_user.conf (or zwave_products_user.xml?) in the same folder with the same format. Those will be saved when you upgrade.

To get the source values (manufacturer id, product type, etc.) grep for UpdateNode in LuaUPnP.log.

== Easy Z-Wave Debugging ==

== Z-Wave specifics ==

Vera maps the command class BASIC to COMMAND_CLASS_SENSOR_BINARY, and responds to BASIC_GET or SENSOR_BINARY_GET with a _REPORT that has a value of 1 if Vera is running (ie it's always 1).

== Advanced debugging for developers ==

Here are some hints for debugging Z-Wave protocol issues. You can access Vera by telnet, or if you already set a password, by ssh.

First, be sure you check the box "verbose logs" under 'Advanced', 'Logging', or, from a console run /usr/bin/VerboseLogging.sh enable.

The logs are in the directory /var/log/cmh. The first 2 digits are the 'log level'. The file: DCERouter.log contains the logging information from the core message router. The file: x-ZWave.log (where x is usually 9) contains all the logs from the Z-Wave module.

Log levels for data sent to the Z-Wave dongle: 40 = data sent to the Z-Wave dongle 41 = data received from the Z-Wave dongle 01 = critical errors 04 = jobs 05 = warnings 06 = variables (which indicates state changes) 07 = events 08 = commands 10 = status messages
 

For commands runed in a scene, the logs won't be getting data from the user, but from a scene, so to see this requests, you should grep for RunScene .

 

So, if you want to watch the router's logs and see what commands are being sent to the various devices, do this:

'''cd /var/log/cmh tail -f DCERouter.log | grep '^08''''

Now from Vera's dashboard, send commands to the devices and you'll see them in the log. The | grep '^08' means to filter only lines that start with 08, meaning log level 08 ("Commands"). tail -f means "follow the log". To stop the tail and get back to the console, if you used ssh to login, you just press Ctrl+C. Unfortunately, often times telnet doesn't forward Ctrl+C, so, when using telnet you need to press Ctrl+Z and then type this to kill the tail command: killall tail; fg

To watch the traffic on the Z-Wave serial bus, type:

'''cd /var/log/cmh tail -f 9-ZWave.log | grep '^40\|^41''''

which means show log level 40 or 41. Normally Vera is polling all the nodes every few seconds, so the logs fill up quickly with Z-Wave traffic from the polling. If you want to turn off automatic polling temporarily for this session so the logs aren't cluttered with polling traffic, type:

'''/usr/bin/MessageSend localhost 0 9 1 966 5 0''' (assuming the Z-Wave device is #9, as default, add 225 1 to make the change permanent)

To force a poll of device 13, type: '''/usr/bin/MessageSend localhost 0 9 1 966 2 13 5 UPDATE'''

Next you can send "COMMAND: #191 - Send Code" to either a Z-Wave Node and the parameter 9 (Text) is a command, or send it to the Z-Wave device and it is a frame. The contents of text are a string of hex or decimal numbers separated with spaces, dashes or underscores, and hex values are preceded with 0x or x. So assuming a dimmable light is device 20 in node 15, either command below will dim it to 50%:

'''/usr/bin/MessageSend localhost 0 9 1 191 9 "0 x13 15 0x3 0x26 0x1 50 4 1"''' #send data (func id x13) to node 15 command class 0x26 command 0x1 (set multi level) to 10% (size=3) with transmit options=4 and funcid=1

'''/usr/bin/MessageSend localhost 0 20 1 191 9 "x26 x1 50"''' #send the message directly to device 20 (the node, not 9 the Z-Wave dongle), so the node id and 'send data' frame are assumed

--Luup update: wget "http://127.0.0.1:49451/data_request?id=lu_action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Node=7&Data=x26-x1-20" node 7 to 20%

--Luup update: wget "http://127.0.0.1:49451/data_request?id=lu_action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Data=0-x13-7-0x3-0x26-0x1-50-4-1" node 7 to 20%

'''/usr/bin/MessageSend localhost 0 14 1 191 9 "x85 2 1"''' #Tell device 14 to report its association group 1

Ask node 4 (a thermostat) to report its temperature: "0 0x13 0x4 0x2 0x40 0x2 5 1"

You can also put an R in front of the binary data, and include the full frame, and it simulates a received frame on the serial api, rather than sending a frame. So to simulate receiving a FUNC_ID_ZW_APPLICATION_UPDATE from node 1 run: '''/usr/bin/MessageSend localhost 0 9 1 191 9 "R0x1 0x9 0x0 0x49 0x84 0x1 0x3 0x2 0x2 0x1 0x38"''' or an encrypted message from node 29 with FUNC_ID_APPLICATION_COMMAND_HANDLER, COMMAND_CLASS_SECURITY: '''"R0x01 0x1C 0x00 0x04 0x00 29 0x16 0x98 0x81 0xEC 0xE1 0x10 0x56 0xFC 0x13 0xDF 0x04 0x45 0x60 0x24 0xA8 0x43 0x89 0xE8 0x22 0x36 0x15 0xA9 0xB1 0x1C"'''

--Luup update: wget "http://127.0.0.1:49451/data_request?id=lu_action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Data=R0x1-0x16-0x0-0x4-0x0-0x4-0x10-0x8f-0x1-0x4-0x3-0x80-0x3-0x64-0x2-0x46-0x4-0x2-0x46-0x7-0x2-0x84-0x7-0x15"

Note that the logs will rotate regularly, meaning the DCERouter.log is archived as DCERouter.log.1.gz, and the old DCERouter.log.1.gz becomes DCERouter.log.2.gz. This is handled by the root cron process that runs /usr/bin/Rotate_Logs.sh.

Every time you do something with Vera this results in a "job". So let's assume you want to see what Vera is doing to configure a device. Type 'date' to see the date/time. Click the 'configure right now' button for the device. Type ''grep AddJob 9-ZWave.log'' to see all the log entries with 'AddJob' in them. Each one is given a number, and an abbreviated description. Say the first job after the 'date' is ''10 01/26/09 16:35:51.640 JobHandler::AddJob job#6 :conf_jh#9 (0x00DD7390) P:40 S:0 <00DD7390> conf_jh#9 type ZWJob_ConfigureNode first 0'' This means it's job#6, the name 'conf_jh#9' means it's a configure job from the main job handler for node #9. You may see lots of other jobs right after #6 to do things like set the Version/Manufacturer, set Associations, etc., because the main configure job (#6) may spawn many other jobs. To see all the log entries for job #6, type ''grep "job#6" 9-ZWave.log''. Pay attention to the lines with m_eJobStatus which indicate the status, such as ''m_eJobStatus Job completed ok''. Let's say you want to see what data is being sent/received as part of job#6, you could do this: ''grep 'job#6\|^40\|^41\|^01\|^05' 9-ZWave.log'' so you see all log entries for job #6, all incoming/outgoing data, plus critical errors (1) and warnings (5). Look for the line 'ready to run' in the logs, which will indicate where job #6 is starting. The logs are color coded, and the less that comes with busybox in Vera doesn't support the -R parameter to view the logs in color, which is much easier to read. So, you can set a root password if you haven't already (type ''passwd''), and then use scp to copy the log files from Vera to another Linux/Mac/Windows with cygwin pc, and then run: ''grep 'job#6\|^40\|^41\|^01\|^05' 9-ZWave.log | less -R'' to see just the filtered portion of the logs in color.

 You can also use MessageSend to send Vera's normal DCE commands directly to devices. The ID's are the same as LinuxMCE. You can also '''tail -f DCERouter.log | grep '^08''''

From the console, if you want to see if a device is configured, enable verbose logging: '''/usr/bin/VerboseLogging.sh enable''', restart the Z-Wave device: '''/usr/bin/MessageSend localhost 0 9 7 1''' then wait for it to finish checking all the devices and '''grep UpdateNode 9-ZWave.log'''. You'll see: '''ZWaveJobHandler::UpdateNodes node 13 PK_DeviceTemplate 37 type ZWaveNonDimmableLight PK_Device 19 cap 0xc9 sec 0xc res 0x0 bas 0x4 gen 0x10 spe 0x3 config 1 LS (on/off)-45W-IPCAM classes 25,27,2b,2c,72,73,77,82,85,86,91,ef,''' config 1 means the device is configured. To reconfigure a device from the command line, send it command 776. For this device it would be: '''/usr/bin/MessageSend localhost 0 19 1 776'''.

Reset the Z-Wave network: '''/usr/bin/MessageSend localhost 0 9 1 776 51 SIS'''

Do a 'soft reset' that doesn't lose any devices, but resets the dongle: '''/usr/bin/MessageSend localhost 0 9 1 776 51 SOFT'''

== Z-Wave Log Messages ==

=== Z-Wave LastNote ===

'''Status="Aborted" LastNote="Timed out waiting for the node to reply"'''

'''Status="Aborted" LastNote="Node is not configured"'''

'''Status="Aborted" LastNote="Unable to get any information on node"'''

'''Status="Aborted" LastNote="Transmit failed with code: 1"'''

== Remote Upgrade with preserve settings ==

curl -k -s -S --fail --retry 3 -o /tmp/firmware.img http://download.controlmyhouse.net/betafirmware/ftp/wl500gP-1.0.543.trx

/usr/bin/cmh-upgrade.sh

== Z-Wave routing matrix ==

See http://forum.micasaverde.com/index.php?topic=2099.msg8292#msg8292

== Z-Wave stress test ==

Start a stress test of the Z-Wave network with this command. Stop by doing a /usr/bin/Reload.sh

wget "http://127.0.0.1:49451/data_request?id=lu_action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Stress=X"

where X is:

#define STRESS_TEST_CONSTANT 1 // Constant BASIC_SET's
#define STRESS_TEST_NEIGHBOR_UPDATE 2 // Constant Neighbor updates
#define STRESS_TEST_WATCHDOG 3 // Constant Watchdog checks -- bugs in the Z-Wave serial API cause this to crash
#define STRESS_TEST_SOFT_RESET 4 // Constant soft resets

== Dead battery operated devices ==

Vera does not flag malfunctioning battery operated devices on the GUI.

Use the following code to log all malfunctioning battery operated devices to a file:

http://forum.micasaverde.com/index.php?topic=5100.msg28346#msg28346

Use the following code to get email notifications about malfunctioning battery operated devices:

http://forum.micasaverde.com/index.php?topic=5130.0