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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nagisa~/node-red-dsmr

v1.0.3

Published

A node to give some structure to a stream of DSMR data

Readme

This package provides a single node for the node-red project. The node consumes a stream of DSMR data such as what might be obtained from an electricity meter over its P1 port over serial or TCP connection, frames it and gives the data a little bit of structure.

Unlike many other implementations of DSMR parsers, this one does not attempt to prescribe meaning to any specific COSEM object, nor does it attempt to figure out the type of specific values. This is best achieved by piping the output of this node to the follow up function node and transforming the data in whatever way is appropriate to your use-case.

Instead the output payload will be replaced with an object along the lines of

{
  "vendor": "ABC",
  "identifier": "USUALLY_SN",
  "0-0:1.0.0": ["240218021712W"],
  "1-0:1.8.0": ["00001234.567*kWh"],
  ...
}

The value for each COSEM object may have more than a single element. This is especially relevant for readings sourced from M-BUS devices or objects representing logs.

It is up to the user to apply meaning to the OBIS keys. Your utility should have documentation on their website explaining the data model of their DSMR telegrams. Obtain it in order to apply meaning to the OBIS codes you get in the payloads after processing.

If you're interested in the specifics of the format, refer to the P1 Companion Standard.