I can see it is working correctly from the logs in HASS.IO but the web client will not connect. I have the broker running on 1883, with anonymous enabled (while testing). Using the web client, I add the IP address of the server, the port 1833 and a client name (e.g. test) but when I click ‘connect’ nothing happens.
I’ve also tried it with a username and password on the client settings and this also does not work - but I know these credentials are OK as I have another Pi client using them to send messages.
Thanks again, David, but it must be too early here and I’ve not had enough coffee yet because I’m not following.
The server and client addresses are set as per the image above. I am using http://serveraddress:8123/mqtt to access the web client. It appears to be working OK except that it does not connect. The web client is the same as this one:
I did give up on this addon because it didn’t like that I was using ssl etc and it was just too hard to make it work. I was getting browser errors as I remember.
I’m using the core addon and if I want to view whats going on (rare unless I’m having a problem) I use MQTT Explorer which is really good for killing any zombies and retained messages.
Because I was using SSL and my duckdns address, the iFram also used ssl and I had to use the local IP address in the HiveMQ screen and then my browser wanted to show everything as not secure and I had to ignore warnings etc and to be honest, the dev wasn’t very helpful and was dripping out information and making obscure statements so it was easier just to use something that works.
Yeah… I just enabled the addon and I get to the login screen and it won’t connect when I click connect… Getting the login interface it just won’t connect to the broker after that…