--- title: "UPS" description: "UPS is a Marketplace integration for Home Assistant. It has 86 installs sharing analytics, needs the vendor's cloud and was last updated October 22, 2026." canonical: "https://vulpo.app/integrations/marketplace/ha-parcel-integrations-ha-ups" url: "https://vulpo.app/integrations/marketplace/ha-parcel-integrations-ha-ups.md" last-updated: "2026-10-22" version: "1.4" --- # UPS > UPS is a Marketplace integration for Home Assistant. It has 86 installs sharing analytics, needs the vendor's cloud and was last updated October 22, 2026. UPS is a Home Assistant integration that tracks UPS parcels by tracking code, with no account needed. It adds sensors for incoming parcels, the next delivery, delivered parcels, awaiting pickup and the time of the last successful update, plus a Deliveries calendar. Parcels can be added or removed through the options dialog or through actions to track and untrack a parcel by its code. Device triggers fire when a parcel is registered, changes status, is delivered or has its expected delivery time changed, so automations can start without code. Delivered parcels can be limited by days or by count, and a per-parcel status history can be switched on. It relies on the vendor's cloud, and updates arrive hours apart because UPS limits lookups, so there is deliberately no manual refresh button. Automatic summary of the README and code of ha-parcel-integrations/ha-ups. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=ha-parcel-integrations&repository=ha-ups&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=ha-parcel-integrations&repository=ha-ups&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **Device triggers**: Its devices can start automations directly. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### After setup - **Add a parcel**: Enter an UPS tracking code to start tracking it. You find it on the shipping confirmation or the missed-delivery card. - **Remove parcels** - **Filter by**: Show delivered parcels from the last X days, or limit to the X most recent. - **Amount**: Number of days or parcels to show. - **Include status history**: Add a per-parcel history attribute listing each status update (timestamp, status, original text). Off by default. - **Tracking codes** - **Delivered parcels: filter by** - **Delivered parcels: amount** - **Include status history** Texts from the code of [ha-parcel-integrations/ha-ups](https://github.com/ha-parcel-integrations/ha-ups). ## Entities - **Calendars**: Deliveries - **Sensors**: Incoming parcels, Next delivery, Delivered parcels, Last successful update, Awaiting pickup ## Actions - **Track parcel**: Start tracking a parcel by its UPS tracking code. Fields: Tracking code - **Untrack parcel**: Stop tracking a parcel by its UPS tracking code. Fields: Tracking code ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. ## From the README > 📦 Part of ha-parcel-integrations, a family of package-tracking integrations for Home Assistant that all publish the same parcel format, statuses and events, so they plug into cross-carrier automations and the optional Parcel Aggregator. Browse the other carriers on the website. > > 💬 Questions or feedback? Join the discussion on the Home Assistant community. > > - Track any number of UPS 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 and a tracking deep-link > - Summary sensors: incoming parcels, next delivery, recently delivered parcels > - Read-only Deliveries calendar, populated when UPS is currently showing a delivery estimate for a parcel > - ups.track\_parcel / ups.untrack\_parcel services, so a dashboard button can add a parcel > - Events + device triggers for no-code automations (parcel registered, status changed, delivered) > - Opt-in per-parcel status history > - A diagnostic last-update sensor > - No manual refresh button, deliberately: UPS allows only a few lookups per hour per connection, so a refresh button would spend the whole allowance in one press (see Polling) From the README of [ha-parcel-integrations/ha-ups](https://github.com/ha-parcel-integrations/ha-ups#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Energy](https://vulpo.app/integrations/category/energy.md), Backup power - Number: 86 installs sharing analytics; 5 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: 1.1.3, last updated October 22, 2026 - Domain: `ups` - Source: - Issues: In Vulpo: Calendar card, Chart card, Apple Watch Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/ha-parcel-integrations-ha-ups --- - HTML version of this page: https://vulpo.app/integrations/marketplace/ha-parcel-integrations-ha-ups - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml