LinuxMCE - User contributions [en]

User:JimmyGosling

2010-01-08T22:53:49Z

JimmyGosling:

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
NIC: 2 x Netgear GA311 Gigabit PCI Adapter (replacement for the failed onboard NICs)
OS: Ubuntu Intrepid Ibex 8.10
Primary App: MythTV Backend
Source code: 0810 (Deployed using DVD installer)
Form Factor: 4U

==System Name: Black Box(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Work)==
Brand: HP 6715b
CPU: AMD Turion 64x2 Mobile
RAM: 3GB
Optical: DVD rewrite
Video Card: ATI Radeon X1250
OS: Windows XP sp2
Primary App: LinuxMCE Orbiter

==System Name: Aspire Revo==
Brand: Acer Aspire Revo 1600

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Network==
Netgear Switch JGS524 24 port Gigabit
Cat6 cabling

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

The green cable has nothing to do with the setup.

The remote sitting on the end table is the only remote for the system, although the system does not controlling the TV, the Fiire remote does.

There are several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show :) The same goes for all of the DVDs and VHS shown on the shelves. It's hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness on the part of the original builder) so lighting control is almost worth the hassle by itself. The led runner lights are controlled via an Insteon controlled receptacle behind the couch.

The "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone who wants to have a great experience in their little basement at a very low cost. Elbow grease not included.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2010-01-08T22:52:47Z

JimmyGosling:

User:JimmyGosling

2009-12-03T21:01:38Z

JimmyGosling: /* System Name: Latop (Work) */

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Work)==

==System Name: Aspire Revo==
Acer Aspire Revo 1600

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-12-03T20:59:40Z

JimmyGosling: /* System Name: Aspire Revo */

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: Aspire Revo==
Acer Aspire Revo 1600

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-12-03T20:57:53Z

JimmyGosling: /* System Name: Acer Aspire Revo */

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: Aspire Revo==
Acer Aspire Revo 1600

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-12-03T20:57:13Z

JimmyGosling:

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: WD NAS==

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-12-03T20:56:34Z

JimmyGosling: /* System Name: Solaris Box (Garage68 Web Server) */

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: WD NAS==

==System Name: Pluto Core (Future Development Box)==
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-06-01T17:42:51Z

JimmyGosling:

Current configuration running '''0710'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: WD NAS==

==System Name: Solaris Box (Garage68 Web Server)==
Type: Sun Fire v100
CPU: 550 MHz UltraSPARC-IIi
RAM: 2 GB
HD: 40 GB 7200 RPM IDE
OS: Solaris 10
CD-ROM: 24x CD-ROM drive
NIC: Two 10/100 Base-T Ethernet ports
Special Features: Lights-Out-Management
Form Factor: 1U

==System Name: Pluto Core (Future Development Box)==
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

User:JimmyGosling

2009-06-01T17:42:21Z

JimmyGosling:

Current configuration running '''0710b3'''

System Specifications:

==System Name: DCERouter (Core)==
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710b3
Form Factor: 4U

==System Name: Theatre MD(Theatre Room)==
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

==System Name: Latop (Roguen Work)==

==System Name: WD NAS==

==System Name: Solaris Box (Garage68 Web Server)==
Type: Sun Fire v100
CPU: 550 MHz UltraSPARC-IIi
RAM: 2 GB
HD: 40 GB 7200 RPM IDE
OS: Solaris 10
CD-ROM: 24x CD-ROM drive
NIC: Two 10/100 Base-T Ethernet ports
Special Features: Lights-Out-Management
Form Factor: 1U

==System Name: Pluto Core (Future Development Box)==
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

==Orbiters/Remote Controls==
1 x Fiire Chief Remotes

==Home Automation==
Insteon PLM
Insteon Light Switch
Insteon Receptical

==Comments==
A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

[[Category:User Setups]]
[[Category:X10 User Setups]]
[[Category:Insteon User Setups]]
[[Category:Orbiter Setups]]

Insteon - Setting Up PLM Template

2008-09-14T00:47:50Z

JimmyGosling: /* 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
'''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/ directory (88_InsteonPLM.sh). The script will not currently exist so it must be created. Depending on who you have logged in as you may need super user privileges.
:The command '''sudo vi /usr/pluto/pnp/88_InsteonPLM.sh''' will both create the file and allow you to edit. The super user password will be required.
:User Notes:
:'''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). The sudo command prefix will work here as well if you are not logged in as root.

=== 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
'''TODO''' Other than looking on the motherboard for the com port label and guess and check methods, what else can be done to identify the correct com port?
:* 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-09-14T00:44:20Z

JimmyGosling: /* 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
'''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/ directory (88_InsteonPLM.sh). The script will not currently exist so it must be created. Depending on who you have logged in as you may need super user privileges.
:The command '''sudo vi /usr/pluto/pnp/88_InsteonPLM.sh''' will both create the file and allow you to edit. The super user password will be required.
:User Notes:
:'''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). The sudo command prefix will work here as well if you are not logged in as root.

=== 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-09-14T00:42:57Z

JimmyGosling: /* 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
'''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/ directory (88_InsteonPLM.sh). The script will not currently exist so it must be created. Depending on who you have logged in as you may need super user privileges.
The command '''sudo vi /usr/pluto/pnp/88_InsteonPLM.sh''' will both create the file and allow you to edit. The super user password will be required.
User Notes:
:'''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). The sudo command prefix will work here as well if you are not logged in as root.

=== 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-09-14T00:36:29Z

JimmyGosling: /* 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
'''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)
User Notes:
'''UPDATE 8/9/08''' Use this format to execute the command '''Kate /usr/pluto/pnp/88_InsteonPLM.sh''' missing "/" after pnp. Williammanda
'''UPDATE 9/13/08''' If there is a little confusion, hopefully this will clear it up a little bit.
:* You must create the new script, 88_InsteonPLM.sh, in the /usr/pluto/pnp/ directory.
:* Depending on who you have logged in as, you may need super user priviledges to complete the task of creating this file, editing it and changing the ownership. All 3 of these tasks can be accomplished by prefixing your command with 'sudo' and entering the appropriate super user password.
<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]]

User:JimmyGosling

2008-04-10T18:43:49Z

JimmyGosling:

Current configuration running 0710b3

System Specifications:

System Name: DCERouter (Core)
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710b3
Form Factor: 4U

System Name: Theatre MD(Theatre Room)
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

System Name: Skirts Desktop (Dell)

System Name: Laptop (Roguen)
Motherboard: IBM
CPU: Intel Centrino
RAM: 2GB
HD: 100GB
OS: Win XP PRO
DVD Burner: built-in
NIC: 10/100TX/802.11g/Bluetooth

System Name: Laptop (Skirt Dell)

System Name: Latop (Roguen Work)

System Name: WD NAS

System Name: Solaris Box (Garage68 Web Server)
Type: Sun Fire v100
CPU: 550 MHz UltraSPARC-IIi
RAM: 2 GB
HD: 40 GB 7200 RPM IDE
OS: Solaris 10
CD-ROM: 24x CD-ROM drive
NIC: Two 10/100 Base-T Ethernet ports
Special Features: Lights-Out-Management
Form Factor: 1U

System Name: Pluto Core (Future Development Box)
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

Orbiters/Remote Controls:
1 x Fiire Chief Remotes

Home Automation:
Insteon PLM
Insteon Light Switch
Insteon Receptical

A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :) The same goes for all of the DVDs and VHS shown on the shelves. It's so hard to part with them isn't it?

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

Obviously my "Theatre Room" isn't massive and I'm not made of money, but LinuxMCE has made a solution like this accessible for someone even like myself who wants to have a great experience in their little basement.

User:JimmyGosling

2008-04-10T18:42:14Z

JimmyGosling:

User:JimmyGosling

2008-04-10T18:41:18Z

JimmyGosling:

Current configuration running 0710b3

System Specifications:

System Name: DCERouter (Core)
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710b3
Form Factor: 4U

System Name: Theatre MD(Theatre Room)
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

System Name: Skirts Desktop (Dell)

