MQTT Broker duplicate

@robb1 wrote:

Hi all
In my initial HassIO setup I used mqtt with an existing broker running on a separate Raspi to HassIO.
When time came to move to a broker on the HassIO (also a Raspi) I had some troubles getting configuration sorted out and seem to have created two instances of a broker.
I have nothing in the configuration.yaml file and have tried deleting the the Mqtt Integration and uninstalling the add-on.
In the logs I am seeing :

1590581406: New connection from 192.168.1.31 on port 1883.
1590581406: New client connected from 192.168.1.31 as mqtt_ab17b99a.d019d8 (p2, c1, k60, u'hass_mqtt').
1590581406: New connection from 192.168.1.31 on port 1883.
1590581406: New client connected from 192.168.1.31 as mqtt_d17523dd.23702 (p2, c1, k60, u'hass_mqtt').

I fear the two broker instances are at the root of my issues.
Can anyone firstly confirm that this is a broken configuration and secondly how to remove the rogue broker - assuming I am right.
A typical device is an ESP8266 with a H-A config like :

cover:
  - platform: mqtt
    name: Blind 1    
    state_topic: "Blind1_esp/posn"  
    command_topic: "Blind1/cmd"
    payload_close: "DOWN1"
    payload_open: "UP1"
    state_open: "UP"
    state_closed: "DOWN"

Posts: 1

Participants: 1

Read full topic