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

Amazon polly NEW voice unsupported #18768

Closed
badstraw360 opened this issue Nov 29, 2018 · 0 comments · Fixed by #18773
Closed

Amazon polly NEW voice unsupported #18768

badstraw360 opened this issue Nov 29, 2018 · 0 comments · Fixed by #18773

Comments

@badstraw360
Copy link

badstraw360 commented Nov 29, 2018

Home Assistant release with the issue:
0.82.1

Last working Home Assistant release (if known):
NA

Operating environment (Hass.io/Docker/Windows/etc.):
Docker

Component/platform:
tts/amazon_polly_say

Description of problem:

When I try to use Mia instead of Penelope, I get this error:

Invalid config for [tts.amazon_polly]: value is not allowed for dictionary value @ data['voice']. Got 'Mia'. (See ?, line ?). Please check the docs at https://home-assistant.io/components/tts.amazon_polly/

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

  - platform: amazon_polly
    aws_access_key_id: xxxx
    aws_secret_access_key: xxxx
    region_name: 'us-east-1'
    voice: Mia

Additional information:

The voice is still unsupported... Would you guys add it please?

Penelope works fine..

fabaff added a commit that referenced this issue Nov 29, 2018
@ghost ghost assigned fabaff Nov 29, 2018
@ghost ghost added in progress labels Nov 29, 2018
@ghost ghost removed the in progress label Nov 29, 2018
fabaff added a commit that referenced this issue Nov 29, 2018
* Update lang list (fixes #18768)

* Fix lint issues
@balloob balloob mentioned this issue Dec 12, 2018
@ghost ghost assigned balloob Dec 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants