# Alexa Remote2 event nodes not working (again)

**URL:** <https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266>\
**Category:** General\
**Created:** [3 August 2023 00:50 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266 "2023-08-03T00:50:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [3 August 2023 00:50 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/1 "2023-08-03T00:50:35Z")

</div>

I know at least a few of us use this node, it seems to be broken again.

There are lots of reports on GitHub but no solutions.

Has anyone here found a fix ?

---

<div class="post-metadata">

**Author:** ![Giamma](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@Giamma](https://discourse.nodered.org/u/Giamma)\
**Post date:** [3 August 2023 09:08 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/2 "2023-08-03T09:08:43Z")

</div>

Same problem here but no solutions ...

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [3 August 2023 09:17 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/3 "2023-08-03T09:17:53Z")

</div>

I'm using alexa-remote-fork version 3.11.3 and that is working fine for me.  
 ![alexa-remote-fork](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/003725c1d307541841bb6718802684581aff21eb.png)  
Just checked the various Alexa nodes, this version was updated 3-months ago, so might be worth trying.

> **[node-red-contrib-alexa-remote2-applestrudel](https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel)**
>
> node-red nodes for interacting with alexa

---

<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:** [3 August 2023 09:52 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/4 "2023-08-03T09:52:33Z")

</div>

Same issue here  
@dynamicdave The issue we are having is that we are not getting any output from  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/e/ce54e0e72b6833d360edc9d921a32461747a5d70.png)

node

Are you able to receive output from yours?

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [3 August 2023 10:50 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/6 "2023-08-03T10:50:40Z")

</div>

Yes. Just asked her "Alexa, what is the time".  
 ![evant](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/2/e2ca6eb21c75678e403208ff28ec7ee2f6e91930.png)

---

<div class="post-metadata">

**Author:** ![Giamma](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@Giamma](https://discourse.nodered.org/u/Giamma)\
**Post date:** [3 August 2023 11:05 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/7 "2023-08-03T11:05:36Z")

</div>

In Italy "applestrudel" - on device activity - don't work ...... (test in this moment)

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [3 August 2023 11:43 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/8 "2023-08-03T11:43:31Z")

</div>

Here are some more details of my setup - I initialise the Alexa node every 6-hours with this flow...

 ![alexa_initialise](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/c/5c4525830142383d7601e7075894c3b5d81b7cf1.png)  
At 7:00am each morning I get a weather report delivered to the Alexa Echo Dot in my back bedroom.  
 ![daily_weather_report](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/4/046146acfe5ad9624db3542b8706363fd1129c6c.png)

---

<div class="post-metadata">

**Author:** ![Giamma](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@Giamma](https://discourse.nodered.org/u/Giamma)\
**Post date:** [3 August 2023 11:50 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/9 "2023-08-03T11:50:32Z")

</div>

Ok, to be clear, "applestrudel" works fine in every node but not on device activity;  
this node don't works, the others yes ....

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [3 August 2023 12:00 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/10 "2023-08-03T12:00:52Z")

</div>

I've not tried Applestrudel recently, I just thought as it had been updated just 3-months ago it would have all the latest fixes. I'll see if I can find a spare RPi to test it out (as I can't install on my existing system as there is a name conflict and I don't want to mess around with my working system as I'm sure I'd break it).

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [3 August 2023 23:55 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/11 "2023-08-03T23:55:26Z")

</div>

> [@dynamicdave](#):
>
> alexa-remote-fork

Thanks for checking Dave 😃  
I assume it's this one [node-red-contrib-alexa-remote-fork](https://github.com/hgross/node-red-contrib-alexa-remote-fork) which hasn't been updated in 3 years 🤨

Just swapped out applstrudel for alexa-remote-fork and events work again.

If anyone else wants to try -

```auto
$ cd .node-red/
$ npm remove node-red-contrib-alexa-remote2-applestrudel
$ npm install node-red-contrib-alexa-remote-fork

```

You will probably see a warning

`npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.`

Not sure what other fixes it must be missing, so will need to test out other nodes.  
But at least it should be fixable by reverting some of the changes in latest applestrudel.

Will post issue with this info on GitHub.

> <https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/138#issuecomment-1664796865>
>
> I'm unsure what happened, but I'm using this node-red integration for my home as…sistant setup. It was working earlier this morning, but now the Alexa events are no longer firing, even though I haven't changed anything. I tried reloading the Alexa login, restarting node-red, and restarting home assistant, but none of that seemed to work. I'm on the latest version of the node. Any advice or fixes would be greatly appreciated. Thanks!
> 
> Edit: The whole node isn't broken, sending commands to Alexa still works, the node just won't fire events from Alexa

---

<div class="post-metadata">

**Author:** ![stephenn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stephenn/32/66644_2.png) [@stephenn](https://discourse.nodered.org/u/stephenn)\
**Post date:** [4 August 2023 00:37 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/12 "2023-08-04T00:37:59Z")

</div>

Would it be possible for someone WAY SMARTER than me to compare the code for the working On Device Activity Node in Fork to the same node for Applestrudel to see what is different and causing issue? I don't have the knowledge to do so.

---

<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:** [4 August 2023 15:32 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/13 "2023-08-04T15:32:44Z")

</div>

This has also worked for me to restore getting Alexa commands 🙂

Quite wierd that an older fork still works! (just read the github comments so now understand its using an older protocol/access method that still works)

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [4 August 2023 16:24 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/14 "2023-08-04T16:24:19Z")

</div>

Yeah, I haven't tested all other nodes yet, but haven't noticed any issues so far. 🤫

Seems like it identifies the problem so should be fixable in newer versions at least.

---

<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:** [4 August 2023 16:59 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/15 "2023-08-04T16:59:24Z")

</div>

Slight problem using node-red-contrib-alexa-remote-fork - the flow I use to send commands to my Alexa device no longer works

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

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [4 August 2023 17:26 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/16 "2023-08-04T17:26:38Z")

</div>

How have you configured that node??

To direct the message to a specific device, I use this...  
 ![alexa_specific_device](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/a/3a81a02601022badf69d7c5250a53e427a8b175a.png)

You can also direct the message to a device via msg.destination or a variable...  
 ![alexa_device_via_a_variable](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/3/e312de1aa5bb2c884efa65e59ab6ca70f205c715.png)

What happens if you try a very simple test flow, like this..  
 ![alexa+test](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/e/5e745d26dee9136fc47beca16a8f88422156d322.png)

---

<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:** [4 August 2023 17:43 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/17 "2023-08-04T17:43:49Z")

</div>

My speak flow still works fine

This flow uses NR to send a command to a device as if you were speaking to it

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/6/06c010eccaa29d4a93769d0639a5aa2cbd3cbb39.png)

---

<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:** [4 August 2023 17:58 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/18 "2023-08-04T17:58:28Z")

</div>

Text commands was add in

- **5.0.2**
  - Incorporate `textCommand` from mbalduccini ([Added textCommand by mbalduccini · Pull Request #181 · 586837r/node-red-contrib-alexa-remote2 · GitHub](https://github.com/586837r/node-red-contrib-alexa-remote2/pull/181/files))

So I doubt alexa-remote-fork version 3.11.3 will have it.

Is slightly weird that it is showing in the config though.

---

<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:** [4 August 2023 18:27 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/19 "2023-08-04T18:27:53Z")

</div>

I did think that might be the reason.☹

I'll temp have to go back to gluing an earpiece close to the microphone input and using my old text-speech flow

---

<div class="post-metadata">

**Author:** ![chx0003](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/chx0003/32/81732_2.png) [@chx0003](https://discourse.nodered.org/u/chx0003)\
**Post date:** [5 August 2023 05:04 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/20 "2023-08-05T05:04:48Z")

</div>

You can use **node-red-contrib-alexa-remote2-applestrudel** instead of **alexa-remote-fork** , only changing a bit of text in the file _alexa-remote2/alexa-wsmqtt.js_ line 174, change `this.connectType2()` to `this.connectType1()` then restart NodeRed and "On Device Activity" and even "Routine Text Command" should work again.

---

<div class="post-metadata">

**Author:** ![Giamma](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@Giamma](https://discourse.nodered.org/u/Giamma)\
**Post date:** [5 August 2023 06:00 UTC](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266/21 "2023-08-05T06:00:15Z")

</div>

Works! 👍 ..... Thank you!

[Next page](https://discourse.nodered.org/t/alexa-remote2-event-nodes-not-working-again/80266.md?page=2)