home-assistant / home-assistant/android

Microwakeword Suggestions, Requests, and Issues

Open
#6,472 12 comments 9 reactions 0 assignees View on GitHub
Assist bug enhancement
Dominant language
Kotlin
Stars
3.9k
Forks
1.1k
Avg merge
1d 12h
Merged PRs (30d)
81

Description

I'm really not sure if this is a feature request or bug report. A little bit of both? Please move if necessary.

I've been testing out the recent release of the Android app's native wake word. Overall it's been great, it's only using about 15% of my battery, which isn't great, but is *far* better than the 25-50% of some of the 3rd party solutions I've tried in the past, and I am *unbelievably* grateful for the work ya'll have done to bring this feature to the app.

That being said, I have a few suggestions:

1. **As silly as it sounds, the number one thing I *really* want here is the ability to implement a custom wake word. I'd love to be able to put a .tflite file (or analogue) onto my phone storage to use as the voice model (similar to the OpenWakeWord integration on the HA server)**.
I've been chasing this ever since the ability to do so got stripped at some point after the galaxy s2 (or s4, I can't remember) era, I guess roughly when Google Assistant first came out and they decided they just *had* to have their branding in the wakeword for the rest of eternity.

2. **After the mobile app's transcript overlay pops up, the wake word no longer functions. I suspect the assistant pipeline (represented by the overlay) keeps control of the mic away from the wake word pipeline? It'd be nice to be able to use the wake word while the overlay is being displayed.**
Rhasspy Mobile had a [somewhat relevant issue](https://github.com/Nailik/rhasspy_mobile/issues/557) with lack of ceding microphone control, which the developer was able to fix. As awesome and capable as Rhasspy Mobile is, I found it would periodically *eat* my battery and had to stop using it. I'm unsure if that unfortunate battery consumption had anything to do with the microphone control ceding fix.

3. **I currently have the app set to use "Okay Nabu" and have gotten quite a few false positives. A sensitivity dial in the options would be cool.**

Thank you all so much for getting this feature implemented, your hard work is truly appreciated!

**Home Assistant Android app version(s):**
2026.2.3-full (beta version)

**Android version(s):**
16 (Build BP2A.250605.031.A3.S908USQS8GZA1)

**Device model(s):**
Samsung Galaxy S22 Ultra (SM-S908U)

**Home Assistant version:**
Install method - Home Assistant OS
Core - 2026.2.3
Supervisor - 2026.02.2
Operating System - 17.1
Frontend - 20260128.6

**Last working Home Assistant release (if known):**
N/A

**Description of problem, include YAML if issue is related to notifications:**
N/A

**Companion App Logs:**
N/A
```

```

**Screenshot or video of problem:**
N/A
**Additional information:**
N/A

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.