Releases: ha-parcel-integrations/ha-sunyou
Release list
1.0.0
Track your SunYou (SYPost) parcels in Home Assistant — the keyless cross-border tracker for the cheap Asia→EU e-commerce shipments (AliExpress-style orders and similar) that SunYou carries before handing the last leg to a national carrier. Like Cainiao, it typically sees a parcel well before the carrier that eventually delivers it does. No account is needed — you enter the tracking code yourself, just like on the SunYou website.
First stable release
No code changed since 0.9.0 — this release marks the integration itself as stable. The payload, the field inventory and SunYou's status codes are confirmed against real, live parcels, not reconstructed from a source repo, and every status maps cleanly onto this suite's canonical set.
The status vocabulary started at 17 confirmed pairs and grew to 28 within hours of release, entirely from real users' logs — at_pickup_point and returning included, both absent from the original research capture. That is by design: an unrecognised code reports unknown rather than guessing, and writes one line to your log with a ready-made issue link, so the vocabulary keeps closing from the field. The numbering pattern still implies a few more unseen siblings.
📦 See every supported carrier — new ones land regularly.
💛 Support the project
0.9.0
Track your SunYou (SYPost) parcels in Home Assistant — the keyless cross-border tracker for the cheap Asia→EU e-commerce shipments (AliExpress-style orders and similar) that SunYou carries before handing the last leg to a national carrier. Like Cainiao, it typically sees a parcel well before the carrier that eventually delivers it does. No account is needed — you enter the tracking code yourself, just like on the SunYou website.
New features
- Track any number of SunYou parcels by tracking code — no account needed
- Per-parcel sensor with the canonical status (
registered/in_transit/out_for_delivery/delivered/ …), the carrier's own status text, origin/destination country and a tracking deep-link - Summary sensors: incoming parcels, recently delivered parcels
sunyou.track_parcel/sunyou.untrack_parcelservices, so a dashboard button can add a parcel- Events and device triggers for parcel registered, status changed and delivered, so your automations need no polling of their own
- Opt-in per-parcel status history, at no extra request since SunYou ships it in the same response
- A manual refresh button and a diagnostic sensor showing when SunYou was last polled successfully
- A configurable polling interval — SunYou drew no rate limiting across dozens of research requests, unlike some carriers in this family
- 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
Known limitation: no delivery forecast
SunYou's tracking API never returns an expected delivery date or window — confirmed against 21 real parcels, the only date-like field on a delivered parcel is elapsed transit days, not an ETA. The "Next delivery" sensor, the Deliveries calendar entity, and the delivery-time-changed event/trigger all exist for parity with the other carriers in this family, but stay empty and inert for SunYou as a result. Every other sensor, event and service works normally.
Why 0.9.0, not 1.0.0
The payload, the field inventory and 17 of SunYou's status codes are confirmed against real, live parcels — not reconstructed from a source repo. What isn't proven closed yet is whether those 17 codes are the whole vocabulary: the numbering pattern (208/20899, 2071/2072) suggests unseen siblings, most plausibly more failure reasons. An unrecognised code is reported as unknown rather than guessed at, 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 close the gap.
📦 See every supported carrier — new ones land regularly.