Owntracks configuration

[Quincarter]

so is there a way to set the manual configuration options for owntracks now? The integration in the UI doesn’t allow for any special options to be configured and now I am getting the inaccurate locations being reported by my devices because i had to remove this override. (FYI my devices have the same inaccurate location setting to 200 in the owntracks app on android)

owntracks:
  max_gps_accuracy: 200
  waypoints: true

FYI I am using nabu casa with the owntracks hook and it is configured via the UI in integrations. My device trackers show up as entities but when i add the configuration.yaml settings, the devices go to unavailable. I am assuming there is some kind of secondary ID getting setup or the owntracks: key is overriding the UI key somehow.

[Tinkerer (aka DubhAd on GitHub)]

The forum gave you a big hint about not replying to a solved thread - you should listen to it, particularly as your question is unrelated to that topic.

known_devices.yaml has nothing to do with how you configure owntracks which still has the YAML configuration you listed.

[Quincarter]

My bad. Sorry about that. I haven’t posted much in this forum so I wasn’t sure the protocol.

So I am not using known_devices.yaml anymore. I configured own tracks from the UI, it was working, then I had to set up the integration again when we got new phones (I lost the hook and encryption key info) and that’s when it stopped tracking properly/wasn’t able to use the configuration.yaml to set other values.

This is what my devices do now with the owntracks configured in the yaml and the ui

When the configuration.yaml doesn’t have owntracks in it, my devices report but they have inaccurate locations reported on occasion.

[Tinkerer (aka DubhAd on GitHub)]

Check the log file for warnings or errors. There may be an error with your YAML, or another problem.

[Quincarter]

Wouldn’t an error in the yaml reveal itself in the Check Configuration?

[Tinkerer (aka DubhAd on GitHub)]

Not always, the UI check misses stuff. The command line configuration check is more complete.

[Quincarter]

interesting. so i was tinkering with this some. As i took away settings from the configuration.yaml, i found that when i have

owntracks:
  max_gps_accuracy: 200
  events_only: true

the events_only makes the integration stops reporting - if i remove that, it starts to report locations again.

Here is another kicker - when i have this configuration, the owntracks integration reports 0 devices:

owntracks:
  max_gps_accuracy: 200
  events_only: true
  waypoints: true
  region_mapping:
    MyHouse: home
    office: work

So what is up with the configuration.yaml piece of this that causes the integration to go haywire?

[Quincarter]

Also just playing with it, i cannot just have waypoints: true either. Basically the only thing that is supported looks to be max_gps_accuracy, everything else causes the devices not not report properly.