keymaster_lock_state_changed is an event that @brenthaag is using. I use it myself for automation triggering and that event has not changed with the v0.1.x release series.
After countless hours of troubleshooting why my HA app notifications suddenly stopped working, I finally found a fix that worked for me, so I figured Iâd share in case it helps someone else.
Before doing anything, I saved all of my codes from the Lovelace dashboard.
Then I removed my lock from Keymaster and, through HACS, uninstalled the Keymaster integration. I rebooted HA after each removal step.
After that, I reinstalled Keymaster and used the same Keymaster name as before.
Next, I deleted my entire Lovelace dashboard and added a new one from:
/homeassistant/custom_components/keymaster/lovelace/frontdoorlock.yaml
I pasted that into the bottom of the Raw Configuration Editor.
The only difference I noticed afterward is that the slot number now appears in the notification (in my case [23]). Not a problem, just an observation.
This fix worked for me on Keymaster v0.1.0.
Hope this helps anyone else running into the same issue!
Youâre close, but looking at the âstatesâ page. You need to check the âeventsâ tab. (1)
On the events tab, paste the event name that @brenthaag mentioned keymaster_lock_state_changed (2), hit âstart listeningâ (3) and then trigger an event by opening a deadbolt or keying in a pin.
You should see the events showing up immediately below. (4)
1 Like
Thank-you so much.
That worked a treat. I assume thats in a Wiki somewhere, apologies if I missed it but really appreciate your following up.
Anytime. 
I had a few hours of power outage and most things recovered without a problem, including HA except Keymaster. Keymaster was working fine for years. Current version is v0.1.0.
All the Automations are gone, and am mostly getting errors âEntity not foundâ on the default Lovelace page.
I read up this thread and I do not know how to fix this.
If I go to Settingsâ>Integrationâ>keymasterâ>Integration entries, under the lock all the details and options are still there.
What is my path forward? I saw someone uninstall and reinstall. Is that the only safe bet?
All of the input_foo type entities that you list on that page are from Keymaster before v0.1.x. The current dashboard files are generated in custom_components/keymaster/lovelace/<lock>.yaml and need to be added to a new dashboard.
thank you. Hairless monkey that fell out of tree here.
So, what is the best approach for me? Get info out what is in there, uninstall, reinstall? or, click something, pull something, and bam, all good?
Well, if you update the dashboard with the newly generated one you should be good as long as there arenât any actual problems with Keymaster
I figured it out. thanks!