A fast and extensible framework to connect any device with your application
The Eclipse Thingweb node-wot is a framework for implementing Web of Things servers and clients in Node.js. It is written from the ground up with Typescript with the goal of providing a fast and extensible framework for IoT applications. Node-wot wants to give developers the ability to create complex business logic without worrying about protocol and low-level details leveraging on a standard metadata format, the Thing Description (TD). Thanks to the TD abstraction developers can find a set of satellite tools to create their applications in a fast and easy way.
The Web of Things (WoT) tackles IoT fragmentation by extending standardized web technologies. It simplifies IoT application development, promoting flexibility and interoperability. WoT preserves existing IoT standards, ensuring reuse, and provides an adaptable, abstract architecture based on real-world use cases across domains. In essence, WoT paves the way for seamless IoT integration by defining an information model capable of describing Things and Services and how to interact with them. This information model is called the Thing Description (TD) and it is a JSON-LD document that describes the Thing and its capabilities, including its network services (APIs), its network interactions, and security requirements. The TD is the cornerstone of the Web of Things architecture and it is the main abstraction that node-wot uses to implement its functionalities. Every Thing has the following capabilities or "affordances":
- ⚙️ Properties: a property is a value that can be read, written or observed. For example, a temperature sensor can have a property that represents the current temperature.
- 🦾 Actions: an action is an operation that can be invoked. For example, a light bulb can have an action that turns it on or off.
- ⚡ Events: an event is a notification. For example, a motion sensor can send an event when it detects motion.
For further information please refer to the official W3C Web of Things website.
- Installation
- Examples
- Implemented/supported features
- No time for explanations - show me a running example!
- Online Things
- Documentation
- Contributing
- License
The framework can be used in two ways: as a library or as a CLI tool. In this section we will explain how to install the framework in both ways.
The framework is composed by different packages that users can use as they please. The core package is @node-wot/core and it is the only mandatory package to install. The other packages are bindings that allow the framework to communicate with different protocols.
Warning
We no longer actively support Node.js version 16 and lower.
Platforms specific prerequisites:
- Linux: Meet the node-gyp requirements:
- Python v3.6, v3.7, or v3.8
- make
- A proper C/C++ compiler toolchain, like GCC
- Windows: Install the Windows build tools through a CMD shell as administrator:
npm install -g --production windows-build-tools
- Mac OS: Meet the node-gyp requirements:
xcode-select --install
If you want to use node-wot as a library in your Node.js application, you can use npm to install the node-wot packages that you need. To do so, cd inside your application folder, and run:
npm i @node-wot/core @node-wot/binding-http --save
To use node-wot as a browser-side JavaScript Library, the browser needs to support ECMAScript 2015.
Using a browser with only ES5 support (e.g., IE 11) might be possible if you add polyfills. If you want to use node-wot as a library in your browser application, you can install the @node-wot/browser-bundle as following:
npm i @node-wot/browser-bundle --save
you can find more installation options in the specific package README.
You can alternatively use node-wot via its command line interface (CLI). Please visit the CLI tool's Readme to find out more.
Another option is to use node-wot inside a docker image. Make sure you are under Linux or under WSL if you are running on Windows.
Clone the repository:
git clone https://github.com/eclipse-thingweb/node-wot
Go into the repository:
cd node-wot
Build the Docker image named wot-servient from the Dockerfile:
npm run build:docker
Run the wot-servient as a container:
docker run --rm wot-servient -h
With node-wot you can create server-side Things, in WoT jargon we call this operation "expose a Thing" or you can create client-side Things, in WoT jargon we call this operation "consume a Thing". An exposed Thing allows you to bring your device or services to the Web with just a few lines of code. On the other hand, with a consumed Thing, you have a fixed interface to interact with devices, potentially using different protocols/frameworks. In the following section, we will show how to create a simple counter Thing and how to consume it. Assuming you have installed and configured node-wot as a library, you can create and expose a counter Thing as follows:
// Required steps to create a servient for creating a thing
const { Servient } = require("@node-wot/core");
const { HttpServer } = require("@node-wot/binding-http");
const servient = new Servient();
servient.addServer(new HttpServer());
servient.start().then( async (WoT) => {
// Then from here on you can use the WoT object to produce the thing
let count = 0;
const exposingThing = await WoT.produce({
title: "Counter",
description: "A simple counter thing",
properties: {
count: {
type: "integer",
description: "current counter value",
observable: true,
readOnly: true
}
},
actions: {
increment: {
description: "increment counter value",
}
}
})
exposingThing.setPropertyReadHandler("count", () => { return count; });
exposingThing.setActionHandler("increment", () => { count++; exposingThing.emitPropertyChange("count"); });
await exposingThing.expose();
// now you can interact with the thing via http://localhost:8080/counter
});Now supposing you want to interact with the device, you have to consume its Thing Description as follows:
// client.js
// Required steps to create a servient for a client
const { Servient } = require("@node-wot/core");
const { HttpClientFactory } = require("@node-wot/binding-http");
const servient = new Servient();
servient.addClientFactory(new HttpClientFactory(null));
servient.start().then(async (WoT) => {
const td = await WoT.requestThingDescription("http://localhost:8080/counter");
// Then from here on you can consume the thing
let thing = await WoT.consume(td);
thing.observeProperty("count", async (data) => { console.log("count:", await data.value()); });
for (let i = 0; i < 5; i++) {
await thing.invokeAction("increment");
}
}).catch((err) => { console.error(err); });If you execute both scripts you will see count: ${count} printed 5 times. We host a more complex version of this example at http://plugfest.thingweb.io/examples/counter.html and you can find the source code in the counter example folder. You can also find more examples in the examples folder for JavaScript and in the examples folder for TypeScript. Finally, for your convenience, we host a set of online Things that you can use to test your applications. You can find more information about them in the Online Things section.
- HTTP ✔️
- HTTPS ✔️
- CoAP ✔️
- CoAPS ✔️
- MQTT ✔️
Firestore//lastSupportedVersion ✔️- Websocket ➕ (Server only)
- OPC-UA ➕ (Client only)
- NETCONF ➕ (Client only)
- Modbus ➕ (Client only)
- M-Bus ➕ (Client only)
Note
More protocols can be easily added by implementing ProtocolClient, ProtocolClientFactory, and ProtocolServer interface.
Note
The bindings for binding-fujitsu and binding-oracle were removed after v0.7.x due to lack of maintainers.
- JSON ✔️
- Text (HTML, CSS, XML, SVG) ✔️
- Base64 (PNG, JPEG, GIF) ✔️
- Octet stream ✔️
- CBOR ✔️
- EXI ⏲️
Can't find your preferred MediaType? More codecs can be easily added by implementing ContentCodec interface. Read more in the Documentation section.
Run all the steps above including "Link Packages" and then run this:
wot-servient -h
cd examples/scripts
wot-servient
Without the "Link Packages" step, the wot-servient command is not available and node needs to be used (e.g., Windows CMD shell):
# expose
node packages\cli\dist\cli.js examples\scripts\counter.js
# consume
node packages\cli\dist\cli.js --client-only examples\scripts\counter-client.js
- Go to http://localhost:8080/counter and you'll find a thing description
- Query the count by http://localhost:8080/counter/properties/count
- Modify the count via POST on http://localhost:8080/counter/actions/increment and http://localhost:8080/counter/actions/decrement
- Application logic is in
examples/scripts/counter.js
First build the docker image and then run the counter example:
# expose
docker run -it --init -p 8080:8080/tcp -p 5683:5683/udp -v "$(pwd)"/examples:/srv/examples --rm wot-servient /srv/examples/scripts/counter.js
# consume
docker run -it --init -v "$(pwd)"/examples:/srv/examples --rm --net=host wot-servient /srv/examples/scripts/counter-client.js --client-only
- The counter exposes the HTTP endpoint at 8080/tcp and the CoAP endpoint at 5683/udp and they are bound to the host machine (with
-p 8080:8080/tcp -p 5683:5683/udp). - The counter-client binds the network of the host machine (
--net=host) so that it can access the counter thing's endpoints. --initallows the containers to be killed with SIGINT (e.g., Ctrl+c)-v "$(pwd)"/examples:/srv/examplesmounts theexamplesdirectory to/srv/exampleson the container so that the node inside the container can read the example scripts.
An example of how to use node-wot as a browser-side library can be found under examples/browser/index.html.
To run it, open examples/browser/index.html in a modern browser, and consume the test Thing available under http://plugfest.thingweb.io:8083/testthing to interact with it.
The JavaScript code that uses node-wot as a library to power this application can be found under: examples/browser/index.js
We offer online simulated Things that are available to be used by anyone.
Their TDs are available at the following links:
- Counter: HTTP at http://plugfest.thingweb.io:8083/counter and CoAP at coap://plugfest.thingweb.io:5683/counter
- Smart Coffee Machine: HTTP at http://plugfest.thingweb.io:8083/smart-coffee-machine and CoAP at coap://plugfest.thingweb.io:5683/smart-coffee-machine
- TestThing: HTTP at http://plugfest.thingweb.io:8083/testthing and CoAP at coap://plugfest.thingweb.io:5683/testthing
- Presence sensor: MQTT at https://zion.vaimee.com/things/urn:uuid:0a028f8e-8a91-4aaf-a346-9a48d440fd7c
- Smart Clock: CoAP at https://zion.vaimee.com/things/urn:uuid:913cf8cb-3687-4d98-8d2f-f6f27cfc7162
- Simple Coffee Machine: HTTP at https://zion.vaimee.com/things/urn:uuid:7ba2bca0-a7f6-47b3-bdce-498caa33bbaf
All of them require no security mechanism to be communicated with. Below are small explanations of what they can be used for:
- Counter: It has a count property that can be read or observed and can be incremented or decremented via separate actions. It is also possible to reset the count value, obtain when the last change occurred, subscribe to a change in the count value or get the count value as an image.
- TestThing: This Thing exists primarily for testing different data schemas and payload formats. It also has events attached to affordances that notify when a value changes.
- Smart Coffee Machine: This is a simulation of a coffee machine that also has a simple user interface that displays the values of properties.
In addition to proving a real-life device example, it can be used for testing
uriVariables. You can ask it to brew different coffees and monitor the available resource level. - Presence Sensor: It mocks the detection of a person by firing an event every 5 seconds.
- Smart Clock: It simply has a property affordance for the time. However, it runs 60 times faster than real-time to allow time-based decisions that can be easily tested.
- Simple Coffee Machine: This is a simpler simulation of the coffee machine above.
Warning
⚒️ We are planning to extend this section and to provide a more detailed documentation. Stay tuned!
This library implements the WoT Scripting API:
- Editors Draft in master
- Working Draft corresponding to node-wot release versions
Additionally, you can have a look at our API Documentation.
To learn by examples, see examples/scripts to have a feeling of how to script a Thing or a Consumer.
To add a new codec, you need to implement the ContentCodec interface. The interface is defined as follows:
export interface ContentCodec {
getMediaType(): string;
bytesToValue(bytes: Buffer, schema: DataSchema, parameters?: {[key: string]: string}): any;
valueToBytes(value: any, schema: DataSchema, parameters?: {[key: string]: string}): Buffer;
}Finally you can add to your servient the new codec as follows:
const { ContentSerdes, JsonCodec } = require("@node-wot/core");
// e.g., assign built-in codec for *new* contentType
const cs = ContentSerdes.get();
cs.addCodec(new JsonCodec("application/calendar+json"));
// e.g., assign *own* MyCodec implementation (implementing ContentCodec interface)
cs.addCodec(new MyCodec("application/myType"));The package td-tools provides utilities around Thing Description (TD) tooling:
- Thing Description (TD) parsing
- Thing Model (TM) tooling
- Asset Interface Description (AID) utility
- ...
Logging in node-wot is implemented via the debug package.
This allows users to enable log messages for specific logging levels (info, debug, warn, or error) or packages.
Which log messages are emitted is controlled by the DEBUG environment variable.
In the following, we will show a couple of examples of its usage using wildcard characters (*).
Note, however, that the syntax for setting an environment variable depends on your operating system and the terminal you use.
See the debug documentation for more details on platform-specific differences.
First, you can enable all log messages by setting DEBUG to a wildcard like so:
DEBUG=* npm startTo only show node-wot-specific logging messages, prefix the wildcard with node-wot:
DEBUG=node-wot* npm startTo only show a specific log level, use one of info, debug, warn, or error as the suffix.
Note in this context that you can provide multiple values for DEBUG.
For example, if you want to show only debug and info messages, you can use the following:
DEBUG='*debug,*info' npm startFinally, you can choose to only display log messages from a specific node-wot package.
For example, if you only want to see log messages for the core package, use the following:
DEBUG=node-wot:core* npm startUsing the log levels above, you can also apply more fine-grained parameters for logging.
For instance, if you only want to see error messages from the binding-coap package, use this:
DEBUG=node-wot:binding-coap*error npm startUsing NPM, you can install Node.js independent from the usually outdated package managers such as apt. This is nicely done by n:
sudo npm cache clean -f
sudo npm install -g n
To get the "stable" version:
sudo n stable
To get the "latest" version:
sudo n latest
Finally, make the node command available through:
sudo ln -sf /usr/local/n/versions/node/<VERSION>/bin/node /usr/bin/node
Please check out our contributing guidelines for more details.
If you are using Eclipse Thingweb node-wot within your organization, please support us by adding your logo to the Eclipse IoT adopters list. To do so, simply open an issue at the Eclipse Gitlab by providing the name of your organization, its logo, and a link to your organization or team. You should be affiliated with that organization for the issue to be implemented.
Dual-licensed under:
Pick one of these two licenses that fits your needs. Please also see the additional notices and how to contribute.
details
We distinguish between the following set of tests.
npm run testruns the default set of tests (without browser tests)npm run test:browserruns the browser tests only (requires Playwright)npm run test:allruns the combination of the afore mentioned tests
Run npm publish --workspaces in root node-wot folder.
- Delete
package-lock.jsonfile - Delete any local cache (like
node_modulesfolders etc.) - Run
npm install - Run
npm dedupe(see #765 (comment))