Problem starting embedded MQTT broker

[anon35356645]

@Tinkerer

Disable it in whatever startup system your platform is using. For example, if you’re using systemd, then systemctl disable mosquitto

how to check if I have this?

[Tinkerer (aka DubhAd on GitHub)]

Hassbian is Raspbian based, which uses systemd.

[anon35356645]

thanks. Do I have to modify the file? Where is it?

[Tinkerer (aka DubhAd on GitHub)]

Just run, as root (so, prefix with sudo if you’re not already root):

systemctl disable mosquitto

[anon35356645]

@Tinkerer

Just run, as root (so, prefix with sudo if you’re not already root):

systemctl disable mosquitto

you mean one time only, after the next reboot will not start again?

[Tinkerer (aka DubhAd on GitHub)]

Correct. Can I suggest a read of the manual page for systemctl (man systemctl to see what the options are, and what they do).

[anon35356645]

@Corey_Johnson

How can I tell if the embedded MQTT is running?

if you don’t have broker: in your configuration

so at least I understood.

All this is very confusing,

[anon35356645]

@Corey_Johnson

I went back to cloud (had it for something way back) but still having issues. I can’t remember if I ever had it working. On a side note, I did get WallPanel installed on a Kindle Fire Tablet. So once I get mqtt figured out I’ll be in business.

if you put
mqtt:
is embedded

if you put
mqtt:
broker: ipaddress

then is mosquitto … go figure

[trati629]

Hi I had the same issue with the front end but I change my Config to:
mqtt:
username: !secret mqtt_pass
password: !secret mqtt
keepalive: 60

from:
mqtt: # Mqtt Broker
broker: 192.168.1.XXX
port: 1883
client_id: home-assistant-1
username: !secret mqtt_pass
password: !secret mqtt
keepalive: 60

hope this helps