Control Lock Code Manager codes and users via RM?

[a.mcdear]

Basically, trying to see if there is a way of manipulating LCM from RM. I want to be able to enable/disable a user/code from Rule Machine. Doesn't seem like this is currently available.

It would be REALLY COOL if LCM could create child switches to enable/disable codes and/or users easily with RM.

So, tying to figure out some sort of workaround, I've looked and it seems like this may be possible to perform this on the lock itself with a custom action, but I am unsure how to proceed from this point. I'm assuming I need to add the appropriate parameters for the code name and the actual digits? I should note that I am using the "Generic Z-wave Lock" driver.

[mike.maxwell]

@a.mcdear

Basically, trying to see if there is a way of manipulating LCM from RM. I want to be able to enable/disable a user/code from Rule Machine

you would just remove or add the code directly to the lock(locks), LCM just reads codes in when it starts.

[a.mcdear]

@mike.maxwell

add the code directly to the lock(locks), LCM just reads codes in when it starts.

Yeah this seems to be the way. This is what I'm trying to do now, but I can't figure out the proper formatting to get the lock to take it properly. I was using custom action "setCode". Then 1st Parameter type string "TestCodeName" and then second parameter as type number "012345" as the test code, but this doesn't seem to be quite right.

[aaiyar]

@a.mcdear

I was using custom action "setCode". Then 1st Parameter type string "TestCodeName" and then second parameter as type number "012345" as the test code, but this doesn't seem to be quite right.

That would be incorrect. There are three variables, which by position are:

1. code position (needs to be a number)
2. pincode (needs to be a string)
3. name (needs to be a string)

So something like:

setCode(10,1234,TestUser)

would set code position 10 to be "1234" and the name to be "TestUser".

[a.mcdear]

@aaiyar

setCode(10,1234,TestUser)

would set code position 10 to be "1234" and the name to be "TestUser".

Perfect. Thank you so much!!

[a.mcdear]

OK, so this is KINDA working - but something isn't quite right still..

When I create a test rule to create my test code and user, it works... but prompts the lock to start a code audit which seems to tie it up and make the lock slow to respond. Seems once this process starts, lock seems to become partially unresponsive until the code audit is over.

At the same time, while this was happening, the reported battery level on my lock has gone down by almost 10%.

and then, when the codes is removed, there is an error, and the code does not get removed from the lock:

[mike.maxwell]

deleteCode only takes one numeric parameter, which is the code slot number.