System Name: Laptop (Roguen)
Motherboard: IBM
CPU: Intel Centrino
RAM: 2GB
HD: 100GB
OS: Win XP PRO
DVD Burner: built-in
NIC: 10/100TX/802.11g/Bluetooth

System Name: Laptop (Skirt Dell)

System Name: Latop (Roguen Work)

System Name: WD NAS

System Name: Solaris Box (Garage68 Web Server)
Type: Sun Fire v100
CPU: 550 MHz UltraSPARC-IIi
RAM: 2 GB
HD: 40 GB 7200 RPM IDE
OS: Solaris 10
CD-ROM: 24x CD-ROM drive
NIC: Two 10/100 Base-T Ethernet ports
Special Features: Lights-Out-Management
Form Factor: 1U

System Name: Pluto Core (Future Development Box)
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

Orbiters/Remote Controls:
1 x Fiire Chief Remotes

Home Automation:
Insteon PLM
Insteon Light Switch
Insteon Receptical

A short description by TheGos is provided below:

[[Image:DSC01212.JPG]]

Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :)

Lights for the room are controller via Insteon. The actual light switches are nowhere close to the room (poor design or laziness probably factored into that decision) and so lighting control was a big "want". The led runner lights are also controled via an Insteon controlled receptacle behind the couch.

User:JimmyGosling

2008-04-10T18:38:27Z

JimmyGosling:

Current configuration running 0710b3

System Specifications:

System Name: DCERouter (Core)
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710b3
Form Factor: 4U

System Name: Theatre MD(Theatre Room)
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

System Name: Skirts Desktop (Dell)

System Name: Laptop (Roguen)
Motherboard: IBM
CPU: Intel Centrino
RAM: 2GB
HD: 100GB
OS: Win XP PRO
DVD Burner: built-in
NIC: 10/100TX/802.11g/Bluetooth

System Name: Laptop (Skirt Dell)

System Name: Latop (Roguen Work)

System Name: WD NAS

System Name: Solaris Box (Garage68 Web Server)
Type: Sun Fire v100
CPU: 550 MHz UltraSPARC-IIi
RAM: 2 GB
HD: 40 GB 7200 RPM IDE
OS: Solaris 10
CD-ROM: 24x CD-ROM drive
NIC: Two 10/100 Base-T Ethernet ports
Special Features: Lights-Out-Management
Form Factor: 1U

System Name: Pluto Core (Future Development Box)
Motherboard: IBM
CPU: 2 x 1GHz Intel
RAM: 2 GB
HD: 100GB
OS: Debian Sarge (Pluto)
CD-ROM: built-in
NIC: Two 10/100 Base-T Ethernet ports
Form Factor: 1U

Orbiters/Remote Controls:
1 x Fiire Chief Remotes

Home Automation:
Insteon PLM
Insteon Light Switch
Insteon Receptical

A short description by TheGos:
Pay no attention to my green network cable there, no that's not part of the setup, I just happen to like wired connections where I can get them for the laptop.

The remote sitting on the end table is my only remote.

I do have several devices under the TV, but obviously the receiver and the media director are the only ones being used. The others are just for show I guess :)
[[Image:DSC01212.JPG]]

User:JimmyGosling

2008-04-10T18:35:15Z

JimmyGosling:

File:DSC01212.JPG

2008-04-10T18:34:36Z

JimmyGosling: Jimmy's Theatre Room

Jimmy's Theatre Room

User:JimmyGosling

2008-04-08T18:50:22Z

JimmyGosling:

Insteon

2008-04-08T16:16:31Z

JimmyGosling:

[[Category: Hardware| ]]
[[Category: Automation]]

