02-10-2017, 07:53 AM
(10-20-2016, 02:52 PM)marcosti wrote: Wrote: Okay, I've figured it out, thanks for all your suggestions!!
The way I managed to have the bus Z-Wave working is doing the following:
1. Create the file /etc/udev/rules.d/10-tty.rules, and add the following (copy the complete line, including the quotes and all);
KERNEL=="ttyS2", SYMLINK+="ttyACM0"
This will make sure that every time you reboot your Pine64, the symbolic link is re-established under the /dev-directory. This is needed since all entries in the /dev-directory are recreated on each boot. So, instead of manually creating a symbolic link each time after the Pine64 boots up, have the udev-rules take care of that for you!
2. make sure that you use beta-releases of Domoticz (under Setup->Settings). Otherwise you will not have the option to select 'OpenZWave USB'.
3. reboot your Pine64, and go to Setup-Hardware and register an OpenZWave USB component, using port '/dev/ttyACM0'
That's it, this enables your bus ZWave module.
Hi,
From the above, I got the impression Domoticz requires the device as /dev/ttyACM0.
I had an issue there, as I have a real serial USB device (RFlink on Arduino Mega) and the Ubuntu USB driver wants to give it device name /dev/ttyACM0
And you can't have 2 devices with same name.
Effectively, the link got overwritten when I connected the RFlink, disabling the communication with the Zwave device
After a bit of fiddling and looking through the Domoticz code to see where the hard code /dev/ttyACM0 was, I found that Domoticz actually does NOT require the name to be /dev/ttyACM0 at all. Anything starting with /dev/ttyACM will be accepted.
So I changed the file /etc/udev/rules.d/10-tty.rules into:
KERNEL=="ttyS2", SYMLINK+="ttyACMZwave"
Now I have BOTH the RFlink (running at real /dev/ttyACM0 port) and the Zwave module (running via symlink device /dev/ttyACMZwave) side by side.
This will not create a conflict, as the ubuntu driver adds numbers behind the /dev/ttyACM name
Might be of help to others...