You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I have a problem I need some help with. I am experiencing a connection/disconnection cycle with a Valetudo 2023.01.0 instance with my Dreame L10 Pro.
Every 2 minutes, more or less, the vacuum is disconnected due to a timeout and after 2 minutes it is connected again.
I do not think this is a network problem, as I am able to access the vacuum's UI without any problem and send instructions to it with any computer on the network.
Here you can see a photo
the history log of the vacuum entity in my server. Note that the longer periods without connections in the chart are because of me restarting the add on to check if that would fix the problem.
I have also tried to reinstall the add-on and default config and it did not work.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Mosquitto broker
What is the version of the add-on?
6.2.1
Steps to reproduce the issue
Install Mosquitto Ad-On (default configuration)
Configure user for roomba
Fill MQTT connection details in Valetudo instance, connect.
...
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
2023-06-07 14:10:58: New connection from 192.168.20.20:36412 on port 1883.
2023-06-07 14:10:58: New client connected from 192.168.20.20:36412 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:10:59: New connection from 172.30.33.3:57822 on port 1883.
2023-06-07 14:10:59: New client connected from 172.30.33.3:57822 as mqttjs_0d03ed87 (p2, c1, k60, u'addons').
2023-06-07 14:11:02: New connection from 172.30.32.1:57563 on port 1883.
2023-06-07 14:11:02: New client connected from 172.30.32.1:57563 as 1A8ow1jl9SQwVkHHmZyohT (p5, c0, k120, u'mqtt').
2023-06-07 14:11:57: New connection from 172.30.32.2:54072 on port 1883.
2023-06-07 14:11:57: Client <unknown> closed its connection.
2023-06-07 14:13:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
2023-06-07 14:13:43: New connection from 192.168.20.20:36420 on port 1883.
2023-06-07 14:13:43: New client connected from 192.168.20.20:36420 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:13:57: New connection from 172.30.32.2:57980 on port 1883.
2023-06-07 14:13:57: Client <unknown> closed its connection.
2023-06-07 14:15:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
2023-06-07 14:15:17: New connection from 192.168.20.20:36424 on port 1883.
2023-06-07 14:15:17: New client connected from 192.168.20.20:36424 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:15:57: New connection from 172.30.32.2:55002 on port 1883.
2023-06-07 14:15:57: Client <unknown> closed its connection.
2023-06-07 14:17:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
2023-06-07 14:17:43: New connection from 192.168.20.20:36436 on port 1883.
2023-06-07 14:17:43: New client connected from 192.168.20.20:36436 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:17:57: New connection from 172.30.32.2:41280 on port 1883.
2023-06-07 14:17:57: Client <unknown> closed its connection.
2023-06-07 14:19:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
2023-06-07 14:19:17: New connection from 192.168.20.20:36440 on port 1883.
2023-06-07 14:19:17: New client connected from 192.168.20.20:36440 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:19:57: New connection from 172.30.32.2:58596 on port 1883.
2023-06-07 14:19:57: Client <unknown> closed its connection.
2023-06-07 14:21:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
2023-06-07 14:21:43: New connection from 192.168.20.20:36448 on port 1883.
2023-06-07 14:21:43: New client connected from 192.168.20.20:36448 as valetudo_CreativeKnowingChinchilla (p2, c0, k60, u'roomba').
2023-06-07 14:21:57: New connection from 172.30.32.2:40374 on port 1883.
2023-06-07 14:21:57: Client <unknown> closed its connection.
2023-06-07 14:23:16: Client valetudo_CreativeKnowingChinchilla has exceeded timeout, disconnecting.
Additional information
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
Hi!
I have a problem I need some help with. I am experiencing a connection/disconnection cycle with a Valetudo 2023.01.0 instance with my Dreame L10 Pro.
Every 2 minutes, more or less, the vacuum is disconnected due to a timeout and after 2 minutes it is connected again.
I do not think this is a network problem, as I am able to access the vacuum's UI without any problem and send instructions to it with any computer on the network.
Here you can see a photo
the history log of the vacuum entity in my server. Note that the longer periods without connections in the chart are because of me restarting the add on to check if that would fix the problem.
I have also tried to reinstall the add-on and default config and it did not work.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Mosquitto broker
What is the version of the add-on?
6.2.1
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: