KeyMaster Z-Wave lock manager and scheduler

Ah auto dashboard, you can’t.

You can set the input_text attribute to have “password”, this is the default in the updated/renamed Keymaster integration.

If the zwave2mqtt system doesn’t expose a service, nothing we can really do.

Thanks again!

One last hopefully obvious fix question.

No notifications are getting generated and I get the following error. I assume I’ve missed something simple.

Any suggestion?

Logger: homeassistant.components.automation.frontdoor_user_notifications
Source: core.py:1395
Integration: Automation (documentation, issues)
First occurred: 12:02:53 PM (2 occurrences)
Last logged: 12:02:53 PM

While executing automation automation.frontdoor_user_notifications
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 404, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1026, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 242, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 250, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 460, in _async_call_service_step
    await self._async_run_long_action(service_task)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 419, in _async_run_long_action
    long_task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1395, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Unable to find service script.frontdoor_manual_notify

Whats the difference between the zwave2mqtt vs OZW? They both have a UI if you choose and both can run independently of HA.

Unless I missed something. OZW UI is based on VNC which I find to be clunky. ZWAVE2MQTT is a Web Interface. It is more aligned to the Zigbee2MQTT interface.

So did you get it to work with lock-manager/keymaster for setting and unsetting the codes?

No without that service call it’s not going to work. I will have to look at my options. Maybe move to OZW. Zigbee is easy compared to ZWave.

Perhaps some zwave2mqtt folk are following this and know what magic sauce they have to brew.

ozw-admin is a native windows application that can be installed on any windows machine. The VNC that you’re referring to is just a convenience for the people who don’t want to install the app on their workstation, but it’s not required if you use the native windows application.

1 Like

See the wiki, you have to make your own script since not all the notification utilize the same arguments :frowning:

Hi all,

I’m just moving from Smartthings to HA, and installing Lock manager to control my Schlage BE469 (OZW). I’ve followed all the instructions in the original post, but I’m getting a configuration error as follows:

Error loading /config/configuration.yaml: Secret GAagent_user_i not defined

I’m at a loss and searching the thread (and google) has been no help. Anyone got advice?

Check your formatting and indentation on your configuration.yaml file.

Thanks for the suggestion. I just double checked and removed any tab indents caused by c/ping the original post. As far as I can tell, it’s correct.

Just to make sureI’m not an idiot, the only thing that should be going into config.yaml is the binary sensor, correct?

Only thing going in configuration.yaml is the packages include.
See the wiki.

Okay, I’m confused…

I didn’t start with the wiki, but now that I have, just to clarify: once I follow the pre-install steps, does that mean I don’t need to add the automations, script, and binary sensor in the first post? I see the binary sensor in the ozw.yaml file I created, and it has a couple automations (missing the “homeassistant start-up” from post 1 but it has the other 2, and it does not have the script listed in post 1.

Are those instructions depracated? I assumed not since there are other obsolete instructions that have been marked out as well.

Once you add that line from the Wiki into configuration.yaml, you don’t need to add any additional lines, you download the ozw.yaml or zwave.yaml and place it in the packages directory. Less fuss :slight_smile:

Way less fuss! Thanks for pointing me in the right direction. Everything is installed now, but not working correctly.

I had/have a bunch of disabled entities, including the ones for access_control and user_code that the integration calls for. I manually enabled those two and refreshed the node, but I just end up with a bunch of “entity not available” boxes. Any help on how to properly enable them? I also tried excluding/reincluding my lock in case it was just a poor pairing…

Now that you enabled the entities, re-configure the integration with the correct sensors by using the “Options” button.

Sorry, should have mentioned that I did that… no joy. I even went back and cut and pasted the lovelace data in case it changed.

And something I did fixed it. I’ve updated, recreated the lovelace dash, etc repeatedly, and rebooted several times over with no joy… I just rebooted HA one more time and all seems to be well.

Thanks a ton for your help.