Releases: ha-parcel-integrations/ha-quickpac
Release list
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
- stop repeatedly re-fetching parcels that have already been delivered, since their details can no longer change, while still keeping them visible in the options list and sensor for the usual retention window
🙋 3 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.10.1
Bug fixes
- name the parcels options menu entry the same way in every language
🙋 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 an "awaiting pickup" sensor.
Other improvements
- Polling is now dynamic and status-driven, adjusting automatically to what your tracked parcels are doing instead of a fixed interval: a quiet window overnight, a fast cadence once a parcel is out for delivery, a slower one otherwise, and a full stop when nothing is tracked or everything has been delivered. There is no longer a user-configurable refresh interval.
- Parcel management is now a separate step from general settings in the options dialog.
- Raised the minimum supported Home Assistant version to 2024.12.
- Improved the bundled out-for-delivery notification automation example.
- Fixed a notification example that showed Dutch text instead of English.
🙋 3 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 Quickpac (Switzerland) parcels. No account is needed — you enter the tracking code yourself, just like on the Quickpac website.
New features
- Track any number of Quickpac parcels by tracking code — no account needed
- Per-parcel sensor with the canonical status (
registered/in_transit/out_for_delivery/at_pickup_point/delivered/ …), Quickpac's own status text and a tracking deep-link - Summary sensors: incoming parcels, next delivery, recently delivered parcels
- Read-only Deliveries calendar
quickpac.track_parcel/quickpac.untrack_parcelservices, so a dashboard button can add a parcel- Events and device triggers for no-code automations (parcel registered, status changed, delivered)
- Opt-in per-parcel status history
- Manual refresh button and a diagnostic last-update sensor
- A configurable polling interval — no throttling observed across dozens of research requests
- 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
Quickpac publishes its own OpenAPI document, so the endpoint, the payload shape and the status-code buckets are all pinned from the carrier's own schema — not reconstructed from a third-party tool. What has never happened is a single populated 200 response: every probe so far has returned 400 for lack of a real Swiss tracking number to test with. Every unmapped status code, every StatusGroup value and any unexpected field logs a one-shot warning with a ready-made issue link. If you have a real Quickpac shipment (a Galaxus/Digitec delivery is the easiest source), a diagnostics dump — or just the warning lines, if any appear — is exactly what closes this out.
Known limitations
- Sender, receiver, the pickup-point address and the expected-delivery window are not available — they sit behind a surname+postcode lookup this integration deliberately does not use, to avoid asking for personal data per parcel. A parcel waiting at a Coop Pick-up point still reports
at_pickup_point; only the address is unavailable. - No delivery-time-changed event will ever fire for this carrier — there is no ETA field anywhere in the public response.
📦 See every supported carrier — new ones land regularly.