@project-chip/matter-node.js-examples 0.11.0-alpha.0-20240909-b3b29745 → 0.11.0-alpha.0-20241006-eccb81ae1

package/dist/esm/tutorial/example02.js

@@ -1,7 +0,0 @@
-import "@project-chip/matter-node.js";
-import { OnOffLightDevice } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { ServerNode } from "@project-chip/matter.js/node";
-const node = await ServerNode.create();
-await node.add(OnOffLightDevice);
-await node.run();
-//# sourceMappingURL=example02.js.map

package/dist/esm/tutorial/example02.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tutorial/example02.ts"],
-  "sourcesContent": ["import \"@project-chip/matter-node.js\";\nimport { OnOffLightDevice } from \"@project-chip/matter.js/devices/OnOffLightDevice\";\nimport { ServerNode } from \"@project-chip/matter.js/node\";\n\nconst node = await ServerNode.create();\n\nawait node.add(OnOffLightDevice);\n\nawait node.run();\n"],
-  "mappings": "AAAA,OAAO;AACP,SAAS,wBAAwB;AACjC,SAAS,kBAAkB;AAE3B,MAAM,OAAO,MAAM,WAAW,OAAO;AAErC,MAAM,KAAK,IAAI,gBAAgB;AAE/B,MAAM,KAAK,IAAI;",
-  "names": []
-}

package/dist/esm/tutorial/example03.js

@@ -1,15 +0,0 @@
-import "@project-chip/matter-node.js";
-import { OnOffLightDevice, OnOffLightRequirements } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { ServerNode } from "@project-chip/matter.js/node";
-class MyOnOffServer extends OnOffLightRequirements.OnOffServer {
-  on() {
-    console.log("Turning on");
-  }
-  off() {
-    console.log("Turning off");
-  }
-}
-const node = await ServerNode.create();
-await node.add(OnOffLightDevice.with(MyOnOffServer));
-await node.run();
-//# sourceMappingURL=example03.js.map

package/dist/esm/tutorial/example03.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tutorial/example03.ts"],
-  "sourcesContent": ["import \"@project-chip/matter-node.js\";\nimport { OnOffLightDevice, OnOffLightRequirements } from \"@project-chip/matter.js/devices/OnOffLightDevice\";\nimport { ServerNode } from \"@project-chip/matter.js/node\";\n\nclass MyOnOffServer extends OnOffLightRequirements.OnOffServer {\n    override on() {\n        console.log(\"Turning on\");\n    }\n\n    override off() {\n        console.log(\"Turning off\");\n    }\n}\n\nconst node = await ServerNode.create();\n\nawait node.add(OnOffLightDevice.with(MyOnOffServer));\n\nawait node.run();\n"],
-  "mappings": "AAAA,OAAO;AACP,SAAS,kBAAkB,8BAA8B;AACzD,SAAS,kBAAkB;AAE3B,MAAM,sBAAsB,uBAAuB,YAAY;AAAA,EAClD,KAAK;AACV,YAAQ,IAAI,YAAY;AAAA,EAC5B;AAAA,EAES,MAAM;AACX,YAAQ,IAAI,aAAa;AAAA,EAC7B;AACJ;AAEA,MAAM,OAAO,MAAM,WAAW,OAAO;AAErC,MAAM,KAAK,IAAI,iBAAiB,KAAK,aAAa,CAAC;AAEnD,MAAM,KAAK,IAAI;",
-  "names": []
-}

package/dist/esm/tutorial/example04.js

@@ -1,10 +0,0 @@
-import "@project-chip/matter-node.js";
-import { OnOffLightDevice } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { ServerNode } from "@project-chip/matter.js/node";
-const node = await ServerNode.create();
-const light = await node.add(OnOffLightDevice);
-light.events.onOff.onOff$Changed.on((newValue) => {
-  console.log(`Light is ${newValue ? "on" : "off"}`);
-});
-await node.run();
-//# sourceMappingURL=example04.js.map

