OpenZwave is a mess

This needs to be pulled until it has been fixed and tested, I have been working with Zwave for the last 5 years, and I can tell you this is not a good upgrade and can destroy your working zwave network. So make sure that you backup before even playing with this, it is not ready for it to be offered even as a beta, documentation is not clear, dependencies are not spelled out, and logging is not consistent or accurate.

Then, rather than posting a rant on the forum, why not provide some actual constructive feedback? That’s the whole point of a beta after all, to find the problems in the code, and the documentation.

Open issues, submit PRs for the docs, and generally help :wink:

The point of my reply is it is Alpha not a beta level, there is a big difference. I do not mind helping with beta level efforts, however having to go to through the code with out documentation and wasting time is another story.

I’ve personally been using it myself for a month or two without issue. I have around 10 nodes. I knew my lock would not work based on the documentation and made a work around.

Of course you should always back up and expect issues with any software upgrade. Let alone beta software.

1 Like

Errm: It’s not an upgrade, it’s a different architecture.

I’ve been running with it for a few days with no issues. It doesn’t support all my devices, but I was happy with that when I chose to install it as I want to help. The devices it does support are working without any apparent problems.
I suggest you revert to the released Wave interface: your network should be OK as the mesh is stored in the stick.

2 Likes