ZWave Debugging - Revision history

Micasaverde at 20:39, 14 June 2016

2016-06-14T20:39:11Z

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

2014-09-18T11:59:17Z

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

Micasaverde: /* Advanced debugging for developers */

2012-09-20T18:33:14Z

‎Advanced debugging for developers

Micasaverde: /* Not getting status changes with door locks, or door locks out of sync */

2012-05-08T15:14:45Z

‎Not getting status changes with door locks, or door locks out of sync

Micasaverde: /* Not getting status changes with door locks, or door locks out of sync */

2012-05-08T15:14:17Z

‎Not getting status changes with door locks, or door locks out of sync

Micasaverde: /* Not getting status changes with door locks, or door locks out of sync */

2012-05-08T15:13:41Z

‎Not getting status changes with door locks, or door locks out of sync

Micasaverde: /* Not getting status changes with door locks, or door locks out of sync */

2012-05-08T15:05:10Z

‎Not getting status changes with door locks, or door locks out of sync

Guessed: /* Advanced debugging for developers */ Add a link for Log levels page, since this [legacy] page comes up frequently in searches

2012-03-15T04:19:34Z

‎Advanced debugging for developers: Add a link for Log levels page, since this [legacy] page comes up frequently in searches

Ap15e: /* Advanced debugging for developers */

2011-12-12T11:49:24Z

‎Advanced debugging for developers

Ap15e: /* Advanced debugging for developers */

2011-12-11T23:10:45Z

‎Advanced debugging for developers

← Older revision		Revision as of 20:39, 14 June 2016
Line 131:		Line 131:

	http://forum.micasaverde.com/index.php?topic=5130.0		http://forum.micasaverde.com/index.php?topic=5130.0
		+
		+	== Replace failed node ==
		+
		+	If you have a Z-Wave node that needs to be replaced with another of the same type, and you want the new node to have the same node ID, be sure the old defective node is removed and powered off. You must not try to connect it and power it up again. Connect or power on the new node that will replace it. It must be unpaired and ready to pair. Go to the 'advanced' section of the device and choose the 'commands' tab and click 'replace failed'. Then activate pairing on the new node. Wait a minute and the new node will be included with the same node id as the old one.

	== Demo Mode ==		== Demo Mode ==

@@ Line 15: / Line 15: @@
 E				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.
+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.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.

@@ Line 33: / Line 33: @@
 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.
-<u>Log levels for data sent to the Z-Wave dongle</u>:<br> 01 = critical errors<br> 02 = warnings<br> 04 = jobs <br>05 = warnings<br> 06 = variables (which indicates state changes)<br>07 = events<br>08 = commands<br>10 = status messages<br> 41 = data sent to the Z-Wave dongle<br>42 = data received from the Z-Wave dongle<br> 50 = luup log
+<u>Log levels for data sent to the Z-Wave dongle</u>:<br> 01 = critical errors<br> 02 = warnings<br> 03 = start/stop/reload events<br> 04 = jobs <br>05 = warnings<br> 06 = variables (which indicates state changes)<br>07 = events<br>08 = commands<br>10 = status messages<br> 41 = data sent to the Z-Wave dongle<br>42 = data received from the Z-Wave dongle<br> 50 = luup log
 <br>

@@ Line 150: / Line 150: @@
 (3) Wait a couple minutes after saving for Vera to settle down so the logs aren't going like crazy.
-(4) Get Putty, a free Windows ssh client.  Just google for putty download.  You don't need to install it, just save it to your desktop.  Run it, put Vera's IP in the host name, leave SSH checked and click Open.  The user name is '''root''' and the password is on the bottom of Vera; it's the same as the wifi password or house id.  If you don't see the root password [[Logon_Vera_SSH#Can.27t_find_the_root_password.3F|Logon # Can't find the root password?]].
+(4) Get Putty, a free Windows ssh client.  Just google for putty download.  You don't need to install it, just save it to your desktop.  Run it, put Vera's IP in the host name, leave SSH checked and click Open.  The user name is '''root''' and the password is on the bottom of Vera; it's the same as the wifi password or house id.  If you don't see the root password see [[Logon_Vera_SSH#Can.27t_find_the_root_password.3F|Logon # Can't find the root password?]].
 (5) Once you're logged in, type this command:

@@ Line 150: / Line 150: @@
 (3) Wait a couple minutes after saving for Vera to settle down so the logs aren't going like crazy.
-(4) Get Putty, a free Windows ssh client.  Just google for putty download.  You don't need to install it, just save it to your desktop.  Run it, put Vera's IP in the host name, leave SSH checked and click Open.  The user name is '''root''' and the password is on the bottom of Vera; it's the same as the wifi password or house id.  If you don't see the root password [[Logon_Vera_SSH#Can.27t_find_the_root_password.3F]].
+(4) Get Putty, a free Windows ssh client.  Just google for putty download.  You don't need to install it, just save it to your desktop.  Run it, put Vera's IP in the host name, leave SSH checked and click Open.  The user name is '''root''' and the password is on the bottom of Vera; it's the same as the wifi password or house id.  If you don't see the root password [[Logon_Vera_SSH#Can.27t_find_the_root_password.3F|Logon # Can't find the root password?]].
 (5) Once you're logged in, type this command:

@@ Line 36: / Line 36: @@
 <br>
-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 .
+For commands run 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 .
 <br>

@@ Line 48: / Line 48: @@
 To watch the traffic on the Z-Wave serial bus, type:
-'''cd /var/log/cmh<br> tail -f 9-ZWave.log | grep '^40\|^41''''
+'''cd /var/log/cmh<br> tail -f 9-ZWave.log | grep '^41\|^42''''
-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:
+which means show log level 41 or 42. 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'''<br>(assuming the Z-Wave device is #9, as default, add 225 1 to make the change permanent)
@@ Line 76: / Line 76: @@
 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&nbsp;:conf_jh#9 (0x00DD7390) P:40 S:0 &lt;00DD7390&gt; 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.
+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&nbsp;:conf_jh#9 (0x00DD7390) P:40 S:0 &lt;00DD7390&gt; 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\|^41\|^42\|^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\|^41\|^42\|^01\|^05' 9-ZWave.log | less -R'' to see just the filtered portion of the logs in color.
 <br> 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''''

@@ Line 33: / Line 33: @@
 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.
-<u>Log levels for data sent to the Z-Wave dongle</u>:<br> 01 = critical errors<br> 02 = warnings<br> 04 = jobs <br>05 = warnings<br> 06 = variables (which indicates state changes)<br>07 = events<br>08 = commands<br>10 = status messages<br> 40 = data sent to the Z-Wave dongle<br>41 = data received from the Z-Wave dongle<br> 50 = luup log
+<u>Log levels for data sent to the Z-Wave dongle</u>:<br> 01 = critical errors<br> 02 = warnings<br> 04 = jobs <br>05 = warnings<br> 06 = variables (which indicates state changes)<br>07 = events<br>08 = commands<br>10 = status messages<br> 41 = data sent to the Z-Wave dongle<br>42 = data received from the Z-Wave dongle<br> 50 = luup log
 <br>
@@ Line 84: / Line 84: @@
 Reset the Z-Wave network:<br>'''/usr/bin/MessageSend localhost 0 9 1 776 51 SIS'''
 Do a 'soft reset' that doesn't lose any devices, but resets the dongle:<br> '''/usr/bin/MessageSend localhost 0 9 1 776 51 SOFT'''
 == Z-Wave Log Messages  ==