Insteon is the product name for a series of devices which communicate using either powerline signalling, RF signalling, or a combination of both. LinuxMCE support for Insteon devices is currently under development. More information on the Insteon devices can be found at [http://www.insteon.com Insteon]. Products are available at [http://www.smarthome.com SmartHome]

Insteon development is currently underway.

There are currently 3 types of Insteon controllers:

1. PowerLinc Controller USB (PLC) 
[[Image:2414u.jpg]] 
2. PowerLinc Controller Serial (PLC) 
[[Image:2414s.jpg]] 
3. PowerLinc Modem (PLM) 
[[Image:2414s.jpg]] 

'''Please Note:''' The PowerLinc Controller Serial and PowerLinc Modem are using the same picture, however they are NOT the same device. They have different part numbers. The PLM is 2412s, the PLC is 2414s.

Among these controllers, there is another device called the EZBridge that uses a PLM to interface ethernet to insteon.
Communication to the EZBridge is accomplished via an XML commandset over an established IP Port.
I have implemented the EZBridge via GSD/Ruby. Source is currently located in the developers forum. (search for EZBridge)
[[Image:31272.jpg]]

The EZBridge is IDEAL for remote locations, summer houses, etc. All communication is via a TCP Socket in xml form.

It is feasable to actually have MORE THAN ONE location set up in your linuxmce system. With the use of an EZBridge, it's just like being there. Lights/Appliances can be turned on/off as if they were local.

1. What is an INSTEON network?
The INSTEON network protocol is a new cost-effective dual-mesh (radio frequency - RF and powerline) home management network technology, that provides a secure, highly-available, affordable, robust home management network for home innovations. INSTEON technology is simple to integrate and will be widely available in a broad set of products offered by SmarthomeTM, Inc. and many other product innovators.

2. Is INSTEON a secure network?
Yes. Every INSTEON device has a unique 24 bit address, all transmissions are encoded onto the network. Additionally, INSTEON is designed to support additional device based encryption technologies.

3. What is a mesh network and how does it work?
The INSTEON network is an integrated (RF, Powerline) redundant, non-supervised, peer-to-peer network. There is no need for routing tables, each device in the network receives messages simultaneously, independent of whether the message originated via a wireless or powerline device. Network devices will "repeat" the signal based on message settings.

4. When will products with INSTEON technology be available?
The first INSTEON products launched the second quarter of 2005. Currently, INSTEON-compatible devices are available from over 15 manufacturers with approximately 50 products available to date.

5. How much will INSTEON-compatible devices cost?
Devices will start at $19.99 retail. INSTEON is a very cost-effective technology to integrate into a wide range of products.

6. How many partners are developing INSTEON products?
SmartLabs is in the process of working with a wide variety of business partners. INSTEON technology is easy to integrate and is priced to be able to include in a broad base of products, from simple inexpensive wireless sensors to large home appliances. To find out more regarding Smarthome's Smart partner program call 866-243-8022. Many of the partners are listed in the partner section of this website.

7. How does INSTEON compare with ZigBeeTM, BluetoothTM, HomePlugTM, X-10TM?

* Bluetooth - Bluetooth is designed as an ad-hoc network technology and as such is not designed to be a home control networking technology.
* ZigBee/Z-Wave - INSTEON is not limited to a single physical network technology and does not require a network controller. It supports both RF and Powerline, enabling a broader set of applications. INSTEON technology is also a more cost-effective and reliable technology allowing it to be integrated into a broader range of products.
* HomePlug - INSTEON is compatible with HomePlug but focused on different applications. HomePlug is tuned to broadband applications while INSTEON is focused on home control. INSTEON is a more cost-effective technology for home management.
* X-10 - INSTEON is a more robust and reliable network yet, it is priced similarly and is compatible with industry standard X-10 devices.

8. If a home has a broadband network, why do I need INSTEON?
Homes will have two networks (Multimedia and Management). The broadband network is focused on a home's multimedia needs and is ideal for sending voice, video and internet throughout the home. The management network (INSTEON) is focused on sending control and simple data between devices within the home (i.e. a light switch turning on multiple lights/devices within the home). While the broadband network could also serve the management needs, on a device basis it is too expensive. Additionally, customers are not willing to plug their washer, microwave or garage door into an Ethernet cable.

9. Does INSTEON work with other home network technologies?
Yes, INSTEON will be introduced with an Ethernet, USB and serial bridge to allow communications with the Internet, computers and wide variety of security and wiring panels. Additionally, INSTEON supports communications with existing X-10 based devices. Smarthome expects development of additional bridges to other network technologies based on market demand.

10. Should I continue to purchase X-10 based products or wait for INSTEON?
One of the significant advantages of the new INSTEON technology is it's backwards compatibility with existing X-10 products. As an example, an INSTEON switch can turn on an X-10 lamp module and an X-10 switch can turn on an INSTEON lamp module. Homeowners can continue to purchase X-10 devices today and then migrate over time to INSTEON.

11. Can the INSTEON technology handle high-bandwidth for application such as A/V distribution?
The protocol is designed to handle simple data, up to 16 bytes per message @ up to 10 messages a second. INSTEON will not support higher-bandwidth application. These applications are best suited for standard Ethernet. Higher band-width support results in higher overall cost. INSTEON is optimized for affordable, reliable, and secure control.

12. What applications are a good fit for the INSTEON technology?

* Scene and remote control lighting
* Security alarm interfaces and sensors
* Home sensors (e.g. water, humidity, temperature)
* Access control (e.g. door locks)
* Heating and cooling (HVAC) control and management
* Audio-video control
* Appliance management
* Energy savings

13. Does INSTEON support other voltages, such as 50Hz/220VAC?
Although Smarthome has not yet designed devices for voltages other than 110VAC/60Hz, the INSTEON technology could be adjusted for 50Hz timing. We do not have a schedule as yet for doing this effort.

14. What platforms (i.e. Windows, Mac, Linux) are supported by the INSTEON protocol?
Supported platforms depend on the interface used to communicate with the INSTEON network. Smarthome's PowerLinc (USB and Serial) and Powerline Modem (Serial) support any platform that can communicate with either a serial or USB port. Additionally, we have partners that have developed and are selling IP interfaces.

15. What devices do not repeat INSTEON signals?
To conserve power, message repeating can be disabled in devices, such as battery operated devices.

16. How is INSTEON support implemented into products?
Smarthome offer's Developer Kits which interface with products to allow communications between the product and the INSTEON network. The interface can be an internal INSTEON chip, a small PC board or an external plug-in adapter with I/O ports connecting to the host product(s).

17. How likely is RF interference?
Very unlikely. In the few situations we've encountered interference with other wireless devices, simply changing the frequency (commonly referred to as "Channels") on the offending device will solve any issues. INSTEON messages are very brief, leaving only a small amount of time for interference to occur.

18. Is every INSTEON compatible device required to be X10 compatible?
X10 compatibility is determined by the product manufacture/vendor. The INSTEON protocol does not mandate X10 compatibility. SmartLab's INSTEON compatible devices are made to support X10.

19. Will I be able to sell the product(s) I develop with the developer's kit?
Yes, you will be able to sell your software product(s) developed from the INSTEON developers kit. Prior to offering for sale, you must submit the product to Smarthome for INSTEON compatibility testing and INSTEON certification. This is a free service that Smarthome provides to insure the software complies with proper INSTEON protocols. Once you are at a stage where the product can be tested, contact us.

20. How do I sell my software or hardware I created using the developer's kits?
Once the product passes compatibility testing, you sell the software and/or hardware through any distribution channels. Additionally, the product may also be submitted to Smarthome category managers for consideration to distribute through Smarthome web and catalog channels.

[[Setting Up PLM Template]]

Images used are Copyright 1995-2008 [http://www.smarthome.com SMARTHOME]

File:31272.jpg

2008-04-08T16:09:30Z

JimmyGosling: EZBridge INSTEON/X10 to IP Bridge

EZBridge INSTEON/X10 to IP Bridge

Insteon

2008-04-08T16:07:41Z

JimmyGosling:

[[Category: Hardware| ]]
[[Category: Automation]]

Insteon is the product name for a series of devices which communicate using either powerline signalling, RF signalling, or a combination of both. LinuxMCE support for Insteon devices is currently under development. More information on the Insteon devices can be found at [http://www.insteon.com Insteon]. Products are available at [http://www.smarthome.com SmartHome]

Insteon development is currently underway.

There are currently 3 types of Insteon controllers:

1. PowerLinc Controller USB (PLC) 
[[Image:2414u.jpg]] 
2. PowerLinc Controller Serial (PLC) 
[[Image:2414s.jpg]] 
3. PowerLinc Modem (PLM) 
[[Image:2414s.jpg]] 

'''Please Note:''' The PowerLinc Controller Serial and PowerLinc Modem are using the same picture, however they are NOT the same device. They have different part numbers. The PLM is 2412s, the PLC is 2414s.

Images used are Copyright 1995-2008 [http://www.smarthome.com SMARTHOME]

Among these controllers, there is another device called the EZBridge that uses a PLM to interface ethernet to insteon.
Communication to the EZBridge is accomplished via an XML commandset over an established IP Port.
I have implemented the EZBridge via GSD/Ruby. Source is currently located in the developers forum. (search for EZBridge)

The EZBridge is IDEAL for remote locations, summer houses, etc. All communication is via a TCP Socket in xml form.

It is feasable to actually have MORE THAN ONE location set up in your linuxmce system. With the use of an EZBridge, it's just like being there. Lights/Appliances can be turned on/off as if they were local.

1. What is an INSTEON network?
The INSTEON network protocol is a new cost-effective dual-mesh (radio frequency - RF and powerline) home management network technology, that provides a secure, highly-available, affordable, robust home management network for home innovations. INSTEON technology is simple to integrate and will be widely available in a broad set of products offered by SmarthomeTM, Inc. and many other product innovators.

2. Is INSTEON a secure network?
Yes. Every INSTEON device has a unique 24 bit address, all transmissions are encoded onto the network. Additionally, INSTEON is designed to support additional device based encryption technologies.

3. What is a mesh network and how does it work?
The INSTEON network is an integrated (RF, Powerline) redundant, non-supervised, peer-to-peer network. There is no need for routing tables, each device in the network receives messages simultaneously, independent of whether the message originated via a wireless or powerline device. Network devices will "repeat" the signal based on message settings.

4. When will products with INSTEON technology be available?
The first INSTEON products launched the second quarter of 2005. Currently, INSTEON-compatible devices are available from over 15 manufacturers with approximately 50 products available to date.

5. How much will INSTEON-compatible devices cost?
Devices will start at $19.99 retail. INSTEON is a very cost-effective technology to integrate into a wide range of products.

6. How many partners are developing INSTEON products?
SmartLabs is in the process of working with a wide variety of business partners. INSTEON technology is easy to integrate and is priced to be able to include in a broad base of products, from simple inexpensive wireless sensors to large home appliances. To find out more regarding Smarthome's Smart partner program call 866-243-8022. Many of the partners are listed in the partner section of this website.

7. How does INSTEON compare with ZigBeeTM, BluetoothTM, HomePlugTM, X-10TM?

* Bluetooth - Bluetooth is designed as an ad-hoc network technology and as such is not designed to be a home control networking technology.
* ZigBee/Z-Wave - INSTEON is not limited to a single physical network technology and does not require a network controller. It supports both RF and Powerline, enabling a broader set of applications. INSTEON technology is also a more cost-effective and reliable technology allowing it to be integrated into a broader range of products.
* HomePlug - INSTEON is compatible with HomePlug but focused on different applications. HomePlug is tuned to broadband applications while INSTEON is focused on home control. INSTEON is a more cost-effective technology for home management.
* X-10 - INSTEON is a more robust and reliable network yet, it is priced similarly and is compatible with industry standard X-10 devices.

8. If a home has a broadband network, why do I need INSTEON?
Homes will have two networks (Multimedia and Management). The broadband network is focused on a home's multimedia needs and is ideal for sending voice, video and internet throughout the home. The management network (INSTEON) is focused on sending control and simple data between devices within the home (i.e. a light switch turning on multiple lights/devices within the home). While the broadband network could also serve the management needs, on a device basis it is too expensive. Additionally, customers are not willing to plug their washer, microwave or garage door into an Ethernet cable.

9. Does INSTEON work with other home network technologies?
Yes, INSTEON will be introduced with an Ethernet, USB and serial bridge to allow communications with the Internet, computers and wide variety of security and wiring panels. Additionally, INSTEON supports communications with existing X-10 based devices. Smarthome expects development of additional bridges to other network technologies based on market demand.

10. Should I continue to purchase X-10 based products or wait for INSTEON?
One of the significant advantages of the new INSTEON technology is it's backwards compatibility with existing X-10 products. As an example, an INSTEON switch can turn on an X-10 lamp module and an X-10 switch can turn on an INSTEON lamp module. Homeowners can continue to purchase X-10 devices today and then migrate over time to INSTEON.

11. Can the INSTEON technology handle high-bandwidth for application such as A/V distribution?
The protocol is designed to handle simple data, up to 16 bytes per message @ up to 10 messages a second. INSTEON will not support higher-bandwidth application. These applications are best suited for standard Ethernet. Higher band-width support results in higher overall cost. INSTEON is optimized for affordable, reliable, and secure control.

12. What applications are a good fit for the INSTEON technology?

* Scene and remote control lighting
* Security alarm interfaces and sensors
* Home sensors (e.g. water, humidity, temperature)
* Access control (e.g. door locks)
* Heating and cooling (HVAC) control and management
* Audio-video control
* Appliance management
* Energy savings

13. Does INSTEON support other voltages, such as 50Hz/220VAC?
Although Smarthome has not yet designed devices for voltages other than 110VAC/60Hz, the INSTEON technology could be adjusted for 50Hz timing. We do not have a schedule as yet for doing this effort.

14. What platforms (i.e. Windows, Mac, Linux) are supported by the INSTEON protocol?
Supported platforms depend on the interface used to communicate with the INSTEON network. Smarthome's PowerLinc (USB and Serial) and Powerline Modem (Serial) support any platform that can communicate with either a serial or USB port. Additionally, we have partners that have developed and are selling IP interfaces.

15. What devices do not repeat INSTEON signals?
To conserve power, message repeating can be disabled in devices, such as battery operated devices.

16. How is INSTEON support implemented into products?
Smarthome offer's Developer Kits which interface with products to allow communications between the product and the INSTEON network. The interface can be an internal INSTEON chip, a small PC board or an external plug-in adapter with I/O ports connecting to the host product(s).

17. How likely is RF interference?
Very unlikely. In the few situations we've encountered interference with other wireless devices, simply changing the frequency (commonly referred to as "Channels") on the offending device will solve any issues. INSTEON messages are very brief, leaving only a small amount of time for interference to occur.

18. Is every INSTEON compatible device required to be X10 compatible?
X10 compatibility is determined by the product manufacture/vendor. The INSTEON protocol does not mandate X10 compatibility. SmartLab's INSTEON compatible devices are made to support X10.

19. Will I be able to sell the product(s) I develop with the developer's kit?
Yes, you will be able to sell your software product(s) developed from the INSTEON developers kit. Prior to offering for sale, you must submit the product to Smarthome for INSTEON compatibility testing and INSTEON certification. This is a free service that Smarthome provides to insure the software complies with proper INSTEON protocols. Once you are at a stage where the product can be tested, contact us.

20. How do I sell my software or hardware I created using the developer's kits?
Once the product passes compatibility testing, you sell the software and/or hardware through any distribution channels. Additionally, the product may also be submitted to Smarthome category managers for consideration to distribute through Smarthome web and catalog channels.

[[Setting Up PLM Template]]

File:2414u.jpg

2008-04-08T15:57:03Z

JimmyGosling: Insteon Powerlinc Controller USB (2414u)

Insteon Powerlinc Controller USB (2414u)

File:2414s.jpg

2008-04-08T15:56:26Z

JimmyGosling: Insteon PowerLinc Modem Serial (2414s) and Powerlinc Controller Serial (2412s). Same picture, but different part numbers.

Insteon PowerLinc Modem Serial (2414s) and Powerlinc Controller Serial (2412s). Same picture, but different part numbers.

Contacts

2008-04-04T01:19:27Z

JimmyGosling:

LinuxMCE is a media centered [[Linux]] distribution. It's built on the solid foundation laid down by debian and Ubuntu. But with all kinds of goodies for the home of the future, from digital video recorder capabilities and home automation to functioning as a telephone switching hub for your home in lieu of a boring intercom system; all tied together by an advanced messaging infrastructure. While the next release 0710 is almost done and focuses on stability, we're already planning for the next release and '''you''' could contribute to it's direction. We're always looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!

----
'''Daniel Kristjansson''' -- contact: danielk -at- cuymedia (.net) 
Responsibilities: Community liaison, organizing open source volunteers and roadmap 
----
'''Justin Burdine''' -- contact: justin -at- cyburdinehosting (.com) 
Offering: Hosting/Bandwidth, Graphic Design (see [[http://cbvfx.com cbvfx.com]]), Video Editing/Promotion (see [[http://cbvfx.com cbvfx.com]]), install/testing 
----
'''John Botte''' -- contact: qualityinterfaces -at- gmail (.com) 
Offering: Forum moderation help. Conceptual ideas, help with firewire support, UI help and testing 
----
'''Jonathan Iannone''' -- Contact: thorn168 -at- yahoo (.com) 
Offering: Help with documentation
----
'''[[User:Nite_man|Michael Stepanov]]''' aka nite_man -- Contact: stepanov.michael -at- gmail (.com) 
Offering: Build and test SDL Orbiter for Linux-based PC and Nokia770/N800/N810, Russian translation, testing and feedback.
----
'''Paul D''' aka Trout -- Contact: linuxmce.gqn@gishpuppy.com 
Offering: Help with documentation, Wiki participation, Testing and feedback.
----
'''Pete Kalogiannis''' -- Contact: pkalogiannis -at- gmail (dot) com 
Offering: [[Insteon]] Integration
----
'''[[User:Ddamron|Dan Damron]]''' -- Contact: dan -at- danthecomputerman (dot) info 
Offering: [[Insteon]] Integration via PLM (In OPEN beta test now!) / EZBridge/EZServ

Offering: [[PLCBUS]] Integration
----
'''Nat''' -- Contact Paul Webber to relay messages to Nat
Offering: Nat has some access to some free or low-cost hardware, like TV Tuners, Video Cards, etc., which he can make available for developers actively working on a project.
----
'''Pierre Hansson''' aka Samme -- Contact: 316097 at gmail dot com 
Offering: Wiki-admin
----
'''Lozzo''' -- Contact via [[User talk:Lozzo|his talk page]] 
Offering: wiki admin & documentation
----
'''Chriss''' 
Offering: SVN hosting (see [http://forum.linuxmce.org/index.php?topic=2277.msg13677#msg13677 forum])
----
'''Larry Brigman''' -- Contact larry dot brigman -at- gmail (dot) com 
Offering: Help with documentation, Wiki participation, QA and testing,
Build script work.
----
'''Robert Wilson''' aka rwilson131 -- Contact: rwilson131 at gmail dot com 
Offering: Wiki Documentation and Creation of [[User Manual]]
----
'''Harald Klein''' aka hari -- Contact: hari at vt100 dot at 
Offering: sqlCVS maintenance, code developement, documentation and testing.
----
'''Seven Walter''' aka CylonSeven -- Contact: Seven -at- Apollo Smart Homes (dot) com 
Offering: QA & Testing, Docs, Wiki, Promotions (Central Texas USA). Plenty of hardware for testing: Hybrid w/ RAID, fast MD/HTPC w/ HiDef & Digital Audio out, Firewire & IP cameras, ZWave, etc. 
----
'''Brandon Kruger''' aka bmk789 -- Contact via [[User:bmk789|User page]] 
Offering: wiki moderation & documentation
----
'''Richard''' aka RichardR -- Contact: Richard (at) openbeta (dot) co (dot) uk
Offering: lots of Video editing and production experience for promotions and videos.
----
'''[[User:JimmyGosling|Roguen]]''' aka JimmyGosling(Forums), JimmyGos (IIRC) or TheGos (IIRC) -- Contact: Roguen (at) garage68 (dot) com 
Offering: code development, wiki documentation

== Alumni ==

'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com) 
Paul launched LinuxMCE on March 15, 2007, but is moving on to other projects. He visits us occasionally but after release 0710 will no longer be solely responsible for any aspect of the LinuxMCE release cycle. See [[History|'''History of LinuxMCE''']], for an explanation of why Paul started the project.

[[Category:Development]]
[[Category:Wiki administration]]

User:JimmyGosling

2008-04-04T01:15:32Z

JimmyGosling: New page: Current configuration running 0710b3 System Specifications: System Name: DCERouter (Core) Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX Case: 1 x 4U Rackmount CP...

Current configuration running 0710b3

System Specifications:

System Name: DCERouter (Core)
Motherboard: 1 x ABIT IP35 Pro LGA 775 Intel P35 ATX
Case: 1 x 4U Rackmount
CPU: 1 x Intel Core 2 Duo E4500 Allendale 2.2GHz 2M shared L2 Cache
RAM: 2 x CORSAIR XMS2 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory
Optical: 1 x Memorex IDE (DVD)
HD: 1 x Western Digital Caviar SE WD5000AAJS 500GB 7200 RPM 8MB Cache SATA 3.0Gb/s Hard Drive
GPU: 1 x MSI NX6200AX-TD128LF GeForce 6200 128MB 64-bit DDR AGP 4X/8X
OS: Ubuntu Feisty 7.04
Primary App: MythTV Backend
Source code: 0710b3

System Name: Theatre MD(Theatre Room)
Motherboard: 1 x Nvidia Gforce 7050PV HDMI
Case: 1 x Apex DM-387
CPU: 1 x AMD 2800+ Sempron 64
RAM: 2 x 512MB DDR2 SDRAM Unbuffered DIMM 240-pin 533MHz
Optical: 1 x Memorex IDE DVD
OS: PXE
Primary App: LinuxMCE FrontEnd

System Name: Skirts Desktop (Dell)

System Name: Laptop (Roguen)
Motherboard: IBM
CPU: Intel Centrino
RAM: 2GG
HD: 100GB
OS: Win XP PRO
DVD Burner: built-in
NIC: 10/100TX/802.11g/Bluetooth

System Name: Laptop (Skirt Dell)

System Name: Latop (Roguen Work)

System Name: WD NAS

Orbiters/Remote Controls:
1 x Fiire Chief Remotes

Home Automation:
Insteon PLM
Insteon Light Switch
Insteon Receptical

Contacts

2008-04-04T01:01:51Z

JimmyGosling:

LinuxMCE is a media centered [[Linux]] distribution. It's built on the solid foundation laid down by debian and Ubuntu. But with all kinds of goodies for the home of the future, from digital video recorder capabilities and home automation to functioning as a telephone switching hub for your home in lieu of a boring intercom system; all tied together by an advanced messaging infrastructure. While the next release 0710 is almost done and focuses on stability, we're already planning for the next release and '''you''' could contribute to it's direction. We're always looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!

----
'''Daniel Kristjansson''' -- contact: danielk -at- cuymedia (.net) 
Responsibilities: Community liaison, organizing open source volunteers and roadmap 
----
'''Justin Burdine''' -- contact: justin -at- cyburdinehosting (.com) 
Offering: Hosting/Bandwidth, Graphic Design (see [[http://cbvfx.com cbvfx.com]]), Video Editing/Promotion (see [[http://cbvfx.com cbvfx.com]]), install/testing 
----
'''John Botte''' -- contact: qualityinterfaces -at- gmail (.com) 
Offering: Forum moderation help. Conceptual ideas, help with firewire support, UI help and testing 
----
'''Jonathan Iannone''' -- Contact: thorn168 -at- yahoo (.com) 
Offering: Help with documentation
----
'''[[User:Nite_man|Michael Stepanov]]''' aka nite_man -- Contact: stepanov.michael -at- gmail (.com) 
Offering: Build and test SDL Orbiter for Linux-based PC and Nokia770/N800/N810, Russian translation, testing and feedback.
----
'''Paul D''' aka Trout -- Contact: linuxmce.gqn@gishpuppy.com 
Offering: Help with documentation, Wiki participation, Testing and feedback.
----
'''Pete Kalogiannis''' -- Contact: pkalogiannis -at- gmail (dot) com 
Offering: [[Insteon]] Integration
----
'''[[User:Ddamron|Dan Damron]]''' -- Contact: dan -at- danthecomputerman (dot) info 
Offering: [[Insteon]] Integration via PLM (In OPEN beta test now!) / EZBridge/EZServ

Offering: [[PLCBUS]] Integration
----
'''Nat''' -- Contact Paul Webber to relay messages to Nat
Offering: Nat has some access to some free or low-cost hardware, like TV Tuners, Video Cards, etc., which he can make available for developers actively working on a project.
----
'''Pierre Hansson''' aka Samme -- Contact: 316097 at gmail dot com 
Offering: Wiki-admin
----
'''Lozzo''' -- Contact via [[User talk:Lozzo|his talk page]] 
Offering: wiki admin & documentation
----
'''Chriss''' 
Offering: SVN hosting (see [http://forum.linuxmce.org/index.php?topic=2277.msg13677#msg13677 forum])
----
'''Larry Brigman''' -- Contact larry dot brigman -at- gmail (dot) com 
Offering: Help with documentation, Wiki participation, QA and testing,
Build script work.
----
'''Robert Wilson''' aka rwilson131 -- Contact: rwilson131 at gmail dot com 
Offering: Wiki Documentation and Creation of [[User Manual]]
----
'''Harald Klein''' aka hari -- Contact: hari at vt100 dot at 
Offering: sqlCVS maintenance, code developement, documentation and testing.
----
'''Seven Walter''' aka CylonSeven -- Contact: Seven -at- Apollo Smart Homes (dot) com 
Offering: QA & Testing, Docs, Wiki, Promotions (Central Texas USA). Plenty of hardware for testing: Hybrid w/ RAID, fast MD/HTPC w/ HiDef & Digital Audio out, Firewire & IP cameras, ZWave, etc. 
----
'''Brandon Kruger''' aka bmk789 -- Contact via [[User:bmk789|User page]] 
Offering: wiki moderation & documentation
----
'''Richard''' aka RichardR -- Contact: Richard (at) openbeta (dot) co (dot) uk
Offering: lots of Video editing and production experience for promotions and videos.
----
'''[[User:JimmyGosling|Roguen]]''' aka JimmyGosling(Forums), JimmyGos (IIRC) or TheGos (IIRC) -- Contact: Roguen (at) garage68 (dot) com
Offering: Java development, wiki documentation

== Alumni ==

'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com) 
Paul launched LinuxMCE on March 15, 2007, but is moving on to other projects. He visits us occasionally but after release 0710 will no longer be solely responsible for any aspect of the LinuxMCE release cycle. See [[History|'''History of LinuxMCE''']], for an explanation of why Paul started the project.

[[Category:Development]]
[[Category:Wiki administration]]

Contacts

2008-04-04T01:00:40Z

JimmyGosling:

LinuxMCE is a media centered [[Linux]] distribution. It's built on the solid foundation laid down by debian and Ubuntu. But with all kinds of goodies for the home of the future, from digital video recorder capabilities and home automation to functioning as a telephone switching hub for your home in lieu of a boring intercom system; all tied together by an advanced messaging infrastructure. While the next release 0710 is almost done and focuses on stability, we're already planning for the next release and '''you''' could contribute to it's direction. We're always looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!

----
'''Daniel Kristjansson''' -- contact: danielk -at- cuymedia (.net) 
Responsibilities: Community liaison, organizing open source volunteers and roadmap 
----
'''Justin Burdine''' -- contact: justin -at- cyburdinehosting (.com) 
Offering: Hosting/Bandwidth, Graphic Design (see [[http://cbvfx.com cbvfx.com]]), Video Editing/Promotion (see [[http://cbvfx.com cbvfx.com]]), install/testing 
----
'''John Botte''' -- contact: qualityinterfaces -at- gmail (.com) 
Offering: Forum moderation help. Conceptual ideas, help with firewire support, UI help and testing 
----
'''Jonathan Iannone''' -- Contact: thorn168 -at- yahoo (.com) 
Offering: Help with documentation
----
'''[[User:Nite_man|Michael Stepanov]]''' aka nite_man -- Contact: stepanov.michael -at- gmail (.com) 
Offering: Build and test SDL Orbiter for Linux-based PC and Nokia770/N800/N810, Russian translation, testing and feedback.
----
'''Paul D''' aka Trout -- Contact: linuxmce.gqn@gishpuppy.com 
Offering: Help with documentation, Wiki participation, Testing and feedback.
----
'''Pete Kalogiannis''' -- Contact: pkalogiannis -at- gmail (dot) com 
Offering: [[Insteon]] Integration
----
'''[[User:Ddamron|Dan Damron]]''' -- Contact: dan -at- danthecomputerman (dot) info 
Offering: [[Insteon]] Integration via PLM (In OPEN beta test now!) / EZBridge/EZServ

Offering: [[PLCBUS]] Integration
----
'''Nat''' -- Contact Paul Webber to relay messages to Nat
Offering: Nat has some access to some free or low-cost hardware, like TV Tuners, Video Cards, etc., which he can make available for developers actively working on a project.
----
'''Pierre Hansson''' aka Samme -- Contact: 316097 at gmail dot com 
Offering: Wiki-admin
----
'''Lozzo''' -- Contact via [[User talk:Lozzo|his talk page]] 
Offering: wiki admin & documentation
----
'''Chriss''' 
Offering: SVN hosting (see [http://forum.linuxmce.org/index.php?topic=2277.msg13677#msg13677 forum])
----
'''Larry Brigman''' -- Contact larry dot brigman -at- gmail (dot) com 
Offering: Help with documentation, Wiki participation, QA and testing,
Build script work.
----
'''Robert Wilson''' aka rwilson131 -- Contact: rwilson131 at gmail dot com 
Offering: Wiki Documentation and Creation of [[User Manual]]
----
'''Harald Klein''' aka hari -- Contact: hari at vt100 dot at 
Offering: sqlCVS maintenance, code developement, documentation and testing.
----
'''Seven Walter''' aka CylonSeven -- Contact: Seven -at- Apollo Smart Homes (dot) com 
Offering: QA & Testing, Docs, Wiki, Promotions (Central Texas USA). Plenty of hardware for testing: Hybrid w/ RAID, fast MD/HTPC w/ HiDef & Digital Audio out, Firewire & IP cameras, ZWave, etc. 
----
'''Brandon Kruger''' aka bmk789 -- Contact via [[User:bmk789|User page]] 
Offering: wiki moderation & documentation
----
'''Richard''' aka RichardR -- Contact: Richard (at) openbeta (dot) co (dot) uk
Offering: lots of Video editing and production experience for promotions and videos.

'''Roguen''' aka JimmyGosling(Forums), JimmyGos (IIRC) or TheGos (IIRC) -- Contact: Roguen (at) garage68 (dot) com
Offering: Java development, wiki documentation [[User:JimmyGosling|User page]]

== Alumni ==

'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com) 
Paul launched LinuxMCE on March 15, 2007, but is moving on to other projects. He visits us occasionally but after release 0710 will no longer be solely responsible for any aspect of the LinuxMCE release cycle. See [[History|'''History of LinuxMCE''']], for an explanation of why Paul started the project.

[[Category:Development]]
[[Category:Wiki administration]]

Advanced Lighting Settings

2008-03-26T21:20:37Z

JimmyGosling: /* Command Chains */

== Setting Ramp Levels==
Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your device manual to see how this is done.

== Command Chains ==
It is possible to assign a sequence of events to a lighting device. For the purposes of this example the light will be turned off and then on. Note: so far it appears that too long of a sequence will kill an event like movie loading.

Advanced lighting senarios can be applied at several levels. For the purposes of this example, they will be applied to the "play movie" event, also known as the auto generated event "showtime"

1) Using the web admin, select "lighting scenarios" from the left menu

[[Image:LightingScenario1.jpg]]

2) Select the event (by clicking on it) in the room that you would like to apply this advanced scenario to. Again, we are using the auto-generated "showtime" event, however this can be a custom event of your choosing

[[Image:LightingScenario2.jpg]]

3) Pull down the "Edit scenario using wizard" drop down box and select "Advanced Wizard"

[[Image:LightingScenario3.jpg]]

4) On the bottom of this table there is a Device Drop down. Use it to select the lighting device that you will be using and click "Add"

[[Image:LightingScenario4.jpg]]

[[Image:LightingScenario5.jpg]]

5) After this device has been added you can enact any of the supplied changes on it. In this case, 3 actions have been applied to the same device. The sequence of these events can be controls by it's order on the table. This order can be controlled using the buttons on the side.

[[Image:LightingScenario6.jpg]]

Advanced Lighting Settings

2008-03-26T21:18:36Z

JimmyGosling: /* Command Chains */

== Setting Ramp Levels==
Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your device manual to see how this is done.

== Command Chains ==
It is possible to assign a sequence of events to a lighting device. For the purposes of this example the light will be turned off and then on.

Advanced lighting senarios can be applied at several levels. For the purposes of this example, they will be applied to the "play movie" event, also known as the auto generated event "showtime"

1) Using the web admin, select "lighting scenarios" from the left menu

[[Image:LightingScenario1.jpg]]

2) Select the event (by clicking on it) in the room that you would like to apply this advanced scenario to. Again, we are using the auto-generated "showtime" event, however this can be a custom event of your choosing

[[Image:LightingScenario2.jpg]]

3) Pull down the "Edit scenario using wizard" drop down box and select "Advanced Wizard"

[[Image:LightingScenario3.jpg]]

4) On the bottom of this table there is a Device Drop down. Use it to select the lighting device that you will be using and click "Add"

[[Image:LightingScenario4.jpg]]

[[Image:LightingScenario5.jpg]]

5) After this device has been added you can enact any of the supplied changes on it. In this case, 3 actions have been applied to the same device. The sequence of these events can be controls by it's order on the table. This order can be controlled using the buttons on the side.

[[Image:LightingScenario6.jpg]]

File:LightingScenario6.jpg

2008-03-26T21:17:51Z

JimmyGosling:

File:LightingScenario5.jpg

2008-03-26T21:17:41Z

JimmyGosling:

File:LightingScenario4.jpg

2008-03-26T21:17:29Z

JimmyGosling:

Advanced Lighting Settings

2008-03-26T21:04:22Z

JimmyGosling: /* Command Chains */

== Setting Ramp Levels==
Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your device manual to see how this is done.

== Command Chains ==
It is possible to assign a sequence of events to a lighting device. For the purposes of this example the light will be turned off and then on.

Advanced lighting senarios can be applied at several levels. For the purposes of this example, they will be applied to the "play movie" event, also known as the auto generated event "showtime"

1) Using the web admin, select "lighting scenarios" from the left menu

[[Image:LightingScenario1.jpg]]

2) Select the event (by clicking on it) in the room that you would like to apply this advanced scenario to. Again, we are using the auto-generated "showtime" event, however this can be a custom event of your choosing

[[Image:LightingScenario2.jpg]]

3) Pull down the "Edit scenario using wizard" drop down box and select "Advanced Wizard"

[[Image:LightingScenario3.jpg]]

4) On the bottom of this table there is a Device Drop down. Use it to select the lighting device that you will be using and click "Add"

5) After this device has been added you can enact any of the supplied changes on it. In this case, 3 actions have been applied to the same device. The sequence of these events can be controls by it's order on the table. This order can be controlled using the buttons on the side.

Advanced Lighting Settings

2008-03-26T21:03:49Z

JimmyGosling:

== Setting Ramp Levels==
Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your device manual to see how this is done.

== Command Chains ==
It is possible to assign a sequence of events to a lighting device. For the purposes of this example the light will be turned off and then on.

Advanced lighting senarios can be applied at several levels. For the purposes of this example, they will be applied to the "play movie" event, also known as the auto generated event "showtime"

1) Using the web admin, select "lighting scenarios" from the left menu
[[Image:LightingScenario1.jpg]]

2) Select the event (by clicking on it) in the room that you would like to apply this advanced scenario to. Again, we are using the auto-generated "showtime" event, however this can be a custom event of your choosing
[[Image:LightingScenario2.jpg]]

3) Pull down the "Edit scenario using wizard" drop down box and select "Advanced Wizard"
[[Image:LightingScenario3.jpg]]

4) On the bottom of this table there is a Device Drop down. Use it to select the lighting device that you will be using and click "Add"

