Should fire when you enter a new code on the parent, I think there’s a toggle to enable/disable the sync tho on the child lock’s view.
It should be firing off notifications. How are you checking?
found part of my issue… I created frontdoor first (parent), then populated all the codes.
Then added my garagedoor lock. nothing would sync to it until I went back to the parent door and erased the codes and re-added them. then it updated the garagedoor slots immediately. So a timing issue. HOWever… I have 4 slots total on the parent door and 4 slots on the garage door.
Slot 1 and 4 are “connected” on the master and garagedoor
Slot 2 and 3 are “adding” on the master, and “connected” on the garagedoor.
This is an odd behavior, so will uninstall all keymaster pieces and start over, (will reconfigure first… then uninstall at last resort)…something seems out of whack.
As for the notifications… that is not working → https://github.com/FutureTense/keymaster/issues/281
UPDATE:…reconfiguring did nothing, nor did removing the frontdoor lock and adding it back.
this was just working fine. guessing zwave is finicky with HA. Odd that 2 slots work and 2 do not on the BE649ZP and all 4 work from syncing to the FE599
UPDATE 2: I’m past the code syncing issue. Now just have the issue with my FE599 locks not triggering notifications. Was told to check if the devices are sending messages through events, but honestly am very lost on how to accomplish this test. If anyone can lend a hand I would be grateful.
1 Like
My unplugged Vera controller is laughing at me now. I have been unable to get my Kwikset lock using Keymaster to send notifications in Home Assistant. The lock is sending events via zwave_js_notifications. I have five more locks to try to integrate, so I’m stuck until I figure this out. Why is this part of Home Assistant so complicated (not that the other parts aren’t)? Vera can’t do 1/10th of what HA can do, but at least you could easily pair a lock with it and get it to send notifications.
Notifications get sent just fine.
This is the only item in scripts.ymal:
(Ignore the indention error)
keymaster_garage1entry_manual_notify:
mode: parallel
sequence:
- service: notify.pushover
data:
title: “{{ title }}”
message: "{{ message }}
Is this correct?
@Lonestar101 use this in the future, will make replies easier on everyone…
if is indented like this, then you are good.
keymaster_garage1entry_manual_notify:
mode: parallel
sequence:
- service: notify.pushover
data:
title: '{{ title }}'
message: '{{ message }}'
Thanks for the reply – and the formatting tip.
Once I pasted your code into scripts, notifications work just fine. Thanks for your help…and your patience with a noob.
1 Like
Hello all,
Just wanted to follow up a previous post I had in this thread as I was having some issues with getting the Yale Assure SL locks to work with this integration. What I ended up learning was a few things: 1. Reset the locks to factory settings before adding to Home Assistant. Next, only set the master code on the lock before adding to keymaster. (Add no other codes). You won’t be able to change/ modify or set the master code to anything else within keymaster. For instance, let’s say I set the master code to “1111” on the physical lock, don’t put that into keymaster as a code position because it will never go from “adding” to connected. This should get your Yale Assure working with keymaster/ HA. It did with me at least, so hopefully it’s not a YMMV (Your mileage may vary situation)
Hello,
Is there anyway to hide all of the automations this add on has created on the automations tab of my home assistant instance? Its all a mess now and was curious if anyone had any solutions to that other than 1. not using this add on or 2. making heavy use of the filter mechanism at the top of the automations page.
Thank you all for any comments on this ahead of time.
Personally, I just stick a '0 - ’ or some other number at the front of all my home grown automations. That at least puts them at the top of the listing and I can force a sort order as well.
I would love for there to be a negative filter option or better yet a more boolean logic based filter for all of the places where there’s a filter in HA
Yeah, that’s what I am doing also (somethings similar).
I would too. This stuff can be complicated enough, and having to look at a bunch of stuff I could care less about doesn’t help much. haha.
Thank you for your response here!
Hi, does this support RFID locks? My locks don’t have a pin code but rather a programmable key fob.
Since that lock uses bluetooth and not zwave, no.
There’s no zwave function to add a RFID tag as far as I can see.
What was happening when it wasn’t working? I tried to get my Yale locks working last fall, but it would get “stuck” and nothing would ever happen. I think when trying to create key codes? If this is the solution to making them work, that would be great! You said you reset to factory defaults, then assign master key code, and then add to KeyMaster?
Yeah, and one other thing I figured out is you essentially can’t reuse any keycode that is already assigned to the lock within the keymaster entry areas. So I tried to enter my master code within the keymaster HA module and it would never move status to “connected”. So when I went nuclear and restored it to factory, all codes could be entered into the keymaster lovelace entry areas except for the master code which I had already programmed into the lock to set it up.
Not being able to reuse a code that is already assigned is common among all of the locks out there. The lock isn’t going to allow the same code to be defined more than once because all the codes have to be unique in the lock.
1 Like
This makes perfect sense. I think in the heat of tech battle sometimes, the mind goes to “wth, work d$#n you” and then all logic goes out the window. haha. Thank you for the response here on this one.
I’m also seeing this on the latest version. Always reverts to 15 and 5 minutes.