> For the complete documentation index, see [llms.txt](https://lrvdlinden.gitbook.io/myparcel-for-homey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lrvdlinden.gitbook.io/myparcel-for-homey/en/installation.md).

# Install and connect

## 1. Install the app

Install **MyParcel** from the [Homey App Store](https://homey.app/en-us/app/nl.lrvdlinden.MyParcel/MyParcel/test/). The app runs on Homey Pro (local platform) with Homey version 12.3.0 or newer.

## 2. Add a carrier

1. Open Homey → **Devices** → **+** → **MyParcel**.
2. Choose your carrier. Every carrier is **its own device**; add one per carrier (or per account) you use.
3. Follow the pairing screen. Depending on the carrier:
   * **Account** – sign in with your carrier account (PostNL, DPD, bpost, Vinted Go, Post & DHL Germany, Mondial Relay, Amazon; optional for DHL, DHL Express and InPost). For some carriers you open a sign-in page and then paste the address you ended on back into Homey.
   * **Tracking number** – enter tracking numbers, sometimes with a postal code (GLS, Trunkrs, Dynalogic, Dragonfly / Intelcom, Budbee, InPost, DHL, DHL Express, bpost).
   * **API key** – FedEx (Track API) and Royal Mail (Click & Drop).
4. Wait for the first sync to finish. Existing parcels are then recorded silently, so you do not get a flood of *new parcel* notifications.

The exact steps are on each [carrier](/myparcel-for-homey/en/carriers.md) page.

## 3. Add tracking numbers later

For carriers that work with tracking numbers you can add or remove numbers through:

* the **device settings** (one number per line, sometimes with a postal code after it), or
* the Flow actions **Track parcel…**, **Stop tracking parcel…** and **Remove delivered parcels**.

Add `out` (or `out`) after a number for a parcel you send yourself, where the carrier supports it (DHL, DHL Express, Post & DHL Germany, Dragonfly).

## 4. Widgets and Flows

* Put the [widgets](/myparcel-for-homey/en/widgets.md) on your Homey Dashboard. **MyParcel Packages** and **MyParcel Delivery** show all carriers by default, including devices you add later.
* Build [Flows](/myparcel-for-homey/en/flows.md) with your carrier's cards; see the [examples](/myparcel-for-homey/en/examples.md).

## Good to know

* **Smart polling:** every 15 minutes when a delivery is near, every 45 minutes otherwise and quiet at night. Delivered parcels are no longer polled.
* **Passwords:** where possible MyParcel only stores tokens, not your password.
* **Repair:** when a login has expired, use **Repair** on the device – no need to remove the device. See [Troubleshooting](/myparcel-for-homey/en/troubleshooting.md).
* Not every carrier provides the same data; empty fields mean the carrier does not return that value.

[Homey App Store](https://homey.app/en-us/app/nl.lrvdlinden.MyParcel/MyParcel/test/) · [Homey Community](https://community.homey.app/t/app-pro-myparcel/159800)


---

# 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://lrvdlinden.gitbook.io/myparcel-for-homey/en/installation.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.