V8 BETA

[marcus-j-davies]

@fabnavigator

V8 BETA 1 is out!

Note!
This is using V10 of ZWave-JS (which is also in BETA), when V10 of ZWave-JS steps out of BETA into stable (for me it already is)
I will of course follow suite shortly after - providing no major issues with my V8 BETAs.

Pre warning: BACK UP YOUR SYSTEM!

Guide - adjust where necessary

cd ~/.node-red
npm install node-red-contrib-zwave-js@beta --force
sudo systemctl restart node-red 

@lurendrejer
I am going to tag you in this also - not sure you do a lot of testing, but just in case 😅

Both,
Please see the change log before installing the beta.
https://github.com/zwave-js/node-red-contrib-zwave-js/blob/8.0.0/CHANGELOG.md

[lurendrejer]

Will be checking this out when I get home in a few days time

[marcus-j-davies]

V8 is when I switched to V10 of the driver (7.2.1, moved to V8 once I learnt of the breaking changes in v10 - and wasn't worth realising 7.2.1 because of it)

[fabnavigator]

@marcus-j-davies,

What about the alcalzone-shared directory?

[marcus-j-davies]

Yup - that can go also 👍

[marcus-j-davies]

as long as you retain zwave-js-cache you have nothing to worry about.

[marcus-j-davies]

zwave-js-cache = All your Zwave Network data

[marcus-j-davies]

@fabnavigator
BETA 2 is up! (uses BETA 7 of V10 of the driver) - that should address the initial issues

npm install node-red-contrib-zwave-js@beta --force

[fabnavigator]

@marcus-j-davies, Looks good so far.

[lurendrejer]

Finally got around to installing the beta.
Everything has seemed stable for the last 24 hours and associations-UI is working again.

Thank you very much!

[marcus-j-davies]

Excellent @lurendrejer

I will be aiming for a stable release soon.

Still one more thing todo, then will push v8 as stable 👍

[marcus-j-davies]

@fabnavigator @lurendrejer

BETA 5 is now available.
I am hoping this is it before taking it to a stable release.

within your .node-red directory
npm install node-red-contrib-zwave-js@beta --force
Restart Node RED

if you haven't already, please see change log.
https://github.com/zwave-js/node-red-contrib-zwave-js/blob/8.0.0/CHANGELOG.md

Would be much appreciated for you to ensure the final BETA is trouble free.

[fabnavigator]

No. I don't run the health check on battery powered devices.

It always fails on an S2 node, but different ones. No issues on the unsecured nodes. Node 105 below was the node that failed this last time.

[marcus-j-davies]

So,
any S2 node (and always)?

[fabnavigator]

No. The first two S2 nodes haven't had an issue. The third has failed multiple times, but this last time the fourth S2 node failed.

[fabnavigator]

Everything was running w/o errors, three rounds, no delay between nodes for almost a month, until 9/19. Tnen node 105 failed, and failed again on 9/21. 9/20 and 9/22 everything passed. On 9/23 node 42 (first S2) failed.

[marcus-j-davies]

Ok,

Can I ask you raise a bug report on the driver repo - remember to include a log file of the error happening so we can see events leading up to it 😅

I have an S2 FLiRS device - that never works with health checks (it did previously), so can add some further logs to it if needed.
It's probably some recent changes to the driver 🤷

[marcus-j-davies]

V8 released.

Should appear in Node RED shortly!

[marcus-j-davies]

I'm gonna look this thread - given we are now out of BETA 😄