OpenHab don't recognize Razberry Board /don't see node in HabMin

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

With z-sticks anyway, you need to add openhab user to dialout group. Not sure abt the Razberry tho

Hi Bob,

I’m a beginner how do I do this? Dialout group?

Sorry for that, newbee

many thx and happy christmas

Peter

It’s -almost- all in the wiki.
See 11.

sudo usermod -a -G dialout openhab

@peterd @sihui is correct.

Hi,

many thx … happy christmas

Peter

Many thx too …

Hi,

unfortunally Bob and your hints doesn’t help. I tried the following

-> useradd -G dialout openhab

-> sudo usermod -a -G dialout openhab

pi@raspberrypi:/opt/openhab $ ps -elf | grep openhab
0 S pi 1345 910 0 80 0 - 1070 pipe_w 14:40 pts/0 00:00:00 grep --color=auto openhab

seems there user is is pi?

Any ideas?

Thx

Peter

Hi Bob

Hi,

unfortunally your hint doesn’t help. I tried the following

-> useradd -G dialout openhab

-> sudo usermod -a -G dialout openhab

pi@raspberrypi:/opt/openhab $ ps -elf | grep openhab
0 S pi 1345 910 0 80 0 - 1070 pipe_w 14:40 pts/0 00:00:00 grep --color=auto openhab

seems there user is is pi?

Any ideas?

Thx

Peter

It is much better, IMHO, to install openHAB using the official instructions using apt-get. This process creates an openhab user that runs the server. Various issues and difficulty helping correct those issues are avoided when installing that way. If you got your instructions from an unofficial how-to, it would be great if you reported back to the author to correct his or her instructions to refer to the official installation instructions.

type
top, then
type
u, then
type in the different usernames you like to check (pi, root, openhab). In my case I type openhab and get the following output, so the user who runs openhab and java is openhab.

But because I don’t use the razberry board I am not of further help to you, sorry.

Edit: and yes, @watou is definitely right, use apt-get, OH runs much more stable then.

Hi

thx I there is no openhab user … I will try the official installation. I found one for a raspi, the guy tried to help … but I could bring it to work …

Thanks again for your support

Peter

Hi,

I will try the official one but I’m not very hopefully, just found a hint that the razberry board causes problem, which are not solved til today

Peter

@watou is correct abt the apt-get method. I switched from “hand-rolled” to apt-get in November and the process is much smoother.

I found one MAJOR MAJOR caveat – the apt-get install in Step 7 says that on Debian 8 (Jessie) you should use the “sudo systemctl start openhab” command rather than the prior “sudo /etc/init.d/openhab start” command.

On a clean Jessie install using apt-get, if you do this (at least the FIRST TIME you run OH and possibly every time) you leave the system with knots of permission conflicts which are very difficult to unsnarl (i.e. it is easier to start from clean SD than figure it out. ) The “old way” using /etc/init.d/openhab start WORKS and calls the proper setup scripts.

Should an issue be opened about this, @bob_dickenson?

I actually think so. Have not had time to open myself since I did the switch to Jessie two weeks ago. (real life interposing itself, etc) What is the best mechanism ? I see two issues: the underlying fault and the wiki doc. Will follow your direction on either/both ASAP

Hi Bob, could you open an issue against the installation scripts, describing in detail the permissions problem you observe, and mention @theoweiss (on GitHub) to see if he would investigate. Any wiki doc changes would then be made to match any code changes. Thanks very much – hopefully any issues can be resolved before 1.8!

Just to mention: I did a Jessie clean install twice and never came across that problem.
Although not all files and folders belonged to user:group openhab:openhab, I had to manually chown from root:root to openhab:openhab.
BUT what I have read somewhere: if you perform an update from wheezy to jessie there are some problems with permissions, but that should have nothing to do with openhab.
This is just my observation …

1 Like

Interesting. I did multiple Jessie clean installs before I finally narrowed down the causal chain to the systemctl invocation instruction. Everyone of them failed on the permission snarl problem — OTO ten or so consecutive clean Jessie installs. I did the following: created clean Raspian Jessie SD. Cloned same to a USB stick. Changed cmdline.txt on /boot to point to / on the stick. Installed as per the apt-get instructions. Failed every time on permission issues IFF my first invocation of OH was thru systemctl rather than /etc/init.d/…

What were the permission issues?