Does anyone have any idea how I can get this to work? I set up OwnTracks following the instructions. On my Android phone, I get an “Unknown host” message when I trying to test OwnTracks. I’m trying to connect via HTTP and have carefully and pasted the URL.
I tried exactly the same thing on another Homey with an iPhone, and it works there… What am I doing wrong?
This is driving me nuts Does anyone have any pointers on how to get this app working with the HTTP option, and what I might have missed trying to follow the setup guide please?
The endpoint generated by ZoneTracks is correct. This is most likely an OwnTracks Android configuration issue:
Set OwnTracks mode to HTTP.
Paste the complete ZoneTracks endpoint into Android’s URL field.
Do not paste it into Host. OwnTracks uses Host for MQTT mode.
Leave MQTT host/port settings irrelevant or cleared.
Make sure the URL starts with https:// and includes the complete /api/app/.../events/<userId> path.
OwnTracks’ Android documentation confirms that HTTP mode requires url, while MQTT mode requires host. This explains why the same endpoint works on iPhone but reports “Unknown host” on Android.
If it works on Iphone the Homey app, etc must be working, so I can only think that it’s something with the OwnTracks settings on Android. I did initially use it via HTTPS on Android but I have switched to MQTT as it’s more efficient.
Thank you for your reply. As I mentioned in my first post I’m using iOS rather than Android. And the Advanced Settings HTTP Endpoint is still in-copyable. I have to delete the user device and recreate it if I need to get the endpoint URL again after initial setup. A small bug I realise, and perhaps an iOS oddity. But frustrating nonetheless the less.
Your reply did give me an idea about the ZoneTracks configuration though, that has got it working, Thank You!
I deleted the defaults from the Host, Port, Password fields, turned off Authentication, and re-applied the URL. I also found that the UserID field had to be set to the exact same (case sensitive) text as the ID name from the Homey User device card, which I didn’t see in the setup instructions, and was possibly the bit I was missing.
It’s easy when you know how… I just couldn’t see the wood for the trees
When you create a device, you can temporarily view the URL which, as you noted, does not display the full address. However, you can retrieve the full URL for the device from the settings after you’ve created it. There you’ll see the entire URL and can copy it.
I have tried every which way possible to access the HTTP Endpoint URL from the user device’s Advanced Settings in the Homey app on my iPhone 14 Pro Max running iOS 27.0 and you can not see the full URL, or copy the URL on either the Advanced Settings page or by tapping the URL field to go to its own page. It just doesn’t work.
The only time, and I do mean the only time, that I was able to access the full URL and copy it, was during the creation of the device. So if I need to access the URL after that, the only way I have been able to do it on my iPhone is to delete the current device and create a new one, and then reconfigure the OwnTracks app to use the new URL.
This has to be a bug. The URL needs to be made copyable from the settings page for iOS (I’m assuming it works in Android, and that is why this hasn’t been fixed yet?)
It’s probably just something to do with the way iPhones display none editable text fields.
I wonder if it would be possible to make the URL accessible in the app settings, perhaps on the Avatars page, a button to copy URL to clipboard?
Trying to add some zones/waypoints, and in both the mobile app on iPhone (iOS) and in the web interface on a desktop browser, when trying to reposition the map to set the waypoint it keeps crashing. I’ve also noticed high CPU usage on my Homey Pro (2026) since the first crash, sitting at around 70% for an extended period afterwards.
OK, so make sure you don’t set a username or password in the OwnTrack HTTP setup. If you do, Homey rejects the connection before the app even sees it.
I just switch my Android phone from MQTT to HTTP and I was also getting the 401 errors in the OwnTracks logs. As soon as I clear the username and password that was left over from the MQTT setup the connection worked.
I have changed the type from label to text in the next version so that you can copy it on an Android phone. It does mean you can edit it, but any changes will not be saved.