New User, Z-Stick/OpenZWave Issues

Configuration Z-Wave
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

34

Checks out; same as mine. But when I started my device path was always /dev/ttyACM0. I used the command in @brusc’s video to determine it. And like you, I have removed my stick to pair it but have also paired through the OPZWCP as well.

35

@rpitera What were the steps you used to get the lock to pair with the zwave stick? I’ve done multiple resets and tried all sorts of combinations of ozwcp and HA in secure pairing mode and nothing seems to work; There aren’t even any logs that show any sort of communication between the stick and the lock. It can see all my other non-secure devices fine.

36

Unfortunately as I mentioned at the top of the thread, I didn’t pair this with my stick. My lock is paired to a WInk Hub.

I have a stick, and was going to pair it with the lock to get the extra attributes but never got around to it and glad I didn’t do it.

I wish I could be more help but have been trying to post what info I can.

37

i got it working! woke up this morning and figured out i’d triy to exclude the lock before calling add node secure, and that did the trick.

Turns out that when you try to add node (nonsecure) it puts the lock into a wierd state where it fails to pair but it also isn’t fully unpaired. In the lock manual it states that you can tell whether it’s paired or not by removing the battery and looking for the light above the manual lockbolt to light up. Mine did not when it was in this wierd state.

Exact steps I used to get this to work:

  1. Start up HA, call node_remove and enroll/unenroll your lock. You should see a green flashing light signaling that it was properly unenrolled
  2. call node_add_secure and enroll the lock.
38

Congrats! I’ll try that when I get home, but I still think we must have two different problems. I’m pretty sure I’ve done that before, and I still can’t get my two insecure Z wave devices to work consistently either.

39

Gonna link this other thread again. The OP, in the beginning, had the same problems I’m seeing now, and in post 5, said he fixed them by “rebuilding python-openzwave and ozwcp.” Any idea how to do that? I responded in his thread but never got a reply.

40

Awesome news! Thanks for sharing your steps as well! Hope this helps @rphillipps16, I’ve really been rooting for him to get this resolved.

I’m still trying to figure out what the heck these are, since I never set up any secure devices yet…

Clipboard01.png808×266 26.4 KB