This is mentioned in the wiki right here: Notification Example Script · FutureTense/keymaster Wiki · GitHub
I’ve been using KeyMaster since 2023, and my automation is filled with tasks that were never run. Are they safe to delete?
I’m hesitant to remove them in case it disrupts my integration, which has been running smoothly for years.
I dont understand your comment… I did not create any notification automations. I only enabled them in the UI…
apologies, I clearly do not understand all of this, and have found no info in the Wiki that details what those top buttons do.
@Ltek the notification automation looks for a script called keymaster_<doorname>_manual_notify which you need to create. Replace <doorname> with the name of your keymaster definition. In this case given the error you provided you need to create a script called keymaster_front_door_manual_notify.
I would recommend leaving them alone. The next major release of Keymaster should clean them up. What you could do if you want to make your automations screen a little cleaner is to group them all into a ‘keymaster’ category and then just collapse it
Thank you for the reply! I’m glad I asked. Looking forward to the update. Grouping them is a great suggestion 
thank you, no where in the Wiki, not the first post on this thread, does it say we need to create the notifications manually… since it created 1000 other things I assumed it did that already and they were disabled until we turned them on in the UI.
and no matter what I try, I get an error creating the script. I’ve made at least 50 YAML automations in the last 3 weeks, never seen this error. I tried using YAML and UI. same issue.
UPDATE: the documentation’s YAML is incorrect, by a good margin. Would be good to update the online documentation to reflect the YAML I have below which does work properly (not the YAML in the screenshot)…
sequence:
- data:
title: "{{ title }}"
message: "{{ message }}"
action: notify.all_mobile_devices
alias: keymaster_front_door_manual_notify
description: ""
1 Like
That’s correct. I knew it sounded awkward when I cobbled it together, but I just wanted to be complete. That said, I never use custom day settings either except for the housekeeper. And even then I think creating an automation might be easier on the user.
Part of the reason I refused to accept donations for the project. I’d feel obligated to do a lot more than I want to, for just a few bucks.
how can we clean up the mobile notifications so they are more user friendly? examples of Current and Preferred
RF lock operation → Remotely Locked
Keypad unlock operation () → Keypad Unlocked using code N
Manual lock operation → Manually Locked
thx
I think I understand. Maybe this can get you started, the template in particular. I use this to create a log that I can view on my security dashboard. I’ll go see if I have something set up for notifications.
alias: Update Keypad History
description: ""
triggers:
- trigger: event
event_type: keymaster_lock_state_changed
event_data: {}
conditions: []
actions:
- action: input_text.set_value
metadata: {}
data:
value: >
{% if trigger.event.data.lockname == "front_door_deadbolt" %}Front door
{%elif trigger.event.data.lockname == "dining_room_deadbolt" %}Dining
room door {% elif trigger.event.data.lockname == "front_yard_deadbolt"
%}Front yard door {% elif trigger.event.data.lockname == "office_door"
%}Office door {% else %}{% endif %} {{
trigger.event.data.action_text|lower }} {% if
trigger.event.data.code_slot_name != "" %} by {{
trigger.event.data.code_slot_name }}{% else %}{% endif %}
target:
entity_id: input_text.keypad_history
mode: single
So, it doesn’t look like I did anything for the notifications, but you could.
I think you have to change the YAML from the package directory since they’re not editable via GUI. But these are the automations you’d beed to play with. Possibly you could adapt the template above. They might get overwritten if you rebuild the packages, or you could just make a totally separate automation that triggers off the same triggers as these, it just wouldn’t be turned on and off from the key master dash
thanks, yea looks like I need to create custom notifications for everything. Was hoping it would be less work and easy to mod the built-in notifications (which are not very useful in the current form)
Having code in an instructions that is wrong / doesn’t work causes pain especially for people new to HA, YAML, etc… is not cool. In the time it took for you to respond, you could have fixed the documentation since I already posted the correct code.
To be honest, this is a community based project by @FutureTense and the other great collaborators, contributors working for free. They set the framework for a great tool many needed. If you would like any customizations you can customize it to your own liking and get help like @Cake1468 has assisted you with. From time to time, they see customization or fixes they would like to add to the project and they add it, then release it.
So, change starts with you and us. So start a customization and share it with all.
Sort of feel this is why @FutureTense and @tykeal refuse to take any sort of monetary donation for this project.
I appreciate this project and all the work done on it, everyone who has helped me and I hope I have helped a few. Thanks.
3 Likes
I get it. I dont have as much time to code (or re-learn what I forgot over the years) so I do what I can.
When I create or mod something I post it back for the community. I’ve been here 2 months and posted back multiple items including modifying the Airscape whole house fan Integration, creating a virtual keypad for Envisalink, and creating complete House Mode + Security Panel workflow and methodology which combines Alarmo & a real Alarm Panel (DSC/Ademco/Honewell) into a single system (uses Alarmo in a way the author did not think of).
That’s great. I can help you customize the notification scripts, but you will have to give me some time because I’m traveling now and only have a tablet in my possession.
You will need to work with templates to get the customization you need. You can read up on that, also look at the ZWAVE logs to see what actions they report and use that in templates, you will be able to make your own notifications independent of Keymaster.
I know you are busy, but you can start small. I’ll help as much as I can,
I have been struggling with locks, time-to-time getting stuck in ‘deleting’ and ‘adding’ status.
So today I am trying to do something about this.
I have found that if I go to
Settings → Integrations → keymaster → Integration entries
and
perform a Reload on of the entries
It will corrupt the integration and cause the cards to say ‘Entity not available’ on all/most of the entities on the integration…
Should this be happening?
Restarts and Reboots of Home Assistant are not fixing this new ‘Entity not available’ problem that I have created simply by Reloading the integration entry.
There’s a couple fixes earlier in this thread that fixes this issue. In addition, there’s a beta of KeyMaster that addresses the issue.
1 Like
There’s alot going on in this thread.
I don’t know which fixes you were specifically referring to.
So I guess that I will just have to leave it broken for now.
Futhermore, I am not seeing any “Beta” versions avail if I try to redownload in HACS.
Any ETA on the release of the fixed code?