# 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:** 1\
**Showing post:** 2

<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

---

_[View the full topic](https://discourse.nodered.org/t/node-red-contrib-amazon-echo-problem/26320)._