If you have lots of these calls try this
You need to have data_template instead of data. Am I wrong?
data_template is not necessary since 117.x. It should be possible to use data as well.
I did not change the code at any place so far and additionally found out, that with the variables component it seem to be still key to use data_template.
Hey, I’ve tried to get the notify feature working now for a while, but it doesn’t do anything when I send it off, and there’s nothing in the logs. There’s just the confirmation that the test script I made was activated, and then nothing. Can anybody help me?
Posting your code would be helpful 
Is there any way to disable some of the entities as I do not use the switches for do not disturb or the sensors for next alarm ect and I have a bunch of these entities I’d like to remove
@Pirol62 can device tracking be set up I’ve tried a few things but it never announces, this is the last I tried.
question_car:
sequence:
- service: alexa_media.update_last_called
- delay: "00:00:01"
- service: notify.alexa_media
data:
target: "{{ states('sensor.last_called_alexa') }}"
data:
type: tts
message: >
{%- if is_state("device_tracker.life360_dee", "home") -%}
The Dee is at home
{%- else -%}
Dee is at {{ states("device_tracker.life360_dee") }}
{% endif %}
Same way you disable any entity, Configuration>Entities, disable whatever you like.
@alandtse
First of all please let me say “I sincerely apologize for losing it on the less than intelligent person that left the less than intelligent vulgar message condemning the long tedious work that you and many others have dedicated to this project for FREE”.
I got your point .
On a separate note, as I read all the comments about so many people having so many issues with reauthorizing, I have to ask myself what am I doing different (and how can I help others do the same) because I have (as he quietly knocks on wood, lol) been with this project since its inception and honestly have never had any real issues with reauthorization and sometimes go for months on end without needing to reauthorize. Although I can say that it has gotten pretty consistent at about every 2 to 3 weeks as of late (STILL A VERY SMALL PRICE TO PAY) I still just simply enter my password then wait for the otp from amazon which usually hits my phone before my finger comes off the submit button, enter it and off to the races for another couple of weeks.
I currently have 14 echo devices that consist of echo first gens, echo second gens, echo dot first gens, echo gen 4s and even an echo auto all active and linked across my home as well as my automotive repair business on the same network (aprox 10k square foot of echo coverage) and as far as authorization no problems at all. I run Home assistant core supervised on a Hyper-V vm that resides in a dell r720 server running on windows server 2016 . I have never used any type of authenticator app (never had a need, and hopefully never will) but do have tons of hassio addons and hacs apps running at any givin time and all my automations are handled by node red (just easier for me to wrap my head around) . This is not me bragging or anything like that , I just sincerely wonder why so many other people have a hard time with the amazon authorizations and I do not , because I definitely do not know what I am doing (not a coder or have any experience at it, I am a mechanic for 30 years) and most everything I know I have learned right here or on other forums from people like you. SO, IF THERE IS ANYTHING AT ALL THAT I CAN DO TO HELP PLEASE DO NOT HESITATE TO ASK.
Given the built-in 2FA a go, great idea and good so far.
Might be worth reminding people that they need to remove the integration and add it again to change the set-up as it’s not obvious but also that it doesn’t affect anything else in your set-up other than to re-enable all those ‘extra’ entities.
Alright, here is my code:
alias: Alexa TTS Test
sequence:
- service: notify.alexa_media
data:
target:
- media_player.noel
data:
type: tts
message: test
mode: single
First up, your spacing is a right mess, try this…
- alias: Alexa TTS Test
sequence:
- service: notify.alexa_media
data_template:
target:
- media_player.noel
data:
type: tts
message: 'test'
Thanks for the heads up, but sadly that also doesn’t work. Is it because I am from Germany? Do I have to add anything to the config?
1 Like
You need to be sure you’re using the url your Amazon account is set up with so if you used amazon.de you need to change it to that during set up rather than the default amazon.com.
Oh, now that seems to make sense. Is there any way I can trigger the setup again?
1 Like
Yep, you can just delete and add it again, anything you’ve already set up will be unaffected.
Delete the entire Integration from the UI, if I understand correctly?
Yep, sounds drastic but isn’t
1 Like
Oh holy shit it actually works that’s unbelievable
Thank you very much for helping me
1 Like
While I stopped posting release info here, I figured we just added such a requested feature I should.
As of 3.4.0, you can directly issue commands to echo device as if you spoke them. Thanks to @keatontaylor for figuring out the API call now that Amazon finally added it.
This basically means all the requested functionality we haven’t been able to provide should now be available so long as Amazon would let you say it verbally. For example, you should be able to create timers, edit your shopping list, etc.
5 Likes