Mail and Packages: Custom component for UPS, FEDEX, and USPS

Development
623

If you’re referring to b10, there was a breaking change listed in the release note. I’ll post it here.

0.2.2-b10

:boom: Breaking Change :boom:

2 sensors renamed, please reconfigure with options button.

:sparkles: Changes :sparkles:

  • Automatic detection of Home Assistant configuration directory added to config_flow
  • Actually disable sensors that are disabled and do not attempt to check them still
  • Added automated checks for formatting (github)
624

OK missed those. When I checked the repository, only release notes up to 0.2.2-b9 were posted.

Also what two sensors were renamed? The option button no longer lists the various sensors so that ones not applicable can be disabled.

625

Ya github moved it down, very weird, HACS should list changes in it’s update window tho.

The drop down should have all the sensors listed, it’s just internal naming for proper ordering of the sensor loops.

626

Looks like some github weirdness occured, lemmie fix the release.

627

OK all fixed. Thanks. Now I must be blind because I still can’t seem to find the install procedures for the custom card that goes with this. And finally, though I got an email today about an Amazon package delivery for tomorrow, am I correct that the sensor will only show it on the day of delivery like packages from other sources?

628

That is correct, you’ll see it tick to 1 tomorrow.

You can add the card to HACS:
Add the repo link: GitHub - moralmunky/Home-Assistant-Mail-And-Packages-Custom-Card: A Custom Lovelace card to pull together the mail and packages sensors.
image

image
image774×709 63.8 KB

Edit: @moralmunky if you revert the filename change, the repo will be fixed :wink:

629

I tried adding this custom card and this is the error that showed up.
“Repostitory structure for master is not compliant”

630

See my edit note for Moralmunky :wink:

631

What should we ‘revert’ it to?

TY

632

I pushed a 0.2.2-b10.1 out, if you’re running betas.

633

Started reading the HACS doc and there was mention of the repo name and file name being the same and then got pulled away and haven’t revisited it.

I think I also have to update the JSON file to match the name change.

In the meantime, people interested can simply download the two JS files. In this case all HACS is doing is downloading the two JS files correct? You still have to manually add the references to the Lovelace resources.

634

Yes unless you have the json file setup then they don’t have to match the repo name :slight_smile:

635

I did a manual install and got the card working but It doesn’t look like it Amazon packages are being handled properly. The summary is showing two packages in transit; however, both were separately delivered several hours ago. But I’m seeing 0 deliveries and there doesn’t seem to be a place to put the number of Amazon packages delivered. Since most of my packages come from Amazon, I would like to see them broken out more like the others.

636

Sounds like a feature request, I’d post it on the card’s github issues tracker.

637

OK no problem, I thought that would be the direction to go so I’ll probably collect my thoughts and submit something tomorrow. :slight_smile: .

1 Like
638

The summary sensor you create is separate from the integration and the custom card, however the numbers it pulls in are from the integration.

Amazon is complicated because they use their own contractors to deliver (and do not send emails to confirm delivery) and they also use USPS and UPS. This means two things:

  • Amazon Contractor: You get the email that says when the package should arrive, there is no day of in transit email and there is no delivery confirmation email. In this case the count will hang out in the email sensor until it is out of the sensors 3 day search scope. @firstof9 am I reading the code right?
  • Amason outside carrier (like USPS or UPS): You get that same email saying when the package should arrive. This, again, shows in the Amazon sensor until it is out of search scope. You also will get a count through which ever carrier they send the package through. If it was USPS, for example, you would see a count in USPS through in transit and delivery.

So when you say you are seeing it indicate 2 packages in transit, it depends on how Amazon sent them to you and if you are getting delivery notifications from the carrier. @firstof9, I see the constant shippers doesn’t include Amazon. So I @ZombiEd is talking about the cumulative in transit sensor, it should have picked up a notification from “capost”, “dhl”, “fedex”, “ups”, or “usps” and hasn’t received (or didn’t sign up for) the delivery confirmation emails, correct?

I suppose some of this Amazon explanation should go into the wiki :no_mouth:

639

Correct Amazon usually sends the “Shipped” email ~3 days in advance.

Correct, we don’t have a ‘delivered’ or ‘delivering’ sensor available to actually tally the counts for Amazon due to their being different.

640

I agree Amazon can be complicated but maybe I can help. The two packages I got today were delivered by Amazon and not one of the carriers. For each one I got a delivery notification yesterday with a subject:

Your Amazon.com order #xxxx has shipped

Then the first line of text :

Hi Edward, your package will arrive: Wednesday, July 22

When each package arrived today (separately) I got another email after each was delivered with the subject:

Delivered: Your Amazon.com order #xxxx

With text:

Hi Edward, Your package has been delivered.

They ask for feedback on the delivery and include a photo of the package left by the front door. They state:

Track your next shipment with Alexa, turn on delivery notification.

The first package arrived at 1:30 and the second at 3:14. I just took a snippet of the the card which at 10:36 shows this:
packages

If the packages are delivered by UPS, USPS, or FedEx, I don’t get a delivery notification from Amazon. But the fact that I got two delivery notices today, implies you can turn them on and they should be looked for to change them from in transit to delivered. Included in both In transit amounts and to the total deliveries if you find delivery notification.

641

I’ll see what I can do to add more robustness to the Amazon sensors. :slight_smile:

642

I really like what you both have done, and please don’t consider my posts as complaints. I was a programmer many moons ago and understand requirement creep. Since I get packages regularly, I will keep notes on notices and provide what I can should you need it.