does not speak correctly either. The script cuts it off at the colon as well. Does not matter if I wrap it in quotes or not. In order to read a time variable, I’ll have to parse it into plain language. That will be kind of a pain. I’d say this is a “bug”, but not one that could not be worked around.
The Media player TTS does not have this issue, but I’m very happy with this script so I’ll have to work around the issue at the moment.
I posted a question since the answer on how best to parse this out in YAML would probably be useful other places as well
Using the IDs does work. There are 1000’s of IDs of course, and probably not the easiest to use the script to find them. Anyone know an easy way to get the amazon station or playlist ID another way?
Not the Easiest, but using a browser (music.amazon.com), found a station, clicked share Station, and then copied URL, it was obvious what the station ID is. I’m sure you could so that with playlists, artists, etc.
For me this is just fine, I dont plan on doing this a whole lot. Would be more of an automation to start a station when I get home or something similar.
EDIT: Easiest option so far. Create a routine to play music. Pick the song, artist, playlist, etc. Choose your music provider such as Pandora, Spotift, amazon, siriusxm, etc, and save the playlist, then call the playlist using the script.
I created a routine called “music music music” called is like so:
alexa_remote_control.sh -e automation:‘music music music’
The routine does require you to select the echo you want or I suspect it will just default to your default echo.
Actually now that I have fully moved over I realize it’s a bit more of an pain than I realized. I have several automation based on people arriving or leaving a location. Since these dont go off all the time I did not realize until tonight.
Stuff like
Person X left “Zone name” at TIMESTAMP , and will be home in X minutes.
Now I’m just getting for example (left at 6:45)
45, and will be home in X minutes.
Adding the :: to the script kind of worked. Spoke time as numbers. Of course not like a time, but that can be worked. Only issue was when I spoke a sentence that started with a time stamp it added the word “speak” even though it was not in my automation. On my request for formatting, I got some good recommendations for better ways to provide the time without a colon that seems to be pretty good.
OK, got it figured out. For Input_datetime, I just pulled the hour and minute attributes
ended up with this
Based on current traffic, you have 15 minutes to leave if you want to get to work by {{ states.input_datetime.work_time.attributes.hour }} {{ states.input_datetime.work_time.attributes.minute }}
Worked great, still have to figure out how to get it to speak leading 0’s better.
This is really probably more of a yaml question, but is there an easy way to set the volume of multiple echos at once. I was thinking it might be a nice way to reset the volume of my echos on a regular basis. or maybe better use would be to max out all the volumes before sending an alert, like smoke detector warning, etc.
ERROR: Amazon Login was unsuccessful. Possibly you get a captcha login screen.
Try logging in to https://alexa.amazon.it with your browser. In your browser
make sure to have all Amazon related cookies deleted and Javascript disabled!
But i don’t get any captcha login screen and i can visit the alexa.amazon.it with my account, but if i disable javascript cannot access anymore.
How to get the script working again?
No, there is not anymore there… in /TMP i have only .alexa.login, but till this morning the script was working and the cookie file was there.
EDIT: i got the captcha, and succesfully accessed to alexa.amazon.it, but the script continue to send me that error…
If you restart your pi or sever the tmp directory gets cleared. The cookie gets deleted as well. You’ll need to get the cookie file again and put it in the tmp directory. It won’t won’t without the cookie
I’m running HA in a python VENV, not hassio on a RPI. This is what I did
I used firefox on my windows computer and then copied the cookie to my ubuntu server. I actually ended up putting the cookie in my /homeassistant/homeassistant/.homeassistant folder and editing the tmp path in the script. as outlined here
There are a lot of different ways to handle the cookie file depeding on your install, I recommend reading/skimming through all of the posts in here, there are a lot of discussions about the cookie file
Ok i did it… i am on hassbian with chrome as browser… found all the cookies and saved the one from amazon.it… it worked so i have again the script running…