It is the same with the older app, was just looking at the app version on my old pixel and it had not been updated, where as my samsung has been updated and they both have the same problem.
lets try this
on you configuration.yaml add this
homeassistant:
auth_providers:
- type: trusted_networks
trusted_networks:
- 10.0.0.0/8
- 192.168.0.0/16
allow_bypass_login: true
- type: homeassistant
change the ip range to yours
this will allow devices on your local network (like your phone) to login without OAuth tokens.
Look like my pixel is showing 2025.6.6-full which is higher than what you posted.
i know you go lower older app
Nope same issue. I am going to restore my HA from an earlier backup before I ran these last rounds of updates.
did you add trusted_network?
post the bug here , not sure what else can do
I have never had to update the yaml before for it to work.
it was a test but ok , i hope you can solve it i dont know what else can be
yea, I am going to restore and see, I have a backup of my system from 6/15 before I did the last round of upgrades, so will see if it works fine after restoring to that version.
i dont think after all the test is from homeassistant or you companion app , must be something from your network
maybe you had a duckdns or another integration app causing the issue
I don’t use duckdns
I have some bubble cards, and a couple of add-ons but they were all working before.
do you have nabucasa subscription?
yes i have nabucasa
did you try with the nabucasa url https: ? instead of a local ip?
I just restored and was able to connect with the app. I am back on HA below, can see updates are needed but may wait maybe someone else will report an issue an it get fixed in a later version.
- Installation methodHome Assistant OS
- Core2025.5.3
- Supervisor2025.06.2
- Operating System15.2
- Frontend20250516.0
These are the upgrades I need, I will eventually try and do some testing by upgrading each item 1 by 1 and see if I can launch the android app after they are upgrade to see which one breaks it.
im on 2025.7.1 without a problem what does the browser_mod do?
edit
After restarting Home Assistant, all Browsers will need a reload to download the latest version of Browser Mod javascript file. Version 2.4.0 includes a notification when a Browser version mismatch is detected, so from 2.4.x onwards simply clicking Reload should be sufficient. If you keep getting the notification, you may need to do a hard Browser reload SHIFT+F5 or in some cases clear your Browser cache.
i think this is the cause of all your problems
seem like uninstalling the android app and reinstalling would have reloaded the settings.
Will try upgrading Assistant core and see if It works.