I ran a few updates at the same time. I probably shouldn’t have for this very reason, but, I’m here now.
I updated ESP Home, Voice Preview Edition, and Home Assistant Core.
Now, my wyoming Satellites and my Voice Preview edition are MUCH slower to resolve commands.
I used to say “Lights on/off” and it was near instant to respond and turn them on or off.
Now, the lights on the PE spin for 2-4 seconds before the lights finally turn off.
When trying to directly from the Voice Assistant pipeline, it’s instantaneous.
I’m at a loss here to track down where the delay has been introduced, but given that it’s not just the PE, but also a Satellite, both of which were working fine until these updates, I’m inclined to believe it’s the HA core update to 2026.1 that introduced the glitch.
Anyone else seeing this? Anyone found a fix?
Apparently this is the likely culprit
opened 04:53PM - 08 Jan 26 UTC
### The problem
After upgrading to 2026.1 this morning, there's a ~5 second del… ay in speech recognition with Assist. This affects all front end platforms I have available to myself (Android App, Chrome desktop browser).
I've tried using different pipelines (Home Assistant Cloud and local faster-whisper/ollama/piper) and they all have the same issue.
I read comments on the 2026.1 release notes from a couple people saying that the CPU on their host spikes via the homeassistant process during this 5-second delay, but I didn't think to check that before I rolled back to 2025.12.5, which has fixed the issue. I've verified that the faster-whisper process doesn't do anything until after this delay, at which point the process is responsive.
[assist_debug.txt](https://github.com/user-attachments/files/24500323/assist_debug.txt)
### What version of Home Assistant Core has the issue?
core-2026.1.0
### What was the last working version of Home Assistant Core?
core-2025.12.5
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
assist_pipeline: https://www.home-assistant.io/integrations/assist_pipeline/
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
- type: stt-start
data:
engine: stt.faster_whisper_2
metadata:
language: en
format: wav
codec: pcm
bit_rate: 16
sample_rate: 16000
channel: 1
timestamp: "2026-01-08T16:08:10.058638+00:00"
- type: stt-vad-start
data:
timestamp: 1200
timestamp: "2026-01-08T16:08:13.697018+00:00"
- type: stt-end
data:
stt_output:
text: " What time is it?"
timestamp: "2026-01-08T16:08:14.851095+00:00"
```
### Additional information
_No response_
tmjpugh
(Tmjpugh)
January 13, 2026, 9:06pm
2
What are you using for STT and TTS?
You can watch esp device logs in esphome device builder
It will give timing of command so you can see where lag is introduced.
Also how is it when run from phone or PC?
I’ve tried using Home Assistant Cloud for everything, and I’ve also tried using Gemini as the conversation agent.
In troublehsooting with Gemini, we came back with the Proxmox box hadn’t been set to Host for the CPU. So, I did that, and then it came back with a pre and post comparision of the lag.
It appears that the delay is in the Voice Activity Detection (VAD) stage.
I set it to Aggressive to close it out quicker, and it helped… but it’s still much longer than pre 2026.1 (or 2026.1.1)
nokirunner
(nokirunner)
January 14, 2026, 11:46am
4
sileroVAD had been introduced (2026.1), they had tried to make it more performing on less performing devices but it didn’t work (2026.1.1), now with the next release we go back to microVAD and the problem should be solved
dev ← synesthesiam-20260112-revert-vad
opened 11:10PM - 12 Jan 26 UTC
## Breaking change
## Proposed change
Revert back to using [microVAD](… https://github.com/rhasspy/pymicro-vad) due to issues raised after release:
* https://github.com/home-assistant/core/issues/160534
* https://github.com/esphome/home-assistant-voice-pe/issues/522
* https://github.com/home-assistant/core/issues/160493
* https://github.com/rhasspy/pysilero-vad/issues/12
## Type of change
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [ ] I understand the code I am submitting and can explain how it works.
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
- [ ] Any generated code has been carefully reviewed for correctness and compliance with project standards.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
2 Likes
2026.2 fixed it up.
Looks like they reverted to MicroVAD
1 Like
How to update to 2026.2 ?
nokirunner
(nokirunner)
January 21, 2026, 1:01pm
7
It should simply appear in the updates, they also updated the entire Linux OS, now everything is faster than ever, I hope they don’t move anything else because now it’s perfect