0.9.0

The first release of the Österreichische Post integration — tracking for parcels carried by Österreichische Post (Austrian Post), Austria's national postal operator.

No account and no API key are needed: you enter the tracking number yourself, just like on Post's own tracking page. Both Post's own numbers and international UPU codes (RR123456789AT) work.

New features

• Per-parcel sensors with the canonical status, Post's own status text, the expected delivery window, the pickup location when a parcel routes to one, the weight and dimensions, and a link to the tracking page.
• Summary sensors — incoming parcels, next delivery and recently delivered — 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 expected delivery, 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.
• oesterreichische_post.track_parcel / oesterreichische_post.untrack_parcel services, so a dashboard button or an e-mail automation can add a parcel without opening the integration options.
• Tracking numbers are checked as you add them — a typo is caught right away, while a number Post does not know yet is accepted, because that is simply a parcel nobody has scanned so far.
• Opt-in status history — the full event timeline per parcel, at no extra request since Post ships it in the same response.
• A manual refresh button and a diagnostic sensor showing when Post was last polled successfully.
• A configurable polling interval (15 minutes to 4 hours; default 30).

Known limitation — and how you can help

The status vocabulary is complete and the error handling is verified, but no real Austrian parcel has been tracked through this integration yet. That is why it ships as 0.9.0 rather than 1.0.0, and it is the one thing you can help with:

• 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 — it says nothing about you or your parcel.
• Two statuses are mapped but have never been seen in the wild. The first time a real parcel reaches one, the integration asks you to confirm it landed in the right place.
• The expected delivery window, sender, weight and dimensions have never been seen filled in. If a real parcel is missing one of them, or if the weight turns out not to be in kilograms and the dimensions not in centimetres, you get the same kind of one-shot warning — with the field name only, never any of its contents.

Other limitations

• Pickup locations show a code rather than a name. When a parcel routes to a branch, post partner, pickup station or locker, pickup_point currently carries Post's own location code; resolving it to a readable name needs a second lookup that this release does not make.
• Only parcels you enter yourself. Post does have a signed-in view that lists your incoming and outgoing parcels automatically, but its login cannot be supported for everyone (ID Austria, Apple and Google sign-in, and two-factor accounts would all be left out), so this release tracks by number only.