I have noticed that the app keeps switching to my local IP in Connection > URL, even though I have repeatedly set my external IP. Anyone else noticed this?
Yes!! I thought I was tripping. I guess I’m okay after all.
I haven’t looked into it because of that. I’ll keep an eye on it and try setting it back to the wan .
1 Like
This appears to be resolved in version 1.0.2 of the app 
If you set the in the base_url in the HTTP http component the discovery detection will show that instead.
If you are using a Dyndns or custom host name to access home assistant externally this is much more useful than the default local IP.
In my case I am using a proxy that is providing HTTPS and a custom name so this is very important for clients that need access in and out of the network.
1 Like
This is still an issue for me on 1.0.3. I have a dyndns address, but when I connect to my home network, the URL in the app switches to the local ip. My router doesnt allow nat loopback, so I cannot use the dyndns address while I’m home. I would be really sweet if I could enter both addresses in the app, to take care of this issue
+1 for this, also have issues with nat loopback. So a switch/mechanic that allows automatic switching to the locally found instance (using the lan ip) and then switching back to the user defined url when no local instance is found anymore (so when switching from wifi to 4g)
One of my short term goals is to allow for an internal and external address. Expect this sometime in May.
Since it already makes use of base_url in the http component it might be worthwhile to build off of that by adding an internal_base_url or something.
Any news on the fix?
Interesting mine does this too
Has this been fixed?
Do anyone know if this is beeing worked on since I’m stuck with NAT-problems which I can’t get around… Would very much like the IOS app to work when connected to my local WIFI as well as when outside my home…