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-ha-state

v1.3.0

Published

observable things in node red

Downloads

54

Readme

node-red-contrib-ha-state

observable things in node red

Install

via the manage palette menu

or manually:

cd <NODE_RED_PATH>
npm install node-red-contrib-ha-state

Functionality

  1. Create a type of a device with a Thing Type Node, which has 2 settings:
    1. attributes: constants that are specific to a thing
    2. states: properties that can change over time
  2. Store a device state in a Thing node
  3. Fire an event when the value of a state changes using an Event node
  4. Compare the values with custom rules in a Gate node
  5. Output the value to another flow with a Value node
  6. Change a state via an Action node

e.g. if you have smart thermostats:

  1. create the Thermostat Thing type:
    1. add attribute id
    2. add temperature, target and battery as states
  2. create a living room Thing of type Thermostat (this represents the actual device)
    1. set the id for the device
  3. manipulate the living room thermostat via the action node, and listen to changes via the event node

Note: a Thing is just a virtual representation of the device, any connection to a real device must be done seperately