Logic for what gets logged in "Notifications" on FindVera?

Community Playground General Discussions
1

Hi,
it seemed like before all events regardless if they were defined in a scene or not were logged in the “Notification” section of FindVera. After I upgraded to Luup, only events that are defined in a scene seems to get logged. What is the logic behind what gets logged? Especially for my Schlage lock, it used to be very nice that everytime a PIN was entered, the user was identified in the “Notifications” log. Now it seems like I have to define an event for each user in a scene for it to be logged.

Also, why are there so many instances of the same device? E.g. for my EZ 3 in 1 I see three different instances of the motion sensor: #22, #22 Motion Detector, #22 Motion Sensor

Just wondering…

2

EH, pre-Luup there was an ‘event’ overload, and users complained that the event log was full of trivial data, like ‘light on’, etc. So now events are defined as ‘priority’ events, which get logged. If you’re into the technical details, it’s the addition of a ‘logCode’ tag in the service descriptor xml file.

However, everything related to door locks is supposed to be logged. Only non-important stuff like lights on/off is not. Can you do this, please? Advanced, Logs, check verbose logging. Then try your pin code in the door lock. Then refresh the vera web page (Ctrl+F5, or similar), click Advanced, Logs, and see if it’s there under Most recent events. If it’s not, go to Advanced, Tech Support and submit a trouble ticket with ‘for Aaron’ in the description describing what happened. I’ll see why it didn’t get in your log.

3

Thanks for the response! I would, but Vera is in my vacation home 400o miles away from where I am:-)

Speaking of logs, when I access my logs under Advanced (remotely), all i get is a Date/Time up in the left corner, and I cannot see any entries. I am on a Mac and have tried both Firefox 3 and Safari 4

4

EH, I’m so glad you said something about Advanced > Logs producing a blank page when done remotely. I thought this was just happening to me!

And once I began using Vera by logging in locally (on my home network), and the Logs work there, I kinda forgot about this issue.

But in firmware revision 616, it definitely remains an issue.

5

I have noticed something interesting. It seems that every door event is logged in “Luup Events”, BUT only door opened/closed is actually identified. A PIN opening is just recorded with a timestamp. Another thing is that opened and closed seems to be reversed. When someone unlocks the door it says “door lock closed” and when the door is locked, it says “door lock opened”. Either it is reversed, or it reports the state before the action taken (which does not immediately make sense to me that it should be designed that way.

6

The “lock action reversed” problem is mentioned prominently here, along with a cure:

http://wiki.micasaverde.com/index.php/Schlage_Lock#Reversing_the_Lock.2FUnlock_Status

Let us all know if this solves the problem, or if you think it’s a “bug”.

7

Thanks, LibraSun, but that is actually not the problem. The states shown on the dashboard are correct. When “Lock” is blue, the door is locked. It is the “Luup Events”/“Notifications”/Message that gets sent that seems to be reversed.

8

I am having this exact same effect as well, however also like EH, in the Dashboard it is correctly identifying the locks locked/unlocked state so it isn’t that the lock(s) was installed incorrectly. The fact that it is only showing a timestamp when a pin is entered (instead of what pin code it was) is annoying.