I have setup the Owntracks app on the IOS of my child, and installed the integration on my HA. During setup, ir provided me the url to be used, as well as the authentification key, which I have entered on there app on the mobile phone.
(Except the http://192.168.1.xxx:8123 which I have replaced by http://myservername:8123)
but on the HA, I do not see any entity created.
Also I can not find any way of finding back the web hook URL nor the authentification key I used …
So I am wondering what I can do now ?
How Can I test it / is there z way to force Owntracks app to send its location to the HA to test ?
Noone to help in here ?
I still have no entities created under the intehration, but strangely on the owntracks app of.my son, the entire family is visible on the map ???!?
I do not have owntracks, but the url you use is an internal url that will not work when you are outside your home. It is not unlikely that you’ll need to provide it a https url that is reachable from outside your home to work, even while still at home.
I now see you also posted a day ago in another existing thread on how to configure owntrackes on ios. The top of this post describes how to do it, and it is with an entirely different url than you show here. So have you actually read the other post and tried to follow the instructions? Did you see what others did to solve their problems? There’s a lot of information there.
But anyways, if your home assistant is not open to the outside world, using ssl, and you are not using that to configure the phones, then it will never do anything useful. It will only be able to show home. You do not need owntracks for that, a wifi based sensor will do that too.
If you need an alternative, I would advise first to see if the Home Assistant Companion app is working for you.
Putpose is well to track the phones when abroad, and my HA is open to the exterior, via the http://myserver:8123 … that is why I changed the proposed URL from http://192.168.1.10:8123 towards the other one.
And yes, the full URL provided by the integration is something like this :
P.S. Companion app on the iPhone is only giving very rare updates, compared to the frequent updates of the companion app on Android, as I posted here :
Are you absolutely sure you opened up HA to the internet using a http: url? Because that is very insecure. You have opened yourself up to all kinds of trouble.
Also, the full url you show still uses a 192.168.x.x ip and that is a local ip. It won’t work from the outside.
How exactly did you open up your instance to the internet?
I’m not suggesting you do not open it to the world, I’m suggesting to do so using one of the many guides to protect it at least with https. If you already have your own domain, it is even easier. If you opened your nas without https too, that is even worse.
But you still have not told how you opened it up. Did you open the port and use NAT to forward it to the nas? Did you forward it to the same port?
Can you open the dashboard from outside using the base url you use for the webhook?
By unchecking that box you are allowing http connections to remain http connections for the nas. That is not safe, but also not where the insecurity begins.
What you still do not say is how your router even allows connections from outside to go to your NAS. I’m guessing you opened a port and used NAT port forwarding. That is not safe. If you can access your NAS or Home Assistant with http, that is not safe.
When you login to your NAS or Home Assistant or your NAS with http, anyone can see your login and password and everything that you do. And they can do the same. Nothing is tehn preventing them from doing anything you can do, including installing whatever they want on your NAS or HA, and let your NAS or HA then go on and attack everything else in your home. So for your own safety I stop helping you make your home even more insecure by adding Home Assistant to the list that they can exploit.
Your first assignment is to close down all http access to your NAS and Home Assistant from outside to your home, and set it up for https instead. Then continue on owntracks.
I should remove the 5000 port I believe from there.
Also this is for the NAS … my Home Assistant also runs on the NAS via a virtual machine installed on it … so I believe if I delete the port 5000 on my router, then the HA will also be “secured” as only accessible through port 5001, which is HTTPS right ?
Most of it sounds good. If your NAS can provide the ssl for your Home Assistant: that I don’t know, but I suspect that isn’t so. I think it will require Home Assistant to provide its own certificates. Personally I use Nabu Casa, so I do not need to provide my own ssl. I did experiment with Cloudflare and hade it working, but Nabu Casa offers more that I like.
There are many guides to use letsencrypt to set up ssl (possibly together with duckdns). Do you have a fixed external ip address or a dynamic one? Is the domain you use one that the synology nas provided for you?
Hello, that is the next step because indeed I have a certificate, but I see the site is still showned as “unsecure”, as you can see below. I have opened a case to synology forum to see how to fix this, because I do not understand :
I have a certificate installed and seems to be still valid on the NAS :
I do not have a fixed IP adress, it is changing every 2 days I think (so dynamic) … but I have my own domain name. The NAS is doing the job for me by linking the dynamic IP adress (read from the provider) to my DDNS :
