I’m having great difficulty trying to get my Razberry to work with the Z-Wave Binding. I have searched and searched the forum and pieced together information from about 5 topics but cannot get it to work. I suspect this is due to me trying a more recent Pi with more recent software.
In an effort to fix this issue for myself and to help others I’ve created a detailed list of what I have done in the hope that we have some up-to-date instructions.
Before disabling BT as above I also tried adding the following dtoverlay=pi3-miniuart-bt to the file but it caused the field in the z-wave binding options to become a drop-down where I could not enter my serial port plus it did not work.(see below this is all I could set it to)
Sorry I was too focused on explaining what I did rather than saying what was wrong and me saying it is not working is obviously not good enough.
I have had many errors but following my method above exactly it states that it is offline because the port does not exist.
17:59:30.638 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_b9d74e20_serial_oof-zwave:serial_zstick:b9d74e20:serial_oof' has been added.
17:59:30.791 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:b9d74e20' changed from UNINITIALIZED to INITIALIZING
17:59:30.831 [INFO ] [ding.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyAMA0'
17:59:30.833 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:serial_zstick:b9d74e20' has been updated.
17:59:30.843 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:b9d74e20' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
17:59:30.850 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:b9d74e20' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE (COMMUNICATION_ERROR): Serial Error: Port /dev/ttyAMA0 does not exist
I don’t know how to verify the port which is why I assumed it was the same as the one on my other Pi with Razberry and z-way installed. I have also tried ttyS0
This was to show that when I added dtoverlay=pi3-miniuart-bt to /boot/config.txt that in the Paper UI the input field could not be edited and was automatically populated with dev/ttyS0
So this error can indicate either that the device doesn’t exist (e.g. isn’t successfully plugged in), is at a different location (e.g. /dev/ttyS0 rather than /dev/ttyAMA0), or the openhab user does not have permission to read and write to the device.
ls -l /dev/tty*
That will list all the serial devices and their permissions. You should see a /dev/ttyAMA0. If you do not you know that your device is showing up as something else (/dev/ttyUSB0 is common). If you see more than one, it is possible that the controller is located at the other one (e.g. /dev/ttyAMA1).
I don’t know how easy this is to do with the Razberry, but with a USB controller one can see what device the controller is showing up as by stopping OH, unplugging the controller, running the ls command from above, plugging the controller back in, running the ls command again and look for the new item in the listing. That new item will be your controller.
Sorry I was too focused on explaining what I did rather than saying what was wrong and me saying it is not working is obviously not good enough.