> For the complete documentation index, see [llms.txt](https://easyedge.gitbook.io/easyedge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easyedge.gitbook.io/easyedge/release-notes/easyedge-5.0/5.02.01.md).

# 5.02.01

## ✨ Highlights

### EdgeNode Observability Enhancements

* New EdgeNode Overview, Status History, and Host Information views provide deeper visibility into edge runtime status and behavior.

### Improved Project Deployment States

* New and updated deploy states give clearer feedback during project lifecycle and deployment operations.

### Performance Improvements in Tree Navigation

* Introduced lazy loading in tree components for faster navigation and better performance in large projects.

## ⚙️ Updates & Improvements

### Studio & Usability

* Introduced a new **Inspect Modal** for improved diagnostics and data visibility.
* Updated global **Enable/Disable** icons for a more consistent user experience.
* Improved **deploy state management** with clearer status transitions and feedback.
* General UI refinements across modals, lists, and navigation.

### EdgeNodes

* Added **EdgeNode Overview** with consolidated runtime information.
* Introduced **Status History** for tracking EdgeNode state over time.
* Added **Host Information** and extended system details visibility.
* Improved **High Aavailability and EdgeNode status widget** for clearer cluster state monitoring.
* Enhanced **Console actions and global/secondary actions** for better control.

### Assets

* Improved **Asset creation wizard** with clearer steps:
  * “Name your Asset”
  * “Configure the Asset Communication Settings”
* Enhanced usability and clarity in Asset configuration flows.

### Library

* Improved **Asset Profile identification step** for better clarity during configuration.
* Enhanced **Data Model wizard tree structure** for easier navigation and consistency.

### General

* Improved list validation and consistency across Studio components.
* Performance and usability improvements across UI elements and workflows.

## 🐞 Fixes

* General bug fixes improving stability, consistency, and reliability across Studio, Assets, Applications, and Data Models.

### Studio - Project

* Fixed an issue where EdgeNode status was displayed incorrectly.
* Corrected behavior where duplicated Data Stream filters showed incorrect names.
* Fixed an issue where AI workflow buttons did not expand properly.

### Assets & Applications

* Fixed issues in **Tag configuration tables**, including column behavior and validation.
* Ensured **Data Type is now always required where applicable**.
* Corrected issues with **discard changes modal** in Asset and Application settings.

### Edge & Devices

* Fixed an issue where **serial ports (tty) were not detected in Studio despite being connected**.
* Corrected **uptime calculation on Raspberry Pi**, which previously showed incorrect values after extended runtime.

### UI & Usability

* Fixed issues related to:
  * Modal resizing and responsiveness.
  * Folder expansion and scrolling behavior.
  * Layout inconsistencies when navigating large structures.

## ✔️ Notes

* This release focuses on **usability, observability, and performance improvements**, especially in EdgeNode management and large-scale project navigation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://easyedge.gitbook.io/easyedge/release-notes/easyedge-5.0/5.02.01.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.