Troubleshooting

Troubleshooting

← Documentation home · Getting started · YAML Cookbook · Troubleshooting

---

Resume TV alerts (exact steps)

Camera, announcement, timer, and weather popups use a separate receiver from the main voice connection. Even if TALK works and the main screen says Connected, the alert receiver can drop after standby, a TV power cycle, an app update, or a Home Assistant reload.

Exact on-TV path (v0.16.6 and newer):

1. Open Kellie's Voice on the TV (not Android/Google TV system Settings).
2. On the main screen choose SETTINGS with the remote.
3. Open Alerts & cameras → TV alert status and press OK.
4. In the TV alert status dialog, select the Resume TV alerts button at the bottom and press OK.

It is not the neighboring TV announcements & cameras toggle and not the main Connect / reconnect control.

If the Resume button is missing:

• Turn Settings → Alerts & cameras → TV notifications & camera popups ON.
• Confirm a valid Home Assistant connection is configured.
• Allow Android Display over other apps permission for Kellie's Voice.

In Home Assistant: the paired TV's TV alert receiver connected diagnostic should become ON after a successful resume. This means the TV is subscribed — it does not guarantee that any particular popup already rendered. Send a fresh test announcement, camera, or timer. Events that occurred while the receiver was disconnected are not replayed.

Manual Resume has been confirmed on an onn 4K Pro. With v0.16.9, a Home Assistant restart also reproduced a misleading permission-denied status while the receiver was actually disconnected. Pressing Resume restored it without changing account permissions. The original issue #78 is closed, but follow-up automatic recovery work is being tested on the dev branch. This is not proof that reconnection works after standby on every device.

v0.17 Beta: diagnosing a screensaver that does not open on idle

In v0.17.0 (or its matched QA build), open Settings → Screensaver → Screensaver status & recovery → Screensaver status & permissions. If the screen says feature ON, source configured, overlay ALLOWED, but Watcher NOT RUNNING, the preview alone does not establish automatic screensaver support. On the current combined v0.17 QA build, the onn 4K Pro automatically restored Mobile Command after a full reboot without opening Kellie's Voice or pressing Resync (hardware PASS in PR #288). Other Android TV firmware still needs testing. If a device fails, record Boot receiver this boot, Startup, Watcher, and Last Android dream event before manually resyncing. The older Resync workaround belongs to an earlier failed QA build, not the latest verified Onn result. Don't change secure pairing or HA login to troubleshoot a stopped watcher. Normal v0.16.14 release instructions remain above and below.

Connected but no speech is recognized

A TV can show Home Assistant voice: ✓ connected and TV alerts: ✓ connected while YOU SAID: Nothing yet stays unchanged. These labels confirm connections, not that Android has granted access to a usable microphone.

1. Press TALK, say a short phrase, and check for a transcript under YOU SAID.
2. Confirm Android has granted Kellie's Voice the Microphone permission.
3. Open SETTINGS → Voice & microphone → Test microphone hardware. Check that an actual microphone is available, not only an echo-reference or audio playback input.
4. Keep Microphone input checks: Safe for normal use. Try unverified microphone (compatibility override) is for controlled tests of physically present, misclassified inputs; it cannot create a microphone when Android exposes none.
5. If the device has no usable microphone, try a compatible USB mic. Google Assistant's remote microphone may be reserved for Google's own app.
6. Report the actual Android/Google TV device model, Android version, APK/HACS versions and non-sensitive diagnostics in issue #71.

Do not mistake remote focus for a setting: a bright blue row is only the highlighted choice. Disable microphone capture on this TV deliberately blocks recording when activated. For the full menu see Microphone routing.

Other common issues

• No microphone detected / silent STT — some Philips TVs expose only echo-reference or line-in devices that are not usable for speech. As of v0.16.8, those TVs can still incorrectly show Listening; see issue #71. Try a compatible USB microphone and share non-sensitive Hardware microphone diagnostics with the maintainers. Use the unverified microphone override only for troubleshooting genuine, misreported microphones. The Google Assistant remote button is not intercepted.
• Action succeeds in Home Assistant but nothing appears on the TV — check the alert receiver status, pairing ID (must be the TV's pairing ID, not an HA device-registry ID), and that the matching APK and HACS versions are installed.
• "This device doesn't support timers" — Home Assistant's native timer intent was used. Direct kellies_voice.start_timer actions work; voice routing requires extra configuration. See Voice and Timers.
• Signature conflict on update — do not uninstall a signed release just to update. Use the in-app updater or install the newer signed APK over the existing one.

Full repository troubleshooting: docs/TROUBLESHOOTING.md.

Next

• Getting Started
• YAML Cookbook

---

← All documentation · Next: FAQ →