I moved my garage door opener over to Hubitat this weekend. It worked perfectly, right away. However checking the logs later, I started to wonder if there was a problem...
[dev:454](http://hubitat/logs/past#dev454)2020-03-01 12:14:41.840 pm [info](http://hubitat/device/edit/454) Garage Door is closed
This is a GoControl/Linear GD00Z-4 using the Generic Z-Wave Garage Door Opener driver. Looking at the events in the device page, it clearly shows open/close events. And it works perfectly.
You know that it really doesn't matter what is in the logs, right? The only person who can answer this is @mike.maxwell because the built-in drivers are not open-source. But logging is just for debugging purposes. As long as it's working and reporting open and closed states correctly in the edit device page under attributes, I really wouldn't worry about it.
Yes, and that was what caught me off guard. I looked in the logs and only saw closures, made the assumption that something was preventing opening from reaching the hub and started debugging it... before realizing both existed in the events
But thinking forward, as I am shifting to use Hubitat for some parts of the home security... it's nice to be able to pull up a log that shows a timeline of events. Like, kitchen door closed, garage door opened, gate opened.... says someone left kindof thing. Going to the events page of each of these devices is really not a useful UI. That's why I was looking at Logging, because it is possible to multi-select devices.
Am I overlooking a better way to get that kind of log? A list of events from a limited set of devices... ?
But the logs are only available for a limited time. It's not like you can go back days or something. And like I said, @mike.maxwell is the only one that can answer a question about the built-in drivers. We don't have access to the code.
My use case above is generally for review when I get an alert, so days of logs isn't necessary. Although it wouldn't hurt.
I was aiming the initial query for Mike or whomever would answer, and will refrain from tagging him again since he's been tagged several times already.
Not following at all, I see door and contact events for open and close.
The description text isn't the beef in an event, the value is.
And in this case including description text for the contact is redundant, the contact event itself is redundant as well, but is left for legacy reasons.
I was looking at the logs. The problem with events is that I have to click into each device to see them. When you're trying to correlate events at your home that's a serious non-starter. You want to see a clear picture in one place.
This example from Abode makes it really clear that even though the alarm went off, one of our devices came close, we had a garage door opener, ... this is unlikely to be a burgler. Because I can see this all in one place, I can grasp the sequence of events.
08:30 PM Kitchen deadbolt Unlocked
08:30 PM Automation : Take video when alarm goes off
08:30 PM Kitchen door Alarm Activated
08:30 PM Kitchen door Opened
08:27 PM Garage door opened
08:24 PM Automation : Wake ecobee when we get near
by *** entering 800 ft of Home
07:20 PM Automation : Turn on cameras when alarm is enabled
07:20 PM Gateway Armed - Away
07:20 PM Automation : Arm to Home mode when we leave
by *** exiting Close to home
07:17 PM Garage door closed
07:13 PM Kitchen deadbolt Locked
07:13 PM Kitchen door Closed
07:13 PM Garage door opened
07:13 PM Kitchen door Opened
07:13 PM Kitchen deadbolt Unlocked
Is there some way to see events across multiple devices which I am overlooking? Right now, it appears that this kind of view is only available from the logs.
