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

Fout: argument of type 'int' is not iterable when parsing #117572

Open
Bram-diederik opened this issue May 16, 2024 · 1 comment
Open

Fout: argument of type 'int' is not iterable when parsing #117572

Bram-diederik opened this issue May 16, 2024 · 1 comment

Comments

@Bram-diederik
Copy link

Bram-diederik commented May 16, 2024

The problem

"{{trigger.slots.artist }}" is parsed as a int in my music integration. I use music assistant. but they say its a hass bug.

I get this executed code in the tracing.

Fout: argument of type 'int' is not iterable
Resultaat:

params:
  domain: mass
  service: play_media
  service_data:
    media_type: artist
    enqueue: play
    media_id: "queens of the stone age"
    entity_id:
      - media_player.snapcast
  target:
    entity_id:
      - media_player.snapcast
running_script: false

with this service call

service: mass.play_media
metadata: {}
data:
  media_type: artist
  enqueue: play
  media_id: "{{trigger.slots.artist }}"
target:
  entity_id: media_player.snapcast

this works.

service: input_text.set_value
metadata: {}
data:
  value: "{{trigger.slots.artist }}"
target:
  entity_id: input_text.mpd_playlist

service: mass.play_media
metadata: {}
data:
  media_type: artist
  enqueue: play
  media_id: "{{ states('input_text.mpd_playlist') }}"
target:
  entity_id: media_player.snapcast

strange thing was that i just became to appear. when i wanted to go to bed. It 1st cached the wrong name playing some thing else then this happened.

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

core-2024.5.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

conversation

Link to integration documentation on our website

https://www.home-assistant.io/integrations/conversation/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @home-assistant/core, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (conversation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of conversation can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign conversation Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


conversation documentation
conversation source
(message by IssueLinks)

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

No branches or pull requests

2 participants