There was a zwave Scan issue with the latest binding (a file was renamed) with a work around noted here. However, this does not seem to be your problem and switching to the 3.3 release should have fixed it
There was a zwave Scan issue with the latest binding (a file was renamed) with a work around noted here. However, this does not seem to be your problem and switching to the 3.3 release should have fixed it