android: Unable to toggle (activate or deactivate) any Sensors in WearOS Companion App

Home Assistant Android version: 2023.3.0-3260

Android version: Android 11/ Wear OS 3.5

Phone model: Samsung Galaxy Watch 5 (HCYT)

Home Assistant version: 2023.5.2

Last working Home Assistant release (if known): None

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

In the WearOS companion App I am unable to activate or deactivate any sensors. But the sensors that are already activated (like battery level) get reported just fine.

I tried this with the 2023.3.0-3260 and beta-9972-8b32f9bf release version. In both cases I ensured all permissions are enabled and background activity is allowed.

The logs provided were recorded with the 2023.3.0-3260 version

Companion App Logs:

The Relevant Part appears to be the following, as the appeared in the logs every time I tried to toggle a sensor

05-10 10:20:07.284  4757  6970 E SensorReceiver: Error while getting core config to sync sensor status
05-10 10:20:07.284  4757  6970 E SensorReceiver: io.homeassistant.companion.android.common.data.integration.IntegrationException: com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
05-10 10:20:07.284  4757  6970 E SensorReceiver:  at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 0]
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl.getConfig(IntegrationRepositoryImpl.kt:493)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl$getConfig$1.invokeSuspend(Unknown Source:14)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
05-10 10:20:07.284  4757  6970 E SensorReceiver:        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
05-10 10:20:07.284  4757  6970 E SensorReceiver: Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
05-10 10:20:07.284  4757  6970 E SensorReceiver:  at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 0]

But I have also uploaded full logs here homasssistant-wearos-log.txt

Screenshot or video of problem:

https://github.com/home-assistant/android/assets/37292429/20fd2b06-7f67-4188-be02-5fdcc8fd30ee

Additional information:

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 19 (15 by maintainers)

Most upvoted comments

Ah, ok. Missing feature or is there something blocking it from being implemented?

feature depends on reading the WiFi SSID, no watch stays connected long enough to make it reliable.

If I just keep the app open on the screen it’s opened on it eventually crashes.

unrelated to this issue, most likely you are seeing #3325

io.homeassistant.companion.android.common.data.integration.IntegrationException: retrofit2.HttpException: HTTP 404

hmm a 404 error? strange. Maybe something happened to device registration on the watch? Could always try to log out and back in from Settings. Although I typically see a 410 error when device registration is missing.

I also get the feeling that all requests from my watch go through Home Assistant Cloud and not directly to my local Home Assistant instance. 🤔

we only use the external URL for Wear OS, the watch does not handle any URL switching.