anyhow fellas… I am almost positive Chris uncovered a buggy and fixed missing parameters in Habmin & Paper UI if not mistaken, but I am talking days ago so probably no merged yet or only in bleeding edge snapshot.
He is also still struggling to get a development environment going I think
But after install, the menu for the device’s configuration parameters is still not displayed. Also I see the date for the binding shown as:
openhab> bundle:list | grep ZWave
270 x Active x 80 x 18.104.22.168901201452 x ZWave Binding
The Jan 20, 2019 date matches the release on Github for 2.5.0.M1. So am I correct in assuming that the link Chris supplies is for the official release that he uploads to his site only for major revisions?
Since @sihui and @Bruce_Osborne pointed out that the database file for the device in question was updated after this (2019.03.12), this means I need to be building the latest from source, or using the install script.
I’ll report back when I’ve tried one. I might install an IDE and attempt to build myself, since I have other bindings that also provide daily updates, and it would be nice to be able to build all of these at will.
The readme for the script has instructions for doing everything manually, including a URL for the latest snapshot of the binding. The link you used should be removed… it was used for testing. This is actually an option in the script too (the development option), since Chris sometimes provides builds for people to test.
good catch Bruce
and also glad to see the parameters buggy squashed @Diogenes please update the title of thread with [SOLVED] and put a check box in the post that helped you solve the problem (you did a lot yourself - good on you)
oh and @Diogenes additional question:
did you upgrade your OpenHAB version or just your zwave binding version?
yeah but issue was most probably because of transport serial package not installing which Diogenes was slick enough to pick up on his own
I am still on stable 2.4 but running a jar zwave, I way try the latest just to see if works
I would recommend at least pre-qualifying this statement with 'if this is not a production installation ’ or some such before authoritatively recommending an upgrade of the entire platform from a stable version. People may be relying on things not breaking and an unneccasary upgrade could cause untold troubles.