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 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-alexa-home

v2.0.2

Published

Works directly with Alexa in your local network

Downloads

342

Readme

node-red-contrib-alexa-home

CI

Known Vulnerabilities

npmjs package registry

The node just works wihtin your local network - no extra cloud stuff is required.

Installation

Install directory from your Node-RED Settings Pallete

or

Install using npm

$ npm install node-red-contrib-alexa-home

Alexa Generation 3 devices

Alexa devices of generation #3 are not using the information used within the detection process. They do rely that all communication is done on port 80! To estatlish this you got 2 different ways to go.

ALEXA_PORT and running as root

You must define an environment variable ALEXA_PORT and set its value to 80. When running node-red as systemd unit as

Environment=ALEXA_PORT=80

To test the change you can also start node-red manually with following:

ALEXA_PORT=80 node-red start

using iptables and port forwarding

You can leave everything as it is and just define port forwarding using iptables

sudo iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 60000

Please consider that any changes to iptables are not presistent, after reboot you have to forward the port again, or use iptables-save as described here

Message Object Properties

the follow msg properties are generated within this node

payload.on: true|false

payload.bri: brightness 0-255

payload.xy Color XY object

alexa_ip: <ip of alexa device interacting with node-red>

With version 1.x now also the input is processed within the node and updates the data to alexa. Within the alexa app you are now able to get the current state of your nodes.

Message input to the nodes

At the moment you can input as payload objects:

Normal an input is not routed as output because this would possibly cause endless update loops. But if you want this and know what you are doing, you can set the output param on the msg to let the input passthrough.