Owntracks with multiple users

Configuration
1

Dear all:

I am probably one of few people started to use owntracks long before I start to use homeAssistant.

I have my own mosquitoes server set up, with multiple users on it.

The problem is that, despite in the configuration I have something that suppose to subscribe everyone:

device_tracker:
  - platform: owntracks
    max_gps_accuracy: 100
    mqtt_topic: owntracks/#
    events_only: true

I can only see myself, no one else. how do i make rest of people on my owntracks/ show up? do I have to register the broker multiple times like this?

mqtt:
  - broker: 123.45.67.8 
    port: 18883
    username: user1
    password: password1
    client_id: homeAssist
    keepalive: 300
  - broker: 123.45.67.8 
    port: 18883
    username: user2
    password: password2
    client_id: homeAssist
    keepalive: 300
  - broker: 123.45.67.8 
    port: 18883
    username: user3
    password: password3
    client_id: homeAssist
    keepalive: 300

or I can somehow tweak entry in known_devices.yaml?

thanks

2

Did you see other users with same account on your phone via owntracks?
Other users mean members in the same account you sign up from cloudmqtt. If you can see other users then you can config in HA part.

On Ha part. you need cloudmqtt bridge, MQTT: Working Mosquitto / CloudMQTT Bridge

3

on my phone, i can see everyone else (i use owntracks to keep track of family members).

so, I do know owntracks behaves properly.

i tried to follow what everyone else is doing by having this following configuration:

device_tracker:
  - platform: mqtt
    devices:
      user1: 'location/user1'
      user2: 'location/user2'
      user3: 'location/user3'

but only user1 showed up in the map in Home assistant :frowning:

my question is how to set it up on Home Assistant.

4

I’m using Owntracks, but a little different than you…
Here is my configuration:

In confiruration.yaml:
device_tracker: !include device_tracker.yaml

in device_tracker.yaml

- platform: owntracks
  max_gps_accuracy: 200
  waypoints: True

Now, the part that I’v set up different:
In OwnTracks application, I’m using the same username and password:
Under preferences - connection - private MQTT - IDENTIFICATION
(For device 1)
Username: Username1
Password: Password 1
Device ID: ID1
Tracker ID: T1

(For device 2)
Username: Username1
Password: Password 1
Device ID: ID2
Tracker ID: T2

5

the setting in configuration.yaml for mqtt

mqtt:
  - broker: 123.45.67.8 
    port: 18883
    username: user1
    password: password1
    client_id: homeAssist
    keepalive: 300

for device_tracker in configuration.yaml

device_tracker:
  - platform: owntracks
    max_gps_accuracy: 100
    waypoints: true
    geocode: true
    waypoint_whitelist:
      - username you create from cloudmqtt for yourself
      - username you create from cloudmqtt for you family member

for mosquitto bridge. I follow from MQTT: Working Mosquitto / CloudMQTT Bridge You have to read from the post where to create the bridge file and how.
the file I create name bridgemosquitto.conf

connection cloudmqtt
address mXX.cloudmqtt.com:23456 <=== come from cloudmqtt detail page. There is 2 ports provide you can use with or without ssl. I do open this port in my router as well. Example port 23456. In router external 23456 interal 23456
topic # in
try_private true
notifications false
start_type automatic
remote_username ABCDEF <== come from username of cloudmqtt details page
remote_password ABCDEF  <== come from password of cloudmqtt details page
remote_clientid AAAAA <=== username you create in cloudmqtt from user page
local_clientid AAAAA <=== from mosquitto username you create I use the same as cloudmqtt
keepalive_interval 300
cleansession true
bridge_protocol_version mqttv311
bridge_cafile /etc/ssl/certs/ca-certificates.crt
bridge_insecure false