KeyMaster Z-Wave lock manager and scheduler

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.

https://raw.githubusercontent.com/FutureTense/lock-manager/master/custom_components/lock-manager/lock_manager_common.txt

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 :woman_shrugging: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?

HACS OZW beta for me. v0.0.11-ozw

@mang0 and @joe_blow, what version of Home Assistant are you using?

Home Assistant 0.114.4

Home Assistant 0.114.3

I’ve got it installed in Docker, can’t imagine that would matter in this case though…

You error message indicates that the user_code sensor is in an unavailable status.

That’s what’s got me scratching my head, here’s that sensor in States:

Mine was one of the disabled entities that I had to physically enable when I first included the lock. It shows enabled, but the statusreport sensor is still listed as unavailable in entities.

The master branch contains the old/current zwave integration. OpenZWave uses ozw.

Your sensor name doesn’t match what you posted in this post append _frontdoor to the sensor name and it should work or reconfigure the integration and re-select your sensor.