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.
@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.
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.
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:
- Start up HA, call node_remove and enroll/unenroll your lock. You should see a green flashing light signaling that it was properly unenrolled
- call node_add_secure and enroll the lock.
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.
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.
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…
I can’t believe it, that actually did it! Thank you so much! No idea why doing the same thing (I think) in OZWCP didn’t do the same thing.
@rpitera, No idea what those entities are. Here’s all of mine. Aside from my lock, I have 2 Lifx bulbs and an Ecobee3 with 3 remote sensors attached to Home Assistant.
1 Like
Now that I have it working, how do you (and @siukwai) configure your locks in HA (or OZWCP but preferably HA)? I’ve seen references to code storage in OZWCP, but it was in hexadecimal, like the network key. If I wanted a code to be, say, 1234, would I just type 0x01 0x02 0x03 0x04, assuming the pin length is set to 4? Long term, I want to be able to remotely create a randomly generated one-time use code, but I definitely won’t be able to do that until I set up port forwarding, DNS, and encryption (BRUH has a great guide on this).
Also, unrelated, but do either of you happen to have an Aeotec Minimote? Bought one on sale the other day and would like to set it up as a scene controller, but I haven’t seen any entities show up in HA.
Thanks again for everything!
@siukwai is going to have to answer this as all my config is done via my Wink hub. After reading your trials and tribulations getting this to work in ZWave, I’m so glad I went the Wink hub route.
I’m just so glad you got it figured out!
Considering how easy the fix ended up being, it doesn’t seem too difficult in the end. All I really had to do was change 3 letters in my config.yaml and remove/re-add through HA. It may take me a while to figure out configurations, but I’m sure it’ll be worth it in the end.
I haven’t spent any time actually making the lock usable in HA; this was just a dry run for me to make sure that I could connect via zwave before installing the lock. I’ll probably get it installed sometime next month so won’t be mucking around in HA configs til then, but lemme know what you figure out!
And I don’t have a Minimote. My automation setup so far is actually pretty simple; just a light switch, an echo dot, and I did try a Cree zwavee bulb for a short period of time.
On a side note, don’t buy Cree bulbs even though they are cheap; when they lose power or if the power if your house’s grid is older and you get small brownouts, they will need to reconnect with the zwave network and they signal “success” by flashing on and off twice. Woke me up several times in the middle of the night with flashing lights before I figured that one out and uninstalled it.
GE Links do the same thing; after a power outage they come on full strength.
I have Lifx bulbs, and they come back on at whatever their last setting was. Long term, I’ll want more than the two I have, so perhaps there’ll be a way around them coming on after an outage at that point
Totally unrelated question:
I’m trying to get custom commands on my Echo working with HA, so I could unlock my door, etc with it. Watching @brusc’s tutorial, I got up until the Lambda test code fails due to “No JSON object could be detected.” Checked the video description and it said that I need external network access, so I moved on to his port forwarding video, got until the end of that, seemingly without a problem, but now I’m locked out of HA altogether, even through my pi’s internal IP. I happened to see that you made a post about a similar thing not too long ago, and am wondering if you could relate at all. Any idea where I could have gone wrong? I can still access ozwcp given that I start that service, so it must be related to Home Assistant somehow
Edit: Think I may have figured it out, forgot to reset my install directory a few times. No idea where I installed things I shouldn’t have, so I’ll probably factory reset everything again tomorrow. Now that I know what I’m doing lock-wise, that shouldn’t be a problem at least
If I wanted a code to be, say, 1234, would I just type 0x01 0x02 0x03 0x04, assuming the pin length is set to 4?
Did you ever make progress on this? From viewing my existing codes in OZWCP, I’m thinking they are stored encrypted since they definitely don’t match my actual codes.
Not yet unfortunately. I did make a new thread for the topic though, that didn’t really gain traction. At this point, I guess all we can do is wait for a configurator/automater to get implemented in a future HA release. Other hubs definitely support that already, and I could just as easily buy a second hub and slave it to HA to get the feature immediately, but that’s money I don’t need to spend. Plus, why buy a hub for one Z-wave device?
Other thread: Smart Lock Owners, How Do You Configure Them inside HA?
1 Like
Agree totally on not adding a second hub. I also don’t want to introduce cloud dependence or delays. Once I figure out how to do it through OZWCP (which I’ve made some progress on), I could probably code something up to add it to the HA interface in the next few months. I’ll keep following your other thread.
That’d be awesome if you could! I’m not much of a programmer myself, aside from the shred of Python you need to configure HA
Thanks for providing this solution. I realize that this is a little late but I am having the same exact issue as you guys and am unsure how to make the call to remove the node in HA as you’ve described above (I’ve never worked with JSON before). Is this syntax correct? Any advice would be appreciated. Thanks again.
{
"description": "Remove a node from the Z-Wave network. Refer to OZW.log for details.",
"fields": {
"lock":"schlage_be469nxcen_touchscreen_deadbolt_locked_5"
}
}
- Joe