Almost there, just checking for a way to auto-import the generated lovelace bits now 
Edit: service works
1 Like
For those having issues running the setup.sh try adding: https://github.com/firstof9/lock-manager to your HACS custom repos, youāll be able to use this same package as an integration in Home Assistant.
All the configuration will be done via the Integrations menu -> + type in the search ālock managerā.
Enter your lock information and door sensors (if applicable, if you donāt have one pick any binary_sensor from the list).
Enter how many code slots youād like, and the packages path should already be populated for you.
Once setup is complete, head over to the dev-tools > services tab there will be a new service called lock-manager.generate_package select that and for the data enter lockname: nameofLock (see example), then click Call Service your files will be generated and then you can follow the rest of the steps from the Readme
Edit:
If youāre using the OpenZwave Beta youāll want this version:
3 Likes
The OZW versions returns a 404 when trying to add into HACS.
Thanks. How can we select which branch we can pull from HACS (so we can use the OZW Beta branch?
Nothing seems to be created when I call the service. I canāt see any error in the log eitherā¦
Susecting a permission issue at this stageā¦
Have you come across this issue before?
Nope everything should have the same permissions that homeassistant has.
Can you screenshot your config screen?
Iād have to do a release or you can just download it into custom_components manually. Hopefully @FutureTense comes back and we can get them merged. 
Same problem here, im calling the service but nothing seems to happen.
Check your home-assistant.log for errors, it should create everything for you.
Example: /config/packages/frontdoor/ should contain yaml files and a frontdoor_lovelace file.
Hello, thanks for your reply. I got the directory to display, but after pasting the frontdoor_lovelace content, I donāt see anything. I see the tab but thereās no content in it. I went to the logs but couldnāt see anything related to it.
Did you paste it in the raw config?
Yes, I pasted it in the raw config. I started all over and still no luck.
When I run the service it is generating the files inside the lockmanager directory, instead of inside my directory. My lockname directory is empty. Iām not sure if this has anything to do with.
No thatās just organization, you can move them manually into there.
Did you restart Home Assistant after generating the files?
Also did you install the additional custom cards for lovelace per the Readme?
The easiest way to add these plugins is using the Home Assistant Community Store.
You will need to go to "Settings" and add the following repositories in order to download the plugins:
https://github.com/thomasloven/lovelace-auto-entities
https://github.com/thomasloven/lovelace-card-tools
Yes, I restarted Home Assistant and used HACS to add the plugins. Also I added the resources in my Lovelace conf.
Does your configuration.yaml have packages enabled?
Example:
homeassistant:
packages: !include_dir_named packages
Yes, I have the following lines:
homeassistant:
customize: !include customize.yaml
packages: !include_dir_named packages
Double check your dev-tools -> states for the input_numbers for the locks, if they exist then itās just a matter of formatting in the lovelace config.
Yes, the inputs are there
UPDATE: I finally got an error in the logs:
Could not render template maindoor Status Report, the state is unknown
Did you modify your entity_id's for your lockās alarm_type and alarm_level?
The status report is at Line 48 in maindoor_lock_manager_common.yaml