New User, Z-Stick/OpenZWave Issues

Just moved in to a new house so I’ve started a new setup, with a Raspberry Pi 3 running Home Assistant, an Aeotec Z-Stick Gen5, and a Schlage Connect, and I’ve been trying to interface between them to no avail.

In the beginning, I was at least able to pair the Z-Stick and the lock, but not get them to show up in HASS. I eventually came across this tutorial, and was able to add a network key to my OpenZWave config.xml and add the secure node to my OpenZWave config, to the point where the status of my lock in the Devices section was “Ready.”

Still not seeing anything in HASS, I went back to the OpenZWave control panel and mistakenly hit the “Reset” button under the controller interface/device name at the top left. Doing this has caused me a ton of problems, apparently. I can’t seem to be able to re-pair the lock and stick at all. I’ve factory reset both multiple times, entered exclusion mode on the stick and successfully unpaired the two (the green check on my lock flashed a few times), but still can’t re-pair the two devices. Any ideas how I can fix this? I don’t mind factory resetting my Pi or reinstalling HASS if that’s the only solution since I’m not to far into configuring anything yet.

Thanks for reading, still pretty new at this

1 Like

You may want to try upgrading to the latest hotfix, 0.25.2 as there was some issues with ZWave locks that prompoted the hotfix.

I’ve had a few people say the same to me. I’ll try once I’m home from work, hope it works!

If you mean at Reddit, one of them was me. :slight_smile:

Keep us posted.

Heh, yup. posted in homeautomation and homeassistant

Still not working, even after 0.25.2. Either get no reaction when pairing (still get one unpairing) or get the red X flashing on the door.

You may need to set it to exclusion mode to reset it first. I had to do this to add it to my Wink hub.

Ah, from OpenZWave Control Panel, like remove_node referenced at the bottom here https://home-assistant.io/getting-started/z-wave/? Think I know what you’re talking about, I’ll try that when I get home again.

There’s a method for doing this from the lock itself using a code, but I’m at a client site so I don’t have it handy.

I think it’s called “Enroll” mode according the user guide, unless there’s another mode. It’s activated by entering the programming code then pressing “0”. Is that it?

1 Like

That’s it.

Was away for the weekend. Think I finally got somewhere though. Don’t know how, but I see the lock in OpenZWave again and it says “ready”, but the value says “off.” Where can I go from here?

Try pressing the outside Schlage button and see if that wakes it up in the control panel.

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!

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.

Hmm, would this help at all?

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?

Sorry; I forgot that link was there…

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?

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