Exacq Unbreaks Avigilon Integration

By: IPVM Team, Published on Oct 18, 2017

For nearly 4 years, Exacq had broken and effectively blocked use with Avigilon cameras, as IPVM reported in January 2014.

Now, Exacq has 'unbroken' this integration, which we see as being a warming of relations between the two companies. In this note, we examine what happened technically and what this signals about the relationship between the companies.

*** ****** * *****, Exacq *** ****** *** effectively blocked use**** ******** *******, ** IPVM ******** ** ******* 2014.

***, ***** *** '********' this ***********, ***** ** see ** ***** * warming ** ********* ******* the *** *********. ** this ****, ** ******* what ******** *********** *** what **** ******* ***** the ************ ******* *** companies.

[***************]

Avigilon ******* **-***** ** *****

***** ******* *.*.* ***** support *** ******** *******, according ** ******* ***** for *********** ****** [**** no ****** *********].

**** *********** **** ******* to ********'* ***** ******, and **** *** ******* any **** ** *********-***** motion ** ****** **** Avigilon *******.

 

IPVM **** *******

** ****** ***** ******* *.*.*.****** with ******** ** *** and ** **** **** cameras *** ********* ****** events ********* ** *** VMS ** ********, ***** below, **** *** ****** window ****** ******* **** on ****** *** ******** when ****** *****.

** ************* ** ****** VMD ** ********* ** Exacq, **** ** ****** sensitivity ** ****(*), **** pre *** **** ********* time:

Pixel ****** ********* ****

**** **** **** ******* works **** ********'* ***** motion ********* ****, *** classified ****** ****** ********* or ********* *****. ***** other events **** ****** *** recognized ** *** ***** server, *** **** *** not ***** *** ****** in *********.

Response **** *****

***** ********* ** ****:

******** *** ***** *** some ****** ******** ** wanted ** ******* ** their ******** ** ** worked **** **** ** test **** ****** *** validation. ** **** **** it's **** *** ***** motion *********.

Avigilon *******

**** ******** **** *** significant ******* ** ******** management *** ******* ****** get ******* *** ***** cameras **-***** ** *****.

****** *** **** - **** time *****, ******** *** **** ********** competing ******* *****, ********* moves **** ***** **** crossed *** **** ** pushing ** **** ***** VMS ********* ** ********, according ** ****** ***** to *** *******. ***** Avigilon ***** *** ** aggressive sales ****, *** ******* has **** **** ******* in *** ******* *** positioning ******.

Beneficial *** ********

**** ** ****, **** move *** ****** ******* as ***** ******* ****** blocked **** *****. ****, of ******, ******* *********** ******** ************ ****** ** ****. However, ***** ********* *********** with ******** *** ** a ******** *** ********** sign *** *** ******** that ********* *** *** simultaneously ******** *** *********** can ****** **** ********.

Comments (12)

For nearly 4 years, Exacq had broken and effectively blocked use with Avigilon cameras, as IPVM reported in January 2014.

Just the Avigilon motion detection was blocked, or Avigilon cameras in general?

VMD. There was no issue connecting to Avigilon cameras with Exacq, but you were limited to continuous recording. Now the VMD and I/O works. 

Didn't VMD anyway work if you just changed the onvifnvcpi.json file, as you pointed out in 2014?

 

At the time, yes, but it wasn't officially supported and would be overwritten every time you updated. I think support got a little spotty at one point, as well.

That makes sense because it's ONVIF motion detection, not some propreitery version.  

So if VMD worked for other ONVIF cameras on Exacq, and assuming Avigilon's implementation was correct, there's no reason it wouldn't work.

Therefore Exacq had to explicitly mark Avigilon cameras as not supporting ONVIF VMD so that the VMS would not even try. 

So really Exacq didn't just break Avigilon VMD, but actually had to break their ONVIF VMD in a way that made it not work for Avigilon.

 

Nope. ONVIF events are not standardized, even something as simple as VMD. Manufacturers can use different XML strings for events as they see fit. 

So in order to integrate various manufacturers, you need to know where their event stream is. It's not much in the way of coding requirements, but it still has to be integrated for each manufacturer.

That's what the onvifnvcpi.json file contains, the manufacturer name, the event (motion), the location of the event stream (RuleEngine/MotionDetection/), the specific motion event name (MotionActive), and whether it's off or on (1/0), shown here:

Nope. ONVIF events are not standardized, even something as simple as VMD. Manufacturers can use different XML strings for events as they see fit.

Are you sure about that? The strings are not arbitrary manfacturer creations, IMHO, and in any case they are dynamically discoverable at run time.  The Analytic test tool expects:

So in order to integrate various manufacturers, you need to know where their event stream is. It's not much in the way of coding requirements, but it still has to be integrated for each manufacturer.

I agree that Exacq did it this way, and therefore needs the Avigilon entry in the file; but I don't think it was necessary based on the ONVIF docs I have seen.

They unfortunately are arbitrary strings. 

In that onvifnvcpi.json file you can find the strings for multiple manufacturers, here's a sampling:

  • VideoSource/MotionAlarm/
  • VideoSource/MotionDetection
  • VideoAnalytics/Motion/
  • VideoAnalytics/MotionDetection/
  • RuleEngine/MotionDetection/ThresholdCrossed/
  • RuleEngine/CellMotionDetector/Motion/

Some use 1 for on and 0 for off, some use "true" and "false", etc., etc. 

They unfortunately are arbitrary strings.

