A few questions, no doubt easy to answer but I’m still trying to wrap my head around this stuff…
I’ll also add that for all the documentation, mqtt hasn’t been easy to understand until I watched a YT where someone actually showed setting up the listening & publishing examples - once I saw that, it cleared a lot up for me… I’m stumped why something that simple isn’t clearly documented.
Anyway…
My error logs show:
1650915284: New connection from 172.30.32.2 on port 1883.
1650915284: Socket error on client <unknown>, disconnecting.
…over and over and over with no time stamp so I’m not sure whether this is 75 years worth of logs or just the last 10 seconds… No idea!
There’s only one exception to the above recurring information and that is this:
1650914564: New connection from 172.30.32.2 on port 1883.
1650914564: Socket error on client <unknown>, disconnecting.
1650914639: Socket error on client 1uNx6w4Q8m7Q7pFSIOTTYE, disconnecting.
1650914660: New connection from 172.30.32.1 on port 1883.
{"result": "ok", "data": {}}1650914661: New client connected from 172.30.32.1 as 5u1bjcWv4RpJHWxJkizkPy (p2, c1, k60, u'moz').
1650914684: New connection from 172.30.32.2 on port 1883.
1650914684: Socket error on client <unknown>, disconnecting.
1650914804: New connection from 172.30.32.2 on port 1883.
1650914804: Socket error on client <unknown>, disconnecting.
Now, The quoted IP seems to be generated by my Synology VM’s networking device…
I did not pretend to get the truth ! I think it’s a normal operation (and BTW I have the exact same here !). You could probably disable the watchdog to be 100% sure. It’s just a guess based on IP resolution wich points to supervisor and watchdog option that NEEDS to actively check the opened MQTT broker with a kind of “ping”.
Yes, I genuinely appreciate your input though as once I’d read your response, it just made perfect sense and I’m fairly confident you’re bang on with your line of thought. Your further exploration of it being a “ping” just reinforces the likelihood of it being correct as that is roughly what my thinking was too once I’d read your answer.
I’m still stumped though why it’s classed as an error… that is misleading and worrying to n00bs like myself who are lacking in confidence in their ability with HAOS.
But once more, I thank you kindly for your thoughts - I feel a lot happier now knowing it isn’t really an error at all and is seemingly normal operation logging rather than an actual error.
