Owntracks and hassio

Installation Home Assistant OS
3

Did you change the port to 8333 for some reason? It’s usually 8883. Also, did you remember to forward the port in your router?

4

lol only a typo …

5

You might take a look at my post. It is a complete working setup in hassio, I only decided to go for Zanzito since it offers me more options and it’s more accurate. TLS with Owntracks and Mosquitto not working

6

As of last night own tracks is connected. ? Ill see how it goes for a couple of days.
Mlamie i’ll definitely give you set up a look.
Thanks all

7

my configuration is on:
HA configuration.yaml :

mqtt:
broker: 192.168.1.41
port: 1883
username: !secret username
password: !secret password

device_tracker.yaml:

  • platform: owntracks
    cd max_gps_accuracy: 200
    waypoints: true

Owntrack APP:

mode: private mqtt
host: whateveryouris.ddns.net (with no https://)
port: 1883
websockets: off
Identification
user: me
pass: nonofyours
device ID: me
tracker ID: em
security TLS: off
parameters
Clean Session: on
keepalive: 60

On my samsung phone, I had to edit the configuration management on the owntracks app and change “mqttprotocollevel” to 3 in order to work.
Also had to port forward 1883 on my router, and it works flawless.

8

Another good working solution is to:

  • Set up cloudmqtt (free tier)
  • Get owntracks connecting to cloudmqtt (TLS)
  • Install mosquitto addon for hassio
  • Configure mosquitto as the mqtt provider for HASS
  • Configure a bridge between mosquitto and cloudmqtt - this is the bridge config for mosquitto that goes in hassio share folder:
    MQTT: Working Mosquitto / CloudMQTT Bridge

Works great.

9

I use GPSlogger instead of Owntracks.

quote:
OwnTracks for Android is no longer maintained.
This version is left for reference and will continue working as is.

GPSlogger works great. Use this manual and it works.

My advise:
make your hassio available by https first.

10

Hi.
I am not able to associate the devices displayed on the frontend with the Owntracks status.
The built-in MQTT broker answers

1510827916: New client connected from 5.170.106.182 as simonesimone (c1, k900, u’Simone’)

so I think it may be an username problem.
I have tried associating to all the MACs in Known_devices.YAML
SimonesimoneSC (userdeviceID), simonesimone, simone_simone, simone_simone_SC,
I think all the combination possible.

ATP it is device_tracker.simonesimone
but the frontend shows me “away” or “not home” according the views, and not “at work”

Where is my fault?

Thank you.

11

Did you add zones?

12

Yes. Both on hassio and on owntracks.
Not ever seen anything different than “away”
It seems that there’s no talk between mqtt and hassio, at least. Or mqtt does not receive lat-long :confused:

EDIT:

I can see zones in the maps and the db on the embedded MQTT being updated.
Devices are updated only when I reopen nmap tracking -that I switched on to avoid conflicts-

13

Hi. Sorry to bother you… can you provide config examples?
I am trying to make it working, but somehow, somewhere something does not talk with something else. :confused:

14

I’m not near my config. But I assume owntracks states is always sayin connected ?

And on the geofence you clicked the share button on the bottom.

And on the main hamburger reporting is switched on. ??

15

From the last:
yes, it is reporting.
(EDIT: I can even see my friends position, so I suppose there’s a dialog with MQTT)
geofences config’d and shared.
(EDIT: even if I assumed that the zone is checked by HASSIO according lat-long, isn’t it?)
owntracks answers “connected” for enpoint state but “endpoint state message” not available.
queue on 0.
MQTT states lots of
New client connected from ecc.,
as told :confused:

Thank you again.

16

Ok here you go:

  1. Install the mosquitto hassio addon
  2. Use the samba addon to create a cloudmqtt.conf config file in \\hassio\share\mosquitto
  3. The cloudmqtt.conf file should look like this:
connection couldmqtt
  address <cloudmqtt server>
  topic # in 1
  try_private true
  notifications false
  start_type automatic
  remote_clientid <cloudmqtt user you configured for HA to login as>
  remote_username <cloudmqtt user you configured for HA to login as>
  remote_password <password for above user>
  keepalive_interval 300
  cleansession true
  bridge_protocol_version mqttv311
  local_clientid <local mosquitto user>
  bridge_cafile /etc/ssl/certs/ca-certificates.crt
  bridge_insecure false

In your hassio mosquitto addon config you need to have:

 "customize": {
    "active": true,
    "folder": "mosquitto"
17

K. :slight_smile:
I’ll try ASAP.
thank you.

18

And nope, again.
I checked the state of the devices on Hass.io while at home and not.
It seems that the lat-long are displayed with home values only when I turn on the NMAP compenent.
With just owntracks, there is NO lat-long in hass.io

I think I am missing something little but really relevant, I suppose to be a facepalm away from the solution.

19

hi sardauker
this is the relevant parts of my config hope it helps.

homeassistant:

Name of the location where Home Assistant is running

name: Home

Location required to calculate the time the sun rises and sets

latitude: .***
longitude: .******

Impacts weather/sunrise data (altitude above sea level in meters)

elevation: 134

metric for Metric, imperial for Imperial

unit_system: metric

Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones

time_zone: Europe/London

Customization file

customize: !include customize.yaml

Show links to resources in log and frontend

introduction:

Enables the frontend

frontend:

Enables configuration UI

config:

http:

Secrets are defined in the file secrets.yaml

api_password: !secret http_password
(TLS and dns stuff)

#Uncomment this if you are using SSL/TLS, running in Docker container, etc.

Checks for available updates

Note: This component will send some information about your system to

the developers to assist with development of Home Assistant.

For more information, please see:

https://home-assistant.io/blog/2016/10/25/explaining-the-updater/

updater:

Optional, allows Home Assistant developers to focus on popular components.

include_used_components: true

Discover some devices automatically

discovery:

Allows you to issue voice commands from the frontend in enabled browsers

conversation:

Enables support for tracking state changes over time

history:

View all events in a logbook

logbook:

Enables a map showing the location of tracked devices

map:

Track the sun

sun:

Weather prediction

sensor:

  • platform: darksky
    api_key:*******

  • platform: mqtt
    state_topic: “button/01/topic”

Text to speech

tts:

  • platform: google

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

mqtt:
broker: core-mosquitto

device_tracker:

  • platform: owntracks
    max_gps_accuracy: 100
    waypoints: True
    waypoint_whitelist:
    • MY NAME (matching username from owntrackes )

zone:

  • name: home
    latitude: .***
    longitude: .****
    radius: 400
    icon: mdi:home
20

Thank you all again.

I Currently can see “friends” (my wife) on owntracks-android
SO
I can be certain that MQTT “talks” back and forth to the phones.

Now the problem has to be between MQTT and Hassio.

I am tinkering constantly with the YAML and the MQTT config, but I can’t see the elephant :confused:

21

Hi Sardauker,

Sorry for digging up this thread, everybody. But I am facing quite similar issues. At bootup I am receiving this error:
Error setting up platform owntracks and deeper down inside the error message: Error talking to MQTT: The client is not currently connected.

Since MQTT (mosquitto, installed as a hass.io package in my case) is running fine, I can only guess that this happens since the broker is not ready yet when trying to set up owntracks.

Has anyone an idea on how to delay the setup of owntracks? Or did you get it to work, @Sardauker?

EDIT: switched to the http version, as @dannyhanes suggested. Works, after activating api_password.

22

Sorry, I have seen the notify just now :frowning:

No, I couldn’t make it work even in http, I switched to Google :frowning: