v1.7.7

Fixed

• The 4-step delivery tracker could get stuck on "Sorting centre" and never advance to "Out for delivery" for ha-postnl v4.x specifically (discussion #17). ha-postnl v4.x reports its status as an UPPERCASE enum (OUT_FOR_DELIVERY, DELIVERED, ...) while DHL/DPD use lowercase; the tracker matched status case-sensitively, so the uppercase value never matched and the tracker stayed on the last step that did. Status values are now normalized to lowercase once, consistently, so every step is recognized regardless of casing. Reported by BerserkeR-Git.

v1.7.6

Fixed

• Switching a carrier's type in the editor kept the previous type's account — changing e.g. PostNL to GLS (or any account-less carrier) left the PostNL account behind, so every generated entity_id pointed at a sensor that doesn't exist for the new carrier; the card then showed nothing, with no error (#14). The carried-over account is now kept only when it actually resolves for the new carrier type — otherwise auto-detection (or an empty account for account-less carriers) takes over. Reported with a root-cause analysis and fix sketch by BerserkeR-Git.
• Expanding the last parcel in a list gave no visible feedback — its details panel opened out of sight below the bottom edge, with nothing on screen visibly changing, in both the main list and the (shorter) carrier popup (#15). A newly-expanded parcel now scrolls into view once its details panel finishes animating open, revealing the panel plus the next header. A row that's already fully visible does not move. Reported with a working fix by BerserkeR-Git.

v1.7.5

Fixed

• A carrier's saved sensor reference could silently go stale and stop showing data — a has_entity_name integration recreating its entities under a newly-added language (or after being removed and re-added) can leave an already-configured carrier's entity_incoming/entity_delivered/etc. pointing at an entity_id that no longer exists at all — surfaced by a GLS account whose entities were regenerated when German support was added (ha-gls#2). The v1.7.2 fix only covered the editor's auto-detect flow, not an already-saved reference going stale later — the card now also repairs a missing entity_id at render time the same way, by matching translation_key + integration platform via the entity registry. When more than one account of the same carrier type matches and the carrier's own stored account name doesn't narrow it to exactly one, it deliberately shows nothing rather than risk mixing in a different account's parcels.

v1.7.4

Fixed

• Carrier icon in the flat list sat too low, off-centre with the parcel name (regression from v1.7.3) — it relied on a hand-tuned vertical-align offset on the ha-icon element, which doesn't translate reliably since ha-icon has its own internal layout. Fixed by flex-centring .ph-name itself instead, which doesn't depend on guessing baseline metrics.

v1.7.3

Added

• Carrier icon per parcel in the flat list — with group_by_carrier: false, each row now shows the carrier's own branded icon next to its name (the same phu:/mdi: icon already used in the banner, carrier popup and grouped-view section headers), instead of relying only on the small status icon's colour tint. Some carrier brand colours sit close enough together that colour alone wasn't always enough to tell them apart at a glance; the icon's shape is unambiguous regardless of colour. Grouped view (the default) is unaffected — it already identifies the carrier via its section header.

v1.7.2

Fixed

• Entity auto-detection broke for non-English/Dutch Home Assistant locales — a has_entity_name integration's entity_id suffix is derived from whatever language HA was displaying when the sensor was first created, not from its (always-English) translation_key. The card only knew English/Dutch suffix words to guess against, so any carrier whose integration shipped a language the card hadn't special-cased (surfaced by a German-language GLS account, ha-parcel-integrations org discussion #3) went undetected entirely. Account/entity detection now also matches Home Assistant's own entity-registry translation_key (never localized) via hass.entities, grouped by device, as the primary path — the old text-guessing logic stays as a fallback for older Home Assistant versions without a registry cache, so nothing regresses there. This fixes the problem class for every current and future language any integration adds, not just German.

No action needed on your end — this only affects the card's automatic sensor detection; any carrier you already configured (including via a manual entity override) keeps working exactly as before.

v1.7.1

Added

• 11 new languages: Czech, Slovak, Hungarian, Romanian, Bulgarian, Ukrainian, Hindi, Swedish, Danish, Finnish, and Norwegian (Bokmål) — chosen to match the language coverage the underlying ha-parcel-integrations carrier integrations themselves recently added (reported in #13 by peternijssen, who maintains several of them). The card now supports 19 languages in total.

Fixed

• Repository description was stale — still read "dutch parcels card for home assistant" despite the card supporting 22 international carriers for a while now (#12).

v1.7.0

Added

• custom_name_scope split into three real scopes — device (browser-only), me (renamed from shared: your own account, synced across your own devices), and new everyone (default): saved instance-wide with live updates via Home Assistant's frontend/system_data API. Reading is open to all users; adding/editing requires an admin account. Needs HA core ≥ ~2025.12.
• sort_order option (auto/newest_first/oldest_first) — fixes #11: In Transit and Sent now sort soonest-first by default instead of the same "most recent first" order Delivered uses.
• group_by_carrier option (default true) — set false for one flat list interleaving all carriers by date instead of grouping them into sections.

Fixed

• 24-hour clock preference ignored — fixes #10. The card now mirrors Home Assistant's own time-format resolution instead of guessing from the language code alone.

Full changelog: CHANGELOG.md

v1.6.1

Fixed

• v1.6.0's release asset was stale for existing HACS installs. The uploaded file was overwritten in place under the same version tag three times while the custom parcel names feature was being built, and HACS only re-downloads when it sees a new version number — not when an existing tag's content silently changes. Anyone already updated to v1.6.0 was stuck on the very first upload (Nova Post/Delhivery/SunYou only, no custom names). No code changed in this release; it exists purely to give HACS a genuinely new version to fetch.

If you're on v1.6.0, update to v1.6.1 in HACS to actually get the custom parcel names feature described in the v1.6.0 notes below.

---

Added

• Custom parcel names — a small "+ Add name" control in each parcel's detail panel lets you give it a short label of your own (e.g. "Birthday gift") instead of just a tracking code (requested in #9). New custom_name_scope option controls where names are saved: device (default) uses the browser's local storage — simple, but per-device only; shared uses Home Assistant's own per-user storage, so a name shows up on every device signed into that HA account — the natural choice for a household sharing one login; off hides the control entirely.
• Nova Post, Delhivery and SunYou carrier support — three new account-less "hub" carriers, identical pattern to Helthjem/Dynalogic: tracking code only, no account, no postal code, no outgoing/letters support.
  • Nova Post — ha-parcel-integrations/ha-nova-post. Ukraine's largest private courier network (Nova Poshta).
  • Delhivery — ha-parcel-integrations/ha-delhivery. India-based logistics company.
  • SunYou — ha-parcel-integrations/ha-sunyou. China-based cross-border courier (SYPost).

Full changelog: CHANGELOG.md

v1.6.0

Added

• Custom parcel names — a small "+ Add name" control in each parcel's detail panel lets you give it a short label of your own (e.g. "Birthday gift") instead of just a tracking code (requested in #9). New custom_name_scope option controls where names are saved: device (default) uses the browser's local storage — simple, but per-device only; shared uses Home Assistant's own per-user storage, so a name shows up on every device signed into that HA account — the natural choice for a household sharing one login; off hides the control entirely.
• Nova Post, Delhivery and SunYou carrier support — three new account-less "hub" carriers, identical pattern to Helthjem/Dynalogic: tracking code only, no account, no postal code, no outgoing/letters support.
  • Nova Post — ha-parcel-integrations/ha-nova-post. Ukraine's largest private courier network (Nova Poshta).
  • Delhivery — ha-parcel-integrations/ha-delhivery. India-based logistics company.
  • SunYou — ha-parcel-integrations/ha-sunyou. China-based cross-border courier (SYPost).

Full changelog: CHANGELOG.md