Android 2021.12: Wear OS Beta!

Nop, noth’ng shows in HA log, I will try to install android studio as you suggest

Error Logcat when I open home assistant application on my watch and click switch:

2022-03-12 23:23:04.829 372-413/? E/BatteryDump: !@new_battery_dump : 4202,-29,2000,168,87,280,DisChg,None,Good,NONE,0,Normal,0,0,12600,1,0,0x77,0x86,0x0f,0x5e,0x01,0x34,0x00,0x01,0,0,8613,4229,0,0
2022-03-12 23:23:06.068 567-721/? E/PkgPredictorService-Collector: record changed bt=1  wifi=1 screen=0
2022-03-12 23:23:06.402 1186-1186/? E/pageboostd: Received HALT command code 2
2022-03-12 23:23:06.583 421-453/? E/BufferQueueProducer: [com.samsung.android.wearable.sysui/com.google.android.clockwork.sysui.mainui.activity.SysUiActivity#0](id:1a5000001c9,api:0,p:-1,c:421) disconnect: not connected (req=1)
2022-03-12 23:23:09.625 567-1233/? E/TaskPersister: File error accessing recents directory (directory doesn't exist?).
2022-03-12 23:23:10.252 15641-16845/? E/SensorReceiver: Exception while updating sensors.
    io.homeassistant.companion.android.common.data.integration.IntegrationException: com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
     at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 0]
        at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl.updateSensors(IntegrationRepositoryImpl.kt:607)
        at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl$updateSensors$1.invokeSuspend(Unknown Source:15)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
        at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:39)
        at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
     Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
     at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 0]
        at com.fasterxml.jackson.databind.DeserializationContext.reportInputMismatch(DeserializationContext.java:1741)
        at com.fasterxml.jackson.databind.ObjectReader._initForReading(ObjectReader.java:359)
        at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:2041)
        at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1459)
        at retrofit2.converter.jackson.JacksonResponseBodyConverter.convert(JacksonResponseBodyConverter.java:33)
        at retrofit2.converter.jackson.JacksonResponseBodyConverter.convert(JacksonResponseBodyConverter.java:23)
        at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:243)
        at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:153)
        at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:923)
2022-03-12 23:23:13.186 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator reporting capabilities
2022-03-12 23:23:13.187 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/intensity
2022-03-12 23:23:13.187 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:13.189 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:13.189 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:13.190 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:13.194 567-837/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl remote_ver  (2).
2022-03-12 23:23:13.196 567-837/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl vendor command (2).
2022-03-12 23:23:13.197 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: supportsHybridHapticEngine
2022-03-12 23:23:13.201 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/hybrid_haptic_engine
2022-03-12 23:23:13.202 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:13.204 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine
2022-03-12 23:23:13.204 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine amplitude : 10000
2022-03-12 23:23:13.204 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine packet_cnt : 1
2022-03-12 23:23:13.204 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine total_size : 4
2022-03-12 23:23:13.205 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine : 4 20 10000 #9 0
2022-03-12 23:23:13.205 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: do_on for timeoutMs: 1
2022-03-12 23:23:13.205 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:1
2022-03-12 23:23:13.206 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:13.206 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine OK
2022-03-12 23:23:13.238 567-567/? E/VibratorService: Vibration finished, cleaning up
2022-03-12 23:23:13.240 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:13.241 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:13.253 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:15.202 421-933/? E/BufferQueueProducer: [Toast#0](id:1a5000001cd,api:0,p:-1,c:421) disconnect: not connected (req=1)
2022-03-12 23:23:16.134 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator reporting capabilities
2022-03-12 23:23:16.134 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/intensity
2022-03-12 23:23:16.134 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:16.140 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:16.140 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:16.141 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:16.149 567-5169/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl remote_ver  (2).
2022-03-12 23:23:16.154 567-5169/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl vendor command (2).
2022-03-12 23:23:16.154 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: supportsHybridHapticEngine
2022-03-12 23:23:16.155 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/hybrid_haptic_engine
2022-03-12 23:23:16.155 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:16.156 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine
2022-03-12 23:23:16.156 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine amplitude : 10000
2022-03-12 23:23:16.156 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine packet_cnt : 1
2022-03-12 23:23:16.157 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine total_size : 4
2022-03-12 23:23:16.157 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine : 4 20 10000 #9 0
2022-03-12 23:23:16.157 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: do_on for timeoutMs: 1
2022-03-12 23:23:16.157 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:1
2022-03-12 23:23:16.158 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:16.158 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine OK
2022-03-12 23:23:16.190 567-567/? E/VibratorService: Vibration finished, cleaning up
2022-03-12 23:23:16.192 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:16.193 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:16.198 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:18.151 421-670/? E/BufferQueueProducer: [Toast#0](id:1a5000001ce,api:0,p:-1,c:421) disconnect: not connected (req=1)
2022-03-12 23:23:28.516 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator reporting capabilities
2022-03-12 23:23:28.517 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/intensity
2022-03-12 23:23:28.517 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:28.519 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:28.520 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:28.520 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:28.526 567-5169/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl remote_ver  (2).
2022-03-12 23:23:28.533 567-5169/? E/VibratorService: [VIB JNI] getInterfaceVersion aidl vendor command (2).
2022-03-12 23:23:28.533 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: supportsHybridHapticEngine
2022-03-12 23:23:28.533 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: isNodeExist node:/timed_output/vibrator/hybrid_haptic_engine
2022-03-12 23:23:28.534 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: true
2022-03-12 23:23:28.536 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine
2022-03-12 23:23:28.536 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine amplitude : 10000
2022-03-12 23:23:28.536 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine packet_cnt : 1
2022-03-12 23:23:28.536 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine total_size : 4
2022-03-12 23:23:28.538 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine : 4 20 10000 #9 0
2022-03-12 23:23:28.538 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: do_on for timeoutMs: 1
2022-03-12 23:23:28.539 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:1
2022-03-12 23:23:28.540 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:28.540 411-411/? E/SecVibrator-HAL-AIDL-EXT: V_2_0: performHybridHapticEngine OK
2022-03-12 23:23:28.572 567-567/? E/VibratorService: Vibration finished, cleaning up
2022-03-12 23:23:28.602 411-411/? E/SecVibrator-HAL-AIDL-CORE: V_1_0: Vibrator off
2022-03-12 23:23:28.602 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: >> writeNode node:/timed_output/vibrator/enable val:0
2022-03-12 23:23:28.605 411-411/? E/SecVibrator-HAL-AIDL-CORE: HW_API: << writeNode node OK : 2
2022-03-12 23:23:30.536 421-453/? E/BufferQueueProducer: [Toast#0](id:1a5000001cf,api:0,p:-1,c:421) disconnect: not connected (req=1)
2022-03-12 23:23:32.957 567-609/? E/Watchdog: !@Sync 183 [2022-03-12 22:23:32.956]
2022-03-12 23:23:34.865 372-413/? E/BatteryDump: !@new_battery_dump : 4195,-36,2000,168,86,280,DisChg,None,Good,NONE,0,Normal,0,0,12600,1,0,0x40,0x86,0x0f,0x5e,0x01,0x34,0x00,0x01,0,0,8603,4228,0,0
2022-03-12 23:23:34.881 741-1142/? E/bt_btif: bta_hf_client_send_at_biev HF indicators 2 is disabled
2022-03-12 23:23:34.881 567-623/? E/BatteryStatsService: Unable to load Power Hal or power.stats HAL
2022-03-12 23:23:34.884 567-623/? E/BatteryStatsService: Unable to load Power Hal or power.stats HAL
2022-03-12 23:23:35.001 312-2077/? E/[email protected]: Error opening event_count for wakeup57: Original kwl [Path]=../../devices/platform/10510000.dwmmc2/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wakeup/wakeup57: Permission denied
2022-03-12 23:23:35.001 344-344/? E/audit: type=1400 audit(1647113014.999:3890): avc:  denied  { read } for  pid=312 comm="Binder:312_3" name="event_count" dev="sysfs" ino=38832 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R870_11_0004 audit_filtered
2022-03-12 23:23:35.002 344-344/? E/audit: type=1400 audit(1647113014.999:3891): avc:  denied  { read } for  pid=312 comm="Binder:312_3" name="max_time_ms" dev="sysfs" ino=38837 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R870_11_0004 audit_filtered
2022-03-12 23:23:35.002 344-344/? E/audit: type=1400 audit(1647113014.999:3892): avc:  denied  { read } for  pid=312 comm="Binder:312_3" name="wakeup_count" dev="sysfs" ino=38833 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R870_11_0004 audit_filtered
2022-03-12 23:23:35.002 344-344/? E/audit: type=1400 audit(1647113014.999:3893): avc:  denied  { read } for  pid=312 comm="Binder:312_3" name="total_time_ms" dev="sysfs" ino=38836 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R870_11_0004 audit_filtered
2022-03-12 23:23:35.002 344-344/? E/audit: type=1400 audit(1647113014.999:3894): avc:  denied  { read } for  pid=312 comm="Binder:312_3" name="expire_count" dev="sysfs" ino=38834 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 SEPF_SM-R870_11_0004 audit_filtered


logcat is too big when i chose Verbos does not fit in here.

Can you please open an issue on GitHub with this error? Would be easier to do troubleshooting there. Definitely something we need to fix, make sure to fill out the issue template when submitting.

at which link?

1 Like

That is a pity not working in old HA versions… I thought the app for wearos would get the “actions” from the mobile app for home assistant, not from the actual server…basically like almost every app I’m using for wearos…was that problem for you when you choose the architecture for the wearos app?? I’m not an expert but if it was like this for me for example would work because the mobile app I’m currently using the last beta version and is OK…
Just a comment for knowing
thanks a lot.

Not at all, you cant expect developers to support something more than 2 years old lol.

our app is a standalone Wear OS app meaning that the app is designed to function without the phone. The phone app is used to make some actions easier but the watch can do everything on its own.

apps can chose how they want to implement features, some apps are just an extension of the phone app. In our case we are a complete app.

I have no idea what you are saying here. You need to update HA core, if you want to continue to enjoy new HA features its on you to make sure your up to date. You cannot judge any of the issues you see until you do so.

Hey thanks for the Quick reply. I really appreciate your job and the rest of the people involved in the HA community. Maybe I didnt clarify this…and writing sometimes we miss feelings. I do not have any complaints at all I totally understand and appreciate your time and the other people. It was just to know, and you have been super clear. Now I know. I don’t judge at all any job done. Again I say very good job and thanks!!!

Does anyone have a link to the Wear OS app in the Play Store?

I can’t find it doing a search. Or at least it’s not in the top 50 items that I can see.

In the phone app go to Configuration > Companion App > Wear OS and you’ll see a button to install the app

Keep in mind Wear OS 2.0+ is supported only

1 Like

Well, there it is…!

thanks!

1 Like

next question is how do I enable location tracking for the watch?

it created the device_tracker entity but it has never updated and only ever shows “unknown”.

all the other sensors seem to be working.

location tracking is not supported yet, the mobile app integration always creates a device tracker which is why its visible.

Ok, thanks.

At least I can stop trying to figure out what I’m missing. :slightly_smiling_face:

So any solution to problems above not switching switches and buttons on WearOS?

Before coming on a forum post, you should really check and respond to the issue you created.

no response there, app does not work unfortunately.

What do you mean no response there? Did you even click on the link?

Of cause, just one reply that it shoudn’t do this and that and that log is short, long log does not fit there. Anyways may forget about watch app, till someone get it fixed. No complaint, just stating the fact, I do not have time to deal with this for now. I may fix it myself…
UPDATE:
Very strange I have reinstalled app and it started working now.