New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fed Ex sensor broken #12990
Comments
I think this error shows up when you are being limited by fedex, I wouldnt be surprised if it goes away in a couple hours. My fedex sensor works fine but sometimes i see an error. |
I get this occasionally as well. We need to increase the interval I think. |
I turned the sensor off for 2 days and just re-enabled. It still fails with the same error. So I don't think its a case of being limited by calls to their service. I tried also deleting the .pickle file and restarting and that didn't do it either. I'm now on 0.65.1. Will try 0.65.2 once the docker file finishes building. |
Error still persist in 0.65.3, even after being disabled for a week.
|
Thats a completely different error than the original bug. |
@dshokouhi Should it be posted as a new issue? |
@Coolie1101 definitely |
Sure thing. |
Closing as a new issue is present. |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
**Home Assistant release (
hass --version
): 0.64.3Python release (
python3 --version
): 3.6.3+Component/platform: FedEx Sensor
Description of problem:
Cannot log in. I can on the site just fine. Just not with HA
Expected:
To log in
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
Was working fine about 15 hours ago.
The text was updated successfully, but these errors were encountered: