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-wot-discovery

v2.0.0

Published

An experimental Node-RED package for Discovery in the Web of Things (WoT).

Downloads

16

Readme

node-red-contrib-wot-discovery

Build Status platform NPM version Coverage Status JavaScript Style Guide

Experimental Node-RED package for discovery in the Web of Things (WoT). It provides a wot-discovery node that can be used for discovering and storing WoT Thing Descriptions (TDs) as well as a wot-scripting node that serves as an interface to node-wot for triggering interaction affordances. As a latest addition, a wot-fetch node provides a way to retrieve TDs directly from URLs using HTTP(S) or CoAP(S).

Screenshot of wot-fetch, wot-discovery, wot-scripting nodes

wot-fetch Node

The fetch node can retrieve TDs from URLs which can either be specified in the node itself or as a message property (using the field msg.tdUrl). It supports the URL schemes http(s) and coap(s).

wot-discovery Node

The discovery node can obtain TDs from the local network (using CoAP) or from a MQTT broker and save them either in the context or in the original message object that was passed to the node.

When using CoAP, you can choose between a number of different methods for obtaining TDs, all of which use IP multicast (both IPv4 and IPv6). You can choose between the multicast addresses for all IPv4/IPv6 nodes or the respective addresses for "All CoAP Nodes".

Supported methods for CoAP so far include:

  • Discovery from /.well-known/wot.
  • Discovery using the CoRE Link Format and /.well-known/core (the correct content type and resource type has to be set in the list of links).
  • Discovery from CoRE Resource Directories. For this method, available Resource Directories are discovered first which are then queried for links pointing to TDs.

For MQTT, WoT producers have to publish their TDs to a topic with the prefix wot/td which can then be queried by the discovery node.

wot-scripting Node

The scripting node consumes TDs that are passed in inside a message object (in the field thingDescription). You can choose which kind of affordance type should be triggered and define a filter (either by affordance name or by the semantic @type). If an affordance returns an output, you can choose where this output should be saved (either in the message or the context) and which field should be used.