I have been using the built-in IVS on my 5442 cameras - it's really helpful at this time of year when leaves, spiders and the central heating exhaust can generate a lot of BI motion alerts.
To test out IVS, I cloned a camera and configured one of the cameras to use BI motion detection (CAM_BI_MOTION) and the other to use the built-in IVS alerting (CAM_IVS_ALERTS). The camera IVS alerting is fine and reliably records events to the camera's SD card.
If you don't tell BI which camera should be the Clone Master, it randomly assigns one of them as the master. This led to a load of confusion on my part because BI was not responding to the IVS alerts (that were being recorded on the Camera's SD card). What I discovered is:
If the CAM_IVS_ALERTS camera is set as the Clone Master, BI acts on the ONVIF alerts generated by the camera and records the clips as expected. But if the CAM_IVS_ALERTS camera is not the Clone Master, BI ignores the ONIVF alerts from the camera. (FWIW, it's fine if they are both configured as Clone Masters.) On my setup at least, it is entirely consistent and repeatable across all of my cameras.
Anybody else experienced this? I couldn't find anything about this issue in the BI help or in the forum.
To test out IVS, I cloned a camera and configured one of the cameras to use BI motion detection (CAM_BI_MOTION) and the other to use the built-in IVS alerting (CAM_IVS_ALERTS). The camera IVS alerting is fine and reliably records events to the camera's SD card.
If you don't tell BI which camera should be the Clone Master, it randomly assigns one of them as the master. This led to a load of confusion on my part because BI was not responding to the IVS alerts (that were being recorded on the Camera's SD card). What I discovered is:
- If you want BI to act on ONVIF alerts from a cloned camera, make sure that camera is set as a Clone Master.
If the CAM_IVS_ALERTS camera is set as the Clone Master, BI acts on the ONVIF alerts generated by the camera and records the clips as expected. But if the CAM_IVS_ALERTS camera is not the Clone Master, BI ignores the ONIVF alerts from the camera. (FWIW, it's fine if they are both configured as Clone Masters.) On my setup at least, it is entirely consistent and repeatable across all of my cameras.
Anybody else experienced this? I couldn't find anything about this issue in the BI help or in the forum.