I just moved my openhab setup to a raspberrypi2 and I can’t for the life of me figure out why my insteon plm won’t talk to openhab
I’m assuming I’m missing a driver or something, but from what I’ve read it should have been installed with raspian out of the box,
I’m runing openhab 1.7.1, brand new installation, with just the insteonplm binding
when i run dmesg i get:
[ 146.776357] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[ 146.776859] usb 1-1.5: Detected FT232RL
[ 146.778125] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0
which I believe to be my insteonplm, so I put:
insteonplm:port_0=/dev/ttyUSB0
in my openhab.cfg
but when I start openhab I get this:
2015-09-23 21:39:02.239 [ERROR] [.o.b.i.i.driver.SerialIOStream] - got no such port for /dev/insteon (Linux, with serial port symlinked to /dev/insteon)
And I have not control of the lights, can somebody please point me in a direction that will help solve this problem?
Sorry the error i get is:
2015-09-23 21:43:39.267 [ERROR] [.o.b.i.i.driver.SerialIOStream] - got no such port for /dev/ttyUSB0 (Linux, with usb based PLM modem)
2015-09-23 21:43:39.269 [ERROR] [.o.b.i.InsteonPLMActiveBinding] - initialization complete, but found no ports!
I had tried another configuration and didn’t realize I had left it.
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.