5) After this device has been added you can enact any of the supplied changes on it. In this case, 3 actions have been applied to the same device. The sequence of these events can be controls by it's order on the table. This order can be controlled using the buttons on the side.

File:LightingScenario3.jpg

2008-03-26T21:02:54Z

JimmyGosling: Advanced Scenario Menu

Advanced Scenario Menu

File:LightingScenario2.jpg

2008-03-26T21:02:27Z

JimmyGosling: Scenario selection

Scenario selection

File:LightingScenario1.jpg

2008-03-26T21:02:00Z

JimmyGosling: Lighting scenario menu

Lighting scenario menu

Advanced Lighting Settings

2008-03-26T20:17:39Z

JimmyGosling: New page: == Setting Ramp Levels== Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your d...

== Setting Ramp Levels==
Currently ramp levels cannot be set in LMCE (this may change soon). The device ramp level can be changed manually however, at the device. Please reference your device manual to see how this is done.

== Command Chains ==
It is possible to assign a sequence of events to a lighting device. For the purposes of this example the light will be turned off and then on.

Advanced lighting senarios can be applied at several levels. For the purposes of this example, they will be applied to the "play movie" event, also known as the auto generated event "showtime"

1) Using the web admin, select "lighting scenarios" from the left menu

2) Select the event (by clicking on it) in the room that you would like to apply this advanced scenario to. Again, we are using the auto-generated "showtime" event, however this can be a custom event of your choosing

