Z-wave binding

SteMo · January 14, 2016, 9:09am

Hello, I need your help.
I try to get the z-wave binding into operation but it always fails. I have a Rasperry 2 with the z-wave extension board.
Habmin runs, the connection is green. It seems to be all right. But when I press the include button in HABmin (and also on the z-wave device) nothing happens. Also no node entry after a reboot.
With the zway software it’s no problem, but I want to use openHAB. I used different devices but always the same result.
Within the openHAB log file I can’t see a hint to z-wave. Therefore I think it’s not running, but I am not sure.
Is there an additional logfile or what ever else where I can see whether the z-wave binding is ok?

Or is there anyone who can give me his Raspberry image that I can use it, because I am not a linux expert and maybe the problem is within this system and the authorization or whatever else.

Hope someone can help and support me. I’m getting crazy.

watou · January 14, 2016, 10:12am

Are you on 1.8.0 or 2.0 Beta 1? The currently available Z-Wave binding is known not to work with openHAB 2.0 Beta 1. FWIW, the Z-Wave binding is working for me on a Raspberry Pi 2 Model B running openHAB 1.8.0, using an Aeon Labs Z Stick Gen 5.

Spaceman_Spiff · January 14, 2016, 12:10pm

Raspberry Pi Model 2 with 1.8.0 working at my place with

Aeon Labs Z Stick Gen 4
Aeon Labs Z Stick Gen 5

SteMo · January 14, 2016, 12:22pm

I am using the 1.7.1 version. The failure I have should be another one.

bob_dickenson · January 14, 2016, 2:22pm

Debugging suggestions:

Have you made the required changes in your openhab.cfg for the zwave binding. If this is a new installation – most likely culprit. If an upgrade to a previously working installation, check to make sure the port name has not changed (esp on OS-level changes !!)
Do you know if the underlying OS has the requisite drivers to talk to the extension board ? ( I don’t have an extension board but use z-stick controllers. )

SteMo · January 14, 2016, 3:53pm

I have changed the 2 necessary points in the config.cfg.
Last week the port name was still a problem, but this should be solved.It’s ttyAMA0 - hopefully. Is there a way to check this whether it’s really the right port?
Regarding the drivers, how can I ckeck this respectively how can I get this driver? On my other SD card I have installed the zway software which runs. Shall I install it also on the openhab SD card to get the driver?

bob_dickenson · January 14, 2016, 4:21pm

I would install the drivers by the same method you did to your working SD card – apt-get or tar…

SteMo · January 14, 2016, 7:24pm

Thanx Bob. I will install the zway.

When I start openhab via the terminal I see nothing:

openhab@raspberrypi:/etc/init.d$ sudo ./openhab start
[ ok ] Starting openHAB server: openhab.
openhab@raspberrypi:/etc/init.d$

Is this right or is also this a failure?

bob_dickenson · January 14, 2016, 7:34pm

this is normal startup msg behavior.

I’d do the following to “inspect”:

A. sudo /etc/init.d/openhab status

This basically will show the last few lines of the openhab log.

B. cd /var/logs/openhab and “tail -f -n40 openhab.log” (or “tail -f -n40 /var/logs/openhab/openhab.log” from anywhere) to watch the ongoing OH. To watch zwave in particular, change the message level to “DEBUG” for the zwave appender in logback.xml and “tail -f -n40 zwave.log” in /var/logs/openhab.

When I’m doing serious config debugging, I’ll have 4 or more command windows open on my pi’s X desktop (vnc remote-d), each window “tail”-ing some different logfile. Highly recommend you spend some time fiddling with logback.xml and your log statements in rules to split various logging targets and message types.

SteMo · January 14, 2016, 8:38pm

Hi,

I had a lookinto the openhab.log and found the following entry:

2016-01-14 21:30:30.155 [WARN ] [WaveController$ZWaveSendThread] - Receive queue TIMEOUT:

as well as in workspace/.log

!ENTRY org.eclipse.equinox.ds 4 0 2016-01-14 20:48:30.635
!MESSAGE Could not bind a reference of component org.openhab.io.habmin.servlet. The reference is: Reference[name = ConfigurationService, interface = org.openhab.binding.zwave.internal.config.OpenHABConfigurationService, policy = dynamic, cardinality = 0…n, target = null, bind = addConfigurationService, unbind = removeConfigurationService]

