November 16, 2023
New features supported
| Features |
Details |
Feature Flag |
| Enhance message inspector for 3rd party sensors |
As an IT/Tenant admin, I want to see both Join Requests from sensors and Join Accepts from IAV to troubleshoot all sensors trying to connect to IAV. |
N |
| Arctic support in IAV (EFT release) |
As an IT/Tenant admin, want to use the LoRaWAN PIM as a gateway for LoRaWAN, with the IR1101 being managed externally by a Cisco management tool. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- From January 12, 2022, API Keys will no longer be available for North Bound APIs. Users should refer to the DevNet documentation for instructions on using login credentials to get the access token.
Limitations
- To ensure NAT works smoothly, it's best to avoid using source ports below 1024 and the port 1900. If not, there's a risk that the IPSec tunnel between the IXM and the cloud environment may fail to connect due to blocked traffic.
- If sensors are onboarded but haven't sent any data, their DevEUI won't appear in the MQTT integration's topic path.
August 3, 2023
New supported features
| Features |
Details |
Feature Flag |
| Downlink support for cisco sensors |
As an IT/Tenant admin, the user can change the uplink frequency of a sensor so it can report data in increments other than default |
N |
| Bulk add of 3rd party sensors |
Users will be able to upload 3rd party sensors in bulk using CSV file and API. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from January 12, 2022 release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
May 10, 2023
New supported features
| Features |
Details |
Feature Flag |
| IAV 3rd party passthrough - Phase 1 |
As an IT/Tenant admin, the user can add an analog sensor to a sensor catalog so that the OT/Installer team can start onboarding the new sensors easily without having to configure individually. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from January 12, 2022 release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
March 7, 2023
New supported features
| Features |
Details |
Feature Flag |
| Transition of org hierarchy to common OD feature |
Organization Hierarchy Management, the service developed by IAV will be made into a common service that can be utilized by other services (CCV, EDM, SEA, EI, etc) |
Y |
| Alerts / templates for velocity RMS X and Y axis |
* User should be able to create alert rules for Velocity RMS on the X, Y, and Z axis of the Vibration Sensor.
* User should be able to add an alert to a template and receive notifications.
* When active, an alert should be visible on the dashboard, asset, and the sensor pages |
N |
| Support for Pulse Counting - Phase-1 |
* Dashboard - A line card to show the cumulative pulse value count
* The user will have the capability to manually modify the reading so that the physical meter value matches the IAV pulse counter.
* Decode the pulse counting data (from two digital inputs) and pass it over the MQTT stream |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from January 12, 2022 release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
December 7, 2022
New supported features
| Features |
Details |
Feature Flag |
| Alerts / templates for 3rd party sensors |
3rd party sensors template
* Add, edit and delete a template for 3rd party sensor
* List view and details information for a 3rd party sensor template
* 3rd party sensor default template
3rd party sensors alerts
* Add an alert rule for 3rd party sensor
* Alert raise for 3rd party sensor |
N |
| Throttle Email / SMS notifications |
Email/SMS notifications are sent only once for any alert raised. This avoids spamming user mail box. |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from January 12, 2022 release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
November 14, 2022
New supported features
This release has no customer-facing features. It includes platform efficiency and stability updates.
Caveats/Known Issues
None
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
September 6, 2022
New supported features
| Features |
Details |
Feature Flag |
| Alerts / templates support for Bridge |
Templates for Bridge
* Add a bridge template with unreachable alert
* Edit the bridge template
* List view for bridge template
* Show the details information for a bridge template
* Delete a bridge template
* Bridge status (online/Offline) support |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from the release of January 2022. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- When data spans across page boundary, sorting columns with duplicate values gives inconsistent results.
- On the mobile app,
- If the user switches from one tenant (with the Bridge feature flag enabled) to the other tenant (with the Bridge feature flag disabled), then they will still see the Bridge inventory tab.
- If the user switches from one tenant (with the Bridge feature flag disabled) to the other tenant (with the Bridge feature flag enabled), then they won't be able to see the Bridge Inventory tab.
The work-around to the above issue is to log out and log in to the mobile app, whenever the user wants to switch tenants.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
June 22, 2022
New supported features
| Features |
Details |
Feature Flag |
| Bridge 3rd Party Sensor Input Configuration (WebUI) |
Support for creating and managing the 3rd party sensors
* View the bridge input details from Web UI
* Configure the Analog/Digital inputs
* Configure sensors with category/unit and provide the input/output mapping
* Update the unit of a sensor from the Bridge input page
* Assign a sensor to an org hierarchy
* Delete a sensor |
Y |
| Bridge 3rd Party Sensor Data/Graph Viewing |
Support for viewing the 3rd party sensor telemetry data and graphs
* View telemetry data (raw and mapped values) in tabular format
* Export the telemetry data to a CSV file
* View the telemetry data in Zing charts (Graph visualization)
* View sensor health
* View 3rd party sensors in the sensor inventory list view
* View the transform data tab with the respective mapping values |
Y |
| Mobile App - Bridge Onboarding |
Support for Bridge Onboarding through Mobile App
* Onboard the Bridge and assign it to an org hierarchy
* View the Bridge list from Inventory tab
* View Bridge details along with configured inputs and their respective sensor assignments |
Y |
| Support of Zing charts for sensors and assets |
* Migration of existing sensors and assets line charts (AM charts) to Zing charts
* New look for boolean charts |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported from the release of January 2022. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- When data spans across page boundary, sorting columns with duplicate values gives inconsistent results.
- On the mobile app,
- If the user switches from one tenant (with the Bridge feature flag enabled) to the other tenant (with the Bridge feature flag disabled), then they will still see the Bridge inventory tab.
- If the user switches from one tenant (with the Bridge feature flag disabled) to the other tenant (with the Bridge feature flag enabled), then they won't be able to see the Bridge inventory tab.
The work-around to the above issue is to log out and log in to the mobile app, whenever the user wants to switch tenants.
Limitations
- Per NAT best practices, source ports of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
April 26, 2022
New supported features
| Features |
Details |
Feature Flag |
| 3rd Party Unit Library Management (WebUI) |
Support for creating and managing Unit library for 3rd party sensors
1. Analog input Sensor Type
* View the Cisco supported default Sensor types and units.
* Manage custom Sensor type and units
2. Digital input
* Manage Alias Types and Alias |
Y |
| Bridge Base Configuration Management (WebUI) |
Bridge Base configuration from the IAV Web UI.
* Add a Bridge using API
* Bridge management (View, Edit, Delete)
* View the raw payload data in the Message Inspector. |
Y |
| Bridge Health/Troubleshooting |
* Bridge Health — Display the Bridge health status, power status and LoRa parameters.
* Troubleshooting — Support for Troubleshooting Bridge - Similar to Sensor troubleshooting. |
Y |
| Alerts/Templates support for Vibration sensor |
* Support for creating Alert rules for Vibration sensor
* Alert attributes supported - Velocity (rms value Z Axis) and Temperature
* Default template and template support for Vibration sensor. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- Forbidden error message pop up is observed intermittently in the sensor telemetry page when the user hits the Refresh button multiple times.
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
February 15, 2022
New supported features
| Features |
Details |
Feature Flag |
| Mobile App |
* Ability to view sensor data on the mobile app
* Home/Landing page changed to the Inventory screen
* Support for Hierarchy and RBAC in the app
* Sensor and Network devices list with pagination support in the Inventory screen
* Sensor summary screen with support for viewing Sensor alerts. |
N |
| Organization Hierarchy Management |
* Support for Tenant/IT Admin to view all Access Control Groups of the selected Organization Level
* Warning message for Edit/Delete template scenario when the user does not have access to all devices present under the Template. |
N |
| Alert Dashboard Enhancements |
* Support for additional filters for all or specific sensors, network devices and assets. |
N |
| Generic Bridge (4-20mA, 0-10V, digital input) PoC |
* Support for adding/on-boarding the Bridge and viewing raw Telemetry Data
* Support for sending raw Telemetry data over MQTT / Azure. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- Forbidden error message pop up is observed intermittently in the alert dashboard page. As a work-around, users can refresh the page (browser refresh) to get rid of this message.
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
January 12, 2022
New supported features
| Features |
Details |
Feature Flag |
| Access control for Organization Hierarchy Management |
* Organization Hierarchy Management
* View the local or aggregated alert counts in the Organization hierarchy adjacent to the Organization levels
* Auto-populate selected Organization hierarchy in the Add Asset page
* Support of Organization Hierarchy with access control
* Manage an Access Control Group
* Manage User association to Access Control Groups
* Support for system-defined and user-defined across control groups
* Support for user sync from UI and auto-assignment of access control group based on user role
* Access control group granular filtering of Assets, Sensors, Network devices and Alerts in the landing dashboard and inventory pages
* Support of aggregation of Sensors/Assets/Network devices in the Organization hierarchy based on defined access levels |
N |
| Alert dashboard Enhancements |
* Filter the alerts by severity, status, asset and device name
* Cross launch to Alert Dashboard from Sensor, Gateway and Asset pages with automatic filter |
N |
| UI Enhancements |
* UI Unification - Support of 'Refresh' button in top right of all pages
* Missing frame symbol visibility improvement in satellite view for RF Performance tool |
|
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys will not be supported from this release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- An error will be shown in the Mobile app during Device onboarding in case the user selects an Organization level that they do not have access to.
- Alert rule name modification will raise new alerts instead of updating the event count for the older alert name.
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
September 21, 2021
New supported features
| Features |
Details |
Feature Flag |
| Organization Hierarchy Management |
* Manage Organization Hierarchy
* Manage Sensors, Assets and Network devices under an Organization Hierarchy
* Support for special Organization Hierarchy sub-node "Unused" for Sensors and Network devices in Inventory state
* Support for Organization Hierarchy filter in the Landing page dashboard and inventory pages
* Support for local persistence of Organization Hierarchy selection filter across Dashboard and inventory pages
* Support for single/bulk movement of Assets, Sensors and Network devices to new Organization Hierarchy level
* View count of Assets/Sensors in Hierarchy details page and cross-launch to inventory pages with associated filter
* Selection of Organization Hierarchy while on-boarding Sensor/Network devices on the Mobile app |
Y |
| RF Performance Tool |
* Filter the best Gateway in the RF performance tool
* View the missed frames in the RF performance map view |
N |
| Anomaly Visualization |
* Multiple threshold line visualization for the alert severity |
N |
| Alert dashboard enhancements |
* Alerts sidebar support containing the alert details - with Acknowledge/Clear actions and cross launch links
* "Alert Name" header in the table has been renamed to "Alert Rule"
* Added Asset column to the alert dashboard |
N |
| Enhancements |
* Support for selecting multiple sensors while creating/updating a template
* Support for multi-delete of Sensors and Network devices |
N |
| Mobile App |
* Version 1.0.4 of Mobile app for iOS and Android
* Selection of Organization Hierarchy while on-boarding Sensor/Network devices
* Pull-to-refresh support on the Network devices inventory page |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
Alert Dashboard
- Asset name for Sensor would be displayed only for newly created alerts and not for the existing alerts.
- Alert threshold value is not rounded-up in UI in the Alert details sidebar in case alert is created with Fahrenheit as the Unit.
- Asset name will be displayed for sensors even if they have been un-asssigned from the asset after alert has been raised. Asset name will not be shown in the sidebar in this case.
- Asset name will not be displayed for sensors if they have been assigned to an asset after alert has been raised. Asset name will be shown in the sidebar in this case.
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been on-boarded, but have not sent any up-links and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
- Text search in Alert Dashboard is not supported for Asset and Device name fields.
- On the Alert Dashboard, Acknowledge and Clear options don't get disabled if Alert is already Acknowledged or Cleared. This works fine in the Sidebar.
August 3, 2021
New features
| Feature |
Details |
Feature Flag |
| MQTT support for Dynamic Topic Pattern |
* Support for dynamic variables in topic pattern for MQTT integration. |
N |
| RF Performance Tools enhancements |
* Support for Tabular Telemetry
* Support for exporting telemetry data in CSV format |
Y |
| SSO support |
* Single Sign On Support for the web app and mobile app using SAML 2.0 |
N |
| Visually indicate anomalies |
* Support for viewing open alerts in sensor telemetry graphical view
* Support for viewing alert thresholds in sensor telemetry graphical view |
N |
| Organization Hierarchy Management |
Support for creation and management of Hierarchy |
Y |
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any up-links and end up in an unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
June 9, 2021
New features
| Feature |
Details |
| RF Performance Tool |
* Support for Adeunis Field Test Device
* RF coverage based on the Field Test Device data sets |
| Localization Support |
* Support for Imperial and Metric Unit Systems.
* Sensor data visualization based on the configured preferences
* Integrations, Email and SMS alert notifications use metric units |
| Northbound APIs |
* Support of Northbound APIs (Asset Types, Assets, Sensors) |
| Mobile App Enhancements |
* Support for template selection during sensor on-boarding
* Help page explaining steps to turn on the sensors.
* Support for showing the progress of network device on-boarding |
| Region Support |
* IN and AU region support in EU Cluster |
| UI Enhancements |
* For AV300 GPS sensors, Latitude and Longitude values of 0 are not plotted. Similarly, fix failed co-ordinates are not plotted. |
Open Issues / Caveats
| Feature |
Details |
| Sensor troubleshooting |
Sensor troubleshooting UI uses a fixed value of one day to calculate un-reachability and does not use the configured template value for the sensor. |
| Alert Dashboard |
The widget in alert dashboard is not auto refreshed although the alert table below is auto refreshed. So, if the user is on the alert dashboard page and there are new alerts added/cleared, then there will be a discrepancy in the alert count between the widget and the table below. |
Limitations
Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
May 20, 2021
New features
- Template Management
- Create/Edit/Delete a template
- Add a device from the template details page
- View associated template from sensor list, detail pages
- Update the Timeout (Missed uplinks) for the Sensor unreachable condition in the templates
- Default IXM Template Support for Unreachable Gateway
- Alert Rule Management
- Create/Edit/View an Alert rule
- List view for Alert rules
- Geofence Alert Support
- Miscellaneous Enhancements
- Create an Azure Integration with Certificate based authentication
- Message Inspector enhanced by showing frame summary information without expanding into frame details
Limitations
Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
Open caveats
- System template (IXM unreachable ) edit template - Fails to show already added recipients (if any)
- All types of upgraded Integrations will show the "Updated by" field as "asset-visibility".
March 16, 2021
New features
- Azure IoT Integration (Learn more)
- Create/Update/Delete an Azure IoT Integration
- Azure IoT Integration with support for streaming sensor telemetry data
- MQTT Integration (Learn more)
- Support for X509 based authentication
- Support for streaming alerts and sensor telemetry data via MQTT
- UI Enhancements
- View Sensor Type information in sensor list view
- Feature support to edit Gateway name and location post creation
- Message inspector feature now enabled only for IT admin users
- View the timestamp in seconds in the Telemetry page
- Launch Network device from sensor troubleshooting page
- View the Network status in the Network device details page
Limitations
- When using NAT, source ports below 1024 should be avoided. Also, a source port of 1900 should be avoided. Otherwise, there can be instances in which the IPsec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- The option "enableSSL" will be true by default in the integrations that are created with PEM (Certificate) based authentication.
- Data and alert payloads for MQTT and Azure have the following placeholder fields which will have default values in this release. In subsequent releases, support for sending actual values for these placeholder fields will be added.
- fCnt (LoRaWAN Frame counter) - This is currently zero.
- Asset ID - This is currently an empty string.
- Gateway Serial - Serial numbers for Network devices. This is currently an empty string.
February 2, 2021
New features
Geofences can be used to track the location of GPS-enabled sensors and associated assets in relation to an area on a map. This allows you to create a virtual perimeter for your real-world geographic area, and receive information as sensors and associated assets enter or leave that area. Learn more.
In future releases, you will be able to apply rules or trigger alerts based on where a sensor is in relation to that "geofence".
Note: Geofencing is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
The name and location of a Sensor can now be edited using UI. Learn more.
Limitations
- The Message Inspector is currently beta functionality and not fully implemented. Cisco will enhance the Message Inspector in future releases and make it generally available.
- Some Cisco sensors may have QR codes that are too small to scan with the mobile application. We advise installers to either scan the full-size QR code on the packaging or enter the DevEUI manually in the mobile application.
- Only public network devices are supported currently.
- Customers need to ensure either of the following:
- Each IXM gets a unique public IP when communicating with the IoT Operations Dashboard (non-NAT deployments scenario).
- If two or more IXM are behind the same NAT, then the deployment sequence of IXMs should be staggered i.e. please maintain a gap of 10 minutes between two IXM starts.
October 12, 2020
Industrial Asset Vision 1.0.0
Supported features
- Cloud SaaS application with support for multiple organizations (multi-tenancy).
- Sensor and network devices onboarding through the mobile application.
- Operational dashboard (OT/LoB) for Asset Tracking.
- Operational dashboard (OT/LoB) for Asset Telemetry (temperature, humidity, door open/close, water leak detection, light and motion detection).
- Export of ad hoc telemetry data.
- GIS map support for visualizing asset and sensor location.
- Asset management views.
- Sensors and network devices' inventory and health views.
- Alert generation and notification.
- Troubleshooting sensors and network devices.
- Report generation and download.
- Streaming sensor data to the customer’s external application (MQTT).
Limitations
- The Message Inspector is currently beta functionality and not fully implemented. Cisco will enhance the Message Inspector in future releases and make it generally available.
- The Contact Tracing feature is a beta functionality and is not ready for production use.
- Some Cisco sensors may have QR codes that are too small to scan with the mobile application. We advise installers to either scan the full-size QR code on the packaging or enter the DevEUI manually in the mobile application.
- Only public network devices are supported currently.
- Customers need to ensure either of the following:
- Each IXM gets a unique public IP when communicating with the IoT Operations Dashboard (non-NAT deployments scenario).
- If two or more IXM are behind the same NAT, then the deployment sequence of IXMs should be staggered i.e. please maintain a gap of 10 minutes between two IXM starts.
Open caveats
| Caveat ID |
Description |
| CSCvv62905 |
Sensor- AV200 - At low temperatures, the battery percentage level keeps fluctuating with each variation in temperature. |
| CSCvv65289 |
Sensor - AV207 - The occupancy sensor's QR code is too small to scan with IAV mobile app. |
| CSCvv65599 |
IPsec tunnel between IXM and Rainier is often unsuccessful when multiple IXMs are present. |