Super Simple Lock Manager available

[UngluedChalice]

@kaws

for keymaster_basic.yaml all I do is replace these parts with my own entities? I put **around the parts

    entities:
      **- lock.front_door**
      **  - lock.another_door**

Yes, but your indentation is wrong on the lock.another_door. It should be directly under the first lock, not indented.

@kaws

notify:

• name: “Lock Notify Group”
  platform: group
  services:
  - service: mobile_app_desertblade_phone
  ** - service: mobile_app_person_ha_app**

How do I find out what mine are called for these two?

Go to developer tools and then Services and type in notify and see what pops up. It will bring up the available notify services that you have set up. It’s been so long since I set it up, I’m not sure if there is something else you need to do on the mobile app to set it up. Googling will help you on this one, as this isn’t a keymaster specific thing. It doesn’t need to be two, it can be as many as you want. It is who you want to send the notifications to.

@kaws

I want a separate dashboard for my locks so I created an entire new blank dashboard. I would use the raw configuration editor and copy everything from lovelace-keymaster-basic.yaml with no changes?

You want a separate dashboard, or another tab? I just made it as another tab, but it shouldn’t matter.

@kaws

I get Entity not available.

Do you have this in your configuration file?

homeassistant:
  packages: !include_dir_named packages

Have you restarted Home Assistant?

[kaws]

The formatting is correct, I tried to make the parts I changed in bold but it didn’t format correctly on here.

I will double check but I am sure I added the packages code to my configuration. I will take a screenshot later.

I did restart HA

Do I have to install Keymaster through HACS?

[UngluedChalice]

No, you don’t want KeyMaster on there at all. We do need to install the key master basic code and put that in your packages directory.

[kaws]

key master basic code = keymaster_basic.yaml?

[UngluedChalice]

Yes, that’s it.

[kaws]

It seems I am using the wrong entity IDs since I can confused as to what entity IDs I am supposed to use.

ZWaveJS UI with Keymaster-Basic

Update Oct 15 the problem was the home_locks group entity IDs. I assumed (novice!) that i could use the entity names as the entity IDs. Oops # Add your locks here lock: - platform: group name: "House Locks" entities: - lock.node_12 #FrontDoor - lock.assure_lever_keypad_with_z_wave_plus #GarageDoor - lock.assure_touchscreen_deadbolt #OfficeDoor

Do I find the entity IDs under Zwave JS UI?

I have always used this

Settings-> Devices & Services → Entities

[kaws]

I have no clue what I am doing wrong.

Make sure I had the correct line in my configuration yaml

packages: !include_dir_named packages

Downloaded the raw keymaster_basic.yaml to make sure I did not miss anything.
Uploaded the raw yaml into the directory

Went to setting->entities. Found my lock. Copied the entity ID and replaced

I have not changed the notify lines in keymaster_basic.yaml yet (I have to find out what mine are called). But this shouldn’t affect anything?

Copied everything from lovelace-keymaster-basic.yaml without changing anything

[UngluedChalice]

Have you restarted? Wouldn’t hurt to figure out the notify part. Just go to Developer Tools and then Services and type notify. and see what comes up.

[kaws]

I have restarted. I’ll edit the notify part and see if anything changes.

I will be very surprised if that is why it is not working for me.

[kaws]

Nope, still not working. I have no idea why at this point.

[tonyvan22]

This was the fix for me: add the packages under homeassistant header in configuration.yaml, save, restart Home Assistant.

homeassistant:
  packages: !include_dir_merge_named packages/
  packages: !include_dir_named packages

[kaws]

I’m trying to under why it would make a difference by reading this documentation but it will take me a while to process it. Packages - Home Assistant

I’ll definitely give it a try when I have a chance! Thanks!

[ultrazero (Greg)]

This integration seems like the ticket. Any desire to get into HACS?

[fresnoboy]

This seems great! Any chance it can support Yale locks with Zigbee modules which are supported in zigbee2mqtt? Zwave was flaky compared with Zigbee which is very solid, and I have about half my locks moved over…

[kaws]

Updating, this did not fix the issue. I haven’t had time to troubleshoot as other things have taken priority

[tlgraf84]

This might be exactly what I’m looking for. But after installing I don’t see an interface for each of my different locks. Does this apply the same codes to all locks at once? I would like the codes to be different for one of my locks… Any tips? Thanks!

[UngluedChalice]

This is just a simple one, so all codes are applied to all locks.

[kenwiens]

I see that this started from simple_lock_manager, that had a limit of 8 or 9 codes. I currently use 13 codes. Is this supported in this (keymaster-basic)?

[MeChicago]

This. This right here was the answer for me.

I am brand new to home assistant, the most important thing for me is lock maintenance and I started with that. I had problems with every lock manager I have been looking at until I saw this comment.

Keymaster Basic seems great and I am going to play a little more with it but making sure it is linked in the configuration.yaml is what made my dashboard go from “Entity not available” to usable!

[markaggar (HassMan)]

No, only 9. Due to the dodgy YAML code I developed - I couldn’t figure out how to deal with double digit numbers…!