0.11.1

Bug fixes

• Loosened tracking code validation to accept any format.

🙋 3 open questions need a real parcel to answer

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project

0.11.0

New features

• skip delivered parcels when checking for updates, since their status can no longer change, reducing the number of requests made without affecting how long delivered parcels remain visible as sensors or in the options list

🙋 3 open questions need a real parcel to answer

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project

0.10.2

Other improvements

• maintenance release: attach the HACS release archive

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project

0.10.1

Bug fixes

• stop spurious diagnostic warnings for known address fields

🙋 3 open questions need a real parcel to answer

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project

0.10.0

New features

• Added a sensor that counts parcels currently awaiting pickup.

🙋 Open questions still need a real parcel to answer

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project

0.9.0

The first release of the Canpar integration — tracking for parcels shipped with Canpar Express, Canada's largest independent courier.

No account is needed: you enter the tracking code yourself, just like on the Canpar website.

New features

• Per-parcel sensors with the canonical status and Canpar's own event code.
• Summary sensors — incoming parcels and recently delivered parcels, each carrying the full parcel list as an attribute so one dashboard card can render everything.
• A read-only Deliveries calendar with the expected delivery window for every active parcel.
• Events and device triggers for parcel registered, status changed and delivered, so automations don't need to poll anything themselves.
• canpar.track_parcel / canpar.untrack_parcel services, so a dashboard button can add a parcel without opening the integration options.
• Opt-in status history — the full event timeline per parcel, at no extra request since Canpar ships it in the same response.
• A manual refresh button and a diagnostic sensor showing when Canpar was last polled successfully.

Known limitations — and how you can help

This release is built and tested against a handful of already-delivered parcels, so it ships conservatively:

• Only eight status codes are mapped so far. An unrecognised one reports unknown rather than guessing, and writes a one-time log line with a ready-made issue link.
• Canpar's event times have no time-zone offset, and an accompanying time_shift field of unconfirmed meaning. Rather than guess, times are shown exactly as Canpar's own local wall-clock values.

That's exactly why this is 0.9.0 rather than 1.0.0 — a real, in-flight parcel, ideally one crossing a time-zone boundary, is what moves it to a stable release.

Installation

Add https://github.com/ha-parcel-integrations/ha-canpar to HACS as a custom repository, install Canpar, and restart Home Assistant.

🙋 Open questions need a real parcel to answer

---

📦 See every supported carrier — new ones land regularly.
💛 Support the project