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

victron-vrm-api

v0.2.11

Published

Interface with the Victron Energy VRM API

Downloads

297

Readme

This node makes it easy to use the VRM API for data retrieval. Though not all possible API calls have been implemented, it can be used for retrieving and creating alarms and fetching installations statistics. It can also be used to retrieve the solar forecast data.

VRM API flow

In order to allow the node to query your site, an access-token needs to be created and filled out in the configuration node.

Inputs

  • payload (string|number|json) - the trigger to query the VRM API

Outputs

  • payload (json) : the VRM answer

The output of the answer depends on the selected configuration. See the VRM API documentation in case you need assistance with interpreting the output.

Configuration

  • Name (string) : The name of the node
  • VRM (config) : The configuration node
  • VRM site id (number) : The site to query. Note that this is the multi-digit number you see in the url of your vrm-site like this: https://vrm.victronenergy.com/installation/123456/
  • API type (string) : The query type
  • Verbose (boolean) : Show the used url in the debug tab?

There are currently 4 API types to choose from:

  • Users
  • Installations
  • Widgets
  • Dynamic ESS

Depending on the API type, more or less extra fields appear.

In case of installation stats there appear some extra configuration options

  • Attribute (string) : Which attribute to fetch
  • Interval (string) : Time between retrieved data points
  • Start (integer) : Timestamp from which to fetch data
  • End (integer) : Timestamp to which to fetch data

In case of installation `dess`` there are even more configuration options.

VRM API edit panel

Note that instead of filling out the number of the VRM site id for installations and widgets in the box, you can also use context variables, e.g. {{flow.siteId}} or {{global.vrmId}}. This allows to query the site that has been set in this context field. Of course you need to make sure that context contains a valid VRM site id first.

Examples

There are several examples included in the package. In order to use them, import them via the victron-vrm-api examples dropdown on the Import nodes page (accessible via the menu or by pressing ctrl-i).

References

Please use either the issues on the GitHub site or the Node-RED space on our community for questions, troubleshooting and suggestions.