Did you install openHAB using apt-get? If so it is running as the openhab user and the openhab user is not a member of the dialout group and therefore does not have permission to read/write /dev/ttyAMA0. The simplest fix is to add the openhab user to the dailout group.
First: the logfile from openhab ist the openhab.log.
The razberry board is not recognize as a serial device by OH. So you have to add the
-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0
in the java start parameter line (start.sh or start.bat or service openhab). Just after -Dosgi.noShutdown=true otherwize it will not work either. If you have other serial devices to use with OH you can add them with a “:”
Those errors look like something else is running which has locked that port. I would recommend rebooting and trying again. If it still has the error I would make sure you don’t have any other software running which might be using that socket. It is possible that the z-wave-server software either keeps something running in the background or it does not clean up after itself very well when you shut it down.
My z-way server doesn’t run unless I manually start it, this is because openhab cannot control the z-way devices if the z-way server is running.
In order to start and stop the z-way-server I runt these:
sudo /etc/init.d/z-way-server stop
sudo /etc/init.d/z-way-server start
I did the
update-rc.d z-way-server disable
and got this result:
pi@raspberrypi ~ $ sudo update-rc.d z-way-server disable
update-rc.d: using dependency based boot sequencing
insserv: warning: current start runlevel(s) (empty) of script z-way-server' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptz-way-server’ overrides LSB defaults (0 1 6).
Like I said before, the z-wave device works along with my mosquitto server so everything is working, its just the runtime shows those errors, which maybe are just fine?