Open 23tom2323 opened 1 year ago
Do you already have prefix files with stored keys? Maybe its a little bit clearer for you, when you have data that you can work with.
Simplified it should something like this (can test it in the afternoon):
[tag_options.car1]
tag_name = "car1"
location = true
waypoint = false
timestamp = 1000000001
radius = false
[tag_options.car2]
tag_name = "car2"
location = true
waypoint = false
timestamp = 1000000001
radius = false
[tag_options.unicorn]
tag_name = "unicorn"
location = true
waypoint = false
timestamp = 1000000001
radius = false
[tag_options.dragon]
tag_name = "dragon"
location = true
waypoint = false
timestamp = 1000000001
radius = false
@mrmay-dev Can i rename the prefixes in the Keyfile? Does it also work?
MUST be tag_options.dragon and tag_name = dragon Identically? ...or can i rename it with tag_name?
@Systm21 , you are right that the prefix name ([tag_options.dragon]
) MUST match the (tag_name = "dragon"
). I think it's redundant and want to work the code so it pulls the prefix from the toml block header.
Yes, changing the prefixes on the keyfile works so long as the name is changed in the settings.toml
. I named mine for Minecraft items. LOL
Also, check out the timestamps. Each key must be unique.
My keyfiles are:
alex.keys
steve.keys
sheep.keys
and the corresponding TOML blocks read:
[tag_options.alex]
tag_name = "alex"
location = true
waypoint = false
timestamp = 1000000001
radius = false
[tag_options.steve]
tag_name = "steve"
location = true
waypoint = false
timestamp = 1000000002
radius = false
[tag_options.sheep]
tag_name = "sheep"
location = true
waypoint = false
timestamp = 1000000003
radius = false
That's what OwnTracks uses to track waypoints. If the timestamps are the same, OwnTracks thinks it's the same waypoint.
Ok, got it. but the timestamps can be anything as long as its unique, just like fakestamps 😁 ?
LOL Love it. Fakestamps!
Yup, any sting of numbers that represent a Unix/Posix date. Honestly, haven't tried future dates... that would be interesting. 😁
Short update. Soon everything will be running. I call up, it goes to the mqtt and the broker gets the data. So far so good.
I noticed in the broker in the objects of the individual ESPs that data is mixed up. For example, data from Unicom is entered into Car. Also changing the TID, what Systm21 has already mentioned, would be really nice.
But today we're going in Holiday for two weeks. 1000 km there and 1000 km back, so I take a few own tags with me. ;-).
Thank you for your support, I'll be back soon.
Cool! Hope it gos well. What app is that screenshot from? Looks interesting.
Tell me about that battery level line that's highlighted. Is it OwnTracks? Been wishing I knew enough to add that into the payload that is sent with the keys.
What app is that screenshot from? Looks interesting.
It's a smarthomeserver called iobroker, simillar to Home Assistant.
Tell me about that battery level line that's highlighted. Is it OwnTracks? Been wishing I knew enough to add that into the payload that is sent with the keys.
Would you like a full json string to sort out, what you need?
{"_type":"location","BSSID":"be:ef:fe:ed:6f:9a","SSID":"SomeWifi","acc":15,"alt":363,"batt":62,"bs":2,"conn":"w","created_at":1694554648,"lat":49.5132895,"lon":9.4512478,"m":-1,"t":"u","tid":"ab","tst":1694553859,"vac":1,"vel":0}
I don't yet understand what the prefix information in the settings.toml should look like.
@settings.toml
or should it look like this?
@settings.toml