Title:
Android Companion App does not switch from Tailscale URL to Local URL when connected to home Wi-Fi
Description:
I have a connection problem with the Android Companion App since version 2026.5.3.
Environment:
Observed behavior:
- Home Assistant is reachable in the Android browser via the local URL:
http://192.168.178.100:8123
- Home Assistant is reachable in the Android browser via the Tailscale URL:
http://100.84.169.66:8123
- The Companion App works when Tailscale is enabled.
- When Tailscale is disabled but the phone is still connected to the configured home Wi-Fi, the Companion App does not switch to the local URL.
- Instead, the app blocks the connection with:
"Insecure connection blocked"
- In the Companion App server settings, the internal connection URL was shown as "Not set", although Home Assistant itself is configured with the local URL.
Expected behavior:
When the phone is connected to the configured home Wi-Fi, the Companion App should use the local URL:
http://192.168.178.100:8123
When the phone is outside the home network and Tailscale is enabled, it should use:
http://100.84.169.66:8123
Additional information:
This setup worked with the previous app version. The issue appeared after updating to 2026.5.3.
The problem seems to be limited to the Companion App, because both URLs work correctly in the Android browser.
Title:
Android Companion App does not switch from Tailscale URL to Local URL when connected to home Wi-Fi
Description:
I have a connection problem with the Android Companion App since version 2026.5.3.
Environment:
Observed behavior:
http://192.168.178.100:8123
http://100.84.169.66:8123
"Insecure connection blocked"
Expected behavior:
When the phone is connected to the configured home Wi-Fi, the Companion App should use the local URL:
http://192.168.178.100:8123
When the phone is outside the home network and Tailscale is enabled, it should use:
http://100.84.169.66:8123
Additional information:
This setup worked with the previous app version. The issue appeared after updating to 2026.5.3.
The problem seems to be limited to the Companion App, because both URLs work correctly in the Android browser.