Autostart openhab 1.8.1 on Raspberry Pi2 (Gen5 Z-Stick)

When I autostart openhab nothing happens. I found this in the log:

2016-03-09 00:18:07.925 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyACM0
2016-03-09 00:18:07.926 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, healtime = 2
2016-03-09 00:18:07.928 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started
2016-03-09 00:18:08.027 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
2016-03-09 00:18:08.029 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2016-03-09 00:18:08.031 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM0
2016-03-09 00:18:08.118 [ERROR] [b.z.i.protocol.ZWaveController] - Serial Error: Port /dev/ttyACM0 does not exist
2016-03-09 00:18:12.931 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been shut down

Based on the speed when doing it manually I’d doubt it is processing to fast to see the stick. Any thoughts?

Thanks in advance,
Jerry

Did you add the user that’s running the autostarted openHAB server to the dialout group, so it has permission to use the serial port?

Did you remove the Gen5 Z-Stick and plug it back in? It will get an new dev path if you remove it to bind and then plug it back in.

Did you try a reboot? This should reset the dev.

What does ls -la /dev/ttyA* return? One of them should be owned by the dialout group.

crw-rw---- 1 root dialout 166, 0 Mar 9 11:38 /dev/ttyACM0
crw–w---- 1 root tty 204, 64 Mar 9 11:30 /dev/ttyAMA0

watou,
Not sure how to tell what user is running the script. I have added a few random users to the dialout group but have not gotten lucky yet. :slight_smile:

Toneus,
I have not removed the Z-Stick and I have rebooted several times.
ls -la /dev/ttyA* returns:
crw-rw-rw- 1 root dialout 166, 0 Mar 9 14:10 /dev/ttyACM0
crw–w---- 1 root tty 204, 64 Mar 9 14:04 /dev/ttyAMA0

I removed everything I had and recreated it and now it is working so I must have missed something. :joy: