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

Tags: #<Tag:0x00007f17513be9c0> #<Tag:0x00007f17513be6a0>

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?

AFAIR they were access permissions on various directory paths. I did the chown dance when I encountered but after the 2nd or 3rd set of that in an install, I punted for clean reinstall. I never did find the right incantation for the directories and permissions which would work. Arrived at my conclusion by multiple clean reinstalls and verifying that OH started after each step. ( Initially I was going through the whole base install and addon installations en masse — so it is also possible that doing the addon installs before ever running OH is a possible causal path. ) It was during this process that I discovered that using the old invocation method /etc/init.d … started OH and did not clobber the permissions…even though it runs systemctl behind the scenes. So there’s something about my installation setup and the instructions to use systemctl which was consistently fatal.

[quote=“bob_dickenson, post:19, topic:5311, full:true”]
Cloned same to a USB stick.[/quote]

I’m far away from being a Linux expert, but how was your stick formatted?
If it was fat32, all the permissions from the systems partition /dev/mmcblk0p2 wouldn’t be copied because mmcblk0p2 has ext4 format and fat32 doesn’t know anything about linux permissions …

But anyway, the only difference in our installation method is that I didn’t clone anything to a usb stick, I left everything on my sd (and use some tmpfs to minimize the write cycles to the sd card to prevent fast wear out).

If I find some spare time the next days I will install openhab on jessie again on a brandnew sd card and tell you if there were any problems.

I used a low-level utility which image copied the SD to the USB. Bit-for-bit copy, not file-by-file so no pre-formatting required. Leaves you with ext4 fs on the USB.

Hi Bob

I followed your advice and just installed Openhab according official method (apt-get) seems to work. Openhab user is in the list now. But how to install habmin?
Using official install, OH uses different folders? For example I couldn’t find openhab-default.cfg? Where could I find openhab.cfg I only found a openhab file (no ext. cfg)?
One the habmin github (if using zwave), it said, I should install habmin 2 but 2 needs habmin1? Is it the same simple copy the whole file in the openhab folder and unzip? For me its a little bit confusing … Is there an apt-get install for habmin install available …

kind regards

Peter

There is no apt-get install for habmin, but the same procs work as in a hand-rolled install, it is just that the webapps folder where you will create the habmin directory is in a different place. Look in /usr/share/openhab/webapps

Hi,

do I get you right ?.. I had to copy the habmin.zip (from https://github.com/cdjackson/HABmin) file in the /usr/share/openhab raspi folder an then unzip it.

many thanks in advance

Peter

into /usr/share/openhab/webapps/habmin Different root directory than a hand-rolled install but same “copy habmin here then move jars to general addons directory” sequence

Hi,

Openhab installed with apt-get, raspi specific commands executed, openhab-default.cfg copied on openhab.cfg
I start openhab with:

sudo systemctl start openhab:

the result:

pi@raspberrypi:/etc/openhab/configurations $ sudo systemctl start openhab
pi@raspberrypi:/etc/openhab/configurations $

seems that openhab.cfg is ignored? I’m right?

HABmin installl manually, works, but I don’t see the razberry board as node?

Any ideas?

Thx Peter

what OS version are you ?

sudo /etc/init.d/openhab start
works across all Raspbian versions. If you are Raspbian Jessie (latest) I have PERSONALLY encountered issues with the “approved” use of systemctl (as opposed to /etc/init.d/openhab).

I use Jessie latest version if using sudo /etc/init.d/openhab start then I get hint to use sudo systemctl start openhab? What do you mean with ‘approved’?
Thx

Peter

Hi,

seems now oOH startet but I see a strange Zwave message could be the reason why I couldn’t see the razberry board … see below

any ideas?

Peter
pi@raspberrypi:~ $ sudo /etc/init.d/openhab status
● openhab.service - Starts and stops the openHAB Home Automation Bus
Loaded: loaded (/usr/lib/systemd/system/openhab.service; disabled)
Active: active (running) since Sa 2016-01-02 14:12:54 CET; 1min 19s ago
Docs: http://www.openhab.org
Process: 4478 ExecStartPre=/usr/share/openhab/bin/setpermissions.sh (code=exited, status=0/SUCCESS)
Main PID: 4633 (openhab.sh)
CGroup: /system.slice/openhab.service
├─4633 /bin/sh /usr/share/openhab/bin/openhab.sh -o
└─4654 /usr/bin/java -Dlogback.configurationFile=/etc/openhab/logback.xml -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true …

Jan 02 14:12:53 raspberrypi setpermissions.sh[4478]: setting permissions and owner openhab:openhab recursively for /var/lib/openhab
Jan 02 14:12:53 raspberrypi setpermissions.sh[4478]: setting permissions and owner openhab:openhab recursively for /var/log/openhab
Jan 02 14:12:53 raspberrypi setpermissions.sh[4478]: setting permissions and owner openhab:openhab for /usr/share/openhab/webapps/static
Jan 02 14:12:53 raspberrypi setpermissions.sh[4478]: setting permissions and owner openhab:openhab for /etc/openhab/jetty/etc/keystore
Jan 02 14:12:53 raspberrypi setpermissions.sh[4478]: setting permissions and owner openhab:openhab for /etc/openhab/configurations/users.cfg
Jan 02 14:12:54 raspberrypi systemd[1]: Started Starts and stops the openHAB Home Automation Bus.
Jan 02 14:13:10 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:10.725 [INFO ] [.o.core.internal.CoreActivator] - openHAB runtime has been start…v1.7.1).
Jan 02 14:13:15 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:15.958 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - mDNS service has been started
Jan 02 14:13:16 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:16.152 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - Service Discovery initializati…mpleted.
Jan 02 14:13:25 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:25.825 [INFO ] [penhab.io.rest.RESTApplication] - Started REST API at /rest
Jan 02 14:13:31 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:31.407 [INFO ] [.o.u.w.i.servlet.WebAppServlet] - Started Classic UI at /openhab.app
Jan 02 14:13:38 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:38.731 [INFO ] [.o.io.habmin.HABminApplication] - Started HABmin REST API at /se…s/habmin
Jan 02 14:13:44 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:44.179 [INFO ] [.z.internal.ZWaveActiveBinding] - ZWave ‘updated’ with null config
Jan 02 14:13:44 raspberrypi openhab.sh[4633]: 2016-01-02 14:13:44.244 [WARN ] [i.internal.GenericItemProvider] - Attempted to register a second… active!
Hint: Some lines were ellipsized, use -l to show in full.
pi@raspberrypi:~ $

wiki says use systemctl method with Debian 8 (Jessie) and above. I found that it created real issues on a clean Jessie installation. MULTIPLE wipe-the-slate and start over reinstalls before I narrowed to systemctl method being a trigger for the permissions issues which were the symptom. Others have not experienced this BUT I was consistently getting the problem on clean installs.

GUESSING you may have two versions of the zwave add-on jar in your addons directory – one from OH install and one from habmin install. If so, delete the lower-numbered version.

Hi

thx no I have all sw up and running but some result, the razberrry board is no recognized as node. Plan to flip to a zwave usb stick …

Continuing the discussion from OpenHab don't recognize Razberry Board /don't see node in HabMin:

[quote=“sihui, post:22, topic:5311, full:true”]
If I find some spare time the next days I will install openhab on jessie again on a brandnew sd card and tell you if there were any problems.[/quote]

I finally found the time to do a new install on Jessie and what can I say: I have now the same problems than you had!
After installation I used systemd to start openhab but I get errors and no logs are created.

