KeyMaster Z-Wave lock manager and scheduler

shmookles · August 18, 2020, 6:15pm

This really ought to be built-into HA as a native integration.

FutureTense · August 18, 2020, 8:19pm

That’s kind of you to say so but I don’t think this is likely to occur. This package is essentially a GUI front end, nothing more.

jvidales · August 18, 2020, 11:37pm

Hey! I’ve updated to the latest version, a couple of errors on the new version: here they are:

maindoor_conditional_notify: Error executing script. Service not found for call_service at pos 2: Unable to find service script/maindoor_manual_notify
maindoor Notifications: Already running
maindoor Notifications: Error executing script. Service not found for call_service at pos 1: Unable to find service script/maindoor_manual_notify
While executing automation automation.maindoor_notifications

firstof9 · August 19, 2020, 3:19am

This has been removed from the package to allow customizing the notification and as not all notification services utilize the same formatting variables.

Here’s an example you can modify and place in your own scripts:

frontdoor_manual_notify:
  mode: parallel
  sequence:
    - service: notify.phones
      data_template:
        title: "{{ title }}"
        message: "{{ message }}"

It’s fine to ignore this, this is due to the new scripting engine updates.

Same as point 1

phdelmac · August 24, 2020, 11:44pm

Hello, I hope someone can point me in the right direction with my issue. I’m trying to run the latest OZW beta 0.9 and have followed the setup directions but cannot get the lovelace frontend to generate even using the setup.sh script.

Here is what I get when I try running the script.

Annotation 2020-08-24 184330

dbrunt · August 25, 2020, 12:31am

I seem to have a problem with the ozw-beta version. These automations do not trigger at startup thus the booleans are not set thus the lock manager does not update/clear codes…

Zwave_loaded_Start_System

dbrunt · August 25, 2020, 12:38am

For my Kwikset lock, I had to go to Devices, search for ozw (or from OpenZWave integration click Devices which gives you the same filtered view) and select the lock. In there I found three disabled “alarm” entities from OZW. Once I enabled them and restarted, I was able to pick them in lockmanager setup for my garage door.

Unfortunately, my Vision ZM1701 does not have those ALARM_CLASS entities so I just picked another to satisfy the setup requirements…

dbrunt · August 25, 2020, 12:42am

Removing an integration does not remove the config/packages/lockmanager/XXXXXX folder.
I had to rm -r XXXXXX so I could start over.
Also, the entities created do not get removed; I had to manually remove those as well…

phdelmac · August 25, 2020, 12:50am

I wish I could get as far as getting that with the latest ozw build. I have followed the setup but cannot get the lovelace yaml to generate into the packages/lock-manager folder

dbrunt · August 25, 2020, 1:07am

Install lock-manager v0.0.0-ozw via HACS Integrations.
Create input_booleans, binary_sensors, automations and scripts listed under Additional Setup.
Restart HA.
The in HA: Configuration, Integrations, add “Lock Manager” which will automatically take you into setting up your first lock which will populate config/packages/<your_lockname>.
Repeat the add integration for additional locks…

dbrunt · August 25, 2020, 1:09am

I’m trying to figure out how best to handle these automations and scripts since they were meant for the Z-Wave integration and not OpenZWave…

- alias: homeassistant start-up
  initial_state: true
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: script.turn_on
      entity_id: script.customstartup

- alias: Zwave_loaded_Start_System
  initial_state: true
  trigger:
    - platform: event
      event_type: zwave.network_ready
    - platform: event
      event_type: zwave.network_complete
    - platform: event
      event_type: zwave.network_complete_some_dead
  action:
    - service: script.turn_on
      entity_id: script.system_cleanup

and likewise, add the following to your 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'
      # You can add other "startup" code here if you wish

mang0 · August 25, 2020, 1:14am

Will regular z-wave integration still be updated?

Trying to decide whether I want to just go with the OpenZWave to begin with. I was thinking I’d wait until it comes out of beta before I switch over. Thoughts?

dbrunt · August 25, 2020, 1:26am

From what I understand, the old integration is no longer being maintained.
I’m switching from HomeSeer where Z-Wave has been the mainstay for 25+years.
The only issue I’m currently having is with HAB iblinds which I’ve started writing a custom device ‘handler’ for and a Monoprice branded Good Way RGBW controller which I don’t have working yet…

dbrunt · August 25, 2020, 2:20am

Kwikset Smartcode OZW ProductCodes: 0x0090 0x0001 0a001
No notification received for keypad unlock…

firstof9 · August 25, 2020, 2:35am

See this post.

mang0 · August 25, 2020, 2:52am

Decided to try to add this thru OpenZwave using HACS. Any idea why I’d be getting a “user input malformed” error when trying to add the integration? All fields are populated except “user code sensor” and “access control sensor” which have no pull down menus attached.

Never mind, I see above I’ll look into creating a dummy…
If there’s an easy way to do this, please let me know!

firstof9 · August 25, 2020, 3:37am

If your sensors are missing, you’ll want to enable them in the device.

dbrunt · August 25, 2020, 3:49am

That doesn’t work for me. I am running OpenZWave 1.6 on another box (not integrated with HA) thus it’s status is already “on” and does not trigger the automation at HA startup…

dbrunt · August 25, 2020, 3:50am

I think I need a HomeAssistant startup automation with condition if ozw status is on then enable the booleans…

dbrunt · August 25, 2020, 4:06am

I’ve setup this automation instead:

- id: 712a904051494d49824430c4ff93a387
  alias: HA Startup - Set Door Lock Booleans
  trigger:
  - event: start
    platform: homeassistant
  condition: []
  action:
  - condition: state
    entity_id: binary_sensor.ozw_network_status
    state: 'on'
  - data:
      entity_id: input_boolean.allow_automation_execution
    service: input_boolean.turn_on
  - data:
      entity_id: input_boolean.system_ready
    service: input_boolean.turn_on
  - condition: state
    entity_id: binary_sensor.ozw_network_status
    state: 'off'
  - data:
      entity_id: input_boolean.allow_automation_execution
    service: input_boolean.turn_off
  - data:
      entity_id: input_boolean.system_ready
    service: input_boolean.turn_off
  initial_state: true
  mode: single

As well as this:

- id: '1598320765664'
  alias: OpenZwave State Changed
  description: ''
  trigger:
  - entity_id: binary_sensor.ozw_network_status
    platform: state
  condition: []
  action:
  - condition: state
    entity_id: binary_sensor.ozw_network_status
    state: 'on'
  - entity_id: input_boolean.allow_automation_execution
    service: input_boolean.turn_on
  - entity_id: input_boolean.system_ready
    service: input_boolean.turn_on
  - condition: state
    entity_id: binary_sensor.ozw_network_status
    state: 'off'
  - entity_id: input_boolean.allow_automation_execution
    service: input_boolean.turn_off
  - entity_id: input_boolean.system_ready
    service: input_boolean.turn_off
  mode: single