Z-wave on synology NAS

[Vilhelm Pihlsgård]

Hello

I am having troubles with my Aeon USB stick.
I have installed OpenHAB 1.4.0 on my Synology NAS togheter with Java 7, wich seems to work. But when I am adding the z-wave module OpenHAB will not run any more.

When I am running "start_debug.sh" I get the following error.

Any ideas abaout whats wrong?

/ Vilhelm

12:12:45.740 [openHAB-job-scheduler_

QuartzSchedulerThread] DEBUG o.quartz.core.QuartzSchedulerThread - batch acquisition of 1 triggers
12:12:45.748 [org.openhab.core.internal.logging.OSGILogListener$NLogListener@135701c] INFO  OSGi - ServiceEvent REGISTERED
12:12:45.750 [org.openhab.core.internal.logging.OSGILogListener$NLogListener@135701c] INFO  OSGi - BundleEvent STARTED
12:12:45.827 [ManagedService Update Queue] INFO  o.o.b.z.internal.ZWaveActiveBinding - Update config, port = /dev/ttyUSB0
12:12:45.837 [ZWave Refresh Service] INFO  o.o.c.service.AbstractActiveService - ZWave Refresh Service has been started
12:12:45.838 [ZWave Refresh Service] DEBUG o.o.b.z.internal.ZWaveActiveBinding - Zwave Network isn't ready yet!
12:12:45.998 [ManagedService Update Queue] INFO  o.o.b.z.i.protocol.ZWaveController - Starting Z-Wave controller
12:12:45.998 [ManagedService Update Queue] INFO  o.o.b.z.i.protocol.ZWaveController - Connecting to serial port /dev/ttyUSB0
12:12:46.141 [FolderObserver] INFO  o.o.m.c.internal.ModelRepositoryImpl - Loading model 'demo.script'
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB1
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x4edefb94, pid=26524, tid=1337877616
#
# JRE version: Java(TM) SE Embedded Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13)
# Java VM: Java HotSpot(TM) Embedded Client VM (24.51-b03 mixed mode linux-arm )
# Problematic frame:
# C  [libNRJavaSerialv6_HF.so+0x8b94]  Java_gnu_io_RXTXCommDriver_testRead+0x1c0
#
# Core dump written. Default location: /volume1/@appstore/OpenHAB/core or core.26524
#
# An error report file with more information is saved as:
# /volume1/@appstore/OpenHAB/hs_err_pid26524.log
Segmentation fault (core dumped)

dmesg gives me:
[   80.270000] init: synoindexd main process (6839) killed by USR2 signal
[   80.310000] init: synoindexd main process ended, respawning
[   85.650000] usbip_common_mod: module is from the staging directory, the quality is unknown, you have been warned.
[   85.660000] usbip_common_mod: usbip common driver1.0
[   85.680000] usbip: module is from the staging directory, the quality is unknown, you have been warned.
[   85.730000] usbip 1-1.3:1.0: this device 1-1.3 is not in match_busid table. skip!
[   85.730000] usbcore: registered new interface driver usbip
[   85.740000] usbip:Stub Driver for USB/IP:1.0
[   92.670000] usbcore: registered new interface driver usbserial
[   92.670000] usbserial: USB Serial Driver core
[   92.730000] USB Serial support registered for FTDI USB Serial Device
[   92.770000] usbcore: registered new interface driver ftdi_sio
[   92.780000] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
[   92.880000] USB Serial support registered for pl2303
[   92.930000] usbcore: registered new interface driver pl2303
[   92.930000] pl2303: Prolific PL2303 USB to serial adaptor driver
[   92.980000] USB Serial support registered for cp210x
[   92.990000] cp210x 1-1.3:1.0: cp210x converter detected
[   92.990000] usb 1-1.3: lock for hub EH
[   93.090000] usb 1-1.3: reset full speed USB device using orion-ehci and address 3
[   93.130000] hub is performing EH
[   93.200000] usb 1-1.3: unlock for hub EH
[   93.200000] usb 1-1.3: cp210x converter now attached to ttyUSB0
[   93.240000] usbcore: registered new interface driver cp210x
[   93.240000] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
[   95.400000] loop: module loaded
[   97.040000] Slow work thread pool: Starting up
[   97.230000] Slow work thread pool: Ready

[pie...@gmail.com]

You do not tell which DSM version and which synology model you are using. But I had a similar problem when I tried to access my rfxcom on DSM 5.0 running on a synology station containing an ARMv5 processor. Apparently libNRJavaSerial does not properly support the ARMv5 processor. 

Assuming this is the same problem, you can try to get it to work by 

