I started out my search looking for a way to have my VERA Lite home automation controller trigger a specific camera to begin recording when a sensor was tripped.
Without getting into too much detail, my VERA system integrates with my DSC alarm system. The DSC has 32 wireless sensor that are used for doors and windows.
When a sensor is tripped, VERA sees it by way of a plugin for the DSC alarm systems. VERA can then execute scripts, such as turn specific lights on/off, arm or disarm the house, etc.
Using an extra sensor, and mounting it in my mailbox, I have VERA send me an email anytime the mailbox is opened. It works great. However, not being satisfied with just a text email, I wanted VERA to send a command to the BI server to trigger a specific camera to record, and more importantly, ALERT by way of push notification and email pics/mp4.
While the cameras are all set up to record on motion via BI, none send an alert. The sensor in the mailbox would be the only trigger for the alert, and would instantly let me know that the box has been opened - by way of the BI app on my phone.
Entering this HTTP string in any web browser will trigger that specific camera to begin recording:
For example:
The user credentials must be for an administrative account.
When BI receives this command, it handles the request as an "external" trigger for the specific camera. So, if you want to receive an alert for this specific type of trigger on the camera, you do the following... Open camera properties, select alerts, and under 'trigger by', uncheck everything except for 'external'.
If you're using VERA, the string must be modified to work under the LUUP engine. Setting up a scene, you choose your trigger, and then for the action, you click on LUUP and paste the following:
It's that simple. And it works great... EXCEPT...
Just as with the Hikvision alarm bit that can be used to trigger a record in BI, this external trigger has the same limitations. That is, if you are using BI's motion detection for the camera, the 'external' trigger my not work. If the camera sees motion and initiates a record event, and as it's recording, BI receives an 'external' trigger, it will ignore the trigger - and any associated alert. The external trigger will only initiate an alert if the camera is NOT already recording.
For example: If my mailbox is opened, BI receives the command to trigger my front camera, and trigger an alert push notification/email. However, since the camera is looking at the mailbox, as my mail lady pulls up, BI's built-in motion detect triggers a record session. Since that session is underway as she opens the mailbox, the subsequent HTTP command VERA sends to BI is ignored, and I never receive my alert.
I can disable the BI motion detection option, but then that same camera will ONLY record when the mailbox is opened. I want both. Record any motion, but alert only if the box is opened - regardless of whether the camera is already recording due to motion.
What a wordy post - sorry. I've sent an email to Ken to ask him if it is possible to have BI respect an external trigger and its associated alert configuration even if that camera is already recording.
I'll post back what I hear. In the meantime, if anyone has any ideas on how to work around this issue (with using a single camera), I'm all ears.
Without getting into too much detail, my VERA system integrates with my DSC alarm system. The DSC has 32 wireless sensor that are used for doors and windows.
When a sensor is tripped, VERA sees it by way of a plugin for the DSC alarm systems. VERA can then execute scripts, such as turn specific lights on/off, arm or disarm the house, etc.
Using an extra sensor, and mounting it in my mailbox, I have VERA send me an email anytime the mailbox is opened. It works great. However, not being satisfied with just a text email, I wanted VERA to send a command to the BI server to trigger a specific camera to record, and more importantly, ALERT by way of push notification and email pics/mp4.
While the cameras are all set up to record on motion via BI, none send an alert. The sensor in the mailbox would be the only trigger for the alert, and would instantly let me know that the box has been opened - by way of the BI app on my phone.
Entering this HTTP string in any web browser will trigger that specific camera to begin recording:
Code:
http://IP_ADDRESS_OF_BI_SERVER:PORT/admin?camera=camera_short_name&trigger&user=XXXXX&pw=XXXXXX
For example:
Code:
http://192.168.1.100:81/admin?camera=Cam6&trigger&user=admin&pw=adminpassword
The user credentials must be for an administrative account.
When BI receives this command, it handles the request as an "external" trigger for the specific camera. So, if you want to receive an alert for this specific type of trigger on the camera, you do the following... Open camera properties, select alerts, and under 'trigger by', uncheck everything except for 'external'.
If you're using VERA, the string must be modified to work under the LUUP engine. Setting up a scene, you choose your trigger, and then for the action, you click on LUUP and paste the following:
Code:
luup.inet.wget("http://192.168.X.X:XX/admin?camera=camera_short_name&trigger&user=XXXXX&pw=XXXXXX",5)
It's that simple. And it works great... EXCEPT...
Just as with the Hikvision alarm bit that can be used to trigger a record in BI, this external trigger has the same limitations. That is, if you are using BI's motion detection for the camera, the 'external' trigger my not work. If the camera sees motion and initiates a record event, and as it's recording, BI receives an 'external' trigger, it will ignore the trigger - and any associated alert. The external trigger will only initiate an alert if the camera is NOT already recording.
For example: If my mailbox is opened, BI receives the command to trigger my front camera, and trigger an alert push notification/email. However, since the camera is looking at the mailbox, as my mail lady pulls up, BI's built-in motion detect triggers a record session. Since that session is underway as she opens the mailbox, the subsequent HTTP command VERA sends to BI is ignored, and I never receive my alert.
I can disable the BI motion detection option, but then that same camera will ONLY record when the mailbox is opened. I want both. Record any motion, but alert only if the box is opened - regardless of whether the camera is already recording due to motion.
What a wordy post - sorry. I've sent an email to Ken to ask him if it is possible to have BI respect an external trigger and its associated alert configuration even if that camera is already recording.
I'll post back what I hear. In the meantime, if anyone has any ideas on how to work around this issue (with using a single camera), I'm all ears.