# Alexa-remote2 nodes issue

**URL:** <https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211>\
**Category:** General\
**Created:** [16 July 2020 15:16 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211 "2020-07-16T15:16:18Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [21 July 2020 16:26 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/21 "2020-07-21T16:26:13Z")

</div>

This is the error

Error: Package exports for '/data/data/com.termux/files/home/.node-red/node\_modules/alexa-remote2/node\_modules/uuid' do not define a valid '.' target (line:6)

---

<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:** [21 July 2020 16:34 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/22 "2020-07-21T16:34:49Z")

</div>

Might be worth exiting NR - manual npm uninstall node-red-contrib-alexa-remote2 - _make sure both node\_modules/node-red-contrib-alexa-remote2 and node\_modules/alexa-remote2 have both been removed_ and then manually npm install node-red-contrib-alexa-remote2 and see if you get anywhere?

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [21 July 2020 17:12 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/23 "2020-07-21T17:12:16Z")

</div>

I have removed and install with no luck. i even remove npm node\_modules folders etc.

so i installed  
npm install node-red-contrib-alexa-remote2@3.10.1

This worked and allowed me to authorise via proxy first time

---

<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:** [21 July 2020 20:10 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/24 "2020-07-21T20:10:42Z")

</div>

That's similiar to what happened to me when I re-installed it last week - it worked again (and it was still on 3.10.1 at that time.

I think it must be a bit of randomness going on with the Amazon authorisation

I notice that the underlying node used as been updated again 2 days ago so I still don't think things are finished yet on this subject

---

<div class="post-metadata">

**Author:** ![whmoorejr](https://avatars.discourse-cdn.com/v4/letter/w/e56c9b/32.png) [@whmoorejr](https://discourse.nodered.org/u/whmoorejr)\
**Post date:** [24 July 2020 03:30 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/25 "2020-07-24T03:30:26Z")

</div>

I've been using 3 different nodes to control Alexa (depending on what I wanted to do). I just updated to 3.10.3, hoping to fix the remote2 authorization issue. My other two nodes were working (Alexa-smart-home & Alexa-home) After the update on just the Alexa-remote2 node, now all three nodes aren't functioning.

The error I get withe Alexa-Remote2 is similar to the issue E1cid was getting. When I click on one of the routines, I get a pop-up that says "Cannot GET /alexa-remote-routines.json" or "Cannot GET /alexa-remote-devices.json". node-red also say's "This node is a type unknown to your installation of Node-Red". There are no options to add or update the account information to even get to the next page where it can deny my password.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [24 July 2020 06:54 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/26 "2020-07-24T06:54:03Z")

</div>

That sounds similar to my error, i suggest uninstalling the node. Then go in to the .node-red folder and remove the alexa-remote2 folder in the node\_modules folder. Then via command line navigate to .node-red folder and npm install

```auto
npm install node-red-contrib-alexa-remote2@3.10.1

```

---

<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:** [24 July 2020 07:14 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/27 "2020-07-24T07:14:12Z")

</div>

JFI -I just tried re-installing on a Pi  
Start condition - NR palette manager says not installed and I had no node-red-contrib-alexa-remote2 folder and no alexa-remote2 folder

installed via palette - it installed 3.10.1 ! (According to the little I know - I'm thinking maybe my package-lock.json has something to do with that? - but just guessing)

Anyway - I updated to 3.10.3 via palette manger - configured it like this

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/a/ca46396f8499c6d588a910d1846887f81a34cea7.png)

(I made sure I used a new file to hold the cookie)

All works fine  
[edit] Just for my own piece of mind - I uninstalled it again - checked folders and alexa-remote2 was still there (node-red-contrib-alexa-remote2 wasn't) - npm uninstalled it - checked package.json and package-lock.json - no mention of it - so re-isntalled node-red-contrib-alexa-remote2 and it installed v 3.10.3 this time

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/5/c581b9b79aef27f0473acf18c7d65832c9c934e8.png)  
[/edit]

---

<div class="post-metadata">

**Author:** ![sneakynuts](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sneakynuts](https://discourse.nodered.org/u/sneakynuts)\
**Post date:** [1 August 2020 01:35 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/29 "2020-08-01T01:35:28Z")

</div>

Anyone got a firestick basic to work with this palete?

---

<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:** [1 August 2020 08:09 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/30 "2020-08-01T08:09:52Z")

</div>

Could you ask your question in a new thread please? 🙂

---

<div class="post-metadata">

**Author:** ![sneakynuts](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sneakynuts](https://discourse.nodered.org/u/sneakynuts)\
**Post date:** [3 August 2020 10:17 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/31 "2020-08-03T10:17:05Z")

</div>

Sure thing!

---

<div class="post-metadata">

**Author:** ![sneakynuts](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sneakynuts](https://discourse.nodered.org/u/sneakynuts)\
**Post date:** [27 August 2020 07:45 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/32 "2020-08-27T07:45:23Z")

</div>

Anyone else having issues all of a sudden with the cookie generation?

---

<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:** [27 August 2020 08:05 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/33 "2020-08-27T08:05:59Z")

</div>

I saw someone had raised an issue on Github yesterday

> <https://github.com/586837r/node-red-contrib-alexa-remote2/issues/147#issuecomment-680783313>
>
> it seems that Amazon changed things ...
> After I did a new setup of my node-red I am not able to connect...

My setup has carried on working - did your fails or were you setting a new instance up

---

<div class="post-metadata">

**Author:** ![sneakynuts](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sneakynuts](https://discourse.nodered.org/u/sneakynuts)\
**Post date:** [27 August 2020 13:01 UTC](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211/34 "2020-08-27T13:01:59Z")

</div>

Just stopped on existing install  
Node keeps asking to open ip:3456  
When i do, it logs in correctly and tells me cookie is generated but i get 'unexpected end to json' error

[Previous page](https://discourse.nodered.org/t/alexa-remote2-nodes-issue/30211.md?page=1)