Yes, let’s simplify and keep one server profile only. You can do screenshots before you delete, just in case.
Restart both your Companion app and your HA server, also just in case.
I will toggle off the “VPN Connected” also. At least for now.
To simplify, let’s use IPv4 format in both of the URLs. So not 100.xxx-yyy.ab.net nor homeassistant.xxx-yyy.ab.net nor 192.168.1.ab.net. Only 4 sets of numbers; no alphabet.
The 192.168.1.xx address is the LAN IPv4 address of your HA server. Use that in the Internal connection URL, which has http:// in front of the IP, and :8123 after the IP.
(And should be the same as what you’d see under Local network in Settings → System → Network… For your sanity you will want to make sure this IP address would never change.)
Verify the Internal URL in your mobile browser, when your phone is on home wifi and no Tailscale.
The 100.x address came from your Tailscale admin console for the HA server. Most, if not all, of your Tailscale nodes would have the 100.x address by default. This address would be in your Home Assistant URL
Test this URL in your mobile browser first, when your phone is not on wifi, but on Tailscale.
= = sidebar = =
I understand this (http) URL would work when you are away. And there are other ways to do the same. We can revisit this later if needed.
= = sidebar 2 = =
I wouldn’t know whether 500 being too high or not in your situation / where you live, but probably too high. After we have got the remote connection going, you can run a series of tests and see if higher or lower would work any better.
= = sidebar 3 = =
When you see SM-S931U in Developer Tools, is there a (or a couple of) HA entity that starts with “device_tracker”…? If so, you should be able to see how any of the device_tracker tracks, via the “source_type” attribute. Some of my device_trackers are of gps type, others are of router type. They do not simply use the presence of wifi, or I should say, they do not scan SSID around your phone.