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

# 4.1.0

### General

* Added support for the following device types:
  * NEON Vibration Sensor - v4.1
  * NEON Steam Trap Sensor - v1
  * NEON Pressure Sensor/Gauge - v1
  * NEON Temperature Sensor - v1
* New UI and styling across all dashboards.
* Unit conversion intorduced. 
* Added support for KR-920 region. 
* Add support for ThingPark Actility LNS

### Events Center

* New feature, events center, introduced to display alarms. Further detail in the [Events Center](/docs/solidred-documentation/common-dashboards/events-center.md) section.

### Entity management

* Plus button to add sites, assets and/or devices included at the top of the navigation panel. 
* Field 'Parent asset' added to the device and asset management, with this, users can move entities in the asset hierarchy. 
* Site management added. 
* Import feature to add devices using the keys files introduced. 


---

# 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://docs.twtg.io/docs/solidred-documentation/release-notes/4.1.0.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.