Release 16.5

Updated

New in ZEDEDA Cloud Release 16.5

Article publish date: (8/19/2025)

ZEDEDA Cloud versions

  • ZEDEDA GUI: 16.5.14
  • ZEDEDA API: 16.5.9

New features 

  • Single-Use Installer:
    As part of the edge node onboarding flow, you can now create and download a single-use installer or a live image through the ZEDEDA GUI without the need for any ZCLI interactions. 
     

  • Edge View UI:
    To provide a more seamless and secure experience for managing your edge devices, Edge View has been enhanced by integrating its functionalities directly into the ZEDEDA GUI, making remote access and troubleshooting for your EVE instances and edge apps more intuitive and efficient. This update eliminates the need for cumbersome SSH or local Docker installations for many common tasks, streamlining your workflow. Key improvements include:

    • Direct UI Interaction: Perform actions like VNC or SSH into applications, and download "collect-info" files directly from the ZEDEDA GUI with one click.

    • Simplified Troubleshooting: Access troubleshooting commands to view logs, files, network- and system-monitoring commands through a terminal session in the ZEDEDA GUI.

    • Improved User Experience: The new integration simplifies complex multi-step processes into single-click operations.
       

  • Edge View Security (Access Control with SSH Key Pairs):
    For enhanced security, you can now limit access to Edge View to specific users. The system uses SSH key pairs for authentication, with a public key being uploaded to the edge node and a private key on the user's laptop. All commands run over Edge View must be signed with the corresponding SSH private key. The edge node verifies the signature on each command using its stored public keys, and if the signature is valid, then the command will be executed. This system helps ensure you can identify who is running commands on your edge devices.
     

  • Hosted EVE-OS Images:
    Hosted EVE-OS Images are designed to simplify the process of updating your edge nodes. This new capability provides a centralized, ZEDEDA-hosted data store for all supported EVE-OS images, eliminating the need to manage your own image repositories. This feature reduces the manual effort and associated costs of maintaining your EVE-OS versions and infrastructure. It also bolsters security by ensuring images are sourced directly from ZEDEDA. You can now more easily keep your edge infrastructure updated with the latest features and critical security patches. To use this enhancement, make sure your firewall permits connectivity to the ZEDEDA-hosted data store URL (an S3 bucket on AWS).
     

  •  Cellular Access Point Name (APN) Attach Configuration: 
    LTE connections consist of two IP bearers, the initial (aka attach) bearer and the default data bearer. Both bearers require configuration settings (APN, IP type, potentially credentials, or more). Manually configuring the initial bearer is often necessary for private LTE networks or when transitioning between network providers, in which case the modem may not have a suitable profile installed. When adding a cellular network from Library > Networks, now you can configure Attach APN details.
     

  • Automate Deployments with Application Profiles: 
    Available for API and Terraform. App Profiles, Asset Groups, and Profile Deployments work together to streamline application delivery to edge nodes. An App Profile acts as a comprehensive bundle, encapsulating applications, network settings, and volume configurations. An Asset Group is a logical grouping of your edge nodes. A Deployment Profile can deploy an App Profile to the edge nodes identified in the Asset Group. This approach, along with the ability to manage it through Terraform, reduces the manual effort required, ensures consistency across devices, and allows for automatic deployment to new devices, making it easier to scale and maintain your edge infrastructure.
     

