> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/salto/salto-troubleshooting/salto-error-doesnt-belong-to-system-when-bringing-locks-online.md).

# Salto error "Doesn't belong to system" when bringing locks online

Reset a Salto lock that was connected to another system before adding it.

The **"Error - Doesn't belong to system"** message appears when the lock was connected to another system first.

Either return the lock to Salto for a factory reset, or reset it at the **original site**:

1. Add the parameter `PPD_RESET_LOCKS` = `1` (System → General Options → Advanced).
2. In the PPD, select the lock and choose **"Allow to reset access points"**.
3. Set a PIN, choose Download, then present the PPD to the lock and enter the PIN.
4. A working **construction card** confirms the lock is at factory default.

Then add the lock normally.

***

🔗 **Related**

* [Updating Salto firmware on devices](/knowledge-hub/products/integrations/third-party-readers/salto/salto-hardware/salto-updating-salto-firmware-on-devices.md). Uses the same PPD.


---

# 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://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/salto/salto-troubleshooting/salto-error-doesnt-belong-to-system-when-bringing-locks-online.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.