New connection from 172.30.32.2:46658 on port 1883

Configuration Zigbee
1

Anybody know why I am seeing this below in the MQTT logs

2026-02-11 07:22:33: Client closed its connection.
2026-02-11 07:24:33: New connection from 172.30.32.2:59894 on port 1883.
2026-02-11 07:24:33: Client closed its connection.
2026-02-11 07:26:07: Saving in-memory database to /data//mosquitto.db.
2026-02-11 07:26:33: New connection from 172.30.32.2:46658 on port 1883.
2026-02-11 07:26:33: Client closed its connection.
2026-02-11 07:28:33: New connection from 172.30.32.2:40416 on port 1883.

2

Home Assistant or some other app/integration is having a connection problem with your MQTT.
Check the passwords are right and logins.

3

Hi. Thanks for the reply
I managed to chasd down the problem. Turns oug to be a linknlink ir_eRemote
After delete and re-install seems to be ok now (during the re install it had an update)
.
Problem started again so I changed the IP address of HomeAssistant so that any rouge mqtt settings nolonger accessed the server
Now seems to be OK. not sure what it is causing these bad connections

4

The problem has re-surfaced and now the log is filling up with the same message
Every 2 minutes something is trying to access the MQTT and closing with an unknown connection.
I re-installed MQTT broker and changed the ip address of the homeassistant server.
Checked the access to MQTT and I dont have any outside connection now as it is clean install

This only happened recently and not sure which updates caused it
If this has no meaning then how to stop it filling up the logs

2026-02-14 18:33:33: New connection from 172.30.32.2:56992 on port 1883.
2026-02-14 18:33:33: Client closed its connection.
2026-02-14 18:35:33: New connection from 172.30.32.2:40200 on port 1883.
2026-02-14 18:35:33: Client closed its connection.
2026-02-14 18:37:33: New connection from 172.30.32.2:33444 on port 1883.
2026-02-14 18:37:33: Client closed its connection.
2026-02-14 18:39:33: New connection from 172.30.32.2:52066 on port 1883.
2026-02-14 18:39:33: Client closed its connection.
2026-02-14 18:41:33: New connection from 172.30.32.2:59562 on port 1883.
2026-02-14 18:41:33: Client closed its connection.
2026-02-14 18:43:33: New connection from 172.30.32.2:38574 on port 1883.

5

That’s no problem. It’s a heartbeat message between HA & Mqtt to verify the connection is still up. That IP you’re seeing is the internal docker IP. Again, absolutely normal.

Not sure why you’re saying this. The 2 minute heartbeat connection messages have been there for years.

Unless you’re actually seeing a problem & can absolutely confirm it’s caused by those messages, you should ignore them.

6

Hi shadowfist
I am seeing them for the first time,
as i am trying to install a new zigbee2mqtt (sonoff dongle max) with no sucess so started checking the logs
Thanks iwill ignord them. Is there any way to have them ignored by the logs to help cleanup and makeveasier to see actual problems without scrolling through days of this useless data

7

As far as I know, no. You could set the log level for Mqtt to Error, but then you’d lose the ability to see when your other devices are connecting without issues.

If you’re troubleshooting issues with Z2M, why not look at the Z2M logs directly? They’ll contain all the info you need, including Mqtt messages being sent

8

The thing that was worrying me was that it shows
“: Client unknown closed its connection.”

2026-02-20 12:27:09: New connection from 172.30.32.2:47070 on port 1883.
2026-02-20 12:27:09: Client <unknown> closed its connection.
2026-02-20 12:29:09: New connection from 172.30.32.2:32910 on port 1883.
2026-02-20 12:29:09: Client <unknown> closed its connection.
2026-02-20 12:31:09: New connection from 172.30.32.2:56958 on port 1883.

9

Yes, it’s done checking, so it disconnects until it needs to check in 2 minutes later. Nothing to worry about at all

10

Hi. Yes
I am ignoring these but would have expected homeassistant to give better statement when logging these and an ability to ignore none errors
But thanks all for the info

11

If it’s bothering you so much, there is a way to hide info level logs. Fair warning, I haven’t tried this myself since it doesn’t bother me - this is all based on searching & reading the official mosquitto docs:

  • Stop the Mosquitto Addon.
  • Enable the customize option in the MQTT addon config.
  • Go to the /share folder using Samba, SSH or whatever you’re comfortable with.
  • Create a folder in there named mosquitto. Inside that folder, create a file named mosquitto.conf with the specific log levels you want to monitor. There’s an example here if you want.
  • Start the Mosquitto Addon.