@project-chip/matter-node.js-examples 0.7.5 → 0.8.0-alpha.0-20240310-474da21a

package/src/examples/DeviceNodeFullLegacy.ts

@@ -0,0 +1,307 @@
+#!/usr/bin/env node
+/**
+ * @license
+ * Copyright 2022-2024 Matter.js Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+/**
+ * IMPORTANT: This example uses a Legacy API which will be deprecated in the future.
+ * It is just still here to support developers in converting their code to the new API!
+ */
+
+/**
+ * This example shows how to create a simple on-off Matter device as a light or as a socket.
+ * It can be used as CLI script and starting point for your own device node implementation.
+ */
+
+/**
+ * Import needed modules from @project-chip/matter-node.js
+ */
+// Include this first to auto-register Crypto, Network and Time Node.js implementations
+import { CommissioningServer, MatterServer } from "@project-chip/matter-node.js";
+
+import { BleNode } from "@project-chip/matter-node-ble.js/ble";
+import { Ble } from "@project-chip/matter-node.js/ble";
+import { OnOffLightDevice, OnOffPluginUnitDevice, logEndpoint } from "@project-chip/matter-node.js/device";
+import { Format, Level, Logger } from "@project-chip/matter-node.js/log";
+import { QrCode } from "@project-chip/matter-node.js/schema";
+import { StorageBackendDisk, StorageManager } from "@project-chip/matter-node.js/storage";
+import { Time } from "@project-chip/matter-node.js/time";
+import {
+    commandExecutor,
+    getIntParameter,
+    getParameter,
+    hasParameter,
+    requireMinNodeVersion,
+    singleton,
+} from "@project-chip/matter-node.js/util";
+import { DeviceTypeId, VendorId } from "@project-chip/matter.js/datatype";
+import DummyWifiNetworkCommissioningClusterServer from "./cluster/DummyWifiNetworkCommissioningServerLegacy.js";
+
+const logger = Logger.get("Device");
+
+requireMinNodeVersion(16);
+
+/** Configure logging */
+switch (getParameter("loglevel")) {
+    case "fatal":
+        Logger.defaultLogLevel = Level.FATAL;
+        break;
+    case "error":
+        Logger.defaultLogLevel = Level.ERROR;
+        break;
+    case "warn":
+        Logger.defaultLogLevel = Level.WARN;
+        break;
+    case "info":
+        Logger.defaultLogLevel = Level.INFO;
+        break;
+}
+
+switch (getParameter("logformat")) {
+    case "plain":
+        Logger.format = Format.PLAIN;
+        break;
+    case "html":
+        Logger.format = Format.HTML;
+        break;
+    default:
+        if (process.stdin?.isTTY) Logger.format = Format.ANSI;
+}
+
+if (hasParameter("ble")) {
+    // Initialize Ble
+    Ble.get = singleton(
+        () =>
+            new BleNode({
+                hciId: getIntParameter("ble-hci-id"),
+            }),
+    );
+}
+
+const storageLocation = getParameter("store") ?? ".device-node";
+const storage = new StorageBackendDisk(storageLocation, hasParameter("clearstorage"));
+logger.info(`Storage location: ${storageLocation} (Directory)`);
+logger.info(
+    'Use the parameter "-store NAME" to specify a different storage location, use -clearstorage to start with an empty storage.',
+);
+
+class Device {
+    private matterServer: MatterServer | undefined;
+
+    async start() {
+        logger.info(`node-matter`);
+
+        /**
+         * Initialize the storage system.
+         *
+         * The storage manager is then also used by the Matter server, so this code block in general is required,
+         * but you can choose a different storage backend as long as it implements the required API.
+         */
+
+        const storageManager = new StorageManager(storage);
+        await storageManager.initialize();
+
+        /**
+         * Collect all needed data
+         *
+         * This block makes sure to collect all needed data from cli or storage. Replace this with where ever your data
+         * come from.
+         *
+         * Note: This example also uses the initialized storage system to store the device parameter data for convenience
+         * and easy reuse. When you also do that be careful to not overlap with Matter-Server own contexts
+         * (so maybe better not ;-)).
+         */
+
+        const deviceStorage = storageManager.createContext("Device");
+
+        if (deviceStorage.has("isSocket")) {
+            logger.info("Device type found in storage. -type parameter is ignored.");
+        }
+        const isSocket = deviceStorage.get("isSocket", getParameter("type") === "socket");
+        const deviceName = "Matter test device";
+        const vendorName = "matter-node.js";
+        const passcode = getIntParameter("passcode") ?? deviceStorage.get("passcode", 20202021);
+        const discriminator = getIntParameter("discriminator") ?? deviceStorage.get("discriminator", 3840);
+        // product name / id and vendor id should match what is in the device certificate
+        const vendorId = getIntParameter("vendorid") ?? deviceStorage.get("vendorid", 0xfff1);
+        const productName = `node-matter OnOff ${isSocket ? "Socket" : "Light"}`;
+        const productId = getIntParameter("productid") ?? deviceStorage.get("productid", 0x8000);
+
+        const netInterface = getParameter("netinterface");
+        const port = getIntParameter("port") ?? 5540;
+
+        const uniqueId = getIntParameter("uniqueid") ?? deviceStorage.get("uniqueid", Time.nowMs());
+
+        deviceStorage.set("passcode", passcode);
+        deviceStorage.set("discriminator", discriminator);
+        deviceStorage.set("vendorid", vendorId);
+        deviceStorage.set("productid", productId);
+        deviceStorage.set("isSocket", isSocket);
+        deviceStorage.set("uniqueid", uniqueId);
+
+        /**
+         * Create Device instance and add needed Listener
+         *
+         * Create an instance of the matter device class you want to use.
+         * This example uses the OnOffLightDevice or OnOffPluginUnitDevice depending on the value of the type  parameter.
+         * To execute the on/off scripts defined as parameters a listener for the onOff attribute is registered via the
+         * device specific API.
+         *
+         * The below logic also adds command handlers for commands of clusters that normally are handled device internally
+         * like identify that can be implemented with the logic when these commands are called.
+         */
+
+        const onOffDevice = isSocket ? new OnOffPluginUnitDevice() : new OnOffLightDevice();
+        onOffDevice.addOnOffListener(on => commandExecutor(on ? "on" : "off")?.());
+
+        onOffDevice.addCommandHandler("identify", async ({ request: { identifyTime } }) =>
+            logger.info(`Identify called for OnOffDevice: ${identifyTime}`),
+        );
+
+        /**
+         * Create Matter Server and CommissioningServer Node
+         *
+         * To allow the device to be announced, found, paired and operated we need a MatterServer instance and add a
+         * commissioningServer to it and add the just created device instance to it.
+         * The CommissioningServer node defines the port where the server listens for the UDP packages of the Matter protocol
+         * and initializes deice specific certificates and such.
+         *
+         * The below logic also adds command handlers for commands of clusters that normally are handled internally
+         * like testEventTrigger (General Diagnostic Cluster) that can be implemented with the logic when these commands
+         * are called.
+         */
+
+        this.matterServer = new MatterServer(storageManager, { mdnsInterface: netInterface });
+
+        const commissioningServer = new CommissioningServer({
+            port,
+            deviceName,
+            deviceType: DeviceTypeId(onOffDevice.deviceType),
+            passcode,
+            discriminator,
+            basicInformation: {
+                vendorName,
+                vendorId: VendorId(vendorId),
+                nodeLabel: productName,
+                productName,
+                productLabel: productName,
+                productId,
+                serialNumber: `node-matter-${uniqueId}`,
+            },
+            delayedAnnouncement: hasParameter("ble"), // Delay announcement when BLE is used to show how limited advertisement works
+            activeSessionsChangedCallback: fabricIndex => {
+                console.log(
+                    `activeSessionsChangedCallback: Active sessions changed on Fabric ${fabricIndex}`,
+                    commissioningServer.getActiveSessionInformation(fabricIndex),
+                );
+            },
+            commissioningChangedCallback: fabricIndex => {
+                console.log(
+                    `commissioningChangedCallback: Commissioning changed on Fabric ${fabricIndex}`,
+                    commissioningServer.getCommissionedFabricInformation(fabricIndex)[0],
+                );
+            },
+        });
+
+        // optionally add a listener for the testEventTrigger command from the GeneralDiagnostics cluster
+        commissioningServer.addCommandHandler("testEventTrigger", async ({ request: { enableKey, eventTrigger } }) =>
+            logger.info(`testEventTrigger called on GeneralDiagnostic cluster: ${enableKey} ${eventTrigger}`),
+        );
+
+        /**
+         * Modify automatically added clusters of the Root endpoint if needed
+         * In this example we change the networkCommissioning cluster into one for "Wifi only" devices when BLE is used
+         * for commissioning, to demonstrate how to do this.
+         * If you want to implement Ethernet only devices that get connected to the network via LAN/Ethernet cable,
+         * then all this is not needed.
+         * The same as shown here for Wi-Fi is also possible theoretical for Thread only or combined devices.
+         */
+
+        if (hasParameter("ble")) {
+            // matter.js will create a Ethernet-only device by default when ut comes to Network Commissioning Features.
+            // To offer e.g. a "Wi-Fi only device" (or any other combination) we need to override the Network Commissioning
+            // cluster and implement all the need handling here. This is a "static implementation" for pure demonstration
+            // purposes and just "simulates" the actions to be done. In a real world implementation this would be done by
+            // the device implementor based on the relevant networking stack.
+            // The NetworkCommissioningCluster and all logics are described in Matter Core Specifications section 11.8
+            commissioningServer.addRootClusterServer(DummyWifiNetworkCommissioningClusterServer);
+        }
+
+        commissioningServer.addDevice(onOffDevice);
+
+        await this.matterServer.addCommissioningServer(commissioningServer);
+
+        /**
+         * Start the Matter Server
+         *
+         * After everything was plugged together we can start the server. When not delayed announcement is set for the
+         * CommissioningServer node then this command also starts the announcement of the device into the network.
+         */
+
+        await this.matterServer.start();
+
+        logEndpoint(commissioningServer.getRootEndpoint());
+
+        // When we want to limit the initial announcement to one medium (e.g. BLE) then we need to delay the
+        // announcement and provide the limiting information.
+        // Without delaying the announcement is directly triggered with the above "start()" call.
+        if (hasParameter("ble")) {
+            // Announce operational in BLE network only if we have ble enabled, else everywhere
+            await commissioningServer.advertise({ ble: true });
+        }
+
+        /**
+         * Print Pairing Information
+         *
+         * If the device is not already commissioned (this info is stored in the storage system) then get and print the
+         * pairing details. This includes the QR code that can be scanned by the Matter app to pair the device.
+         */
+
+        logger.info("Listening");
+        if (!commissioningServer.isCommissioned()) {
+            const pairingData = commissioningServer.getPairingCode({
+                ble: hasParameter("ble"),
+                softAccessPoint: false,
+                onIpNetwork: false,
+            });
+
+            const { qrPairingCode, manualPairingCode } = pairingData;
+
+            console.log(QrCode.get(qrPairingCode));
+            logger.info(
+                `QR Code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=${qrPairingCode}`,
+            );
+            logger.info(`Manual pairing code: ${manualPairingCode}`);
+        } else {
+            logger.info("Device is already commissioned. Waiting for controllers to connect ...");
+        }
+    }
+
+    async stop() {
+        await this.matterServer?.close();
+    }
+}
+
+const device = new Device();
+device
+    .start()
+    .then(() => {
+        /* done */
+    })
+    .catch(err => console.error(err));
+
+process.on("SIGINT", () => {
+    // Clean up on CTRL-C
+    device
+        .stop()
+        .then(() => {
+            // Pragmatic way to make sure the storage is correctly closed before the process ends.
+            storage
+                .close()
+                .then(() => process.exit(0))
+                .catch(err => console.error(err));
+        })
+        .catch(err => console.error(err));
+});

