Owntracks Config Hass 83.3


I’m stumbling hard on re-configuring after the latest 83.3 update. Just not sure of the correct config of Owntracks and Mosquitto.

Here’s what I know. Config Owntracks to HTTP. Was using MQTT before 83.3 with no issues. I’m Forwarding 1883.
1544030158: New connection from (removed IP) on port 1883. 1544030158: Socket error on client <unknown>, disconnecting.

Added Owntracks to configuration:
max_gps_accuracy: 200
waypoints: true
mqtt_topic: “owntracks/#”
events_only: true

I can tell my issue appears to be an authentication issue. Just not sure where or what I’m missing. Any help would be much appreciated.


I had these errors. Did you remember to restart after changing the config file?


Do you have an account set up for mqtt that you login with in your mqtt config file?
Something like this? (and NOT homeassistant for a login)

  "logins": [
      "username": "mqtt",
      "password": "whatever-you-want"
  "anonymous": true,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"


It is not going to work without using proper indentation.


No I do not have an MQTT account setup. Yes I see the indentation, I will adjust that. Currently having SD card issues, so once I get back to the current version I’ll revisit this.


You said you were switching Owntracks to HTTP, but you have MQTT topics in the config yaml. HTTP doesn’t use MQTT and should be configured in the phone app to use Private HTTP. Authentication is done through the long random url you get when enabling Owntracks in HA Integrations. Sorry if I’m not understanding correctly.


just change:
- platform: owntracks
max_gps_accuracy: 500
waypoints: True
#- platform: owntracks
max_gps_accuracy: 500
waypoints: True

and leave the rest as is. if it doesn’t get anything from http it checks mqtt so no need to change it.

also an http header is bigger than a mqtt header, so i dont really know why you would want to change to http anyway. mqtt packet is smaller thus cheaper, might just be a few bits so over a year just a few cents, but still.


Understandable and thank you. For some reason I was under the impression that owntracks needed to be HTTP under 83.3. I apologize as I’m currently trying to do this in a vacuum of no time.


no worries, i was a bit confused and worried too when i first read it.