Feature Request: normalize event times in raw shipment data

[pkolbus]

Thanks for this integration -- it works really well.
In sensor.parcel_raw_shipment_data, the deliveries.event[].date values are strings in different formats per carrier. For example:

• amzlus: Tuesday, May 13 1:31 PM (or "Wednesday, April 30 ")
• fedex: May 13, 2025 13:31
• ups: 05.13.2025 13:31
• usps: Tuesday, May 13 1:31 pm

It would be helpful for the sensor to provide these as datetime when possible for a consistent presentation. dateutil.parser.parse() can handle at least the above formats, but unfortunately this isn't exposed in HA templates.

I'd be happy to work on a PR for this, but not sure about the following aspects:

• whether this should be an additional event attribute, or if it can replace the existing date
• what formats are used by the other 320 carriers

[PineappleEmperor]

Hi 👋🏻

We're already doing this in the active parcel code, I think the only reason we didn't include it in the raw is so that it's entirely raw.

As I see it, I think it'd probably make more sense to have another (default disabled) raw sensor that attempts to clean up the data, I was considering having a go at some of the various statuses which are also anything but consistent..

Saying that, adding an additional field to the JSON shouldn't break anything if people are using it.. though may show up unexpectedly if people are just printing it.

Feel free to give it a go! Definitely nab the code from the active shipment as a starting point.

[pkolbus]

Thanks for the tips. Agree a separate sensor would make the most sense. I'll give it a go, hopefully this month, when I find a bit of spare time.

[nagtegaal]

Thanks for the tips. Agree a separate sensor would make the most sense. I'll give it a go, hopefully this month, when I find a bit of spare time.

It would be nice to see the code of the extra sensor here, so others can benefit from it either.
Thanks in advance...