Why does hassio supervisor keep connecting to the mqtt broker addon?

1 
2023-10-04 19:26:03: New connection from 172.30.32.2:36972 on port 1883.
2023-10-04 19:26:03: Client <unknown> closed its connection.
2023-10-04 19:28:03: New connection from 172.30.32.2:41456 on port 1883.
2023-10-04 19:28:03: Client <unknown> closed its connection.
2023-10-04 19:30:03: New connection from 172.30.32.2:38920 on port 1883.
2023-10-04 19:30:03: Client <unknown> closed its connection.

And the list goes on.

Looking this up:

for id in $(docker ps | awk '{print $1}'); do echo $id; docker inspect $id | grep IPAddress; done

I found the following container:

image
image822×72 8.78 KB

Why is it doing this? Can I configure it to use mqtts somehow, and actually stay connected if it really needs to?

2

Supervisor checks if the mqtt add-on is still alive. I don’t think you can configure it.

1 Like
3

IMG_0878
IMG_08781229×1017 144 KB

I would not recommend turning it off though.

1 Like
4

Ahh, the healthcheck watchdog, that’s it.

Okay, that makes sense, just wish there was a way for it to check without spamming the logs.