# Node Red, Alexa

**URL:** <https://community.gladysassistant.com/t/node-red-alexa/5442>\
**Category:** Configuration\
**Created:** [June 12, 2020, 10:28am UTC](https://community.gladysassistant.com/t/node-red-alexa/5442 "2020-06-12T10:28:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![benPi](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/b/53a042/32.png) [@benPi](https://community.gladysassistant.com/u/benPi)\
**Post date:** [June 12, 2020, 10:28am UTC](https://community.gladysassistant.com/t/node-red-alexa/5442/1 "2020-06-12T10:28:46Z")

</div>

Hello,

I am sharing a need that could lead to an integration.

I use Alexa for:  
1- Talking to Gladys v4  
2- Its AI is really powerful and works quite intuitively.  
You can send a percentage or a color.

Here is the plugin that works best 🙂

> **[node-red-contrib-amazon-echo](https://flows.nodered.org/node/node-red-contrib-amazon-echo)**
>
> Alexa-controlled Node-RED nodes for the latest Amazon Echo devices.

There is also a Node Red skill:

> **[Node-RED](https://www.amazon.fr/dp/B01N0D97FZ)**
>
> Node-RED

Finally, on Home Assistant, they integrate Node Red

Advantage: Instead of developing many integrations, you can rely on all the nodes already created, especially Alexa but there are many others.

[![](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/9/90b47d19f3d1c2053451192c75bb7ef8149d74f0.jpeg "Mastering Node-RED: Custom Alexa Commands + Node-RED Dashboard") ](https://www.youtube.com/watch?v=4QfoXdcfqKI)

> **[repository/node-red at master · hassio-addons/repository](https://github.com/hassio-addons/repository/tree/master/node-red)**
>
> Home Assistant Community Add-ons. Contribute to hassio-addons/repository development by creating an account on GitHub.

Since Node Red already works with npm and Docker containers, it looks very similar.  
As Gladys V4 does not have all its features, I am trying to use this in the meantime to create simple automations.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [June 15, 2020, 8:19am UTC](https://community.gladysassistant.com/t/node-red-alexa/5442/2 "2020-06-15T08:19:42Z")

</div>

Great! So you managed to integrate them together, huh? 🙂 Don’t hesitate to write a little tutorial if so!

---

<div class="post-metadata">

**Author:** ![benPi](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/b/53a042/32.png) [@benPi](https://community.gladysassistant.com/u/benPi)\
**Post date:** [June 16, 2020, 6:49pm UTC](https://community.gladysassistant.com/t/node-red-alexa/5442/3 "2020-06-16T18:49:57Z")

</div>

> [@pierre-gilles](#):
>
> write a small tutorial if yes!

No, it’s a need but I don’t master module creation enough, mainly because I don’t know JavaScript.

Actually, it works directly: Alexa → NodeRed → Device. But as a result, there is no global management of devices (scenarios, etc.).

Another small blockage: Alexa dot 3rd gen works on port 80, which cannot be listened to if Node Red is not in administrator: you therefore need to redirect the port. And in a Docker container, it’s still complex for me.