!ENTRY org.eclipse.equinox.ds 4 0 2016-01-14 20:48:30.636
!MESSAGE Could not bind a reference of component org.openhab.io.habmin.servlet. The reference is: Reference[name = ConfigurationService, interface = org.openhab.binding**.zwave.internal.**config.OpenHABConfigurationService, policy = dynamic, cardinality = 0…n, target = null, bind = addConfigurationService, unbind = removeConfigurationService]

It seems that the z-wave do not run. But why??

bob_dickenson · January 15, 2016, 11:11am

Are you sure the zwave add-in jar has been added to your add-ins directory ? If not, do that first and re-try.

If the zwave jar IS in your add-ins OR it still fails after your add it to that directory, edit the logback.xml file so that it includes the following (among other things):

    
        ${openhab.logdir:-logs}/zwave.log
        
        
            ${openhab.logdir:-logs}/zwave-%d{yyyy-ww}.log.zip
        
            30
        
        
            %d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{30}[:%line]- %msg%n%ex{5}

also the following

This will give you a really verbose and protocol-specific zwave.log file. Look at that CAREFULLY. Find the ERROR or WARNING messages and work backwards (ie toward the beginning of the log) looking for the component or phase names as your chain of evidence. This will help isolate what was going on at the time of failure and guide the next steps.

SteMo · January 15, 2016, 6:31pm

I did what Bob recommended. The add-in jar for z-wave is installed.
The logfile gives the following infos.
Sorry, it’s rather long, but maybe see anyone of you whats going wrong. I found the “ConverterHandler not initialised” as well as "Protocol error ". Is this the problen an if, how can I solve it.

