Local Voice Assistant Pipeline Fails To Announce TTS In 2025.5.x

by ADMIN 65 views

The Problem

Upgrading from Home Assistant Core version 2025.4.4 to 2025.5.0 has resulted in a failure of the local Voice Assistant pipeline to announce the TTS response for the first command/pipeline after 10 minutes of idle. This issue persists even after downgrading to previous versions, including 2025.0, 2025.1, and 2025.2. The pre-announce audio cue plays, but the announcement itself does not.

Symptoms and Reproduction Steps

To reproduce the issue, follow these steps:

  1. Upgrade to Home Assistant Core version 2025.5.0.
  2. Speak the wake word and ask a question, such as "What time is it?"
  3. The pre-announce audio cue plays, but the TTS response is not announced.
  4. Speak the wake word again and ask the same question.
  5. The pre-announce audio cue plays, and the TTS response is announced.
  6. Wait for 10+ minutes.
  7. Speak the wake word and ask the same question.
  8. The pre-announce audio cue plays, but the TTS response is not announced.
  9. Speak the wake word again and ask the same question.
  10. The pre-announce audio cue plays, and the TTS response is announced.

Troubleshooting Attempts

Several troubleshooting attempts have been made to resolve the issue:

  • Downgrading to Home Assistant Core version 2025.4.4 resolves the issue.
  • Upgrading to previous versions, including 2025.0, 2025.1, and 2025.2, does not resolve the issue.
  • The Voice Assistant debug logs appear identical for successful and unsuccessful pipelines.
  • Piper logs do not show any suspicious activity.

System Configuration

The system is running Home Assistant OS with a USB speakerphone.

Integration and Diagnostics Information

  • Integration causing the issue: No response.
  • Link to integration documentation on our website: No response.
  • Diagnostics information: No response.

Example YAML Snippet

Additional Information

No additional information is available.

Conclusion

The local Voice Assistant pipeline fails to announce the TTS response for the first command/pipeline after 10 minutes of idle in Home Assistant Core version 2025.5.0. This issue persists even after downgrading to previous versions. Further investigation is required to resolve this issue.

Recommendations

Based on the symptoms and troubleshooting attempts, the following recommendations are made:

  • Further investigation is required to identify the root cause of the issue.
  • The Voice Assistant debug logs and Piper logs should be reviewed in more detail to identify any suspicious activity.
  • The system configuration and integration settings should be reviewed to ensure that they are correct and up-to-date.

Future Development

To resolve this issue, the following development steps should be taken:

  • Review the Voice Assistant code and identify any potential issues or bugs.
  • Investigate the Piper logs and Voice Assistant debug logs to identify any suspicious activity.
  • Update the system configuration and integration settings to ensure that they are correct and up-to-date.

Timeline

The following timeline is proposed to resolve this issue:

  • Week 1: Review the Voice Assistant code and identify any potential issues or bugs.
  • Week 2: Investigate the Piper logs and Voice Assistant debug logs to identify any suspicious activity.
  • Week 3: Update the system configuration and integration settings to ensure that they are correct and up-to-date.
  • Week 4: Test the Voice Assistant pipeline to ensure that the issue is resolved.

Resources

The following resources will be required to resolve this issue:

  • Voice Assistant code and documentation.
  • Piper logs and Voice Assistant debug logs.
  • System configuration and integration settings documentation.

Conclusion

Q: What is the issue with the local Voice Assistant pipeline in Home Assistant Core version 2025.5.0?

A: The local Voice Assistant pipeline fails to announce the TTS response for the first command/pipeline after 10 minutes of idle. This issue persists even after downgrading to previous versions, including 2025.0, 2025.1, and 2025.2.

Q: What are the symptoms of this issue?

A: The symptoms of this issue include:

  • The pre-announce audio cue plays, but the TTS response is not announced.
  • The issue only occurs after 10 minutes of idle.
  • The issue persists even after speaking the wake word and asking the same question multiple times.

Q: What troubleshooting attempts have been made to resolve this issue?

A: Several troubleshooting attempts have been made to resolve this issue, including:

  • Downgrading to Home Assistant Core version 2025.4.4 resolves the issue.
  • Upgrading to previous versions, including 2025.0, 2025.1, and 2025.2, does not resolve the issue.
  • The Voice Assistant debug logs appear identical for successful and unsuccessful pipelines.
  • Piper logs do not show any suspicious activity.

Q: What system configuration is being used?

A: The system is running Home Assistant OS with a USB speakerphone.

Q: What integration and diagnostics information is available?

A: The following integration and diagnostics information is available:

  • Integration causing the issue: No response.
  • Link to integration documentation on our website: No response.
  • Diagnostics information: No response.

Q: What is the proposed timeline to resolve this issue?

A: The proposed timeline to resolve this issue is as follows:

  • Week 1: Review the Voice Assistant code and identify any potential issues or bugs.
  • Week 2: Investigate the Piper logs and Voice Assistant debug logs to identify any suspicious activity.
  • Week 3: Update the system configuration and integration settings to ensure that they are correct and up-to-date.
  • Week 4: Test the Voice Assistant pipeline to ensure that the issue is resolved.

Q: What resources will be required to resolve this issue?

A: The following resources will be required to resolve this issue:

  • Voice Assistant code and documentation.
  • Piper logs and Voice Assistant debug logs.
  • System configuration and integration settings documentation.

Q: What is the expected outcome of resolving this issue?

A: The expected outcome of resolving this issue is that the local Voice Assistant pipeline will be able to announce the TTS response for the first command/pipeline after 10 minutes of idle, without any issues or errors.

Q: What are the next steps to resolve this issue?

A: The next steps to resolve this issue are to:

  • Review the Voice Assistant code and identify any potential issues or bugs.
  • Investigate the Piper logs and Voice Assistant debug logs to identify any suspicious activity.
  • Update the system configuration and integration settings to ensure they are correct and up-to-date.
  • Test the Voice Assistant pipeline to ensure that the issue is resolved.