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-hs100

v1.1.0

Published

Node red module for controlling HS100 and HS110 devices.

Downloads

29

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

biddsterbiddster

Keywords

node-redtp-linktplinkhs100

Readme

node-red-contrib-hs100

This Node-RED node is for controlling tp-link Wi-Fi Smart Plug - Model HS100 (and HS110).

This node has only been tested with a HS100(UK). The HS100 is also available in US and EU plug versions. We expect they will work too.

This node simply wraps the excellent work here https://github.com/czjs2/hs100-api.

Installation

Change directory to your node red installation:

$ npm install node-red-contrib-hs100

Alternatively, use the Palette Manager in Node-RED.

Configuration

Drag this node on to a worksheet and double click it. Enter the IP address of the plug on your network. Save and deploy.

Dynamic configuration of IP address

Alternatively you can dynamically set the IP address of the plug. To do this set the message property 'hs100_address' to the address of the plug that you wish to control.

Actuations

This node supports a number of actuations that are invoked by sending a msg.topic or msg.payload to the node's input.

| Topic/Payload | Description | | ------------------ | :----------------------------------------------------------------------------------: | | on | To turn the HS100 on. | | off | To turn the HS100 off. | | info | Get all plug info, combination of sysinfo, cloudinfo consumption, schedulenextaction | | sysinfo | Get general plug information. | | cloudinfo | Get TP-Link Cloud information. | | consumption | Get power consumption data | | powerstate | Returns true if plug is on. | | schedulenextaction | | | schedulerules | | | awayrules | | | timerrules | | | time | | | timezone | | | scaninfo | | | model | |

Turn on

Turn off

Obtain power consumption data

The HS100 is a simple switch and does not support consumption. The HS110 includes the power consumption feature.

I have been told that the power consumption feature is working with the Australian version of the HS110.

I don't have an HS110 to test with though.

To obtain the power consumption, send a message to this node's input with the topic or payload set to consumption. The consumption data will be sent via this node's output in msg.payload.