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
Oh ok so you just hit the remove node and then go unpair on the lockset? You don’t have to put anything into the “Service data” field on dev page? Thanks for the guidance, still quite new at this.
Joe
Lemme know if that works for you
OK I’ve been beating on this thing for 2 days now. I’m running on Pi virtual environment install from the Bruh video.
My z-wave config path is: config_path: /srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config
I’m trying to use the ozwcp app located in /srv/hass/src/open-zwave-control-panel.
I’ve modified options files in both places (since the control panel has it’s own options.xml) to include a network key.
I always get this error in the logs though.
2016-10-23 19:09:21.437 Info, Setting Up Provided Network Key for Secure Communications
2016-10-23 19:09:21.437 Warning, Failed - Network Key Not Set
2016-10-23 19:09:21.437 Info, mgr, Added driver for controller /dev/ttyACM0
2016-10-23 19:09:21.437 Info, Opening controller /dev/ttyACM0
<?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="0xF9, 0x09, 0xB8, 0xF9, 0x07, 0x42, 0x16, 0x28, 0x5B, 0x44, 0x21, 0xB3, 0xA3, 0xC3, 0x4D, 0x34” />
<!-- 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>
The key is not important to me since I’m just starting out with secure devices. I can change it.
What am I missing here to get the key to work?
I’m new to this forum so this issue may have been resolved already. I had the same problem as @dax333. I resolved it by closing ozwcp and re-opening it. It appears that ozwcp only reads its configuration file when it starts up.