LinuxMCE - User contributions [en]

Use my own pictures in the Screen Saver

2008-05-18T08:46:23Z

Justnulling2:

The photo screen saver does a great job and ensures that media is displayed all the time, even if you just happen to be listening to music.
By default, the photos come from flickr and are downloaded regularly to your local drives.

But it would be nice to use your own photos in this screen saver, perhaps alongside the flickr ones or perhaps as a replacement.

This is a guide to do just that...

'''Quick Update: In 710B4 it's possible to select photos for screensaver in much easier way. See Files & Media -> Screensaver option...'''''
== Italic text ==
''

=== Background ===
All media on your linuxMCE system is catalogued and stored in a database. The database allows for attributes to be stored for each media file.
One such attribute is "Screen Saver For MD". By setting this attribute this picture will be used as one of the pictures for the Media Director Screen Saver.
Photos are selected by random from all the photos that exist with the "Screen Saver For MD" attribute set.

There are a number of ways to set this attribute for individual files. They are;
* Setting an attribute from the web admin screens
* Setting an attribute from the command line
* Assigning a picture to the screen saver from the Orbiter

=== Setting an attribute from the web admin screens ===
'''NOTE: Pictures must be smaller than 1240 x 1240. Hope this saves some a bit of fustration. '''
There is a section on the web admin screens that allow the setting of attributes for media.
It is available under Files & Media -> Media Files Sync

The left hand window frame gives a tree view into the directory structure of home/public/data.
Typically photos will be stored under the pictures sub-directory.
The right hand window frame gives a view of the files found and their status with relation to linuxMCE's database.

Firstly determine the pictures you wish to use, and locate them using the directory browser.
Then ensure that the files are ticked to indicate existing in both the database and on disk. If not then choose the type as 'LinuxMCE Pictures' and press the 'Add to database' button.

Once they are added to the database you should be able to select them and see the details (metadata) associated with them.

Part of the details include any currently set attributes for the file, which you can choose to Edit or Remove.
There is also a section to Add Attributes. Only attribute that have been associated with the particular file types can be selected from the drop down box.
''Note: If you do not see 'Screen Saver For MD' in this box then you will need to Associate the attribute.''

Select the attribute 'Screen Saver For MD' and enter or select the Attribute name value of '*'. Then press the Add button next to the box and your done.

A quick reload router should be enough to ensure that files are refreshed from the database and you should start to see your selected picture as one of the screen saver files.

==== Associate the attribute ====

Unfortunately by default this attribute has not been associated with the picture media type. Perhaps a bug, who knows. Anyway, to associate it you will need to run the following piece of SQL to put the required association into the database.

You will need to get to the command prompt of your CORE machine and from the command prompt (your default user should be fine) run:

mysql -u root -D pluto_media -N -e "INSERT into MediaType_AttributeType(EK_MediaType, FK_AttributeType, Identifier, CombineAsOne) values(7,30,0,1)"

Do a quick reload router and then the attribute should show up in the dropdown box under add attributes

''Note: If someone knows a better way to do this or can see some adverse side effects please update''

=== Setting an attribute from the command line ===

There is functionality built into the system that allows an attribute to be set through a sequence of Command Messages sent to the right device. This is what the flickr.pl script uses to assign the downloaded files the right attributes.
The commands can be executed from anything that can send linuxMCE messages (including the web admin screens) but this method will utilise the MessageSend utility available from the linux command line.

You will need to firstly determine the full filename and path for the file you wish to set the attribute for.
This method assumes that the file has already been sync'd with linuxMCE and exists in the data base.

The first command queries the database for the file ID of a particular filename.

The second command assigns an attribute type/value to the returned file ID

* Logon to your linuxMCE CORE and get to the linux command prompt
* execute the following command
/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 <pathtofile>

Substituting your full path to the file where is says <pathtofile>

''eg: /usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 /home/public/data/pictures/sample.jpg''

You should get a response something like this:
0:OK
145:11392

The number next to the '145:' is the important part. This is the fileID. If this is zero then your command has not found a match in the database and you may need to take other measures to ensure that the database is sync'd with your files.

