It should flip to “On” when the pin in HA and the pin in the lock match 
FYI - The UI has been cleaned up a bit. PINS are now in one of four possible states
- Connecting (PIN is trying to be added to the lock)
- Connected (PIN has been added to the lock and confirmed)
- Disconnecting (Code slot is trying to be cleared)
- Disconnected (Code slot has been cleared and confirmed)
First off let me start out by saying thank you to FutureTense and firstof9 and everyone else that has helped with this project.
I am in the process of setting up the intergration using HAC and am running into some issues. Hopefully somebody can help me.
I have a single Schlage (Allegion) BE469 Touchscreen Deadbolt that I would like to use with this project but am running into issues with the configs. Is it possible for somebody to post a copy of their working configuration.yaml, automations.yaml, and scripts.yaml so I can replicate the needed functions.
I have reviewed the wiki and am running into an issue with the first steps, after creating the packages folder under the config folder and updating my Configuration.yaml I receive the following error.
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
homeassistant:
name: Home
latitude: XX
longitude: XX
elevation: XX
unit_system: imperial
time_zone: America/New_York
cloud:
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
packages: !include_dir_named packages
Cool - I assume that will be in the next update?
Also, is there a button I need to push to “send” the new codes to the lock? Or does it just happen after I enter them?
I think you need to move the
packages: !include_dir_named packages
to underneath the
homeassistant:
section.
1 Like
That is correct. 
To send the codes you toggle the “Enabled” switch. Once you turn this on, it sends the codes.
The codes are sent once you flip the enable switch.
OK, that’s what I thought, mine didn’t seem to get the codes for some reason. I’ll try again and see if I can get the relevant entries in the z-wave log.
Edit: when I disable, then enable it, I don’t see the node being interacted with at all in the z-wave log. My node (node 25) isn’t even mentioned. Does it just queue up the changes and wait for the device to check in? Or push them immediately?
Immediately, if allow_automations is off, then no codes get send.
I think it’s on:
input_boolean:
binary_sensor:
But I just can’t seem to get the UI to send the codes (at least according to the log)
Is it possible that the fact that I don’t have a user_sensor entity is causing this to break?
What do you mean?
Sorry, here’s what I mean:
The User Code Sensor dropdown shows only:
sensor.door_lock_alarm_level_backdoor
and not
sensor.be469zp_connect_smart_deadbolt_user_code
like the example in github. I just don’t have an entity available in HA for the lock.
If you renamed your entities that’s fine, those should be the correct ones.
However your “start from code slot#” should be 1.
I only renamed them to remove the “schlage be…” stuff to make it more readable, but I always keep the actual entity type in the name (in this case “alarm_level”). I just want to make sure I am selecting the right one.
As for the start from code slot - I have a code entered into the door manually (so we can still use it while I get this set up in HA). Will starting from 1 overwrite that code?
1 Like
Shouldn’t but I guess to be on the safe side, hold off changing it for now.
Ok so I followed the guide and am now stuck with the following issue from the web UI. I see the following
When I try to send the new pin to the lock it does not seem to send. It shows "PIN Synchronized with lock. I also see an entity not available from sensor.frontdoor_code_slot_1 and so on.
I can send the lock codes using the built in HA service and from the Z-Wave Node Management screen.
I’m in the same boat as you. I’ve never been able to see a “user_code” entity for my Schlage lock. The only thing that dropdown shows for me is an “alarm_level” entity which feels incorrect…