Voice assist troubles

[remote coral]

I have a "Jarvis" programmed with Extended Open AI, and a "MASS" also programmed with Extended Open AI. Jarvis controls my voice assist, MASS controls the Music Assistant integration. Currently, when I ask Jarvis to play a song on a specific speaker it will reply that it is either off, and will ask to turn it on (which it does), or say that it is playing. The problem is it never actually plays music or changes what Music assistant is queued to play.

[stiff ruin]

What do your system logs say? Usually it would show what it tried to do on the MA side

[remote coral]

well now Im getting this

Unexpected error during intent recognition (intent-failed) Unexpected error during intent recognition (intent-failed)

[stiff ruin]

Would need to check the ha logs and see what went wrong

[rough prism]

FYI for next time this is not a player provider question nor is it MA so should be in the #lounge

[remote coral]

it hasnt had this issue yet, so I think for the most part it is MA. Im not sure where to put it otherwise

https://community.home-assistant.io/t/sentence-parsing-works-but-voice-assist-fails-with-music-assistant/801040

thhis guy is having the same issue

[stiff ruin]

You need to check the ha log because THAT is the intent handler, not MA

If the intent malfunctions, HA logs would explain why

Could be several reasons that it could fail. Even the LLM itself can cause issues

[open perch]

Did you found a solution? I get this too with the following logs:

2024-12-08 11:44:12.014 ERROR (MainThread) 
[homeassistant.components.assist_pipeline.pipeline] Unexpected error during intent recognition
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 1057, in recognize_intent
    intent_response := await conversation.async_handle_intents(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self.hass, user_input
        ^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/conversation/__init__.py", line 233, in async_handle_intents
    return await default_agent.async_handle_intents(user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 1351, in async_handle_intents
    conversation_result = await self._async_process_intent_result(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        result, user_input
        ^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 441, in _async_process_intent_result
    intent_response = await intent.async_handle(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<10 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 121, in async_handle
    raise UnknownIntent(f"Unknown intent {intent_type}")
homeassistant.helpers.intent.UnknownIntent: Unknown intent MassPlayMediaOnMediaPlayer
2024-12-08 11:44:12.225 ERROR (MainThread) [frontend.js.modern.202411276] Uncaught error from Chrome 131.0.0.0 on Windows 10
ReferenceError: Cannot access 't' before initialization
unsub (src/dialogs/voice-command-dialog/ha-voice-command-dialog.ts:404:12)
callback (node_modules/home-assistant-js-websocket/dist/connection.js:23:33)
forEach (node_modules/home-assistant-js-websocket/dist/connection.js:15:25)

[stiff ruin]

Is that on the new HA core integration? If so, voice commands don't work with it

Only the HACS one presently works with voice commands

[open perch]

Gotcha, I was missing that info 🙂

[raw violet]

Is that true? It should be listed in the docs if so, which it isn't.

[stiff ruin]

it is actually

If you go to https://music-assistant.io/integration/voice/

right at the top of the page is a banner that says "AVAILABLE VIA HACS INTEGRATION ONLY"

[open perch]

Will it work at any moment, or should I just revert to HACS version?

[raw violet]

Hmmm, TBF, I'm confused with the docs.... Yesterday, when I was upgrading, I landed on a page which was specifically describing the differences, I cannot find it now. But it is irrelevant, since I just read Marcel's post on voice commands being dropped from MA. I guess we need be a bit patient in the turbulent transition....

[stiff ruin]

Yeah at the moment the core integration doesn't seem to have anything, not sure when/if they are going to do anything about it on the MA side, or if HA is going to add something for it, it's a bit unclear. That's why I am saying on HACS until I hear more 😅

[raw violet]

The was something about blueprint.... It was in general channel here...

[stiff ruin]

Yeah I kinda remember that

[raw violet]

#homeassistant-integration message

[stiff ruin]

Yeah, the native part is what I am curious about

[rough prism]

Further enhancements to the core integration are planned for next month. How much gets done depends on the devs other work. For those that need the advanced functionality just sit tight on the HACS integration as it is working fine.