Rebooting makes no difference. It’s still going strong - every minute for days now.
I briefly had my Roomba connected. Somehow, it wandered back to the other WiFi network and I cannot get it back on the automation network. That’s also retrying (every second) forever, but at least I understand what’s going on (although it’s also reporting “online” so who knows what’s going on, for sure).
I was setting up MQTT to start the Tuya adventure, but it’s a bit intimidating and I haven’t started, yet. I’ll try deleting the Roomba and the Bridge, rebooting, then re-adding the Bridge.
Something is starting a connection:
2022-02-25 22:19:02.955 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 7013ea02-0c89-4d7b-8266-f3c2703a1b49
There is no Thing that should be. This is going to be TMI, but I’ll trim the logs down as much as possible. The startup sequence in openhab.log
2022-02-25 22:18:58.773 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
The first Thing in event.log
2022-02-25 22:19:00.269 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0100:ecb5fa1de3aa:2' changed from INITIALIZING to ONLINE
Then a not-Thing back in openhab.log. I have no idea where this coming from. I haven’t tried to use Influx, yet, so I have no idea what might be wrong with its configuration.
2022-02-25 22:19:00.840 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'QueryablePersistenceService.query()' on 'org.openhab.persistence.influxdb.InfluxDBPersistenceService@51ac99': error parsing query: found .623, expected ; at line 1, char 47
Then the iRobot binding dumps tons of debug logs (from when I was trying to connect the Robot; I haven’t changed the binding back to info level). The end of it, still in openhab.log:
2022-02-25 22:19:01.410 [DEBUG] [nal.discovery.IRobotDiscoveryService] - bundle org.openhab.binding.irobot:3.2.0 (264)[org.openhab.binding.irobot.internal.discovery.IRobotDiscoveryService(309)] : Changed state from satisfied to active
2022-02-25 22:19:02.408 [DEBUG] [nal.discovery.IRobotDiscoveryService] - Starting broadcast for /10.247.246.255
2022-02-25 22:19:02.955 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 7013ea02-0c89-4d7b-8266-f3c2703a1b49
It could be the iRobot binding, but there a whole 500msec between those; lots could have happened. The binding has no configuration, that I can see. The description does say this " The binding interfaces to the robot directly without any need for a dedicated MQTT server." The word “dedicated” is a poor choice. Does that mean that there is one built into the binding and I don’t need an “external” MQTT server? Does that mean that I can share a non-dedicated external MQTT server with other things?
In events.log, the tplink binding comes up. In openhab.log the zwave controller starts (also in debug level) initializing, then in events.log it starts coming up. Then in openhab.log the MQTT issue starts:
2022-02-25 22:19:13.824 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '10.247.251.1'. Next attempt in 60000ms
2022-02-25 22:19:13.927 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 7013ea02-0c89-4d7b-8266-f3c2703a1b49
The obvious thing to do is Remove the iRobot binding and reboot again. No joy.
2022-02-25 22:40:36.782 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 6e514f56-bd36-4ab3-8b6e-47f2d2e0b16a
...
2022-02-25 22:40:47.538 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '10.247.251.1'. Next attempt in 60000ms
2022-02-25 22:40:47.599 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 6e514f56-bd36-4ab3-8b6e-47f2d2e0b16a
As long as I’m pulling this apart, I might as well yank the MQTT Binding out, too. The mosquitto process is still running. Rebooting… And the error is gone. On the bright side, mosquitto is back up.
Adding the binding back… Hmm… The Setting page has “System MQTT Broker” at the bottom, under “Other Services”; this is not a Thing. I didn’t notice if that was there before I restored the binding. Whacking it again. It’s gone and so is the System MQTT Broker. At the risk of destablization, I’m not rebooting, just adding it back. The “System MQTT Broker” is back. As are the errors:
2022-02-25 22:53:52.934 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 6fc79bde-3772-4c1a-bdbe-8483471b03a7
2022-02-25 22:54:03.330 [INFO ] [.reconnect.PeriodicReconnectStrategy] - Try to restore connection to '10.247.251.1'. Next attempt in 60000ms
2022-02-25 22:54:03.377 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '10.247.251.1' with clientid 6fc79bde-3772-4c1a-bdbe-8483471b03a7
This is definitely the MQTT binding. I don’t see anything on that System Broker page that looks wrong (it’s the same as documented, above). I suspect that Removing the binding did not erase the configuration, wherever that might be stored, because the Broker Port is set and I set it. It was blank the first time I looked at this page - long before I made this post.
Hope that helps.
