[Bug 625]: confirm specific user code notification works. Now you get the name of the user code entered on a Schlage lock in the notification
If you are talking about notification without creating a specific scene to notify (in Luup Events that is) then this isn’t fixed. It still only shows a date stamp and that is it, no user code name.
If this is reported somewhere else then please let me know, I am sick of having to create a scene to notify me for every single user code in every single lock (I have about 75-85 at any given time).
While we are at it, why does it report “Door lock opened” when the deadbolt it locked and “Door lock closed” when the deadbolt is unlocked? Shouldn’t this be the opposite?
Really looking forward to these two items being fixed… I have only upgraded the firmware in my test unit to 979, my others are still running 944 which seems pretty stable.
[i]Reversing the Lock/Unlock Status
If the lock/unlock status of your door lock is backwards, meaning Vera’s ‘Dashboard’ shows it is locked when it’s really unlocked and vice-versa, it’s possible the lock was oriented upside-down when mounted. To solve this issue, go to Vera’s ‘Setup’ page, click the ‘Devices’ tab and click the ‘+’ button next to the door lock, and then the ‘Advanced’ button. If you see a parameter “#305 Reverse”, enter a value of 1. Save this change. Vera will now reverse the lock/unlock status.
If parameter #305 is not in the list, then at the bottom of the page, type 305 in the “New Device Data ID” field, and type 1 in the “New Device Data Value” field. Click ‘Add’. Then save your changes. Vera will now reverse the lock/unlock status. [/i]
I am having this problem and I did not put the lock in upside down. The internal bolt had a ‘TOP’ on it. I tried doing these instructions but they seem to be for an older firmware as there is no New Device Data ID field. I am not sure what to do. Can someone correct that wiki entry?
It’s at the bottom after you click on the advanced tab, it is a line that says New Value and has a button that says add.
Unless someone installed the lock upside down on purpose for some reason (the outside would have to be upside down as well so the schlage button would be upside down) then I don’t think this really applies. My comment was that something is messed up in the terminology of how Vera reports the action of unlocking and re-locking the door, on the dashboard it correctly reports the lock/unlock status of the door, but in the logs it reports unlocking as door lock closed and locking as door lock opened. I think somewhere along the lines someone was thinking of the status of the latchbolt itself (unlocked, latchbolt is in the closed or retracted state and locked it is in the opened or extended state). This terminology is confusing however.
[i]Reversing the Lock/Unlock Status
If the lock/unlock status of your door lock is backwards, meaning Vera’s ‘Dashboard’ shows it is locked when it’s really unlocked and vice-versa, it’s possible the lock was oriented upside-down when mounted. To solve this issue, go to Vera’s ‘Setup’ page, click the ‘Devices’ tab and click the ‘+’ button next to the door lock, and then the ‘Advanced’ button. If you see a parameter “#305 Reverse”, enter a value of 1. Save this change. Vera will now reverse the lock/unlock status.
If parameter #305 is not in the list, then at the bottom of the page, type 305 in the “New Device Data ID” field, and type 1 in the “New Device Data Value” field. Click ‘Add’. Then save your changes. Vera will now reverse the lock/unlock status. [/i]
I am having this problem and I did not put the lock in upside down. The internal bolt had a ‘TOP’ on it. I tried doing these instructions but they seem to be for an older firmware as there is no New Device Data ID field. I am not sure what to do. Can someone correct that wiki entry?[/quote]
If parameter #305 is not in the list, then at the bottom of the page, type 305 in the “New Device Data ID” field, and type 1 in the “New Device Data Value” field. Click ‘Add’.
There is no New Device Data ID field or New Device Data Field.
I did get 305 with a value of 1 in there, but it does not change the display on the dashboard to be correct. I am not sure how it effects the log yet.
If you are talking about notification without creating a specific scene to notify (in Luup Events that is) then this isn't fixed. It still only shows a date stamp and that is it, no user code name.
Just create a scene, add an event "a user code is entered’, and choose the “any user”.
under Luup Events it is still reporting a time stamp and nothing
under Luup Notifications it reports Pin Code and if you click on that it will tell you the user (pin code name).
under Notifications it reports Pin Code and if you click on it it also tells you the user (pin code).
Would it be possible under Luup Events for it to list the user instead of the blank? That way it would take a lot less clicks to see who was accessing the lock.
Thanks for getting this working the way it does now however, I can create a ton less scenes from now on.
[quote=“micasaverde, post:5, topic:165135”]
If you are talking about notification without creating a specific scene to notify (in Luup Events that is) then this isn’t fixed. It still only shows a date stamp and that is it, no user code name.
Just create a scene, add an event "a user code is entered’, and choose the “any user”.
One question though, why would anyone want to install the deadbolt upside down in the first place? Not really sure why this option is even out there to reverse the status.
I know but it does not match the terminology used in the docs.
If parameter #305 is not in the list, then at the bottom of the page, type 305 in the “New Device Data ID” field, and type 1 in the “New Device Data Value” field. Click ‘Add’.
There is no New Device Data ID field or New Device Data Field.
I did get 305 with a value of 1 in there, but it does not change the display on the dashboard to be correct. I am not sure how it effects the log yet.[/quote]
It must depend on what side of the door you mount it on. I have mine with the front keypad side on the left side of the door. People who do not have this problem probably have the lock mounted on the right side of a door. Vera should probably have a way to adjust this on the main lock setup screen rather than make you enter some code 305 that is hard to figure out. I got code 305 entered and it did not change anything.
The ability to control this lock is a big win for Vera but it needs to have a setting for this right up on the main config screen.
I have 8 of them in total on both right hand and left hand doors and they all report the lock/unlock status on the dashboard correctly with no messing around with the settings. I can think of no reason you would even want to change the status.
If you take a look at the back of the lock with the cover off (if you installed the lock correctly) that little teardrop knob that the spindle sticks out of (the flat piece of metal that the thumbturn rotates) is pointing up when the bolt is retracted (unlocked) or the direction of the latchbolt when the bolt is extended (locked). If you installed it on a RH (Right Hand, hinge right swing in) or a RHR (Right Hand Reversed, hinge right swing out) door then the teardrop will point right (as you are looking at the inside of the lock) when the door is locked or if it is installed on a LH (Left Hand, hinge left swing in) or a LHR (Left Hand Reversed, hinge left swing out) door then the teardrop will point left (as you are looking at the inside of the lock) when the door is locked.
With that said you will notice that when the teardrop is pointing up it is pushing up a switch. This is what tells the electronics of the lock that the door is unlocked. When this switch is pushed up (presumably the door is unlocked) you can push the Schlage button (without entering a valid code) and lock the door from the outside. If you install the lock incorrectly (where the teardrop is not pointing up with the latchbolt retracted) then what you will end up with is a door that can be unlocked without entering a code and simply pushing the Schlage button and turning the knob to unlock the door.
In this last case with the lock installed incorrectly (doesn’t matter what the orientation is of the latch (on a RH, LH, RHR or LHR door) or if the lock is upside down or not, changing that setting still doesn’t do anything for you that would be helpful. (Unless your intention for some unknown reason is to allow anyone that pushed the schlage button to unlock your lock without entering a code and you then want this action reported correctly in the dashboard??)
I may misunderstand the intention of the reversing of the status here and be way off base, but I can’t really understand why anyone would need to change those settings.
[quote=“rsilvers, post:8, topic:165135”]The upside down thing does not make sense.
It must depend on what side of the door you mount it on. I have mine with the front keypad side on the left side of the door. People who do not have this problem probably have the lock mounted on the right side of a door. Vera should probably have a way to adjust this on the main lock setup screen rather than make you enter some code 305 that is hard to figure out. I got code 305 entered and it did not change anything.
The ability to control this lock is a big win for Vera but it needs to have a setting for this right up on the main config screen.[/quote]
If you can walk up and push the Schlage button and it turns green (not light up the keypad blue) and you can retract the bolt (all without entering a code) then you need to remove the inside portion of the lock, retract the bolt, make sure the little teardrop is pointing up and then install the inside portion of the lock again.
Yeah. I will try that. I know that it requires the code for me to re-lock the deadbolt, so that is evidence I had it in wrong. I knew that was not how my other Schlage locks behaved, but I assumed they did it on purpose to force people to enter a code to lock it for the purpose of an audit trail.
So it is the cam that could be upside down, not the lock.
I was just reading through some old posts I made and remembered that the links do have the ability to turn this feature off (pushing the schlage button to allow locking the lock from the exterior without entering a code). I don’t have the command right in front of me, but it is in the Link documentation. It defaults to allow locking without a code however.
[quote=“rsilvers, post:12, topic:165135”]Yeah. I will try that. I know that it requires the code for me to re-lock the deadbolt, so that is evidence I had it in wrong. I knew that was not how my other Schlage locks behaved, but I assumed they did it on purpose to force people to enter a code to lock it for the purpose of an audit trail.
So it is the cam that could be upside down, not the lock.[/quote]
Would it be possible under the Luup Events log for Vera to report what pin code was entered instead of just a timestamp? Without this, you must create a scene as you stated and choose any user, but unless you have this emailed to someone it will not be logged under Luup Notifications or the Notifications log, so then there is no record (I created this scene and did not check the notify users box so it didn’t do anything. I don’t want an email generated every single time a pin code is entered, just for it to be recorded into a log in case I need to go back at some time and check to see who entered and what time/date.
[quote=“micasaverde, post:5, topic:165135”]
If you are talking about notification without creating a specific scene to notify (in Luup Events that is) then this isn’t fixed. It still only shows a date stamp and that is it, no user code name.
Just create a scene, add an event "a user code is entered’, and choose the “any user”.
Ok… A little more tinkering and I figured out if you uncheck the box “sending an email to” under users then check the box by that user in the scene next to notify users you won’t get an email but it will be reported under the notifications log. I would still like for the code to be reported under the Luup Events. One thing I also noticed is that the time stamp in Luup notifications is PST even though I am in EST (and have the time/date set correctly in Location (everything else has the correct time/date).
[quote=“scotthay, post:15, topic:165135”]Would it be possible under the Luup Events log for Vera to report what pin code was entered instead of just a timestamp? Without this, you must create a scene as you stated and choose any user, but unless you have this emailed to someone it will not be logged under Luup Notifications or the Notifications log, so then there is no record (I created this scene and did not check the notify users box so it didn’t do anything. I don’t want an email generated every single time a pin code is entered, just for it to be recorded into a log in case I need to go back at some time and check to see who entered and what time/date.
[quote=“micasaverde, post:5, topic:165135”]
If you are talking about notification without creating a specific scene to notify (in Luup Events that is) then this isn’t fixed. It still only shows a date stamp and that is it, no user code name.
Just create a scene, add an event "a user code is entered’, and choose the “any user”.
On your GE Module, make sure firmware is v2.0a or v3.0a, these support the lock beaming
Once you install the module, try and HEAL NETWORK overnight and see if this helps