madas
September 8, 2009, 10:03pm
1
Hello!
Got my 2412U PLC and plugged it in to Vera but I see this error at the top of the X10 Page
Insteon: Insteon Failed
There aren’t many options on the X10 Page but I have
/dev/usb/tts/1 set as the port
and dmesg from the device shows
Manufacturer: FTDI
So I think we’re correct on the port. Any ideas where next?
I’m using .899
How did you arrive at the proper (or any) string to type into the Port: field under Insteon/X10’s “More Options” pane? Why not just “1” or “USB1” or “ttyUSB1”?
Just curious.
madas
September 8, 2009, 10:40pm
3
It was already in there actually…
Have you tried switching the Insteon PLM’s USB cable to the port currently occupied by Vera’s dongle (with or without the dongle plugged back into Port 1)?
Also, have you reset/restarted Vera since plugging in the 2412U?
guessed
September 8, 2009, 10:44pm
5
The “/dev/usb/tts/1” format @madas references is the same used for other serial devices like the ZWave USB Dongle itself.
From the firmware I saw, there’s a specific driver for the X10 stuff, and it was Lua-based from memory (I can’t remote to mine right now). I’m assuming this is “pre-configured” when it auto-detects.
So… what’s logged in the Luaupnp file over in the /var/log/cmh/ directory? It might give you more insight into what’s failing.
If it doesn’t, try bumping Vera’s log level and re-connecting it.
madas
September 8, 2009, 11:19pm
6
I tried with just the PLC and no Z-Wave and it still doesn’t work. The port defined under the X10 page actually changes automatically, so it must auto detect.
I have rebooted Vera before making all hardware changes.
The LuaUPnP.log file ends up being about 140k…any easy way to get it off? or anything I can grep out?
guessed
September 8, 2009, 11:51pm
7
typically you can:
[tt] tail -f LuaUPnP.log | grep ‘^50|^01’[/tt]
while performing the activity, assuming you have a large enough scroll window or use [tt]more[/tt] to paginate (but lose the color coded output). Errors will usually come through in Bold-Red, but on one of the above error codes (“50” or “01” at the beginning of a line)
Alternatively, if you can get the Device ID allocated to the device, you can do something similar with:
[tt] tail -f LuaUPnP.log | grep “:deviceID :”
and you’ll also catch some of the lines localized for that device.
guessed
September 8, 2009, 11:51pm
8
oh, and submit a Vera ticket for it also, so that MCV can formally debug it. I’m sure they’ll know way quicker than we can reverse engineer it, but we might as well try while we wait.
madas
September 9, 2009, 12:15am
9
I did submit a ticket. They general take a few days
Here is a grep from the logs (attached too as it doesn’t view so well on here!)
root@HomeControl:/tmp/log/cmh# cat LuaUPnP.log |grep “InsteonNetwork1”#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x380f>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x380f>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1005>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0xc04>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0xc04>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x400>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1807>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1807>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1807>#hooks: 0 upnp: 1 v:(nil)/NONE duplicate:0 <0x1807>
madas
September 9, 2009, 12:21am
10
Another log grepped on Insteon
DeviceID (even with -i for case insensitive) doesn’t show much
guessed
September 9, 2009, 2:28am
11
from that last log, looks like your deviceID for the [parent] Insteon controller is 49.
It also looks, from this page:
http://wiki.micasaverde.com/index.php/Luup_Loglevels
that the Insteon Log levels are:
// Insteon starts with 6
LV_INSTEON 60
LV_SEND_INSTEON 61
LV_RECEIVE_INSTEON 62
so the grep can be changed to “^6” to find the Insteon log lines beginning with “6”.
This reminds me of how I over-eagerly clicked the “Activate Insteon” button (in .899) last week, wondering what it did … and being somewhat alarmed that there is not a “Deactivate Insteon” button.
Do you recall whether you clicked “Activate” prior to - or after - connecting the 2412U?
The PLC isn’t supported (powerline controller). You need a PLM (powerline modem). PLC uses a different protocol because it’s meant to be a stand-alone controller. PLM is simpler and should be much cheaper in the near future since it doesn’t have a built-in cpu. You want the 2412U.
You need to click ‘activate’ to enable the Insteon module before Vera will even try to find the 2412U. It also creates a new top level device. Added a mantis to add the ‘remote Insteon’ button. http://bugs.micasaverde.com/view.php?id=626
Read his original post: It’s a 2412U he’s using (a PLM).
FYI, I think MCV meant “Remove Insteon” button.
madas
September 9, 2009, 11:21am
15
Yes I have a 2412U
MCV are going to remotely connect to my vera to take a look
madas
September 9, 2009, 7:49pm
16
running a grep with ^6 doesn’t show anything i’m afraid. I’ll post when I hear something from MCV. They emailed and asked me to open access to Vera for them.