> 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="https://2831658296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKwQxnS51pLI9fOl4xXp%2Fuploads%2F4HmgalyPsXkBrBTWyGtn%2Fimage.png?alt=media&amp;token=ead7e1fa-1517-4feb-b97f-b45cfb992193" 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="https://2831658296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKwQxnS51pLI9fOl4xXp%2Fuploads%2FkAM1ugnJz0TstsS21vbL%2Fimage.png?alt=media&amp;token=f540c637-ce8b-42e4-a837-f41aad170161" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/sensors/disabling-sensor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.