Configuration manager access

[pnpebeling]

Hello,

I am converting the ZWave portion my home automation .NET project from openZWave to ZWaveJS via ZWaveJS.NET. I am using the current version of ZWaveJS.NET in "Self Hosted" mode. The conversion has gone quite smoothly. I have a need to access the manufacturer information and since there are no public methods within ZWaveJS.NET to access the ZWaveJS configuration manager I am attempting to add some.

I have include the JWaveJS.NET source code as a project within my solution and am in the process of adding extension methods to provide configuration manager access. My extension methods follow the established pattern for sending requests to the server code. I have successfully added an extension method to retrieve a node's neighbor nodes.

My attempts to access the server configuration manager have not been successful. My extension method and the server response are shown below. From reviewing the server documentation I believe I have formatted the command correctly, however I get Unknown Command responses.

Any insight into this issue is appreciated.

paul ebeling

public static Task<CMDResult> CfgMgrTest(this Controller controller, ZWaveNode Node) {
  Guid ID = Guid.NewGuid();

  TaskCompletionSource<CMDResult> Result = new TaskCompletionSource<CMDResult>();
  Driver.Callbacks.Add(ID, (JO) => {
    CMDResult Res = new CMDResult(JO);
    if (Res.Success) {
      Res.SetPayload(JO.Value<JObject>("result"));
    }
    Result.SetResult(Res);
  });

  Dictionary<string, object> Request = new Dictionary<string, object>();
  Request.Add("messageId", ID);
  Request.Add("command", "config_manager.lookup_manufacturer");

  Request.Add("manufacturer_id", Node.manufacturerId);

  string RequestPL = Newtonsoft.Json.JsonConvert.SerializeObject(Request);
  Driver.Client.SendAsync(RequestPL);

  return Result.Task;
}

{
"type": "result",
"success": false,
"messageId": "5edbfc06-73ae-464c-b9f6-bfe6ebac08b5",
"errorCode": "unknown_command",
"args": {
"command": "config_manager.lookup_manufacturer"
}
}

[marcus-j-davies]

Hi @pnpebeling

You likely havant compiled the middleware image (PSI file) to the latest version - therefore, it's not pulling down the server version that included this functionality (config manager)

See https://github.com/zwave-js/ZWaveJS.NET/tree/main/PSI for the PSI source

The 'current' version of the PSI is based on schema 17 - quite old now, its currently on schema version 40
The V4 branch https://github.com/zwave-js/ZWaveJS.NET/tree/4.0.0 is based on 35

(I think config_manager was added in schema v38)

The are a 2 parts to this project...

• The .Net DLL
• The PSI file

The PSI file contains an embedded version of the Zwave JS Driver, and the web socket server - its the web socket server, that will handle this functionality - and I doubt schema version 17 - contained this functionality.

The PSI file is compiled to an exe - and hosts an embedded runtime of the Driver and Server - the DLL fires it up, and connects to it via web socket

See : https://github.com/zwave-js/zwave-js-server

Try using the V4 branch (be aware of a lot of breaking changes) + the need to now compile your own PSI
form here - bump the dependency on the PSI project to the latest server version (35-> 40), and you should be able to move forward.

[marcus-j-davies]

1. Pull down V4
2. Edit the dependencies on the PSI project to pull down the latest Driver and Server
3. Build it
   - cd to ./PSI
   - run npm install && npm run build
   - rename ./dist/server.exe to ./dist/server.psi, and distribute the image with the library.
4. Patch your application. (to handle the breaking change in V4)

You could just try bumping the server and driver on the current version you have downloaded (and build as normal)

[marcus-j-davies]

UPDATE

---

V4 now has the Config Manager

Driver.ConfigManager.LookupDevice(int ManufacturerID, int ProductTypeID, int ProductId)
Driver.ConfigManager.LookupManufacturer(int ManufacturerID)

Again - you need to compile your own PSI, to take advantage

[pnpebeling]

Thanks for the prompt reply. I've downloaded V4 and compiled the PSI. I'm working through the breaking changes now ... though they are not as bad as I feared. thx again.