stale[bot]
commented
4 years ago 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.
I faced an issue with Hassio on Raspberry PI 3B+ After adding another tasmota device everything just blocked. In logs I got messages like
Devices were unable to connect to the MQTT server and became blocked. I spent 3 evenings trying to troubleshoot it. When I was restarting MQTT Service from inside of the docker container it was running OK. When restating a container from supervisor - I've got the same errors. When running supervisor on RPI and MQTT on Hassio from my VM it was working. As a result I understood that it is not related to tasmota at all. Even on clean Hassio installation it was failing.
Root cause of this issue was somehow related to performance. I had 10 users with 20 character length passwords. After adding the 11-Th user it started to fail. I reduced number of characters, it helped but started failing with 15-20 users.
I fixed it for me by using a password file like in this issue :
585
It makes sense to add some notes related to password file into documentation. Maybe there is a way to build a password file automatically once plugin is starting using the configuration parameters? Also it would be nice to have an option to have MQTT authentication only by disabling Hassio authentication plugin.