Spam at log. Messages like: New connection from 172.30.32.2

[KitHubek]

Describe the issue you are experiencing

At log many many logs ad below:

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.1.2

Steps to reproduce the issue

1. Go to mosquito logs

...

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?

1661770800: New connection from 172.30.32.2:54258 on port 1883.
1661770800: Client <unknown> closed its connection.
1661770920: New connection from 172.30.32.2:54260 on port 1883.
1661770920: Client <unknown> closed its connection.
1661771040: New connection from 172.30.32.2:54262 on port 1883.
1661771040: Client <unknown> closed its connection.
1661771160: New connection from 172.30.32.2:54264 on port 1883.
1661771160: Client <unknown> closed its connection.
1661771280: New connection from 172.30.32.2:54266 on port 1883.
1661771280: Client <unknown> closed its connection.
1661771400: New connection from 172.30.32.2:54268 on port 1883.
1661771400: Client <unknown> closed its connection.
1661771520: New connection from 172.30.32.2:54270 on port 1883.
1661771520: Client <unknown> closed its connection.
1661771640: New connection from 172.30.32.2:54272 on port 1883.
1661771640: Client <unknown> closed its connection.
1661771760: New connection from 172.30.32.2:54274 on port 1883.
1661771760: Client <unknown> closed its connection.
1661771880: New connection from 172.30.32.2:54276 on port 1883.
1661771880: Client <unknown> closed its connection.
1661772000: New connection from 172.30.32.2:54278 on port 1883.
1661772000: Client <unknown> closed its connection.
1661772120: New connection from 172.30.32.2:54280 on port 1883.
1661772120: Client <unknown> closed its connection.
1661772240: New connection from 172.30.32.2:54282 on port 1883.
1661772240: Client <unknown> closed its connection.
1661772360: New connection from 172.30.32.2:54284 on port 1883.
1661772360: Client <unknown> closed its connection.
1661772480: New connection from 172.30.32.2:54286 on port 1883.
1661772480: Client <unknown> closed its connection.

Additional information

No response

[martijntinus]

Had the same issue, devices cant connect to the mqtt server ether. After two or three restarts it fixed itself.

[mdegat01]

If you disable watchdog does it go away?

[klausdm]

Had same issue after installing 6.1.3. Rebooted twice.... came back to normal operation.

[hdprice]

I've got the same problem, ring-mqtt can't connect, it's logs say it's not authorized. Triple checked all configs, everything looks good and this was working for over 2 years before the update last week. Is there any way to roll back the update?

[almirus]

workaround - Simply edited the file in the Mosquitto Configuration page, using the 3 dots at the top and choosing edit in yaml, delete last space and save

[madAndroid]

Experiencing the same issue - any Home Assistant restart causes the broker to fail.. restarting the broker via the add-on in supervisor, "fixes" the problem, until the next HA restart.

[jkasten80]

Same for me

[SCratORS]

Same for me

[jkasten80]

Any news here? The problem is still there

[SCratORS]

This problem is solved by disabling watchdog

[ChristophCaina]

This problem is solved by disabling watchdog

I wouldn't call it "solving" - when you need to disable a functionallity. It is more a workaround in my eyes...

[github-actions[bot]]

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.

[roblatour]

bad bot - this issue is not resolved - problem remains notwithstanding work arounds

[KitHubek]

problem still exsist

[ngosang]

Problem still exists in 2023.12.1

[vbueschken]

Problem still exists in 2023.12.3

[Ferrari2]

Still exists at 30.1.2024 :-)

[tokken1]

Problem besteht immer noch am 7.02.2024

[starsoccer]

Still an issue. Is there a reason we cant either ignore connection and not log them? Or alternatively have a status topic that just is updated every 2 minutes?

[Seylox]

So apparently this is not an issue but rather an (annoying) side effect of the hass.io supervisor checking if the add-on is still responding. See also @frenck's response here: https://github.com/home-assistant/core/issues/51603#issuecomment-856523532

[starsoccer]

So apparently this is not an issue but rather an (annoying) side effect of the hass.io supervisor checking if the add-on is still responding. See also @frenck's response here: home-assistant/core#51603 (comment)

Ive seen that thread and while I understand this is a semi intended effect, the effect is still an annoyance to many. I think there are alternative options to check for uptime that dont require a log entry.

Or alternatively just simply implementing a filter to not show these logs, or better yet not log this in the first place if its coming from the supervisor would also be a decent solution