unhandled driver.cpp exception, using leviton vrc0p+3

[GoogleCodeExporter]

What steps will reproduce the problem?
1.using r992 from svn, plus openzwave-control-panel (also compiled using latest 
svn)
2.built zwave network using aeon labs z-stick s2, one linear binary switch 
(node 3)
3.everything works great
4.add one Leviton vrc0p+3 (id'd as node 4)
5.openzwave-control-panel (using open-zwave) crashes, with log below:

2015-01-18 08:31:37.145 Detail, 
2015-01-18 08:31:37.145 Info, Node004, Sending (Query) message (Callback 
ID=0x00, Expected Reply=0x49) - Request Node Info (Node=4): 0x01, 0x04, 0x00, 
0x60, 0x04, 0x9f
2015-01-18 08:31:37.149 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x60, 
0x01, 0x9b
2015-01-18 08:31:37.149 Detail, 
2015-01-18 08:31:37.149 Info, Node004, FUNC_ID_ZW_REQUEST_NODE_INFO Request 
successful.
2015-01-18 08:31:37.169 Detail, Node004,   Received: 0x01, 0x15, 0x00, 0x49, 
0x84, 0x04, 0x0f, 0x02, 0x00, 0x00, 0x85, 0x77, 0x82, 0x73, 0x86, 0x72, 0x91, 
0x98, 0xef, 0x26, 0x2b, 0x2c, 0x1e
2015-01-18 08:31:37.169 Detail, 
2015-01-18 08:31:37.170 Info, Node004, UPDATE_STATE_NODE_INFO_RECEIVED from 
node 4
2015-01-18 08:31:37.170 Info, Node004,   Optional command classes for node 4:
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_ASSOCIATION
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_NODE_NAMING
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_HAIL
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_POWERLEVEL
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_VERSION
2015-01-18 08:31:37.170 Info, Node004,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2015-01-18 08:31:37.170 Info, Node004,   CommandClass 0x91 - NOT REQUIRED
2015-01-18 08:31:37.170 Info, Node004,   Using Configured Network Key 
(AddingNode: false KeySet: false)
2015-01-18 08:31:37.170 Warning, Invalid Network Key. Does not contain 16 Bytes 
- Contains 0
2015-01-18 08:31:37.170 Warning, Raw Key: 
2015-01-18 08:31:37.170 Warning, Parsed Key:
2015-01-18 08:31:37.170 Error, Exception: Driver.cpp:6300 - 103 - Failed to 
Read Network Key
Error: Driver.cpp:6300 - Failed to Read Network Key

What is the expected output? What do you see instead?
Everything to work great, or Driver.cpp to handle the missing data gracefully

What version of the product are you using? On what operating system?
open-zwave trunk r992, on Ubuntu 14.10

Original issue reported on code.google.com by Pete.M.0...@gmail.com on 18 Jan 2015 at 1:50

• Blocked on: #427

[GoogleCodeExporter]

Can you attach the full OZW_Log.txt, after you removed the zwcfg*xml and 
restarted.

Original comment by uAle...@gmail.com on 18 Jan 2015 at 3:19

[GoogleCodeExporter]

Log file attached, after removing the zwcfg*xml file, restarting, 
reinitializing, etc.  Thanks!

Original comment by Pete.M.0...@gmail.com on 18 Jan 2015 at 5:22

[GoogleCodeExporter]

Original comment by Pete.M.0...@gmail.com on 18 Jan 2015 at 5:23

Attachments:

• OZW_Log.txt

[GoogleCodeExporter]

I checked if your node004 is a security device, but it doesn't seem to be.

Can you copy-paste your open-zwave/config/options.xml file? Mine looks like 
(security key is disabled!):

<?xml version="1.0" encoding="utf-8"?>
<!-- To be effective, this file should be placed in the user data folder 
specified in the Options::Create method -->
<Options xmlns='http://code.google.com/p/open-zwave/'>
  <Option name="logging" value="true" />
  <Option name="Associate" value="true" />
  <Option name="NotifyTransactions" value="false" />
  <Option name="DriverMaxAttempts" value="5" />
  <Option name="SaveConfiguration" value="true" />
  <!-- <Option name="RetryTimeout" value="40000" /> -->
  <!-- If you are using any Security Devices, you MUST set a network Key -->
  <!-- <Option name="NetworkKey" value="0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10" /> -->

  <!-- Some Devices have a big UserCode Table, that can mean startup times
  when refreshing Session Variables is very long (Especialy on Security
  Devices) This option will make the UserCode CC stop on the first
  "available" usercode slot rather than retrieve every one -->
  <Option name="RefreshAllUserCodes" value="false" />
</Options>

Original comment by uAle...@gmail.com on 18 Jan 2015 at 5:57

[GoogleCodeExporter]

Here's my options.xml file.  I haven't made any changes to it.

<?xml version="1.0" encoding="utf-8"?>
<!-- To be effective, this file should be placed in the user data folder 
specified in the Options::Create method -->
<Options xmlns='http://code.google.com/p/open-zwave/'>
  <Option name="logging" value="true" />
  <Option name="Associate" value="true" />
  <Option name="NotifyTransactions" value="false" />
  <Option name="DriverMaxAttempts" value="5" />
  <Option name="SaveConfiguration" value="true" />
  <!-- <Option name="RetryTimeout" value="40000" /> -->
  <!-- If you are using any Security Devices, you MUST set a network Key -->
  <!-- <Option name="NetworkKey" value="0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10" /> -->

  <!-- Some Devices have a big UserCode Table, that can mean startup times
  when refreshing Session Variables is very long (Especialy on Security
  Devices) This option will make the UserCode CC stop on the first
  "available" usercode slot rather than retrieve every one -->
  <Option name="RefreshAllUserCodes" value="false" />
</Options>

Original comment by Pete.M.0...@gmail.com on 18 Jan 2015 at 6:13

[GoogleCodeExporter]

Node 4 does appear to be a security enabled device, it's just dying before it 
logs it out. Currently no way to disable the security CC for a node, though 
that feature is planned. Reason it exits now is cause the exception handling 
code is not throwing to your app yet. When we turn that on, you will get a 
exception, but OZW will continue going. 

Original comment by jus...@dynam.ac on 20 Jan 2015 at 6:40

[GoogleCodeExporter]

Original comment by jus...@dynam.ac on 20 Jan 2015 at 6:41

• Now blocked on: #427