1.2.1

Bug fixes

• Loosened tracking code validation to accept any format.

---

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

1.2.0

New features

• stop repeatedly re-fetching parcels that have already been delivered, using the previously retrieved data to keep them shown in the options list and sensor for the usual delivered-retention window

---

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

1.1.1

Other improvements

• maintenance release: attach the HACS release archive

---

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

1.1.0

New features

• Polling is now fully dynamic and status-driven — the refresh-interval option has been removed; Home Assistant now adjusts how often each parcel is checked automatically based on its status.
• Split parcel management out of the settings form in the options flow, so adding/removing parcels and changing settings are now separate steps.
• Added a sensor that counts parcels currently awaiting pickup.

---

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

1.0.0

Nova Post moves to 1.0.0 on the strength of a real captured parcel — the happy path is now confirmed end-to-end, not reconstructed from documentation and third-party clients.

New features

• Switched to Nova Post's confirmed /site/v.1.0/ tracking surface — richer than the previous method in almost every way: a real event history, weight, dimensions, the pickup-point/branch name and a direct tracking-page link are all populated now.
• Optional per-parcel status history (history attribute), off by default like every other carrier in the family.
• Tracking codes are no longer limited to 14 digits — short reference codes and cross-border alphanumeric aliases (e.g. SHCN8143247690) are accepted too.
• Status mapping now uses Nova Post's own published 57-code table, not a third-party reconstruction, including a proper out_for_delivery state.
• Translations for every country Nova Post actually serves — German, French, Spanish, Italian, Polish, Czech, Slovak, Hungarian, Finnish, Romanian, Lithuanian, Estonian and Latvian join English, Dutch and Ukrainian.

Trade-off worth knowing

• sender/receiver now show a country and city, never a name — the new surface only carries geography. The old surface's named fields have no equivalent here.

---

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

0.9.0

The first release of the Nova Post integration — tracking for parcels carried by Nova Post (Nova Poshta), Ukraine's largest parcel-locker and courier network.

No account and no API key are needed: you enter the 14-digit tracking number (TTN) yourself, just like on the Nova Poshta website.

New features

• Per-parcel sensors with the canonical status, the carrier's own status text, the pickup location when a parcel routes to a branch or locker, and the sender/recipient name when the carrier provides one.
• Summary sensors — incoming parcels and recently delivered — each carrying the full parcel list as an attribute so one dashboard card can render everything.
• Events and device triggers for parcel registered, status changed and delivered, so your automations need no polling of their own.
• nova_post.track_parcel / nova_post.untrack_parcel services, so a dashboard button or an e-mail automation can add a parcel without opening the integration options.
• A manual refresh button and a diagnostic sensor showing when Nova Poshta was last polled successfully.
• A configurable polling interval (15 minutes to 4 hours; default 30).

Known limitation — and how you can help

The endpoint, the keyless apiKey: "" path and the not-found signal are all live-confirmed against a real probe, and the status vocabulary and field names are grounded in the carrier's own published documentation — but no real Nova Poshta parcel has ever been tracked through this integration. That is why this ships as 0.9.0 rather than 1.0.0, and it is the one thing you can help with:

• A status outside the known vocabulary makes the parcel report unknown rather than guessing, and writes one line to your log with a ready-made issue link.
• Whether DocumentWeight is really in kilograms, and what a delivered parcel's timestamp and delivery-window fields actually look like, have never been confirmed. If your parcel populates one of these, you get the same kind of one-shot warning — with the field name only, never any of its contents.

Other limitations

• No delivery date/time. Candidate fields exist on the carrier's side, but which one populates and in what shape is unconfirmed, so this release leaves them None rather than guess.
• No tracking-page link. No public consumer tracking-page URL has ever been captured for Nova Poshta.

---

📦 See every supported carrier — new ones land regularly.