I tried two test cases using clean SD card images on the Pi…
A) I completely uninstalled all the Z-Way server software, and the Z-Way openHAB binding; and just used the ZWave binding; in that test case the RaZberry board is reported in openHAB as Offline.
B) I uninstalled the ZWave binding; installed the Z-Way server, and Z-Way openHAB binding; in that test case it works.
Had the same workaround these days. Installed the zway software for making a firmware update of the razberry and geting rid of the dead nodes. You must remove the zway server in the autostart with : sudo update-rc.d z-way-server remove sudo shutdown -r now
In addition to that I had to set again the ports in openhabian- config and the port of the thing zwave controller in paper-ui. Then the controller changed to online again.
So you mean that the ZWay software must be actually present even if it is not running? Why is that?
No, there is actually no reason for having both installed on the raspberry. Both programms use same ports, so there are problems if you have the zway server running and the zwave binding.
Ok. So we are back to my original problem: with ZWay software and no ZWave it works but with ZWave and no ZWay it does not work.
Please use the search function, there are a lot of threads dealing with Razberry problems.
If you can’t find a solution open a new thread as this one has probably nothing to do with your specific problem.
I dont really see your problem. Remove all of the zway stuff and install the zwave binding. If the controller doesnt go online, just do a complete fresh openhabian install. The Razberry will work, because hundreds of people are using this zwave controller.
CFor goodness sakes guys, please look at what I have been saying…
So could you please kindly stop trying to blame another piece of software, or another piece of hardware, or trying to push me off to another thread. The title of this thread describes exactly my problem, and it relates exactly to this ZWave driver.
The ZWave binding uses the standard serial drivers from ESH - it has not direct control over the serial ports etc, and there’s nothing that can be done in the ZWave binding. I think it’s reasonably unlikely to be a problem with the binding, but if it is, you need to provide supporting information.
If you are really sure that the problem is in the ZWave binding as you indicate, then it would be appreciated if you can try to debug it further as I personally don’t think it’s the case, and as the binding maintainer, there’s not much that can be done without more specific information on your problem. For example, I don’t see any debug logs here - that is always a good starting point when there is a problem (I apologise if they are provided as this is quite a long thread and I might have missed them?).
Many thanks Chris. I will post some logs next week (May 1st probably)…
I tried to install the latest snapshot from today in order to anyhow contribute, but I still have lots of troubles with assigning a port permanently to the Wave USB stick. After every restart I have to assign it manually and in several times the bridge keeps staying offline. In order to at least have a stable installation I wanted to get back to #1360 which worked good for me unfortunately it is not yet part of my cache anymore. Is there anyhow an option to re-download an older snapshot to the cache?
Hi,
i experience the same problem since a few builds of the snapshot version. I came from 2.4 which doesn’t had that type of problems. I use a Razberry and no usb stick.
I tried to track down the issue a litte bit but had no real success so far.
If I need to guess is would say something is broken on the esh serial implementation or it has some type of race condition and needs more time on startup… but I cannot see anything at the code at least…
My solution is: Assigning the serial port another time after each reboot. For whatever reason I have two options with the same name. If I switch to the other available option / port, the USB stick initialises and switches to green. Unfortunately this doesn’t make it very reliable as the restart should be possible without a manual interaction. My feeling it is that is working better with today’s snapshot #1580 compared to the 70s. But this is only a guess.
Known issue:
Hi Chris, you were right, the issue was related to the serial port settings. The Razberry Pi config screen settings in the screenshot below fixed the issue. Many apologies for wasting your time.
@AndrewFG I followed your suggestions and did a restart. Unfortunately my duplicate port /dev/ttyACM0 still exists. Additionally there is now a /dev/ttyS0 added to the picklist. Furthermore I still have to manually choose the port after the restart in order to activate the z-wave controller / bridge.
Edit: Did some further tests. The options 1 and 3 in openhabian config have no impact for whatever reason. Is there a need to power off the device in order to take effect?
Hey,
I had the same Problem on a Synology Diskstation,
I added the follow line in setenv file
EXTRA_JAVA_OPTS="-Xms250m -Xmx350m -Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0"
this is from Openhabian Setup and its working for me too.
The setenv file is placed on synology at @appstore/openHAB/runtime/bin
I have been struggling with my new raspbian installation using the Aeotec z-wave stick also. It seems there is an “interesting” hardware glitch that’s causing the /dev/ttyACM0 device (apparently that’s what the z-wave stick uses) to not be created. See this post on github:
The bottom line is that the the raspberry pi’s USB ports and the Aeotec z-wave stick aren’t playing nice. Solution is to use an unpowered USB hub! Huh, go figure 
Welcome to openHAB.
Yes, this is a known problem and already was mentioned in this forum:
Have fun with openHAB.
This solved the problem for me. Also got the “3 serial ports showing up in Paper UI” issue after this. Chose the middle one. Immediately came online.
For the curious, the steps are: