Insteon How-To?

[twodogs]

I bought my Insteon 2412S modem and I've replaced the porch light switch with a 2476S. I've scoured everything I can find on how to get LMCE to recognize and control the porch light and I'm out of ideas.

There is a wiki on setting up a new template, but this seems outdated.

http://wiki.linuxmce.org/index.php/Setting_Up_PLM_Template

When I try to follow the instructions I see that there are already templates. Actually 2 templates: "Insteon PLM" seems to have plug/play info but no ruby code, "Insteon PLM DCE" seems to have ruby code but no plug/play. I tried the "PLM DCE" and as soon as I selected the template, Sarah came up and started loading software. Then it tried a DCE reload and hung while trying to generate the still incomplete Insteon device - I hadn't even had a chance to select the serial port yet.

I looked at this wiki but it seems Insteon is already installed.

http://wiki.linuxmce.org/index.php/Running_the_Insteon_PLM_Driver_for_the_First_Time

I would love a good shove in the right direction. What are the first steps? Which is the best template? Do I try to link the modem and light switch before or after setting things up in LMCE?

[Aviator]

I've just ordered a 2413s PLM which is similar. I should have it within a week. Maybe we can work together to get these working and then update the documentation?

Regards,
Michael

[twodogs]

Count me in. The setup info is probably in the wiki somewhere. With both of us looking, we're bound to find it.

[twodogs]

I'm making progress. I think I've created the PLM device. Events are showing up in the Pluto log. The LED is blinking on the 2412S modem. I also see that a lighting device was created but I have an on/off switch and the template is for a dimmer. So the only light that I can control is the LED on the modem. At least I'm closer. When I succeed I'll write a wiki how-to. Does anyone know if there is a tutorial on how to properly install a Generic Serial Device for which a template has already been written?

John

[tschak909]

somebody really needs to make the Insteon device a C++ device... I thought all of this was checked into the database and made PNP years ago...

-Thom

[twodogs]

Here is what I've done so far.
1. Replace the old wall switch with the 2476S switch
2. Plugged the 2412S modem into the wall and connected the serial cable into the Core.
3. Open the Admin page
4. Wizard > Devices > Generic Serial Device
5. Add Device
6. Pick device template 1932 (Insteon PLM)


7. Software begins to download, then the "finished" message appears telling me to restart router.


8. Go back to admin page, select device, and see errors


9. Go into advanced tab and select controlled via Core, serial port ttyS0, save, restart router.
10. No workee. "Send command to device" reports fail. GSD log does not exist in Pluto folder.
11. Reboot computer and see more software download (rubytlk or some such). Now I can send commands to the device, the GSD log exists, and the LED on the modem begins to flash. But I still can't control the light. Below, for your viewing pleasure, is the tail end of the log (after the 2600 lines of start code).

Code: [Select]

2601:end
2603:(***):MY DEVICE:38
(***):SndIns:Queue:1
(***):out:02 6B 40 Length:3
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:2
(***):Finding Children..
(***):reading stored Child configuration:
(***):********************************************************
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:2
(***):IN:02 6B 40 06 Length:4
(***):SetCfg Completed
(***):Command Completed.
(***):SndIns:Queue:1
(***):out:02 69 Length:2
(***):IN:02 69 06 02 57 E2 01 0A 97 0B 01 01 FF Length:13
(***):GetLnk ACKED
(***):LnkData Message Received
(***):{"Parameter2"=>"57", "Parameter3"=>"E2", "Parameter4"=>"01", "Parameter5"=>"0A", "Parameter6"=>"97", "Parameter7"=>"0B", "Response"=>"LnkData", "Parameter8"=>"01", "Parameter9"=>"01", "Parameter10"=>"FF", "Parameter1"=>"02"}
(***):record Flags:E2
(***):Controller
(***):Insteon ID:0A.97.0B, Group:01
(***):Command Completed.
(***):SndIns:Queue:1
(***):out:02 6A Length:2
(***):IN:02 6A 15 Length:3
(***):sendGetNext NACKED
(***):Command Completed.
(***):Entered CheckChildRecordsinPLM
(***):Record: = 0A.97.0B Group:01
(***):checking to see if it needs to be added as a child...
(***):ExistsinChild:InsteonID:0A.97.0B
(***):ExistsinChild result:FALSE
(***):0A.97.0B needs to be added to the child database
(***):addtochild Routne called
(***):Adding 0A.97.0B to the child database...
(***):Child is Insteon
(***):PING Sent!
(***):0A.97.0B exists in PLM
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:1
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:1
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):Command Completed.
(***):Queue Empty.
(***):RERUN=TRUE, RESTARTING
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):X-----------SndIns: Waiting for response to:SndIns
(***):X-----------SndIns: Current Queue Length:1
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:25
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:25
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):Command Completed.
(***):Queue Empty.
(***):RERUN Not needed
(***):Reporting Child Devices
(***):Child:0A.97.0B
(***):Config:["****************"]
(***):0A.97.0B
This seems like progress to me, but I don't know what comes next. I think I have to push and hold the modem reset for 10 seconds, then go do the same on the light switch. The LEDs blinked but not much else happened. How do I tell LMCE that there is a light to control?

