> 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/sensors/disabling-sensor.md).

# Disabling Sensor

**The following information is valid only for physical sensors. Virtual sensor deletion is described in another topic.**

**DISABLE SENSOR** button in Sensor **CONFIG** tab is active when:

1. Sensor is not included in enabled and active Integration;
2. Sensor is not included in enabled and active Rule.

<div data-with-frame="true"><figure><img src="/files/SD09nSyTEMWvVLrxlXav" alt=""><figcaption></figcaption></figure></div>

Pressing this button will disable the sensor from the cloud logically. This means:

* This sensor will not be found in any filters
* This sensor's **Tags** will be cleared
* No **Alarms** will be created for this sensor
* No history measurement data is deleted

**Please note**: the logical sensor's disabling does not impact aranet.cloud sensors number license. Sensor's data will continue to be registered in the cloud. To completely delete the sensor from the license and stop registering its data, you must unpair the sensor from Aranet Pro base.&#x20;

When a sensor is logically disabled, it appears in the **Disabled sensors** tab of the **SETTINGS** menu. You can restore a disabled sensor anytime: open the sensor's card and click the **RESTORE SENSOR** button in the **CONFIG** tab. You will need to add **Tags** to the sensor and include it in **Rules** again.

<div data-with-frame="true"><figure><img src="/files/zGQ7FATSt9q5ne5j5sAo" 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/sensors/disabling-sensor.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.