#Companion app won't connect to one HA instance after connecting to another

1 messages · Page 1 of 1 (latest)

loud vine
#

I run two HA instances. One at home which I can also access from the internet. The second is at church, which I can only access locally.

At church this morning, I connected my phone (Google Pixel 8, Companion app on auto update) to the church instance and all was good.

I left church and went home, and the app is still trying to connect to the church instance. In the "can't connect" box, I hit the "Settings" selection. When it opens companion app settings, under "Servers & devices" it shows "Add server". Neither of the instances appears there, so I can't select my home instance.

I leave it sitting for a minute (screen timeout) or so, and Android reports "Home Assistant isn't responding" with options to "Close App" or "Wait". I've hit "Wait" several times in a row, but it never populates the list of servers so I can't select my home instance.

Fortunately, the church is only 5 minutes away, so I can easily run back there, connect, then switch back to my home instance, but that's a royal pain. Am I missing something? Is this a bug of some sort? I'm reasonably certain that this isn't the first time I've ever forgotten to switch back, but it's definitely the first time I've had an issue switching from home.

Point me at the phone log location, and I'll happily share that. If there are any other things I need to do/test, let me know.

digital oyster
#

i would start with rebooting HA and phone. Check network for possible ip/dns/time issues.

gleaming star
loud vine
loud vine
digital oyster
#

what happens if you clear the companion app cache?

loud vine
#

Companion App v 2025.8.7-full
Forgot I could look in the phone settings to get that.
Cache cleared. Still no dice.

digital oyster
#

rebooted haos too (no restart)?

loud vine
#

restarted the Docker. That seems to have done the trick.
Interesting, the container had been up for only 32 hours after a power failure Sat evening. Odd that something was wrong when it came back up.

#

tyvm @digital oyster.

digital oyster
#

NP enjoy! @gleaming star maybe your solution too?

loud vine
#

@gleaming star don't know if this will help you...

#

jinx

digital oyster
#

always reboot network and devices first to rule out underlying network issues (it's all in my name)

#

and keep haos updated.

loud vine
gleaming star
#

Both of my HA instances are on mini PC(Generic x86-64). I have tried rebooting HA OS and network but It is not working for me at all.