KeyMaster Z-Wave lock manager and scheduler

Looks like some kind of issue with the telegram notification service.

webpack.config.js has nothing to do with KeyMaster.

Quick Question to inquire if Zigbee is on anyoneā€™s roadmap?

It is but itā€™s slow going.

For several weeks (and maybe more), Iā€™ve been seeing the following error in my logs:

This error originated from a custom integration.

Logger: custom_components.keymaster.binary_sensor
Source: custom_components/keymaster/binary_sensor.py:49
Integration: keymaster (documentation, issues)
First occurred: 8:47:22 AM (14 occurrences)
Last logged: 9:19:03 AM

Z-Wave integration not found

Z-Wave integration not found.

Iā€™m on v0.0.82 of the Keymaster integration. In at least some preliminary testing, it appears that the integration is working well for one of my locks, but not for the other. New codes donā€™t get added, old codes donā€™t get deleted. Iā€™ll try removing and re-adding the integration for that lock to see if that fixes it.

Iā€™m just going through the logs to fix things, and figured Iā€™d share in case this has come up elsewhere. Iā€™ve made no changes to the integration or to my network that I think would cause this.

EDIT: Removing and re-adding the instance of the integration for that lock only seems to have worked. Iā€™ll watch the logs.

Not sure what I am doing wrong. I setup and I am getting notifications but they donā€™t contain information. Just says "keypad unlock operation ()

mode: paqrallel
sequence:
  - service: notify.mobile_app_sm_n981u
    data:
      title: "{{ title }}"
      message: "{{ message }}"
alias: ""
max: 10

Can anyone tell me where I messed up?``

Thatā€™s not a valid mode.

@firstof9 that must have been a typo when i posting somehow??? cause it doesnā€™t actually say that in the script
image

So a message saying keypad unlock operation () would indicate that thereā€™s no name associated with the slot that unlocked the door.

It should say something similar to keypad unlock operation (Michael) if you put the name ā€œMichaelā€ in the slot name that opened the lock.

names are there
image

Try Dev-tools ā†’ Events
and enter keymaster_lock_state_changed into the ā€œEvent to subscribe toā€ and press Start Listening

Then go operate your lock with your code and see what info is reporting.

1 Like

very strangeā€¦ its now working (showing names) and i didnā€™t do anythingā€¦ oh wellā€¦ just glad its working

1 Like

I just started using the Watchman integration (pretty good so far), and itā€™s identified a bunch of unused/missing entities, the vast majority of which are associated with Keymaster. Now, I have Keymaster-related files in two locations:

<HA-IP>\config\custom_components\keymaster
<HA-IP>\config\packages\keymaster

Iā€™m wondering, are they both necessary? What I want to do is clean up any redundant or deprecated files & references, and then probably hide some of the valid ones from Watchman so they donā€™t appear in future reports. I believe the references to ā€œmissingā€ entitles like input_boolean.override_parent_LOCKNAME_TEMPLATENUM are necessary for Keymaster to continue working.

You should have the following (at a minimum) in your ignored files configuration option for watchman

/config/custom_components/*, /config/packages/*

1 Like

I suppose that makes sense. That really cleared up the Watchman reportā€¦ down to two references I can explain, and two I can eliminate. Thanks.

No worries, I donā€™t actually us watchman myself, but since someone complained about all the entities that the report generates for Keymaster and my integration (that relies on Keymaster) I had to figure it out :smiley:

I never found a need for watchman, and with the changes to HA to raise issues on missing entities or bad automations, I find it even less relevant

Yeah, I now that Iā€™ve cut out a lot of the chaff, I can see that some of the (Keymaster) entities that Watchman returned are entirely by design and need to be ignoredā€¦ particularly ones in the folders you pointed out.

I can see running a Watchman report maybe once a month going forward. Anything I do with HA beyond Lovelace happens in fits & starts, so Iā€™ll go weeks or a month without fooling with it, then come back to upgrade and find (or, uh, create) breaking changes and orphaned entities.

EDIT: This is a bit satisfying to see, thoughā€¦

-== Watchman Report ==- 

-== Congratulations, all 11 services from your config are available!

-== Congratulations, all 135 entities from your config are available!

-== Report created on 09 Jan 2023 12:02:04
-== Parsed 20 files in 0.61s., ignored 30 files 
-== Generated in: 0.00s. Validated in: 0.00s.

One thought would be to assign a code slot to the arm function, when that code is entered you could arm the system and lock all of your door locks.

Personally, this sounds like a great idea. Of course, then @StevieRay05 needs to train the cleaners (and others) to enter a different code when they leave :wink:

Hadnā€™t thought of that, I guess that could work. But yes, then everyone would need to remember 2 codes. One to unlock/disarm and one to lock/re-arm.

At that point, Iā€™d probably just put a button by the front door that delays for 30 seconds and then locks the door and arms the alarm.