-
Notifications
You must be signed in to change notification settings - Fork 290
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
last_called is too slow? #83
Comments
Not at this time. We will be exposing a service in the future as the current polling method results in too much polling of Alexa servers. |
Yes that would be a much better option |
FYI, the Alexa App already allows you to do location specific control of at least lights. You'll need to use HA's emulated Hue and ensure within the AlexaApp it treats that switch as a light. I think you could also do the TV too, but I haven't tested it. |
Really, how? I've not seen this option before, do you mean via a routine? There only the option "Alexa will respond from" which give device specific controls |
https://www.amazon.com/gp/help/customer/display.html?nodeId=201749250. Might be region specific. |
Nice that works thank for help |
@alandtse I'd like to use the last_called sensor for the following case. Unfortunately as the topic says currently it's too slow. I like to turn on an input boolean with a routine in alexa by my voice. This than will trigger an automation which sends a tts to the last_called alexa. This way it must be fast or it will send the tts to wrong alexa. EDIT: my sensor.last_alexa only updates it's state after I restart home assistant. currently all of my alexa devices show |
This branch has an exposed service for the adventurous who want to test it.
{
"email" : ["email1", "email2"]
} |
Hi
I'm trying to make of the last_called attribute. Ie things like "Alexa Turn On Lights" / "Alexa Turn On TV" and then based on the echo that was used turn on the lights for that room.
This #65 suggest that @brianhanifin got it working. But in my test there a good 10 seconds delay until the correct echo is reported back correctly.
Is there any way to force a refresh of the last_called attribute?
Cheers
The text was updated successfully, but these errors were encountered: