6.3.0

Version 6.3.0

Attention

• API: missionCenter properties latitude and longitude may no longer be null.
• API: deviceLocationChanged and deviceLocations properties deviceLocationX and
  deviceLocationY are now required (always present).
• EchoShield: Minimum supported SW version is now 8.0.0.
• API: DeviceMiscellaneousData type assetData may be modified from API. For very advanced
  integrations only.
• API: Uthreat/UthreatBasis property muted can now also have values suppressed and type. This
  will only happen if the client has subscribed for suppressed uthreats.
• UthreatBasis threat property can no longer have value true.
• API: Additional property affiliation added to Uthreat and UthreatHistory.
• API: uthreatHistory elements now includes property uasId if it has been decoded by a sensor.
• uthreat history database will be reset.

Improvements

• Mission center is automatically set to match device locations. For vehicle solutions it will be
  automatically updated as the vehicle moves with appropriate intervals.
• Support for marking affiliation (friend, hostile, etc.) of drones, including TAK integration.
• GPS asset support for general NMEA message handling. Compass orientation
  will translate to asset heading in deviceGeolocation.
• GPS asset ip and port may be specified as : when adding the asset.
• Alarm zone ignores threats with friendly or neutral affiliation.
• ECM auto-jamming ignores threats with friendly or neutral affiliation.
• The ONVIF camera asset has been updated to support additional types of ONVIF cameras.
• EchoShield: Support for SW version 8.
• API: Optional classification property added to UthreatBasis to convey information about
  classification for devices supporting classification.
• Preview of Site Tuner feature for reducing false alarm rate on installations. The feature works
  by analyzing internal database collections and setting up filters for unwanted threats. The
  feature is still under development. Use at own risk.
• Support for composite of 3 Dobermann RF effectors.
• Sapient: detectionReports uses objectInfo to describe the detected threat, e.g. the RF
  protocol detected.
• Sapient: detectionReports uses the state field to convey the state of the threat. Value will
  transition from started to updated to stopped.
• Sapient: RF geolocated threats will, along with rangeBearing detectionReports from each sensor,
  also result in a location detectionReport from one of the involved sensors. Location detection
  reports will be sent from the same device throughout the lifetime of the threat. The feature is
  enabled by default, but can be disabled in environment via
  SAPIENT_RF_GEOLOCATION_ON_EDGE_NODE.