- retrieving the file native/linux/ARM/libNRJavaSerial_legacy.so from the OpenHAB/server/configuration/org.eclipse.osgi/bundles/203/1/.cp/lib/nrjavaserial-3.8.8.jar (if you do not know how: a .jar file is a zip file, so just open using an unzip program)    

- change the startup of OpenHAB to let libNRJavaSerial know that it should use this native library instead of the one it apparently chooses by default. Add the following to the java command in the start_*.sh scripts: -DlibNRJavaSerial.userlib=<PATH WHERE YOU PLACED THE LIB>/libNRJavaSerial_legacy.so

good luck,

 Piebe

[Vilhelm Pihlsgård]

Thank you!

I am using DSM 5 on a DS213 which is powered by an ARMv5 CPU so I will give your solution a try.

I think it's weird though, that OpenHAB starts OK when I remove the z-wave binding addon.

best regards

Vilhelm

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/f-EvJzQKl-4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Vilhelm Pihlsgård]

Thank you Piebe.
This was it!

Now I have to figure out how to get habmin to run...

[joe...@gmail.com]

Thank you for this post. I recently performed an upgrade on my 212+ Synology to DSM 5.0 update 2 and could not for the life of me get the communication from /dev/ttyUSB0 working post upgrade.

Things tried before this:

- checked Aeon Zwave stick on windows to ensure it was not a hardware issue. Checked out.

- tried a different USB port.

- played with SynoZWave package until this was completely exhausted. Uninstalled, reinstalled, manually loaded device drivers, reviewed OS logs (ie. dmesg). Everything seems to be ok from the device driver perspective. dmesg logs appeared clean and appropriate. However, I decided to compile/rebuild the usbserial.ko, ftdi_sio.ko, cp210x.ko drivers on a Suse linux VM under the DMS 5.0 Tool chains and latest source. After rebuilding and installing new drivers, openhab still failed to communicate to USB serial port.

- Finally saw your post about ARM5 and libNRJavaSerial. This ended up solving the issue. I'm not too familiar with NRJavaSerial and it's internal method of loading the native driver.

Worked on this for 8 hours trying to fix this with one failure after another. THANKS AGAIN!!!

[joe...@gmail.com]

Not sure if you are experiencing this, but here's what I see:

- On DSM 4.3, zwave connected to /dev/ttyUSB0 out of the box. No additional config needed. State of devices were accurately reflected in GreenT and all devices responded robustly.

- Upgraded to DSM 5.0 and I had to config within my startup libNRJavaSerial_legacy.so.

- Now, in GreenT the state of my zwave devices are not updating

- Now, on occasion, some of my zwave devices do not respond to command. Appears to happen often to my Somfy motor controllers for some shades I have. I've even had to restart openhab to get the device to respond to commands again.

Not sure if this legacy.so version is going to cut it. Thoughts?

[joe...@gmail.com]

btw: with all of the different things I tried before configuring legacy.so, I did rebuild the usbserial.ko, cp210x.ko and ftdi_sio.ko. Maybe I should try reverting back to the synzwave ko files?

What module .ko file versions are you using?

[joe...@gmail.com]

fyi... reverted back to synozwave driver versions. So far, so good. All the ZWave devices are reporting the correct state within GreenT.

[Vilhelm Pihlsgård]

Hello gentlemen

Can someone tell me whats wrong and how to fix it?

21:15:16.503 [ManagedService Update Queue] INFO  o.o.b.z.i.protocol.ZWaveController - Starting Z-Wave controller
21:15:16.504 [ManagedService Update Queue] INFO  o.o.b.z.i.protocol.ZWaveController - Connecting to serial port /dev/ttyUSB0
21:15:16.629 [FolderObserver] INFO  o.o.m.c.internal.ModelRepositoryImpl - Loading model 'demo.sitemap'

#
# A fatal error has been detected by the Java Runtime Environment:
#

#  SIGILL (0x4) at pc=0x4edd9b94, pid=3822, tid=1340404848
#
# JRE version: Java(TM) SE Embedded Runtime Environment (7.0_55-b13) (build 1.7.0_55-b13)
# Java VM: Java HotSpot(TM) Embedded Client VM (24.55-b03 mixed mode linux-arm )

# Problematic frame:
# C  [libNRJavaSerialv6_HF.so+0x8b94]  Java_gnu_io_RXTXCommDriver_testRead+0x1c0
#

# Core dump written. Default location: /volume1/@appstore/OpenHAB/core or core.3822

#
# An error report file with more information is saved as:

# /volume1/@appstore/OpenHAB/hs_err_pid3822.log
Segmentation fault (core dumped)
DiskStation>

--