package/dist/esm/tutorial/example04.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tutorial/example04.ts"],
-  "sourcesContent": ["import \"@project-chip/matter-node.js\";\nimport { OnOffLightDevice } from \"@project-chip/matter.js/devices/OnOffLightDevice\";\nimport { ServerNode } from \"@project-chip/matter.js/node\";\n\nconst node = await ServerNode.create();\n\nconst light = await node.add(OnOffLightDevice);\n\nlight.events.onOff.onOff$Changed.on(newValue => {\n    console.log(`Light is ${newValue ? \"on\" : \"off\"}`);\n});\n\nawait node.run();\n"],
-  "mappings": "AAAA,OAAO;AACP,SAAS,wBAAwB;AACjC,SAAS,kBAAkB;AAE3B,MAAM,OAAO,MAAM,WAAW,OAAO;AAErC,MAAM,QAAQ,MAAM,KAAK,IAAI,gBAAgB;AAE7C,MAAM,OAAO,MAAM,cAAc,GAAG,cAAY;AAC5C,UAAQ,IAAI,YAAY,WAAW,OAAO,KAAK,EAAE;AACrD,CAAC;AAED,MAAM,KAAK,IAAI;",
-  "names": []
-}

package/dist/esm/tutorial/example05.js

@@ -1,14 +0,0 @@
-import "@project-chip/matter-node.js";
-import { OnOffLightDevice } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { ServerNode } from "@project-chip/matter.js/node";
-const node = await ServerNode.create();
-const light = await node.add(OnOffLightDevice);
-await node.start();
-await light.act(async (agent) => {
-  await agent.onOff.toggle();
-  console.log("On/off state after first toggle", agent.onOff.state);
-  await agent.onOff.toggle();
-  console.log("On/off state after second toggle", agent.onOff.state);
-});
-await node.close();
-//# sourceMappingURL=example05.js.map

package/dist/esm/tutorial/example05.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tutorial/example05.ts"],
-  "sourcesContent": ["import \"@project-chip/matter-node.js\";\nimport { OnOffLightDevice } from \"@project-chip/matter.js/devices/OnOffLightDevice\";\nimport { ServerNode } from \"@project-chip/matter.js/node\";\n\nconst node = await ServerNode.create();\n\nconst light = await node.add(OnOffLightDevice);\n\nawait node.start();\n\nawait light.act(async agent => {\n    await agent.onOff.toggle();\n    console.log(\"On/off state after first toggle\", agent.onOff.state);\n\n    await agent.onOff.toggle();\n    console.log(\"On/off state after second toggle\", agent.onOff.state);\n});\n\nawait node.close();\n"],
-  "mappings": "AAAA,OAAO;AACP,SAAS,wBAAwB;AACjC,SAAS,kBAAkB;AAE3B,MAAM,OAAO,MAAM,WAAW,OAAO;AAErC,MAAM,QAAQ,MAAM,KAAK,IAAI,gBAAgB;AAE7C,MAAM,KAAK,MAAM;AAEjB,MAAM,MAAM,IAAI,OAAM,UAAS;AAC3B,QAAM,MAAM,MAAM,OAAO;AACzB,UAAQ,IAAI,mCAAmC,MAAM,MAAM,KAAK;AAEhE,QAAM,MAAM,MAAM,OAAO;AACzB,UAAQ,IAAI,oCAAoC,MAAM,MAAM,KAAK;AACrE,CAAC;AAED,MAAM,KAAK,MAAM;",
-  "names": []
-}

package/src/examples/BridgedDevicesNode.ts

