Comments (11)
@GitHubQueenn the files in /usr/local/owntracks/userdata
are only for your information, not the source of the passwords etc.
To set a password of your choice, edit configuration.yaml
as shown below and re-run ./bootstrap.sh
.
(the optional password is not described in the setup guide, but only in the configuration.yaml
file itself)
# configuration for OwnTracks backend quicksetup
# Specify your DNS domain, the name by which this OwnTracks
...
# Configure yourself and a list of friends who will be using
# this backend. Each friend will use their "username" to login
# to the site and to the apps. Their device is a "devicename"
# (this can be any suitable name, but we recommend you keep it
# generic so as to not have to change this if you move to a
# distinct device; i.e. "myphone" instead of "siemens-e2"),
# and their "tid" is a tracker- id which is used to label users
# on the map. A tid is a string of length two characters.
# Optionally a "password" may be set below; if omitted, passwords
# are generated and stored at /usr/local/owntracks/userdata/*.pass
# on this system.
#
friends:
- { tid: UD, username: user, devicename: device, password: yourpassword }
...
from quicksetup.
Friend-specific passwords are actually documented in the Booklet, and linked to from the bottom of the Quicksetup page.
from quicksetup.
@ckrey @jpmens Thank you. Real quick: how come one user here shows as "owntracks/b/phone" but the other as just "fs"? I would like to have "owntracks/b/phone" show as just the TID if possible, like the "fs" user does. Is that possible? Because when the one user sees the other, they show up on the map as "owntracks/b/phone" instead of their TID like "fs" does.
Looks like: https://i.imgur.com/WXZg6tm.png
Nowhere in my config or anywhere I see is the tid/names set to "owntracks/b/phone"
from quicksetup.
TIDs are two characters and are configured on the device respectively via the autoconfiguration you might have done. I'm assuming one of the devices is publishing via HTTP which we reccomend you don't do: in /usr/local/owntracks/userdata you'll find *.otrc
files which you send to the device (e.g. via email) and open it in OwnTracks there. The TID you configured in configuration.yaml
.
from quicksetup.
TIDs are two characters and are configured on the device respectively via the autoconfiguration you might have done. I'm assuming one of the devices is publishing via HTTP which we reccomend you don't do: in /usr/local/owntracks/userdata you'll find
*.otrc
files which you send to the device (e.g. via email) and open it in OwnTracks there. The TID you configured inconfiguration.yaml
.
Both devices are using MQTT. So far, for my friend and myself, we have just used my domain to log into the OwnTracks server and then tapped on the links to import the configs to our phones (Android & iPhone). The only place I see "owntracks/b/phone" is at the OTRC file at this line:
"subTopic": "owntracks/+/+ owntracks/+/+/event owntracks/+/+/info owntracks/b/phone/cmd",
The TID shows how I originally set it as "bb". I also see it in the app under "pubTopicBase"
from quicksetup.
You are saying there's a discrepancy between the TID in pubtopic and subtopic; that can only be due to editing of the configuration; I don't think there's a bug in the generation of our OTRC files.
Please don't confuse TID with the username contained in the topic.
You have also not said which device (iPhone or Android) is fs
and which is bb
from quicksetup.
It is much easier to understand the issue here if you embed your images rather than using an external link:
from quicksetup.
Let me explain how it works and what you can do to change it:
![Bildschirmfoto 2024-03-22 um 09 08 31](https://private-user-images.githubusercontent.com/4027289/315935774-7192b5f8-c860-4bc6-aa97-d0680b44fa6b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxMzM1OTYsIm5iZiI6MTcxOTEzMzI5NiwicGF0aCI6Ii80MDI3Mjg5LzMxNTkzNTc3NC03MTkyYjVmOC1jODYwLTRiYzYtYWE5Ny1kMDY4MGI0NGZhNmIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjNUMDkwMTM2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTI3MjQyMDBhOWM3ZDY5NTJlZjA2YjRhMzc2Mzg1OGEyMTgwMzZhNTE2YWE3NzAzYWViZDQ4ODA2YTg1OWRkOSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.FsHNe247jz89KNSK9LBAc5pOBwSQakW_SfGEKRwV6Qk)
The Name
column uses the topic
or if available the name
field of the card published to the MQTT broker https://owntracks.org/booklet/features/card/#card.
The TID
column shows the tid
element of the location message. If the location message does not contain a tid
, it uses the last two letters of the topic
.
** In your case, fs
has published a card (either via MQTT to the backend or directly from the iOS OwnTracks app) and owntracks/b/phone
**
- In the
Frontend
, theName
is displayed. - On the
Live map
theTID
is displayed if available instead of thetopic
if noname
is given
from quicksetup.
The card made from fs was directly from the iPhone app. So how would we get rid of the "owntracks/b/phone" to just show "bb" like the other just shows "fs"?
from quicksetup.
from quicksetup.
Closing as answered.
from quicksetup.
Related Issues (20)
- MQTT configuration changes HOT 8
- User-specific MQTT ACLs? HOT 3
- Add template validation for mosquitto*.* when 2.1 is released
- User-specific waypoints for inline/otrc configuration HOT 6
- Check task duration: why does otrc generation take so long? HOT 2
- bootstrap.sh should detect if it's being run as priviledged user
- Assertion failing during OwnTracks installation HOT 4
- Please Delete This
- Battery shows 0% no matter what at https://owntracks.domain.com/owntracks/table/ HOT 3
- Rate-Limited By OpenCage? HOT 2
- Change "mqttProtocolLevel" HOT 1
- Quicksetup acme "cant find solver" "firewall problem?" HOT 10
- Post quicksetup connection issues HOT 2
- mosquitto restart issue during install HOT 9
- Front end URL could be improved HOT 1
- Quicksetup: Where does the data live? HOT 2
- How Quicksetup logs Let's Encrypt certificate renewals
- Installing new Frontend version leaves old files in place
- Mosquitto doesn't start up if LE isn't configured
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from quicksetup.