Connection to AEON z-wave stick fails after "upgrade" to snapshot

Add-ons Bindings
,
1

I had a working Openhab2 Beta3 installation and decided to go for the latest snapshot version to look at the latest developments in Openhab2. The upgrade was done by: apt-get purge openhab2-online and the reinstalling from scratch. I then added the user openhab to the group dialout, added ttyAMA0 to /etc/default/openhab2 and restarted my raspberry pi, installed the z-wave binding and Habmin. I have set the port for the z-wave controller to /dev/tty/AMA0 in Habmin. But I cant connect to it. The log shows the following:

2016-09-06 19:54:29.279 [INFO ] [b.core.service.AbstractActiveService] - HTTP Refresh Service has been started
2016-09-06 19:54:29.675 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2016-09-06 19:54:33.988 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyAMA0'
2016-09-06 19:54:34.182 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2016-09-06 19:54:34.226 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2016-09-06 19:54:34.290 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2016-09-06 19:54:34.296 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2016-09-06 19:54:42.365 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-09-06 19:54:47.384 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-06 19:54:52.404 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-09-06 19:54:57.425 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=GetVersion[0x15], type=Request[0x00], priority=High, dest=255, callback=0, payload=
2016-09-06 19:55:02.444 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-09-06 19:55:07.464 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-06 19:55:12.484 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-09-06 19:55:17.504 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=MemoryGetId[0x20], type=Request[0x00], priority=High, dest=255, callback=0, payload=
2016-09-06 19:55:22.524 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-09-06 19:55:27.544 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-06 19:55:32.564 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-09-06 19:55:37.584 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=SerialApiGetCapabilities[0x07], type=Request[0x00], priority=High, dest=255, callback=0, payload=
2016-09-06 19:55:42.604 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-09-06 19:55:47.624 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-06 19:55:52.644 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-09-06 19:55:57.664 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=SerialApiSetTimeouts[0x06], type=Request[0x00], priority=High, dest=255, callback=0, payload=96 0F 
2016-09-06 19:56:02.684 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-09-06 19:56:07.704 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-06 19:56:12.724 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-09-06 19:56:17.744 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=GetSucNodeId[0x56], type=Request[0x00], priority=High, dest=255, callback=0, payload=

No other z-wave servers are running.

Any help will be greatly appreciated.

2

Does habmin shows the Controller thing as online?

And are you really sure that AMA0 ist the right port? I remember that I also had this device port in my list, but the right one for my Aeon stick was some kind of ACM… (didn’t remember exactly)

3

It was the right port when using the beta version. In Habmin it says “Controller is offline”. If I try with ACM0 it says that port does not exists.

4

I would suggest to do the following:

Start your OS (in my case: raspbian) without (!) the AEON stick.
Do a
ls /dev/tty*
to see the output.
Connect the Aeon-stick and do the command again.
Have a look which port was added to make sure this one belongs to the stick
Do a
sudo usermod -a -G dialout openhab
Reboot the whole system
Start Habmin and enter the port in the controller thing (maybe you also delete the current controller thing first and let habmin find the thing once again)
Check if habmin status for the controller changes to ONLINE.

Wait…as I wrote this…you wrote that you entered /dev/tty/AMA0 in habmin. Doesn’t it have to be /dev/ttyAMA0 (without the slash after tty)?? Ah, I see the “wrong” declaration in your text but the (probably) correct declaration in the log file. Maybe you check this again…

1 Like
5

That helped me:-) By following your steps I found out that the port had changed to ACM0. After changing /ect/default/openhab2 by adding -Dgnu.io.rxtx.SerialPorts=/dev/ttyACM0 to the EXTRA_JAVA_OPTS and restarting the system the stick is recognized by Habmin. Thank you for your help.