How to make Vera recognize your USB-to-Serial Adapter

[quote=“michaelk, post:20, topic:164602”]
I’'l add it to the wiki- but wanted to let the powers that be know that the this 4-port model comes up fine to be configured by the vera UI.

http://www.mcmelectronics.com/product/83-10137

I happened to have it floating around from my old homeseer system also.

just plugged it in.

I saw a post that the to kick things over have to hit save or reboot. SO I hit save. Vera took loingerthan usual to come back. when it came back up i went into serial configuration and all looks well.[/quote]

or maybr not… not sure if it is working . I can’t get my 2414s insteon cottoller to work with i…

I’ll fight some more later. Going to bed…

so searched and read some more here that the 2414 is not supported currently by vera. So I dont really know if the usb-> 4-port serial adapter is in fact working as I dont have a serial device that will work with vera to confirm.

But it seems to show up properly and vera lets me fiddle with the various values.

for those interested- I can confirm the 4-port model above works fine.

(broke down and bought a 2412s to play with it)

Hey (sarcasm mode = ON), let me know when things get simpler, and I can “Just plug the USB-to-Serial cable/adapter in, and Vera will recognize it.” (sarcasm mode = STANDBY)

The moment someone starts in with “Go to the Linux command line and type (insert several lines of meaningless Mandarin Chinese here)…” my eyes glaze over and I feel violated.

Vera is always connected device, there’s no reason for it not to ask a repository at findvera what to do with this specific adapter, and download whatever script reqired…

I keep promising myself I will try again, but frankly got SO frustrated trying to make X10 work with Vera (my primary aim when I bought her!) that I’ve given up. Now, Vera just turns on a lamp, sets my thermostat temperatures, and manages my Schlage lock.
Period. All else has been put on hold until I feel the X10 issue has been resolved.

It might be easier to upgrade from X10 then…

Vera2 1.1.1047

Has the install of USB → Serial adapters moved on?

I have a cable which reports in Windows as Vendor 0x403 Product 0x6010 (FT2232H)

I have followed the instructions for rmmod -f ftdi_sio and insmod 0x403 0x6010 but don’t get anything useful in dmesg and nothing in the Dashboard.

Correction: I can now see the device attached with the 232BM driver but still nothing in the MiosDevelopers / Serial Configuration of the dashboard.

“IF YOU FIND THAT THIS IS WORKING FOR YOUR ADAPTER PLEASE PASTE ON THIS THREAD IT’S KERNEL MODULE, VENDOR AND PRODUCT CODE SO I COULD ADD THEM BY DEFAULT IN THE FIRMWARE.”
[/quote]

Hi CJ,

