Unable to connect to broker from tdm on MacOS

[nickidw]

I'm unable to connect to my MQTT broker (builtin HomeAssistant). TDM just says Connecting to broker, and after a few seconds Disconnected. Is there any debug switch I can enable?

[nickidw]

I enabled logging in homeassistant and saw this:

2019-05-01 18:45:12 ERROR (MainThread) [hbmqtt.broker] Invalid connection from (client @=192.168.11.249:59459) : [MQTT-3.1.2-1] Incorrect protocol name: "MQIsdp"

[nickidw]

Looks like I need to install mosquito rather as mqtt broker?

[andrethomas]

I use mosquito and it works fine with TDM - Have not tested with others.

[jziolkowski]

I'm developing against mosquitto as well and it works as expected.
Are you positive this error is from TDM? Because it uses Paho as MQTT backend and it uses protocol ver. 3.1. It doesn't even support ver. 3.1.2

[nickidw]

As per original post I use the homeassistant builtin broker, and saw the errors in the homeassistant log. I only see the errors when trying to connect with TDM.

[jziolkowski]

If it's in fact TDM, then your broker is wrong. Like I said, Paho doesn't use anything > 3.1.1. Please install Mosquitto and try again.

[effelle]

@nickidw as a side note, please be adviced that on Home Assistant starting from release 0.92 the embedded broker has been marked as deprecated. This means bugs may not be fixed, and the functionality may be removed in a future release.

[nickidw]

Thank you, I did see that :-)

…

On Mon, May 6, 2019 at 2:11 PM Federico Leoni ***@***.***> wrote: @nickidw <https://github.com/nickidw> as a side note, please be advice that on Home Assistant starting from release 0.92 the embedded broker has been marked as deprecated. This means bugs may not be fixed, and the functionality may be removed in a future release. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC3VXAUGCOLJ6WZUKBFVRBLPUAN5LANCNFSM4HJUT7ZA> .

[andrethomas]

Closing this as a workaround has been provided here