Home Assistant can't publish to MQTT

Configuration
1

Current state of things: I have mosquito running and can publish to it from owntracks (I can see the messages using

mosquitto_sub -h [email protected] -t owntracks/# -p 8883 --capath /etc/ssl/certs/ -u "user" -P "password"

But if I use the MQTT developer tool in the webinterface, set topic to “owntracks/test” and Payload to “test” I don’t receive anything.

Config:
mqtt:
  broker: [email protected]
  port: 8883
  client_id: home-assistant
  username: user
  password: password

I made the certificates using Letsencrypt certbot. Also I use the same user for all applications. Is that a problem?

The commandline running hass outputs

[Errno 104] Connection reset by peer
2017-12-29 16:37:45 INFO (Thread-12) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server

every couple of minutes and when I try to publish a MQTT package it says

2017-12-29 16:39:34 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=mqtt, service_data=payload_template=test, topic=owntracks/test, service=publish, service_call_id=139738780625776-46>
2017-12-29 16:39:34 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=139738780625776-46>

So what’s wrong with my configuration?

2

Did you find a solution? I’m having the same problem (MQTT broker seems fine, messages from hass don’t seem to appear).

3

I’d like to know if there was a solution as well. if I remove the ssl certificate I can connect perfectly. I assume it’s because of the capath. I’ve tried copying and specifying certificates but nothing seems to work as expected.

4

So after two days of debugging I realized that I was missing one parameter,

certificate: /etc/ssl/certs/ca-certificates.crt

and now my system works. I purchased my own ssl certificate so it was hard to find documentation, but this worked for me and now my system is up and running. Hopefully that helps you out.