Mqtt Socket Error

Configuration
1

Hi

I was hoping that someone could help

I continuously get the below errors
1583483125: Socket error on client <unknown>, disconnecting.
1583483140: New connection from 192.168.1.4 on port 1883.
1583483140: Socket error on client <unknown>, disconnecting.
1583483155: New connection from 192.168.1.4 on port 1883.
1583483155: Socket error on client <unknown>, disconnecting.
1583483170: New connection from 192.168.1.4 on port 1883.
1583483170: Socket error on client <unknown>, disconnecting.

That ip is my haas installation.
All MQTT devices are no problem?

2

With frequent disconnections it is useful to check whether you have used the same client name on different devices, eg in your HASSIO client and in another device.

3

Where do I see the hassio client id

4

I restarted the add-on and followed this in the log.
Initially Haas makes a connection and the id is random, I do not think that is the issue.
Anyone got an idea as to why it keeps disconnecting?

1583738597: New client connected from 192.168.1.4 as auto-2D1982FE-4A07-3ACE-8DC7-6B92D7031053 (p2, c1, k60, u'mqttuser').
1583738606: New connection from 192.168.1.4 on port 1883.
1583738606: Socket error on client <unknown>, disconnecting.
1583738621: New connection from 192.168.1.4 on port 1883.
1583738621: Socket error on client <unknown>, disconnecting.
1583738636: New connection from 192.168.1.4 on port 1883.
1583738636: Socket error on client <unknown>, disconnecting.
6

I’m having the same problem as you, i wonder if you found a solution?

7

any news about it? I have the same issue during connecting APPDAEMON to my MQTT broker. (I use hassio i.e. dockers)

8

On my side this was bad cofiguration that does the problems with users and broken MQTT.
If anybody uses auth_providers , must be added -type: homeassistant .

homeassistant:
  auth_providers:
    - type: homeassistant

What is the reason that this is not done automatically in code behind and must be done manually?