@alandtse I see in the v2.10 release notes:
I’ve used this before to have one Alexa in one room “dropin” on another Alexa in another room.
What would be an example use case for this feature using the Alexa Media Player?
BTW, Thanks for all your work on this component 
I just expose features when they appear in the Alexa app. If you figure out how to use it, please update the Wiki.
The dropin notification creates a push notification on your mobile devices with the Alexa app installed (similar to when you use “push” as the type) with the difference being that, when you open the notification, it launches the Alexa app in the Dropin section allowing you to chose a device to drop in on.
I’d imagine that this would be if useful used as part of an automation triggered by a motion sensor as the notification would allow you to easily drop in on your house to see (if you have an Echo device with a camera) or hear what is going on.
Just submit and you should get image with captcha.
I have been getting the increased request for reauthorize for almost two months. This has only encouraged me to look for non-cloud local solution for local announcements. This integration is great but realized this too necessary to leave for web and not local.
Anyone got suggestions for local?
I’ve been experiencing the same issue, and it just keeped prompting and because of it my calls to routines don’t run
ive been on the beta channel and running the latest 113.xx
i saw in the HA logs errors about session closed
i have the lastest verison in HACS i had the latest beta version in HA
i even turned on 2FA
I had a snapshot from the 22nd June so i restored back to HA 111.4
just HA nothing else
and hey presto
the issue is gone i left the beta channel
i got prompted to upgrade to 112.4 and the issue reappeared
I have restored back to 111.4 and the issue has gone.
and i still have 2FA enabled
so the issue is not with Alexa Media Player Component but something with HA and a change they have made.
Well updated.
Running 113 now and all good
Since HA doesn’t allow testing of events with /, in the next release it will switch to alexa_media_player_relogin_required. The old event will still fire for the next few releases but I will deprecate it eventually.
Upgraded on sunday to 113.1. Everything worked.
Over this night, alexa doesn’t work. No issues, no captcha requested.
Simply doesn’t work.
There is no pickle file I can delete.
2 times restart - no change in status.
What could be wrong?
OK - strange things going on:
I tested around and found out, that a script, I executed, worked but on an echo which wasn’t expected.
This script did not work, which made me assuming, alexa integration is broken:
instant_message:
sequence:
- service: notify.alexa_media
data_template:
target: "{{ states.input_select.message_target.state }}"
data:
type: tts
message: "{{ states.input_text.text1.state }}"
Then I activated some further simple scripts which simply gave out the outside temperature of my netatmo and suddenly, after waiting around 30 Minutes, the instant message worked again.
Its confusing, but everything seem to work again.
Is it also possible to fire an event when the login is successful?
We could use that in an automation to clear the relogin notification.
I’d love to post a screenshot of my issue, but every time I upload an image, it’s broken… not sure what that is about…
anyways, in my Notifications on my HA install, I get a configurator error that tells me:
“Click button to configure Alexa Media Player - Captcha - my-email-address”
I click “Configure” and I get a modal that passes along the error from Amazon saying:
“Important Message! To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below”
the captcha: shows a broken image, so i cannot enter it
I don’t have any idea what to do with this and the integration is completely broken.
I’d guess “remove the integration and reinstall” might be a suggested solution, but damn, I have a ton of Node-RED rules using the existing entity IDs, I’d hate to do this scorch the earth method and have those entities change. Plus that doesn’t give me much confidence long term more than anything
I noticed the same thing in my browser preview field but if I go ahead and post the picture it works anyway. So it looks like it’s just a bug in the preview box.
Try it and see if it works.
I’ve also had that I’ve just had to enter some random characters and hit submit the the next time it comes up with a viewable captcha picture.
Thank you SO much… that did the trick!
This is great. Will be updating and testing as soon as it gets out. Thanks!!
Yes, but it’s already supposed to clear the configurator prompt once a login is successful. I can add in an event regardless.
Ok, thanks.
I was thinking that the relogin required event could turn on an input boolean to give you a notification that one is required but then you would need to turn off the boolean manually. with a login succesful event you could use that to turn off the notification boolean.
I’ve tried tinkering with the JSON of the last_alexa sensor many times with no luck. But now that there’s a last_called_timestamp as well as the last_called, I thought I’d try again. At last I think I’ve cracked the ‘2 accounts’ problem 
By adding a sort on the timestamp after the last_called attribute:
{{ states.media_player | selectattr('attributes.last_called','eq',true) | sort(attribute='attributes.last_called_timestamp', reverse=true) | map(attribute='entity_id') | first }}
(Removing the “,'eq’true” also seems to work but is it better to leave it to narrow the filtering?)
So far it’s worked with the last one I spoke to even after a timer going off a different Echo Dot and triggering the script non verbal in HA.
But I’m still not sure if: 
a) it’ll work with several accounts, and
b) will any other background events shift the timestamps? (would only be an issue for non-verbally triggered scripts though).
But I hope this proves to be solid and helps out others in the same boat 
I have been sratching my head, reading posts and wiki’s and trying all sort of combination but always receiving a Failed to call service media_player/play_media. required key not provided @ data[‘media_content_id’]
I have added one of my Echo’s after adding the Alexa media player. The goal is to have several button for our favorite radios. Push and hop they are starting on the Echo.
Can anyone be so kind to tell me what I have done wrong ?
type: entities
title: MEDIA GROUP
entities:
- type: 'custom:mini-media-player'
entity: media_player.sebastien_s_echo
shortcuts:
buttons:
- service: media_player.play_media
name: Test
entity_id: media_player.sebastien_s_echo
media_content_id: BBC one
media_content_type: TUNEIN
Try "BBC one" in quotes.
Thanks but still same error 
Ah just realized you’re using the custom mini-media-player which I don’t know anything about, so its more a question about how to setup a service call for the mini-media-player. May want to look at this link on shortcut objects. As a guess, try the following:
....
shortcuts:
buttons:
- name: Test
type: service
id: media_player.play_media
data:
entity_id: media_player.sebastien_s_echo
media_content_id: "BBC one"
media_content_type: TUNEIN
Otherwise, I suggest bringing your question up on a forum topic for the custom media player as more eyes may be looking at it than here.