PSI Updates

[pnpebeling]

Hi,
I know we're getting into a busy time of the year, ... but ... is there anyway to get a PSI refresh to the latest server and zwave-js versions?
thx
-paul

[marcus-j-davies]

Hi Paul,
I’ll aim to get an update done as soon as possible (ad-hoc if necessary).
I’m currently fighting off a seasonal illness.

Marcus

[marcus-j-davies]

Hi Paul,

I'll book out some time over the Weekend to update the library,
will ping you once done.

Marcus

[marcus-j-davies]

@pnpebeling

What target are you using for your App?
I am removing some older frameworks, in order to make it easier to keep maintained.

The frameworks I am going to keep are:

• net6.0
• net7.0
• net8.0
• net9.0
• netstandard2.1

I currently maintain an embedded WebSocket Library, but its getting in the way.

The reason its embedded, as it dropped support for older frameworks, which I am now looking todo also, so can switch to the actively maintained Library.

[pnpebeling]

Well here is my current environment.

• Visual Studio 2022
• Target Framework: .NET Framework 4.8
• Microsoft .NET SDK 9.0.308 installed

Until now I've never had the need to upgrade past 4.8. The problem is that nothing past 4.8.1 is available in my project build options. I'm looking into the issue but haven't found a clear-cut answer. I'm willing to update in the future, but right now I'd rather not add one more complication to this project. Would it be possible for you to create one more project update at the current level, then drop support in a subsequent release?

-p

[pnpebeling]

The versioning issue might be a moot point since I compile the ZWAVEJS.NET source as a library within my project ...

[marcus-j-davies]

Hi @pnpebeling,

V4 will be getting 1 last bump to the current schema (working on it right now), then after that, I will be looking to bump to v5 shortly after - where it will drop support for net48, netstandard2.0 - and target only those above (and will keep in line with modern framework versions thereafter)

It is in use by The HomeSeer project - and they have been warned, and will be keeping a private version of V4, as their product cant go past Net48 due to their customer base - so they will maintain their own fork past V4.

Moving forward (after the last update)

If you cant move past NET48 - keep a fork of V4, and update it, accordingly, when new versions of the driver / server are released - but it will be your own code base - more then happy to guide you when you need to update functions or other things.

if you want to stay inline with the official project, and use it's code base as is, it will only support NET6+

v5 will lose the internal web socket source - and use the official library it is based of (which does not support <NET6)

tl;dr
The next update I make to V4 will contain the latest driver + a few updates - but after that (v5) will drop support for anything below < NET6, so you will see v4 get the latest Driver version.

The reason you will have to maintain your fork of V4 (if cant move past NET48) - is due to the web socket lib, and the fact the current lib does not support < .NET6

v4 - holds onto source code for the web socket (which at the time of embedding, did support < NET48)
v5 - will switch to the official lib which only supportsNET6+

Hope that makes sense

[pnpebeling]

Thanks. Makes perfect sense.

-p

[marcus-j-davies]

I will tag you once V4 has been updated - trying to get it done before Monday

[marcus-j-davies]

@pnpebeling

I have added a new method to the CMDResult class, to address something I find a little annoying..

public T ResultPayloadAs<T>()
{
     return ResultPayload is T value ? value : default!;
}

Example use

Driver.Controller.Nodes.get(4).GetDefinedValueIDs().ContinueWith((R) =>{

    ValueID[] VIDs = R.Result.ResultPayloadAs<ValueID[]>()
    
    foreach(ValueID VID in VIDs){
         // Do something with VID (Value ID)
    }
})

This removes the need to do manual casting, which annoys me 😄

This will be available in v4 (I still need to push it over to V4 yet) - but hoping to in the next few days

[pnpebeling]

Just checking in ... how's the final V4 release going.

-p

[marcus-j-davies]

Hi @pnpebeling

Sorry, I have been in ill health - hence the disappearance, but better now, then work got really in the way.
I will aim to transpose the changes I made in v5, into V4 (minus the .NET framework drop) this weekend

Message me Friday & Sat morning - to remind me, I really want to get it done, so I'm good for it 😄

[marcus-j-davies]

@pnpebeling

Do you want to now pull the latest V4 sources from the V4 branch?

• Driver version : 15.20.0
• PSI Server Version : 3.5.0 (schema 44)
• Added method (CMDResult) public T ResultPayloadAs<T>() - Removes the need to cast the result yourself
• Added method (Controller) SetMaxLongRangePowerlevel
• Added method (Controller) GetMaxLongRangePowerlevel
• Added method (Controller)ToggleRF
• Added event (ZWaveNode) NodeInfoEvent
• Some small result path corrections

Let me know if any issue.
This commit will likely be the last before I drop support for older versions of the .NET SDK, and the embedded source of the WS lib.

To build the PSI

• Download a clean copy of the branch
• With in the PSI folder, issue the following
  • npm install
  • npm run build
  • Rename sever.exe to server.psi

[marcus-j-davies]

V4 has now been published to NuGet - But I think you compile the source anyway, so more an FYI.

The next major PR will render the Main Branch with the dropped frameworks - so maybe grab a copy off it now. it will be a lil while before the V5 branch gets merged

[pnpebeling]

Installed and testing. No issues.

thanks

-p