* Now execute the following command
/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 <fileID> 122 30 5 "*"

Substituting the fileID that you just discovered where it says <fileID>

''eg: /usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 11392 122 30 5 "*"''

* You can then repeat for any other files that you want to use

Below is a simple script which takes all the jpg files in the current directory, resizes them
to a screensaver safe size, and then marks them as being usable by the screensaver. There is no error checking and it shrinks all the images in place, so make sure you make a copy of the images first and place them in another directory. Note: this would normally be run on a directory below /home/public/data/pictures.

#!/bin/bash

# Copyright 2008 (c) Daniel Kristjansson
# You may use this for any purpose whatsoever, so long as you preserve the copyright notice.
# You may relicense this and add your own contributions freely.
# Use this at your own risk.

MAX_SIZE=1024 #don't set it bigger than 1240

for FILE in `ls *.jpg *.JPG` ; do
PWD=`pwd`
FILEID=`/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 $PWD/$FILE | tail -n 1 | sed -e 's/^.*://g'`
RES=`identify -verbose $FILE | head -n1 | awk '{ print $3 }'`
WIDTH=`echo $RES | sed -e 's/x.*//g'`
HEIGHT=`echo $RES | sed -e 's/.*x//g'`

NEW_WIDTH=$WIDTH
NEW_HEIGHT=$HEIGHT
if [ $WIDTH -gt $MAX_SIZE -o $HEIGHT -gt $MAX_SIZE ] ; then
if [ $WIDTH -gt $HEIGHT ] ; then
NEW_WIDTH=$MAX_SIZE
NEW_HEIGHT=`expr $NEW_WIDTH "*" $HEIGHT "/" $WIDTH`
else
NEW_HEIGHT=$MAX_SIZE
NEW_WIDTH=`expr $NEW_HEIGHT "*" $WIDTH "/" $HEIGHT`
fi
fi

if [ $WIDTH != $NEW_WIDTH -o $HEIGHT != $NEW_HEIGHT ] ; then
echo file id: $FILEID old dim: $RES : w $WIDTH : h $HEIGHT \-\> new dim: $NEW_WIDTH $NEW_HEIGHT
convert $FILE -resize ${NEW_WIDTH}x${NEW_HEIGHT}! resized_$FILE
mv resized_$FILE $FILE
else
echo file id: $FILEID old dim: $RES : w $WIDTH : h $HEIGHT
fi

/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 ${FILEID} 122 30 5 "*"
done

=== Assigning a picture to the screen saver from the Orbiter ===

Sounds like a good idea??? Unfortunately it is not currently possible, but I thought that this sounded like a logical thing to do so have put this placeholder in.

Essentially, screens in the Orbiter have buttons that trigger message Command to be sent. So setting up a button in the Picture view screen "add to Screen Saver" should be quite straight forward.

If you feel like getting involved maybe this is somewhere you can start.....

NOTE: Pictures must be smaller than 1240 x 1240. Hope this saves some a bit of fustration.

[[Category: Tutorials]]

Use my own pictures in the Screen Saver

2008-05-18T08:45:45Z

Justnulling2:

Use my own pictures in the Screen Saver

2008-05-18T08:44:18Z

Justnulling2:

The photo screen saver does a great job and ensures that media is displayed all the time, even if you just happen to be listening to music.
By default, the photos come from flickr and are downloaded regularly to your local drives.

But it would be nice to use your own photos in this screen saver, perhaps alongside the flickr ones or perhaps as a replacement.

This is a guide to do just that...

'''Quick Update: In 710B4 it's possible to select photos for screensaver in much easier way. See Files & Media -> Screensaver option...'''''
== Italic text ==
''

=== Background ===
All media on your linuxMCE system is catalogued and stored in a database. The database allows for attributes to be stored for each media file.
One such attribute is "Screen Saver For MD". By setting this attribute this picture will be used as one of the pictures for the Media Director Screen Saver.
Photos are selected by random from all the photos that exist with the "Screen Saver For MD" attribute set.

There are a number of ways to set this attribute for individual files. They are;
* Setting an attribute from the web admin screens
* Setting an attribute from the command line
* Assigning a picture to the screen saver from the Orbiter

=== Setting an attribute from the web admin screens ===
'''NOTE: Pictures must be smaller than 1240 x 1240. Hope this saves some a bit of fustration. '''
There is a section on the web admin screens that allow the setting of attributes for media.
It is available under Files & Media -> Media Files Sync

The left hand window frame gives a tree view into the directory structure of home/public/data.
Typically photos will be stored under the pictures sub-directory.
The right hand window frame gives a view of the files found and their status with relation to linuxMCE's database.

Firstly determine the pictures you wish to use, and locate them using the directory browser.
Then ensure that the files are ticked to indicate existing in both the database and on disk. If not then choose the type as 'LinuxMCE Pictures' and press the 'Add to database' button.

Once they are added to the database you should be able to select them and see the details (metadata) associated with them.

Part of the details include any currently set attributes for the file, which you can choose to Edit or Remove.
There is also a section to Add Attributes. Only attribute that have been associated with the particular file types can be selected from the drop down box.
''Note: If you do not see 'Screen Saver For MD' in this box then you will need to Associate the attribute.''

Select the attribute 'Screen Saver For MD' and enter or select the Attribute name value of '*'. Then press the Add button next to the box and your done.

A quick reload router should be enough to ensure that files are refreshed from the database and you should start to see your selected picture as one of the screen saver files.

==== Associate the attribute ====

Unfortunately by default this attribute has not been associated with the picture media type. Perhaps a bug, who knows. Anyway, to associate it you will need to run the following piece of SQL to put the required association into the database.

You will need to get to the command prompt of your CORE machine and from the command prompt (your default user should be fine) run:

mysql -u root -D pluto_media -N -e "INSERT into MediaType_AttributeType(EK_MediaType, FK_AttributeType, Identifier, CombineAsOne) values(7,30,0,1)"

Do a quick reload router and then the attribute should show up in the dropdown box under add attributes

''Note: If someone knows a better way to do this or can see some adverse side effects please update''

=== Setting an attribute from the command line ===

There is functionality built into the system that allows an attribute to be set through a sequence of Command Messages sent to the right device. This is what the flickr.pl script uses to assign the downloaded files the right attributes.
The commands can be executed from anything that can send linuxMCE messages (including the web admin screens) but this method will utilise the MessageSend utility available from the linux command line.

You will need to firstly determine the full filename and path for the file you wish to set the attribute for.
This method assumes that the file has already been sync'd with linuxMCE and exists in the data base.

The first command queries the database for the file ID of a particular filename.

The second command assigns an attribute type/value to the returned file ID

* Logon to your linuxMCE CORE and get to the linux command prompt
* execute the following command
/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 <pathtofile>

Substituting your full path to the file where is says <pathtofile>

''eg: /usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 /home/public/data/pictures/sample.jpg''

You should get a response something like this:
0:OK
145:11392

The number next to the '145:' is the important part. This is the fileID. If this is zero then your command has not found a match in the database and you may need to take other measures to ensure that the database is sync'd with your files.

* Now execute the following command
/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 <fileID> 122 30 5 "*"

Substituting the fileID that you just discovered where it says <fileID>

''eg: /usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 11392 122 30 5 "*"''

* You can then repeat for any other files that you want to use

Below is a simple script which takes all the jpg files in the current directory, resizes them
to a screensaver safe size, and then marks them as being usable by the screensaver. There is no error checking and it shrinks all the images in place, so make sure you make a copy of the images first and place them in another directory. Note: this would normally be run on a directory below /home/public/data/pictures.

#!/bin/bash

# Copyright 2008 (c) Daniel Kristjansson
# You may use this for any purpose whatsoever, so long as you preserve the copyright notice.
# You may relicense this and add your own contributions freely.
# Use this at your own risk.

