Hello everyone I just bought a watch on Wear OS 3.5 (TicWatch 5). And installed the Home Assistant on them. I expected the clock to constantly send heart rate data to the server. However, the data is not sent until the display is switched to the active state (by me).
I tried to disable all the power saving features, but it didn’t help.
Has anyone encountered this problem ?
I have the exact same issue on a Galaxy Watch 5 Pro
Yep, similar issues on a Galaxy Watch 4.
At times, updates just stop coming in.
It might be related to switching the watch to power saving mode. Even after disabling it, updates still do not come in until I go the the watch settings on the companion app.
For samsung watches you guys need to go into the Samsung watch companion app on the phone and grant the HA app background access, its a feature specific to Samsung devices. For ticwatch I am not sure if they call it something else, Wear OS does not allow apps to ignore battery optimizations so not too much we can do.
The problem is really not on the homeassistant side. After the following actions on the watch and smartphone, the sensors began to update properly:
Hi,
Same here with a Xiaomi Watch S2 Pro under Wear OS 3.5, this driving me crazy as Wear OS devices have a very bad battery autonomy so I did some automations under Home Assistant to warn me through Google Home devices and Telegram messages when the watch is low on battery but this works only a few times as the battery level does not update correctly/regularly within HomeAssistant probably because of a power saving mode on the watch or other similar feature to keep battery …
Would love to hear someone has found some informations on how to solve this.
Regards,
lolo
Has anyone fixed the problem in the meantime? I have the same problem with my OnePlus Watch 2R. The Home Assistant sensors are not automatically updated in the background. They are only updated when I open the app on the smartwatch.
Following Wear OS Sensors not update at the background - #5 by 1iverea9er, I gave the OHealth app on my smartphone permission to work in the background and send notifications. Unfortunately, this did not lead to a solution.
Adding on to this because I still haven’t found a fix.
I thought I had solved it when I realized my Galaxy Watch 4 Classic has a setting within the watch to sleep some apps and Home Assistant was listed on it. However, even after removing it from the Sleeping Apps Setting it still doesn’t seem to be resolving the issue.
Steps below in case anyone wants to try it though:
Settings > Battery > Sleeping Apps > Long Press “Home Assistant” > Remove from List
Same thing with OnePlus Watch 3. I wanted to enable BLE Transmitter, but noticed that any other sensor is not working after couple of minutes of inactivity. OHealth has background access enabled 
@spaghetti, have you solved your issue by chance?
now do the same thing with the home assistant app so it can run freely in the background…the update rate will indeed be slower than the phone.
Thanks for idea, however that’s been long done (on the phone side) too, since I use beacon monitoring on Pixel 9 Pro that way successfully when I go outside.
I also notice once the reporting stops, the HA App on WearOS is killed, since if i open it up, it loads from scratch. So that’s the reason i can’t send any commands to the watch or read any sensors, until i open the app again.
you need to do it on the watch app too, Samsung for example does it from their companion app. Pixel watch does not have an option like that. One plus may be different
if you keep the homescreen open you are probably hitting a known bug where the app crashes and indeed at that point the app needs to be reopened. If you open the app and swipe it away that prevents the crash and should keep the app open. Also you need to make sure when you send commands to the watch that the critical format is followed. Alternatively to avoid the crash setup favorite entities and turn on the “show only favorites” option from the watch app settings.
Interestingly, swiping to the right from HA screen goes back to the App list and kills the HA immediately.
However, pressing the homescreen button seems to keep the HA open (if i open it up, no loading icon is present). I guess I need to avoid swiping now to keep it alive 
It lasted once 15 minutes without crash, second time around 5 minutes… third 30 minutes. But eventually HA was closed again and of course didn’t recover.
Things tried so far (unsuccessfully):
adb shell pm disable-user --user 0 com.heytap.wearable.powermanager this disabled Battery App and theoretically the RTOS Processor (BES), but in practice HA is still being shut down after some time. Maybe it has more chance to come back later “randomly”, but not good enough for me.I too am seeing slow sensor updates (battery and sleep sensor) from a Galaxy watch 7. I’ve altered/enabled all of the above to make sure it’s not sleeping/getting killed etc. The sleep sensor is between 1 and 2 hours later when being switched on (though off seems like a few mins).
I also only get battery level changes when I ‘do something’ with the watch, like connect or disconnect from the phone’s bluetooth (when I walk away and come back to the phone). I’d love to get realtime battery updates while it’s charging.
So, i think i have a workaround. HA Tile does not help, however if you use Watchface with complication and select one of the complications as HA Entity State (Like On/Off, not a Button):
then it seems to keep the main Processor active. Of course, battery life will be reduced, but at least there is an option to make HA be useful for me and active BLE Transmitter again.
