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

v1.0.3

Published

Node-RED nodes for connecting to a Kolibri Broker (e.g. HMS Hub)

Downloads

12

Readme

Node-RED Kolibri Nodes

There are two types of Node-RED nodes, kolibri in and kolibri out, which can be used to exchange data with a Kolibri Broker (e.g. HMS Hub).

Attention:

Since version the plugin version 1.0.0 we only support the Kolibri Protocol V3.2. Logging in with a Kolibri Version v3.2 to a Kolibri Broker will convert the user to a new format introduced in v2.0. After that it is not possible to use the original ('kolibri') protocol version with that user. If you want to continue using the older Kolibri Protocol version please use the plugin version 0.4.1.

Please also keep in mind that the timestamp resolution changed since the kolibri protocol v2.0 to microseconds resolution.

For more details about changes in v1.0.0 please see CHANGELOG.md or the release logs.

Nodes Overview

Kolibri in

This node can subscribe to the specified data point path of the connected Kolibri Broker. The kolibri in has the following properties.

Required:

  • Kolibri broker
  • Data Point Path: Path to the data variable

Optional:

  • Name: Node name that is displayed in the Node-RED flow
  • Resume: if true, all data values from last successful request will be included. The client must login with the same clientId from the session that should be resumed.

Kolibri out

This node can publish to the specified data point path of the connected Kolibri Broker. The kolibri out has the following properties.

Required:

  • Kolibri broker
  • Data Point Path: Path to the data variable

Optional:

  • Name: Node name that is displayed in the Node-RED flow

Getting started

Add a node to a Node-RED flow. Edit the node configurations, deploy it.

Node Configuration

On the edit page you can adjust three properties.

Kolibri Broker: Add or choose a Broker connection. New Broker connections require the following properties.

Required:

  • Server URL
  • Server Port
  • Username
  • Password
  • Path: Login path
  • Kolibri protocol version
  • Project

Optional:

  • Name: Node name that is displayed in the Node-RED flow
  • Enable Proxy
  • Proxy Server
  • Proxy Port
  • ClientId: Client name or uuid of the connecting client (required if resume is set on the Kolibri In Node)

After deploying the flow the Nodes are trying to connect to the configured Broker(s). If the connections are established successfully a green "connected" label is displayed. If the connection is closed a red "disconnected" label is displayed.