> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker/troubleshooting.md).

# Troubleshooting

## Access the Device Info Menu

Opening the **Info Menu** on your Pebble Tracker will give you access to the IMEI and Serial Number, as well as allow you to obtain the device’s public key using the Pebble Desktop tool, if needed.

{% embed url="<https://youtu.be/c5uX2ePeQvA>" %}

## Retrieve the Device Public Key

### 1. Install PebbleUSBTools

Make sure you installed the required driver and PebbleUSBTool by following the section "**Install and run Pebble USB tools" in** [Online Firmware Update](/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker/firmware-update.md#offline-firmware-upgrade)

### 2. Access the Info menu in your Pebble Tracker&#x20;

Check out the video in the previous section for a visual guidance:

1. Power off the device
2. Press and keep pressing the arrow down
3. Press the power button once
4. Use the arrow keys to select the "About Pebble" and the power button to confirm

### 3. Retrieve the Public Key

Inside the Pebble USB tool, wait for the status bar to show the "*Pebble Connected"* message and then click "**Fetch PubKey**"

<figure><img src="https://content.gitbook.com/content/EyawgxYexImpo6OGzEiR/blobs/AHIvPrn8gxMNuQaXgoul/image.png" alt=""><figcaption></figcaption></figure>


---

# 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.iotex.io/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker/troubleshooting.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.