MAX_SIZE=1024 #don't see bigger then 1240
for FILE in `ls *.jpg *.JPG` ; do
PWD=`pwd`
FILEID=`/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 819 13 $PWD/$FILE | tail -n 1 | sed -e 's/^.*://g'`
RES=`identify -verbose $FILE | head -n1 | awk '{ print $3 }'`
WIDTH=`echo $RES | sed -e 's/x.*//g'`
HEIGHT=`echo $RES | sed -e 's/.*x//g'`

NEW_WIDTH=$WIDTH
NEW_HEIGHT=$HEIGHT
if [ $WIDTH -gt $MAX_SIZE -o $HEIGHT -gt $MAX_SIZE ] ; then
if [ $WIDTH -gt $HEIGHT ] ; then
NEW_WIDTH=$MAX_SIZE
NEW_HEIGHT=`expr $NEW_WIDTH "*" $HEIGHT "/" $WIDTH`
else
NEW_HEIGHT=$MAX_SIZE
NEW_WIDTH=`expr $NEW_HEIGHT "*" $WIDTH "/" $HEIGHT`
fi
fi

if [ $WIDTH != $NEW_WIDTH -o $HEIGHT != $NEW_HEIGHT ] ; then
echo file id: $FILEID old dim: $RES : w $WIDTH : h $HEIGHT \-\> new dim: $NEW_WIDTH $NEW_HEIGHT
convert $FILE -resize ${NEW_WIDTH}x${NEW_HEIGHT}! resized_$FILE
mv resized_$FILE $FILE
else
echo file id: $FILEID old dim: $RES : w $WIDTH : h $HEIGHT
fi

/usr/pluto/bin/MessageSend dcerouter -targetType template -r -o 0 2 1 391 145 ${FILEID} 122 30 5 "*"
done

=== Assigning a picture to the screen saver from the Orbiter ===

Sounds like a good idea??? Unfortunately it is not currently possible, but I thought that this sounded like a logical thing to do so have put this placeholder in.

Essentially, screens in the Orbiter have buttons that trigger message Command to be sent. So setting up a button in the Picture view screen "add to Screen Saver" should be quite straight forward.

If you feel like getting involved maybe this is somewhere you can start.....

NOTE: Pictures must be smaller than 1240 x 1240. Hope this saves some a bit of fustration.

[[Category: Tutorials]]

Cisco 7970

2008-05-15T18:49:26Z

Justnulling2:

[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]

== Preface ==
[[Image:Cisco7909.JPG]]

