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

Development
1004

That maybe my changes, let me review.

1005

I’m stuck in a similar problem. In response to all my entities being unavailable, I remove M&P and then am now attempting to re-deploy. System is running b5. No matter which set of options I’m choosing I get the “User input malformed”. Checking the MP4 option (suggested in response to the post quoted above) doesn’t change the outcome.

edit: while typing this up it appears that I’m not the only person facing this. Let me know if I can provide any more detail.

1006

As we were just discussing in the previous posts, it looks like the option to select which entities are available was inadvertently removed in the latest beta. @firstof9 is investigating.

1 Like
1007

b6 soon to fix this.

1 Like
1008

b6… the sensor list is back, but still getting malformed user input

image
image534×699 28.8 KB

1009

aha, if i entered an “Amazon forwarded email address” into the field, I was able to submit

1010

Same result here. Sensors are now available, but User Input Malformed prevents me from submitting.

1011

enter "" into the amazon forwarding part and it should work.

1012

even after re-configuring and restarting, the entities are still unavailable.

1013

Anything from the debug log?

1014

The debug log shows that it’s successfully getting the emails and parsing them, but I don’t see any data regarding setting the entities, or why they might be set to unavailable

1015

They’d go unavailable if the data coordinator is failing to update them.
That should be the only time.

1016

I just did a reload from the integrations page, then re-submitted the configuration, and they’re back! with the correct data it looks like! woot!

1 Like
1017

beta 6 all sensors gone. Have to go back to 2.2 release to get them back.

1018

Did you try the trick @Michael_Griffin did with the reload and re-submit?

1019

Just checking in, b6 is working OK for me and THANK YOU @firstof9 for the quick fix! That’s pretty incredible turnaround and I appreciate it.

1 Like
1020

Maybe we should all complain and have them add it back

Maybe they heard you because today I got an email with an embedded image. WTF Amazon, you wildly inconsistent…sigh…

1021

LOL guess i’ll take removing that code off my todo list then

Also part of the reason it’s not integrated into the “in transit” and “delivered” sensors.

1024

it never ends :frowning: I woke up this morning to unavailable sensors again. There was an error, so I guess that’s good? At least we can work the error.

image
image915×528 35.8 KB

1026

This line shows you’re requiring 15 digits for a FedEx tracking number, but the one I got today was only 12 digits. Maybe that’s causing the issue?

EDIT
I updated that line on my local installation from "\\d{15,34}" to "\\d{12,34}' and the sensors are back available

1 Like