Skip to content

Initial text-to-speech (TTS) docs #1588

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

Merged
merged 15 commits into from
Dec 17, 2016
Merged

Initial text-to-speech (TTS) docs #1588

merged 15 commits into from
Dec 17, 2016

Conversation

fabaff
Copy link
Member

@fabaff fabaff commented Dec 13, 2016

Description:
Initial text-to-speak (TTS) docs

Pull request in home-assistant (if applicable): home-assistant/core#4837

@mention-bot
Copy link

@fabaff, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mnoorenberghe to be a potential reviewer.


- **language** (*Optional*): The language to use. Defaults to `en`.
- **cache** (*Optional*): If you want to use the caching feature. Defaults to `true`.
- **cache_dir** (*Optional*): The port on which the APCUPSd NIS is listening. Defaults to `tts`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale description

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@robbiet480
Copy link
Member

It should be text-to-speech, not text-to-speak.

@fabaff
Copy link
Member Author

fabaff commented Dec 14, 2016

Thanks

@fabaff fabaff added the new-integration This PR adds documentation for a new Home Assistant integration label Dec 14, 2016
@fabaff fabaff changed the title Initial text-to-speak (TTS) docs Initial text-to-speech (TTS) docs Dec 14, 2016
@@ -0,0 +1,36 @@
---
layout: page
title: "Google"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This title should be less generic e.g. "Google Text-to-Speech"

ha_release: 0.35
---

The `google` text-to-speech platform uses [Google](https://www.google.com) Text-to-Speech engine to read a text with natural sounding voices.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we link "Google Text-to-Speech engine" to Google API docs?


# {% linkable_title Cache %}

The component have 2 cache. A long time cache on file system, they can controll with `cache` option on platform config or service call `say`. And a in memory cache for fast response to media player, they will be auto cleanup after several time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph needs rephrasing and typo fixes.

- platform: google
```

The following optional parameters can be used with any platform. However tts component will only look for global settings under the configuration of the first configured platform:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note about the implementation, not docs: Why are we adding this limitation to a new platform? It's something I understand is supposed to be fixed in other platforms.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that @pvizeli could answer this question be than me. From my point of view it looks like that we don't want to handle multiple caches.

@fabaff fabaff merged commit 220ff1b into next Dec 17, 2016
@fabaff fabaff deleted the tts branch December 17, 2016 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-integration This PR adds documentation for a new Home Assistant integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants