Weird vacuum behaviour when internet access blocked #1994
Replies: 2 comments 1 reply
-
For additional context, I've also attached my
|
Beta Was this translation helpful? Give feedback.
-
Vacuums rely on the cloud for mapping, so the device is likely considering it a major problem for the internet to be inaccessible, or perhaps overflowing some buffer for outgoing messages. Looking at your full symptoms, it appears to be dropping the connection, then when the reconnection occurs it is pausing. Do you have the protocol version set? The attempts at connecting using the wrong protocol may be what is causing the pausing if it is set to Auto. |
Beta Was this translation helpful? Give feedback.
-
Hi, first of all thanks for the excellent integration. I currently have 14 devices running through Tuya-Local and it's been great!
I recently purchased a Lefant M1 vacuum cleaner and created a YAML file to get it into Tuya-Local (after working through this discussion I will create a PR to add support). Initially I allowed my vacuum cleaner access to the internet to ensure I could debug any issues easily and it worked perfectly in Tuya-Local.
However, it's my standard practice to isolate smart home devices from the internet (which is actually why I'm using Tuya-Local), so configured my router to block the vacuum's connection to the internet (and note I block local DNS too as per the note on the README).
Weirdly after internet isolation, the vacuum still connects to Tuya-Local and is controllable, but pauses whatever action you've given it approximately 1min after you start it. For example, if I start a clean, the vacuum will begin cleaning but then halt after 1min and similarly with the"Return to Dock" command. I initially thought the vacuum itself was doing this (due to no internet connectivity), but it appears to be the integration, because if I start a command and immediately disable the integration, the vacuum continues to operate with no issues. As soon as I start the integration again, it pauses it's current action.
I grabbed the debug logs when this was occurring (note I've purely filtered for the vacuum here):
You can see from the logs that it gets a couple of errors which might be contributing to the issue:
And at some point it seemingly just goes into standby mode even though I haven't initiated this myself.
My question is, has anyone else experienced a similar issue? Is there any way around this?
Beta Was this translation helpful? Give feedback.
All reactions