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

@pilot-things/node-red-contrib-pilot-things

v1.5.0

Published

Provides Node-RED nodes for Pilot Things interoperability

Downloads

13

Readme

node-red-contrib-pilot-things

  

This project offers multiple nodes which integrate Pilot Things and Node-RED one another.

Currently, we offer nodes that allow Node-RED to submit data to the Pilot Things platform for storage or decoding (the decoded result can then be used in the flow for other purposes).

Prerequisites

You need valid Pilot Things credentials to use these nodes.

To sign-up for free, please contact us.

For support go to https://support.pilot-things.com/.

Installation

Either use the Menu - Manage palette option or run the following command in your Node-RED user directory - typically ~/.node-red

npm install @pilot-things/node-red-contrib-pilot-things

Send node usage

Note: This node is only available for Pilot Things Studio customers

This node sends data to Pilot Things Studio. Pilot Things will automatically create the sensors, and can decode the data after associating the sensor to a product.

This node can be used in a Kerlink Gateway with SPN.

See node help for more details.

Decode node usage

Note: There are two nodes available

  • decode library is for Sensor Library customers
    • With this node timestamp and metadata cannot be provided, only data and product ID.
  • decode studio is for Pilot Things Studio customers

The decode node decodes sensor payload to convert it to measurements. You must use a product ID that is a sensor unique ID. For instance product e6ae04f9-5f57-4992-8bda-41ae5ff0bf8d is an Adeunis LoRaWAN Field Test. A full list is available here.

If you do not have a real sensor you can use the inject node. For instance using the following JSON would decode sample data for a Field Test.

{
    "data": "0F2E3CCD3338D23931F5",
    "metadata": {
        "FPort": 3
    },
    "productId": "e6ae04f9-5f57-4992-8bda-41ae5ff0bf8d"
}

See node help for more details.

FAQ

My data is in a non supported data format! How do I submit it to the Pilot Things nodes?

One can use a function node with 1 output containing the code to convert the input into a format that the Pilot Things nodes will understand. For example, if the input is a byte array, the following code will convert it into a NodeJS Buffer, which the Pilot Things nodes understand:

msg.payload.data = Buffer.from(msg.payload.data);
return msg;

The decoder errors with "Too many invalid login attempts"!

Combining the frequent uplink nature of some devices with the auto locking of accounts in Pilot Things after too many unsuccessful attempts can result in your account being locked on the platform by the node. To mitigate this, the node will stop trying after 5 failed logins in a row and will refuse to try again until one of the following occurs:

  • The credentials used by the node to authenticate with Pilot Things have been changed;
  • 1 hour has passed since the last failed login;
  • The node context has been cleared (this happens upon a restart of the Node-RED server unless it has been configured otherwise).