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

@instathings/modbus-herdsman-converters

v2.0.7

Published

A set of descriptor for converting data coming from Modbus sensors

Downloads

9

Readme

modbus-herdsman-converters

Collection of device converters to be used with modbus2mqtt.

Contribute

Add an entry to devices.js. Every device can be described with the following structure:

{
    model: 'SDM120', // Vendor model number, look on the device for a model number
    vendor: 'Eastron', // Vendor of the device (only used for documentation and startup logging)
    description: Energy meter', // Description of the device, copy from vendor site. (only used for documentation and startup logging)
    supports: 'voltage, current, power', // Actions this device supports (only used for documentation)
    fromModbus: {}, // We will add this later
    toModbus: {}, // Should be empty, unless device can be controlled (e.g. lights, switches).
},

Specify input register addresses

From the device datasheet add the addresses of the input register you want to read data from in the fromModbus key this way.

{
  ...,
  fromModbus: {
    temperature: {
      address: 30001
    }
  }
}

Where the key temperature will be the output key to report the value. A descriptor like this would generate the following output:

{
  temperature: <value read from address>
}