My forum

I plugged Tellstick duo in and lsusb:
Bus 002 Device 014: ID 1781:0c31 Multiple Vendors

And udev.sh will do like this:
/usr/local/sbin/tdadmin controller connect --pid=0c31 --vid=1781 --serial=XYZ1234212

but no /dev/ttyUSBx will found after that

Tellstick software:
http://svn.telldus.se/telldus/trunk/telldus-core
Checked out revision 1793.

What could be the problem??

I found from syslog..
udevd-work[581]: '/sbin/modprobe' (stderr) 'FATAL: Module usb:v1781p0C31d0600dc00dsc00dp00icFFiscFFipFF not found.'

??

The older Tellstick is working perfect.

I installed this Duo to Windows XP and it's working ok, so something wrong with my linux conf, and can't understand what part I am missing.

You are not supposed to have anything under /dev/ for a TellStick Duo. We use libftdi instead of ftdi_sio in 2.1.

Not working .. I compiled with libftdi and .. .. missing the module usb:v1781p0C31d ...

from syslog:
udevd-work[5604]: '/sbin/modprobe' (stderr) 'FATAL: Module usb:v1781p0C31d0600dc00dsc00dp00icFFiscFFipFF not found.'

and rfcmd .. rfcmd LIBUSB NEXA E 2 1
usb - open error: device not found. Is it busy?

With tdtool I got the unit working.

But now I have question, where from I can read signals?

Is there way to have some serial under /dev/ ? Some old beta software maybe? I would like to read/write by that way.

rfcmd is depricated and removed in 2.1.

You can of course patch the kernel and modify rfcmd for this if you want but this is unsupported by Telldus

I am trying to handle with tdtool or so, but if I watch the content of /tmp of files TelldusEvents and Client .. they are just zero lengths, .. what's happening, I don't understand.

The sockets in /tmp are for internal use only.

If you want to listen for events you must use our API.

Here is an easy python example:
http://developer.telldus.com/browser/tr ... llbacks.py

I almost got working the duo under /dev.. I used old telldus-core, version 2.0.103 .. but I have little problem.. the duo will found under /dev if I have the old tellstick plugged in, if I take it away, the new one will not found under /dev

I just compared lsmods and did not notice any difference, little lost about this.

If you want to use rfcmd and a serial under /dev with TellStick Duo you cannot use telldus-core. It will not work without patching.

For rfcmd and TellStick Duo this must be done:
ftdi_sio must find VID: 0x1781 and PID: 0x0C31 (TellStick is PID: 0x0C30). This can be done either patching the code or sending this as command line arguments.
rfcmd must be changed to talk using the baudrate 9600 instead of 4800.

It's working!
And not working anymore.

I think I have some problems with modprobing in boot. Maybe.

I added some script for boot to modprobing the device. Now it's working and I have serial device under /dev, so I can easily read and write that. Just using bash-script for receiving and sending signals. So nice and simple!