npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-red-contrib-amazon-echo

v0.1.17

Published

Alexa-controlled Node-RED nodes for the latest Amazon Echo devices.

Readme

node-red-contrib-amazon-echo

❗️Important (2026): Alexa local discovery is unreliable / may not work

As of 2026, users continue to report unstable or broken Alexa connectivity with node-red-contrib-amazon-echo, including:

  • Devices not being discovered reliably (or at all)
  • Previously discovered devices disappearing or showing “Device not responding”
  • Voice commands sometimes executing with a delay while Alexa reports an error

This module relies on local Philips Hue Bridge (v1) emulation for Alexa discovery and control. Since August 2025, changes on Amazon’s side appear to have affected this approach.

For detailed analysis, community findings, and historical context, see:

  • GitHub issue: “Device not responding – August 2025” #210

Alternatives

If you require a stable and future-proof Alexa - Node-RED integration, consider:

  • Community-maintained alternatives listed at https://www.voicenodes.com
  • DuloNode - an Alexa Smart Home Skill-based solution created by the author of node-red-contrib-amazon-echo

Node-RED Contrib Amazon Echo module

Alexa controlled Node-Red nodes supporting the latest Amazon Echo devices

NO Alexa Skills required.

NO cloud dependencies.

Installation

Install from your Node-RED Manage Palette

or

Install using npm

$ npm install node-red-contrib-amazon-echo

How to use

  • Add Amazon Echo Hub node to your flow.
  • Add multiple Amazon Echo Device nodes linked to the Amazon Echo Hub node.
  • Note: Use unique names for device nodes. Alexa will use the node name to manage your smart device.
  • Ask "Alexa, discover devices" or start the discovery procedure from the Alexa mobile app.

Usage screenshot

Features

  • Turning on/off
  • Dimming
  • Setting the light color

Supported devices

  • All Echo devices

Example Alexa commands

  • "Alexa, turn on/off {device}"
  • "Alexa, switch on/off {device}"
  • "Alexa, set {device} to 50%"
  • "Alexa, turn my {device} light green"
  • "Alexa, set the {device} light to orange"
  • "Alexa, make the {device} warmer"
  • "Alexa, brighten {device} to 60 percent"
  • "Alexa, dim the {device} lights"

Requirements

The Amazon Echo Hub node starts a service listening on port 80, which requires the Node-RED process to be started with root privileges or requires firewall rules to redirect the traffic.

Troubleshooting

Detailed troubleshooting instructions can be found on the Wiki.

Bugs and feature requests

Please create an issue on GitHub.