For internal connection you can define in the companion which WLAN SSID is a home WLAN of yours.
But sometimes I just activate the VPN of my AVM Fritz!Box. Then my mobile phone is virtually at home and I can do phone calls like at home, access my NAS and all internal servers.
Only the HA app is not able to recognize this circumstance.
The decision if the internal URL should be used should not be dependent on any WLAN. The WLAN SSID does not tell you that you can access your internal network. You could connect your android device with your local intranet via a USB-Ethernet-adapter and a cable. Use bluetooth. Infrared. Whatever.
Who had the idea that the only possible connection for internal networks is Wifi?
OK. Possible solution. Just check if you can access the internal URL. If it is available, you can use it. A Ping returns instantly an error if the server is not available at all, I guess that would happen also when trying the internal URL. If that works, remove that WLAN SSID crap.
you can also bypass the check and use the non-recommended approach on the home network config page in app. The reason to try internal only if available is because some servers respond too slow and adds a delay. Nobody likes a delay on an instant update sensor for example. Also current logic matches iOS.
The beta Android companion app has the option to use the internal connection on any VPN connection. This is wrong in a similar way like the WLAN SSID idea.
On my mobile I use DNS66 for ad blocking. This means that there usually is a VPN active. Only if the right wire guard connection or a special IPsec connection is active, my mobile is connected to the home intranet. So I guess the implementation of the beta companion is not supposed to improve the situation for me.
The Ethernet option has the same problem. If I’d use the USB-C-Ethernet adapter I have on a regular basis, I’m quite sure I wouldn’t only use it at home.
Will try the home network config page next. Could you please give me a link to the documentation? Did not find the right links using Google search.
Just understood what is meant by the delay if the internal URL would be checked by availability.
It would be complete nonsense that every access uses the internal URL while it is not available, and then uses the external if the access fails.
If the internal URL is not available, this should be remembered and only the external URL being used for access. But it should be checked on a regular basis, let’s say every 10 minutes, if the app comes to foreground, if any connection configuration changes (any WLAN active, VPN any change) if the internal URL is available. If it is available, it gets used from that moment for every access. Until any access falls, which switches to the external URL usage.
