Hello, I tried to follow the instructions to install on Hassbian (I think it was only originally for hass.io)
created the directories as suggested.
I did try WGET to get alexa.py but this ended up being some kind of HTML file so copied and pasted the code from the link instead.
Update the configuration.yaml as suggested.
Restarted home assistant.
First of all it complained about BeautifulSoup / bs4 so I used pip to install that - that appeared to have been successful (in fact I think I managed to installed it for Python3 and 2) - I ran a test script which seemed to indicate BS was working (which I found in another post somewhere).
Each time I restart Home Assistant, the alexa.py script complains that no module ‘bs4’
This is working great, but for some reason I am not able to uninstall the add on. It is not running, but when I try to uninstall it asks me if I am sure I want to uninstall it, then closes the window and goes back to the main Hassio add ons page. Doesn’t seem to affect functionality, but it will not uninstall for me.
Many thanks, that did the trick. I was unfamiliar with the command source /srv/homeassistant/bin/activate (I did get an error about libcryptodome but the media players have authenticated and appeared) - now to see if I can turn them on and test them.
very annoying the new setup every time you restart HA you need to put capcha;
and the main problem is that capcha doesnt seem to work all the time and that makes you setup the configurator.alexa_media_player witch also seems to have to try many times until you get the mediaplayer
sense you always updating and restarting HA to set new things, going with all this troubles and process seems to be a big pain
Since I moved to Homeassistant running from a Docker container, I never had a problem missing dependencies, such as this BeautifulSoup and others … it seems that the docker container is very well provisioned with everything it needs to run. As for the alexa tts, I just edited my configuration.yaml file, like this,
and it all just went fine from there … no errors. Try Docker, it’s easy when a new version of Home Assistant emerges, just stop the container, pull the new one, copy configuration and start the new container … no stopping ha service, no entering virtual environment, I remember installing all those packages and maintaining them regularly … no more, just try it, try Docker … just a thought.
I have done just that today, installed on Raspbian and after some issues getting the systemctl script to auto boot HA correctly, I can confirm the component is working!
The captcha appears on each reboot, which is already known, but other than that, it seems to work very well. Great job @keatontaylor