Hello, I use this for a few things - dinner time announcement and doors left open, and haven’t noticed any trouble with it. However my logs are filled with warnings. I ignore them - expected?
Update of media_player.living_room_dot is taking over 10 seconds
Thanks!
Hello guys,
for me this works pretty well but only a few hours… After this time ha get’s no updates from my alexa devices. (no volumes, no playing titles).
When I reboot my ha, it’s working again without a captcha.
Any fix ?
Thanks!
I know you said you now do things differently but is it possible to post the config for how you did this (without using Node-Red)?
I’ve also noticed that too! Can be days before it stops working, but at some point it definitely stops and needs a restart.
Here is a link to a google doc that has the node red sequence that is above.
It involves setting up a sensor called last_alexa. The sensor will contain the name of the last echo that you used. Here is the link to how to do it:
Alexa_remote_control.sh for hassio
Its a bit of pain to get it working but the value of being able to refer back to the echo you last spoke to, is invaluable.
You’re an absolute champ, thanks very much mate.
Feeling really stupid about now. I have been trying to get this to work for a couple of hours and I get no response of any sorts from HASSIO that even resembles that I have added anything. I created the alexa.py file in the media_folder and copied the version 0.9.5 information into that file then added the media_player information into the configuration file without using quotes. Got no errors but also have no Alexa still. Am I missing something pretty obvious?
I’m not sure why, but mine did that also. It just seemed like a couple of full reboots got mine going. Tho, I’m stuck at the captcha part now…
What version of the file are you using? The message you’re getting is from an older version before we made substantial improvements to the configuration. The latest version is VERSION 0.9.5.
@lessmann
Please make sure the alexa_media.pickle is deleted. If you enable debugging logs for alexa_media_player it should give you more information on where your login fails. It probably is a 2 factor authentication issue. If you do pull logs, you can message me directly with a private gist to store your logs (scrub password/email) and I can try to help.
I knew it was something that I over looked. I had ver .7 not .95. I just tried installing this couple days ago. Not sure how I got older version.
Thank you! Seems to be working not
One more question mate, what part of the flow sets what you can ask Alexa? Meaning the “Is the garage door open?” question. Or is that defined somewhere else? Cheers.
Another question, what do I need to set
Tts:
-platform:
Right now it’s set to google. Alexa doesn’t like that. Lol
if i understand correct the questions are set inside the alexa app in the section routines.
you dont set the TTS platform.
the mediaplayer adds a service called media_player.alexa_tts
Ok, I should just comment tts out then?
if you dont use google TTS or any other TTS then you dont need the TTS section.
Ok, sounds good. That was in my config file from day one, figured it was supposed to be used. When I get home tonight I’ll play with that.
Thabks for your help!
I figured that may be the case, but I’m curious as to what is used as an intermediary between Alexa and HASS/NodeRed. Do you create a switch and then get the routine to trigger that? Cheers.
a switch, an input_boolean, the brightness from a virtual light(none existing light created in HA), anything that can be set in home assistant that can be used to trigger an automation.
i use:
so thats my flow.