> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/buttons-and-keys/unlocking.md).

# Pembukaan kunci

Atur dan gunakan kata sandi pembuka kunci digital untuk perangkat GPS di Navixy dengan blok pembuka kunci. Ketersediaannya bergantung pada model perangkat.

Menetapkan sandi digital persisten untuk perangkat yang memiliki kunci elektronik atau immobilizer. Sandi disimpan di perangkat dan tetap aktif sampai diubah. Gunakan **Buka kunci** untuk mengirim perintah membuka kunci ke perangkat dari jarak jauh.

## Pengaturan

* **Kata sandi**: kode buka kunci yang akan disimpan di perangkat. Ubah di sini kapan saja. Sandi baru akan menimpa sandi sebelumnya.
* **Buka kunci**: mengirim perintah buka kunci ke perangkat secara langsung, membuka kunci tanpa perlu memasukkan sandi secara manual.

## Ketersediaan

Muncul pada model perangkat dengan kunci elektronik atau immobilizer digital.

## Lihat juga

* [Kata sandi](/docs/user/id/guide/devices-and-settings/device-specific-controls/buttons-and-keys/password.md): tetapkan kode buka kunci yang berlaku terbatas waktu.


---

# 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://navixy.com/docs/user/id/guide/devices-and-settings/device-specific-controls/buttons-and-keys/unlocking.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.