-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with OUTPUT_FOLDER = Configuration[“owntag_options“][“output_folder "]
#3
Comments
Here's a quick-fix for the issue. I'll update the repo after checking for other bugs. Make sure the .keys files are in a directory called
Now, edit line 18. REMOVE this line:
REPLACE IT with this one:
Let me know if the change works for you. |
Thanks for progressing the project.
Hope this helps. |
fixed in #4 |
You have to install Paho-mqtt.
owntags.sh is a Shell file, not python, syntax is : |
@Systm21 got it. I didn't pull it directly from your request... but (noob problem) didn't know how to just pull an item or two from the changes you proposed. I'm learning. :) |
I made the changes...
|
This error looks like what you get when the password is missing or wrong in the Check out the Also, update the Python libraries. The cryptography is super important. pip install --upgrade pip
pip install pyobjc cryptography six paho-mqtt |
...also please use updated files in repo, can have something todo with the old toml problem. |
Found a mistake in mine: Oh man. The settings-template.toml also clearly states Password macOS/computer…. I had the iCloud password in there. 😕
I think the problem could be the keys. I added the car1.keyfile and the private key B64 to the /owntags/application/keys/ folder. The content of my car1.keyfile is one line: Is the car1.keyfile correct? My settings.toml : -- INSTRUCTIONS --Make a copy of this file and rename it settings.toml.add information about your system, MQTT broker, OwnTracks setup.Create a new settings block for each tag.[owntag_options] [mqtt_secrets] mqtt_broker = "192.168.1.86" # broker address MQTT options for using TLS. No changes needed if your server is not using TLS.mqtt_tls = "None" # To use TLS comment out this line by putting a '#' in front of it. Uncomment these lines and adjust to your needs[mqtt_secrets.mqtt_tls]ca_certs = "keys/isrgrootx1.cer" # cert location, the 'keys' folder is a good place
[owntracks_options] Each tag can be configured to appear as 'waypoints' on your device only, or as 'locations' that are sharedwith other users. 'locations' are easier to start with.OwnTags can share the tag as both, odd things will happen and be prepared for some challenges.[tag_options.prefix]tag_name = "prefix" # the prefix of your keylocation = true # (not required) locations are seen by everyone with access to the topic (they act like users)waypoint = false # (not required) waypoints are only seen on your phone (or device)timestamp = 1000000001 # (required for wayponts) Must be unique, can be any past Unix/Posix timestamp.radius = false # (not required) use number for radius in meters, if
|
The keys must be converted to the format, which is used in the headless-haystack project. |
I can create new keys using headless-haystack (generate_keys.py) The result would be: Is the SROSOM.keys file the correct format? Then I would feed them my data. |
.keys, yes |
error first reported here
As a quick look, line 18:
This tells the script where to find the
.keyfiles
. I'm poking at this now and looking at what I'm using now to update/fix this.The text was updated successfully, but these errors were encountered: