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-trigger-atleast-every-x

v1.1.0

Published

Send On and Off and if long time no On then send On and then Off. Now proper closing.

Downloads

34

Readme

node-red-contrib-trigger-atleast-every-x

node-red-trigger-atleast-every-x is used to watch the payload coming in. Usually used with an ON or OFF payloads. When ON is received, the unit resets and sends an ON. If it's reset and OFF is received, an OFF is send and then the node makes sure that after x seconds an ON is send, unless reset. Incoming OFF payloads are ignored in the mean time. If the unit has send an ON because of the timer, after y seconds, an OFF is send and the unit is reset to send an On.

Install

Run the following command in the root directory of your Node-RED install. Usually this is ~/.node-red

npm install node-red-contrib-trigger-atleast-every-x

Using

This node sends an On payload when an On is received and an off when an Odd payload is received. So, it's a piece of wire. Well, no. When the last send payload is an Off payload, then a timer is started. If that timer runs down, an On payload is send and another timer is started after which an Off is send. When in "timer" mode, then off payloads are ignored. But an On when in timer mode resets all (and sends an On). So it filters messages witrh the same payload in sequence and has a timer mode to make sure On's are send, even in Off mode.

This is useful in an Under Floor Heating system. The pump of an UFH divider unit needs to be run every week or 10 days for somewhere around 5 minutes, to keep it in operation condition. On a related note, if you'd control the pump, for instance with an Tasmota-ted Sonoff Basic, then make sure it's turning on or off is delayed some 2 minutes, so the valves / thermal actuators on the UFH unit are either 1/3 open or 2/3 closed. If the pump runs and all UFH loops are closed, either you'lll heard it, or you'll run the risk of damaging the unit. Best way to avoid this is have a (!) loop per UFH unit some 1/4 or 1/3 open all the time. It heats up if something else heats up, so an bathroom or a hal, something in the middle of the house, but not often visited, os a good candidate.