> 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-deployment/deploy-sensors.md). # Deploy Wildfire Sensors Deploy Wildfire Sensors using tree nails or garden wire, then let them calibrate for 14 days before they are ready to detect fires. ## Deployment steps
Register Wildfire Sensors
  1. Before mounting the Wildfire Sensor, scan the Device ID using the Deployment app to register the Sensor and provide its GPS location with the Silvanet Cloud.
Mount Wildfire Sensors
  1. Install Wildfire Sensors using treenails or garden wire, then let them calibrate for 14 days before they are ready to detect fires.
Sensor Calibration
  1. Wildfire Sensors require 14 days after deployment to be calibrated to the environment. During this time the they do not provide useful data.
Sensor normalization
  1. Wildfire Sensors require time to stabilize depending on the type of activity it has encountered.
{% file src="/files/c5sgQ7p1aZUIM3LV8G2y" %} Dryad Field Guide {% endfile %} --- # 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-deployment/deploy-sensors.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.