[twodogs]

Bump?

[Michaelree]

I believe all you have left to do is to cross link the devises to the PLM.  When linking devices manual the first device that you put into linking mode will be the controller and the seconded device will be the responder.  For example to cross link a device you will go to the PLM and hold the set button for 10 sec until it starts blinking and then go to the light switch, for a switch link dimmer you hold paddle on for 10 sec, the dimmer should beep, and the light on the PLM should also have stopped blinking. you then have to repeat this process but put the light switch into linking mode first, and then put the PLM into linking mode.  This makes will make the two devices cross linked.  after you link all your devices this way reload the router and watch the log file wait till it is done doing everything and then look below the Config:["*****"] line everything listed below that line are the device ID's of all the devices that are now part of your system, and should have been added as children, you will need to reload your router one more time.  That should do it.

[twodogs]

I can't wait to try it. Fingers crossed. Thank you.

John

[twodogs]

Still no luck. I push/hold the PLM reset and it blinks. I push/hold the light switch and it beeps once and begins to blink. The PLM and light switch continue blinking for about 4 minutes. Does this mean the link is not established? I tried reversing the order and doing the light switch, then the PLM but the result was the same. The Insteon components did not come with detailed instructions, and I could not find anything on the website. I am completely mystified how anyone can get Insteon working with LinuxMCE. Here is the log.

Code: [Select]

2603:(***):MY DEVICE:38
(***):SndIns:Queue:1
(***):out:02 6B 40 Length:3
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:2
(***):Finding Children..
(***):reading stored Child configuration:
(***):********************************************************
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:2
(***):IN:02 6B 40 06 Length:4
(***):SetCfg Completed
(***):Command Completed.
(***):SndIns:Queue:1
(***):out:02 69 Length:2
(***):IN:02 69 06 02 57 E2 01 0A 97 0B 01 01 FF Length:13
(***):GetLnk ACKED
(***):LnkData Message Received
(***):{"Parameter2"=>"57", "Parameter3"=>"E2", "Parameter4"=>"01", "Parameter5"=>"0A", "Parameter6"=>"97", "Parameter7"=>"0B", "Response"=>"LnkData", "Parameter8"=>"01", "Parameter9"=>"01", "Parameter10"=>"FF", "Parameter1"=>"02"}
(***):record Flags:E2
(***):Controller
(***):Insteon ID:0A.97.0B, Group:01
(***):Command Completed.
(***):SndIns:Queue:1
(***):out:02 6A Length:2
(***):IN:02 6A 15 Length:3
(***):sendGetNext NACKED
(***):Command Completed.
(***):Entered CheckChildRecordsinPLM
(***):Record: = 0A.97.0B Group:01
(***):checking to see if it needs to be added as a child...
(***):ExistsinChild:InsteonID:0A.97.0B
(***):ExistsinChild result:FALSE
(***):0A.97.0B needs to be added to the child database
(***):addtochild Routne called
(***):Adding 0A.97.0B to the child database...
(***):Child is Insteon
(***):PING Sent!
(***):0A.97.0B exists in PLM
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:1
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:1
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 10 00 Length:8
(***):IN:02 62 0A 97 0B 0F 10 00 06 Length:9
(***):Got PING ACK
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):Command Completed.
(***):Queue Empty.
(***):RERUN=TRUE, RESTARTING
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):X-----------SndIns: Waiting for response to:SndIns
(***):X-----------SndIns: Current Queue Length:1
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:25
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:25
(***):SndIns:Queue:1
(***):out:02 62 0A 97 0B 0F 19 00 Length:8
(***):IN:02 62 0A 97 0B 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):Command Completed.
(***):Queue Empty.
(***):RERUN Not needed
(***):Reporting Child Devices
(***):Child:0A.97.0B
(***):Config:["****************"]
(***):0A.97.0B
05 04/09/11 8:26:09.986 Socket::ReceiveData 0x96665a8 failed, bytes left 0 start: 1890000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 8 Command_Impl1 Dev #38 <0xb57fbb90>
05 04/09/11 8:26:09.986 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #38 <0xb57fbb90>
01 04/09/11 8:26:09.986 Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #38 <0xb57fbb90>
05 04/09/11 8:26:09.986 Dumping 1 locks <0xb57fbb90>
05 04/09/11 8:26:09.986 finished check for exceptions <0xb57fbb90>
05 04/09/11 8:26:09.986 OL: (0x96666f4) (>75) MessageQueue Command_Impl.cpp l:822 time: 5:00:00p (1302359169 s) thread: 3053439888 Rel: Y Got: Y <0xb57fbb90>
== ATTEMPT FRESH START ==
1 04/09/11 08:28:47 /usr/pluto/bin/Spawn_Device.sh 38 (spawning-device) 15098 Dev: 38; Already Running list: 15,16,18,19,29,30,
== FRESH START ==
1 04/09/11 08:28:47 /usr/pluto/bin/Spawn_Device.sh 38 (spawning-device) device: 38 ip: localhost cmd_line: Generic_Serial_Device
0 04/09/11 08:28:48 38 (spawning-device) Entering 38
========== NEW LOG SECTION ==========
1 04/09/11 08:28:48 38 (spawning-device) Starting... 1
1 04/09/11 08:28:48 38 (spawning-device) Found /usr/pluto/bin/Generic_Serial_Device
RCODE:
   0:require 'Ruby_Generic_Serial_Device'

