That’s the way that HA operates. The best you can do is use the filter at the top to filter the automations to the ones you want. I really wish I could find a negative filter like !keymaster in the search box. That would make it easier to hide the ones I can’t edit.
Is there a trick to getting HACS to pull the latest v0.0.75 release? It’s seemingly only finding v0.0.74 as the latest release for me, so I had to manually input the changes in services.py for the TypeError bug. 
Thanks. Yeah, the problem is it shows v0.0.75 as older compared to v0.0.74 
so now there’s a persistent update notification. But easily ignored!
Looking for any suggestions (searched the forums, no luck). I have the integration installed and all looks ok, but the codes are never added/deleted - just hang in this state. The lock responds to lock/unlock commands, so I know it’s on the zwave network and working. Suggestions?
I just ran into that myself while trying to add another code. I had finally decided to put my zwave-js into debug mode and it was getting back from the lock that it couldn’t add it because of a duplicate code (which I can’t find in a dump of the configuration!) I ended up using a different code and everything was fine (still can’t get the code I was trying to use to go in though).
I posted a “dummy” release so you can get the latest v76
1 Like
Did you change the code length? I use Zwave JS and there is a tab inside the lock node for Configuration. It must be set to the lengths you are trying to use. It looks like you used 8 in one place and 6 in another. Not sure that is your problem, but wrong code length behaves as you describe.
1 Like
Had a VERY bad day yesterday where my Aerotec dongle fried itself. Spent the better part of today readding 47 nodes into Zwave JS. I have everything back up and running but I am seeing the same issues as those above. My Keymaster is in a constant state of adding/deleting. Does not matter what you do. The lock itself has zero codes on it except the master lock code.
Locks: Yale YRD110
Keymaster Configuration: Parent/Child; then tried the locks as self-masters
HA 2021.10.6
ZwaveJS 0.1.45
Uninstall keymaster. Factory reset the lock, then re-interview it. Then install the integration.
I just got this setup and all seems to be going well so far. After migrating from SmartThings and using RBoy Apps to manage my locks and door sensors, this is pretty damned close to what I was hoping to find.
I’m not sure if I maybe missed something, but is it possible to have the auto lock timer start once the door sensor reports as closed? Right now as soon as the door is opened, the 15 minute timer starts. There are times when I leave the front door open for awhile and don’t want the lock engaging again until the door is closed.
I’m using a Yale Assure zwave lock if that helps at all.
1 Like
Any suggestions as to what the fault is when keymaster is stuck at “deleteting / adding” state on the key slots.
But there are no attempts to do anything in the logs.
The logs only list the pins that are manually set,
2021-11-01 22:16:53 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 1 value: xxxx
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 2 value: xxxxx
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 3 not enabled
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 5 value: xxxx
2021-11-01 22:16:58 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)
Defined 5 slots from slot 10 and up, also there is no entries in the zwavejs log either.
And the automation input_boolean.allow_automation_execution is active
I’m actually in the middle of tweaking this so that the timer starts once the deadbolt unlocks. Let me think about ways so users can put their own logic in.
If zwavejs isn’t showing activity then you’ve got to solve that issue first. Try interviewing the lock again.
Since I’m just getting started with migrating to Home Assistant, I have no idea yet on where I’d begin to look to poke around at some of your code. All I really want to do is add an option for myself where I can choose when to start the timer (deadbolt unlock or door sensor closed).
Hang tight. It will be the deadbolt unlocking when I push my next changes.
Hi all, wondering if someone could help me out, I migrated over to the Zwave JS from the Zwave depreciated today and no longer have the alarm type and alarm level sensor, they were turned off by default. Even when I turn them on, the status just says unknown when operating the lock. Through searching i read that in some of the JS implementation these values are no longer reported to sensors but are in the events stream. My question is though, how do you get this back into a sensor to use with this addon? Has anyone else come across this problem? is there are simpler solution? I have the Yale touchscreen Yale Key Free Touchscreen Deadbolt YRD446. Any help or pointers would be appreciated. Cheers
My Yale Assure lock did something similar after upgrading as well. The entity name reverted back to default somehow. Once I went and added _frontdoor to the end of each entity, things were back to normal.
Use the sensor.fake entries for the sensors, the integration reads the events from zwavejs internally.