Server dropdown in 'Manage tiles' view has no items

[j4k0xb]

Home Assistant Android app version(s): 2026.6.5-full

Android version(s): 16 (Evolution X Custom ROM)

Device model(s): Xiaomi Mi 9T Pro

Home Assistant version:

• Core 2026.6.4
• Supervisor 2026.06.2
• Operating System 18.0
• Frontend 20260527.7

Last working Home Assistant release (if known):

Description of problem, include YAML if issue is related to notifications:

I can't manage tiles because it requires selecting a server, but the dropdown has no items.
Other people also encountered this bug:

• https://www.reddit.com/r/homeassistant/comments/1txnr83/comment/opxymga/
• https://www.reddit.com/r/homeassistant/comments/1txnr83/comment/orhawzh/

Companion App Logs:

--------- beginning of system
06-25 04:02:01.045 24891 24891 D InsetsController: show(ime())
06-25 04:02:01.047 24891 24891 D InsetsController: Setting requestedVisibleTypes to 511 (was 503)
06-25 04:02:01.067 24891 24891 D InsetsController: show(ime())
06-25 04:02:04.831 24891 24891 D InsetsController: Setting requestedVisibleTypes to 503 (was 511)
06-25 04:02:07.287 24891 24891 D InsetsController: show(ime())
06-25 04:02:07.287 24891 24891 D InsetsController: Setting requestedVisibleTypes to 511 (was 503)
06-25 04:02:07.318 24891 24891 D InsetsController: show(ime())
06-25 04:09:31.875 24891 24891 D InsetsController: show(ime())
06-25 04:09:31.875 24891 24891 D InsetsController: Setting requestedVisibleTypes to 511 (was 503)
06-25 04:09:35.810 24891 24891 D InsetsController: Setting requestedVisibleTypes to 503 (was 511)
06-25 04:09:37.421 24891 24891 D InsetsController: show(ime())
06-25 04:09:37.422 24891 24891 D InsetsController: Setting requestedVisibleTypes to 511 (was 503)
06-25 04:09:37.435 24891 24891 D InsetsController: show(ime())
--------- beginning of main
06-25 04:10:19.548 24891 24891 D VRI[Pop-Up Window]: visibilityChanged oldVisibility=false newVisibility=true
06-25 04:10:19.577 24891 24891 D WindowOnBackDispatcher: setTopOnBackInvokedCallback (unwrapped): androidx.navigationevent.OnBackInvokedInput$createOnBackAnimationCallback$1@c715c14
06-25 04:10:19.621 24891 24891 D IntegrationRepositoryImpl: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1782353390917, currentMillis: 1782353419620)
06-25 04:10:19.646 24891 24891 I ImeTracker: io.homeassistant.companion.android:36012d8e: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
06-25 04:10:19.648 24891 24891 D IntegrationRepositoryImpl: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1782353390917, currentMillis: 1782353419648)
06-25 04:10:19.656 24891 24891 D IntegrationRepositoryImpl: setAppActive(): true
06-25 04:10:20.056 24891 13585 D WebSocketCoreImpl: Sending message 484: {type=ping, id=484}
06-25 04:10:20.073 24891 25039 D WebSocketCoreImpl: Websocket: onMessage (text: HIDDEN)
06-25 04:10:20.074 24891 25039 D WebSocketCoreImpl: Message id 484 received
06-25 04:10:50.065 24891 13080 D WebSocketCoreImpl: Sending message 485: {type=ping, id=485}
06-25 04:10:50.082 24891 25039 D WebSocketCoreImpl: Websocket: onMessage (text: HIDDEN)
06-25 04:10:50.082 24891 25039 D WebSocketCoreImpl: Message id 485 received
06-25 04:10:52.922 24891 24891 I ImeTracker: io.homeassistant.companion.android:47a33a96: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
06-25 04:10:52.925 24891 24891 D IntegrationRepositoryImpl: isAppLocked(): false. (LockEnabled: false, appActive: true, expireMillis: 1782353390917, currentMillis: 1782353452925)
06-25 04:10:52.928 24891 24891 D IntegrationRepositoryImpl: setAppActive(): true
06-25 04:10:54.110 24891 24891 D WindowOnBackDispatcher: setTopOnBackInvokedCallback (unwrapped): android.app.Activity$$ExternalSyntheticLambda0@9b8b277
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.174 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.175 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.176 24891 24891 I ImeTracker: io.homeassistant.companion.android:560b8076: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT_CLOSE_CURRENT_SESSION fromUser false
06-25 04:10:54.176 24891 24891 I ImeTracker: io.homeassistant.companion.android:560b8076: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
06-25 04:10:54.683 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.683 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.696 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.714 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.746 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.746 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.766 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.766 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.781 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.798 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:54.817 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:55.962 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:56.414 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:58.825 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:58.908 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:58.961 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:10:59.393 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.242 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.620 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.631 24891 24891 D WindowOnBsackDispatcher: setTopOnBackInvokedCallback (unwrapped): androidx.navigationevent.OnBackInvokedInput$createOnBackAnimationCallback$1@c715c14
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:00.721 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:03.367 24891 24891 E mpanion.android: Invalid resource ID 0x00000000.
06-25 04:11:03.484 24891 24973 D LogcatReader$readLog: Read logcat for pid 24891