[Michaelree]

If the lights do not stop blinking then a link was not created.  I think you have a problem with the devices not being able to communicate and not with linuxmce.  Is the PLM and the device on the same power phase?  Do you have a phase coupler?  For Insteon to work for the hole house you have to have at least 2 wired devices that are also capable of wireless transmission one installed on each phase, or a phase coupler.  You can test this by using an extension cord to power the PLM from the same circuit as one of the devices is on and try linking it that way.

[twodogs]

Still no luck. I thought Insteon used both RF and power line to transmit commands so I took not special pains to install on the same phase. As it turns out, the modem was on the opposite phase. I used an extension cord to correct that, but still can not establish a link. I tried to reset both devices to factory (for switch: push/hold 10 seconds till it blinks, then do it again; for PLM unplug for 10 seconds, then plug in while holding button for 3 seconds). Then I retried the linking procedure with no luck.

The PLM comes with a 1-page quick start guide that is basically the home automation equivalent of the flight attendant brief "here's how to fasten your lap belt".

Does the 2412S PLM have a (insert strong expletive here) proper manual? The virtual swearing is directed at Smarthome, not you Michaelree - I greatly appreciate your help.

John

[Michaelree]

For switches, at least the ones I have to, factory reset them you have to pull out the little button right below the paddle for like 10 sec and then push it in and hold it for 3 sec.  If I remember correctly.  Not all of the devices do both wired and wireless, you just have to look and see what you have.  There use to be a manual for the PLM, but I can't seem to find it online anymore.  I would call smarthome the customer support is not all that bad.  The receiver/transmitter in the PLM is not as strong as the ones in other devises, I ran into this when I only had a few Insteon devises.  Also from what I have read, CFL can cause a lot of interference if they are low cost, same with ceiling fans.  I do have a few eco Dimmable LED bulbs and they seem to work great.  What is the device you are trying to link with the PLM?

[twodogs]

So far all I'm doing is trying to get the 2412S PLM to talk to the 2476S (hooked up to 3 CFLs in the back porch roof). First step is to get the lights working with MCE, then I'll add a few more devices and create some scenarios. The switch does have a pull-out button that I can mess with. I'll call customer support tomorrow and see if they can help. Is there a correct order to doing all of this? So far the sequence I've tried is...
1. install 2476S switch
2. plug in the 2412S PLM and connect to LMCE with RS232
3. Add the PLM device in LMCE
4. Try to link the PLM and switch

John

[Michaelree]

I would go with this order
1. Install the 2476S
2. Plug in the 2412S PLM
3. Cross link the PLM and the switch
4. Connect to LMCE with RS232, and add the PLM device in LMCE
For some reason I thought that Ddamron has stated someplace that you have to have at lest on link created before you add the PLM to the system.