Releases: ha-parcel-integrations/ha-dynalogic
Release list
0.13.1
Bug fixes
- Loosened tracking code validation to accept any format.
🙋 6 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 already-delivered parcels when refreshing tracking data, since a delivered parcel's status can no longer change, while still keeping them in the options list, sensor and delivered-retention window
🙋 6 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.12.2
Other improvements
- maintenance release: attach the HACS release archive
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.12.1
Bug fixes
- mention Belgian postcodes in the postcode hint and error message
Belgian four-digit postcodes were already accepted, but the setup and
add-parcel screens still described the Dutch 1234AB format only, so a
Belgian user had no reason to think their postcode would work.
🙋 6 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.12.0
New features
- Polling is now fully dynamic and status-driven, replacing the previous fixed refresh interval.
- The postcode is now set once for the whole hub instead of per parcel, and parcel management now has its own step in the options flow, separate from settings.
🙋 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
- Support Belgian deliveries alongside the Netherlands — the postcode check now accepts both the Dutch (4 digits + 2 letters) and Belgian (4 digits) formats.
- Add a French translation, for Belgian users.
🙋 6 open questions need a real parcel to answer
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.10.1
Bug fixes
- The recipient's name is now filled in on every parcel. Dynalogic carries it in a field this integration did not know the name of, so the parcel's
receiverattribute was always empty.
0.10.0
Fixed
- Delivery history and delivery times were being thrown away. Dynalogic sends its timestamps in a different format than 0.9.0 expected, so every timestamp on every parcel was silently discarded — which meant an empty history and no "delivered at" time, on all parcels. Both formats are now read correctly. If your parcels had no history, they will after updating.
- Downloaded diagnostics now redact more of the carrier's own fields, including the driver's details and your standing delivery instructions.
New
- The sender is now shown on each parcel — the shop the parcel came from, e.g.
bol. - The recipient is now shown as well
- The carrier's own status text is now visible in the parcel's raw data, alongside the status fields
Still missing: the delivery window
The one response we have ever seen was of a parcel that had already been delivered — and those do not carry a delivery window at all. So the next delivery sensor and the Deliveries calendar are still empty, and that is the last significant gap before 1.0.
If you have a Dynalogic parcel that is still on its way, a diagnostics download from that parcel is the single most useful thing you can send us. Integration ⋮ menu → Download diagnostics. Everything identifying is stripped out before the file is written. That one file is what would give this integration its calendar.
Still below 1.0
Warnings in the log remain expected and deliberate — parts of Dynalogic's response have still never been seen, so the integration keeps reporting what it is unsure of. Each is logged once, not every poll, and please open an issue with what you see. It demonstrably works: this release exists because someone did.
Dynalogic delivers to the door and runs no parcel-shop network, so the at_pickup_point status never occurs. A delivery to a neighbour is reported as delivered.
📦 See every supported carrier — new ones land regularly.
0.9.0
Track your Dynalogic parcels in Home Assistant 🇳🇱 — the Dutch last-mile carrier behind a lot of deliveries that never mention its name. No account needed, just the order number and the postcode it is being delivered to, the same way you would on the Dynalogic tracking page.
You may be a Dynalogic customer without knowing it. The same network and the same tracking sit behind MediaMarkt, Samsung, Nespresso (machinereparatie), Menken, Dynasure and Dynahealth. One integration covers all of them — if your tracking link points at one of those sites, this tracks that parcel.
New features
- Track any number of Dynalogic parcels by order number + delivery postcode — account-less, using the same public API Dynalogic's own app talks to
- The postcode is asked once when you set the integration up and becomes the default for every parcel; a parcel going to another address can carry its own
- Adding a parcel checks it with Dynalogic straight away, so a mistyped order number or the wrong postcode is caught there instead of showing up weeks later as a parcel that never moved
- Per-parcel sensor with the canonical status (
registered/in_transit/out_for_delivery/delivered/ …), the carrier's own status fields and the delivery history - Summary sensors: incoming parcels, next delivery, recently delivered parcels
- Read-only Deliveries calendar
- Events and no-code device triggers — parcel registered, status changed, delivered, delivery time changed
dynalogic.track_parcel/dynalogic.untrack_parcelservices (add a parcel straight from a dashboard button), a manual refresh button, a configurable refresh interval, opt-in per-parcel status history, 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
Dynalogic delivers to the door and runs no parcel-shop network, so the at_pickup_point status never occurs. A delivery to a neighbour is reported as delivered.
It also sends no status text. Instead it reports which kind of job a parcel is (delivery, pickup, swap, return), how far along it is, and a numeric result code — so the raw_status field carries all three, like DEL_DEF/3/27.
This is an early 0.9.0 release, and unusually so. Dynalogic documents nothing about the data it returns, and this integration was written without a real parcel to check it against. The statuses should be right; what is definitely missing is the expected delivery window — the field exists in their app, but not under any name we could identify, so the next delivery sensor and the calendar stay empty for now. The recipient details are unmapped for the same reason.
To fix that, the integration reports what it does not know. On the first parcel you track, expect warnings in the log: the structure of the response (field names and types only, no values — safe to paste), each status combination and what it made of it, and anything it could not recognise. Each is logged once, not every poll. Please open an issue with what you see — those reports are the entire path to 1.0. If you would rather not see them, logger: can silence custom_components.dynalogic.parcels.
📦 See every supported carrier — new ones land regularly.