[Solved] Zwave quit recognizing Serial Port even w/ reboot

I’m running on a Rasberry Pi with an Aeon stick and every now and then it quits seeing the stick on /dev/ttyACM0 but usually after a reboot it comes back online. It went down today and won’t come back. I’ve verified that the port is there, I’ve verified all my group settings for dialout.

If I login through startup.sh I get the following errors:

java.lang.UnsatisfiedLinkError: gnu.io.RXTXCommDriver.nativeGetVersion()Ljava/lang/String; thrown while loading gnu.io.RXTXCommDriver
java.lang.NoClassDefFoundError: Could not initialize class gnu.io.RXTXCommDriver thrown while loading gnu.io.RXTXCommDriver

If I run debug on bootup I get this info which doesn’t seem too helpful:

2016-12-25 17:24:25.630 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2016-12-25 17:24:25.633 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller.
2016-12-25 17:24:25.658 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
2016-12-25 17:24:25.701 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=325, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:25.705 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=326, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:25.790 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=327, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:25.813 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=328, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.082 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=329, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.083 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=330, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.092 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=331, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.148 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=332, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.250 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=333, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.256 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=334, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.289 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=335, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.351 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=336, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.363 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=337, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.450 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=338, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.451 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=339, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.475 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=340, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.572 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=341, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.591 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=342, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.608 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=343, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.621 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=344, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.636 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=345, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.661 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=346, service.bundleid=193, service.scope=singleton} - org.openhab.binding.zwave
2016-12-25 17:24:26.839 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler.
2016-12-25 17:24:26.844 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Controller status changed to OFFLINE.
2016-12-25 17:24:26.846 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 31: Controller is not online.

Any other ideas?

1 Like

Looks like it was either a build issue or a missing library. Installed this library: RFXCom issue on RP3 and did an apt-get update/upgrade and am now back online together and am back up and running. Not sure which one solved the issue but glad to be back online.