Started getting some errors in the logs after the last update to v 1.2.0

Question

Started getting some errors in the logs after the last update to v 1.2.0

Closed this issue 10 months ago · 6 comments

xhemp commented 10 months ago

After the last update to v.1.2.0, I started getting this error:

https://logpaste.com/clYx4EDm

I didn't chage anything in the configuratiion.
Reverted to v1.1.1 and everything is back to normal.

Answer 1 · 2024-02-26T14:16:59.000Z

Same here.

Answer 2 · 2024-02-26T15:36:59.000Z

This should be fixed with 1.2.1

…

On Mon, 26 Feb 2024, 14:17 dinan5, ***@***.***> wrote: Same here. — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEPFVDGIUEXOKBDLZHPQ3DYVSKOPAVCNFSM6AAAAABDZD5GTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGI2TCMBXGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Answer 3 · 2024-02-26T15:43:08.000Z

Confirmed, @CodeFoodPixels , thanks for taking a look!

Answer 4 · 2024-02-26T17:25:41.000Z

Reopened this one, I a not sure if it's related or not but it works fine after a reboot but after some time, I've been getting:

2024-02-26 17:19:49.313 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 1. Reason: Timed out waiting for response to sequence number 15215076
2024-02-26 17:20:10.504 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 2. Reason: Timed out waiting for response to sequence number 15235078
2024-02-26 17:20:29.302 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 3. Reason: Timed out waiting for response to sequence number 15255079
2024-02-26 17:20:49.305 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 4. Reason: Timed out waiting for response to sequence number 15275081
2024-02-26 17:21:09.306 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 5. Reason: Timed out waiting for response to sequence number 15295081

And the vacuum status is Error, checked the Eufy app and the vacuum is just fine so not sure what's going on.

Then it says the vacuum is fine after some time and it starts the count again:

2024-02-26 17:23:51.913 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 1. Reason: Timed out waiting for response to sequence number 15456035
2024-02-26 17:24:10.260 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 2. Reason: Timed out waiting for response to sequence number 15476036
2024-02-26 17:24:30.260 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 3. Reason: Timed out waiting for response to sequence number 15496037
If you need me to try and send any further logs, please, let me know.

Let me know if you need any further logs on this.

Answer 5 · 2024-02-26T18:11:43.000Z

It's not related, and it's not a bug. It means that it failed to reach the vacuum for whatever reason. Could be down to the vacuum not responding, could be that your network is busy and the packet is getting lost

…

On Mon, 26 Feb 2024, 17:25 xhemp, ***@***.***> wrote: Reopened this one, I a not sure if it's related or not but it works fine after a reboot but after some time, I've been getting: 2024-02-26 17:19:49.313 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 1. Reason: Timed out waiting for response to sequence number 15215076 2024-02-26 17:20:10.504 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 2. Reason: Timed out waiting for response to sequence number 15235078 2024-02-26 17:20:29.302 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 3. Reason: Timed out waiting for response to sequence number 15255079 2024-02-26 17:20:49.305 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 4. Reason: Timed out waiting for response to sequence number 15275081 2024-02-26 17:21:09.306 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 5. Reason: Timed out waiting for response to sequence number 15295081 And the vacuum status is Error, checked the Eufy app and the vacuum is just fine so not sure what's going on. Then it says the vacuum is fine after some time and it starts the count again: 2024-02-26 17:23:51.913 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 1. Reason: Timed out waiting for response to sequence number 15456035 2024-02-26 17:24:10.260 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 2. Reason: Timed out waiting for response to sequence number 15476036 2024-02-26 17:24:30.260 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 3. Reason: Timed out waiting for response to sequence number 15496037 If you need me to try and send any further logs, please, let me know. Let me know if you need any further logs on this. — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEPFVBTGNQUQ24UREE4X5DYVTASDAVCNFSM6AAAAABDZD5GTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUG4YDINJXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 6 · 2024-02-26T18:14:21.000Z

I was just pinging the vacuum and didn't lose any packet but it's fine, thanks for taking a look!
I will get 1.1.1 again on it as it was working great.