# Node-red-contrib-amazon-echo problem

**URL:** <https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320>\
**Category:** General\
**Created:** [8 May 2020 17:03 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320 "2020-05-08T17:03:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pfanne98](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@Pfanne98](https://discourse.nodered.org/u/Pfanne98)\
**Post date:** [8 May 2020 17:03 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320/1 "2020-05-08T17:03:41Z")

</div>

Hi,  
i have a Raspberry Pi 4 with IOBroker and the Node-Red adapterand i like to control some lights with alexa, so i get the palette "node-red-contrib-amazon-echo". After that i insertet the amazon echo hub and a device with a unique Name. But if a serch for new devices in the alexa app it cant find the new device.  
So what have i done wrong. Maybe i have to ad an alexa skill or something?

 ![Node-red problem](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/7/87a4cbc0a578ee93efffba8dce257ebe67968e71.png)  
sorry for my very bad english im a german guy and dont speak english so often...

---

<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:** [8 May 2020 17:30 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320/2 "2020-05-08T17:30:31Z")

</div>

I got tripped-up by the same or a very similar problem.  
Here's a link to what I found to use port 8980 rather than port 80 (which needs to run as root - not good news).

> [@Alexa Voice Command to start the flow?](https://discourse.nodered.org/t/alexa-voice-command-to-start-the-flow/15606/4):
>
> I use node-red-contrib-alexa-home-skill as that's the only one I've found that works for my particular Echo version Its convoluted to setup (as all the alexa stuff is in different ways) but it works for me Requires setting up account on 3rd party site

Hope it works for you.  
Regards, David

---

<div class="post-metadata">

**Author:** ![Pfanne98](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@Pfanne98](https://discourse.nodered.org/u/Pfanne98)\
**Post date:** [9 May 2020 12:17 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320/3 "2020-05-09T12:17:37Z")

</div>

I tried that but it didn't work at all.  
But thanks anyway 🙂

---

<div class="post-metadata">

**Author:** ![Pfanne98](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@Pfanne98](https://discourse.nodered.org/u/Pfanne98)\
**Post date:** [9 May 2020 12:23 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320/4 "2020-05-09T12:23:55Z")

</div>

with blockly the connection to Amazon echo works, however, it is much more cumbersome than with node-red.  
If it is blockly then it should be because of the connection from node red to the amazon 2 adapter or?

---

<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:** [8 July 2020 12:23 UTC](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320/5 "2020-07-08T12:23:58Z")

</div>

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