@@ -1,260 +0,0 @@
-#!/usr/bin/env node
-/**
- * @license
- * Copyright 2022-2024 Matter.js Authors
- * SPDX-License-Identifier: Apache-2.0
- */
-
-/**
- * This example shows how to create a new device node that is composed of multiple devices.
- * It creates multiple endpoints on the server. For information on how to add a composed device to a bridge please
- * refer to the bridge example!
- * 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 "@project-chip/matter-node.js";
-
-import { requireMinNodeVersion } from "@project-chip/matter-node.js/util";
-import { BridgedDeviceBasicInformationServer } from "@project-chip/matter.js/behavior/definitions/bridged-device-basic-information";
-import { VendorId } from "@project-chip/matter.js/datatype";
-import { logEndpoint } from "@project-chip/matter.js/device";
-import { OnOffLightDevice } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { OnOffPlugInUnitDevice } from "@project-chip/matter.js/devices/OnOffPlugInUnitDevice";
-import { Endpoint, EndpointServer } from "@project-chip/matter.js/endpoint";
-import { AggregatorEndpoint } from "@project-chip/matter.js/endpoints/AggregatorEndpoint";
-import { Environment, StorageService } from "@project-chip/matter.js/environment";
-import { ServerNode } from "@project-chip/matter.js/node";
-import { Time } from "@project-chip/matter.js/time";
-import { execSync } from "child_process";
-
-requireMinNodeVersion(16);
-
-/** Initialize configuration values */
-const { isSocket, deviceName, vendorName, passcode, discriminator, vendorId, productName, productId, port, uniqueId } =
-    await getConfiguration();
-
-/**
- * Create a Matter ServerNode, which contains the Root Endpoint and all relevant data and configuration
- */
-const server = await ServerNode.create({
-    // Required: Give the Node a unique ID which is used to store the state of this node
-    id: uniqueId,
-
-    // Provide Network relevant configuration like the port
-    // Optional when operating only one device on a host, Default port is 5540
-    network: {
-        port,
-    },
-
-    // Provide Commissioning relevant settings
-    // Optional for development/testing purposes
-    commissioning: {
-        passcode,
-        discriminator,
-    },
-
-    // Provide Node announcement settings
-    // Optional: If Ommitted some development defaults are used
-    productDescription: {
-        name: deviceName,
-        deviceType: AggregatorEndpoint.deviceType,
-    },
-
-    // Provide defaults for the BasicInformation cluster on the Root endpoint
-    // Optional: If Omitted some development defaults are used
-    basicInformation: {
-        vendorName,
-        vendorId: VendorId(vendorId),
-        nodeLabel: productName,
-        productName,
-        productLabel: productName,
-        productId,
-        serialNumber: `matterjs-${uniqueId}`,
-        uniqueId,
-    },
-});
-
-/**
- * Matter Nodes are a composition of endpoints. Create and add a single multiple endpoint to the node to make it a
- * composed device. This example uses the OnOffLightDevice or OnOffPlugInUnitDevice depending on the value of the type
- * parameter. It also assigns each Endpoint a unique ID to store the endpoint number for it in the storage to restore
- * the device on restart.
- *
- * In this case we directly use the default command implementation from matter.js. Check out the DeviceNodeFull example
- * to see how to customize the command handlers.
- */
-
-const aggregator = new Endpoint(AggregatorEndpoint, { id: "aggregator" });
-await server.add(aggregator);
-
-for (let idx = 0; idx < isSocket.length; idx++) {
-    const i = idx + 1;
-    const isASocket = isSocket[idx]; // Is the Device we add a Socket or a Light?
-
-    const name = `OnOff ${isASocket ? "Socket" : "Light"} ${i}`;
-
-    const endpoint = new Endpoint(
-        isASocket
-            ? // For a Bridged Device we need to add a BridgedDeviceBasicInformation cluster as server
-              OnOffPlugInUnitDevice.with(BridgedDeviceBasicInformationServer)
-            : OnOffLightDevice.with(BridgedDeviceBasicInformationServer),
-        {
-            id: `onoff-${i}`,
-            bridgedDeviceBasicInformation: {
-                nodeLabel: name, // Main end user name for the device
-                productName: name,
-                productLabel: name,
-                serialNumber: `node-matter-${uniqueId}-${i}`,
-                reachable: true,
-            },
-        },
-    );
-    await aggregator.add(endpoint);
-
-    /**
-     * Register state change handlers and events of the endpoint for identify and onoff states to react to the commands.
-     *
-     * If the code in these change handlers fail then the change is also rolled back and not executed and an error is
-     * reported back to the controller.
-     */
-    endpoint.events.identify.startIdentifying.on(() => {
-        console.log(`Run identify logic for ${name}, ideally blink a light every 0.5s ...`);
-    });
-
-    endpoint.events.identify.stopIdentifying.on(() => {
-        console.log(`Stop identify logic for ${name} ...`);
-    });
-
-    endpoint.events.onOff.onOff$Changed.on(value => {
-        executeCommand(value ? `on${i}` : `off${i}`);
-        console.log(`${name} is now ${value ? "ON" : "OFF"}`);
-    });
-}
-
-/**
- * In order to start the node and announce it into the network we use the run method which resolves when the node goes
- * offline again because we do not need anything more here. See the Full example for other starting options.
- * The QR Code is printed automatically.
- */
-await server.start();
-
-/**
- * Log the endpoint structure for debugging reasons and to allow to verify anything is correct
- */
-logEndpoint(EndpointServer.forEndpoint(server));
-
-/*
-  If you want to dynamically add another device during runtime you can do so by doing the following:
-
-    const name = `OnOff Light 3`;
-
-    const endpoint = new Endpoint(OnOffLightDevice.with(BridgedDeviceBasicInformationServer), {
-        id: `onoff-3`,
-        bridgedDeviceBasicInformation: {
-            nodeLabel: name,
-            productName: name,
-            productLabel: name,
-            serialNumber: `node-matter-${uniqueId}-3`,
-            reachable: true,
-        },
-    });
-    await aggregator.add(endpoint);
-
-    endpoint.events.onOff.onOff$Changed.on(value => {
-        executeCommand(value ? `on3` : `off3`);
-        console.log(`${name} is now ${value ? "ON" : "OFF"}`);
-    });
-
- */
-
-/*
-   To remove a device during runtime you can do so by doing the following:
-        console.log("Removing Light 3 now!!");
-
-        await endpoint.close();
-
-   This will automatically remove the endpoint from the bridge.
- */
-
-/*********************************************************************************************************
- * Convenience Methods
- *********************************************************************************************************/
-
-/** Defined a shell command from an environment variable and execute it and log the response. */
-function executeCommand(scriptParamName: string) {
-    const script = Environment.default.vars.string(scriptParamName);
-    if (script === undefined) return undefined;
-    console.log(`${scriptParamName}: ${execSync(script).toString().slice(0, -1)}`);
-}
-
-async function getConfiguration() {
-    /**
-     * Collect all needed data
-     *
-     * This block collects all needed data from cli, environment or storage. Replace this with where ever your data come from.
-     *
-     * Note: This example uses the matter.js process 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 storage contexts
-     * (so maybe better not do it ;-)).
-     */
-    const environment = Environment.default;
-
-    const storageService = environment.get(StorageService);
-    console.log(`Storage location: ${storageService.location} (Directory)`);
-    console.log(
-        'Use the parameter "--storage-path=NAME-OR-PATH" to specify a different storage location in this directory, use --storage-clear to start with an empty storage.',
-    );
-    const deviceStorage = (await storageService.open("device")).createContext("data");
-
-    const isSocket = Array<boolean>();
-    const numDevices = environment.vars.number("num") || 2;
-    if (await deviceStorage.has("isSocket")) {
-        console.log(`Device types found in storage. --type parameter is ignored.`);
-        (await deviceStorage.get<Array<boolean>>("isSocket")).forEach(type => isSocket.push(type));
-    }
-    for (let i = 1; i <= numDevices; i++) {
-        if (isSocket[i - 1] !== undefined) continue;
-        isSocket.push(environment.vars.string(`type${i}`) === "socket");
-    }
-
-    const deviceName = "Matter test device";
-    const vendorName = "matter-node.js";
-    const passcode = environment.vars.number("passcode") ?? (await deviceStorage.get("passcode", 20202021));
-    const discriminator = environment.vars.number("discriminator") ?? (await deviceStorage.get("discriminator", 3840));
-    // product name / id and vendor id should match what is in the device certificate
-    const vendorId = environment.vars.number("vendorid") ?? (await deviceStorage.get("vendorid", 0xfff1));
-    const productName = `node-matter OnOff ${isSocket ? "Socket" : "Light"}`;
-    const productId = environment.vars.number("productid") ?? (await deviceStorage.get("productid", 0x8000));
-
-    const port = environment.vars.number("port") ?? 5540;
-
-    const uniqueId =
-        environment.vars.string("uniqueid") ?? (await deviceStorage.get("uniqueid", Time.nowMs().toString()));
-
-    // Persist basic data to keep them also on restart
-    await deviceStorage.set({
-        passcode,
-        discriminator,
-        vendorid: vendorId,
-        productid: productId,
-        isSocket,
-        uniqueid: uniqueId,
-    });
-
-    return {
-        isSocket,
-        deviceName,
-        vendorName,
-        passcode,
-        discriminator,
-        vendorId,
-        productName,
-        productId,
-        port,
-        uniqueId,
-    };
-}

