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-shelly-mqtt

v1.2.8

Published

Shelly MQTT protocol helper for Node-Red.

Downloads

235

Readme

node-red-contrib-shelly-mqtt

Shelly MQTT support for Node-Red.

Configuration

This node includes a simple config node which accepts MQTT broker (same as native Node-Red MQTT config instance) and device name. The device name is the topic prefix of the device (without shellies/).

For example, if your device is using the topic: shellies/shellyswitch25-abcdefg then your device name is shellyswitch25-abcdefg.

Usage

The Shelly-Device node accepts one input and emit one output. The input is used to control the device through message object:

  • msg.action = on or off for relay, open, close or stop for roller devices
  • msg.position = position in percentage for roller devices
  • msg.optime = the operation time (milliseconds) of the required action (roller only, very useful for venetian blinds)

The output will emit the current status of the relay for relay devices or the current status and position of the roller for roller devices. It is also emits the current power of the relay, but mosly for inner testing. Use it if you want :)

And of course - you can also set the action from the UI (the node will try the input message if defined and then fall back to the UI action).

Emit stop

Use this flag to set the device to report only a stop action after the required operation (from input) is completed. You can use this to chain multiple actions one by one.

Node name (extra feature)

The node name, if not set, is taken from the configuration node together with the action, so the node name resulting in a nice string describing the required action without setting the name in the UI.

You can also use your own name and add * at the end so the node will add the action to your custom name (for example: my node name*).