Updated last night..owntracks error now

Good day,

So I updated to 0.83.2 last night, then today started to do some work on HA. I ran the check config and am now getting:

Platform not found: device_tracker.owntracks_http

This is the device_tracker section from my configuration.yaml

device_tracker:

  • platform: unifi
    username: !secret unifi_username
    password: !secret unifi_password
    host: <>
    port: 8443
    verify_ssl: False
    interval_seconds: 30
    consider_home: 180
    track_new_devices: yes

  • platform: nmap_tracker
    hosts: <>

  • platform: owntracks_http

I haven’t modified anything under this section in over a year.

In the release notes there is a breaking change for owntracks in 0.83

Thanks, I totally missed that when I skimmed the release notes.

I’m in the same boat, removed the entries from my configuration.yaml, tried to setup the new “integration” but am having no luck, unsure if its an issue with my reverse proxy config but it worked perfectly previously.

sorry to bump this, ut what was that change? My OT stopped working a week ago, havent changed anything, but maybe that could be it… now where to find the change?

There is no way I could remember the release notes from a couple of months ago. I think you need to read them yourself to find that out.

Search the blog… just show blog posts and it’s probably on the first page

thanks, found it, and I had forgotten I had already implemented the change to owntracks: versus the older device_tracker: owntracks successfully and had a perfectly working setup till yesterweek.

I don’t want the new integration to rely on http, but need the mqtt option, since I have 2 HA instances reading from that mqtt broker.

Tried the new integration style setup, bt that gave me a ridiculously long https address… and, how would I have my iPhone push to 2 HA instances each having their own http address. There’s no way in that url to lead it to 1 of my 2 Pi’s by means of a port. Tried it, no succes.

This doesn’t seem every well thought through, or I must be missing the obvious here…

Or could it be the Owntracks App got an update because of which it now stopped working correctly…?