No luck, I get this error:
2015-09-24 00:58:28.043 [ERROR] [.o.b.i.i.driver.SerialIOStream] - got no such port for /dev/ttyAMA0 (Linux, with usb based PLM modem)
2015-09-24 00:58:28.055 [ERROR] [.o.b.i.InsteonPLMActiveBinding] - initialization complete, but found no ports!
could there be a permissions issue? I’m running under the pi accound and I start with sudo ./start.sh I would think that would grant all ther permissions needed, but I’m newish to linux so IDK.
Yes, could be a permission error, but when you start with “sudo …” openhab runs with root permission.
I do the same and have no problems at all.
Sorry, my knowledge about Linux ends at this point, you have to wait for more experienced users …
The first thing to establish is that you can actually connect to the FTDI device at a lower level.
I use the “cu” tool like this:
cu -l /dev/ttyUSB0
just to see if I can open the port. There are a host of other tools like this (screen etc), or you could actually just try to write to the port via
echo "foo" > /dev/ttyUSB0
Run this as sudo first, then try under the userid you want to run. You may have to set udev rules (does raspian even run udev?) to create the device under group “plugdev”, and make your user id a member of “plugdev”.
There is no point trying to run the insteonplm binding until you have established at the OS level that the device is present and working.
Once you have that going, proceed with getting rxtx/java/insteonplm working.I usually don’t have to add any magic rxtx flags into the startup script. In fact I would first try without them.
I believe on ubuntu 14.04 the package
to install is called “cu”. Don’t know about raspian.
Well, that you are not getting an error when you echo to
/dev/ttyUSB0 is a good sign.
Try
cat /dev/ttyUSB0
and watch for characters on the console, or
cat /dev/ttyUSB0 > some_file_name.txt &
and see if the filename grows. That would tell you if messages are
coming in.
You may have to flip some light switches to generate traffic.
Are there any other usb serial devices attached that could show up
under /dev/ttyUSB0?
Now try and run openhab under the same user id that you ran the
previous tests under (hopefully not root, that's insecure).
Let me know what the insteonplm debug log says.
If you have energy for it, there is another tool, more primitive
than openhab, that shares the low-level interface with the
insteonplm binding. You may want to see if you can get that one to
work:
