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

v1.4.0

Published

Node to communicate with Atlas Scientific Ezo modules over I2C.

Downloads

25

Readme

node-red-contrib-ezo

This Node-Red is designed to communicate with Atlas Scientific Ezo modules over I2C.

Install

Either use the Manage Palette option in the Node-RED Editor menu, or run the following command in your Node-RED user directory - typically ~/.node-red

npm install --unsafe-perm node-red-contrib-ezo

Usage

Designed to accept all standard commands from the Atlas Scientific documentation.

Input

All commands can be sent as a single string in msg.payload, those which have a command and input value separated by a comma can be broken into msg.command and msg.payload properties. Commands can differ from one Ezo module to another, please refer to Atlas Scientific's website for documentation. Below are a few examples of commands structured in an acceptable manner.

Since v1.3.0 msg.address can be set dynamically on input. Since v1.4.0 msg.bus can be set dynamically on input.

msg = { payload: 'L,0' };  // turns led off

msg = { command: 'L', payload: 1 };  // turns led on

msg = { command: 'L', payload: false };  // turns led off

msg = { command: 'L', payload: '1' };  // turns led on

msg = { payload: 'Status' };  // returns status

msg = { command: 'R'};  // reads probe

msg = { command: 'R', address: 105, bus: 1 }  // reads probe at address 105 and bus 1

Ouptut

Some commands such as 'Sleep', 'Factory', and 'I2C,n' do not provide a response so will not generate an output message. Most commands will generate a response containing the original command and a value, however some Ezo modules can generate multiple values in which the msg.payload will contain an array. If the output value can be parsed to a number it will be, otherwise it will be a string. Since v1.1.1 extra properties in input pass through to output.

msg = {
    topic: String,
    command: String,
    payload: String / Number / Array,
}

Examples of commands and responses:

Ezo Board: Temperature
Command: Status
Raw Response: 1?STATUS,P,3.28

Node Output:

msg = {
    topic: 'tempurature',
    command: 'STATUS',
    payload: [
        'P',
        '3.28',
    ],
};

--- OR ---

Ezo Board: pH
Command: R
Raw Response: 19.831

Node Output:

msg = {
    topic: 'ph',
    command: 'R',
    payload: 9.831,
};

Errors

Since v1.1.0 errors are catchable by the CATCH node. If an error occurs, a message will not be sent. Common errors include the following:

'Invalid payload!' - Error: Command must be under 32 characters.
'Syntax Error!' - Error: Ezo board did not recognize the command.
'No data to send.' - Warning: Command sent to the Ezo board was empty.

Important Note

This node uses the I2C-bus package from @fivdi. You can find his work on github: https://github.com/fivdi/i2c-bus