3) Pull down the "Edit scenario using wizard" drop down box and select "Advanced Wizard"

4) On the bottom of this table there is a Device Drop down. Use it to select the lighting device that you will be using and click "Add"

5) After this device has been added you can enact any of the supplied changes on it. In this case, 3 actions have been applied to the same device. The sequence of these events can be controls by it's order on the table. This order can be controlled using the buttons on the side.

Running the Insteon PLM Driver for the First Time

2008-03-26T19:58:34Z

JimmyGosling:

[[Category: GSD| ]]
[[Category: Automation| ]]
[[Category: Tutorials| ]]
==Monitoring the log==

Because this is a BETA driver, I recommend that everyone who runs this, please monitor the log for errors.

To monitor the log:
:* Open WebAdmin
:* On the Left pane, select 'Generic Serial Devices'
:* On the Insteon PLM Device, click 'Advanced'
:* in the TOP RIGHT, click 'FOLLOW LOG'

This will pop up a new window with the log processing in real time.
When you quick reload the router, I'd recommend pressing F5 on the Log window to clear out the old history.
During the initialization of the GSD, it shows all the code (over 2000 lines) before it actually 'starts' (hence the refresh)

==Initial Device Setup==
===Insteon Devices===
====Running for the first time====
Initially, the driver needs at least ONE active lighting device. The driver will download this device's database and attempt to extract other Insteon ID's from it. Then it goes out and PINGS those devices in turn, to find out what kind of device they are. Once that is finished, it attempts to download each device's database, in turn, looking for more Insteon devices. This procedure, nicknamed 'Spidering', continues until all devices and device links are recognized. Once this 'Spider' is complete, the driver reports all detected devices, to LinuxMCE.

