search

Brandawg93 / homebridge-fordpass

Control your Ford vehicle in HomeKit using Homebridge.
GNU General Public License v3.0
61 stars 15 forks source link

[Bug]: [FordPass] Status failed with error: ETIMEDOUT #197

Closed prezmc closed 1 year ago

prezmc commented 2 years ago

Describe the bug

Recently I have started to see this error: [FordPass] Status failed with error: ETIMEDOUT ...and its frequency is increasing.

I have attempted removing and re-adding my auth info (and verified the auth info with the ford pass app).

I am in the US region, and I have turned off auto refresh at this point. Nothing seems to help resolve. Not sure if this is a Ford service issue, or an API limiting function, or what.

Debug Output

[8/10/2022, 3:33:26 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 3:47:20 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 4:00:20 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 4:12:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 4:26:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 4:39:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 4:52:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 5:04:20 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 5:16:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 5:30:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 5:43:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 7:51:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 8:25:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 8:39:26 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 8:50:36 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 8:50:36 AM] [FordPass] Cannot get information for 2020 F-150 lock [8/10/2022, 9:02:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 9:25:21 AM] [FordPass] Status failed with error: ETIMEDOUT [8/10/2022, 9:38:21 AM] [FordPass] Status failed with error: ETIMEDOUT

Steps to reproduce

  1. Issue happens on its own. No known trigger on my end that initiates it.

Device Type

Docker Container on Ubuntu Server

iOS Version

n/a

Bug Persistence

Consistently

Last Working Version

No response

tornenen commented 2 years ago

Same error for me. Based in EU.

jcleek commented 2 years ago

Same for me

tornenen commented 2 years ago

Had to disable the Plugin cause of this. Lock was jumping from closed to open to closed to open...

prezmc commented 2 years ago

Are you sure it's actually unlocking? I get the same messages from HomeKit but I go out and look...and it's locked. Either way, it's unsettling.

tornenen commented 2 years ago

Yeah its not unlocking the Vehicle. But its annoying cause ive Push notifications enabled for it.

Brandawg93 commented 2 years ago

I've published a new test version (v1.8.1-test.0) that should fix this. Let me know if so, and I'll submit the new version.

jcleek commented 2 years ago

n00b question: How do we update without it being published?

jcleek commented 2 years ago

I got it. I will let you know if it resolves the issue.

prezmc commented 2 years ago

Same - v1.8.1-test.0 installed

jcleek commented 2 years ago

At 1 am I got a notification that my truck was locked. You can trust me, I wasn't awake to lock it :-\

prezmc commented 2 years ago

@Brandawg93 The error messages seem to be gone, but as @jcleek noted, there is still some weird behavior with the notifications. I just used HomeKit to lock my truck, it said it locked. a few min later, it said it was unlocked.

slowpc1 commented 2 years ago

Yep , Was reaching this as well and noticing it. Going to disable for now as the toast notification on apple tv gets a bit to "busy"

Brandawg93 commented 2 years ago

Did this just start happening randomly? It could be the way Ford implements their APIs.

When you lock your vehicle, the plugin knows that you just tried to lock it, so it sets the vehicle to "locked". Then it sends the request to Ford that it was locked. (It only sets the "locked" state upon successful request.) Once Ford receives it, they should update their cached values, but sometimes this doesn't happen. A minute later, the plugin requests the cached values which are now stale, and it thinks the vehicle is unlocked again.

As for @jcleek's issue, I'm not sure if a random notification is a cache issue or plugin issue. I'm looking into that.

I am going to go ahead and publish what I have because I think it will at least help a bit with the notification spam.

prezmc commented 2 years ago

It has been random. What you're saying makes sense based on the symptoms we saw. Having said that, I have not seen the weird behavior reoccur recently. Maybe Ford was having an issues as well. I have done several tests of locking, unlocking, checking status, starting, etc. All have worked fine. I think you're test code works.

On a side note - is it possible to pull more data, such as fuel levels, oil status, etc?

prezmc commented 2 years ago

Just an update, there are still some periodic errors coming through: [8/25/2022, 2:21:15 AM] [FordPass] Cannot get information for Ford F-150 lock [8/25/2022, 3:44:38 PM] [FordPass] Cannot get information for Ford F-150 lock

Brandawg93 commented 1 year ago

I think Ford may be testing rate limiting their API. Every so often I get the same errors, but I don't have notifications turned on for my vehicle.

prezmc commented 1 year ago

Yea, that or service issues. The errors are definitely sporadic. However, all my my requests to Lock or Start seem to work. I think it's safe to close the issue, and just monitor it.