The only error that matters in that shot is the very last line. It says you have the ozw version service call in there, for some reason the ozw service call slid into the regular zwave branch and fuber the service call.
If you’d like to give the new openzwave setup a try feel free, the package works with both.
It does work with both, but make sure you select the matching release.
I’m trying to build the package using the new HACS integration. I had it working fine using the script previously but wanted to add a few more code slots.
I get the following in the logs:
2020-09-02 09:45:27 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template frontdoor Status Report: str: Invalid domain name 'UC'
It appears the scripts aren’t communicating with the lock. Here’s the Lovelace view:
My thought is that the appropriate script isn’t opening the new slots. I’ve checked the yamls and everything seems to be in order.
what does line 39-40 show in your frontdoor_lock_manager_common.yaml show?
should be something like:
{% set UC = 'sensor.kwikset_touchpad_electronic_deadbolt_alarm_level_frontdoor' %}
{% set AC = 'sensor.kwikset_touchpad_electronic_deadbolt_alarm_type_frontdoor' %}
Here’s what I have in my yaml:
{% set UC = 'sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_alarm_level_frontdoor' %}
{% set AC = 'sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_alarm_type_frontdoor' %}
Of note, I also have a sensor called:
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_access_control_frontdoor
that appears as a second option in the integration configuration for the access control sensor. I’ve tried both and get the same results.
Quick question…
So say I needed to remove/re-add the node to my z-wave lock randomly. Would I be able to leave all the settings alone and then just rename all the entity IDs to what they were originally, or would I have to remove all associated files/entities and re-call the service to generate the lock package again? Thanks!
you should be using the sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_access_control_frontdoor and
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_user_code_frontdoor sensors.
What does your device listing look like?
Mine:
also worth noting, the services associated with the package are not working. They are generating:
Failed to call service lock/set_usercode. 18
yes, you can leave the settings as long as the entities are the same names.
Here’s mine:
The relevant sensors are as follows:
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_access_control_frontdoor
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_alarm_level_frontdoor
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_alarm_type_frontdoor
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_power_management
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_sourcenodeid
Oh you’re using the zwave integration, never mind.
yes, built in zwave integration. Should I try the OZW beta or does that only work with OZW?
what does line 244-246 show in your frontdoor_lock_manager_common.yaml show?
action:
- service: ozw.set_usercode
data_template:
entity_id: lock.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_locked_frontdoor
There’s the problem, drop this file into the custom_componets/lock-manager/ directory and regenerate the files.
So that removed the OZW reference from frontdoor_lock_manager_common.yaml but it’s still behaving the same. Services not working and, of course, Lovelace not responding.
I’m still unclear, in my case, which sensor I should be pointing the package to for the access control sensor as I have both:
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_access_control_frontdoor
and
sensor.assa_abloy_yale_key_free_touchscreen_deadbolt_yrd446_alarm_type_frontdoor
although I suppose that’s not relevant since I’ve tried both and it’s not working with either.
In your case, it shouldn’t matter, but alarm_type would be the one I’d pick.
Make sure your allow_automtaions is toggled on as well.
That’s toggled. I’ve checked everything else I can think of. Also, deleted the custom-component and package and tried the HACS install from scratch. Same error in the logs:
2020-09-02 19:10:34 ERROR (MainThread) [homeassistant.components.template.sensor] Could not render template frontdoor Status Report: str: Invalid domain name 'UC'
I’ve triple checked that line in frontdoor_lock_manager_common.yaml.
Curious to hear if this has come up for anyone else.
I’m actually getting that error in my logs as well, but both my front and back door locks seem to be working 
I’m using OZW though.
EDIT: Scratch that, setting user names / pin codes for my locks are working. Status notifications are not and have never been working afaik. Both sensor.frontdoor_statusreport and sensor.backdoor_statusreport are listed as “unavailable” in entities.
Did you install via HACS or with the script?