enocean binding on Synology DS213+ (kernel driver package)

[die...@hofrichter.at]

The enocean binding works with the enocean USB300 usb-stick.
To enable the USB300 on an Synology DS213+ two things are needed:

1. The kernel drivers:

• usbserial, ftdi_sio and cdc-acm are already included in DSM 4.3
• pl2303 and cp210x are in the attached usb-driver-kernel-2.6.32-dh-syno-qoriq-0.001.spk - you can install this package in DSM via the package manager -> manual installation

2. nrjavaserial

• OpenHab comes with the latest stable version of nrjavaserial 3.8.8 (at the moment (17.11.2013)). It's in {openhab_root}/server/plugins/org.openhab.io.transport.serial
  The newer unstable nrjavaserial 3.9.1 is needed for the qoric cpu of the DS213+
  This version is included in the (otherwise unchanged) attached usb-driver-kernel-2.6.32-dh-syno-qoriq-0.001.spk. Just put the attached file in {openhab_root}/server/plugins/ and delete the original file {openhab_root}/server/plugins/org.openhab.io.transport.serial...

[Kai Kreuzer]

Dieter,

This sounds really great! Before this valuable information is lost, I think it would be a good idea to add it to the Tips&Tricks section in the wiki: https://github.com/openhab/openhab/wiki/Samples-Tricks. What do you think?

Regards,

Kai

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.
<usb-driver-kernel-2.6.32-dh-syno-qoriq-0.001.spk>

[Dieter Hofrichter]

The file org.openhab.io.transport.serial_1.3.1.201309182025.jar was not uploaded... I added it now as a .zip file

The enocean binding works with the enocean USB300 usb-stick.
To enable the USB300 on an Synology DS213+ two things are needed:

1. The kernel drivers:

• usbserial, ftdi_sio and cdc-acm are already included in DSM 4.3
• pl2303 and cp210x are in the attached usb-driver-kernel-2.6.32-dh-syno-qoriq-0.001.spk - you can install this package in DSM via the package manager -> manual installation

2. nrjavaserial

• OpenHab comes with the latest stable version of nrjavaserial 3.8.8 (at the moment (17.11.2013)). It's in {openhab_root}/server/plugins/org.openhab.io.transport.serial
  The newer unstable nrjavaserial 3.9.1 is needed for the qoric cpu of the DS213+
  

• This version is included in the (otherwise unchanged) attached  org.openhab.io.transport.serial_1.3.1.201309182025.jar. Just unzip and put the attached file in {openhab_root}/server/plugins/ and delete the original file {openhab_root}/server/plugins/org.openhab.io.transport.serial...

[Dieter Hofrichter]

thank you!

done -  this valuable information is now at https://github.com/openhab/openhab/wiki/Samples-Tricks#enocean-binding-on-synology-ds213-kernel-driver-package ;-)

[Kai Kreuzer]

Thanks!

[peter.k...@gmail.com]

I'm trying to get an Aeon Z-Wave stick working on my Synology DS213+ and I think I'm getting close. I followed the instructions regarding driver specific for the Synology, but I'm a bit puzzled by the sheer amount of USB devices that the Synology reports. On 'normal' Lunix boxes it's rather easy to know which port the USB stick is connected to, usually /dev/ttyUSB0 or something. However, on the Synology I see 8 USB ports (/dev/ttyUSB0 to /dev/ttyUSB7) plus a separate directoty called 'usb' with yet another set of devices.

Is there a way to determine which of all those listed devices is actually the one the USB Z0-Wave stick is connected to?

Thanks,

Peter

Op zondag 17 november 2013 22:47:23 UTC+1 schreef Dieter Hofrichter:

[Dieter Hofrichter]

Dear Peter, on the command line

dmesg |grep ttyUSB

does the trick for me...

DiskStation213> dmesg |grep ttyUSB
[   91.011273] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
DiskStation213>

[Thomas Eichstädt-Engelen]

thanks, Dieter!

[peter.k...@gmail.com]

Hi Dieter,

Thanks for the info. 

In my case it gave the following response.

DS_Syn213> dmesg |grep ttyUSB
[ 89.715832] usb 2-3: cp210x converter now attached to ttyUSB0
DS_Syn213>

I configged the zwave details in the openhab.cfg file and restarted.

22:02:43.294 INFO o.o.c.internal.CoreActivator[:92]- openHAB runtime has been started (v1.3.1).

22:02:51.758 INFO o.o.i.s.i.DiscoveryServiceImpl[:92]- mDNS service has been started

22:02:56.385 INFO o.o.i.r.i.RESTApplication[:158]- Started REST API at /rest

22:03:02.269 INFO o.o.u.w.i.s.WebAppServlet[:99]- Started Classic UI at /openhab.app

22:03:07.639 INFO o.o.b.z.i.ZWaveActiveBinding[:379]- Update config, port = /dev/ttyUSB0

22:03:07.645 INFO o.o.c.s.AbstractActiveService[:189]- ZWave Refresh Service has been started

22:03:07.723 INFO o.o.b.z.i.p.ZWaveController[:128]- Starting Z-Wave controller

22:03:07.724 INFO o.o.b.z.i.p.ZWaveController[:627]- Connecting to serial port /dev/ttyUSB0

22:03:07.855 ERROR o.o.b.z.i.p.ZWaveController[:642]- null

22:03:17.646 INFO o.o.c.s.AbstractActiveService[:201]- ZWave Refresh Service has been shut down

In short, close but no sigar. I'm open for any suggestions on how to get it working.

Cheers,

Peter

Op woensdag 11 december 2013 12:27:10 UTC+1 schreef Dieter Hofrichter:

[Dieter Hofrichter]

Dear Peter,

I don't own any zwave device - so I can't help too much here. If you
already have installed the latest nrjavaserial as described in the
other post you could still start OpenHAB with more debugging
output...(a start script should be in /var/packages/openhab/target/)

Have fun!

[peter.k...@gmail.com]

And somehow it now works! I was prepared to dig into this issue and spend many hours on it, but when I start OpenHAB via the command line, either normal or debug, it works. I get a proper report of the nodes that are associated with the Aeon Z-Wave stick. I'll proceed, although I'm wondering what the difference is between start/stop via the Package Center in DSM and doing it on the command line. Maybe a privileges thing, as command line is being done as root.

Cheers,

Peter

Op woensdag 11 december 2013 23:42:16 UTC+1 schreef Dieter Hofrichter: