home-assistant
No more local access connection
since updating l'as companion version on m'y Redmi notez13 internal ip nonworkonf anymore, external ip is ok
There are not a lot of details for us to work with here. Does the internal IP address still work in the browser on your phone? Which companion app version did you update to?
Yes internal ip works fine in a the browser of m'y phone I use 2025.5.3-full Sometimes its working with 10 tries. In data mode its perfect Thanks
Same problem here. It doesn't seem to switch to the local URL and stays stuck on the external one, which means that the loopback protection kicks in and you can't connect. A good idea would be to check if the local instance is available when the external one fails.
Yes internal ip works fine in a the browser of m'y phone
That is odd, as the app shouldn't be doing anything different than the browser for finding the IP/domain - it is all handled by the system. Could you check the app logs for the error and post it here? Maybe you have a different issue.
It doesn't seem to switch to the local URL and stays stuck on the external one
This (switching the url to use) sounds like a different problem. Double check your settings and if you think they are correct, please create a new issue so we can keep this one focused.
On home assistant server with tcpdump i can see packets from home assistant companion But still error message, after multiple tries its working
Once again, please check the app logs for the error or give us an exact error message. The fact that the server is receiving packets isn't something we can use to help you right now.
I have the same problem since today. I had the update for about a week. I can access HA on the local ip from my browser no issue. If I disconnect from wifi the app works normal. On my wifi I can't use the app. If I remove my wifi ssd from the home networks in the app everything works fine. I also get a lot of local 127.0 login errors when trein the app. Hope this helps
There's no more option to pick the internal URL to reconnect to if the connection to external fails either. Used to be there. It's as if the app relies too hard on an Android API that has been recently changed?
There's no more option to pick the internal URL to reconnect to if the connection to external fails either. Used to be there. It's as if the app relies too hard on an Android API that has been recently changed?
That's exactly the option I'd like to have. As I understand it the wifi information on Android is locked behind the geoloc being enabled for some ungodly reason. So basically you'd need to have it on at all times and my 2011-ass reflexes tell me to never leave it on to spare the battery.
So simply being able to say "hey if you can't connect here try this as fallback" would be great.
There's no more option to pick the internal URL to reconnect to if the connection to external fails either. Used to be there. It's as if the app relies too hard on an Android API that has been recently changed?
its still there was moved and renamed to help lower confusion on users who were enabling it when they did not need to.
Settings > companion app > select your server > home network and change the bottom drop down option to the non-recommended one.
That option only flips the behavior, it gives a connection failure for external connections instead which have "Use external URL".
There's no reason why it shouldn't allow "Use internal URL" instead when external has been tried and failed, rather than not giving the option.
There's no way to get confused, the button spells out what is going to get used - It'd be even better if the dialog box said it too.
Really actually supporting automatic retry for internal would be much better.
the option is meant to try the internal URL first without caring about location being enabled or the SSID being connected, just to always try that first. Without that the app will only use the internal URL when it thinks it can. The setting just tells teh app to ignore the condition and try anyways.
For the APIs teh app will be able to try and silently fail for internal/external but for the WebView yes indeed you need to click on refresh once or twice.
To be clear, this is still an issue. I set the internal connection URL to be the LAN IP, I had the home network set properly, it detected properly, I even tried enabling the option to "use internal connection URL when loading dashboard and unknown if connected to home network". At no point was the internal connection URL attempted. I've resorted to just setting both URIs to the LAN IP. I'd much rather be able to have the non-local IP set to my SSH tunnel though, since I don't have it exposed to WAN otherwise.