package/src/examples/ComposedDeviceNode.ts

@@ -1,197 +0,0 @@
-#!/usr/bin/env node
-/**
- * @license
- * Copyright 2022-2024 Matter.js Authors
- * SPDX-License-Identifier: Apache-2.0
- */
-
-/**
- * This example shows how to create a new device node that is composed of multiple devices.
- * It creates multiple endpoints on the server. For information on how to add a composed device to a bridge please
- * refer to the bridge example!
- * 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 "@project-chip/matter-node.js";
-
-import { requireMinNodeVersion } from "@project-chip/matter-node.js/util";
-import { DeviceTypeId, VendorId } from "@project-chip/matter.js/datatype";
-import { logEndpoint } from "@project-chip/matter.js/device";
-import { OnOffLightDevice } from "@project-chip/matter.js/devices/OnOffLightDevice";
-import { OnOffPlugInUnitDevice } from "@project-chip/matter.js/devices/OnOffPlugInUnitDevice";
-import { Endpoint, EndpointServer } from "@project-chip/matter.js/endpoint";
-import { Environment, StorageService } from "@project-chip/matter.js/environment";
-import { ServerNode } from "@project-chip/matter.js/node";
-import { Time } from "@project-chip/matter.js/time";
-import { execSync } from "child_process";
-
-requireMinNodeVersion(16);
-
-/** Initialize configuration values */
-const { isSocket, deviceName, vendorName, passcode, discriminator, vendorId, productName, productId, port, uniqueId } =
-    await getConfiguration();
-
-/**
- * Create a Matter ServerNode, which contains the Root Endpoint and all relevant data and configuration
- */
-const server = await ServerNode.create({
-    // Required: Give the Node a unique ID which is used to store the state of this node
-    id: uniqueId,
-
-    // Provide Network relevant configuration like the port
-    // Optional when operating only one device on a host, Default port is 5540
-    network: {
-        port,
-    },
-
-    // Provide Commissioning relevant settings
-    // Optional for development/testing purposes
-    commissioning: {
-        passcode,
-        discriminator,
-    },
-
-    // Provide Node announcement settings
-    // Optional: If Ommitted some development defaults are used
-    productDescription: {
-        name: deviceName,
-        deviceType: DeviceTypeId(isSocket[0] ? OnOffPlugInUnitDevice.deviceType : OnOffLightDevice.deviceType),
-    },
-
-    // Provide defaults for the BasicInformation cluster on the Root endpoint
-    // Optional: If Omitted some development defaults are used
-    basicInformation: {
-        vendorName,
-        vendorId: VendorId(vendorId),
-        nodeLabel: productName,
-        productName,
-        productLabel: productName,
-        productId,
-        serialNumber: `matterjs-${uniqueId}`,
-        uniqueId,
-    },
-});
-
-/**
- * Matter Nodes are a composition of endpoints. Create and add a single multiple endpoint to the node to make it a
- * composed device. This example uses the OnOffLightDevice or OnOffPlugInUnitDevice depending on the value of the type
- * parameter. It also assigns each Endpoint a unique ID to store the endpoint number for it in the storage to restore
- * the device on restart.
- *
- * In this case we directly use the default command implementation from matter.js. Check out the DeviceNodeFull example
- * to see how to customize the command handlers.
- */
-
-for (let idx = 0; idx < isSocket.length; idx++) {
-    const i = idx + 1;
-    const isASocket = isSocket[idx]; // Is the Device we add a Socket or a Light?
-    const endpoint = new Endpoint(isASocket ? OnOffPlugInUnitDevice : OnOffLightDevice, { id: `onoff-${i}` });
-    await server.add(endpoint);
-
-    /**
-     * Register state change handlers of the endpoint for identify and onoff states to react to the commands.
-     *
-     * If the code in these change handlers fail then the change is also rolled back and not executed and an error is
-     * reported back to the controller.
-     */
-    endpoint.events.identify.startIdentifying.on(() => {
-        console.log(`Run identify logic for sub device ${i}, ideally blink a light every 0.5s ...`);
-    });
-
-    endpoint.events.identify.stopIdentifying.on(() => {
-        console.log(`Stop identify logic for sub device ${i}...`);
-    });
-
-    endpoint.events.onOff.onOff$Changed.on(value => {
-        executeCommand(value ? `on${i}` : `off${i}`);
-        console.log(`OnOff ${i} is now ${value ? "ON" : "OFF"}`);
-    });
-}
-
-/**
- * Log the endpoint structure for debugging reasons and to allow to verify anything is correct
- */
-logEndpoint(EndpointServer.forEndpoint(server));
-
-/**
- * In order to start the node and announce it into the network we use the run method which resolves when the node goes
- * offline again because we do not need anything more here. See the Full example for other starting options.
- * The QR Code is printed automatically.
- */
-await server.run();
-
-/*********************************************************************************************************
- * Convenience Methods
- *********************************************************************************************************/
-
-/**
- * Defines a shell command from an environment variable and execute it and log the response
- */
-function executeCommand(scriptParamName: string) {
-    const script = Environment.default.vars.string(scriptParamName);
-    if (script === undefined) return undefined;
-    console.log(`${scriptParamName}: ${execSync(script).toString().slice(0, -1)}`);
-}
-
-async function getConfiguration() {
-    const environment = Environment.default;
-
-    const storageService = environment.get(StorageService);
-    console.log(`Storage location: ${storageService.location} (Directory)`);
-    console.log(
-        'Use the parameter "--storage-path=NAME-OR-PATH" to specify a different storage location in this directory, use --storage-clear to start with an empty storage.',
-    );
-    const deviceStorage = (await storageService.open("device")).createContext("data");
-
-    const isSocket = Array<boolean>();
-    const numDevices = environment.vars.number("num") || 2;
-    if (await deviceStorage.has("isSocket")) {
-        console.log(`Device types found in storage. --type parameter is ignored.`);
-        (await deviceStorage.get<Array<boolean>>("isSocket")).forEach(type => isSocket.push(type));
-    }
-    for (let i = 1; i < numDevices; i++) {
-        if (isSocket[i - 1] !== undefined) continue;
-        isSocket.push(environment.vars.string(`type${i}`) === "socket");
-    }
-
-    const deviceName = "Matter test device";
-    const vendorName = "matter-node.js";
-    const passcode = environment.vars.number("passcode") ?? (await deviceStorage.get("passcode", 20202021));
-    const discriminator = environment.vars.number("discriminator") ?? (await deviceStorage.get("discriminator", 3840));
-    // product name / id and vendor id should match what is in the device certificate
-    const vendorId = environment.vars.number("vendorid") ?? (await deviceStorage.get("vendorid", 0xfff1));
-    const productName = `node-matter OnOff ${isSocket ? "Socket" : "Light"}`;
-    const productId = environment.vars.number("productid") ?? (await deviceStorage.get("productid", 0x8000));
-
-    const port = environment.vars.number("port") ?? 5540;
-
-    const uniqueId =
-        environment.vars.string("uniqueid") ?? (await deviceStorage.get("uniqueid", Time.nowMs().toString()));
-
-    // Persist basic data to keep them also on restart
-    await deviceStorage.set({
-        passcode,
-        discriminator,
-        vendorid: vendorId,
-        productid: productId,
-        isSocket,
-        uniqueid: uniqueId,
-    });
-
-    return {
-        isSocket,
-        deviceName,
-        vendorName,
-        passcode,
-        discriminator,
-        vendorId,
-        productName,
-        productId,
-        port,
-        uniqueId,
-    };
-}