Hello again,
Im sorry I had to leave town for the past 2 weeks but I’m back now trying to get this all sorted.
So I tried to add a new code and got the following error:
hold tight, we’re reworking some of the templates for less errors 
Alright everyone, the latest version is now up on FutureTense’s repo:
Please point your HACS to his repo as that is where any further development will occur.
If you are using OZW make sure to enable betas in HACS.
Steps to enable beta:
Once you do that you’ll see the -ozw versions in the drop down.
You are no longer required to rename your sensors, except to help you determine which door/sensors are which. Updated README is still in progress.
If you’re running the beta, yes, otherwise there’s the regular 0.0.6 for zwave you can use, same rules apply no more having to rename the sensors, etc …
so I can just use the built-in weave integration, no need for any additional z-wave ad-ons like the beta – correct?
That’s correct, just make sure you don’t grab a version tagged with -ozw at the end, or leave the Show Betas toggled off.
Yikes that was it, sorry not sure how I grabbed the wrong but it shows now - Thx
“If all goes well, you will also see a new directory (by default <your config directory/packages/lockmanager/> ) for each lock with yaml and a lovelace files.”
Do I need to do something for this package to show or should it be auto generated?
With the latest code it should generate when you press ‘Submit’.
Did you add the integration?
The adding the integration was the missing piece for me. I started filling out the form and stopped when it asked for the Alarm Type & Alarm Level sensors. I have a Schlage BE469 however I don’t have either of these entities associated with the lock. A number of other sensors and binary sensors but not Alarm Type or Alarm Level. Will this be issue to utilize this setup? Can they be left blank? Maybe the bigger question is why I don’t have them if it seems like I should for the BE469.
That Alarm Type and Alarm Level will only let you select the appropriate sensor, if I recall correctly. If you click the dropdown only one entity should be listed.
^ This
No
Sorry I should update the text to say Alarm Type/Access Control and Alarm Level/User Code. The readme is still getting worked on to help clarify these things as well. Also, if you don’t have a door sensor you can pick any binary_sensor as it’s only used if you are monitoring the opens and closes of the door, or make yourself a “dummy” template sensor and use that.
ah, I do have Access Control and User Code sensors. I’ll try those. Thx
I switched over to the OpenZWave integration, and in hindsight I wish I hadn’t. It was a royal pain in the neck getting things working. Even when I decided to abandon that approach and go back to the original Zwave network, it was headache after headache.
The one thing I learned is that after doing anything with zwave devices is to be extremely patient after removing and adding nodes (secure or otherwise) to your network. It sometimes takes minutes, or even hours for your devices and associated entities to appear in Home Assistant.
Another thing to be aware of, is don’t go “toggle crazy” turning input_booleans on/off to test if a PIN is part of a lock. I’ve been having unreliable performance, where the PIN is not matching the visual state of the lock.
YMMV when switching over 
My switch over was super smooth, but then again all my devices are mains powered no batteries except for my lock. 
Had I to do over again, I’d have done a factory reset on every Zwave device and started with OpenZWave from the get go. Even if the interface leaves a lot to be desired. Fortunately @firstof9 knows his stuff and was able to get me over most of the humps.
I was laughing about this, because I’ve probably struggled with this more than anyone else. And I wrote the friggin project. But AFAIC this is just as much @firstof9’s project as it is mine. He brought it to the masses with HACS integration. I’m extremely grateful for his participation in all things Home Assistant.
Also of note is the helpful gurus in #zwave on discord. Freshcoast knows the SDS docs inside and out. lol
