As i said i got error when using the template dev tool… I think this is intended to show the last echo device called as it’a an attribute of the devices.
Sry I missed that.
Ok, but how can this information be used? I don’t get the use of this sensor.
What do you plan to do with it?
I just updated from 0.9.5 to 1.0.0. Everything worked perfectly before, but now I am having an issue with getting the media player to update correctly with what is currently playing. If i ask Alexa to to play Spotify, it works as expected (with a little longer delay than previously) showing the song that is currently playing. If i use the Spotify media player component and change the source from there, the new source I selected never updates with what is currently playing. I also have the same issue of the song not updating when I ask Alexa to play Spotfy on a different device (e.g. asking the Alexa in my office to play Spotify in the bedroom). Is anyone else having this issue or know of a solution?
Same here. I am using mini-media-player card but not getting the full-cover artwork like before.
And i get this in /states:
The device is actually playing a song.
EDIT: The full cover appears just many minutes after…
I think I just figured out why the Last triggered Sensor could be useful.
I’d like to be able to ask alexa for certain sensors.
For example:
Routine: “Does it rain” that triggers an input boolean to turn on
Automation that’s looks for that Boolean and than triggers the Mediaplayer to tell you the answer with an if that’s looks for rain/notrain.
The issue here would be to know which Alexa was asked and only push the message to that device.
Is this how you use this sensor. Does someone have a ready to use automation?
try this
1 Like
Thanks… now it gives me the right result in dev-template editor.
The sms or email captcha prompt is something Amazon generates for some reason. This may be related to suspicious activity or some other reason. We save the log-in cookie so in theory won’t be asked until the next login.
This is a known issue for now. The component doesn’t update because it doesn’t poll unless it knows the device is active. The work around is to do something to that playing device either through HA or with your voice. It should then start checking the device until it stops playing. At this point I don’t see any API information that can tell us that the reason an Alexa was last interacted with was to enable playing on a different Alexa.
The reason we disabled the old behavior was because this component has to contact Amazon’s servers for each Alexa and having every single Alexa polling every 30 seconds 24 hours a day could potentially cause issues with throttling.
2 Likes
So the reason I don’t remember it, is probably because I never had to verify right in this component. So Amazon doesn’t do that for any user?
Wouldn’t the switch to the new component mean a new login?
But yeah if they only do that for certain reasons, and mine doesn’t trigger that reason and won’t see it.
after selecting email I get this 
What’s happens after pressing confirm? Did you look in the notifications and/or the log?
I have this in log file
2019-02-24 21:51:18 WARNING (MainThread) [homeassistant.loader] You are using a custom component for alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
EDIT: just to be sure I’m using ver 0.88.1 and there is the three .py files in alexa_media folder
This log file entry is nothing to worry about, this is a normal warning for custom components after ha restarts.
That’s all I can tell you about that. Sry
If the email route isn’t working, we’ll need you to enable advanced debugging along with regular debugging. There might be something with the webpages Amazon shows for email sms that we aren’t processing correctly. Please review the wiki for details.
The alternative is to try the sms route. I know others have confirmed the sms route works. I haven’t heard any confirmation on the email route.
This component is no longer registering the service alexa_tts. Is anyone else seeing that?
Maybe add support for custom updater, if possible
meh,
Deleting the Amazon pickle file should give you Captcha instead after the next reboot. Then you can just fill out the Captcha
did you update and relocate the component?
Actually, It has to be because I need to redo the captcha, completely forgot about that step. But the image isn’t showing up, on to the next mystery.
read back a bit here, most misteries are already spoken about 