Tns1:Device/HardwareFailure/StorageFailure The cause can be tamper actions like camera movement or coverage. Tns1:VideoSource/GlobalSceneChange/RecordingServiceĭevice reports a large portion of the video content changing. Tns1:VideoSource/GlobalSceneChange/ImagingService Tns1:VideoSource/GlobalSceneChange/AnalyticsService Tns1:VideoSource/ImageTooBright/RecordingService Tns1:VideoSource/ImageTooBright/ImagingService Tns1:VideoSource/ImageTooBright/AnalyticsService Tns1:VideoSource/ImageTooDark/RecordingService Tns1:VideoSource/ImageTooDark/ImagingService Tns1:VideoSource/ImageTooDark/AnalyticsService Tns1:VideoSource/ImageTooBlurry/RecordingService Tns1:VideoSource/ImageTooBlurry/ImagingService Tns1:VideoSource/ImageTooBlurry/AnalyticsService Tns1:RuleEngine/CellMotionDetector/MotionĬell based motion detection determined by placing a grid over the video source and determining changes. Polygonal field detection determines if each object in the scene is inside or outside the polygon. Tns1:RuleEngine/FieldDetector/ObjectsInside To help with development of this component, enable info level logging for and create an issue on GitHub for any messages that show “No registered handler for event”. Below is a list of currently supported event topics along with the entities they create. This integration uses the ONVIF pullpoint subscription API to process events into sensors that will be automatically added to Home Assistant. The possible options are: tcp, udp, udp_multicast, http.Įxtra options to pass to ffmpeg, e.g., image quality or video filter options. You can configure specific FFmpeg options through the integration options flow by clicking the gear icon on the top right of the integration details page. You may disable unwanted entities through the Home Assistant UI. However, you may want to use a lower quality image. Usually, the first profile has the highest quality and it is the profile used by default. This integration will add entities for all compatible profiles with the video encoding set to H.264. Each profile provides different image quality, or in the case of an NVR, separate connected cameras.
Most of the ONVIF devices support more than one audio/video profile. Many Pelco cameras are Profile T conformant devices.If running Home assistant Core in a venv, ensure that libxml2 and libxslt python interfaces are installed via your package manager. Profile T is also complementary to Profile S. Profile T also covers ONVIF specifications for motion region configuration. Profile T for advanced video streaming such as the use of H.264 and H.265 video compression. Many Pelco cameras are Profile Q conformant devices. Profile Q provides quick discovery and basic configuration of conformant products over IP networks. Profile G for edge storage and retrieval for IP-based video systems – Pelco cameras with edge storage for recording video data are conformant Profile G and also S devices. Profile S also covers specifications for PTZ control, audio in, multicasting, and relay outputs for devices and clients that support these features.
Profile S for basic video streaming over IP networks – Pelco cameras are sending devices and VideoXpert is a requesting or receiving client.
Details can be found in individual Pelco specification (spec) sheets and via the ONVIF conformant product listing. This includes cameras from AXIS, Bosch, Dahua, FLIR, Hanwha, Oncam, Sony, Vivotek, and others.ĭifferent Pelco products support different profiles.
ONVIF standards are also primary means for integrating a wide range of cameras with Pelco VideoXpert. ONVIF is widely adopted and the primary means of integrating Pelco cameras with different non-Pelco video management systems. Pelco is actively involved in technical and executive leadership in ONVIF which is an open industry forum that provides and promotes standardized interfaces for effective interoperability of IP-based physical security products.