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

Alexa Media TTS support #96

Closed
alandtse opened this issue Mar 12, 2019 · 5 comments
Closed

Alexa Media TTS support #96

alandtse opened this issue Mar 12, 2019 · 5 comments
Labels
enhancement New feature or request

Comments

@alandtse
Copy link

Hi,
For the alexa_media_player custom component we're about to deprecate our media_player.alexa_tts service in the next version or so 1.2.0 and I wanted to give you a heads up since you support that service call for our users.

Instead of the old service, the new default service should be: notify.alexa_media. The json data will be

{
"message":"test",
"data":{"type":"tts"},
"target":["media_player.kitchen"]
}

We'll likely deprecate the service after one full release cycle to confirm parity between notify and media_player.alexa_tts.

@kalkih
Copy link
Owner

kalkih commented Mar 12, 2019

Hey,
Thanks for the heads up.
Just to be sure, does the target parameter support an array of more than one entity?

Thanks.

@kalkih kalkih added the enhancement New feature or request label Mar 12, 2019
@kalkih
Copy link
Owner

kalkih commented Mar 12, 2019

@alandtse Another question, is string accepted as target value, or does it have to be an array, even if there's only one target?

@kalkih
Copy link
Owner

kalkih commented Mar 12, 2019

@alandtse
Copy link
Author

alandtse commented Mar 12, 2019

Yes. It will support both a string and an array of strings. FYI, we released 1.2.0 and will keep the old service till 1.3.0.

@alandtse
Copy link
Author

Closing as I believe this is resolved. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants