KeyMaster Z-Wave lock manager and scheduler

firstof9 · June 15, 2020, 1:42pm

Apparently there’s an issue already open regarding this. It doesn’t effect me so I didn’t know it existed until l caught up on the 0.111 release blog forum post.

khouse75 · June 18, 2020, 7:16pm

Looks like there was an open issue for state history not loading when using certain databases but those didn’t apply to my situation. I ended up creating mqtt sensors to temporary store the states with the retain flag set. The retain flag is necessary, otherwise the mqtt sensor values will be unknown. These mqtt sensors are then updated when lock manager values are updated. Upon HA start, the new mqtt sensors get their values from the mqtt broker and the lock manager states are then set from from those mqtt sensors. Works perfectly every time.

This is not an issue with Lock Manager. This is an HA issue. Lock Manager is working perfectly.

firstof9 · June 18, 2020, 8:16pm

Your core.restore_state file in .storage may be corrupted.

Steps you could try:

Shut down Home Assistant
Rename core.restore_state to core.restore_state.bak
Start Home Assistant
See if the values repopulated from your database.

celoberger · June 19, 2020, 3:13pm

Hi There, I’ve installed the lockmanager and the installation seems fine, but when I enable a code, I don’t see the status turn yellow, and the codes aren’t working in the lock.
I had originally defined codes manually through the zwave console, and those continue to work fine.
Am I missing something with the installation? When I install the lockmanager, does/should it overwrite existing codes that were defined?

celoberger · June 19, 2020, 3:45pm

To add to this since I’m also new to HA, the automation that adds a code doesn’t seem to be triggered after entering the code:

How could I go about troubleshooting this?

firstof9 · June 19, 2020, 4:03pm

Check your home assistant log for errors.

celoberger · June 19, 2020, 5:20pm

Basic question, but where exactly? Developer Tools -> Logs?

firstof9 · June 19, 2020, 5:25pm

That works, check for errors saying something about automation or specifically automation.frontdoor_add_code

celoberger · June 19, 2020, 5:27pm

I see these guys:

firstof9 · June 19, 2020, 5:30pm

Did you create the binary_sensor.allow_automation entity as well?

celoberger · June 19, 2020, 6:06pm

I did not. Is it documented somewhere?

firstof9 · June 19, 2020, 6:11pm

Sure is use this link

celoberger · June 19, 2020, 6:48pm

Thank you. I’ve added the input boolean and the binary sensor but when I check the configuration I get the error below. Do I need to add all the extra code (input_boolean, binary_sensor, automation and script) in order for the config to check out or am I doing something wrong?

firstof9 · June 19, 2020, 6:57pm

Please post configuration as text, no pictures, it makes it harder to help.

Fix the input_boolean by removing input_boolean. from system_ready this should fix all those errors.

EDIT: I submitted a PR to fix the documentation to adjust that.

celoberger · June 19, 2020, 7:35pm

Sorry, will include the code. So I’m almost there. I’m still getting the error for the binary sensor. Here’s my code. I have a separate binary_sensor.yaml file which I’m including in the main config file.

Do I need to specify the platform for those binary sensors?

#wyze
  - platform: wyzesense
    device: auto
    
#Grouping of Windows
  - platform: template
    sensors:  
      window_status:
        friendly_name: 'Window Status'
        device_class: window
        value_template: >
          {% set sensors = [states.binary_sensor.wyzesense_basement_window,
                            states.binary_sensor.wyzesense_room1_window,
                            states.binary_sensor.wyzesense_room2_window,
                            states.binary_sensor.wyzesense_mudroom_window,
                            states.binary_sensor.wyzesense_office_window] %}
          {{ sensors | selectattr('state','eq','on') | list | count > 0 }}

#Grouping of Doors          
      door_status:
        friendly_name: 'Door Status'
        device_class: door
        value_template: >
          {% set sensors = [states.binary_sensor.wyzesense_garage_door,
                            states.binary_sensor.wyzesense_porch_door] %}
          {{ sensors | selectattr('state','eq','on') | list | count > 0 }}

#Lockmanager
    allow_automation:
      friendly_name: "Allow Automation"
      value_template: "{{ is_state('input_boolean.allow_automation_execution', 'on') }}"

    system_ready:
      friendly_name: "System ready"
      value_template: "{{ is_state('input_boolean.system_ready', 'on') }}"
      device_class: moving

firstof9 · June 19, 2020, 7:49pm

Your indentaiton is off slightly.

Try this:

#wyze
  - platform: wyzesense
    device: auto
    
#Grouping of Windows
  - platform: template
    sensors:  
      window_status:
        friendly_name: 'Window Status'
        device_class: window
        value_template: >
          {% set sensors = [states.binary_sensor.wyzesense_basement_window,
                            states.binary_sensor.wyzesense_room1_window,
                            states.binary_sensor.wyzesense_room2_window,
                            states.binary_sensor.wyzesense_mudroom_window,
                            states.binary_sensor.wyzesense_office_window] %}
          {{ sensors | selectattr('state','eq','on') | list | count > 0 }}

#Grouping of Doors          
      door_status:
        friendly_name: 'Door Status'
        device_class: door
        value_template: >
          {% set sensors = [states.binary_sensor.wyzesense_garage_door,
                            states.binary_sensor.wyzesense_porch_door] %}
          {{ sensors | selectattr('state','eq','on') | list | count > 0 }}

#Lockmanager
      allow_automation:
        friendly_name: "Allow Automation"
        value_template: "{{ is_state('input_boolean.allow_automation_execution', 'on') }}"

      system_ready:
        friendly_name: "System ready"
        value_template: "{{ is_state('input_boolean.system_ready', 'on') }}"
        device_class: moving

EDIT: Highly recommend using VSCode to edit your YAML files.

celoberger · June 19, 2020, 8:17pm

Thank you again, I’ll look at getting VSCode.

Thanks for the indention. All the extra manual code now checks out, and I’ve added them all and restarted HA.

Unfortunately it doesn’t seem to be working still. I’m seeing the message below, and the status shows as connected, but not yellow.

firstof9 · June 19, 2020, 8:40pm

They will never be yellow, unless your theme makes ‘on’ status yellow.

Could you post your frontdoor.ini that you edited? You might be missing the alarm_level sensor and alarm_type sensor.

celoberger · June 19, 2020, 8:52pm

Progress is being made. I had to create the two automations through the GUI as opposed to the YAML. I then restarted HA and I could see that they got triggered. Now when I disable and enable a code on the door, I can see the other automations being fired.

But when I test the code I just added, it’s still not working at the door.

#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="schlage_bolt"

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

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

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

Below are my door lock entities, just to ensure I have the lowest common denominator set correctly

firstof9 · June 19, 2020, 8:55pm

That all looks good.

Any new errors in the log?