> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/device-maintenance/reboot.md). # Reboot Sensor Reboot Guide This guide outlines the steps to reboot temperature sensors using the ACT button. Rebooting the sensor is an essential first step in troubleshooting, especially when a device is not communicating with the gateway. *** #### When to Reboot the Sensor * If the sensor has stopped transmitting data. * If the sensor appears offline in the monitoring system. * If you’ve recently changed the battery and want to restart the sensor. *** #### Reboot Procedure 1. Locate the ACT Button * The ACT (Activate) button is positioned on the front face of the sensor unit. 2. Press and Hold * Press and hold the ACT button firmly. * A green light (LED) will illuminate steadily. 3. Wait for the Flash * Continue holding the button until the green light begins to flash. * This flashing indicates that the reboot process is complete. 4. Release the Button * Once the light flashes, release the button. 5. Post-Reboot Behavior * The sensor will immediately attempt to communicate with the gateway. * It sends a join request and attempts to re-establish its network connection. *** #### Notes * If the green light does not flash, ensure the button is held long enough (typically 3–5 seconds). * If rebooting does not resolve the issue, check battery voltage. *** This process is simple, effective, and one of the primary diagnostics steps before proceeding to advanced troubleshooting or hardware inspection. --- # 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.didge.io/home/foodcore-sensors/device-maintenance/reboot.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.