0.9.1

Other improvements

• If a real Packeta parcel returns event timestamps in a format we haven't confirmed yet (which would affect the delivery time and event ordering), the integration now flags it so you can help us fix the parsing.
• Reporting an unrecognised status now shows you how to attach a diagnostics file — which usually contains everything we need to fix it.

0.9.0

Track your Packeta (Zásilkovna) parcels in Home Assistant — the Central-European pickup-point and locker network (CZ, SK, HU, PL, RO). No account needed, just the "Z" tracking number, the same way you would on the Packeta tracking page.

New features

• Track any number of Packeta parcels by tracking number — account-less, using Packeta's public tracking API
• Per-parcel sensor with the canonical status (registered / in_transit / out_for_delivery / at_pickup_point / delivered / …), the carrier's own status text and a tracking deep-link
• Summary sensors: incoming parcels and recently delivered parcels
• Events and no-code device triggers — parcel registered, status changed, delivered
• packeta.track_parcel / packeta.untrack_parcel services (add a parcel straight from a dashboard button), a manual refresh button, a configurable refresh interval, opt-in per-parcel status history, and a diagnostic last-update sensor
• Part of the ha-parcel-integrations family: the same canonical parcel format, statuses and events as the other carriers, so it plugs straight into the Parcel Aggregator and cross-carrier automations

Notes

Packeta is a pickup-point / locker network and its tracking carries no delivery ETA, so the next-delivery sensor and calendar stay empty by design.

This is an early 0.9.0 release. The tracking endpoint and its "not found" response are verified live, but the success payload and status mapping are reconstructed from a community client and are best-effort until confirmed against a real parcel. If your log shows an "Unrecognised Packeta status" warning, please open an issue with the line so the mapping can be extended.

Credits

Thanks to the itsvic-dev/deliveries project, whose public client helped confirm the tracking payload and status codes.