Connection reset issues #61
Comments
|
@FuturamaPhill I've made another tweak and it's in 1.2.5 |
|
Tried deleting the integration and re downloading, Still getting below: |
|
This now genuinely seems like an issue communicating properly with the
vacuum. What model do you have?
…On Fri, 1 Mar 2024, 19:28 FuturamaPhill, ***@***.***> wrote:
@CodeFoodPixels <https://github.com/CodeFoodPixels>
Still getting below:
2024-03-01 19:25:54.482 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0xa, {'gwId': 'bf4b0ace39a5f9f09ajma7', 'devId': 'bf4b0ace39a5f9f09ajma7'}, 41684429, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:25:54.482 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:25:54.495 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:25:54.495 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:25:54.586 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:25:54.586 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:25:54.586 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:25:54.604 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:25:54.604 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:04.439 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:04.439 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:04.439 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:04.458 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:04.458 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:14.515 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:14.516 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:14.516 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:14.534 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:14.534 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:24.521 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:24.521 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:24.521 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:24.539 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:24.539 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:34.474 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:34.474 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:34.474 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:34.492 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:34.492 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:44.456 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:44.456 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:44.456 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:44.474 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:44.474 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:54.412 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:54.412 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0xa, {'gwId': 'bf4b0ace39a5f9f09ajma7', 'devId': 'bf4b0ace39a5f9f09ajma7'}, 41744429, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:54.413 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:54.426 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:54.426 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:54.517 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:26:54.517 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:26:54.518 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:26:54.538 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:26:54.538 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:27:04.480 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Processing queue. Current length: 1
2024-03-01 19:27:04.480 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Sending to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668): Message(0x9, b'', 0, <Device bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)>)
2024-03-01 19:27:04.480 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connecting to bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
2024-03-01 19:27:04.498 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Connection reset: [Errno 104] Connection reset by peer
2024-03-01 19:27:04.498 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi] Disconnected from bf4b0ace39a5f9f09ajma7 (192.168.0.144:6668)
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEPFVHFECUAQPBGVBP3X7DYWDJFVAVCNFSM6AAAAABECCURXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTG44TANZVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I have the 15C MAX. Just thought i'd test network connectivity and appears fine from my pc: |
|
Huh, I have the exact same vacuum without issue 🤔
A couple of ideas to try:
- turn the vacuum on and off with the switch
- delete and re-add the vacuum (not the integration)
…On Fri, 1 Mar 2024, 19:50 FuturamaPhill, ***@***.***> wrote:
I have the 15C MAX.
Just thought i'd test network connectivity and appears fine from my pc:
PS C:\> tnc 192.168.0.144 -port 6668
ComputerName : 192.168.0.144
RemoteAddress : 192.168.0.144
RemotePort : 6668
InterfaceAlias : WiFi
SourceAddress : 192.168.0.84
TcpTestSucceeded : True
PS C:\> ping homeassistant.local
Pinging homeassistant [192.168.0.245] with 32 bytes of data:
Reply from 192.168.0.245: bytes=32 time=1ms TTL=64
Reply from 192.168.0.245: bytes=32 time=3ms TTL=64
Reply from 192.168.0.245: bytes=32 time=3ms TTL=64
Reply from 192.168.0.245: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.0.245:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEPFVHEILSWLPVCAWVRM23YWDLZPAVCNFSM6AAAAABECCURXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTHAYTQMJSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Tried that already, power switch and I held down the button for 10sec+ to resetup the wifi, assume thats the deletion process unless i'm wrong? Tried power switch again just in case and still just getting : When I have the integration enabled it seems to cause issues with my zigbee2mqtt devices aswell causing them to go unknown every couple of minutes, this was when I was getting loads of connection resets though so not sure if it was just having an issue with the number of requests.
|
|
No, go to the integration page (https://my.home-assistant.io/redirect/integration/?domain=robovac), click the 3 dots next to your vacuum and click delete. Then re-add it. |
|
@CodeFoodPixels Ah right apologies already tried that a few times but did it again just now same results: |
|
@CodeFoodPixels saw there was an update so downloaded and attached logs below: |
|
I've added a little more logging if you could try again please? |
|
|
So I was able to replicate this by opening the eufy app on my phone before the integration started on HA, and I found this comment from someone on another project: clach04/python-tuya#2 (comment) Do you have anything else connecting to the vacuum when trying this? |
I do use the app to control the vac but its not open 24/7 so would imagine if it can only communicate to one device at a time it would eventually disconnect from phone and connect to HA, I haven't connected anything else to it. I have closed the app on my pixel (force stop), enabled the integration, deleted the existing instance of my 15c max and added it again and still getting below in logs: Is there anything else you can suggest, im guessing I need to use the app to setup the robovac to start with as the robovac wont know what wifi to connect to, would uninstalling the app make a difference ? I've also tried deleting my unifi integration that links into my WAP just in case it was causing a conflict but still the same issue |
|
Tried beta version to see if that made any difference but still getting below: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
home-assistant_2024-03-01T15-34-55.387Z.log
Originally posted by @FuturamaPhill in #57 (comment)
The text was updated successfully, but these errors were encountered: