February 28, 2024
New features supported
| Features | Details | Feature Flag |
|---|---|---|
| Ability to decode payloads of 3rd party sensors in IAV | As an IT/Tenant admin, the user can easily add a payload decoder from a 3rd party sensor vendor or write a new payload decoder to expose the telemetry of the sensor in IAV before MQTT integration. | Y |
| Downlink support for 3rd party sensors | As an IT/Tenant admin, the user can adjust the sensor's uplink frequency so that it can report data at increments other than the default. | Y |
| Arctic support - GA ready | To make Arctic GA ready, the user needs to conduct final validations. Additional requirements will be determined once the initial Arctic support features are developed. | 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 will not be 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
- To adhere to NAT best practices, avoid using source ports below 1024 and specifically avoid using port 1900. Otherwise, blocked traffic may lead to instances where the IPSec tunnel between the IXM and the cloud environment fails to establish.
- If sensors that have been onboarded but haven not sent any uplinks end up in an unreachable state, their DevEUI will not be present in the MQTT integration's topic path.