Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sorry, I am not aware of any area called play rock. #2

Open
sobchek opened this issue Jan 7, 2025 · 3 comments
Open

Sorry, I am not aware of any area called play rock. #2

sobchek opened this issue Jan 7, 2025 · 3 comments

Comments

@sobchek
Copy link

sobchek commented Jan 7, 2025

I have been using custom sentences and intent_script for basic voice control of music assistant with the core integration. Wasn't working until the latest update, but once updated it was working at a simple level. Saw this blueprint and installed it with the default media player. It created the automation, and it all looks good to me, but every search returns something like:

"Play rock the casbah by the clash"

"Sorry, I am not aware of any area called play rock"

Is there some additional step im missing? The issue seems to stem from 'no valid targets.'

Music Assistant server: 2.3.5
Core: 2025.1.1
Supervisor: 2024.12.3
OS: 14.1


``` stage: done
run:
  pipeline: 01j63nxzvp20gxge71fm3ydd1k
  language: en
  runner_data:
    stt_binary_handler_id: null
    timeout: 300
events:
  - type: run-start
    data:
      pipeline: 01j63nxzvp20gxge71fm3ydd1k
      language: en
      runner_data:
        stt_binary_handler_id: null
        timeout: 300
    timestamp: "2025-01-07T16:33:33.061501+00:00"
  - type: intent-start
    data:
      engine: conversation.home_assistant
      language: en
      intent_input: play rock the casbah by the clash
      conversation_id: null
      device_id: null
      prefer_local_intents: false
    timestamp: "2025-01-07T16:33:33.061606+00:00"
  - type: intent-end
    data:
      processed_locally: true
      intent_output:
        response:
          speech:
            plain:
              speech: Sorry, I am not aware of any area called play rock
              extra_data: null
          card: {}
          language: en
          response_type: error
          data:
            code: no_valid_targets
        conversation_id: null
    timestamp: "2025-01-07T16:33:33.451827+00:00"
  - type: run-end
    data: null
    timestamp: "2025-01-07T16:33:33.451866+00:00"
intent:
  engine: conversation.home_assistant
  language: en
  intent_input: play rock the casbah by the clash
  conversation_id: null
  device_id: null
  prefer_local_intents: false
  done: true
  processed_locally: true
  intent_output:
    response:
      speech:
        plain:
          speech: Sorry, I am not aware of any area called play rock
          extra_data: null
      card: {}
      language: en
      response_type: error
      data:
        code: no_valid_targets
    conversation_id: null
@marcelveldt
Copy link
Member

the sentences in the blueprint need to be extended to add more phrases.
Currently its a bit strict. Probably "play the album rock the casbah by the clash would probably work. So specify the media type

@sobchek
Copy link
Author

sobchek commented Jan 8, 2025

the sentences in the blueprint need to be extended to add more phrases.

Currently its a bit strict. Probably "play the album rock the casbah by the clash would probably work. So specify the media type

I removed the blueprint sentences and replaced them with much simpler versions like "play the song {media_name} by {artist}" and started getting matched intents and the correct response from MA and media player.

Will have to slowly experiment with adding more complexity back in to the sentences to see how far it can go.

Also to note, adding more than one sentence with modifications, like an additional sentence for "listen to the song {media_name} by {artist}" broke the automation and couldn't match intents anymore.

@marcelveldt
Copy link
Member

Feel free to suggest improvements and/or your experiences

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants