MQTT Client <unknown>

Configuration
1

My mosquitto logs are flooded with disconnection messages like this

2023-09-05 07:45:40: New connection from 172.30.32.1:48815 on port 1883.
2023-09-05 07:45:40: New client connected from 172.30.32.1:48815 as hass23 (p5, c0, k60, u'homeassistant').
2023-09-05 07:46:49: New connection from 172.30.32.2:50794 on port 1883.
2023-09-05 07:46:49: Client <unknown> closed its connection.
2023-09-05 07:48:49: New connection from 172.30.32.2:44260 on port 1883.
2023-09-05 07:48:49: Client <unknown> closed its connection.
2023-09-05 07:50:49: New connection from 172.30.32.2:49130 on port 1883.
2023-09-05 07:50:49: Client <unknown> closed its connection.

I’m assuming this is not core. So what is this? How to track this ip?

2

It is HA Supervisor checking if the MQTT Add-on is still alive. Nothing to worry about.

5 Likes
3

I was debugging io.adafruit broker bridge disconnections every 5s. Solution was to set clientid option. That’s why this “unknown” client grabbed my attention. Nothing to worry about but this is not how supervisor should check broker alive, right?

4

Thanks, I also recognized this, but I didn’t know the subnet of that ip address.

Thanks again

5

I had same problem, this thread helped me figure out it was the Watchdog. Every two minutes I had this same ip hit. Once disabled the Watchdog, logs stopped. Re-enabled Watchdog, logs started with this again. I feel better now.

2 Likes
6

This was driving me crazy when debugging some stuff. Glad to hear it’s just the watchdog, also got 2 minute increments.

7

Why can’t this be a more meaningful message?

3 Likes