Screenshot or video of problem:

Additional information:
I only added a single server to the app.
Server view:

• HA URL: https://<domain>/ in conjunction with a local reverse proxy and DNS server.
• Internal connection URL: Not set.
• Server name: blank (shows default value Home). Setting it to some other value does not fix the issue.

I can provide more details with adb or root if required for troubleshooting.

[j4k0xb]

This fixed it for me (no server dropdown shown as expected for 1 server, can save tiles now) but doesn't run in parallel yet, so someone with more compose and kotlin experience please create a PR.

viewModelScope.launch {
      val servers = withContext(Dispatchers.IO) {
          serverManager.servers()
      }

      this@ManageTilesViewModel.servers = servers

      servers.forEach { server ->
          val serverId = server.id

          val entities = withContext(Dispatchers.IO) {
              loadEntitiesForServer(serverId)
          }

          val entityRegistry = withContext(Dispatchers.IO) {
              loadEntityRegistry(serverId)
          }

          val deviceRegistry = withContext(Dispatchers.IO) {
              loadDeviceRegistry(serverId)
          }

          val areaRegistry = withContext(Dispatchers.IO) {
              loadAreaRegistry(serverId)
          }

          this@ManageTilesViewModel.entities[serverId] = entities
          this@ManageTilesViewModel.entityRegistries[serverId] = entityRegistry
          this@ManageTilesViewModel.deviceRegistries[serverId] = deviceRegistry
          this@ManageTilesViewModel.areaRegistries[serverId] = areaRegistry
      }

      selectTile(slots.indexOf(selectedTile))
}

LLM explanation based on the above code and manual debugging:

---

The server dropdown could appear in an invalid “empty” state even when only a single server was configured.

Root cause

The issue was caused by inconsistent initialization timing between:

• servers being loaded
• per-server entity/registry maps being populated asynchronously
• selectedServerId being derived inside selectTile() using a fallback (serverManager.getServer())

Although servers was already assigned, selectTile() could still execute while the view model was in a partially initialized state. In particular, selectedServerId could temporarily diverge from the actual servers list (e.g. due to fallback selection or DB values), which made this condition intermittently true:

servers.none { it.id == selectedServerId }

android/app/src/main/kotlin/io/homeassistant/companion/android/settings/qs/views/ManageTilesView.kt

Lines 139 to 147 in 712bee1

	if (viewModel.servers.size > 1 || viewModel.servers.none { it.id == viewModel.selectedServerId }) {
	ServerExposedDropdownMenu(
	servers = viewModel.servers,
	current = viewModel.selectedServerId,
	onSelected = viewModel::selectServerId,
	title = R.string.tile_server,
	modifier = Modifier.padding(top = 16.dp),
	)
	}

This caused the UI to incorrectly render the server selector even when only one server existed, sometimes resulting in an empty or inconsistent dropdown state.

Contributing issue

The original coroutine structure also contributed to the problem: per-server initialization used nested launch calls inside an async, which were not part of the awaitAll() synchronization boundary. This allowed selectTile() to run before all server-dependent state (entities and registries) was fully populated.

awaitAll() only waits for the outer async blocks. The inner launch coroutines are fire-and-forget relative to that async. So the outer awaitAll() can complete while inner work is still running.

android/app/src/main/kotlin/io/homeassistant/companion/android/settings/qs/ManageTilesViewModel.kt

Lines 197 to 213 in 712bee1

	viewModelScope.launch(Dispatchers.IO) {
	val servers = serverManager.servers()
	this@ManageTilesViewModel.servers = servers
	servers.map { server ->
	val serverId = server.id
	async {
	launch { entities[serverId] = loadEntitiesForServer(serverId) }
	launch { entityRegistries[serverId] = loadEntityRegistry(serverId) }
	launch { deviceRegistries[serverId] = loadDeviceRegistry(serverId) }
	launch { areaRegistries[serverId] = loadAreaRegistry(serverId) }
	}
	}.awaitAll()
	withContext(Dispatchers.Main) {
	// The entities list might not have been loaded when the tile data was loaded
	selectTile(slots.indexOf(selectedTile))
	}
	}

Fix

• Reworked initialization to load all server-dependent data in a deterministic sequence
• Ensured all per-server entities and registries are fully loaded before calling selectTile()
• Removed the window where selectedServerId and servers could be temporarily inconsistent

Result

• Server dropdown is now only shown when there are actually multiple servers
• No more empty or transient dropdown state when a single server exists
• Initialization is now fully deterministic and free of partial-state UI rendering artifacts

---

[oungsi2000]

I'm currently on this. Probably it seems Jetpack Compose bug. see also https://youtrack.jetbrains.com/projects/CMP/issues/CMP-8595/MutableState-update-on-IO-thread-doesnt-recompose

[TimoPtr]

It is indeed the issue.