mrmay-dev / owntags Goto Github PK

At the moment, there are 2 prefix_files in the keys folder. All data is anonymized so don't worry, everything is fine with above data.

Hope @mrmay-dev can help to fix it, i get stuck here.

anonymous@iMac-Pro application % python3 request_reports.py --time 23:59  --owntags
2029 Sep 99 (Mon) 24:05:06
Using python3
Days: 0, Hrs: 23, Min: 59
200 OK

271 reports received.
25 reports used.
Used 1000000000 as creation_stamp for bv14N+8
'bv14N+8'
Traceback (most recent call last):
  File "/Users/anonymous/Desktop/owntags-main/application/request_reports.py", line 182, in <module>
    ordered = owntags(ordered, time_window, found)
  File "/Users/anonymous/Desktop/owntags-main/application/OwnTags_plugin.py", line 118, in owntags
    if tag_options[prefix]["location"]:
KeyError: 'bv14N+8'

I'm curious, how do you use (or want to use) tags as part of a home automation system?

As mentioned by @system21 in seemoo-lab/openhaystack#213 (reply in thread), seems there have been a few times that message failed to deliver to the receivers, however, there was no further information provided.

I have looked at the code of this project, multiple places used QoS:0 which might allow the message to be discarded, which makes me wonder maybe it's worth to give a try to adjust the location message QoS from 0 to 1 in code could improve the delivery.

Ref:
https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/#:~:text=Published%3A%20February%2016%2C%202015,guarantee%20for%20a%20specific%20message.

First of all, it works, really cool 😁

Is it possible to make the tags a bit clearer? the keyfile is named bike and the tag appears as "ke" under "Friends" that is not very cool. or is it a owntracks thing?
You can klick on it and the identifier shows bike, but the trackerid only accepts two characters? If you have more tags, thats very mixed up.

error first reported here

As a quick look, line 18:

OUTPUT_FOLDER = Konfiguration["owntag_options"]["output_folder"]`

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.

It took me a while to figure out how to schedule scripts to run on MacOS. I believe cron is still working but depreciated, so I decided to look into Apple's LauchD. Seems way more complicated than what I need, still I ended up using LauchControl. It works well and I can see the logs.

How are you scheduling OwnTags to run on your system?

Not sure if this is possible because you put how far back in reports you want, but it would be useful for the output to say "last report received at X" or under missing keys say when it was last seen.

Either way keep up the good work, glad to finally have a way of easily integrating into home assistant :)

I don't yet understand what the prefix information in the settings.toml should look like.

owntags/
└── application/
    └── keys/
        ├── prefix-1.keyfile	 # Car1
        ├── prefix-2.keyfile	 # Car2
	├── prefix-2.keyfile	 # Unicorn
	└── prefix-2.keyfile 	 # Dragon

@settings.toml

[tag_options.prefix prefix-1]
[tag_options.prefix prefix-2]
[tag_options.prefix prefix-3]
[tag_options.prefix prefix-4]


tag_name = "prefix-1" # Car1
tag_name = "prefix-2" # Car2
tag_name = "prefix-3" # Unicorn
tag_name = "prefix-4" # Dragon

or should it look like this?

owntags/
└── application/
    └── keys/
        ├── car1.keyfile	 
        ├── car2.keyfile	 
	├── unicorn.keyfile	 
	└── dragon.keyfile 	

@settings.toml

[tag_options.prefix]
tag_name = "car1"  
location = true 
waypoint = false  
timestamp = 1000000001  
radius = false  

[tag_options.prefix]
tag_name = "car2"  
location = true 
waypoint = false  
timestamp = 1000000001  
radius = false  

[tag_options.prefix]
tag_name = "unicorn"  
location = true 
waypoint = false  
timestamp = 1000000001  
radius = false  

[tag_options.prefix]
tag_name = "dragon"  
location = true 
waypoint = false  
timestamp = 1000000001  
radius = false  

...because you can see it in the commits 👍

First off, thanks for poking at this project. It sat around since I was happy with how it was working and with others taking interest (gives me the warm fuzzies) I'm happy to keep it moving forward.

So, as a heads up, I am noob programmer (can't do list-comprehension or use ternary operators correctly) and a noob at GitHub. Which means I'll probably screw things up as a I learn, with a little help I know we can keep that down to a minimum.

Thanks for being here. With your help and interest I'm sure we'll have fun working on this.

Happy coding!