Keymaster Gd

[Cheryll Witting]

Whenfirst installed, we assigned a member to the role of Keymaster. However, that person has left the company and we would like to switch the keymaster role to another member. Unfortunately, we are having issues with buddpress on the back end cannot assign the second person the role then delete the first Keymaster user.

Normally to remove a person as Keymaster (with bbPress), you would go to wp-admin (backend) and click on the Users link on the left panel. Check the box beside the name of the user you would like to demote and then at the top of the table, on the second select box, change from Keymaster to Subscriber or whatever role you want. Same goes for the person you would like to promote, check the name of user in the table, then change to Keymaster in the second select box. By the way, you can have more than one Keymaster on bbPress forums.

So I am having an issue after the recent updates. I am running 2021.3.1 and 0.0.26, with the old ZWave integration on a Kwikset lock. If I set any of the advanced options for pin state the PIN Status switches to Disconnecting and PIN synchronised with lock is always Off.

This was working a few days ago, before the updates. I have tried uninstalling, removing the repo, deleting any remaining files or entities and reinstalling, but I get the same behaviour. Any ideas what I am doing wrong?

This is literally the only thing in my log file:

2021-03-08 15:16:58 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration keymaster: No module named 'openzwavemqtt'

This was my first integration from HACS. There is no reference to this requirement in HACS or KeyMaster installation notes. HACS installation notes and FAQ talks about elements, repositories and integrations but never mentions packages. Anyway, problem solved. On to the next one.

I setup my Schlage Z-Wave Plus lock using the original simplified Z-Wave lock manager and while some of the functions no longer work I can still assign codes and activate/deactivate users. It was a pretty mammoth task for me at the time to get it working but with perseverance I did.

I have been reading this thread with interest and would like to try this new manager but it kinda terrifies me lol. First of all what is the best way of removing all of the old lock manager components so I could start clean. I know how to remove the lock from the Z-Wave integration and then perform a factory reset.

Long story short, translating any of this data into the scheduling variables inside keymaster seems like a waste of time when we can already easily set the codes with standard home assistant API calls with the existing variables. Calling the input_* services for the keymaster entities is trivial now as is and works fine.

Whie this is working great for my simple needs of ocasionally setting up a guest pin, I am thinking about removing it due to the amount of clutter it left in my automations and scriptds UI. Before I do is there a way to hide them?

The most useful interim functionality would be the option to remove the scheduling functions that are in place, but I have no idea how difficult a task that would be. Frankly, your software most likely functions damn near perfect as is for almost everyone that uses it.

Personally, if I could select an option to not include the weekday advanced scheduling from generating I would. I would keep the date range scheduling, but I could see some folks not wanting even that.

Secondly, I would probably do some work to combine all the various automations. For instance there is a synchronize_code_slot__ and a turn_on_access_limit__code_slot_number> for every code slot defined. The thing is, that in both of these cases it looks like something that is conceivable to bring down to a single automation that uses the triggering entity name to drive changes. This is already being done with many of the basic lock automations (changes codes, sending notifications, etc)

I can give an example of where it causes problems.

When creating a new lovelace dashboard the default is to add every entity. Each and every keymaster variable shows up and makes it almost impossible to load.

It also makes the history tab on the ios phone app completely unloadable.

My rough guess is the tipping point for this is probably only five keymaster locks with with five codes each.

On another note, you likely already know this, but there are System log entries pointing to defaults missing on time templates related to Keymaster. Is that on your radar? They will likely stop working with the next release.

I hope someone can help me with this

I set up everything as per installation instructions

when I paste the lovelace code, I get the cards but i get " entity not available: sensor.connected :" and " entity not available: binary_sensor.active" errors.

What am I doing wrong?

Also ran into the issue although I was upgrading from the old non HACS integration to keymaster. How do you go about the process you mentioned? Did you just remove the integration from HACS? How do you then go about installing the older version?

After this I think I restarted HA again at this point then went through the process of reinstalling my parent and child keymaster locks which was successful. After that I was able to go back into HACS and upgrade Keymaster to the latest version which is now 0.0.74 and I have had no problems on this version.

nope didnt help

patrepon852463 26 KB

it keeps unlinking and removing my license benefits i need help why is no one helping with a issue this big bro i have to relink every 4 hours and my server becomes unaccesibble as it says dont have the right license to support 64 people and it goes to 48

indeed i have i regenarated a new key it works for a few hours then the slots come back to 48 and i have to go to keymaster where my benefits are no longer there and reconnect my patreon and wait till it fixes and restart my server which has concluded into me loosing half my members in 2 days

Autolock after X time (just do it)

Toggle: Only lock after close, with added requirement for door sensor

Toggle: Auto unlock if locked while open, with the same door sensor being required and timeout before unlocking (default 1 min)

I figured out my issue, there were a couple. Main one was that I had to re-interview the lock. It was showing options for 5 user codes under the user codes section of zwave control panel, but after re-interviewing, it started properly showing 30. The other issue was that keymaster had the status deleting for the first 5 pin codes. To fix this, I had to manually set those 5 user code slots to available in the zwave control panel. After those 2 things everything is working as expected!

Italy native Il Flaco Scivola debuts for the first time with TBX Records bringing his signature funky sounds. Soulful rhythms, funk infused basslines and deep swirling chords are all packed into these four massive groovers.Follow: ://soundcloud.com/tbx-recordsBuy on Beatport: -keymaster-ep/3057059

3a8082e126