====Running for the Second time====
Once the devices have been added to LinuxMCE, they can now hold their configuration. Even though all the databases were downloaded during the first run, the devices themselves did not exist, and therefore, we can't store their configuration during the first run. This happens on the second run. You will now see a 'Configuration' field in each device. This holds the device's Type, Database Delta, and all ALDB records (the remote database) encoded into a long string.

If, at any time, you want to re-download a device's database, simple delete the configuration string. Upon next reload, the driver will go out and redownload the remote database.
====Running after the first two times====
Part of the configuration string is something called a DATABASE DELTA. It's basically a byte that increments each time the remote database is altered.

I store the Database Delta when I read the complete database. Then, upon router reloads, I ONLY read the database delta from the device. I compare that with the value stored in it's configuration, and if they are the same, I know I don't need to do any further downloads to that device.

This speeds up initialization dramatically. Sending 1 command vs sending 8 commands per record, and on average, more than 2 records.

:Currently, I cannot figure out how to call the Lighting Wizard. Ideally, this would run at this point to allow simple configuration of all the lighting devices.
:Alas, you'll have to use webAdmin to select Rooms and Floorplan Object Types. (don't forget this, it's important!)

Note: The Driver will automatically determine the type of device. If it's a Dimmer, it will assign it to Lighting Switch (dimmable). If it's a switched device(on/off), it will assign it to Lighting Device (ON/OFF). If it's a EZRain1 Sprinkler controller, it will assign it to an Irrigation device! (This may need some debugging)

