0.9.1

Other improvements

• Better self-reporting while the mapping settles. If Helthjem ever sends an estimated-delivery date in a format we don't recognise, the integration now writes one line to your log with a ready-made issue link instead of quietly dropping the date. As with an unrecognised status, reporting that line is all it takes to help confirm the last unverified pieces of a keyless, account-free integration.

0.9.0

The first release of the Helthjem integration — tracking for parcels delivered by Helthjem, the Norwegian home-delivery carrier many Norwegian webshops use.

No account is needed: you enter the parcel reference yourself, just like on Helthjem's own tracking page, and the integration reads the same keyless endpoint that page uses.

New features

• Per-parcel sensors with the canonical status, Helthjem's own status code, the estimated delivery date, the service (pickup) point when a parcel routes to one, and a link to the tracking page.
• Summary sensors — incoming parcels, next delivery, and recently delivered parcels, each carrying the full parcel list as an attribute so one dashboard card can render everything.
• A deliveries calendar — a read-only view of every parcel with an estimated delivery date, at no extra request.
• Events and device triggers for parcel registered, status changed, delivered and delivery-time changed, so your automations need no polling of their own.
• helthjem.track_parcel / helthjem.untrack_parcel services, so a dashboard button can add a parcel without opening the integration options.
• Opt-in status history — the full event timeline per parcel, at no extra request since Helthjem ships it in the same response.
• A manual refresh button and a diagnostic sensor showing when Helthjem was last polled successfully.
• A configurable polling interval (15 minutes to 4 hours; default 30).

Known limitation — and how you can help

This first release was built by reading Helthjem's live tracking API directly, without a real parcel to check it against. The response shape is confirmed, but Helthjem's status vocabulary is not yet — the mapping from Helthjem's own status codes onto the shared parcel states is a best-effort reconstruction.

A status we do not map yet makes the parcel report unknown rather than guessing, and writes one line to your log with a ready-made issue link. Opening that issue with the logged line is all it takes to complete the mapping — the code alone is enough, it says nothing about you or your parcel.

Worth reporting too: a status that feels wrong rather than unknown. Those are the mappings with the least evidence behind them — and that is why this is 0.9.0 rather than 1.0.0.