Indigo Domotics

I've finally switched out my locks for the Kwikset 916, and almost everything is fine, but ZWave Lock Manager is having problems sending commands to my locks.

I have a Lock Manager device set up and associated with each lock. If I set up an action that just does a simple "Get User PIN" for one lock, I get:

Code: Select all

May 29, 2017, 3:57:18 PM
   Action Group                 Get Code
   Z-Wave Lock Manager          Requesting PIN for user 1
   Z-Wave Lock Manager Error    Error in plugin execution ExecuteAction:

Trace back (most recent call last):
  File "plugin.py", line 146, in getUserPin
InvalidParameter: could not find module/node for action


If I look at Line 146 and do what it's doing manually in a script action:

Code: Select all

indigo.zwave.sendRaw(device=indigo.devices[1555487768], cmdBytes=[0x63, 0x2, 0x1], sendMode=1)


I get no error and see the following in the log:

Code: Select all

Z-Wave                 sent "Mud Room Lock" raw command [63 02 01]
Z-Wave Lock Manager    Status:  User code 1 is 1 2 3 4 5 6 (Node: 4)


(...where 1 2 3 4 5 6 stands in for the one code I set manually on the lock when setting it up)

Any idea what might be happening here?

One further update:

The Device ID in the script above is for the actual Z-Wave lock, which is what I would have expected. After turning on debugging in Lock Manager, it appears that the Get User PIN action is trying to use the ID of the Lock Manager device itself instead of the Z-Wave lock it's associated with. I assume that's failing because it isn't a valid target for raw Z-Wave commands.

Ah, that's probably a bug I've introduced when merging the beta code into the main stream over the weekend. It's precisely that set of code that I switched but I thought I'd done a find in the code for all references to it.

I'll sort it tonight!

Peter


Sent from my iPhone using Tapatalk Pro

Right, I've just uploaded 1.0.36 to the same link in the announcement thread.

Can you check it out?

Peter

Just updated and I don't get a dropdown list from the 4 set commands in Lock Manager Actions but Device Actions > Lock Controls I do .
I did do a resync and reset Indigo.

CliveS

You need to create dummy lock devices - see the latest announcement post for .35

Peter


Sent from my iPhone using Tapatalk Pro

howartp wrote:

Right, I've just uploaded 1.0.36 to the same link in the announcement thread.

Can you check it out?

Peter

Fixed for Get User PIN, thanks, but it looks as if the same problem also (still) exists for Set User PIN.

Code: Select all

May 30, 2017, 5:34:36 PM
   Action Group                    Test Manager
   Z-Wave Lock Manager Debug       setUserPin action called
   Z-Wave Lock Manager Debug       Indigo lock selected: 14551786
   Z-Wave Lock Manager Error       Error in plugin execution ExecuteAction:

Traceback (most recent call last):
  File "plugin.py", line 109, in setUserPin
  File "plugin.py", line 543, in setPin
KeyError: (14551786,)


(14551786 is the Manager device)

Grrr. I thought I'd been careful to copy the fix through get, set and clear!

I'll try do it as soon as I can get on a pc.


Sent from my iPhone using Tapatalk Pro

1.0.37 now live.


Sent from my iPhone using Tapatalk Pro

Peter,

I have now read the .35 release notes, my fault for jumping from .34 to .36!! and see for a new trigger I get the option of the Lock Device( Node 55) or the dummy lock, can I use either?

A couple more bugs to eradicate


31 May 2017, 09:21:19
Z-Wave Lock Manager Debug logging enabled
Schedule Front Door Lock Time Set
Z-Wave Lock Manager Debug setRCT action called
Z-Wave Lock Manager Debug Indigo lock selected: 1802317647
Z-Wave Lock Manager Debug 11111100001
Z-Wave Lock Manager Debug 111
Z-Wave Lock Manager Debug 7
Z-Wave Lock Manager Debug 11100001
Z-Wave Lock Manager Debug 225
Z-Wave Lock Manager Debug 2017
Z-Wave Lock Manager Setting lock time to 31/5/2017 9:21:26 (UK format DD/MM/YYYY HH:MM:SS)
Z-Wave Lock Manager Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 189, in setRTC
InvalidParameter: could not find module/node for action


31 May 2017, 09:21:52
Action Group Front Door Lock Wrong Code Set Limit & Timeout
Z-Wave Lock Manager Debug setWrongLimit action called
Z-Wave Lock Manager Debug Indigo lock selected: 1802317647
Z-Wave Lock Manager Setting incorrect code limit to 3 attempts with 60 second timeout:
Z-Wave Lock Manager Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 224, in setWrongLimit
InvalidParameter: could not find module/node for action

CliveS

PS You really should get a lock just to appreciate the great plugin you have done "blindfolded"... Thank you!

Hi Clive.

Believe me, if I had any doors that were suitable for locks, I'd have one by now - a fellow plugin user offered to buy me one just to say thank you - but we have uPVC doors with multipoint locks on (UK) for which there's only one Zwave lock on the market and they cost a fortune vs most keypads/locks that you guys are using!

I hadn't realised how poorly I'd written these routines in the beta (I think I must have broken off half way through changing direction) which is why they're now popping up in the live releases.

I'll get it sorted.


Sent from my iPhone using Tapatalk Pro

I must admit to gatecrashing the thread as I have one of those expensive locks (Yale) fitted here in Consett but the bugs are agnostic when they bite.

howartp wrote:

1.0.37 now live.


Sent from my iPhone using Tapatalk Pro

That's got it. Thanks! Get/Set/Clear all behaving fine.

Not to hijack my own thread, but I had some thoughts I'd actually started to work on in the interim anyway (since, for want of a non-Indigo Z-Wave controller, I've been having to configure my locks via scripts anyway), but since you have a working plug-in already, it might appeal to you: I'd gone down the route of making a "lock user" device. For configuration each user would have a code and a multi-select list of locks the code would have access to. There are situations where the "indigo.zwave,indigo.relay" filter wouldn't be sufficiently narrow, so maybe let the user select a full list of actual locks as a matter of plug-in config. The plug-in could then watch for changes to users (e.g., a schedule that only enables the "Housekeeper" user at certain times) and, as a first pass, just crudely rewriting the the whole user set of each lock, but then maybe later figuring out a way to push smarter, more minimal deltas.

Then when a code is used, you can fire a trigger off the actual user device, so you get consistency for auditing purposes (the slot a given code occupies on a given lock may change, or vary from lock to lock).

Another nice security feature would be a utility to forcibly clear every slot that is not known to be claimed by an active user

Give a mouse a cookie, eh?

I may still work on this some myself, but like I said, I thought you might take interest.

Great!

I've already got the concept of lock users in beta, but I'm not keen on how I've done it at the moment so I'll give your ideas some thought as well.


Sent from my iPhone using Tapatalk Pro