New User, Z-Stick/OpenZWave Issues

Configuration Z-Wave
14

I’ve tried a few different things here and there the last couple days, and think I can narrow it down to a network key mismatch somewhere. The only place I’ve edited mine is in my options.xml in the Openzwave directory. Below is the log entries when I try and highlight the lock and click “Add Node,” as well as my options.xml text.

OpenZWave Log Output:

2016-08-09 01:45:42.846 Detail, Queuing (Controller) Add Device
2016-08-09 01:45:42.846 Info, Add Device
2016-08-09 01:45:42.846 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x15, 0x64
2016-08-09 01:45:42.846 Detail, Notification: ControllerComand - Starting
2016-08-09 01:45:42.846 Info, Notification: ControllerCommand home c047e481 Event 1 Error 0
2016-08-09 01:45:42.846 Detail,
2016-08-09 01:45:42.846 Info, contrlr, Sending (Command) message (Callback ID=0x15, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x15, 0x64
2016-08-09 01:45:43.847 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-08-09 01:45:43.847 Detail, contrlr, Removing current message
2016-08-09 01:45:43.847 Detail, contrlr, Notification: Notification - TimeOut
2016-08-09 01:45:43.847 Info, Notification: Notification home c047e481 node 255 Timeout
2016-08-09 01:45:43.847 Detail, Notification: ControllerCommand - Error - Failed
2016-08-09 01:45:43.847 Info, Notification: ControllerCommand home c047e481 Event 3 Error 10

Options.xml (network key is obscured):

<?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 -->
">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="0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00" />
<!-- 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" />
<Option name="ThreadTerminateTimeout" value="5000" />
</Options>

Directory of my options.xml is /srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config if that helps.

If you can find anything, I really appreciate it!

15

Sorry, I know next to nothing about network keys; in fact I wasn’t even sure what they were when they showed up in my states panel as I never set them up. Hopefully someone else will check in on this.

16

Hmm, would this help at all?

17

That’s actually the page I linked in the OP lol. The only thing I think is different on my end is directories. Should I start a new thread, since my original problem is gone?

18

Sorry; I forgot that link was there…

19

Have you by chance looked at this other similar thread here? Looks like he fixed his issue using another HA platform called Domoticz, ever used it?

20

No, I’ve seen the thread and seen mentions of Domoticz other places but never used it.

21

I’m having the exact same problem as well. Raspberry Pi3, Aeotec Z-Stick Gen5, and a Schlage Connect (BE469). Just set up a clean install of the RPI All-In-One Installer, and am on HA 26.2. I’ve been trying to add the lock through ozwcp since that seems like the most foolproof method.

  1. Start ozwcp
  2. Initialize the controller at /dev/ttyACM0.
  3. Controller -> Add Device
  4. Go to Schlage Connect and try to enroll device.

OZWCP Log File:
2016-08-15 05:57:59.414 Detail, Queuing (Controller) Add Device 2016-08-15 05:57:59.414 Info, Add Device 2016-08-15 05:57:59.414 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b 2016-08-15 05:57:59.415 Detail, Notification: ControllerComand - Starting 2016-08-15 05:57:59.415 Info, Notification: ControllerCommand home f216247e Event 1 Error 0 2016-08-15 05:57:59.415 Detail, 2016-08-15 05:57:59.415 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b 2016-08-15 05:57:59.418 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x07, 0x00, 0x00, 0xbf 2016-08-15 05:57:59.418 Detail, 2016-08-15 05:57:59.418 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2016-08-15 05:57:59.418 Info, contrlr, ADD_NODE_STATUS_FAILED 2016-08-15 05:57:59.419 Detail, contrlr, Removing current message 2016-08-15 05:57:59.419 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4 2016-08-15 05:57:59.419 Detail, Notification: ControllerCommand - Failed 2016-08-15 05:57:59.419 Info, Notification: ControllerCommand home f216247e Event 8 Error 0 2016-08-15 05:57:59.419 Detail, 2016-08-15 05:57:59.419 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4 2016-08-15 05:57:59.472 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x00, 0x00, 0xbe 2016-08-15 05:57:59.472 Detail, 2016-08-15 05:57:59.472 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2016-08-15 05:57:59.472 Detail, Node006, Expected reply was received 2016-08-15 05:57:59.473 Detail, Node006, Message transaction complete 2016-08-15 05:57:59.473 Detail, 2016-08-15 05:57:59.473 Detail, contrlr, Removing current message 2016-08-15 05:57:59.473 Detail, Notification: ControllerCommand - Completed 2016-08-15 05:57:59.473 Info, Notification: ControllerCommand home f216247e Event 7 Error 0

When I try to enroll the Schlage connect lock, it looks like OZWCP doesn’t even log any additional lines (not communicating with the lock).

When i naively tried to pair the lock in HA before adding a network key in ozwcp, I noticed that although enrollment would fail on the Connect lock (I’ve never gotten a green checkbox on my lock to flash), it looked like HA would notice the lock as I could see it in HA though none of the settings in HA would work.

RPhilipps16, are you seeing the same thing?

22

Been searching through OpenZWave threads, it seems that mucking around with the zwcfg file may help. Haven’t tried it yet.

https://groups.google.com/forum/#!searchin/openzwave/network$20key|sort:date/openzwave/Jqs-UZeOhiA/dYWRjmzAAwAJ

23

Probably a dumb question, but did you try “Add device (secure)” instead of “add device” in ozwcp?

I think I’m just gonna try factory resetting everything and hope I messed something stupid up when installing

24

Yeah I’ve been trying both, with no success either way. When you set up your Pi3, did you use the All-In-One installer (https://home-assistant.io/getting-started/installation-raspberry-pi-all-in-one/) or did you install openzwave separately?

And when you were able to initially pair the stick with the lock, was that through ozwcp? I haven’t been able to see any communication between the stick and the lock in logs, and I’ve already ruled out any malfunction with my stick or RPi as it pairs other z-wave non-secure devices fine, which is incredibly frustrating.

25

I think I may have done both by accident. Not sure if that would result in two different Z wave directories. What’s frustrating is that I haven’t had any devices pair, secure or not. I also have a First Alert smoke/CO detector and an Aeotec Minimote (just got today so I haven’t tried too hard), both with no luck so far. Hopefully the reinstall will fix that

26

Again, I’ve tried both through just the stick (press it to enter pairing) and through ozwcp. Does the stick need to stay connected to the Pi to get ozwcp pairing to work?

27

I’ve always paired it through Home Assistant or paired it in testing through ozwcp.

In HA, go to http://localhost:8123/dev-service and on the right side you should see a bunch of services you can call. Among them, if you’ve set up openzwave properly, add_node and add_node_secure. This has helped me when trying to debug since then there are log files :slight_smile:

28

Does the stick need to be connected to the pi during that method, or do you take it out and enter pairing through the stick?

29

I keep my stick connected to the Pi the whole time. I didn’t even know that you could pair with the stick disconnected from a computer

30

I’d been following BRUH Automation’s videos mostly and he does it out of the Pi. Click the button to enter pairing, and hold it to enter exclusion. I’ll try doing it in the pi once I reset. Thanks!

31

Finally reinstalled, and on a whim I changed my config’s USB path from /dev/ttyUSB0 to /dev/ttyACM0 and that got Z wave recognized in HA. Aside from that, though, I’m back where I started. I can see my lock in both HA and OZWCP, though in OZWCP, the lock has a status of “Ready” and a value of “off”, just like before. I still can’t seem to add unsecured Z wave devices via the HA or OZWCP methods though. Here’s a snippet of my OZWCP log when I click “lock”

Edit: I managed to add my alarm and remote, briefly at least, in OZWCP, but after rebooting my Pi, they went back to the status of “Probe (sleeping)”, which is apparently impossible to escape. Maybe they’ll come back tomorrow

2016-08-16 01:29:54.368 Info, Node002, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2016-08-16 01:29:54.373 Info, Node002, Value_Lock::Set - Requesting lock to be Locked
2016-08-16 01:29:54.373 Detail, Node002, Queuing (Send) DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x19, 0x47
2016-08-16 01:29:54.373 Detail, Node002, Queuing (Send) DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x1a, 0xba
2016-08-16 01:29:54.374 Detail,
2016-08-16 01:29:54.374 Info, Node002, Sending (Send) message (Callback ID=0x19, Expected Reply=0x04) - DoorLockCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x62, 0x01, 0xff, 0x25, 0x19, 0x47
2016-08-16 01:29:54.382 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-08-16 01:29:54.382 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-08-16 01:29:55.630 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x19, 0x00, 0x00, 0x7d, 0x8f
2016-08-16 01:29:55.630 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x19 received (expected 0x19)
2016-08-16 01:29:55.631 Info, Node002, Request RTT 1256 Average Request RTT 1255
2016-08-16 01:29:55.631 Detail, Expected callbackId was received
2016-08-16 01:30:04.375 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-08-16 01:30:04.375 Detail, Node002, Removing current message
2016-08-16 01:30:04.376 Detail, Node002, Notification: Notification - TimeOut
2016-08-16 01:30:04.376 Info, Notification: Notification home dd0f4eae node 2 Timeout
2016-08-16 01:30:04.376 Detail,
2016-08-16 01:30:04.376 Info, Node002, Sending (Send) message (Callback ID=0x1a, Expected Reply=0x04) - DoorLockCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x62, 0x02, 0x25, 0x1a, 0xba
2016-08-16 01:30:04.385 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-08-16 01:30:04.385 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-08-16 01:30:05.677 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x1a, 0x00, 0x00, 0x81, 0x70
2016-08-16 01:30:05.677 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x1a received (expected 0x1a)
2016-08-16 01:30:05.677 Info, Node002, Request RTT 1300 Average Request RTT 1277
2016-08-16 01:30:05.677 Detail, Expected callbackId was received
2016-08-16 01:30:14.377 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-08-16 01:30:14.377 Detail, Node002, Removing current message
2016-08-16 01:30:14.377 Detail, Node002, Notification: Notification - TimeOut
2016-08-16 01:30:14.377 Info, Notification: Notification home dd0f4eae node 2 Timeout

32

In your configuration.yaml, what is your zwave config_path pointing to?

33

Haven’t ever changed it, it’s at /srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config