iRobot Binding floods logs - Roomba i4

Add-ons Bindings
1

Hi,

when using the iRobot binding with my i4, the logs get flooded like this:

2026-01-03 07:52:25.028 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

2026-01-03 07:52:35.028 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.188.62'. Next attempt in 10000ms

2026-01-03 07:52:35.028 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

2026-01-03 07:52:45.029 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.188.62'. Next attempt in 10000ms

2026-01-03 07:52:45.029 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

2026-01-03 07:52:55.029 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.188.62'. Next attempt in 10000ms

2026-01-03 07:52:55.029 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

2026-01-03 07:53:05.029 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.188.62'. Next attempt in 10000ms

2026-01-03 07:53:05.030 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

2026-01-03 07:53:15.030 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '192.168.188.62'. Next attempt in 10000ms

2026-01-03 07:53:15.030 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.188.62' with clientid 6F37F749429B4D5481F649CE788ABD8E

However, the Thing appears online and I can also communicate with it. I.e. OpenHAB let’s me start cleaning it. So, the “password handshake” has successfully been done.

Yet, the messages appear. It happens sporadically. When I am disabling and enabling the thing again, the messages do not appear. After some hours it starts again.

Any idea?

2

Bindings don’t log like this without reason. Something is causing the connection to your MQTT broker at 192.168.188.62 to get lost. Then the binding tries every ten seconds to reestablish the connection.

Some debug level logging might show more information.

It might be the case that it is successful in reconnecting but only briefly. Just long enough to exchange a few messages.

Do you have any other MQTT Things connected to this broker? How are they behaving, in particular the MQTT Broker Thing?

Do you use a unique userid in the MQTT connection to the broker for both Things? When you try to establish more than one connection to a broker with the same userID it kicks out the previous connection.

3

The 62 IP address is the Roomba’s built-in MQTT server. While writing this I checked the Binding’s description again and here is what it says about known problems :melting_face::

Sometimes during intensive testing Roomba just stopped communicating over the local connection. If this happens, try rebooting it. On my robot it’s done by holding “Clean” button for about 10 seconds until all the LEDs come on. Release the button and the reboot tone will be played. It looks like there are some bugs in the firmware.

I think this the “solution”. -_-