home-assistant / home-assistant/android

Multiple servers, with one unavailable server breaks device control

Open
#5,298 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Kotlin
Stars
3.9k
Forks
1.1k
Avg merge
1d 12h
Merged PRs (30d)
81

Description

**Home Assistant Android app version(s):**
2025.5.1-full
**Android version(s):**
10
**Device model(s):**
Samsung S10+
**Home Assistant version:**
2025.5.1
**Last working Home Assistant release (if known):**
Unknown
**Description of problem, include YAML if issue is related to notifications:**
Steps to reproduce:
1. Have 2 servers configured in the homeassistant app, one is unavailable. (One of mine is only accessible via a VPN).
2. Attempt to modify device controls.
3. Get a "Couldn't load devices" message, and cant see any buttons, even from the server that should be accessible.

Expected outcome: Show the devices for the server that is reachable, perhaps with an on-screen toast to notify the user that a server was unavailable?

**Companion App Logs:**

[homeassistant_companion_log_4-12-2025_1-1-41.txt](https://github.com/user-attachments/files/20149851/homeassistant_companion_log_4-12-2025_1-1-41.txt)

```

```

**Screenshot or video of problem:**
Nothing really helpful, but it is very easy to reproduce.
**Additional information:**
`app/src/main/kotlin/io/homeassistant/companion/android/controls/HaControlsProviderService.kt:126` suggests that that should already work correctly. I'm guessing that because my second server times out, the caller of `createPublisherForAllAvailable` is timing out, so the failure is at a higher level? Perhaps there needs to be a shorter timeout?
I cant replicate it in a modern android emulator, so I have no idea if this is worth tackling.

Feel free to close if this is a waste of time.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.