Agreed they are different.  Though they look somewhat more alike than arbitrary, consider for instance stream URLS. Maybe it's a holdover from early ONVIF implementations?

Regardless my point was that whatever data definition the device used it could be dynamically retrieved at run time via SOAP calls etc, obviating the need for the motion parts of the file.  Perhaps it was easier for Exacq to manage it the way they did it.

Now the new Analytic test tool expects RuleEngine/MotionRegionDetector/Motion and event.

8.8 has been the best feature release in years in my opinion. Exacq nailed it on this one.

Is it possible to use current Avigilon models with the latest versions of Exacq still or is it limited to specific models.  They only have a couple listed.

We've had an Avigilon camera added to Exacq for months, if not more than a year, with no issues. It only works with the camera's VMD, not analytics, but is otherwise fine.

Archived video from today, with motion highlighted blue in the timeline.

Read this IPVM report for free.

This article is part of IPVM's 6,432 reports, 865 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now

Related Reports

Avigilon Open Analytics Tested on Apr 16, 2020
After years of effectively closed analytics, Avigilon decided in late 2018 to...
Genetec Security Center 5.9 Release Examined on Feb 06, 2020
Genetec released the next major version of Security Center, less than a year...
Anyvision Layoffs on Mar 19, 2020
Anyvision has conducted a layoff, citing the impact of coronavirus, joining a...
Cisco Acquiring Fluidmesh on Apr 09, 2020
Cisco announced it is acquiring niche wireless manufacturer...
Favorite VSaaS Providers 2020 on Apr 17, 2020
VSaaS is starting to become mainstream but who are integrator's...
Avigilon ACC Cloud Tested on Jul 08, 2020
Avigilon merged Blue and ACC, adding VSaaS features to its on-premise VMS,...
JCI "Fever Camera" Partners With China TVT on May 19, 2020
Johnson Controls (JCI) is the next big player to get into the 'fever camera'...
Access Control Course Spring 2020 - Register Now - Last Chance on Apr 21, 2020
IPVM offers the most comprehensive access control course in the...
Resideo AlarmNet Has Major Outage on Mar 12, 2020
AlarmNet suffered a major outage yesterday, impacting Total Connect, Resideo,...
Axis Discontinues Companion Hardware, Fully NDAA Compliant on Feb 03, 2020
Axis will be fully NDAA compliant, as the company has confirmed to IPVM it is...
IPConfigure Presents Orchid Fusion VSaaS on Apr 30, 2020
IPConfigure presented Orchid Fusion VSaaS at the April 2020 IPVM New Products...
Use Access Control Logs To Constrain Coronavirus on Apr 09, 2020
Access control users have included capabilities that are not commonly used...
FDA Defines Correct Operation of "Fever Cameras" on May 26, 2020
The US FDA has now defined the correct operation of "Thermal Imaging...
Openpath Raises $36 Million on Jul 16, 2020
Openpath has raised $36 million as 2020 has become a boom year for access...
Wyze Fails To Deliver Own On-Board Analytics, Launches Novel Name Your Own Price Service on Jul 24, 2020
While Wyze failed to deliver their own onboard analytics to replace the...

Recent Reports

SIA Coaches Sellers on NDAA 889B Blacklist Workarounds on Aug 05, 2020
Last month SIA demanded that NDAA 899B "must be delayed". Now that they have...
ADI Returns To Growth, Back To 'Pre-COVID Levels' on Aug 05, 2020
While ADI was hit hard in April, with revenue declining 21%, the company's...
Exposing Fever Tablet Suppliers and 40+ Relabelers on Aug 05, 2020
IPVM has found 40+ USA and EU companies relabeling fever tablets designed,...
Indian Government Restricts PRC Manufacturers From Public Projects on Aug 04, 2020
In a move that mirrors the U.S. government’s ban on Dahua and Hikvision...
Directory of 200 "Fever" Camera Suppliers on Aug 04, 2020
This directory provides a list of "Fever" scanning thermal camera providers...
Face Masks Increase Face Recognition Errors Says NIST on Aug 04, 2020
COVID-19 has led to widespread facemask use, which as IPVM testing has shown...
Dahua Loses Australian Medical Device Approval on Aug 04, 2020
Dahua has cancelled its medical device registration after "discussions" with...
Google Invests in ADT, ADT Stock Soars on Aug 03, 2020
Google has announced a $450 million investment in the Florida-based security...
US Startup Fever Inspect Examined on Aug 03, 2020
Undoubtedly late to fever cameras, this US company, Fever Inspect, led by a...
Motorola Solutions Acquires Pelco on Aug 03, 2020
Motorola Solutions has acquired Pelco, pledging to bring blue back and make...
False: Verkada: "If You Want To Remote View Your Cameras You Need To Punch Holes In Your Firewall" on Jul 31, 2020
Verkada falsely declared to “3,000+ customers”, “300 school districts”, and...
US GSA Explains NDAA 889 Part B Blacklisting on Jul 31, 2020
With the 'Blacklist Clause' going into effect August 13 that bans the US...
Access Control Online Show July 2020 - On-Demand Recording of 45+ Manufacturers Presentations on Jul 30, 2020
The show featured 48 Access Control presentations, all now recorded and...
Face Detection Shootout - Dahua, Hanwha, Hikvision, Uniview, Vivotek on Jul 30, 2020
Face detection analytics are available from a number of manufactures...
Sunell is The First China Manufacturer to Market NDAA Compliance on Jul 30, 2020
Most China manufacturers are going to be impacted by the NDAA 'Blacklist...