-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
prefix in the settings.toml #6
Comments
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):
@mrmay-dev MUST be |
@Systm21 , you are right that the prefix name ( Yes, changing the prefixes on the keyfile works so long as the name is changed in the Also, check out the timestamps. Each key must be unique. My keyfiles are:
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. 😁 |
Cool! Hope it gos well. 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. |
It's a smarthomeserver called iobroker, simillar to Home Assistant.
Would you like a full json string to sort out, what you need?
|
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
The text was updated successfully, but these errors were encountered: