> For the complete documentation index, see [llms.txt](https://docs.dryad.app/dryad-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dryad.app/dryad-documentation/silvanet-suite/silvanet-sma/site-view/wildfire-sensor-data.md).
# Wildfire Sensor data
Each Silvanet device sends data to the Silvanet Cloud. This data is then displayed as line graphs for a selected time period.
The default period is 24 hours. Select a time period for the displayed data sent in a range of 6 hours, 12 hours, 24 hours, 3 days or 10 days.
| Graph | Device | Description |
| ------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Air Pressure | Wildfire Sensor | Displays the environment's barometric Pressure (in hPa) over a selected time period. |
| Temperature | Wildfire Sensor | Displays the air temperature (in Fahrenheit or Celsius depending on user settings) over a selected time period. |
| Humidity | Wildfire Sensor | Displays the humidity level in the environment over a selected time period. |
| Air Quality | Wildfire Sensor | Displays the quality of the air available in the environment around the sensor. |
| Energy Level | Gateways and Sensors | Displays the level of energy stored in the supercapacitors throughout the day and during the night. Under normal conditions the Silvanet device should have sufficient energy stored to remain powered up throughout the night. |
---
# 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://docs.dryad.app/dryad-documentation/silvanet-suite/silvanet-sma/site-view/wildfire-sensor-data.md?ask=&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.