I just want to have your advise:
I want to use the zwave.me (http://en.z-wave.me) service both with my vera2.
For that, I need to use a little prg downloaded from zwave.me (=z-connector package) to autorize communication between my zwave network and the zwave prg “zwave.me” runing on the cloud. This also need to use a zwave antenna like AEON LABS z-stick (or even integrated zwave antenna from vera2?).
I’m not programmer and I really need some help to do that or even just to know if it’s possible. I want to join the package so that you can check it but I can’t do that on this post. The package is available on http://en.z-wave.me and really light to download.
Could you please give me 5 min and check that?
I’ll really be grateful.

Thank you,

sebastian

I have a device with a cp210x chipset. Serial communication works partly. I can receive data but I am unable to send data. Anyone an idea what this might be?

I added the line “vendor:10c4 product:ea60” to serproxy.ports and it is recognised in UI4.

0: module:cp210x name:“CP210X” vendor:10c4 product:ea60 num_ports:1 port:1 path:usb-00:03.0-1.1
1: module:pl2303 name:“PL-2303” vendor:067b product:2303 num_ports:1 port:1 path:usb-00:03.0-1.2.2
2: module:pl2303 name:“PL-2303” vendor:067b product:2303 num_ports:1 port:1 path:usb-00:03.0-1.2.4

Switched to an FTDI USB chip which now works both directions. I could not get the cp210x to work (could receive but not send data from vera). I am quite convinced the issue is with the cp210x driver on vera. If anyone has a hint how to fix this please let me know.

0: module:ftdi_sio name:“FTDI FT232BM Compatible” vendor:0403 product:6001 num_ports:1 port:1 path:usb-00:03.0-1.1
1: module:pl2303 name:“PL-2303” vendor:067b product:2303 num_ports:1 port:1 path:usb-00:03.0-1.2.2
2: module:pl2303 name:“PL-2303” vendor:067b product:2303 num_ports:1 port:1 path:usb-00:03.0-1.2.4

0: module:cp210x name:“CP210X” vendor:10c4 product:ea60 num_ports:1 port:1 path:usb-00:03.0-1.1
→ Can be made to work partly by editing serproxy.ports (receiving data but not sending).

0: module:ftdi_sio name:“FTDI FT232BM Compatible” vendor:0403 product:6001 num_ports:1 port:1 path:usb-00:03.0-1.1
→ Can be made to work by editing serproxy.ports (receiving data but not sending). Works reliably (so far) on 9600. With a speed of 115200 it stopped working after a while (all serial ports in the system then stop and no data is sent or received).

Seems to me the whole serproxy thing on vera2 is not very reliable. Is this just my experience (picking the two worst possible usb chips) or is that a general known issue (maybe it is fixed on newer vera systems with a fresh wrt version).

device : usb-rt3883-ohci-1
chipset/name : pl2303 / prolific 2303 usb<>rs232 bridge
running on port 3481

seems to work , have nothing to test it on as there is no rs232 plugin for my samsung tv (syncmaster 400p)
i have the codes for it though, so if anyone willing to cut n paste the data into plugin for the panasonic tv , it would be greatly appreciated. i have no time look at it myself for the comming month or so :frowning:

i was thinking… maybe someone can make a virtual rs232 device on the pc which communicates with the vera so the vera can show the pc stats hd usage/fan/temps etc ? wouldnt that be cool :slight_smile:

I have a Prolific PL2303 and would like to get it working.

This thread is difficult to follow… where are the instructions for a linux noobie (that can use command line, putty, etc) on how to get it running?

thx!

@Aaron,
CJ’s post that started this thread is an accurate list of the commands to run, and the output to provide. If you post the output, that he’s referencing in that first post, to this thread then I’m sure someone will assist.

[quote=“guessed, post:35, topic:164602”]@Aaron,
CJ’s post that started this thread is an accurate list of the commands to run, and the output to provide. If you post the output, that he’s referencing in that first post, to this thread then I’m sure someone will assist.[/quote]

after looking around it seems that the Vera with UI5 recognized the adapter I put on… I just needed to tell it to use that as the Insteon interface and it started reading the devices on my PLM. Pretty cool

Guys,

you’re lucky, I am in UI5 and no more serproxy.port file.

But, it sees my both usb serial (all after reboot of course)

root@MiOS_xxxxxxx:/# l /dev/tty* crw-rw-rw- 1 root root 5, 0 Jan 1 1970 /dev/tty crw-rw-rw- 1 root root 4, 64 Jun 19 01:40 /dev/ttyS0 crw-rw-rw- 1 root root 4, 65 Jan 1 1970 /dev/ttyS1 crw-rw-rw- 1 root root 188, 0 Jun 19 01:01 /dev/ttyUSB0 crw-rw-rw- 1 root root 188, 1 Jun 19 01:01 /dev/ttyUSB1 root@MiOS_35101944:/#

and

root@MiOS_xxxxxx:/proc/tty/driver# cat usbserial usbserinfo:1.0 driver:2.0 0: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0403 product:6001 num_ports:1 port:1 path:usb-rt3883-ohci-1.1 1: module:cp210x name:"cp210x" vendor:10c4 product:ea60 num_ports:1 port:1 path:usb-rt3883-ohci-1.3 root@MiOS_35101944:/proc/tty/driver#

Ok, both are here but none in UI5, just my old pl2303 (prolific) is present.

Anyone can explain this or more have a solution to see my 2 usb serial in UI5 ?

Thank you for your help.

Well,

Guessed saved my life in this post (needed to manually create the file serproxy.ports)

http://forum.micasaverde.com/index.php/topic,10817.0.html

really thanks to him

By the way, anyone knows what is the use for the field “path” in serial port configuration ?
I think the device number field is used to be sure to identify the same device after reboot ? Is that correct ?

just got a vera lite and sq blaster and got all of that set up with no problems. now i’d like to interface my alarm via usb->serial adapter (belkin F5U409). I didn’t see the belkin on the supported devices page but thought id give it a try anyways. This is my first attempt at ssh into vera and all seems to be well. this is what i get when i run the commands

“usb 2-1: USB disconnect, address 2
mct_u232 ttyUSB0: MCT U232 converter now disconnected from ttyUSB0
mct_u232 2-1:1.0: device disconnected
+usb 2-1: new full speed USB device using rt3883-ohci and address 3
+mct_u232 2-1:1.0: MCT U232 converter detected
+usb 2-1: MCT U232 converter now attached to ttyUSB0”

after checking back on UI5 i still have “not available” listed under Serial Port Config tab

is the adapter just not supported or did i need to do something with a “serproxy.ports” file

any help would be appreciated!

don key,

You didn’t say that you rebooted the Vera between here

[quote=“don key, post:39, topic:164602”]+usb 2-1: new full speed USB device using rt3883-ohci and address 3
+mct_u232 2-1:1.0: MCT U232 converter detected
+usb 2-1: MCT U232 converter now attached to ttyUSB0"[/quote]

and here

after checking back on UI5 i still have "not available" listed under Serial Port Config tab

so I’m assuming that you didn’t. Do that. Tell us how you go.

Edit: If that doesn’t make any difference, you need to find out what the vendor and product ids are. run “lsusb” with the device unplugged, then again with it connected. The new line is the one you need. You can try feeding this into the /etc/cmh/serproxy.conf file, creating the file if necessary.

(Disclaimer: I haven’t ever done this; I’m just going by the posts I’ve read.)