[Deprecated] Event Watchdog - Keep an eye on what's important in the Event log

Introducing 'Event Watchdog'
Keep an eye on what's important in the Event log.

This has been added to Event Engine.

Features:

  • Search the event log in real time based on device, type and/or keywords you select
  • Keysets consists of a 'main keyword or phrase', 'up to 4 secondary keywords' and '2 doesn't contain keywords'
  • Display the a list on your dashboard!
  • When a keyset has a match, log item can also be pushed

Apps can be found on my GitHub or by using the Hubitat Package Manager.
(HPM is highly recommended)

When reporting problems...

  • Be sure you are on the latest version. I won't troubleshoot an older version.
  • Turn on debug and screenshot the issue happening in the log. One line or just the error doesn't cut it. I need a log.
  • Post the screenshot of the log with an explanation of the problem.

Thanks

3 Likes

saved

New version on GitHub...

Driver:
1.0.1 - 06/29/20 - Learned some new things

Hey

I have configured your app like that:
Select a Opton to 'Watch' * - Event_Type
Select the Type of Event to log - contact

And I left all the keywords blank. I have also tried to put as a Secondary Keyword 1 - "open" and as a Secondary Keyword 2 - "close".
And nothing happend.

What did I do wrong?
How to use it?

Sorry about that, Try the new version on GitHub...

Update both child and driver

Thanks

1 Like

Looks like there is still an issue, it's throwing nulls in the report.

I'll keep working on it.

1 Like

Okay, new version on GitHub...

Thanks

Ok now it works - I have got some things in bpt-eventData.
BUT.. there is no information which contact opened and closed. Look at it:
bpt-eventData :
||||
| --- | --- | --- |
|08-6 15:59|-|Contact was opened|
|08-6 15:59|-|Contact was closed|
|08-6 15:59|-|Contact was opened|
|08-6 15:59|-|Contact was closed|
|08-6 15:59|-|Contact was opened|
|08-6 15:59|-|Contact was closed|
|08-6 15:58|-|Contact was opened|
|08-6 15:58|-|Contact was closed|
|08-6 15:58|-|Contact was opened|
|08-6 15:58|-|Contact was closed|

But I don't know which contact.. Am I doing something wrong?

Should look like this...

Please turn on debug logging and show your results here (screenshot).

Thanks

Do you mean this?

Perfect. Now show my a screenshot of how you have the app setup. Specifically the Keyword setup.

See below

great, now one more thing. Show me a device that is showing up as just Contact.

Okay, just updated the app/driver on GitHub. Please update and capture another log.

Then change the Device Label to English (garage door?) and capture yet another log.

Let's see what happens. :thinking: :man_shrugging:

I updated the app.
Log before contact name changing:

Log after contact name changing to "Garage door":

And still nothing:
bpt-eventData :
||||
| --- | --- | --- |
|08-6 18:50|-|Contact was closed|
|08-6 18:50|-|Contact was opened|
|08-6 18:48|-|Contact was closed|
|08-6 18:48|-|Contact was opened|
|08-6 18:26|-|Contact was opened|
|08-6 18:25|-|Contact was closed|
|08-6 18:25|-|Contact was opened|
|08-6 18:25|-|Contact was closed|
|08-6 18:25|-|Contact was closed|
|08-6 18:24|

Great info, thanks. Was thinking maybe the non-English was throwing something off but the logs are exactly the same.

I changed up some code though and updated GitHub again.

Install the latest from GitHub, open the child app and hit 'Done'. Hopefully we see some magic. :wink:

It's magic indeed!
Now it works perfect:
bpt-eventData :
||||
| --- | --- | --- |
|08-6 19:37|-|Drzwi główne - Contact was closed|
|08-6 19:37|-|Drzwi główne - Contact was opened|
|08-6 19:37|-|Drzwi do garażu - Contact was closed|
|08-6 19:36|-|Drzwi do garażu - Contact was opened|
|08-6 19:36|-|Garage door - Contact was closed|
|08-6 19:36|-|Garage door - Contact was opened|

Thank you very much for your help! You're the best!
I owe you big beer! Just let me know when you are in Poland! :smiley:

1 Like

Awesome, glad is working

1 Like

One more thing.
Could you please add 3 tables instead of 1?
I mean bpt-eventData1, bpt-eventData2, bpt-eventData3 because now bpt-eventData can only handle more or less 10 events. It is not too much :slight_smile: