0.11.0

New features

• skip re-fetching parcels that have already been delivered, reducing unnecessary network requests while still keeping delivered parcels visible in the options list and sensor for the usual retention window

🙋 2 open questions need a real parcel to answer

---

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

0.10.1

Bug fixes

• stop hiding parcel details that fell outside a fixed set of fields

🙋 2 open questions need a real parcel to answer

---

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

0.10.0

Breaking changes

• The service field barcode is now tracking_code — bpost.track_parcel and bpost.untrack_parcel take tracking_code instead of barcode, matching every other carrier in the family. Update any automation, script or dashboard button that calls these services; the shipped dashboard example shows the new form. Your tracked parcels and hub settings are unaffected — nothing needs re-adding, and the Configure dialog is unchanged.

---

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

0.9.0

First release. Track your bpost (Belgium) parcels in Home Assistant — no account needed, one hub per delivery postal code, then add parcels by barcode.

New features

• Track any number of bpost parcels by barcode — no account needed, one hub per delivery postal code
• Per-parcel sensor with the canonical status (out_for_delivery / delivered / unknown / …), the carrier's own status text, the expected delivery window (when bpost reports one) and a tracking deep-link
• Summary sensors: incoming parcels, next delivery, recently delivered parcels
• Read-only Deliveries calendar with the expected delivery windows
• bpost.track_parcel / bpost.untrack_parcel services, so a dashboard button can add a parcel
• Events + device triggers for no-code automations (parcel registered, status changed, delivered, delivery time changed)
• Opt-in per-parcel status history
• Manual refresh button and a diagnostic last-update sensor
• French and Dutch translations, alongside English

Good to know

• The field map was reconstructed from third-party open-source clients. A first real parcel has since confirmed the delivered/delivered_at and status-history shapes; the ETA window shape and a pickup-point delivery's payload are still unconfirmed, so this stays pre-1.0.0 for now.
• If your log shows an "Unrecognised bpost activeStep code", "expectedDeliveryTimeRange was populated for the first time" or "deliveryPoint was populated for the first time" warning, please open an issue with the line — that is how the mapping grows.

Credits

• Field map and endpoint reconstructed from the community integrations therealabradolf/ha-bpost-tracker and myTselectionPublic/homeassistant-bpost-integration.