Correct way to use metadata through Rules
AnsweredHello
What is the best way to use correctly metadata through rules ?
Situation :
I would like to notify (mobile and email) when camera triggers something, only if intruder system is armed or not (via HTTP API event)
To keep metadata of camera triggered, have I to make notification directly inside rule or can I use generic event to send notification (with data) ?
see attached png to show
-
Norman : no answer ?
0 -
Hi Julien ROMANO,
Please see THIS support article or for more details THIS thread on this community.
JIRA-DOC-497
0 -
Thank you, I already read theses articles (and congrats support answer on the thread)
BUT you didn't answer to my question
0 -
Do I understand you want a notification with a camera thumbnail in case the intrusion system is armed?
Then the following steps apply:
- Create a rule: Generic Event >>> Send Email
- Create a rule: Generic Event >>> Send Mobile Notification
- Create a rule: On Analytics Event >>> Do HTTP request (to trigger the first 2 rules) metadata parameters should be included it you want a thumbnail of the applicable device(s).
It could look like something like this:
https://<serverIp>:7001/api/createEvent?caption=<anyCaption>&metadata={"cameraRefs":["cameraId1","cameraId2"]} - Create a rule to enable rule 3.
- Create a rule to disable rule 3.
0 -
Hi Norman
no, I know to notify users
I don't between way A or way B, what is the best way to get the right notification (and keep metadata : the good cam picture)
because I get a lot of cam on my rules and make a rule per cam is heavy
0 -
Hi Julien ROMANO,
A and B both are possible.
When using the Generic Events you need to add the cameraRefs to the metadata parameter in the Generic Event, and this has to be done per camera. This method most likely will be used if the analytics don't have the cameraRefs or when multiple thumbnail images need to be added to the email of notification.
It's up to you to decide which one provides the solution for your case.
0
Please sign in to leave a comment.
Comments
6 comments