> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Release 19.2.29

> Article Published Date: 6/24/2026. Edge Infrastructure Services versions: ZEDEDA UI 19.2.9, ZEDEDA API 19.2.29. Resolved issues and fixes for Node Cluster volumes and more.

Article Published Date: 6/24/2026

## Edge Infrastructure Services Versions

* ZEDEDA UI: 19.2.9
* ZEDEDA API: 19.2.29

## Resolved Issues and Fixes

* **Volume instance device ID assignment for Node Cluster volumes.** A prior change inadvertently removed device ID assignment for volume instances explicitly bound to a node Cluster (ENC). Edge Infrastructure Services now restores the correct assignment.
* **Volume instance network ID assignment timing for Node Cluster volumes.** Edge Infrastructure Services now defers network ID assignment for ENC-bound volume instances until app assignment, preventing mismatches when a volume is placed on a specific cluster node.
* **Incorrect passthrough adapter configuration sent to nodes.** Edge Infrastructure Services was incorrectly including network interfaces in the passthrough adapter configuration sent to EVE-OS (Edge Virtualization Engine). This could cause unexpected behavior on nodes; network interfaces are now correctly excluded.
* **Redundant processing during network instance configuration merges.** Edge Infrastructure Services was parsing node configuration data once per network instance during merges, causing unnecessary overhead on nodes with many network instances. Each node's configuration is now parsed once and reused.
* **GPS data handling in device location queries.** GPS data structures were not being copied before use in multi-node location queries, which could cause data loss when the underlying database records were released. Edge Infrastructure Services now copies GPS data correctly.
* **Network ports with no upstream network incorrectly excluded from the system adapter list.** A filter intended to exclude bond member ports from the system adapter list dropped ports that hosted network instances but had no upstream network. Edge Infrastructure Services now excludes only bond member ports.