Razberry Board doesn't appears as node in HabMin

Setup, Configuration and Use Beginners
, ,
1

Hi all,

I installed OpenHab 1.7.1 and habmin 1.5.0 on raspberry P2 (udated/upgrade done). I see the razberry board as /dev/ttyAMA0. Starting Openhab shows the following zwave error message:

pi@raspberrypi:/opt/openhab $ sudo ./start.sh
Launching the openHAB runtime…
osgi> 2015-12-16 15:09:09.512 [INFO ] [.o.core.internal.CoreActivator] - openHAB runtime has been started (v1.7.1).
2015-12-16 15:09:14.139 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - mDNS service has been started
2015-12-16 15:09:14.325 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - Service Disco very initialization completed.
2015-12-16 15:09:23.529 [INFO ] [penhab.io.rest.RESTApplication] - Started REST API at /rest
2015-12-16 15:09:29.039 [INFO ] [.o.u.w.i.servlet.WebAppServlet] - Started Classic UI at /openhab.app
2015-12-16 15:09:35.130 [INFO ] [.o.io.habmin.HABminApplication] - Started HABmin REST API at /services/habmin
2015-12-16 15:09:40.545 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyAMA0
2015-12-16 15:09:40.548 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, healtime = 2
2015-12-16 15:09:40.552 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started
2015-12-16 15:09:40.638 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
2015-12-16 15:09:40.640 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2015-12-16 15:09:40.641 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyAMA0
RXTX Warning: Removing stale lock file. /var/lock/LCK…ttyAMA0
2015-12-16 15:09:40.754 [INFO ] [b.z.i.protocol.ZWaveController] - Serial port is initialized
2015-12-16 15:09:43.804 [WARN ] [eController$ZWaveReceiveThread] - Protocol error (OOF). Got 0x5A. Sending NAK.
2015-12-16 15:09:48.803 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempt s left!
2015-12-16 15:09:53.832 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempt s left!
2015-12-16 15:09:58.862 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempt s left!
2015-12-16 15:10:03.893 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = GetVersion (0x15), type = Request (0x00), payload =
2015-12-16 15:10:08.912 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-12-16 15:10:13.942 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2015-12-16 15:10:18.962 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2015-12-16 15:10:23.983 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = MemoryGetId (0x20), type = Request (0x00), payload =
2015-12-16 15:10:29.002 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-12-16 15:10:34.032 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2015-12-16 15:10:39.062 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2015-12-16 15:10:44.083 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = SerialApiGetCapabilities (0x07), type = Request (0x00), payload =
2015-12-16 15:10:49.112 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-12-16 15:10:54.142 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2015-12-16 15:10:59.172 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2015-12-16 15:11:04.204 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = SerialApiSetTimeouts (0x06), type = Request (0x00), payload = 96 0F
2015-12-16 15:11:09.232 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-12-16 15:11:14.262 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2015-12-16 15:11:19.292 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2015-12-16 15:11:24.323 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = GetSucNodeId (0x56), type = Request (0x00), payload =

osgi>

Strange thing, up to this time I didn’t have a zwave node included. Starting Habmin shows
the zwave Bindung but on the right side under devices no node appears. I assumed the razberry board should appear as node1?
Properties shows:port port /dev/ttyAMA0 Heal time 2

Any ideas what is wrong…

Many thanks in advance …

Kind regards

Peter

2

Hi Peter,
Did you find out a solution for this?
I stuck at the same point.

3

Hi,

no I changed it against an Aeon Gen5 Stick … now it works better but to bring zwave up and running is not an easy thing …

4

Hi guys,

I have the Razberry zwave board and am also stuck at the same point. I did have this board working with the zway software (just didn’t like all the remote access stuff baked into it) so I know it does work. Any suggestions?

5

You could try openHABian, as far as I remember it has build in support for the razberry (dealing with the serial and permission stuff …):

6

That is correct :slight_smile:

7

Managed to resolve this (I was already on openHABian), by adding dtoverlay=pi3-disable-bt to /boot/config.txt as the Bluetooth on my Pi3 was conflicting with the z-wave controller board.

Was only able to gather this by a random guess but might help someone having the same problem.