KeyMaster Z-Wave lock manager and scheduler

FutureTense · October 9, 2020, 3:56pm

Did you rename those by adding sidedoor to the end?

FutureTense · October 9, 2020, 3:57pm

You are using zwave so you shouldn’t have that.

Leaffan · October 9, 2020, 4:04pm

Yes _sidedoor added

Leaffan · October 9, 2020, 4:06pm

Right but the automation to run the script.system_startup_cleanup will not run without binary_sensor.ozw_network_status set to on

firstof9 · October 9, 2020, 4:28pm

I’ll have to take a look at @ptdalen’s setup and see if we can compare those codes.

mmiller7 · October 9, 2020, 8:24pm

Is there a way to install Lock-Manager without HACS?

I seem to be stuck with HACS saying “HACS is waiting for Home Assistant to finish startup before starting startup tasks” forever (20 minutes so far…running on a VM x86_64 Xeon 3.7GHz server 4 CPU cores, 2GB RAM, SSD backed disk…). Everything else looks like its alive and well, no idea why or what it means.

EDIT: Nevermind…after 30 minutes it finally started. No idea why. I am still curious if HACS is actually required.

firstof9 · October 9, 2020, 8:50pm

Not required but it makes it tons easier to manage updates.

Deonte_Threatt · October 9, 2020, 10:26pm

I have tried to follow the instructions and search the form but it is not generating the input_text for the pins

firstof9 · October 10, 2020, 12:06am

Update to 0.0.23, that was some of my testing code that slipped in. Once you update go through the Options and just hit Submit it’ll generate the needed bits. Then you can head to Server Controls and reload Input Text and you should be all set.

Amishman · October 10, 2020, 1:07am

I must have done something wrong. It doesn’t seem to work. I added the code and restarted HA. binary_sensor.allow_automation is set to off. I change a code from disconnected /connected but it doesn’t change. If I go to automations and manually execute open_zwave_network_up it works and changes it to on. There are no error messages.

- alias: homeassistant start-up
  initial_state: true
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: input_boolean.turn_off
      entity_id: input_boolean.system_ready
    - service: input_boolean.turn_off
      entity_id: input_boolean.allow_automation_execution


- alias: open_zwave_network_down
  initial_state: true
  trigger:
    - platform: state
      entity_id: binary_sensor.ozw_network_status
      to: "off"
  action:
    - service: homeassistant.turn_off
      entity_id: input_boolean.allow_automation_execution
    
- alias: open_zwave_network_up
  initial_state: true
  trigger:
    - platform: homeassistant
      event: start
    - platform: state
      entity_id: binary_sensor.ozw_network_status
      to: "on"
  action:
    - service: homeassistant.turn_on
      entity_id: input_boolean.allow_automation_execution

firstof9 · October 10, 2020, 1:25am

In dev-tools -> States what does binary_sensor.ozw_network_status show? On or Off?

Amishman · October 10, 2020, 1:44am

I restarted HA and binary_sensor.allow_automation is set to off. binary_sensor.ozw_network_status shows on.

firstof9 · October 10, 2020, 2:39am

Check your log for errors.

firstof9 · October 10, 2020, 3:48am

Version 0.0.22 - 0.0.23

Changes

Removed “Confirmation” dialog the package will now get regenerated after you hit the submit buttons
Reverted change of input_number back to input_text for the PINs (this was testing code shouldn’t have been there)

Bug Fix

Fix small bug with config flow not triggering the regeneration

Reminder: If you have any feature requests or found a bug, feel free to report them on the Github Repo’s Issue page.

rda1990 · October 10, 2020, 4:06am

I am missing the service binary_sensor.ozw_network_status I am running zwave not open zwave.

firstof9 · October 10, 2020, 4:16am

You’ll need a different automation to toggle the input_boolean when Home Assistant starts up.
Let me see what I can find.

EDIT (for zwave something like this should work):

- alias: open_zwave_network_down
  initial_state: true
  trigger:
    platform: event
    event_type: zwave.network_stop
  action:
    - service: homeassistant.turn_off
      entity_id: input_boolean.allow_automation_execution

- alias: open_zwave_network_up
  initial_state: true
  trigger:
    platform: event
    event_type: zwave.network_start
  action:
    - service: homeassistant.turn_on
      entity_id: input_boolean.allow_automation_execution

(there may be indention errors)

Amishman · October 10, 2020, 12:42pm

I restarted my virtual machine and HA and binary_sensor.allow_automation is set to off. binary_sensor.ozw_network_status shows off. There are no errors in the logs.

This is my configuration.yaml.

homeassistant:
  packages: !include_dir_named packages

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

input_boolean:
  allow_automation_execution:
    name: 'Allow Automation'
    initial: off

  system_ready:
    name: 'System Ready'
    initial: off

binary_sensor:
  - platform: template
    sensors:
      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

  - platform: mqtt
    name: ozw_network_status
    state_topic: OpenZWave/1/status/
    value_template: >
      {{ "ON" if value_json.Status in ["driverAwakeNodesQueried", "driverAllNodesQueriedSomeDead", "driverAllNodesQueried"] else "OFF" }}
    json_attributes_topic: OpenZWave/1/status/
    device_class: "connectivity"

This is my automations.yaml.

- alias: homeassistant start-up
  initial_state: true
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: input_boolean.turn_off
      entity_id: input_boolean.system_ready
    - service: input_boolean.turn_off
      entity_id: input_boolean.allow_automation_execution


- alias: open_zwave_network_down
  initial_state: true
  trigger:
    - platform: state
      entity_id: binary_sensor.ozw_network_status
      to: "off"
  action:
    - service: homeassistant.turn_off
      entity_id: input_boolean.allow_automation_execution
    
- alias: open_zwave_network_up
  initial_state: true
  trigger:
    - platform: homeassistant
      event: start
    - platform: state
      entity_id: binary_sensor.ozw_network_status
      to: "on"
  action:
    - service: homeassistant.turn_on
      entity_id: input_boolean.allow_automation_execution

firstof9 · October 10, 2020, 4:21pm

There’s your problem.

jvidales · October 10, 2020, 6:23pm

Hello, is this app compatible with zigbee keypads? or could it be?

Thanks in advance

firstof9 · October 10, 2020, 11:49pm

I’m sure it could be made to.