Hey, I wanted to ask if it's possible to access the Last Call sensor directly from Alexa. I managed to import the Last Call sensor into HA, but it only triggers when I give a command twice to another Alexa. If I only give a command once, e.g., “Alexa, what time is it?”, nothing happens until I repeat the command. At the same time, I want to transfer the command to HA to trigger further scripts/automations.
#Alexa last call sensor
1 messages · Page 1 of 1 (latest)
Amazon has basically killed the functionality of that sensor. While it may appear that it takes giving the command twice, that is not necessarily the case... Amazon has just significantly reduced the frequency at which that data is pushed back from their servers.
So there is no way to get somehow arround this? But thanks for the Info
Not that I've heard of.
If there was, I'm fairly certain the devs for Alexa Media Player or Alexa Devices would have implemented it. Without the last called feature so much of the previous functionality of using Alexa with HA is now gone.
I would love to be able to respond on the same echo I used to issue a command 😢
I use node-red and this seems to work for me. I call my command and then it waits for 1,100 milliseconds and then it uses the "update last called" action from Alexa media player. It was flaky before I put in the delay. Then I output my message to notify.alexa_media_last_called.
Using node red has nothing to do with how quickly amazon updates the sensor
What about the call to update last called action? Does that have something to do with getting it to work?
I created a skill specifically to make using alexa-actions much easier and more reliable.
It's an Alexa-hosted skill that acts as a context sensor, capturing the person_id (who) and the exact device_id (where) in real-time. This solves the common issue of dialogues starting on the wrong Echo or with the wrong user permissions.
check it out: https://github.com/2Max2Pax/mio-fantasma