package/src/examples/IlluminatedRollerShade.ts

@@ -0,0 +1,130 @@
+/**
+ * @license
+ * Copyright 2022-2024 Matter.js Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+// Include this first to auto-register Crypto, Network and Time Node.js implementations
+import "@project-chip/matter-node.js";
+
+import { GoToLiftPercentageRequest, WindowCoveringServer } from "@project-chip/matter.js/behaviors/window-covering";
+import { OnOffLightDevice, OnOffLightRequirements } from "@project-chip/matter.js/devices/OnOffLightDevice";
+import { WindowCoveringDevice } from "@project-chip/matter.js/devices/WindowCoveringDevice";
+import { ServerNode } from "@project-chip/matter.js/node";
+
+/**
+ * This example demonstrates implementation of a "composed" device comprising multiple sub-devices
+ *
+ * Our example device, the Excelsior 1000 EZ-Nite™, is a roller shade with an illuminated valance.
+ */
+
+const LiftingWindowCoveringServer = WindowCoveringServer.with("Lift", "AbsolutePosition", "PositionAwareLift");
+
+/**
+ * Implementation of the Matter WindowCovering cluster for the shade motor.
+ *
+ * TODO - some of this should probably move to WindowCoveringServer
+ */
+class RollerShade extends LiftingWindowCoveringServer {
+    get currentPos() {
+        return this.state.currentPositionLiftPercent100ths ?? 0;
+    }
+
+    get targetPos() {
+        return this.state.targetPositionLiftPercent100ths ?? 0;
+    }
+
+    set targetPos(position: number) {
+        this.state.targetPositionLiftPercent100ths = position ?? 0;
+    }
+
+    override async initialize() {
+        this.reactTo(this.events.targetPositionLiftPercent100ths$Change, this.writeTargetToMotor);
+
+        await this.readTargetFromMotor();
+        if (this.targetPos === null) {
+            this.targetPos = this.currentPos;
+        }
+    }
+
+    override upOrOpen() {
+        // 0 = 0%, fully open
+        this.targetPos = 0;
+    }
+
+    override downOrClose() {
+        // 10000 = 100%, fully closed
+        this.targetPos = 10000;
+    }
+
+    override stopMotion() {
+        this.targetPos = this.currentPos;
+    }
+
+    override goToLiftPercentage(this: RollerShade, request: GoToLiftPercentageRequest) {
+        this.targetPos = request.liftPercent100thsValue;
+    }
+
+    protected async writeTargetToMotor() {
+        // For this contrived example we just log the target position and don't actually animate our fake roller shade
+        console.log("Window covering target position is now", `${this.targetPos / 100}%`);
+    }
+
+    protected async readTargetFromMotor() {
+        // Our fake shade is stuck open
+        this.state.currentPositionLiftPercent100ths = 0;
+    }
+
+    protected set currentPos(value: number) {
+        this.state.currentPositionLiftPercent100ths = value;
+    }
+}
+
+/**
+ * Implementation of the OnOff cluster for our valance light.
+ */
+class ValanceLight extends OnOffLightRequirements.OnOffServer {
+    override initialize() {
+        this.reactTo(this.events.onOff$Change, this.#stateChanged);
+    }
+
+    #stateChanged(value: boolean) {
+        console.log(`Valance is now ${value ? "illuminated" : "dark"}`);
+    }
+}
+
+/**
+ * Our Matter node.
+ */
+const node = new ServerNode({
+    id: "excelsior1000",
+
+    productDescription: {},
+
+    commissioning: {
+        passcode: 20202021,
+        discriminator: 3840,
+    },
+
+    basicInformation: {
+        vendorName: "Acme Corporation",
+        productName: "Excelsior 1000 EZ-Nite™",
+        vendorId: 0xfff1,
+        productId: 0x8000,
+        serialNumber: "1234-12345-123",
+    },
+
+    parts: [
+        {
+            type: WindowCoveringDevice.with(RollerShade),
+            id: "shade",
+        },
+
+        {
+            type: OnOffLightDevice.with(ValanceLight),
+            id: "valance",
+        },
+    ],
+});
+
+await node.run();

package/src/examples/LightDevice.ts

@@ -0,0 +1,60 @@
+/**
+ * @license
+ * Copyright 2022-2024 Matter.js Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+// This demonstrates bringing a "light" device online with matter.js.
+
+// Include this first to auto-register Crypto, Network and Time Node.js implementations
+import "@project-chip/matter-node.js";
+
+import { OnOffLightDevice, OnOffLightRequirements } from "@project-chip/matter.js/devices/OnOffLightDevice";
+import { ServerNode } from "@project-chip/matter.js/node";
+
+// Matter exposes functionality in groups called "clusters".  For this example device we override the matter.js "On/Off"
+// cluster implementation to print status to the console.
+class ReportingOnOffServer extends OnOffLightRequirements.OnOffServer {
+    // Intercept the "on" command to the Matter On/Off cluster to print a log message.
+    override async on() {
+        console.log("Turning light ON");
+        await super.on();
+    }
+
+    // This is the functional inverse of on() above.
+    //
+    // For demonstration purposes we update state ourselves rather than deferring to matter.js's default "off" handler
+    // via super.off().
+    override off() {
+        console.log("Turning light OFF");
+        this.state.onOff = false;
+    }
+
+    // Use event handlers to log on/off state reactively, after it changes.
+    override initialize() {
+        this.events.onOff$Change.on(value => {
+            console.log(`Light is now ${value ? "ON" : "OFF"}`);
+        });
+    }
+}
+
+// Devices are compositions of behaviors like OnOffServer above.  To extend an existing device you use builder methods.
+//
+// In this case we are using with() to install our On/Off cluster behavior.
+const ExampleLight = OnOffLightDevice.with(ReportingOnOffServer);
+
+// Physical devices appear as "nodes" on a Matter network.  As a device implementer you use a NodeServer to bring a
+// device online.
+//
+// Note there are a large number of options to NodeServer that we are allowing to take default values here.  See
+// IlluminatedRollerShade.ts for a more detailed example.
+const node = await ServerNode.create();
+
+// Nodes are a composition of endpoints.  Add a single endpoint to the node, our example light device.
+await node.add(ExampleLight);
+
+// Our device is now built and we can bring the node online.
+//
+// Note that you may serve multiple nodes from a single process.  We only have one, however, so we can use the run()
+// method of the node.
+await node.run();