Watson-TTS - Missing comma preventing other voices being used. #24487
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The comma was missing for one of the listed voices in the new watson_tts component. This was preventing it and the next one from being a valid voice in configuration.
Invalid config for [tts.watson_tts]: value is not allowed for dictionary value @ data['voice']. Got 'en-GB_KateVoice'. (See /config/configuration.yaml, line 96). Please check the docs at https://home-assistant.io/components/tts.watson_tts/
Connection lost. Reconnecting…
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Not required
Example entry for
configuration.yaml(if applicable):