Install lock-manager v0.0.0-ozw via HACS Integrations.
Create input_booleans, binary_sensors, automations and scripts listed under Additional Setup.
Restart HA.
The in HA: Configuration, Integrations, add “Lock Manager” which will automatically take you into setting up your first lock which will populate config/packages/<your_lockname>.
Repeat the add integration for additional locks…
I’m trying to figure out how best to handle these automations and scripts since they were meant for the Z-Wave integration and not OpenZWave…
- alias: homeassistant start-up
initial_state: true
trigger:
platform: homeassistant
event: start
action:
- service: script.turn_on
entity_id: script.customstartup
- alias: Zwave_loaded_Start_System
initial_state: true
trigger:
- platform: event
event_type: zwave.network_ready
- platform: event
event_type: zwave.network_complete
- platform: event
event_type: zwave.network_complete_some_dead
action:
- service: script.turn_on
entity_id: script.system_cleanup
and likewise, add the following to your scripts:
system_cleanup:
sequence:
#- service: homekit.start If you use homekit, uncomment this statement
- service: input_boolean.turn_on
entity_id: input_boolean.system_ready
- service: input_boolean.turn_on
data:
entity_id: 'input_boolean.allow_automation_execution'
customstartup:
sequence:
- service: input_boolean.turn_off
data:
entity_id: 'input_boolean.allow_automation_execution'
# You can add other "startup" code here if you wish
Will regular z-wave integration still be updated?
Trying to decide whether I want to just go with the OpenZWave to begin with. I was thinking I’d wait until it comes out of beta before I switch over. Thoughts? 
From what I understand, the old integration is no longer being maintained.
I’m switching from HomeSeer where Z-Wave has been the mainstay for 25+years.
The only issue I’m currently having is with HAB iblinds which I’ve started writing a custom device ‘handler’ for and a Monoprice branded Good Way RGBW controller which I don’t have working yet…
Decided to try to add this thru OpenZwave using HACS. Any idea why I’d be getting a “user input malformed” error when trying to add the integration? All fields are populated except “user code sensor” and “access control sensor” which have no pull down menus attached.
Never mind, I see above 
I’ll look into creating a dummy…
If there’s an easy way to do this, please let me know!
If your sensors are missing, you’ll want to enable them in the device.
That doesn’t work for me. I am running OpenZWave 1.6 on another box (not integrated with HA) thus it’s status is already “on” and does not trigger the automation at HA startup…
I think I need a HomeAssistant startup automation with condition if ozw status is on then enable the booleans…
I’ve setup this automation instead:
- id: 712a904051494d49824430c4ff93a387
alias: HA Startup - Set Door Lock Booleans
trigger:
- event: start
platform: homeassistant
condition: []
action:
- condition: state
entity_id: binary_sensor.ozw_network_status
state: 'on'
- data:
entity_id: input_boolean.allow_automation_execution
service: input_boolean.turn_on
- data:
entity_id: input_boolean.system_ready
service: input_boolean.turn_on
- condition: state
entity_id: binary_sensor.ozw_network_status
state: 'off'
- data:
entity_id: input_boolean.allow_automation_execution
service: input_boolean.turn_off
- data:
entity_id: input_boolean.system_ready
service: input_boolean.turn_off
initial_state: true
mode: single
As well as this:
- id: '1598320765664'
alias: OpenZwave State Changed
description: ''
trigger:
- entity_id: binary_sensor.ozw_network_status
platform: state
condition: []
action:
- condition: state
entity_id: binary_sensor.ozw_network_status
state: 'on'
- entity_id: input_boolean.allow_automation_execution
service: input_boolean.turn_on
- entity_id: input_boolean.system_ready
service: input_boolean.turn_on
- condition: state
entity_id: binary_sensor.ozw_network_status
state: 'off'
- entity_id: input_boolean.allow_automation_execution
service: input_boolean.turn_off
- entity_id: input_boolean.system_ready
service: input_boolean.turn_off
mode: single
Oh thanks. Didn’t realize so many of the sensors were disabled.
So now I (think) I have everything done, all panels are showing up in lovelace, but I am just seemingly unable to set the PIN codes via the UI. input_booleans, binary_sensor, automations, and scripts have been added… I have two PIN codes set in UI but neither are working, even with toggling off/on and with restarts. I do have one error/warning in logs:
Log Details (WARNING)
Logger: homeassistant.components.ozw.sensor
Source: components/ozw/sensor.py:40
Integration: OpenZWave (beta) (documentation, issues)
First occurred: 10:15:51 PM (1 occurrences)
Last logged: 10:15:51 PM
Sensor not implemented for value User Code
Any ideas?
Ignore that log message it’s nothing. Make sure allow_automations is on otherwise you can’t set PINs.
Are we talking at this level?
input_boolean:
allow_automation_execution:
name: 'Allow Automation'
initial: off
I played with this for most of the day yesterday including excluding/including, regenerating the lock-manager folder in packages… and couldn’t get this working. Seems like everything is good to go, except it doesn’t allow me to actually set PINs… so I guess it’s not good to go. 
Found another error:
Logger: homeassistant.components.template.sensor
Source: components/template/sensor.py:248
Integration: template (documentation, issues)
First occurred: 6:58:56 PM (1 occurrences)
Last logged: 6:58:56 PM
Could not render template backdoor Status Report: str: Invalid domain name 'UC'
Toggle the input_boolean on from the states.
I’ve updated my automations to this:
- alias: zwave down
initial_state: true
trigger:
- platform: state
entity_id: binary_sensor.ozw_network_status
to: "off"
action:
- service: homeassistant.turn_off
entity_id: input_boolean.allow_automation_execution
- alias: Zwave_loaded_Start_System
initial_state: true
trigger:
- platform: homeassistant
event: start
- platform: state
entity_id: binary_sensor.ozw_network_status
to: "on"
condition:
- condition: state
entity_id: binary_sensor.ozw_network_status
state: "on"
action:
- service: homeassistant.turn_on
entity_id: input_boolean.allow_automation_execution
with the binary_sensor:
binary_sensor:
- platform: mqtt
name: ozw_network_status
state_topic: OpenZWave/1/status/
value_template: >
{{ "ON" if value_json.Status in ["driverAwakeNodesQueried", "driverAllNodesQueriedSomeDead", "driverAllNodesQueried"] else "OFF" }}
json_attributes_topic: OpenZWave/1/status/
device_class: "connectivity"
input_boolean.allow_automation_execution state is set to on.
I’ve toggled enabled in the GUI (off/on) and nothing so far. Haven’t actually been able to have the PIN codes stick. Any other ideas you think I could try? I’m using a Schlage BE469ZP deadbolt.
Are you using ozw or zwave?
Which version are you running of the integration?
ozw. The newest version the 0.0.11-ozw.
So when you enter the PIN into the slot and toggle Enable what do you see?
Logbook shows
Status is connected
enabled_backdoor_1 turned on
Then I mosey on over to the door and try to enter the pin, and it just shows me a red x 