2016-01-15 19:18:54.948 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding started. Version 1.7.1
2016-01-15 19:18:55.027 DEBUG o.o.b.z.i.ZWaveActiveBinding[:175]- ConverterHandler not initialised. Polling disabled.
2016-01-15 19:18:55.036 INFO o.o.b.z.i.ZWaveActiveBinding[:325]- Update config, port = /dev/ttyAMA0
2016-01-15 19:18:55.038 INFO o.o.b.z.i.ZWaveActiveBinding[:330]- Update config, healtime = 2
2016-01-15 19:18:55.039 DEBUG o.o.b.z.i.ZWaveActiveBinding[:282]- Initialising zwave binding
2016-01-15 19:18:55.203 INFO o.o.b.z.i.p.ZWaveController[:146]- Starting Z-Wave controller
2016-01-15 19:18:55.206 INFO o.o.b.z.i.p.ZWaveController[:154]- Z-Wave timeout is set to 5000ms. Soft reset is false.
2016-01-15 19:18:55.208 INFO o.o.b.z.i.p.ZWaveController[:407]- Connecting to serial port /dev/ttyAMA0
2016-01-15 19:18:55.429 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1460]- Starting Z-Wave thread: Receive
2016-01-15 19:18:55.436 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1244]- Starting Z-Wave thread: Send
2016-01-15 19:18:55.439 INFO o.o.b.z.i.p.ZWaveController[:427]- Serial port is initialized
2016-01-15 19:18:55.439 DEBUG o.o.b.z.i.p.ZWaveController[:1201]- Starting Z-Wave thread: Input
2016-01-15 19:18:58.444 DEBUG o.o.b.z.i.p.ZWaveController$WatchDogTimerTask[:176]- Initialising network
2016-01-15 19:18:58.473 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 255: Creating empty message of class = GetVersion (0x15), type = Request (0x00)
2016-01-15 19:18:58.475 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 1
2016-01-15 19:18:58.475 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 0
2016-01-15 19:18:58.479 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 15 E9
2016-01-15 19:18:58.479 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 255: Creating empty message of class = MemoryGetId (0x20), type = Request (0x00)
2016-01-15 19:18:58.481 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 15 E9
2016-01-15 19:18:58.481 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 1
2016-01-15 19:18:58.489 WARN o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1555]-Protocol error (OOF). Got 0x61. Sending NAK.
2016-01-15 19:18:58.492 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 255: Creating empty message of class = SerialApiGetCapabilities (0x07), type = Request (0x00)
2016-01-15 19:18:58.493 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 2
2016-01-15 19:18:58.498 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 255: Creating empty message of class = SerialApiSetTimeouts (0x06), type = Request (0x00)
2016-01-15 19:18:58.499 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 3
2016-01-15 19:18:58.502 DEBUG o.o.b.z.i.p.s.GetSucNodeIdMessageClass[:30]- Get SUC NodeID
2016-01-15 19:18:58.505 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 255: Creating empty message of class = GetSucNodeId (0x56), type = Request (0x00)
2016-01-15 19:18:58.506 WARN o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1555]- Protocol error (OOF). Got 0x10. Sending NAK.
2016-01-15 19:18:58.510 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 4
2016-01-15 19:19:00.043 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 4 - deferring network monitor functions.
2016-01-15 19:19:03.505 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-15 19:19:05.045 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 4 - deferring network monitor functions.
2016-01-15 19:19:05.051 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 5
2016-01-15 19:19:05.053 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 4
2016-01-15 19:19:05.055 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 15 E9
2016-01-15 19:19:05.057 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 15 E9
2016-01-15 19:19:05.060 WARN o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1555]- Protocol error (OOF). Got 0x61. Sending NAK.
2016-01-15 19:19:10.053 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 4 - deferring network monitor functions.
2016-01-15 19:19:10.074 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-15 19:19:10.076 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 5
2016-01-15 19:19:10.077 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 4
2016-01-15 19:19:10.079 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 15 E9
2016-01-15 19:19:10.081 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 15 E9
2016-01-15 19:19:15.054 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 4 - deferring network monitor functions.
2016-01-15 19:19:15.094 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-15 19:19:15.136 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 5
2016-01-15 19:19:15.137 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 4
2016-01-15 19:19:15.139 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 15 E9
2016-01-15 19:19:15.140 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 15 E9
2016-01-15 19:19:20.056 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 4 - deferring network monitor functions.
2016-01-15 19:19:20.155 WARN o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1365]- NODE 255: Too many retries. Discarding message: Message: class = GetVersion (0x15), type = Request (0x00), payload =
2016-01-15 19:19:20.157 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 3
2016-01-15 19:19:20.429 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 20 DC
2016-01-15 19:19:20.431 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 20 DC
2016-01-15 19:19:25.058 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 3 - deferring network monitor functions.
2016-01-15 19:19:25.444 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-15 19:19:25.445 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 4
2016-01-15 19:19:25.446 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 3
2016-01-15 19:19:25.447 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 20 DC
2016-01-15 19:19:25.449 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 20 DC
2016-01-15 19:19:25.559 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 76 01 76 65 20 33 2E 39 39 00 01 95 61 76 65 20 33 2E 39 39 00 01 95 01 76 01 01 76 65 20 33 2E 39 39 01 76 65 20 33 2E 39 39 00 01 95 61 76 65 20 33 2E 39 39 00 01 95 61 76 65 20 33 2E 39 39 00 01 95 01 10 57 39 00 01 95 01 08 01 20 F4 19 AE BF 01 2B 01 2B 20 F4 19 AE BF 01 2B 01 08 01 20 F4 19 AE BF 01 2B 06 01 01 20 F4 19 BF 01 01 01 20 F4 19 AE BF 01
2016-01-15 19:19:25.580 ERROR o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1440]- Message is not valid, discarding
2016-01-15 19:19:30.059 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 3 - deferring network monitor functions.
2016-01-15 19:19:30.464 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-15 19:19:30.466 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 4
2016-01-15 19:19:30.467 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 3
2016-01-15 19:19:30.470 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 20 DC
2016-01-15 19:19:30.472 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 20 DC
2016-01-15 19:19:35.061 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 3 - deferring network monitor functions.
2016-01-15 19:19:35.484 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-15 19:19:35.486 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 4
2016-01-15 19:19:35.487 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 3
2016-01-15 19:19:35.489 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 20 DC
2016-01-15 19:19:35.490 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 20 DC
2016-01-15 19:19:40.063 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 3 - deferring network monitor functions.
2016-01-15 19:19:40.505 WARN o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1365]- NODE 255: Too many retries. Discarding message: Message: class = MemoryGetId (0x20), type = Request (0x00), payload =
2016-01-15 19:19:40.506 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 2
2016-01-15 19:19:40.508 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 07 FB
2016-01-15 19:19:40.510 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 07 FB
2016-01-15 19:19:45.065 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 2 - deferring network monitor functions.
2016-01-15 19:19:45.524 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-15 19:19:45.526 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 3
2016-01-15 19:19:45.527 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 2
2016-01-15 19:19:45.529 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 03 00 07 FB
2016-01-15 19:19:45.531 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 255: Sending REQUEST Message = 01 03 00 07 FB
2016-01-15 19:19:45.772 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 F4 01 2B 01 2B 01 2B 01 01 2B 01 08 01 20 F4 19 AE BF 01 2B 01 AE BF 01 2B 01 08 01 20 F4 19 AE BF 01 2B 01 01 20 19 BF 47 04 00 00 01 FE 83 FF 88 CF 1F 00 00 FB 9F 7D A0 67 00 80 80 00 80 86 00 00 40 1A 00 59 04 00 00 01 FE 83 FF 88 CF 1F 00 00 FB 9F 7D A0 67 00 80 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 40 1A 00 59 01 04 CF 7D A0 67 00 80 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 40 1A 00 59 01 2B 01 07 05 00 01 47 04 00 00 01 FE 83 FF 88 CF 1F 00 00 FB 9F 7D A0 67 00 80 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 40 1A 00 59 06 47 04 00 00 01 FE 83 FF 88 CF 1F 00 00 FB 9F 7D A0 67 00 80 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 40 1A 00 59 04 00 00 01 FE 83 FF 88 CF 1F 00 00 FB 9F 7D A0 67 00 40 1A 00 59 01 04 00 00 01 FE
2016-01-15 19:19:45.805 ERROR o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1440]- Message is not valid, discarding
2016-01-15 19:19:50.066 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:315]- Network Monitor: Queue length is 2 - deferring network monitor functions.

