> 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-hardware/salto-updating-salto-firmware-on-devices.md).

# Update Salto device firmware

Update Salto device firmware using a PPD and verify the installed version.

New devices often need firmware updates. Update **only one firmware version per session**. Use a **PPD** (three-pin prong or RF).

1. Run PPD **Firmware Diagnostic** to show the device's Firmware Identity and version (some devices have multiple).
2. Download the needed file: connect the PPD to the Salto workstation → System → PPD → **Download Firmware Files** → Send.
3. Take the PPD to the device and choose **Update Firmware**, then present it to the lock. The lock updates automatically and reboots.
4. Re-run the Diagnostic to confirm.

![Salto PPD showing the Firmware Diagnostic screen (device 0134, firmware 01.71) presented to a lock](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5b54dbedb5647f625be4e029c79c7aaa26ca74bc%2FSECHUB-SALTO-09-ppd-firmware-diagnostic.jpg?alt=media)


---

# 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-hardware/salto-updating-salto-firmware-on-devices.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.