===X10 Devices===
X10 Devices must all be added manually to the Lighting Devices. X10 devices are truly 'dumb' devices, and hence, don't have databases to download.

X10 Motion Sensors can be used as Security Devices. They report an ON command when motion is sensed, and an OFF when no motion is sensed (within a timeout period)

X10 and Insteon can co-exist. (You can have a mix of devices)

==Bidirectional Communication==
The Insteon devices support Full 2-way communication. You can verify this by watching the logs as you turn a light switch on/off or dim/brighten a light switch.

X10 Devices support 2-way communication of ON/OFF commands only. Support for more commands can be implemented with little trouble. (I had to get the beta out)

==Error Detection==

As with all communication systems, there's always errors. Power Line Communication errors are handled in this fashion:
:* Process IDLE triggers about once every 2-3 seconds (I think)
:* Commands will TIMEOUT on the FIFTH Process IDLE (watch the log, you'll see)
:* When a TIMEOUT is detected, the command is retried 3 times before FAILING.
:* When a command FAILS, the driver simply discards the command.

==Sample Setup==
[[Image:GenericDevice.JPG]]
This is a picture of the PLM setup. This is what it should look like after you have completed the steps detailed in this wiki. Your "com port on PC" will likely be different as well as the room name (should be the room containing your core)

[[Image:LightingDevice.JPG]]
This second picture is for two devices. the first the light dimmer switch, and the second is actually switchable wall receptical which in this setup is used for floor lights. (NOTE: Soon there will be an automatic setup, but current these were set up manually)

The floorplan info is not needed, this is just the map point for your floorplan. (you may not have/want/need one)
The PK_FloorplanObjectType will be setup when you add the new device and pick a template
The port channel number (also referred to as the Insteon ID) is a hex code you'll find on the device itself. (a small sticker at the bottom)

Some additional information concerning the configuration string:
As noted in the second image device configuration strings: This field is added by ddamron's driver, so you don't have to put anything there.
fyi:

:* 00-01 = Device Cat
:* 02-03 = Device Subcat
:* 04-05 = Database Delta

after the ******** starts the ACTUAL DEVICE's COMPLETE DATABASE (in the form it's stored in the device)

For this example: Device # 75 is Insteon Devcat 01 (Lighting Control Dimming) and subcat 04 = SwitchLinc V2 Dimmer 1000W [2476DH]
Your Device # 76 is Insteon Devcat 02(Lighting Control Switched) and subcat 08 = OutletLinc [2473S]

To activate the 'spider', reset the configuration line, (delete it). When the router is reloaded, it compared the database delta (04-05) with the database delta in the remote device. If they are different, it downloads the complete database automagically, then examines that database for links it doesn't know about, attempts to connect to them, adds them as 'children', and downloads their device databases, and continues like so, until it doesn't find any new records.

==Advenced Setup==
[[Advanced Lighting Settings]]

Running the Insteon PLM Driver for the First Time

2008-03-17T14:55:21Z

JimmyGosling: /* Sample Setup */

