What could be amiss here, i can see my Owntracks on 8883 in the mqtt log, my phone is connected and i can publish locations etc etc.
Just never shows up in Home Assistant.
because of the above, i am not able to create a mqtt sensor yet, dont know what topic to subscribe to, other than my username
since im trying to use owntracks for tracking home / not home, would i need the lon and lat into one template? For security settings i havent set Home in the app (and since im not using it encrypted now, maybe i shouldn’t…) so would have to rely on calculating lat/long.
yes, and im seeing it now. Not sure how to get the lon and lat together in a way i can use it for using it as home-away.
some values are a bit fuzzy. type gets value location, but i cant see the location itself?
It’s populating the known_devices.yaml file with OwnTracks devices?
If not - take a look at this thread, he had issues with the embedded broker populating known_devices.yaml
If it is populating known_devices.yaml, all you need is your home lat/lon also set in your configuration.yaml and the device_tracker will automatically select your home or not_home states from the values in the MQTT message.
its not populating the known_devices, but i can subscribe to the mqtt stream.
If i read correctly, it will populate the known_devices when configured through the _htpp component, using homeassistant as username and ha_password . for obvious reasons (…) it;s not my preferred configuration, handing over my HA credentials to other apps…
Conseqeuntly, I am looking for a way to have HomeAssistant use the mqtt topics,that it can read, and which i can get into the frontend with dedicated mqtt sensors:
surely i have my lat/lon set in configuration.yaml. If you say it will automatically st my home/not_home status, in which entity would it do that? maybe i just cant see it pop up (using a default_view) and must look for it in the dev-tools…