Expanded Firmware Support in zwave-js-server

[pnpebeling]

Before the project moves away from V4, how difficult would it be to include a zwave-js-server with expanded firmware support? There are numerous firmware APIs that are not exposed by js-server and thus unavailable in ZWaveJS.NET. I'm not necessarily asking for a roll of ZWaveJS.NET, just a version which includes a JS-server in which the firmware APIs are available. I have made one or two custom additions to ZWaveJS.NET, so I'm relatively confident I can add the additional firmware support in ZWaveJS.NET, but without server support I'm stuck. thanks

-p

[marcus-j-davies]

Hi @pnpebeling

The server its self - is not my project, it's a project indeed of the org, but not in my tent so to speak of the camp.

@AlCalzone, @raman325 ?

@pnpebeling
Evan if it doesn't make it into V4 (V5 is under way) - unlikely sorry (unless its a simple implementation)
you can use the MethodFactory class to add support - I added MethodFactory so consumers can add new methods, that it does not ship with.

MethodFactory example:

var NewMethod = ZWaveJS.NET.MethodFactory.CreatePRIMITIVE(DriverInstance,"controller.some_not_baked_in_method","result.some_path");

Dictionary<string,object> Args = new Dictionary<string, object>();
Args.Add("nodeId",5);
Args.Add("data", new byte[2]{0x01,0x02});

NewMethod(Args).ContinueWith(....) // primitive

Excluding messageId & command (these are handled internally) your Args object is simply the properties that the command needs to execute.

• CreateVOID
• CreatePRIMITIVE
• CreateCLASS (asks for the Type to cast to, once the result has been returned)

The resulting value from the path, is what is evaluated

Hope this helps

[raman325]

There are numerous firmware APIs that are not exposed by js-server

Can you share which APIs are missing? I found one controller.getAllAvailableFirmwareUpdates, are there others?

[pnpebeling]

The Z-Wave JS API documentation, "updateFirmware" section alludes to some support functions in the Utils section which seem to deal with manual processing of firmware files outside of the Firmware Update Service. Here are three APIs mentioned in the documentation but not exposed by the server.

extractFirmwareAsync
guessFirmwareFileFormat
tryUnzipFirmwareFile

I've developed my own home control system around the .NET project. I'm down this "rabbit hole" because I have a device with firmware not published in the Update Service. I'm reasonably confident that I can develop the necessary .NET extensions to communicate with the server, so I don't require any ZWaveJS.NET code updates to support these APIs. From my limited knowledge of the Z-Wave JS environment, what I do need are JS Server updates to expose the APIs and some direction in updating the server (new .psi) within the existing ZWaveJS.NET release.

Can I live without this feature? .. sure .. but my OCD nags at me ... Any help in this area would be appreciated, thanx

-p