KeyMaster Z-Wave lock manager and scheduler

[darrylb (Darryl)]

It gets stuck. Ill run the refresh_codes shortly.

[firstof9]

Right for this use case I’d suggest not running both at the same time

[tykeal (Andrew Grimberg)]

And that’s why I just opened a couple of issues against the repo as I tried to get it setup on my test system. It’s not going very far since I don’t have an actual Zwave lock attached to my test system but a virtual lock via the virtual components HACS integration.

[Rodrick]

@darrylb

which are stuck always in “adding”

What you explained is something I am very familiar with, I used to get this a lot, the solution is to add a buffering repeater between the lock and your HA instances. A buffering repeater can be any AC (non-battery) power ZWAVE device or an actual Zwave extender.

I have experinced this with HA and Samsung Smartthings Aeotec Hub V3.

The symptoms of the issue are, you can lock or unlock the lock remotely, but sending programing commands are delayed, unresponsive, or returns an error.

I have several locks, what I’m currently using is Aeotec Range Extender 7 (s2) or a ZWave Outlet.

[darrylb (Darryl)]

I actually have 3 repeaters, specifically the Aeotec Range Extender 7 with s2 security online/healthy. Never solved this issue.

Last time I tried to disable/re-enable and it gets stuck on adding, I didnt see a zwave command get issued, so I suspect my area is before zwave specifically.

[darrylb (Darryl)]

So, I can it on my 3 locks. It solved one of them! Not the other 2…

[info4hx4 (John)]

@tykeal

@info4hx4

I would love to see a matrix of locks.

Probably wouldn’t be a bad idea. I can state that Kwikset’s Zwave compatibility seems to pass muster for KeyMaster. They’re the only locks I use. I’ve got several of the older 910s, 912s, and the newer HC620s. Pretty much all the problems I have with the locks is the initial setup and occasionally the lock missing a code update when the Zwave network is a little saturated with events. That’s usually cleared up with a keymaster.refresh_codes call.

I installed the Kwikset CH-620 Z-Wave, without problems, despite the documentations.

Thank you for the recommendation.

[tykeal (Andrew Grimberg)]

Which ZWave server are you running? I personally switched to the ZWave-JS UI one so that I could directly inspect what the codes in the slots are.

A few times I’ve seen issues where there was another slot with the same code I was trying to set, or at least the first 4 digits were the same. I know that on Kwikset locks (or at least the older ones) the first 4 digits have to be unique for some messed up reason, so, while you can have codes that are longer (up to 8 digits) they’ve killed off a large portion of the PIN space by doing that.

If you’re running the HA ZWave-JS (which is what gets installed by default when you add the ZWave integration) then you would need to turn up the logging on it and try resetting the slot code and watch the logs to see if it complains of a code already in use.

[firstof9]

A lot of the time codes getting stuck are because the UserCode command class is missing and the lock needs to be re-interviewed. Why I always recommend to install ZwaveJS UI.

[info4hx4 (John)]

No idea. How could I tell? And, how would I switch back and forth?

[firstof9]

@info4hx4

how would I switch back and forth?

You don’t stick to ZwaveJS UI.

@info4hx4

How could I tell?

You’d be missing the Command Class called UserCodes from the list.

[tykeal (Andrew Grimberg)]

@info4hx4

how would I switch back and forth?

As @firstof9 states, you don’t switch back and forth. I recommend using this post on how to switch to ZWave JS UI and retain all your names and configuration.

[greysnowcat]

Sorry for slow reply, I’ve been getting over a nasty cold.

This is what I see when I check dev tools

[firstof9]

And what’s the error message in home-assistant.log ?

[greysnowcat]

Interestingly enough I ran the HA update 2023.2.2, a day ago, and suddenly the notification started coming to my HA mobile app on Android when the lock is used. It must not have loaded the scripts and automations after I fixed the entity names.

I am seeing the following in the logs though:

Also, when the lock is manually cycled the notification is showing as Manual Lock (user for Code 1) and I’m not sure why that is occurring, when the old behaviour was to just note the lock was manually cycled.

Any ideas?

[firstof9]

“Already running” is fine you can ignore those messages or set the script to parallel mode.

@greysnowcat

Also, when the lock is manually cycled the notification is showing as Manual Lock (user for Code 1) and I’m not sure why that is occurring, when the old behaviour was to just note the lock was manually cycled.

This is what the lock is reporting. Manual lock/unlock and then it sends what slot, usually slot 1, it’s a firmware thing.

[aellicott09]

That worked amazingly. Thank you

[ehfortin]

Hi,

At step 8, when you say to copy in the generated dashboard configuration, is that the file MY_DOOR_lovelace that you are referring to? And if so, you just write it over the 2-3 lines that are there by default when creating a customer dashboard?

That’s what I did but I’m getting this as a result:

So, I guess it’s the proper place and right file but there is something incorrect for sure. Missing file somewhere?

[tykeal (Andrew Grimberg)]

Looks like 2 different issues to me.

1. Verify that you have the following in your configuration.yaml under the homeassistant section:

packages: !include_dir_named packages

2. Check the wiki again for the extra front end components you need to install via HACS

You will need to restart your HA if you’ve had to add the packages declaration.

[ehfortin]

Hi,

Yes, I finally find the right wiki and have it working now.

Thank you.