home-assistant / home-assistant/android

Wake word opens text input instead of starting voice listening

Open
#7,201 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Kotlin
Stars
3.9k
Forks
1.1k
Avg merge
1d 12h
Merged PRs (30d)
81

Description

**Home Assistant Android app version(s):**

2026.6.5-full (22884)

**Android version(s):**

Please let me know if the exact Android version is required. I can provide it.

**Device model(s):**

Samsung Galaxy Tab A11+

**Home Assistant version:**

Core: 2026.7.2
Supervisor: 2026.07.3
Operating System: 18.1

**Last working Home Assistant release (if known):**

Unknown. This is my first attempt to use Wake Word Detection.

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

Wake Word Detection is enabled and configured with the wake word "Okay Nabu".

The Home Assistant Companion App is configured as the default Android Digital Assistant.

When I say "Okay Nabu", the wake word is detected successfully.

However, instead of immediately starting a voice conversation and listening for my command, the Companion App opens the Assist text input together with the Android on-screen keyboard.

The microphone never starts listening.

The problem occurs every time and is fully reproducible.

Configuration has been checked multiple times:

- Home Assistant is configured as the default Digital Assistant.
- Wake Word Detection is enabled.
- Wake word: "Okay Nabu".
- Voice assistant is configured correctly.
- Conversation agent is working.
- Microphone permission is granted.
- Home Assistant server is reachable and working normally.

The problem appears during the transition from wake-word detection to the Assist voice session.

**Companion App Logs:**

Not available.

I have not attached Android logs because this would require installing Android debugging tools (ADB) only for this issue.

If logs are required, I will try to provide them after receiving instructions from the developers.

**Screenshot or video of problem:**

I will attach screenshots showing:

- Wake Word configuration
- Assist configuration
- Device settings
- Home Assistant version

**Additional information:**

The wake word itself is detected correctly.

The issue is not that Wake Word Detection fails.

The issue is that after successful wake-word detection the application switches to text input mode instead of starting voice listening.

Image

Image

Image

Image

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the configured “Okay Nabu” flow on the reported Android device and inspect the transition from successful wake-word detection to the Assist session. Compare the path that opens text input with the expected voice-listening path, collecting Android logs if needed. Done means the wake word opens Assist with the microphone listening instead of the keyboard.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.