Yale Lock - Cannot create Trigger for PIN

Community Playground Getting Started & Initial Setup
1

Just received my Vera3 and have setup my Zwave mesh with 2 switches, 1 Yale lock and GE controller. Everything works so far 8)
I can create triggers to send email when the Yale lock is opened. However, it does not fire triggers for specific PINS (I am entering the PIN index i.e 1 or 2 for the first two PINS). Also, it looks like the trigger is created with a description “undefined” unlike all other triggers (such as low battery) which are appropriately named. Is this a bug?

2

There was an issue that affected some Veras regarding triggers. It has been fixed for the next firmware release, which will be this week.

3

@ mcvflorin, I’m having the same problem with a Schlage lock:

[url=http://forum.micasaverde.com/index.php/topic,8761.0.html]http://forum.micasaverde.com/index.php/topic,8761.0.html[/url]

However, it does not appear to be limited to triggers. Rather, it’s some kind of read/write issue. Besides the trigger problem that smadhu and I are having, I’ve seen the following:

  • when a USB stick is added for logging, PIN code notifications occur sporadically. It’s still identified as “undefined”, though.

  • I see no logging or alert information on either the user alert or device alert screens. I am getting some notifications sporadically (including pin code entries) and there is sporadic display of “last run” information on the triggers page.

  • I can enter a static IP address, but when Vera power cycles it goes back to DHCP.

  • When I check the box to receive update emails on the user info page, that box unchecks upon saving the change.

  • on the lock setting tab, I can’t enter a value for “Fire warning event when battery is below”.

Is this the problem that the firmware update is going to address?

Thanks,

fb

4

@fubarbloke

Please enable Tech Support and submit a trouble ticket, then tell me the ticket number so I can check.

5

@mcvflorin,

Thank you very much for the follow up. I sent you a PM with details.

Unfortunately, the trouble ticket doesn’t seem to be going through. I get an error message:

Submitting trouble report…
ERROR:Failed to submit your issue:
Done.

I get the error message whether or not the “send logs” box is checked.

Tech support access is enabled, though, and I sent you that info.

Thanks,

fb

6

Replied in an e-mail.

7

@mcvflorin Thanks! The pin entry glitch is gone, thank you very much for that. I’ll look forward to the next firmware rev. I think this is going to work out fine.

Cheers,

fb

8

After the new update, I am having this exact issue.
I can trigger events from open/close, but not PIN entry…

9

@electricessence

Please enable Tech Support and submit a trouble ticket so we can investigate.

Thanks.

10

@mcvflorin:
I messaged support via MiCasaVerde’s site today.
No response yet.

11

Tech Support has been enabled.

12

This was fixed in 1.5.420. I believe my colleagues from Tech Support contacted you. If not, can you tell me the ticket number you submitted?

13

Same problem and ticket 95098 submitted. Can we install the new release 420 to try it?

Thanks
MAtteo

14

Ticket #:95103

15

I am also having problems with my Yale lock. I have set the settings to notify me when a bad pin is entered and to log when someone enters a pin but I only get logs if I click lock or unlock from Vera. The battery is also still reporting 100% after about 2 weeks which I doubt is accurate. I submitted a ticket but haven’t gotten a response yet.

I’m currently running 1.5.408. We’re can I get 1.5.480?