LinuxMCE allows the use of many devices as [[Orbiters]]. One of them is the [http://www.cisco.com/en/US/products/hw/phones/ps379/ps5440/index.html CISCO 7970]. You can use it to control your home as well as to make calls.

To add a new CISCO 7970 phone as an Orbiter follow these simple instructions (from information in the [http://forum.linuxmce.org/ LinuxMCE support forum]).

== Preparation ==

CISCO 7970 phone is plug-in-play device; LinuxMCE adds it automatically when it is plugged into the network. But first, we have to make some preparations. Run an Orbiter. Be sure that no others tasks are running.
Check the DHCP setting of your phone. It should be something like that: "get IP via DHCP and no alternative servers".
Check the range of MAC addresses:
#Go to Advanced --> Configuration --> Device Template.
#Chose manufacturer CISCO. You should see in the right list at least two models: 7970 and 7960.
#Press the button 'Show model'.
#On the opened window check 'Range MAC addresses'. The range contains two big decimal digits. To get correct range for your phone first see its MAC address. A MAC address is six groups of two hexadecimal digits, separated by hyphens (-) or colons (:). The first three groups identify a maker. You leave them and fill the rest by 0 and F. For example, if MAC is 00:16:78:CD:01:D8 its range will be 00:16:78:00:00:00 - 00:16:78:FF:FF:FF. After that you should convert those two values into LinuxMCE representation. To do that run a script /usr/pluto/bin/convert_mac and pass the hexadecimal values as parameters:
/usr/pluto/bin/convert_mac 00:16:78:00:00:00
/usr/pluto/bin/convert_mac 00:16:78:FF:FF:FF
:As result you will get two big decimal digits. Add them to the phone template and store.
If you have problems with phone installation, it may be related to firmware. The phone should have the latest firmware upgrade. (I didn't have any problem with existing firmware on my CISCO 7970, though).

Note for '''CISCO 7960 SIP''' users: if your phone fails to register with asterisk then edit /tftpboot/SIPDefault.cnf and append
nat_enable: 1

== Installation ==

#Plug the phone power and network cable. Note if you have two network cards on your core you should plug network cable in the right switch.
#During boot of the phone after 2-3 minutes you should see on the Orbiter a message about new device with your phone MAC address was detected. You should click by caption "Cisco 7970" below that.
#After that the phone should be registered with asterisk and you can see a normal CISCO screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for CISCO7970.
#When this operation finishes you'll see a message on the Orbiter screen. Make a quick reload of router (Wizard -- Reboot -- Quick Reload Router. I also rebooted CISCO 7970 because I didn't see anything in the menu Services).
#Now go to menu Services on CISCO 7970 and chose Orbiter.

== Troubleshooting ==
*Problem: Phone boots successfully but there is no any message on the Orbiter's screen.
*Solution: If the message doesn't appear check MAC addresses range.

== Some useful tips ==
*To reset a Network configuration of CISCO79xx go to menu 'Network Setting' and press the following sequence of buttons:
**#**
*To check network communications between CISCO7970 and CORE run tcpdump on the CORE:
tcpdump -i eth1 [CISCO7970 IP Address]
or to see detailed packets information:
tcpdump -i -vv eth1 [CISCO7970 IP Address]

Email suggestions to: stepanov.michael [at] gmail [dot] com or leave a comment.

==Add Directory buttons to Cisco IP Phone==

=== Download ===
Download the files here: [http://www.unit-e.cc/~thom/Directory.zip http://www.unit-e.cc/~thom/Directory.zip]

=== Synopsis ===

This set of files adds a working Directory for your Cisco IP phone. It has been tested on my Cisco 7970 phone, but does not use any additional features, so it should work on any of the other Cisco IP phones that support XML services, such as the Cisco 7960.

It adds the following Features:

* Directory button now works!
* Works with Contacts from the Pluto phone directory
* Paginates them based on # of entries in phone book
* Shows the phone type.

=== Installing this Patch ===

* Unpack the files to the pluto-admin directory. (/var/www/pluto-admin/)
* edit the file /tftpboot/SEPDefault7970.cnf.xml (it just needs to be the default xml for your cisco phone, adjust as needed.)
** Find the <directoryURL></directoryURL> tags, and place '''http://192.168.80.1/pluto-admin/directory.php''' between them.
* Reboot the phone by pressing the settings button, and pressing the following button sequence '''**#**'''

Once the phone boots, try the directory by pressing the Directory button!

If there are any problems, let me know --[[User:Tschak909|Tschak909]] ( thom.cherryhomes (at) gmail (dot) com ).

SMB / Samba NAS Configurations

2008-05-15T18:34:26Z

Justnulling2:

[[How to setup Samba with two workgroups?]]
[[How to setup Samba to follow symbolic links?]]

Problem: we have shares for each users. if I want to access it from Windows, I have to enter password. if I don't this on first access, windows won't ask my anymore to enter password and just denies access. How can I force windows, to reenter password for share ???

If your samba password doesn't work then run this on core to update your samba password:
sudo smbpasswd pluto_USER
where USER is your username. For instance to change john's password run sudo smbpasswd pluto_john

[[Category: Tutorials]]

Insteon - Setting Up PLM Template

2008-04-02T20:50:28Z

Justnulling2: /* Adding a Code Group */

[[Category:Tutorials| ]]
[[Category:Automation| ]]
[[Category:GSD| ]]
:''' UPDATED: 11-MAR-08 Many bugs fixed, X10 fixes...
:''' 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'

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

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

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

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

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

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

:* Scroll down to the bottom of the popup window and click Save
:* Click Close
:* Modify the SECOND LAST LINE of this script (88_InsteonPLM.sh) and change the LAST number to your Template ID.
:* add this script file to /usr/pluto/pnp (88_InsteonPLM.sh)
<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]]