2025.12 OpenAI issue

Configuration Voice Assistant
1

I’ve got issue with OpenAI integration and Voice Assistant after 2025.12. All local questions are working OK but every question that requires OpenAI response causes red circle spinning

2

The same issue here in my Home Assistant after updating from 2025.11 to 2025.12.2.
I saw there’s aready an issue in the HA GitHub, so I think there’s hope for a solution…

3

Anyone found a solution?

4

Anything in the log to help diagnose? Red circle spinning isn’t much to go on. What’s the voice pipeline debug for your assistant say when it does that?

5

I’m back at 2025.11 just for my speakars to work but someone had the same issue with this:

2025-12-07 17:07:25.431 ERROR (MainThread) [homeassistant.components.openai_conversation] Error talking to OpenAI: Error code: 400 - {'error': {'message': 'No tool output found for function call 01KBWRS3MBY5X3V619DFY22Y9C.', 'type': 'invalid_request_error', 'param': 'input', 'code': None}}

and look also here:
https://github.com/home-assistant/core/issues/158445

1 Like
6

Not much, but a bit of ditection…https://support.nabucasa.com/hc/en-us/articles/25764604971421-Status-colors-of-the-LEDs-status-LEDs-on-Home-Assistant-Voice-Preview-Edition

7

Thanks, I know what the vpe looks like when it errors. My point is it tells us absolutely nothing except there’s an error.

The other link is extremely helpful, thanks @grozanski looks like it’s been reported.

8

Processing built-in commands and user automations as tools, which appeared in the December update, and adding them to the general chat log causes chaos in the request structure. This breaks some APIs.
If the provider’s requirements do not match the request sent by the integration, this will lead to similar errors.

1 Like
9

For what its worth, I upgraded VAPE to 2025.12.1 yesterday and encountered a similar problem (I have no real correlation that this is a firmware version problem):

  • LED Circle turned Red after speaking intent;
  • the Conversation Agent pipeline Debug showing NLP with a “X” (implying it did not execute) nevertheless the STT output was correct, and there was a statement Unexpected error during intent recognition (intent-failed).

So was going to spend more time today on this, and capture some logs, etc. but for whatever reason it is now working without any problem.

10

Looks like 2025.12.5 fixed the issue for me