0.11.0

New features

• always check An Post on the adaptive schedule that speeds up while a parcel is out for delivery, slows down while it's still on its way, and stays quiet overnight apart from two catch-up checks, so parcels that show up on your account without going through Home Assistant still get picked up; the old "Refresh every" setting is gone and existing installs move over automatically

🙋 2 open questions need a real parcel to answer

---

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

0.10.1

Other improvements

• maintenance release: attach the HACS release archive

---

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

0.10.0

New features

• Automatic polling — Refresh every can now be set to Automatic instead of a fixed number of minutes. New installs default to it; existing installs keep their current fixed value until you switch. Automatic adjusts how often An Post is checked based on what your parcels are actually doing:

  • No polling between 00:00–06:00 local time, aside from one catch-up check right at each end of that window, so an overnight update is never missed.
  • Checks every 15 minutes while a tracked parcel is out for delivery today, starting an hour before its delivery window opens.
  • Checks every 45 minutes otherwise — this is also the minimum cadence, since it's the only way to discover a new shipment that appeared in your account.
  • Delivered parcels never affect the cadence — only what's still in transit counts.
  • A small, fixed per-install offset is added on top, so not every An Post installation polls at exactly the same second.

  This is opt-in for now, but it's expected to become the default — and eventually the only — polling behaviour across the parcel-integrations suite. If you try Automatic, we'd genuinely like to hear how it goes: share your experience in this discussion.

🙋 2 open questions need a real parcel to answer

---

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

0.9.0

A custom Home Assistant integration that tracks your An Post parcels. Sign in with your own An Post account and every parcel it already knows about is imported automatically; a parcel someone else sent you can be added to the account's watchlist from Home Assistant too.

New features

• Auto-imports every parcel your An Post account already knows about — no per-parcel setup
• an_post.track_parcel / an_post.untrack_parcel services add or remove a bare tracking number from the account's own watchlist, for parcels the account has not linked yet
• Per-parcel sensor with the canonical status (registered / in_transit / delivered / returning / problem / …), An Post's own category id, the expected delivery moment and a tracking deep-link
• Summary sensors: incoming parcels, next delivery, recently delivered parcels
• Read-only Deliveries calendar with the expected delivery moments
• Events and device triggers for no-code automations (parcel registered, status changed, delivered, delivery time changed)
• Automatic re-authentication when the An Post session expires
• Manual refresh button and a diagnostic last-update sensor
• Part of the ha-parcel-integrations family: the same canonical parcel format, statuses and events as the other carrier integrations, so it plugs straight into the Parcel Aggregator and cross-carrier automations

Why 0.9.0, not 1.0.0

The login → my-deliveries-api chain is live-validated end-to-end with a real Irish account, and the payload shape and status vocabulary are confirmed from An Post's own app — not guessed. What has never been seen is a populated response: the account used to build this integration had no parcel in transit. Every unmapped tracking-event category logs a one-shot warning with a ready-made issue link, and the same applies to schema drift and unparseable dates. If you get a real An Post parcel, a diagnostics dump after it updates — or just the warning line, if one appears — is exactly what closes this out.

Known limitations

• An Post's own status vocabulary has no same-day-delivery or "ready for collection" category, and the payload carries no pickup-point field, so out_for_delivery and at_pickup_point are never produced by this integration.
• Per-parcel status history (history attribute) is not available yet — it lives on a per-parcel detail call whose response shape has never been captured live.

---

📦 See every supported carrier — new ones land regularly.