KeyMaster Z-Wave lock manager and scheduler

Share your Projects!
#82

I am unfortunately getting a similar error. Everything seems to work fine with my front door lock if I remove the single quotes from input_boolean.allow_automation_execution and input_boolean.allow_automation_execution in my scripts.yaml:

# LOCK MANAGER 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

However, my second (garage) lock is not functioning properly. I am getting the following errors in log:

Error while executing automation automation.garagesd_clear_code. Invalid data for call_service at pos 1: expected int for dictionary value @ data['code_slot']

AND

Error rendering data template: str: Invalid entity ID 'input_text.garagesd_pin_'

If I run ‘lock.set_usercode’ from services tab with the following data:

node_id: 12
code_slot: 1
usercode: 1234

It seems to work. Obviously doesn’t change the code in lovelace but if I check through the zwave panel I can see the code has changed.

#83

I removed the ’ ’ from those entity_id: sections and my errors went away, but none of the functionality is still working. I did notice some more of the ’ ’ in the _lock_manager_common.yaml file so you may want to check there and see if that resolves the issues for your other door locks.

I tried to run the ‘lock.set_usercode’ from the services tab and the ‘lock.get_usercode’ but they don’t work for me so i’m thinking there is something else that i’m missing also.

I used to use the code from here https://community.home-assistant.io/t/zwave-lock-manager/79252 and that was working.

#84

Yeah, I think my removing those actually did nothing… I found some better ways to debug and found it was a false positive. Anyhow, hate to say the obvious, but you’ve checked your entity ID naming, right?

#85

I am unable to run ./setup.sh

I get…

“bad interpreter: No such file or directory”

Any ideas? Thanks.

#86

where are you trying to run it?

#87

yeah i checked them over several times and no luck

#88

Not sure what you mean. Ubuntu terminal I guess?

#89

have you tried to install gawk? mentioned here:

#90

Yes I saw that comment before and installed gawk via the apt install method.

#91

I’ve been testing the code by adding notifications right after the trigger happens and I get the initial notification (Code Created step 1). However, I am not getting the notification that it’s finished (Code Created Done) after the service: lock.set_usercode section

    - alias: OutsideGarageDoor Add Code
      condition:
        - condition: state
          entity_id: binary_sensor.allow_automation
          state: 'on' 
      trigger:
        entity_id: binary_sensor.active_outsidegaragedoor_1, binary_sensor.active_outsidegaragedoor_2, binary_sensor.active_outsidegaragedoor_3, binary_sensor.active_outsidegaragedoor_4, binary_sensor.active_outsidegaragedoor_5, binary_sensor.active_outsidegaragedoor_6
        platform: state
        to: 'on'
      action:
        - service: persistent_notification.create
          data_template:
            title: "debug"
            message: "Code Created step 1"
        - service: lock.set_usercode
          data_template:
            node_id: >- 
                {{states.lock.schlage_be469nxcen_touchscreen_deadbolt_locked_outsidegaragedoor.attributes.node_id}}
            code_slot: >-
                {% set object_id = trigger.to_state.object_id %}
                {% set index = 17 %}
                {% set code_slot = object_id[index:] %}
                {{ code_slot  }}
            usercode: >-
                {% set object_id = trigger.to_state.object_id %}
                {% set index = 17 %}
                {% set code_slot = object_id[index:] %}    
                {% set codetext = 'outsidegaragedoor_pin_' + code_slot | string %}
                {% set code = states['input_text'][codetext].state %}
                {{ code | string }}
        - service: persistent_notification.create
          data_template:
            title: "debug"
            message: "Code Created Done"
#92

Forgot to ask, any errors in your log when running lock.set_usercode from your developer panel?

#93

Not showing any errors when i use the developer panel.

#94

That is super strange. Can you ensure that node_id is active and the default user codes are associated with it?

#95

when i try to run the unlock using developer panel or even from Lovelace lock/unlock, the door locks and unlocks and it says unlocked from RF or something in that nature.

#96

Have you verified you are using the correct node_id when calling the service from dev panel?

#97

yes and i made sure the lock node id matches with the zwave one.

#98

Hmmm… without seeing your lock-manager files, zwave setup, entity ID list, and logs… this is really tough to debug. It has to be something super small though. If you can find a way to post some of the above elsewhere, let me know… happy to dig further when I find some time.

#99

I think i’ve configured everything correctly including adding the _frontdoor suffix to all my lock related entities as well as adding the “base lock” to the .ini. However, I’m getting the below referenced, “entity not available” issue. Has anyone dealt with or found a solution to this issue?

image

#100

Hi! I thought I’d installed simplified Zwave lock manager correctly, but clearly something has gone wrong. Specifically, I’m getting several errors:

  1. HassIO is giving me: “Component error: system_ready - Integration ‘system_ready’ not found. Component error: allow_automation - Integration ‘allow_automation’ not found. Component error: input_boolean.system_ready - Integration ‘input_boolean.system_ready’ not found. Component error: allow_automation_execution - Integration ‘allow_automation_execution’ not found.” -->the instructions said to add these “to the existing configuration”–I assumed that was configuration.yaml, so I added them but this seems to be causing an issue.

  2. On the lock page of LoveLace, I get the following errors of entities not being found.
    “Entity not available: input_text.frontdoor_name_1…” etc. as some users have noted above.

Here’s my entity list:

image
image1764×850 62.5 KB

And here’s my .ini file to configure this:

#See README for more information.
[lockmanager]

#number of PINS to setup in lovelace
numcodes=6

#the name or location of the lock you are setting up (no spaces)
lockname="FrontDoor"

#the "lowest common denominator" of the factory lock name.
lockfactoryname="yale"

#The name of the (optional) door sensor.
sensorname="FrontDoor_dummy"

#the "lowest common denominator" of the factory door sensor name.
sensorfactoryname="dummy"

#the Home Assistant EntityID of your (optional) garage door
garageentityid="cover.dummy_garage"

Any ideas where I’m going wrong? Thanks for any insight ya’ll can provide!

#101

post your relevant configuration.yaml file.