Supervisor installation (6.01) of mosquitto

I installed 6.01 recently and apart from the removal of anonymous logins (why!?) it doesn’t autodiscover and also when I add the broker integration it installs under the user ‘homeassistant’ which in the documentation it says this login shouldn’t be used.

If I remove this, create a new user hamqtt/hamqtt and then add this login to the integration, the old instance is still running and still using the homassistant login.

Is MQTT broken until the next update? Installing mosquitto on a PI is a necessary pain. Have I missed something? so19 0/1 makes no difference.

When a tasmota device autodiscovers it doesn’t work, and then mqtt goes offline for 60 secs. Hardware absolutely fine (lenovo i3 4gb 120ssd)

Couldn’t demonstrate this to a potential customer and don’t want to install two machines due to ha mqtt being borked.

The homeassistant supervisor is getting so close to being brilliant, then it feels like nobody tested a fundamental building block.

Supervisor log below. I have two tasmota factory reset relays - mqtt user added and correct, ssl off, and you can see it connects, recognises the name, then later it calls the same device ‘unknown’ - This supervisor version of MQTT should be removed, or two versions installable - an original, un-fettled version and this one.

g.
1628885597: New connection from 10.0.0.128 on port 1883.
1628885597: New client connected from 10.0.0.128 as DVES_FE905A (p2, c1, k30).
1628885650: New connection from 10.0.0.141 on port 1883.
401: Unauthorized1628885650: Socket error on client , disconnecting.
1628885657: New connection from 10.0.0.141 on port 1883.
1628885657: Socket error on client , disconnecting.
1628885668: New connection from 10.0.0.141 on port 1883.
1628885668: Socket error on client , disconnecting.
1628885681: New connection from 10.0.0.141 on port 1883.
{“result”: “ok”, “data”: {}}1628885682: New client connected from 10.0.0.141 as DVES_FDDA3F (p2, c1, k30, u’hamqtt’).
1628885787: Client DVES_FDDA3F has exceeded timeout, disconnecting.
1628885803: Client DVES_FE905A has exceeded timeout, disconnecting.
1628885907: New connection from 10.0.0.141 on port 1883.
1628885907: New client connected from 10.0.0.141 as DVES_FDDA3F (p2, c1, k30, u’hamqtt’).
1628885963: New connection from 10.0.0.128 on port 1883.
1628885963: New client connected from 10.0.0.128 as DVES_FE905A (p2, c1, k30).
1628885996: Socket error on client DVES_FE905A, disconnecting.
1628886002: New connection from 10.0.0.128 on port 1883.
1628886002: Socket error on client , disconnecting.
1628886013: New connection from 10.0.0.128 on port 1883.
1628886013: Socket error on client , disconnecting.
1628886034: New connection from 10.0.0.128 on port 1883.
1628886034: Socket error on client , disconnecting.
1628886065: New connection from 10.0.0.128 on port 1883.
1628886065: Socket error on client , disconnecting.
1628886106: New connection from 10.0.0.128 on port 1883.
1628886106: Socket error on client , disconnecting.
1628886157: New connection from 10.0.0.128 on port 1883.
1628886157: Socket error on client , disconnecting.
1628886218: New connection from 10.0.0.128 on port 1883.
1628886218: Socket error on client , disconnecting.
1628886289: New connection from 10.0.0.128 on port 1883.
1628886289: Socket error on client , disconnecting.
1628886370: New connection from 10.0.0.128 on port 1883.
1628886370: Socket error on client , disconnecting.
1628886461: New connection from 10.0.0.128 on port 1883.

Had to give up. Installed seperate HA/mosquitto on docker. mqtt broken via supervisor install.

Found this explanation: [Unknown client connecting to MQTT broker · Issue #51603 · home-assistant/core · GitHub ]