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

v1.4.3

Published

A collection of Node-RED nodes for IoTFlows.

Downloads

13

Vulnerabilities

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

Links

Maintainers

iotflowsiotflows

Keywords

node-rediotflows

Readme

A collection of Node-RED nodes to interact with IoTFlows to send and receive IoT messages, execute a function on the device, or publish alerts/notifications via IoTFlows Cloud.

Usage

All IoTFlows nodes are used with the IoTFlows Console. You can create a free account and start integration IoT to your Node-RED. For specific information about the IoTFlows console, go to the IoTFlows Documentation or visit IoTFlows Getting Started Examples..

Nodes Provided:

  • datastream out
  • datastream in
  • alert channel out
  • action start
  • action finish

Server Configuration

You can configure the Server settings of these nodes using the credentials of A Device Client created in the IoTFlows Console. To get started, you can create a project, create a device, and create a Device Client from the right side navigation.

Optional: if you are interested in remote accessing the Node-RED of your device, you may check out the IoTFlowsOS. Learn more at https://docs.iotflows.com/downloads

datastream out

The datastream out node is used to publish data to IoTFlows Cloud. You will then be able to refresh the Topic and all your Data Streams for your Device will be displayed. The msg.payload sent to this node will be published to the cloud.

datastream in

The datastream in node is used to subscribe to the Data Streams and received the messages published by other devices in your Project.

alert channel out

The alert channel out node is used to publish an Alert to an IoTFlows Alert Channel. Members of the Alert Channel can receive these alerts with their preference of text message or email, or simply by visiting the IoTFlows Console.

action start

The action start node is used to define an Action that can be executed by another Device or web application. This can be used to to execute a function or to control an actuator connected to this device. These Actions can be executed using an HTTP POST call with Basic Access Authentication of the Device Client Credentials. Learn more at Execute Action from Cloud

action finish

Every action start needs to be finished with an action finish node to confirm that the action was properly executed. When an action is triggered with an HTTP request, this will result in a HTTP response code of 200.

Additional Resources

  • IoTFlows Documentation
  • Publishing a Data Stream
  • Subscribing to a Data Stream
  • Publishing an Alert
  • Execute an Action