alexa_devices using device_id announce duplicates

[DEEJCUK]

The problem

using device_id with announce via dev tools / actions duplicates the announcement making it play twice,device_id is the default if using dev tools
using entity_id does not exhibit this, i was testing using dev tools

now obviously i know how to make it right, but im not sure if this is an intended side effect as i know using some pickers in HAOS use device_id

What version of Home Assistant Core has the issue?

core-2025.6.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

alexa_devices

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

this announces twice (using dev tools / actions)


action: notify.send_message
data:
  message: hello this is an announcement
target:
  device_id: 1ddcXXXXXXXXXXXd31978


this works correctly (only 1 announcement)

action: notify.send_message
data:
  message: hello this is an announcement
target:
  entity_id: notify.echo_plus_announce

Anything in the logs that might be useful for us?

nothing

Additional information

No response

[home-assistant]

Hey there @chemelli74, mind taking a look at this issue as it has been labeled with an integration (alexa_devices) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of alexa_devices 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 alexa_devices 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)}}

---

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

[z-master42]

Why use the device ID or the device at all?

[DEEJCUK]

i dont really understand the question unless its asking Why use the device id at all ?
if so, i answered that in my original message
device_id is the default if using dev tools

if its something else, can you elaborate a bit ?

[z-master42]

Why is the Device ID the default in the developer tools? Nothing is preselected.

Simply use the second case (in your example).

[DEEJCUK]

i did as mentioned
now obviously i know how to make it right, but im not sure if this is an intended side effect as i know using some pickers in HAOS use device_id
this is more for the dev(s) in case its not an intended output, which i doubt it is, why would it be if it does it twice ?

[z-master42]

Is it two announcements in succession or is it one announcement and speaking once? So once with an announcement tone and once without?

[DEEJCUK]

its 2 of the same word or phrase after the announce sound in quick succession, i just tested with 2025.6.2
and only using the device picked from the choose device picker and not when selecting the entity via choose entity

[tricoos]

Same here - just installed the update 2025.6.2 and enabled Alexa Devices: most often the text is spoken twice, but there's only a single notifcation sound. I also just picked the device.
As there is only a single notification sound I doubt it's a configuration issue and the addon simply sends the text twice.

[chemelli74]

If you use the device it I bet that core use all notify entities, so both announce and speak together.

Try using the entity_id of speak and after it played the entity_id of announce and report back.

[tricoos]

@chemelli74 Thanks, that works! I tested it with two scripts and one automation. Simply replacing the device by the speak entity resolved the issue! 👍