Cannot Connect to Broker on Windows: 'Connection Lost'

[artistro08]

So I have a broker over at HiveMQ and for the life of me, I cannot connect to it.

everytime I get this:

My configuration is as follows:

{
    "active_entities": [
        {
            "type": "AppInfo"
        },
        {
            "type": "Monitor"
        },
        {
            "enable_hibernate": "N",
            "type": "Power"
        }
    ],
    "active_warehouses": [
        {
            "address": "[redacted].s2.eu.hivemq.cloud",
            "port": "8884",
            "name": "Kaito",
            "username": "[redacted]",
            "password": "[redacted]",
            "add_name": "Y",
            "use_tag": "Y",
            "type": "HomeAssistant"
        }
    ],
    "settings": [
        {
            "update_interval": "10",
            "retry_interval": 1,
            "type": "App"
        }
    ]
}

Am I missing a part of configuration? I also allowed IoTuring to bypass the firewall

[richibrics]

Do you connect other MQTT clients to the same broker using the client name "Kaito" ?

[artistro08]

Acutally, yes, Ill see if that's it

[artistro08]

Hmm still does it

[richibrics]

it happened to me twice, the reasons were:

• I used twice the same client id, changing it solved instantaneously
• The broker asked for a specific usage of the client id and messages topics so these rules always disconnected me

[richibrics]

@artistro08 do you have any other computer / os to try it ?

[artistro08]

The broker asked for a specific usage of the client id and messages topics so these rules always disconnected me

That might be it. I'll try it and report my findings

[artistro08]

How do I go about making sure the client id is good? I tried on both my pcs and it was a no go

[artistro08]

I also have IoTLink installed. Would that conflict? I make sure to disable it when I do run IoTuring

[richibrics]

Test a client id without uppercase letter, no spaces, and that you are sure no other client is already using on your account for that broker. Additionally, you can look at the Event history for your account at HiveMQ to see the events: the broker could log the disconnection reason there

[artistro08]

Still no dice. Logs don't say anything, tried a lowercase name, even tried a different mqtt client and that connected fine.

Gonna call it quits, thanks for your help

[artistro08]

It looks like this isn't windows specific, but rather SSL specific. I just tried this with a linux host over HiveMQ and it does not work. Completely different name.

[richibrics]

Hi, do you still have this problem ? If not, how did you solve ?

[artistro08]

I do have the problem, but never was able to solve