0.10.1

Other improvements

• When Trunkrs reports a delivery reason code (the failed / not-delivered states we still need to map), the integration now flags it so you can help us complete the status vocabulary.
• Reporting an unrecognised status now shows you how to attach a diagnostics file — which usually contains everything we need to fix it.

0.10.0

Other improvements

• The tracking service now uses tracking_code, matching every other integration in the family. The old trunkrs_nr field still works but is deprecated and will be removed in a future release — update your automations that call trunkrs.track_parcel / trunkrs.untrack_parcel to tracking_code.

---

📦 See every supported carrier — new ones land regularly.

0.9.0

The first release of the Trunkrs integration. Trunkrs has no customer account, so you register each parcel by its Trunkrs number plus the delivery postal code — the same pair the Trunkrs website asks for.

New features

• Per-parcel sensors with the sender, receiver, expected delivery window, the parcel's own status text and a link to the Trunkrs tracking page.
• Summary sensors — incoming parcels, next delivery, and recently delivered parcels, each carrying the full parcel list as an attribute so a dashboard card can render everything from one entity.
• A deliveries calendar showing the expected delivery windows, so upcoming parcels appear alongside the rest of your day.
• Events and device triggers for parcel registered, status changed, delivered, and a changed delivery window — enough to build "my parcel is on its way" automations without polling anything yourself.
• trunkrs.track_parcel / trunkrs.untrack_parcel services, so a dashboard button can add a parcel without opening the integration options.
• Opt-in status history — a per-parcel attribute listing each update with its timestamp.
• A manual refresh button and a diagnostic sensor showing when Trunkrs was last polled successfully.

Known limitation — and how you can help

The status vocabulary is still incomplete. Only SHIPMENT_DELIVERED has been seen on a real parcel so far, so a parcel in any other state reports unknown. It is never wrongly marked delivered — an unmapped status stays honest rather than guessing.

Each unrecognised status logs a one-shot warning containing a ready-made issue link. If you see one, opening that issue with the logged line is all it takes to get that status mapped for everyone.

Credits

Thanks to @joerimul for sharing a real tracking payload.