Running the Insteon PLM Driver for the First Time

2008-03-17T14:52:49Z

JimmyGosling: /* Sample Setup */

[[Category: GSD| ]]
[[Category: Automation| ]]
[[Category: Tutorials| ]]
==Monitoring the log==

Because this is a BETA driver, I recommend that everyone who runs this, please monitor the log for errors.

To monitor the log:
:* Open WebAdmin
:* On the Left pane, select 'Generic Serial Devices'
:* On the Insteon PLM Device, click 'Advanced'
:* in the TOP RIGHT, click 'FOLLOW LOG'

This will pop up a new window with the log processing in real time.
When you quick reload the router, I'd recommend pressing F5 on the Log window to clear out the old history.
During the initialization of the GSD, it shows all the code (over 2000 lines) before it actually 'starts' (hence the refresh)

==Initial Device Setup==
===Insteon Devices===
====Running for the first time====
Initially, the driver needs at least ONE active lighting device. The driver will download this device's database and attempt to extract other Insteon ID's from it. Then it goes out and PINGS those devices in turn, to find out what kind of device they are. Once that is finished, it attempts to download each device's database, in turn, looking for more Insteon devices. This procedure, nicknamed 'Spidering', continues until all devices and device links are recognized. Once this 'Spider' is complete, the driver reports all detected devices, to LinuxMCE.

====Running for the Second time====
Once the devices have been added to LinuxMCE, they can now hold their configuration. Even though all the databases were downloaded during the first run, the devices themselves did not exist, and therefore, we can't store their configuration during the first run. This happens on the second run. You will now see a 'Configuration' field in each device. This holds the device's Type, Database Delta, and all ALDB records (the remote database) encoded into a long string.

If, at any time, you want to re-download a device's database, simple delete the configuration string. Upon next reload, the driver will go out and redownload the remote database.
====Running after the first two times====
Part of the configuration string is something called a DATABASE DELTA. It's basically a byte that increments each time the remote database is altered.

I store the Database Delta when I read the complete database. Then, upon router reloads, I ONLY read the database delta from the device. I compare that with the value stored in it's configuration, and if they are the same, I know I don't need to do any further downloads to that device.

This speeds up initialization dramatically. Sending 1 command vs sending 8 commands per record, and on average, more than 2 records.

:Currently, I cannot figure out how to call the Lighting Wizard. Ideally, this would run at this point to allow simple configuration of all the lighting devices.
:Alas, you'll have to use webAdmin to select Rooms and Floorplan Object Types. (don't forget this, it's important!)

Note: The Driver will automatically determine the type of device. If it's a Dimmer, it will assign it to Lighting Switch (dimmable). If it's a switched device(on/off), it will assign it to Lighting Device (ON/OFF). If it's a EZRain1 Sprinkler controller, it will assign it to an Irrigation device! (This may need some debugging)

===X10 Devices===
X10 Devices must all be added manually to the Lighting Devices. X10 devices are truly 'dumb' devices, and hence, don't have databases to download.

X10 Motion Sensors can be used as Security Devices. They report an ON command when motion is sensed, and an OFF when no motion is sensed (within a timeout period)

X10 and Insteon can co-exist. (You can have a mix of devices)

==Bidirectional Communication==
The Insteon devices support Full 2-way communication. You can verify this by watching the logs as you turn a light switch on/off or dim/brighten a light switch.

X10 Devices support 2-way communication of ON/OFF commands only. Support for more commands can be implemented with little trouble. (I had to get the beta out)

==Error Detection==

As with all communication systems, there's always errors. Power Line Communication errors are handled in this fashion:
:* Process IDLE triggers about once every 2-3 seconds (I think)
:* Commands will TIMEOUT on the FIFTH Process IDLE (watch the log, you'll see)
:* When a TIMEOUT is detected, the command is retried 3 times before FAILING.
:* When a command FAILS, the driver simply discards the command.

==Sample Setup==
[[Image:GenericDevice.JPG]]
This is a picture of the PLM setup. This is what it should look like after you have completed the steps detailed in this wiki. Your "com port on PC" will likely be different as well as the room name (should be the room containing your core)

[[Image:LightingDevice.JPG]]
This second picture is for two devices. the first the light dimmer switch, and the second is actually switchable wall receptical which in this setup is used for floor lights. (NOTE: Soon there will be an automatic setup, but current these were set up manually)

The floorplan info is not needed, this is just the map point for your floorplan. (you may not have/want/need one)
The PK_FloorplanObjectType will be setup when you add the new device and pick a template
The port channel number (also referred to as the Insteon ID) is a hex code you'll find on the device itself. (a small sticker at the bottom)

Some additional information concerning the configuration string:
As noted in the second image device configuration strings: This field is added by ddamron's driver, so you don't have to put anything there.
fyi:
00-01 = Device Cat
02-03 = Device Subcat
04-05 = Database Delta
after the ******** starts the ACTUAL DEVICE's COMPLETE DATABASE (in the form it's stored in the device)

For this example: Device # 75 is Insteon Devcat 01 (Lighting Control Dimming) and subcat 04 = SwitchLinc V2 Dimmer 1000W [2476DH]
Your Device # 76 is Insteon Devcat 02(Lighting Control Switched) and subcat 08 = OutletLinc [2473S]

To activate the 'spider', reset the configuration line, (delete it). When the router is reloaded, it compared the database delta (04-05) with the database delta in the remote device. If they are different, it downloads the complete database automagically, then examines that database for links it doesn't know about, attempts to connect to them, adds them as 'children', and downloads their device databases, and continues like so, until it doesn't find any new records.

File:LightingDevice.JPG

2008-03-17T14:46:35Z

JimmyGosling: this is a sample lighting device setup for insteon

this is a sample lighting device setup for insteon

Running the Insteon PLM Driver for the First Time

2008-03-17T14:45:58Z

JimmyGosling:

File:GenericDevice.JPG

2008-03-17T14:45:09Z

JimmyGosling: This is the sample of the Generic Device setup for Insteon

This is the sample of the Generic Device setup for Insteon

Insteon - Setting Up PLM Template

2008-02-29T21:17:12Z

JimmyGosling: /* Adding a New Template */

[[Category:Tutorials| ]]
[[Category:Automation| ]]
[[Category:GSD| ]]
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron
:Bear with me, this is my first wiki..
:--ddamron 02:52, 6 January 2008 (MST)
Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver Complete, and in Release Candidate 1. I'm sure there are still a few bugs(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. (unless it makes it into the 0710 release!)

==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==
* Log into the webadmin
* select Interfaces(under Devices using the left hand menu), or by using Wizard>Devices>Interfaces (using the top menu)
* click Add device (loads Pick Device Template popup)

===Adding Smarthome Manufacturer===
:with the Pick Device Template Popup:
:* click Add Manufacturer (loads Add Manufacturer popup)

::with the Add Manufacturer popup:
::* 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'.
:* Click Add device Template (popup changes to Add model)
:* 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'
::* 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)
<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-02-29T21:13:30Z

JimmyGosling: /* Setting up the Template */

[[Category:Tutorials| ]]
[[Category:Automation| ]]
[[Category:GSD| ]]
:''' UPDATED: 13-FEB-08 X10 Support fixed!
'''
:--ddamron
:Bear with me, this is my first wiki..
:--ddamron 02:52, 6 January 2008 (MST)
Here are the steps to create an Insteon PLM Template. This driver is written entirely in Ruby. Please consider this driver Complete, and in Release Candidate 1. I'm sure there are still a few bugs(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. (unless it makes it into the 0710 release!)

==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==
* Log into the webadmin
* select Interfaces(under Devices using the left hand menu), or by using Wizard>Devices>Interfaces (using the top menu)
* click Add device (loads Pick Device Template popup)

===Adding Smarthome Manufacturer===
:with the Pick Device Template Popup:
:* click Add Manufacturer (loads Add Manufacturer popup)

::with the Add Manufacturer popup:
::* 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'.
:* Click Add device Template (popup changes to Add model)
:* 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
:* 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'
::* 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)
<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]]