pi@raspberrypi:~ $ sudo service openhab status -l
● openhab.service - Starts and stops the openHAB Home Automation Bus
   Loaded: loaded (/usr/lib/systemd/system/openhab.service; enabled)
   Active: inactive (dead) since Sun 2016-01-03 12:38:28 UTC; 11min ago
     Docs: http://www.openhab.org
  Process: 2779 ExecStart=/usr/share/openhab/bin/openhab.sh -o (code=exited, status=0/SUCCESS)
  Process: 2734 ExecStartPre=/usr/share/openhab/bin/setpermissions.sh (code=exited, status=0/SUCCESS)
 Main PID: 2779 (code=exited, status=0/SUCCESS)

Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at java.lang.reflect.Method.invoke(Method.java:483)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: <title>Invalid Configuration Location</title>Locking is not possible in the directory "/var/lib/openhab/workspace/org.eclipse.osgi". A common reason is that the f...
Jan 03 12:38:28 raspberrypi openhab.sh[2779]: Unable to create lock manager.
Hint: Some lines were ellipsized, use -l to show in full.

I followed exactly the OH wiki on apt-get installation.
My time is limited today so I will stop messing around with this … the problem is, I don’t remember how I installed OH on Jessie the last time, maybe I used the “old” init.d way …

Hmm, @theo_weiss, would you be able to have a look at the previous comment? Perhaps you’ve already fixed this for 1.8? Thank you.

Hello everybody,

I’m a beginner and I’m also struggeling with that problem:
I don’t see any node in HABmin.

My hardware:

  • Raspberry Pi 3
  • RaZberry z-wave-board

My installation:

  • Raspbian (Image downloaded from https://www.raspberrypi.org/downloads/)
  • Openhab 1.8.3 (apt-get installation)
  • z-way (Installation with wget -q -O - http://razberry.z-wave.me/install | sudo bash)
  • HABmin (Installation with wget https://github.com/cdjackson/HABmin/archive/master.zip)

In /usr/share/openhab/addons I see:

  • org.openhab.binding.zwave-1.8.3.jar
  • org.openhab.io.habmin-1.7.0-SNAPSHOT.jar
  • and other bindings.

Openhab is running fine and I can also control it by HABdroid.
With z-way I’m able to include z-wave-devices.
(I already added two devices, but also tried without any added devices before.)

Before starting HABmin I stopped z-way-server with
sudo service z-way-server stop
and prevented it from starting up again automatically with
sudo update-rc.d z-way-server disable

Then restarted openhab with
sudo /bin/systemctl restart openhab.service

Now z-way status is:
sudo service z-way-server status


●z-way-server.service - LSB: RaZberry Z-Wave service

   Loaded: loaded (/etc/init.d/z-way-server)

   Active: inactive
(dead)

I can run HABmin by
http://192.168.1.106:8080/habmin/index.html.

In HABmin I can see the z-wave-binding
but on the right side there are no nodes.

My zwave.log shows:


2016-10-29 08:03:16.200 [DEBUG]
[.zwave.internal.ZWaveActivator:36  ]-
Z-Wave binding started. Version 1.8.3

2016-10-29 08:03:16.320 [DEBUG]
[.z.internal.ZWaveActiveBinding:175 ]- ConverterHandler not initialised.
Polling disabled.

2016-10-29 08:03:16.334 [INFO ]
[.z.internal.ZWaveActiveBinding:325 ]- Update config, port = /dev/ttyS0

2016-10-29 08:03:16.335 [INFO ]
[.z.internal.ZWaveActiveBinding:330 ]- Update config, healtime = 2

2016-10-29 08:03:16.336 [INFO ]
[.z.internal.ZWaveActiveBinding:375 ]- Update config, setSUC = true

2016-10-29 08:03:16.336 [INFO ]
[.z.internal.ZWaveActiveBinding:384 ]- Update config, softReset = false

2016-10-29 08:03:16.337 [INFO ]
[.z.internal.ZWaveActiveBinding:393 ]- Update config, masterController = true

2016-10-29 08:03:16.337 [DEBUG]
[.z.internal.ZWaveActiveBinding:282 ]- Initialising zwave binding

2016-10-29 08:03:16.402 [INFO ]
[b.z.i.protocol.ZWaveController:148 ]- Starting Z-Wave controller

2016-10-29 08:03:16.403 [INFO ]
[b.z.i.protocol.ZWaveController:156 ]- Z-Wave timeout is set to 5000ms. Soft
reset is false.

2016-10-29 08:03:16.404 [INFO ]
[b.z.i.protocol.ZWaveController:322 ]- Connecting to serial port /dev/ttyS0

2016-10-29 08:03:16.573 [DEBUG]
[eController$ZWaveReceiveThread:1413]- Starting Z-Wave thread: Receive

2016-10-29 08:03:16.590 [INFO ]
[b.z.i.protocol.ZWaveController:342 ]- Serial port is initialized

2016-10-29 08:03:16.594 [DEBUG]
[WaveController$ZWaveSendThread:1197]- Starting Z-Wave thread: Send

2016-10-29 08:03:16.603 [DEBUG] [b.z.i.protocol.ZWaveController:1154]-
Starting Z-Wave thread: Input

2016-10-29 08:03:19.611 [DEBUG]
[veController$WatchDogTimerTask:178 ]- Initialising network

2016-10-29 08:03:19.627 [DEBUG]
[o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of
class = GetVersion (0x15), type = Request (0x00)

2016-10-29 08:03:19.628 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1

2016-10-29 08:03:19.628 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 0

2016-10-29 08:03:19.631 [DEBUG]
[o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of
class = MemoryGetId (0x20), type = Request (0x00)

2016-10-29 08:03:19.631 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 15
E9 

2016-10-29 08:03:19.632 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1

2016-10-29 08:03:19.633 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 15 E9 

2016-10-29 08:03:19.637 [DEBUG]
[o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of
class = SerialApiGetCapabilities (0x07), type = Request (0x00)

2016-10-29 08:03:19.638 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 2

2016-10-29 08:03:19.641 [DEBUG]
[o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of
class = SerialApiSetTimeouts (0x06), type = Request (0x00)

2016-10-29 08:03:19.641 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 3

2016-10-29 08:03:19.643 [DEBUG]
[i.p.s.GetSucNodeIdMessageClass:30  ]-
Get SUC NodeID

2016-10-29 08:03:19.644 [DEBUG] [o.b.z.i.protocol.SerialMessage:109
]- NODE 255: Creating empty message of class = GetSucNodeId (0x56), type =
Request (0x00)

2016-10-29 08:03:19.645 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 4

2016-10-29 08:03:21.347 [DEBUG] [z.internal.ZWaveNetworkMonitor:315
]- Network Monitor: Queue length is 4 - deferring network monitor functions.

2016-10-29 08:03:24.653 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 2 attempts left!

2016-10-29 08:03:24.654 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 5

2016-10-29 08:03:24.654 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 4

2016-10-29 08:03:24.655 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 15
E9 

2016-10-29 08:03:24.656 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 15 E9 

2016-10-29 08:03:26.348 [DEBUG] [z.internal.ZWaveNetworkMonitor:315
]- Network Monitor: Queue length is 4 - deferring network monitor functions.

2016-10-29 08:03:29.673 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 1 attempts left!

2016-10-29 08:03:29.676 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 5

2016-10-29 08:03:29.677 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 4

2016-10-29 08:03:29.678 [DEBUG] [o.b.z.i.protocol.SerialMessage:233
]- Assembled message buffer = 01 03 00 15 E9 

2016-10-29 08:03:29.679 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 15 E9 

2016-10-29 08:03:31.349 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 4 -
deferring network monitor functions.

2016-10-29 08:03:34.693 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 0 attempts left!

2016-10-29 08:03:34.694 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 5

2016-10-29 08:03:34.698 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 4

2016-10-29 08:03:34.699 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 15
E9 

2016-10-29 08:03:34.700 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 15 E9 

2016-10-29 08:03:36.350 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 4 -
deferring network monitor functions.

2016-10-29 08:03:39.713 [WARN ]
[WaveController$ZWaveSendThread:1318]- NODE 255: Too many retries. Discarding
message: Message: class = GetVersion (0x15), type = Request (0x00), payload = 

2016-10-29 08:03:39.714 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 3

2016-10-29 08:03:40.150 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 20
DC 

2016-10-29 08:03:40.151 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 20 DC 

2016-10-29 08:03:41.351 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 3 -
deferring network monitor functions.

2016-10-29 08:03:45.163 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 2 attempts left!

2016-10-29 08:03:45.163 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 4

2016-10-29 08:03:45.164 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 3

2016-10-29 08:03:45.165 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 20
DC 

2016-10-29 08:03:45.166 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 20 DC 

2016-10-29 08:03:45.167 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x04. Sending
NAK.

2016-10-29 08:03:45.493 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x0E. Sending
NAK.

2016-10-29 08:03:45.513 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x04. Sending
NAK.

2016-10-29 08:03:46.352 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 3 -
deferring network monitor functions.

2016-10-29 08:03:50.183 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 1 attempts left!

2016-10-29 08:03:50.602 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 4

2016-10-29 08:03:50.603 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 3

2016-10-29 08:03:50.604 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 20
DC 

2016-10-29 08:03:50.606 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 20 DC 

2016-10-29 08:03:51.352 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 3 -
deferring network monitor functions.

2016-10-29 08:03:55.623 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 0 attempts left!

2016-10-29 08:03:55.624 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 4

2016-10-29 08:03:55.624 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 3

2016-10-29 08:03:55.625 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 20
DC 

2016-10-29 08:03:55.626 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 20 DC 

2016-10-29 08:03:56.353 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 3 -
deferring network monitor functions.

2016-10-29 08:04:00.643 [WARN ]
[WaveController$ZWaveSendThread:1318]- NODE 255: Too many retries. Discarding
message: Message: class = MemoryGetId (0x20), type = Request (0x00), payload = 

2016-10-29 08:04:00.644 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 2

2016-10-29 08:04:00.645 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 07
FB 

2016-10-29 08:04:00.646 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 07 FB 

2016-10-29 08:04:01.354 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 2 -
deferring network monitor functions.

2016-10-29 08:04:05.663 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 2 attempts left!

2016-10-29 08:04:05.664 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 3

2016-10-29 08:04:05.664 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 2

2016-10-29 08:04:05.665 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 07
FB 

2016-10-29 08:04:05.666 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 07 FB 

2016-10-29 08:04:06.355 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 2 -
deferring network monitor functions.

2016-10-29 08:04:10.683 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 1 attempts left!

2016-10-29 08:04:10.684 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 3

2016-10-29 08:04:10.684 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 2

2016-10-29 08:04:10.685 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 07
FB 

2016-10-29 08:04:10.686 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 07 FB 

2016-10-29 08:04:11.356 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 2 -
deferring network monitor functions.

2016-10-29 08:04:15.703 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 0 attempts left!

2016-10-29 08:04:15.703 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 3

2016-10-29 08:04:15.704 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 2

2016-10-29 08:04:15.705 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 07
FB 

2016-10-29 08:04:15.706 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 07 FB 

2016-10-29 08:04:16.357 [DEBUG]
[z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 2 -
deferring network monitor functions.

2016-10-29 08:04:20.723 [WARN ]
[WaveController$ZWaveSendThread:1318]- NODE 255: Too many retries. Discarding
message: Message: class = SerialApiGetCapabilities (0x07), type = Request
(0x00), payload = 

2016-10-29 08:04:20.724 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 1

2016-10-29 08:04:20.725 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 06
96 0F 65 

2016-10-29 08:04:20.726 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
05 00 06 96 0F 65 

2016-10-29 08:04:20.729 [DEBUG]
[eController$ZWaveReceiveThread:1481]- Receive Message = 01 03 00 01 04 

2016-10-29 08:04:20.730 [ERROR]
[eController$ZWaveReceiveThread:1393]- Message is not valid, discarding

2016-10-29 08:04:20.763 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x0E. Sending
NAK.

2016-10-29 08:04:20.783 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x04. Sending
NAK.

2016-10-29 08:04:25.743 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 2 attempts left!

2016-10-29 08:04:25.744 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 2

2016-10-29 08:04:25.744 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 1

2016-10-29 08:04:25.745 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 06
96 0F 65 

2016-10-29 08:04:25.746 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
05 00 06 96 0F 65 

2016-10-29 08:04:30.763 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 1 attempts left!

2016-10-29 08:04:30.764 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 2

2016-10-29 08:04:30.765 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 1

2016-10-29 08:04:30.767 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 06
96 0F 65 

2016-10-29 08:04:30.769 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
05 00 06 96 0F 65 

2016-10-29 08:04:30.772 [DEBUG]
[eController$ZWaveReceiveThread:1481]- Receive Message = 01 03 00 01 82 

2016-10-29 08:04:30.774 [ERROR] [eController$ZWaveReceiveThread:1393]-
Message is not valid, discarding

2016-10-29 08:04:30.803 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x12. Sending
NAK.

2016-10-29 08:04:30.823 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0xC0. Sending
NAK.

2016-10-29 08:04:30.843 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0x02. Sending
NAK.

2016-10-29 08:04:30.863 [WARN ]
[eController$ZWaveReceiveThread:1508]- Protocol error (OOF). Got 0xF8. Sending
NAK.

2016-10-29 08:04:35.783 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 0 attempts left!

2016-10-29 08:04:35.784 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 2

2016-10-29 08:04:35.787 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 1

2016-10-29 08:04:35.788 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 06
96 0F 65 

2016-10-29 08:04:35.789 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
05 00 06 96 0F 65 

2016-10-29 08:04:40.804 [WARN ]
[WaveController$ZWaveSendThread:1318]- NODE 255: Too many retries. Discarding
message: Message: class = SerialApiSetTimeouts (0x06), type = Request (0x00),
payload = 96 0F 

2016-10-29 08:04:40.804 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 0

2016-10-29 08:04:40.809 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 56
AA 

2016-10-29 08:04:40.810 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 56 AA 

2016-10-29 08:04:45.823 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 2 attempts left!

2016-10-29 08:04:45.824 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1

2016-10-29 08:04:45.824 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 0

2016-10-29 08:04:45.825 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 56
AA 

2016-10-29 08:04:45.826 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 56 AA 

2016-10-29 08:04:50.843 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 1 attempts left!

2016-10-29 08:04:50.844 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1

2016-10-29 08:04:50.849 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 0

2016-10-29 08:04:50.850 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 56
AA 

2016-10-29 08:04:50.851 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 56 AA 

2016-10-29 08:04:55.863 [ERROR]
[WaveController$ZWaveSendThread:1309]- NODE 255: Timeout while sending message.
Requeueing - 0 attempts left!

2016-10-29 08:04:55.864 [DEBUG]
[b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1

2016-10-29 08:04:55.867 [DEBUG]
[WaveController$ZWaveSendThread:1211]- Took message from queue for sending.
Queue length = 0

2016-10-29 08:04:55.868 [DEBUG]
[o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 56
AA 

2016-10-29 08:04:55.869 [DEBUG]
[WaveController$ZWaveSendThread:1268]- NODE 255: Sending REQUEST Message = 01
03 00 56 AA 

2016-10-29 08:05:00.883 [WARN ]
[WaveController$ZWaveSendThread:1318]- NODE 255: Too many retries. Discarding
message: Message: class = GetSucNodeId (0x56), type = Request (0x00), payload =


User openhab is added to dialout-group and typing

top

u

openhab

shows that the user runs java and openhab.sh

So I don’t know what’s my mistake.
Can anybody help me please?

Thanks, rud