Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add flowcard option to catch log events for a specific zone when heimdall is set to log #18

Closed
pohomey opened this issue Apr 15, 2018 · 7 comments

Comments

@pohomey
Copy link

commented Apr 15, 2018

Sometimes you also want to catch log events (not thus not only when armed) to e g trace movement.
Add flowchart option to catch (log) events for a specific zone (or all). When triggered - consider to provide tags for time (and if all zones is supported - also tag for zone).

@daneedk

This comment has been minimized.

Copy link
Owner

commented Apr 17, 2018

@pohomey
I don't understand what you are asking, can you explain?
What problem are you trying to solve?

@pohomey pohomey changed the title Add flowchart option to catch log events for a specific zone Add flowcard option to catch log events for a specific zone Apr 17, 2018

@pohomey

This comment has been minimized.

Copy link
Author

commented Apr 17, 2018

Sorry - the title was mangled by apple predictive word replacements/"corrections" (fixed it). See below for more info (please don't hesitate to ask questions). I think helimdall is by far the best tool for security I've seen outside a real alert system. I was hoping to get it to expand in scope somewhat.

I'd like a flowcard that catches movement events when heimdall is set only to log the event (I have not seen that kind of card - or have I missed something?). I understand that I can use flowcards to catch alarm events when the system is armed and movement create an alert event, but in this case I'd like the option to catch events that normally only would be logged (as configured). The purpose for this is to trace movements happening before an actual alert, where the movements/event itself is not reason to trigger an alarm. E g when an alert event is detected on motion sensor 5 (MS5), did the person causing that alert come by the MS1, MS2 or trough MS3 or possibly trough MS4 before running into the MS5 (causing an alert event).
Another way to achieve this might be to add option to retrieve the e g last three logged movements before an alert event is triggered and make it available when an actual alert occurs.

Another subject: Is there a tag/card (or internal functionality) to see when the latest logged event occurred? If so - perhaps add option to automatically arm after e g X hours/minutes of no (logged) movements? Or (even better) to get a flowcard event when no logged movements/events has occurred in X hours?

@pohomey pohomey changed the title Add flowcard option to catch log events for a specific zone Add flowcard option to catch log events for a specific zone when heimdall is set to log Apr 17, 2018

@daneedk

This comment has been minimized.

Copy link
Owner

commented Apr 23, 2018

So, a flow card that gets triggered when a log line is written for a sensor, with tags for the device and the state. That should be possible.

For your second question, the log lines (in Heimdall) have a time stamp so I guess that's covered. To let something happen when no logged movements/events have occurred you can use the 'A device hasn't reported in ' trigger card and filter on the name tag
image

@daneedk

This comment has been minimized.

Copy link
Owner

commented Apr 23, 2018

This is the new flow card which gets triggered when a device set for logging changes state:

image

Not yet submitted to the app store, please let me know if this fits your request.

@pohomey

This comment has been minimized.

Copy link
Author

commented Apr 23, 2018

Yes, "A logline was written" should do the trick - nice.

@daneedk

This comment has been minimized.

Copy link
Owner

commented Apr 24, 2018

App is submitted to the app store.

@daneedk

This comment has been minimized.

Copy link
Owner

commented May 2, 2018

Version 1.0.13 is published

@daneedk daneedk closed this May 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.