Enhanced features

  • Tool Tips: In addition to the existing “i” informational icon in the ZEDEDA GUI for showing upfront info messages, a "?" is now used for hover tooltips and help tooltips for form fields. 

  • Edge Sync Config Bulk Download:
    From the existing Edge Nodes > NODE_NAME > … > Download Edge Sync Config, you can now select multiple edge nodes from the list to download edge node configurations in bulk. The output is a single JSON file that aggregates multiple node configurations for each selected node into a file titled edge_sync_config_config_{timestamp}.json, which is downloaded to your local system.
     

  • VLAN Metrics:
    From the existing Edge Nodes > Adapters tab > expand the adapter, you can toggle Show/Hide Reported Status for your adapters. From Edge Nodes > Adapters tab > VLAN Details button > expand the logical label, now you can also toggle Show/Hide Reported Status for your VLANS. The status details include the following:   

    • Bytes transferred & received

    • Packets transferred & received

    • Errors

    • Drops

    • ACL drops

    • ACL limit rate drops
       

  • ECC Memory Monitoring: 
    Error-correcting code (ECC) memory is a type of memory that can detect and correct common types of internal data corruption. This ECC Memory Monitoring feature reports on correctable (single-bit) and non-correctable ECC errors. These errors are a sign of early hardware failures, enabling you to replace hardware before the errors become non-correctable and have operational impact. From the existing Edge Nodes > Status tab, now you can see the number of correctable and non-correctable errors, plus the overall status of ECC Memory, such as:  

    • Not applicable

    • Pass

    • Degraded: correctable ECC errors

    • Failed: non-correctable ECC errors
       

  • Smart Status:
    Self-Monitoring, Analysis, and Reporting Technology (SMART) metrics provide insights into the health and performance of storage disks. These metrics enable proactive monitoring, helping to identify potential failures before they occur. By leveraging SMART data, you can ensure optimal storage performance, prevent data loss, and extend the lifespan of storage devices. From the existing Edge Nodes > Storage tab, now you can see the overall SMART Status (if it’s available to click), plus the vendor specific attributes:  

    • Id

    • Attribute name

    • Value (Temperature conversion from raw Kelvin to Celcius)

    • Raw Value of temperature
       

  • Project Types Renaming: Legacy is now Standard in the GUI:

    • We've renamed the Legacy project type to Standard. This change clarifies the naming convention that emerged when “deployment projects” were introduced as a new project type. 

    • This update streamlines your experience, such that when you add a new project, the GUI form automatically defaults to selecting Standard as the project type. You can find this change when adding a new project under Administration > Projects, and clicking Add New.

    • The update is just a visual UI change. It still uses the same ENUM in the backend, so there is no impact to existing configurations. 
       

  • Managing EVE-OS Images: Latest is now Default in the GUI.
    We've renamed the Latest image to Default image. This change clarifies the naming convention when you define the EVE-OS version as the primary one that you want to use, since you can use any version, and it does not necessarily have to be the latest. As part of the Hosted EVE-OS Images feature, you can also change the default EVE-OS image to be used for edge nodes through the ZEDEDA GUI. See setting the default EVE-OS image.

  • Columns removed from Edge Node Onboarding Workflow: 
    We have streamlined the Edge Node Onboarding workflow by removing several read-only columns from tables in the ZEDEDA GUI. These columns (Bundle and Run State from the Network Adapters table, and Bundle from the IO Adapters table) were removed from the second page of the onboarding wizard. This change reduces unnecessary complexity, making the onboarding process faster and more intuitive, as these columns didn't contribute to user decision-making.
     

  • In the Marketplace, you can now filter by App Type.

  • In the Edge Sync configuration, you can now (optionally) include a Data Store.
    • If you intend to use collect-info.sh for troubleshooting, then you need a local HTTP Data Store within the air-gapped environment where you’re running Edge Sync.
    • This feature requires EVE-OS version 14.5.2-LTS or greater.

Known issues


Edge View UI issues:

  • Single Remote Console Session per Edge Application: Only one remote console session can be active per edge application at a time.

  • For Edge View VNC sessions, only one ongoing VNC session per edge node is supported.

  • Graceful Session Closure Recommended: We recommend closing the session from the Edge View UI screen before attempting to access another app on the same edge node. Switching between apps may result in errors, such as “Command execution failed”.

  • Connection Limit Configuration: If the default number of allowed connections per session is set to 1, parallel activities will be restricted. We recommend configuring the default allowed connections to more than 1 to enable smoother parallel workflows. The Edge View policy in the project should be updated according to the required number of connections.

  • SSH Terminal Persistence: The SSH terminal session will not persist when navigating away from the screen.

  • SSH Terminal Autocomplete Limitation: The SSH terminal operates in a typing-only mode, and command auto-completion using the Tab key will not work.

  • Status Display on Connectivity Loss: If the device loses connectivity to ZEDEDA Cloud, the Edge View status will still be shown as 'Activated' in the UI. However, the node's status color will update to reflect the actual connectivity state.

  • VNC is not working from the new Edge View UI Screen. 

Miscellaneous:

  • VNC is not working from the existing Edge App screen. 

  • In the single-use EVE-OS installer option for onboarding an edge node, the live image boot is not working properly if an existing EVE-OS image is already present on the edge node. 

  • In the single-use EVE-OS installer option for onboarding an edge node, the toggle for “I already have EVE-OS installed on my device or I will install it later” and the associated installation instructions shown are not valid for this flow.

  • The static IP address of the Docker runtime shows as empty (NOT AVAILABLE) in the API after an edge node reboots due to power failures, despite the runtime retaining the IP internally.

    • The static IP is missing from API responses after multiple power failure reboots, but visible via SSH on the runtime.
    • Docker Compose apps run correctly even when the IP is not reported in the API.
    • The issue does not self-resolve over time and occurs intermittently after several reboot attempts.
    • The runtime’s network state is internally consistent; it is the network addresses maintained by EVE that take time to stabilize.
Was this article helpful?
1 out of 1 found this helpful