Even I do have correct setup multiple user codes, in the event controller under “A PIN code is entered” comes up the
field “which user code” with right to it a drop down menue “please select” which does not show any options to select a certain code. What happend? That aplies for both looks. I have the same setup in a different home but all is fine.
That is a major option I need to have.
I have this same problem with my Kwikset and Vera 2. Have you found a solution?
UI4? UI5?
I seem to remember Milspec saying in a different thread that he was running UI4.
If you’re trying to trigger a scene triggered by the Event “A PIN code is entered” in UI4, you just click the Event tab, and then enter the PIN code index # in the field labeled “Which PIN code number?” as shown below…
See this thread for more info.
Delta, are you sure you have UI4 with no modifications? Because I have UI4 and on the Event tab in Scenes it does not ask for Pin Code like your screen shot shows, but ask for User Code. But the drop down lists no codes
Interesting. Yes, I’m sure. My firmware version is noted in my sig.
I have three user PIN codes, all programmed from Vera, and notifications always worked as expected after manually entering the index number (no drop-down). However, now I’m using a different notification scheme…
I’m running UI4 with the same firmware version Delta. Here is what I see in those places, it closely matches your’s Paul but still looks different.
I’m going to try removing the device and re-adding it in a couple days. I’m away and can’t do it now.
I just noticed under the Advanced Tab on the Kwikset deadbolt that it says Black and Decker is the manufacturer. Is that normal? I wonder if there are different versions of these locks floating around and that’s why Delta’s works properly and mine and Paul’s does not.
As shown in this screen shot, mine shows Kwikset. I believe “model” was once populated with the word “Deadbolt”, but it’s since disappeared.
Is your device file the same?
Here are all the settings in my advanced tab. Check against yours and tell me what looks different.
These are more settings on that screen.
Well, I can’t see “device_type”, that’s an important one… mine is [tt]urn:schemas-micasaverde-com:device:DoorLock:1[/tt]
Some of the other items are out of order, and I also have a field called “synced” under “room” which has a value of 0.
My “PinCodes” field actually contains the PIN Codes, where yours has asterisks. It’s difficult to compare since the order of the variables is very different. “VersionInfo” is the same, “ManufacturerInfo” is in fact the same.
Mine is the same. urn:schemas-micasaverde-com:device:DoorLock:1
So more info, nothing ground breaking though. I’ve tried deleting the kwikset lock from the Vera. When I did so it automatically readded the lock with default settings. I’m not sure if that’s good enough or I need to exclude it from the network and then reinclude it but it definitely was reset in most anyway I can think of.
No change on the pin code issue though. I’ve also tried healing the network, moving the Vera to a table 5 feet away from the lock and deleting the lock and readding it, as well as try a couple more browsers, this time I tried FireFox and Opera. No Joy either way.
The more I look at this problem, the more I see it as an issue with Vera and not the lock. Even if there were a slightly different revision on the lock Vera should be recognizing that and adapting.
It would be great if we could get someone else to chime in with some prophetic knowledge. We already have 3 people with this issue.
Bump
Still having this problem. It’s a bit of an issue.
You said you were going to exclude and then re-include. Have you given that a shot?
Yes, I’ve confirmed that unpairing and re-pairing the device had no effect. It’s still not showing anything in the logs nor am I able to use PIN codes to set notifications or trigger scenes.
This is a major pain in the ass. Half the reason I invested in this system was to do this, so I could monitor when my door was unlocked and set specific scenes when certain codes were used.
Please help.
I’m happy to report a moderate ammount of sucess. I took the time today to contact the MCV support team and was happy to see I received a response this afternoon. Unfortunately I was told the following
Hi XXXXXXX,
This issue was fixed in UI5. To upgrade to UI5 please visit:
https://cp.mios.com/firmware
Please let me know if you need further help.
Thanks,
At that point I decided, even though this was a stuipid idea, I would do a factory reset instead of installing UI5. I say stupid because I was at work at the time, far away from my vera, probably not the smartest idea. So when I got home, and had to use the key to get in, I spent some time setting up the Vera 2 from scratch.
When it was all said and done all my devices were already associated, however the lock was having problems. Vera kept saying “Failed at: Getting Secure Classes”. It wasn’t able to determine the manufacurer of door lock and I couldn’t set codes or anything. I went through several iterations of excluding the device from Vera, power cycling vera, readding the device, and then power cycling Vera again. Finally it decided to click and recognize the lock properly. It took several more minutes of configuring and it now allows me to enter codes and to use the notification and scene event trigger properly with codes. YAY!!!
However it’s still flashing the “Failed at: Getting Secure Classes” on an semi regular basis and the Log still doesn’t work.