KeyMaster Z-Wave lock manager and scheduler

Share your Projects!
522

Yes, this is what I have:

Screen Shot 2020-07-28 at 13.35.19
Screen Shot 2020-07-28 at 13.35.19778×874 27.9 KB

523

Did you get an error after turning Enabled on?

524

Nope, nothing related to lock-mnager

525

And if you check under commandclass 99 in MQTT for your lock, do you not see the code 1234 for slot 1?

Example:
topic: OpenZWave/1/node/14/instance/1/commandclass/99/value/3096224984514583/
value:

{
    "Label": "Code 11:",
    "Value": "1234",
    "Units": "",
    "ValueSet": true,
    "ValuePolled": false,
    "ChangeVerified": false,
    "Min": 0,
    "Max": 0,
    "Type": "String",
    "Instance": 1,
    "CommandClass": "COMMAND_CLASS_USER_CODE",
    "Index": 11,
    "Node": 14,
    "Genre": "User",
    "Help": "UserCode 11",
    "ValueIDKey": 3096224984514583,
    "ReadOnly": false,
    "WriteOnly": false,
    "Event": "valueAdded",
    "TimeStamp": 1595709325
}
526

Sorry found the error, grab 0.0.2-1-ozw via HACS.

527

Im not using OZW should I still get the release?

528

sorry i thought you were.
does it work if you manually trigger lock.set_usercode from services?

529

It works if I call the service manually

530

Ok give me a few to review the template some more, I haven’t done a deep look at everything yet.

531

Great, let me know if you need anything!

532

Did you create a binary_sensor called allow_automation per the Readme?

533

That part I missed, I was trying to get the above tings to work before getting to the next steps.

So no I’ve added them like this:

input_boolean:
  allow_automation_execution:
    name: 'Allow Automation'
    initial: off
  system_ready:
    name: 'System Ready'
    initial: off
    
binary_sensor:
  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

But I’m getting an error:
Invalid config for [binary_sensor]: required key not provided @ data[‘platform’]. Got None. (See ?, line ?).

Not sure if i’m doing this right. I already played with indentation but still no luck.

534

Give this a shot

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

I got a new error with that:

Invalid config for [binary_sensor]: required key not provided @ data[‘platform’]. Got None. (See ?, line ?).

7:03:15 PM – Hass.io (ERROR) - message first occurred at 6:53:35 PM and shows up 3 times

mapping values are not allowed here in “/config/configuration.yaml”, line 68, column 24

7:03:15 PM – util/yaml/loader.py (ERROR)

536

It’s the indents.

EDIT: Adjusted indents and order.

537

So now I got no errors but the code is still not being passed to the lock

538

The input_boolean allow_automation_execution is turned on?

539

It was off and I put the state to on throu developer > states but still now luck. I’m gonna try restarting HA.

EDIT: it didn’t work.

540

I’m still looking into it, stand by.

Edit: @jvidales alright give the new version a shot, please review the updated Readme as well.

541

I’ve completely tested the 0.0.3 version on my own lock/HA system and the templates work, with that in mind, I’ve only tested with the OpenZwave Beta version.