Cookies are another way to login if you have trouble with the standard login. If you’re already logging in, there’s no need to use cookies. In fact, cookies cannot use oauth tokens so you will not get any benefits from the change to oauth.
Ok, I appreciate that then. I am going to just use password, captcha, and 2FA and setup the 2FA auto-refresh feature then.
Thanks for the tip!
edit: worked perfectly! Hopefully I don’t have to keep resetting my amazon password every 6 weeks or so.
That has never been the URL. You’re on an old version of HA that didn’t provide a correct link for custom components. Here is the component link from a working HA.
Thanks, but finding the component is not the problem.
When I have to restart HA to renew the connection to Alexa, I get a notification in the UI that the alexa_media integration is not working. Normally there would be a Configure link that I would click to do the captcha and 2FA login again. Since yesterday I haven’t been seeing the Configure link, just an alexa_media link that gives me a 404 error with the url I mentioned. No idea why Configure went missing.
But as I went over it again for the 15th time to verify the exact sequence, it just suddenly reverted to working again. I got he Configure link as usual, and was able to complete the login process. Again, no idea why it suddenly started working again.
I can’t get my HA in a state where it can update. I’ve already spent probably 40 hours trying to do that, without success. I’m running on an old 32-bit box with Ubuntu 18.04. It took me 2 days to get Python 3.8 installed and running as a basic upgrade prerequisite, and only after tracking down dozens of errors and updating dozens of other components. But HA would not boot, even in a stripped down configuration. I tracked down dozens more errors and dozens more system components needing update before I finally stalled at one that was insurmountable, as it required an Ubuntu upgrade to a version that’s not supported on my old hardware. I was therefore forced to give up, and hang on with this HA version until such future date as I can buy a new Raspberry Pi, install a new version of Linux and HA, and start over again from scratch. That’s no small expense and no small project.
I’m glad you got it working but I don’t have any idea how it’d give you that url.
On the upgrade front, I’m not sure how old your hardware is but if you’re able to get docker running (it is supported on 18.04), HA on docker would avoid the dependency hell you’re running into. There is a performance hit vs bare metal but I think HA is fairly light. My production and dev machines use hassio in docker and I’ve found it makes the whole upgrade process painless. Ubuntu instructions.
If only I could get Docker working! It is supported by Ubunto 18.04, and it installs, but won’t run successfully. That was one I tried to fix for several hours. No good.
It should work as I am running docker on ubuntu 18.04.
Glad to know hassio in docker works on ubuntu 18.04 too. Is this the recommend way over regular docker? Is there an easy way to migrate from regular docker to hassio?
I believe hassio on Docker isn’t an officially supported deployment so no it’s not recommended and that is a downside. My understanding is if you copy your entire config directory including subdirectories, it should transfer all your settings.
1 Like
Is there any way to integrate source change for the Polk Command Bar so I can switch between HDMI1 and HDMI2 on it? Or rather, is that data that is being retrieved now or can be retrieved at all?
Will all due respect, this is not a realistic take. Expectations such as the ones you expressed above is what can end support for an integration.
@alandtse is contributing substantial services for support, development, bug squashing, and the continuous dance to connect successfully with Amazon and their ever changing authentication methods. He isn’t paid to do this. He can correct me if I’m wrong, but I would be shocked if he barely has time to support the current release…
For you to expect him to support older versions (April 2019!!!), when support requests are practically non-stop, is not reasonable for a one man volunteer show… For volunteers there should be no expectations, but only gratitude.
7 Likes
i dont have expectations, i just noted that the choice of words were bad.
he must not compare himself to people who are about the worst in supporting. 
and saying that those people dont even support it, doesnt make a valid point.
i rather see that he states what he supports and what not. and stick to that.
the problem with thinks like this is: this companent updates irregular, and HA updates regular in a very high rate. so actually he can only garantee anything that he has working himself.
which for me is fine, but then i would ask: on what is it tested? which HA, which amazon, which intergration version.
and i think that should be on the top from the docs or on the github.
then someone who takes the time to read back could see: on version from HA xxx the version from this intergration xxx did work.
at this point it is: get everything to the latest version. keep checking because the latest version can change every day.
as far as i can see it (with all the respect i got for @alandtse) he is in most cases trying to support blindly. because people dont tell which HA version or intergration version or which amazon server.
and i think he can save a lot of energy by stating clearer lines. (and maybe make it somehow possible for others to tell what works for them (HA version/intergration version/amazon server/ date))
so im sorry if it sounded like im the one criticising his support. it really was about his choice of words
edit: and i think it also would save an enormous amount of energy if this topic was closed and with the mods from HA there was communicated to make it into a subforum. because with almost 5000 answers noone reads back, not even 10 reaktions.
I already require people to provide information on GitHub if they want help. You’d be surprised how often I have to respond to an issue with “please fill out the template”. Most get closed by the stale bot because I never get the info. There are some repeat reporters who know what to provide and I typically close their issues quickly. The short answer is if I get enough info, I’ll try to help resolve it.
As for what I support, I’ll support the version of HA I use which is beta. If people can get it to run on older versions, then that’s great but my target is what I use. I’ve think I’ve stated it before, but there’s enough tools on GitHub to figure what versions were released for a corresponding HA release. If someone wants to add a wiki page identifying the versions explicitly, I don’t have a problem with it. In fact, I appreciate anyone who helps update the Wiki as it’s one less thing for me to deal with.
I did open a GitHub discussions section if people want to use a threaded forum.
2 Likes
I have a custom command to arm my alarm system when I press a button, but it doesn’t work on my Echo Show 10. The exact same command sent to an OG Echo works fine but Alexa says some sort of error that “in order to use that command you must say Arm ADT Stay”. If I do that it just complains that Alexa Guard isn’t enabled. Basically it seems like my Echo Show 10 won’t respond to the same Alexa Media Player custom command that the the first gen Echo responds to fine. Any ideas? This is the command I send in Node-Red:
{
"entity_id": "media_player.living_room",
"media_content_id": "Tell ADT to arm stay",
"media_content_type": "custom"
}
BTW, other commands such as “What time is it” work fine as custom commands on the Show 10. Anyone smarter than me know what could be going wrong?
Have you tried actually saying it directly to the Show to see if you get the same reaction? I’ve got one Dot that refuses to accept a certain spoken command exists despite all the others being perfectly happy with it.
Yeah, I’ve tried it. It’s almost as if the old Echo is not as particular about commands as the newer devices. The Show 10 insists that the command be “Arm ADT Stay” but that doesn’t work with custom commands because it gives me some sort of error about using Echo Guard. Very strange problem.
So I removed my Alexa intergration then re-added it. Now I can’t get it back, it shows me the:
**alexa.amazon.ca**
Amazon will send a push notification per the below message. Please completely respond before continuing.
But when I authorize via txt msg it still doesn’t go anywhere once I press submit (the popup stays there).
I even tried deleting the cookie file that is created in the /config/.storage
I used the cookies field as well…
Nothing works, I can’t get the Alexa integration added to my Hassio.
SOLVED: enabled then added a 2FA code and it worked.
I tried to add a shortcut to play ‘my list’ from amazon music but seems not working, not sure the syntax is right or not? I do have a play list ‘my list’ in amazon music and when I say ‘play my list from amazon music’ to alexa the echo dot plays music.
artwork: cover
entity: media_player.office_dot
hide:
volume: false
shortcuts:
buttons:
- type: service
name: My List
id: media_player.play_media
data:
entity_id: media_player.office_dot
media_content_type: play my list from amazon music
media_content_id: custom
columns: 4
source: icon
type: 'custom:mini-media-player'
Hi,
‘from amazon music’ is not necessary here.
For own playlists I say ‘shuffle my Trance best playlist’
For tunein radio stations I say ‘tunein antenne bayern’
Thanks. The above shortcut code doesn’t work no matter what I put in the media_content_type 
You have media_content_type and media_content_id the wrong way round there. SHould be:
data:
entity_id: media_player.office_dot
media_content_id: play my list from amazon music
media_content_type: custom
1 Like
Hi, I am dependent on last_called updating almost real time for many of my scripts but for the last few days this doesn’t seem to the case. It is taking a good few minutes for it to update suddenly. Is there anything that could cause this sudden change?