Releases: ha-parcel-integrations/ha-budbee
Release list
0.13.1
Bug fixes
- Loosened tracking code validation to accept any format.
🙋 4 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.13.0
New features
- skip re-fetching parcels that have already been delivered or collected, reducing unnecessary polling while keeping their sensors and history available for as long as delivered parcels are normally retained
🙋 4 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.12.1
Other improvements
- maintenance release: attach the HACS release archive
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.12.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.
🙋 Open questions still need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.11.0
New features
- Add Swedish, Danish, Finnish and Norwegian translations.
- Add a French translation, for Budbee's Belgian deliveries.
🙋 5 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.10.0
New features
- Locker parcels now show an expected delivery time once Budbee provides one — typically once the parcel reaches its final terminal before your locker. Confirmed against a real order followed all the way from drop-off to pickup.
Other improvements
- Removed an internal log warning about locker parcel collection timestamps, now that the question it was asking has been answered by a real order.
📦 See every supported carrier — new ones land regularly.
0.9.1
Bug fixes
- A parcel in a Budbee Box no longer briefly reports as "at the pickup point" the moment the sender drops it off — it now correctly shows as in transit until it is actually waiting for you in the locker.
- A locker parcel arriving at a Budbee terminal no longer reports as "returning to sender". Arriving at a terminal is ordinary forward progress, not a return, and is now shown as in transit.
📦 See every supported carrier — new ones land regularly.
0.9.0
Track your Budbee parcels in Home Assistant 🇳🇱 🇧🇪 🇸🇪 🇩🇰 🇫🇮 🇳🇴 — home deliveries and Budbee Box lockers alike. No account needed, and no e-mail address either: just the tracking or order number.
Budbee's own tracking page asks for your e-mail address; this integration does not. That second factor only unmasks your own name, address and phone number in the response — nothing a parcel sensor reads. So there is one less e-mail address stored in your Home Assistant configuration, and one less thing to type.
New features
- Track any number of Budbee parcels by tracking or order number — account-less, using the same public API Budbee's own tracking page talks to
- Handles both kinds of Budbee order: a delivery to your door and a parcel dropped in a Budbee Box. They are served by different endpoints with different status vocabularies, and the integration picks the right one per parcel
- A parcel waiting in a locker reports
at_pickup_point, with the locker's name as its pickup point — and only becomesdeliveredonce you have actually collected it - Per-parcel sensor with the canonical status (
registered/in_transit/out_for_delivery/at_pickup_point/delivered/ …), Budbee's own status text, the expected delivery window and a tracking deep-link - Summary sensors: incoming parcels, next delivery, recently delivered parcels — plus outgoing parcels for returns you send back through Budbee
- Read-only Deliveries calendar
- Events and no-code device triggers — parcel registered, status changed, delivered, delivery time changed, and the outgoing pair
budbee.track_parcel/budbee.untrack_parcelservices (add a parcel straight from a dashboard button), a manual refresh button, a configurable refresh interval, 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
"Delivered" does not mean delivered on a locker parcel. Budbee reports Delivered the moment a parcel goes into the Budbee Box, which is not the same as you having it. This integration reports that as at_pickup_point and saves delivered for the moment Budbee says you collected it — so a "your parcel has arrived" automation fires when the parcel is genuinely yours, not when it is locked in a hatch.
Budbee returns no status history, on either endpoint, so unlike the other integrations in the family there is no history option here — the history attribute is always empty. A locker parcel also has no delivery window: what it has instead is a collection deadline, which is not the same thing and is not presented as one.
This is an early 0.9.0 release. The integration was built against a single real parcel — a Dutch locker order — plus Budbee's own tracking client for everything else. Locker parcels should be solid; home deliveries are mapped from a payload nobody has seen yet, and so are returns you send and orders outside the Netherlands.
To fix that, the integration reports what it does not know. On a home delivery, expect a warning in the log listing the response structure (field names and types only, no values — safe to paste), and shorter warnings for an unrecognised status, a field it does not map, or a parcel it decided you are sending. Each is logged once per restart, not on every poll. Please open an issue with what you see and what Budbee's own page showed at the time — those reports are the entire path to 1.0. If you would rather not see them, logger: can silence custom_components.budbee.parcels.
📦 See every supported carrier — new ones land regularly.