# Status icons

The Site Management app and the Deployment app share a common set of status icons for Wildfire Sensors, Mesh Gateways and Border Gateways.&#x20;

These color-coded icons allows the status of WildFire Sensors and Gateways to be easily identified.

{% hint style="info" %}
**Multiple Sensors deployed at a single location**

If two or more Wildfire Sensors have been deployed in a tight configuration (for testing purposes, for example) they appear as a single Sensor icon when zoomed out in Map view.&#x20;
{% endhint %}

## Wildfire Sensor status icons

<table data-full-width="false"><thead><tr><th width="100">Icon</th><th>Description</th></tr></thead><tbody><tr><td><img src="/files/uJXJnTypfRnuNnjbHxar" alt=""></td><td><strong>Planned</strong>: <br>The location of the sensor has been defined but has not been deployed.</td></tr><tr><td><img src="/files/UJjhMZDJD5MnoeTzlcdF" alt=""></td><td><strong>Deployed</strong>: <br>Sensor is deployed but not yet connected to the Silvanet Cloud.</td></tr><tr><td><img src="/files/fcjs0Z7fqI3VV5Rgoy2U" alt=""></td><td><strong>Calibrating</strong>: <br>Sensor is currently within the 14 day Calibration period and has not finished calibrating.</td></tr><tr><td><img src="/files/dAaBQ0WqMqPQbyZsFsh6" alt=""></td><td><strong>Active</strong>: <br>Sensor is connected to the Silvanet Mesh Network and is sending/receiving data.</td></tr><tr><td><img src="/files/uRbTx7hcX0Vm6KXH8L3Z" alt=""></td><td><strong>Monitor</strong>: <br>Sensor has not sent data to the Silvanet Cloud within the last 6 to 12 hours.</td></tr><tr><td><img src="/files/AWsejHht00l2z8rZRzc9" alt=""></td><td><strong>Inactive</strong>: <br>Sensor has not sent data for more than 12 hours. Sensor not connected to Border Gateway, superconductors are drained or other issues.</td></tr><tr><td><img src="/files/Bo73PAgtN7mtzMs29zgO" alt=""></td><td><strong>Fire Detected</strong>: <br>Sensor has detected a fire and has sent a Fire alert to the Silvanet Cloud.</td></tr></tbody></table>

## Mesh Gateway status icons

<table data-full-width="false"><thead><tr><th width="100">Icon</th><th>Description</th></tr></thead><tbody><tr><td><img src="/files/3h2uhucgRuZqqB82q5tR" alt=""></td><td><strong>Planned</strong>: <br>The location of the Mesh Gateway has been defined but not yet deployed.</td></tr><tr><td><img src="/files/aXXVQewJbKFhEpf5MVZv" alt=""></td><td><strong>Deployed</strong>: <br>The Mesh Gateway is deployed but is not yet connected to the Silvanet Cloud.</td></tr><tr><td><img src="/files/ZjykWoJIDwRlnvkW6Lmg" alt=""></td><td><strong>Active</strong>: <br>Mesh Gateway is connected to the Silvanet Cloud and is forwarding messages on from sensors or other Gateways.</td></tr><tr><td><img src="/files/JNBT9OvSmoJOrLZrX6xM" alt=""></td><td><strong>Monitor</strong>: <br>Mesh Gateway has not sent data to the Silvanet Cloud within the last 6 to 12 hours.</td></tr><tr><td><img src="/files/isPynbsl9VTPXqsbVRwA" alt=""></td><td><strong>Inactive</strong>: <br>Mesh Gateway has not sent data to the Silvanet Cloud for 12 hours.</td></tr></tbody></table>

## Border Gateway status icons

<table data-full-width="false"><thead><tr><th width="100">Icon</th><th>Description</th></tr></thead><tbody><tr><td><img src="/files/c31xEzgHK8as9k7oSJdQ" alt=""></td><td><strong>Planned</strong>: <br>The location of the Border Gateway has been defined but not yet deployed.</td></tr><tr><td><img src="/files/rPwyFhxwkeRYzigfQG8T" alt=""></td><td><strong>Deployed</strong>: <br>The Border Gateway is deployed but not yet connected to the Silvanet Cloud.</td></tr><tr><td><img src="/files/lsxO7dJ8eYzojUFCoyn0" alt=""></td><td><strong>Active</strong>: <br>Border Gateway is connected to the Silvanet Cloud and is sending/receiving messages.</td></tr><tr><td><img src="/files/xd5n6T9USJftRawaLkL9" alt=""></td><td><strong>Monitor</strong>: <br>Border Gateway has not sent data to the Silvanet Cloud within the last 6 to 12 hours.</td></tr><tr><td><img src="/files/ZpIw19muzsZy1onKK8R8" alt=""></td><td><strong>Inactive</strong>: <br>Border Gateway has not sent data to the Silvanet Cloud for 12 hours.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.dryad.app/dryad-documentation/resources/status-icons.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
