Alexa Intent Slot ID unavailable

[AzonInc]

The problem

It seems like Slot ID values were removed with this PR.
However not everyone is using Slot IDs as Entity IDs only. It would be of great value for custom Skills to have the optional ID field available.

Slot: TramStation
Value: Berlin Main Station
ID: 25698742

Example Intent to pass the Tram Station ID to a Script which is passing it to NodeRED

TramIntent:
  action:
    service: script.turn_on
    target:
      entity_id: tram_request
    data:
      id: {{ TramStationID }}
  speech:
    type: plain
    text:  Okay, i'm looking for the next Tram to {{ TramStation }}

What version of Home Assistant Core has the issue?

2023.1.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

TramIntent:
  action:
    service: script.turn_on
    target:
      entity_id: tram_request
    data:
      id: {{ TramStationID }}
  speech:
    type: plain
    text:  Okay, i'm looking for the next Tram to {{ TramStation }}

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of alexa can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign alexa Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

alexa documentation
alexa source
_{^{(message by IssueLinks)}}

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.