you can try it this way
- service: notify.alexa_xxxx
data:
data:
type: announce
target:
- media_player.alexa_device
message: "Hey your message goes here"
I was able to get the automation to fire when the text box data is changed. But it reads the message line starting at states, not what is typed in the box.
- alias: Announce Input to all alexa
trigger:
- platform: state
entity_id: input_text.alexa_tts
action:
- service: notify.alexa_media
data:
target:
- media_player.living_room
#title: "My title for Echo show"
data:
type: announce
#method: all
message: {{ states('input_text.alexa_tts') }}
This is how i got mine setup and it is working for me.
### Alexa Instant Script As A package ##
## Input Text
input_text:
text1:
name: manual_message
initial: 'Enter Yor Text Here'
## Input Select
input_select:
message_target:
name: Type Of Broadcast
options:
- "media_player.alexa1"
- "media_player.alexa2"
- "media_player.alexa3"
- "group.alexa_all"
initial: "media_player.alexa1"
icon: mdi:speaker-wireless
### Script Config###
Script:
instant_message:
sequence:
- service: notify.alexa_media
data_template:
target: '{{ states.input_select.message_target.state }}'
data:
type: announce
message: '{{ states.input_text.text1.state }}'
### group ###
group:
alexa_media_scripts:
name: Alexa Announcements Scripts
icon: mdi:script
entities:
- script.instant_message
- input_select.message_target
- input_text.text1
###########################################
# Lovelace Card #
###########################################
- type: horizontal-stack
cards:
- type: entities
entities:
- entity: input_text.text1
name: Alexa Broadcast
type: 'custom:text-input-row'
- entity: input_select.message_target
name: Speakers
- action_name: To Run...
icon: 'mdi:voice'
name: 'Press Me !!!'
service: script.instant_message
type: call-service
1 Like
I did not need it to be that fancy.
I did get it working, the last line was the secret sauce!
- alias: Announce Input to all alexa
trigger:
- platform: state
entity_id: input_text.alexa_tts
action:
- service: notify.alexa_media_everywhere
data:
data:
type: announce
#method: all
message: '{{ states.input_text.alexa_tts.state }}'
Hi, I’m doing it the same way but: what is the group media_scripts for?
that was the group name, i used
### group ###
group:
alexa_media_scripts:
name: Alexa Announcements Scripts
icon: mdi:script
entities:
- script.instant_message
- input_select.message_target
- input_text.text1
Yes, I saw this. But it has no further relevance right?
that was my way off grouping things in HA state UI only
ah, ok thanks 
I’ve been having trouble with OTP.
I tried SMS, email, push to device and using the code from an authenticator app.
If i select advanced debugging all i see is an error after I close the window OTP confirmation window but nothing else.
2020-03-04 15:51:41 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2020-03-04 15:51:41 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
Thoughts?
Advanced debugging will save the webpages for review in your config directory. You still need to enable Alexa_media specific debugging. Please review the wiki for details.
Same issue. Clicking Confirm doesn’t do anything.
Does anyone know if video can be incorporated into an automation using this component? For example, I have Arlo cameras in my kids’ rooms. I already have them integrated into HA. I would like to create an automation that displays video on an Echo Show when sound is detected in their rooms at night. Is this possible? Thanks in advance!
Did you fixed those errors? I am having the same issues (not the websocket related)…
I have stopped the node red add on and removed the ring integration, but still getting errors. Less errors, but still errors.
I don’t use node red and ring integration. I just disabled the state detection from the integration page and now see what happens…
I think it all works (can send notifications and have “the buttons"in lovelace”
But I keep havin the nasty errors:
Is it possible to get a notification when I need to enter new captcha? Is there a sensor that holds this state?
You can ignore those messages… Devs use it for testing things
Good idea. That would help to avoid confusion when alexa misses important notifications
1 Like