# Node-red-contrib-alexa-remote2 and node red not configuring

**URL:** <https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-and-node-red-not-configuring/30239>\
**Category:** General\
**Created:** [17 July 2020 02:10 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-and-node-red-not-configuring/30239 "2020-07-17T02:10:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenkoknz](https://avatars.discourse-cdn.com/v4/letter/k/58956e/32.png) [@kenkoknz](https://discourse.nodered.org/u/kenkoknz)\
**Post date:** [17 July 2020 02:10 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-and-node-red-not-configuring/30239/1 "2020-07-17T02:10:06Z")

</div>

Hi,

The node-red-contrib-alexa-remote2 is just about the only node out there at the moment to easily control alexa and meke alexa speak among other things. If anyone knows of alternative please share.

This may (or may not) be helpful, if you are having problems with trying to configure the alexa remote2 node and getting it to work.

I tried to setup remote2 again today (node was working using proxy method before), as I have change the password in alexa, but at login it just displays "invalid email address" and the node no longer work as it cant login to alexa account using proxy method.

Finally, after long search on the internet, using the "proxy" method to configure the node may not work anymore (apparently alexa had changed "something" recently).

Below is a workaround to get it working again:

Workaround using cookie to configure tested ok (17jul20):  
Using cookie method to configure node works, but is not explicitly stated in the node's guidelines on how to do this, and no reference on how to get the cookie.  
I finally managed to get the node working again using this link to get the cookie (note: I cannot make sense using chrome method, but manage to use firefox to get the cookie): [https://github.com/586837r/node-red-contrib-alexa-remote2/blob/master/get\_cookie.md](https://github.com/586837r/node-red-contrib-alexa-remote2/blob/master/get_cookie.md)

Anyone else having this problem?

Cheers,

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [17 July 2020 07:54 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-and-node-red-not-configuring/30239/2 "2020-07-17T07:54:05Z")

</div>

> [@Alexa-remote2 nodes issue](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211):
>
> Just a heads up - I was documenting how to use the nodes for a blog and went thru setup again and it fails authorising agains Amazon - having spent hours trying to resolve (and having to reset my password in the process) I went to issues on the node and its already been reported If you follow link to other software using same concept and either speak Deutches or use a translator slight_smile - you can see its something to do with changes at Amazon end So, in the meantime - I think people …

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [15 September 2020 07:54 UTC](https://discourse.nodered.org/t/node-red-contrib-alexa-remote2-and-node-red-not-configuring/30239/3 "2020-09-15T07:54:07Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.