Home Assistant release with the issue:
0.94.4
Last working Home Assistant release (if known):
Only with pip install
Never worked on hassio
Operating environment (Hass.io/Docker/Windows/etc.):
Three times no luck
Component/platform:
picotts
Description of problem:
Even picotts is installed on the base system (for example on raspian lite or debian 9) the component can't come up in home assistant (hassio based). I'm not sure if there is any (special) step needed which is not written in the docs (https://www.home-assistant.io/components/picotts/) or that picotts is just broken on hassio?
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
# Example configuration.yaml entry
tts:
- platform: picotts
Traceback (if applicable):
‘pico2wave’ was not found
00:01 PM components/picotts/tts.py (ERROR)
Additional information:
+1 for cloud free tts
I don't know if this one here (https://pypi.org/project/py-picotts/) has any relevance and that picotts could be included hassle free as a bundled component (including picotts itself and not rely on system packages) with py-picotts?
In 0.95.4 with hassio picotts is broken too
Broken in 0.96.x as well :crying_cat_face:
Guess what... pico tts still doesn't work with 0.97 and hassio :disappointed:
I wonder what's needed to have a local tts with hassio...
pico tts is not available for hassio 0.98
No cloud free :no_entry_sign::cloud: _tts_ available for hassio at the moment (as far as I know)
ha 0.99 + hassio + picotts = broken :broken_heart:
The 100th release of home assistant still doesn't play at all with hassio & picotts :sob:
0.101 :-1:
Should this issue be moved to or a new issue opened under the hassio issue tracker? (https://github.com/home-assistant/hassio/issues) or hassio-homeassistant (https://github.com/home-assistant/hassio-homeassistant)
This is not broken for Hass.io specific, but for Docker as well @jchambers2012, I would say: no. Besides, the repository your pointing to is the Hass.io Supervisor, which is not responsible for these things.
Hi,
I stumbled across a seemingly working implementation for picoTTS.
https://github.com/Poeschl/Hassio-Addons/tree/master/picoTTS
https://github.com/Poeschl/ha-picoTTS_remote
Together with the pending pull-request, this is working for me. Might be worth a check and potentially an inclusion with the add-ons. Would be nice to have an offline tts service again.
Edit 2020-02-08:
Correct link: Repo. Pull Request got accepted, working flawlessly ever since from my perspective.
You said that the picotts never worked on hass.io, right?
Picotts rely on OS-level native library, which the picotts component page clearly stated.
The problem is that both hass.io distribution and docker distribution in effect put a wrapper, in effect to shield the user from the underlying operating system. This in normal times made life very convenient for the user to use home assistant, but the user will be stuck with whatever the native libraries the home assistant come with.
In an idea world, you want the home assistant components COME with the native libraries built in. In most cases,, this is true.
For some reason, picotts is one component which native library is not built-in. You will need to install native library at the OS level to make picotts to work.
In my case, IÂ went into docker container itself and install the library inside the docker to make it to work.
There is a way to use Pico TTS on Hassio (All-In-One), but it requires a custom Add-On and a HACS integration. It's not ideal, but it does work well right now in HomeAssistant 0.111
Thanks @Poeschl !
My working setup:
Install the custom Pico tts Home-Assistant Add-On
Add the custom repository to the Home-Assistant 'store':
Install and start the Add-On - no configuration necessary
Install the corresponding HACS integration:
Use the Pico tts service as you normally like:
or by a service call like..
Revel in the awesomeness of open source & local tts!
Note: If the tts service doesn't seem to work for you, you'll need to make sure that your base_url for home-assistant does not use ssl (https). This may be a deal breaker for some people, but it shouldn't be if you use something like the NGINX Proxy Manager add-on that allows your Home-Assistant to access your instance using https even though home-assistant itself is using http. And, if you still want to be that guy that wants to use https in his internal network, you can just add a host override in your router to point any internal home-assistant traffic to NGINX Proxy manager - thus giving you https everywhere while home-assistant itself can still call the pico service happily.
* Add the custom repository to the Home-Assistant 'store':
Rather than a screenshot with lines over the URL could you please include the repository URL as a link?
Take a look there 😉: https://github.com/Poeschl/Hassio-Addons
Most helpful comment
Take a look there 😉: https://github.com/Poeschl/Hassio-Addons