bob_dickenson · January 15, 2016, 7:19pm

I think maybe @chris should look at this one. Clearly some protocol and/or device issue here.

chris · January 15, 2016, 7:37pm

I’m not sure what’s up here. The OOF error means that the binding has received a byte that it wasn’t expecting - eg if it’s expecting a start byte, and it gets some other byte, then that’s an ‘out of frame’ error…

But I would have expected to see some packet data in the received message at the end, but this is just rubbish as well.

One possibility is that the speed is wrong, but this is fixed and I’ve never heard of anything using anything different. I’m reasonably sure that others are using the z-wave extension board on the Pi (it would be good if someone confirmed this since it’s possible that this board requires a different baud rate).

chris · January 15, 2016, 7:46pm

It seems z-wave RPi board is using the same speed (115k) as the other standard Z-Wave USB sticks, so it’s probably not that…

I found this for installation - it’s probably not useful, but thought I’d post it all the same…
http://razberry.z-wave.me/install

SteMo · January 16, 2016, 6:13pm

I did some further steps. Now it looks a little better, but 2 errors remains. Do it help to find the problem?

2016-01-16 19:10:31.759 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 25: Node advancer - queued packet. Queue length is 1
2016-01-16 19:10:31.775 ERROR o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1356]- NODE 25: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-16 19:10:31.776 ERROR o.o.b.z.i.p.s.SendDataMessageClass[:158]- NODE 25: Got an error while sending data. Resending message.
2016-01-16 19:10:31.777 DEBUG o.o.b.z.i.p.ZWaveController[:985]- Callback ID = 14

chris · January 17, 2016, 7:11pm

Timeout errors like these are not completely uncommon - although they should be rare. They are normally indicative of poor communications - wireless communications is never 100% guaranteed, so this will happen, but if it’s happening often then you should look at the network topology to see what can be improved…

SteMo · January 17, 2016, 10:19pm

Thanx all of you. In the meantime I could solve my problem.
I have installed the zway Software with the UI. I rebootet the system and stopped the openhab programm. Then I included the devices with zway. After that I stopped zway and started openhab - and the devices were included. Yeah.

Now there is one remaining problen. Zway starts always when I reboot the system. How can I avoid this? Where can I delete this autostart.

chris · January 18, 2016, 12:02am

Maybe you should ask this on the zway forum (if there is one)?

Eddiie · January 22, 2016, 3:40pm

sudo service z-way-server stop
sudo update-rc.d z-way-server disable