> For the complete documentation index, see [llms.txt](https://docs.nemopi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nemopi.com/fundamentals/buoys-and-sensors/caring-for-your-nemo-pi.md).

# Caring for your Nemo Pi

Checking and servicing your buoy periodically will help Nemo Pi continuously deliver high-quality data.

We recommend you conduct routine inspections of the buoy to identify any signs of damage, wear, or malfunction. Check for any loose or corroded parts, signs of water leakage, and the condition of the mooring lines and hardware. By performing regular checks and fixing any damage, you can prolong the life of your Nemo Pi buoy.

{% hint style="info" %}
We recommend organisations check their buoys and any accompanying sensors at least monthly.
{% endhint %}

## Tips for checking your buoy

1. Check for signs of external damage on the buoy's body and secure any loose items
2. Check for damage on the buoy's waterproof casing. If you notice any damage to the casing, you can try patching it with Duct tape
3. Secure and enforce any loosened antennae or sensor cables outside of the buoy
4. Wipe off dirt and salt marks on the solar panel with a wet cloth

If you encounter any difficulty, [please contact the Nemo Pi team](/overview/contact-us.md) for support. We can also help you organise replacement parts.


---

# 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.nemopi.com/fundamentals/buoys-and-sensors/caring-for-your-nemo-pi.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.