> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/assets/replace-sensor-in-asset.md).

# Replace Sensor in Asset

Sensor replacing in Asset is simple: drag-and-drop new sensor to the old sensors Measurement Point on the timeline.

1. Log in to your Aranet Cloud workspace with administrator rights and navigate to **ASSETS** menu.
2. Click on the Asset you want to edit, Asset properties pop-up window will open.
3. Select CONFIG tab and click **EDIT ASSET**.
4. Click and start to drag the new sensor to the timeline. Assisting placeholders will appear on the timeline:

<div data-with-frame="true"><figure><img src="https://forum.aranet.com/site/assets/files/3013/ac_sens_replace1.1586x0-is.jpg" alt=""><figcaption></figcaption></figure></div>

5. Drag and release a new sensor on the Measurement point of the sensor you want to replace:

<div data-with-frame="true"><figure><img src="https://forum.aranet.com/site/assets/files/3013/ac_sens_replace2.1583x0-is.jpg" alt=""><figcaption></figcaption></figure></div>

New sensor has replaced the old one in the measurement point starting from the current time. You can adjust replacement time by selecting the sensors ribbon and clicking on the edit icon. ![](/files/D1g3P5VRqM41wHxDz2wG)

Now the sensor named "CO2\_New" changed its status to attached with a yellow flag, and removed from the Asset sensor named "CO2\_No2", which became available for attaching to another asset and has a green flag.&#x20;

<div data-with-frame="true"><figure><img src="https://forum.aranet.com/site/assets/files/3013/ac_sens_replace3.398x0-is.jpg" alt=""><figcaption></figcaption></figure></div>


---

# 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://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/assets/replace-sensor-in-asset.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.