LinuxMCE - User contributions [en]

Insteon - Setting Up PLM Template

2008-08-10T01:49:32Z

Williammanda: /* Adding Ruby Code */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
'''UPDATE''' I had to remove the ruby code from 141 & 161. The PLM wouldn't start due to errors from these two. 8/9/08 williammanda

===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on. '''UPDATE''' I didn't see any "COM PORT ON PC" field. You wil need to reload the router first, then you see the "COM PORT ON PC" field. 8/9/08 Williammanda
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T01:49:08Z

Williammanda: /* Adding Ruby Code */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
'''UPDATE''' I had to remove the ruby code for 141 & 161. The PLM wouldn't start due to errors from these two. 8/9/08 williammanda

===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on. '''UPDATE''' I didn't see any "COM PORT ON PC" field. You wil need to reload the router first, then you see the "COM PORT ON PC" field. 8/9/08 Williammanda
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T00:16:28Z

Williammanda: /* Setting up the Generic Serial Device */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on. '''UPDATE''' I didn't see any "COM PORT ON PC" field. You wil need to reload the router first, then you see the "COM PORT ON PC" field. 8/9/08 Williammanda
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T00:11:16Z

Williammanda: /* Setting up the Generic Serial Device */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on. '''UPDATE''' I didn't see any "COM PORT ON PC"
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T00:07:52Z

Williammanda: /* Making the Driver Plug & Play */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on.
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T00:07:14Z

Williammanda: /* Making the Driver Plug & Play */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command Kate /usr/pluto/pnp/88_InsteonPLM.sh missing "/" after pnp. Williammanda
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on.
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Insteon - Setting Up PLM Template

2008-08-10T00:06:39Z

Williammanda: /* Making the Driver Plug & Play */

[[Category:Tutorials]]
[[Category:Power Line Control]]
[[Category:GSD| ]]
{| align="right"
| __TOC__
|}

:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron

Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver complete, and is in Release Candidate 1. I'm sure there are still a few bugs (although we've ironed most of them out now). The more people testing this code, the more bugs we can find, and get this to a release state. Once it's in release state, it will be added to sqlcvs and offered via a 'quick' update.

==Supported Devices==
This driver supports ONLY the Powerlinc Modem model (PLM)#2412S. The code will NOT work for a model #2414 also known as a Powerlinc CONTROLLER (PLC).

NOTE: I am expecting a PLC to arrive in the mail in the next few days. Support for that device will be sooner than later.

Simplehomenet's EZBridge/EZServ products will be added once this code is stable. These products are a 'wrapper' for the PLM, and hence, use the same code. Integration will be a matter of adding the 'wrapper' code. (which is done)

==Setting up the Template==
* Goto [[LinuxMCE Admin Website]]-->Wizard-->Devices-->Interfaces
* Add device-->Add Manufacturer
* type 'Smarthome' (and click Add)
*Click Close

===Adding a New Template===
:*Press F5 to refresh the page.
:*In the Manufacturer field, select 'Smarthome'.
:*Under Device Category, select 'Lighting Interface <-- Interfaces'.
:*Add device Template
:* select the LAST option:

<nowiki>"It's a simple, generic serial device controlled by RS232, Ethernet or USB, which you'll control with Pluto's GSD and embedded Ruby snippets (very easy). Examples: Lighting control, alarm panels, surveillance cameras, thermostats, weather stations, a/v equipment with RS232 ports, etc"</nowiki>

:* Type in 'Insteon PLM' in the name or model#.
:* Click Add
There will not be a confirmation screen, instead the page will be blank
:* Close the Add device Template window.

===modifying the new Template===
* In Webadmin, Select Advanced, Configuration, Device Templates (from the top menu)
* In the Device Template field, select 'Insteon PLM'
* click 'Pick Device Template' (loads Edit Device Template Popup)
:* NOTE the Template Number! write this down. (it will be needed for Plug N Play)
:* Make sure 'Implements DCE' is checked (should be)
:* In the Comm Method, select RS232
===Adding a Code Group===
:* Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)
::* In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
::* click 'Create new group'

----
b4 is broken have to run sql manually to add new group
close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and
note '''Device_Category''' and '''Manufacturer''' you will need to set them in sql code below

''INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES ('''Device_Category''','''Manufacturer''',"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);''

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'
----

::* If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
::* Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
::* Check 'Ruby Internal Commands'
::* click Update

===Adding Ruby Code===
::* In the #756 Report Child Devices field (the big one) copy and paste this code:
:::[[Insteon PLM Ruby Code 756]]
::* In the #776 Reset field, copy and paste this code:
:::[[Insteon PLM Ruby Code 776]]
::* In the #760 Send Command to Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 760]]
::* In the #788 StatusReport field, copy and paste this code:
:::[[Insteon PLM Ruby Code 788]]
::* In the #373 Private Method Listing field, copy and paste this code:
:::[[Insteon PLM Ruby Code 373]]
::* In the #351 Process IDLE field, copy and paste this code:
:::[[Insteon PLM Ruby Code 351]]
::* In the #350 Process Incoming Data field, copy and paste this code:
:::[[Insteon PLM Ruby Code 350]]
::* In the #355 Process Initialize field, copy and paste this code:
:::[[Insteon PLM Ruby Code 355]]
::* In the #384 Process Receive Command for Child field, copy and paste this code:
:::[[Insteon PLM Ruby Code 384]]
::* In the #356 Process Release, leave it blank. (no code for now)
::* Click Update
::* Click Close
===Adding Device Data===
:* Press F5 for refresh the 'Edit Device Template' popup
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port on PC' and click Add.
:* in the Comments Field, type
COM Port
:* in the Default Value field, type
/dev/ttyS0
:* check the 'Required' and 'Allowed to Modify' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'COM Port BaudRate' and click Add.
:* in the Comments Field, type
Baud Rate
:* in the Default Value field, type
19200
:* check the 'Required' and 'Use Master Device List Defaults' boxes
:* In the 'Device data' section, in 'Add a New Parameter' select 'Only One Per PC' and click Add.
:* in the Comments Field, type
Only One Per PC
:* in the Default Value field, type
1
:* In the 'Device data' section, in 'Add a New Parameter' select 'Auto-assign to parents room' and click Add.
:* in the Comments Field, type
Assign to Parents Room
:* in the Default Value field, type
1

===Making the Driver Plug & Play===
:* Scroll down to the 'Plug & Play' Section
:* Enter These values:
::From =
0
::To =
0
::Vendor Model ID =
2412S
::PNP protocol =
Proprietary
::Serial Number =
Insteon PLM
::Parms is blank
::PNP detection script is
88_InsteonPLM.sh
::Comment is
Insteon PLM

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh) '''UPDATE 8/9/08''' Use this format to execute the command Kate /usr/pluto/pnp/88_InsteonPLM.sh missing "/" after pnp.
<pre>
#!/bin/bash

echo "Insteon Powerline Modem Detection Script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 19200 -t "\02\60" -i 1 -s "\03\05"
if [[ "$?" -ne 0 ]]; then
echo "It's not an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is an Insteon Powerline Modem"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1901
fi
</pre>
:* chmod 755 /usr/pluto/pnp/88_InsteonPLM.sh (make it executable)

=== Setting up the Generic Serial Device ===
:* on the top, select Wizard, Devices, Generic Serial Devices. You should now see the InsteonPLM device.
:* select the room it's in.
:* in the Controlled By box, select CORE
:* select Update (at the bottom)
:* Now, in the COM PORT ON PC, you can select the com port it's on.
:* select Update (at the bottom)

You are Done!

==Next Steps==
go to [[Running the Insteon PLM Driver for the First Time]]

Selecting the Right UI

2008-08-09T18:57:12Z

Williammanda: /* UI2 with alpha blending */

{| align="right"
| __TOC__
|}
[[Category:Tutorials]]

==Selecting the Best User Interface (UI)==

The LinuxMCE on-screen Orbiter User Interface (UI) was designed to be viewed on a basic television from 10' away. There are currently three versions of the UI, and selection depends on the type of video card you have. See more [[screenshots]] of the different UIs.

The highest resolution user interface (UI2 with alpha blending) only works with nVidia cards in the 6xxx, 7xxx, or 8xxx series. Use [[Graphics Test]] to determine which UI your graphic card can support.

===UI1===
[[Image:Orbiter.jpg|thumb|500px|left|UI1 or Basic UI]]
<br style="clear:both;"/>
This is the basic UI. If you can load Kubuntu, this UI will work with nearly all graphics hardware, and it requires no special drivers. There are few special effects enabled in this UI. The menus are full screen; when you start media your media also becomes full screen (replacing the menu menu screen).

If you need to do use the '''media menus''' while your media is playing, the media shrinks to a corner of the screen and the rest of the screen shows your media menu. If you need to return to the '''main menu''' to do something else (like adjust the lights), your media is hidden while the main menu appears is displayed.

===UI2 medium===

[[Image:MainMenuUI2M.jpg|thumb|500px|left|UI2 with medium settings (masking)]]
<br style="clear:both;"/>

This is a lightweight, OpenGL-based version of the newest UI. This requires a video card that currently supports OpenGL and XDamage. This UI uses '''masks''' to overlay the media behind the menus.

===UI2 with alpha blending===

[[Image:MainMenuUI2B.jpg|thumb|500px|left|UI2 with alpha blending]]
<br style="clear:both;"/>

In this UI, your media is first and foremost -- the media is always full-screen (it never shrinks and never disappears).

If you're not watching any media, LinuxMCE downloads photos from flickr.com, which are presented in the background (like a screensaver). When the main menu or media menu is displayed, it is blended into the background media image (which is known as alpha blending). This is true whether the screensaver images are being displayed or whether your media (like a video) is playing. This UI includes a 3D media browser, which shows the media files in your home on the sides of a rotating 3D cube.

Few video card manufacturers have the necessary composite extensions in their Linux drivers to support these capabilities, however. At the moment the graphics cards have been confirmed to support the functions of UI2 are the nVidia 6xxx and 7xxx and 8xxx series (with at least 128MB RAM).
'''Update 8/9/08''' 9000 series is also supported. Williammanda

===Controlling the LinuxMCE UI===
There are several ways to manipulate the UI. Here are some examples.

*[[Control LinuxMCE using an Infrared remote]]
*[[Control LinuxMCE with Gyro Remote]]
*Use the keyboard/mouse of a Media Director.