4.0.0 Branch Update

[pnpebeling]

Hi,

The recent 4.0.0 update appears to change version checking. I've incorporated the new code and I'm getting some version check errors on startup. (within Driver.cs) The SetApiVersionCB is failing with the "schema_incompatible" error. After some poking around I found the following change seems to fix things.

(Driver.cs, Line 26) private int _schemaVersion = 40; //pae 42;

thanx.

pae

p.s. any progress on V15 support?

[marcus-j-davies]

Hi @pnpebeling ,

Sorry, just be busy in other projects currently

v4 should now be compatible with v15 (in the last few miniutes)
But the jump from 14 to 15 has created some breaking changes.

• Building the PSI now requires > Node v20

And to build the latest PSI
Make sure to delete, and pull down latest v4 sources

cd PSI
npm install        /* Pulls in the correct Driver and Server versions */
npm run build      /* Builds the PSI to a native binary */

The schema error, is due to changes made in the server its self (that we have a dependancy on)
but the last changes should address it (it pulls in the required versions)

let me know how it goes

[marcus-j-davies]

EXTRA INFO

You can test if the PSI works after build
After building the PSI, run npm run test

BUT - update the COM port name in the script (for OSX its /dev/tty.XXXXX)

ZWaveJS.NET/PSI/package.json

Line 19 in cc2d5db

"test": "export WS_PORT=7070 SERIAL_PORT=/dev/tty.usbmodem214301 CONFIG=$(<./test_config.json) && ./build/dist/server",

This test uses a dummy config - just to make sure the driver starts up (so you may need to change the test storage location)

Test Config
https://github.com/zwave-js/ZWaveJS.NET/blob/4.0.0/PSI/test_config.json
you may beed to alter the test script, to add .exe to the end

[pnpebeling]

Hi,

Successful build and install !!! ... thanks

The only breaking change I have found so far is the DeviceConfig property of the Controller class. This property now returns null. Is this intentional or a bug? If intentional, was it dropped from the server side or on the .net side. If .net would you consider restoring it?

thanks again

-pae

[marcus-j-davies]

It still there.

I just need to patch the ESBuild output of the driver, as the config database uses relative paths, and so it doesn't take into account the Virtual File System in the PSI (so fails to load the device config database)

Its just some changes that occurred in v15 of the driver that were overlooked

Have tested a patch locally - will upload shortly

[marcus-j-davies]

UPDATE

Pull down the latest v4 branch, and try and build again - hopefully the config has now been restored

[pnpebeling]

Success, the missing DeviceConfig property has returned. thanx for the prompt response.