https://wiki.universal-devices.com/api.php?action=feedcontributions&user=Yardman+49&feedformat=atomUniversal Devices, Inc. Wiki - User contributions [en]2024-03-29T05:35:40ZUser contributionsMediaWiki 1.41.0https://wiki.universal-devices.com/index.php?title=Talk:ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3737Talk:ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-20T00:51:07Z<p>Yardman 49: </p>
<hr />
<div>Mike:<br />
<br />
A couple of things:<br />
<br />
- Step 5 in your procedure: At least as of version 2.6, there is no need to "Remove" the old device after you have finished with the "Replace"; the replace process does it automatically.<br />
<br />
- Do you want me to add the two "Known Issues" to this page? Since this is supposed to be a "How-To" that waks you through procedures, then the most current information should be present. Users shouldn't have to go to another section to see these warnings, as they will probably miss them. Also, if they don't follow these two additional steps, their Remotelincs that may be controllers for the replaced device won't work properly, nor will there programs that used to use the replaced devices.<br />
<br />
Frank.</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Known_Issues&diff=3602ISY-99i/ISY-26 INSTEON:Known Issues2008-01-18T13:36:57Z<p>Yardman 49: </p>
<hr />
<div><br />
==Using "Replace....with" for Insteon Devices==<br />
<br />
'''Known issue 1:''' As of version 2.6 firmaware, there is no requester message directing the user to put into "Programming Mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no requester message is presented.<br />
<br />
The RemoteLinc is placed into Programming mode by simultaneously holding down the "Bright" and "Dim" buttons for 10 seconds or until the status light begins flashing.<br />
<br />
<br />
'''Known Issue 2:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
<br />
<br />
----<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:INSTEON_Device&diff=3601ISY-99i/ISY-26 INSTEON:INSTEON Device2008-01-18T13:34:30Z<p>Yardman 49: </p>
<hr />
<div>This device node is located as a branch under the ISY node. Expanding the ISY node (My Lighting), will show the devices within the network.<br />
<br />
<br />
[[Image:ISY Node Expanded.PNG|frame|none|''Figure 33. ISY Node branch expanded showing devices.'']]<br />
<br />
<br />
Selecting a device in the INSTEON Device branch will show the device properties in the view pane. <br />
The pane will also have controls by means of a slider or buttons. These controls allow the user to directly control and setup the device via the computer. Currently the ISY supports all SmartHome lights, switches and dimmers. Depending on the device that is linked to the system, you will be presented with the permissible control action the system can help you perform and automate. For example in Figure 32 the “Entry-1 Overhead” light was selected and its properties are shown in the view pane.<br />
On level and ramp rate adjustment are controlled with a slider control. On level sets the amount of light within 0 and 100%, where 100% is full brightness or ON. Ramp rate sets the amount of time it takes to reach the set ON level from OFF to ON and from ON to OFF. <br />
<br />
Setting the device properties via the ISY does not require you to press the set button on the device. Unlike manually setting the ramp rates and ON levels, you need not press the Set Button to store the set values. All you need to do is set the sliders to the desired level or ramp rates.<br />
<br />
<br />
[[image:Device Properties.PNG|frame|none|''Figure 34 – Device Properties'']]<br />
<br />
<br />
Buttons available are ON, Fast ON, OFF, Fast OFF, Brighten and Dim. <br />
ON or OFF Buttons, turns on/off the lights using the preset ON/OFF levels and ramp rate. This action is similar to pressing the switch once.<br />
<br />
Fast ON/OFF Buttons, turns on/off the lights to full ON/OFF at the fastest ramp rate. This action is the similar to quickly tapping the switch twice.<br />
<br />
Brighten and Dim Buttons, adjusts the light level by 5% for every click of the button. If you press and hold the button the level will change at 5% step for every second it is held.<br />
<br />
Mutually Exclusive Button allows you to group the buttons in Exclusive OR state. This button select is only available with the KeypadLinc Devices. The idea is you group a set of buttons so that only one button will be in ON state at any time. For example, you group buttons A and B, where A is assigned as All ON and B as All OFF. The state of the status LED in each button will be as follows:<br />
<br />
<br />
<Table border=1 cellspacing=0 cellpadding=0 style='margin-left:.2in'><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'> '''ACTION''' </td><br />
<td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'> '''REACTION''' </td></tr><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'>When All ON (button A) is pressed the status LED is Lit.</td> <br />
<td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'>Button B LED is not Lit.</td></tr><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'> When ALL OFF (button B) is pressed the status LED is Lit.</td> <td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'>Button A LED is not Lit.</td></tr><br />
</table><br />
<br />
<br />
Refer to the KeypadLinc User’s Manual Grouping Button section for more information.<br />
The ISY creates groups by creating a scene. This is accomplished by selecting Mutually Exclusive Button on the GUI and dragging the device buttons into the Mutually Exclusive Button 1 or 2. Refer to Figure 35.<br />
<br />
<br />
[[image:Mutually Exclusive.PNG|frame|none|''Figure 35. Mutually Exclusive Buttons.'']]<br />
<br />
Button Toggle Mode sets the button state to toggle from ON to OFF and vice versa, or stay always ON, or always OFF. Assigning a button for toggle OFF sets it to either always ON or always OFF mode setting. The ISY will ask you to physically set the button to ON or OFF (key status LED ON or OFF) in the process. Refer to the KeypadLinc User’s Manual Toggle Mode section for more information.<br />
<br />
<br />
<br />
Select and hold the slider control, move it to the level or ramp rate your desire. As you change these settings the device will proportionately change the lamp brightness or ramp up/down time of the lamp.<br />
<br />
The tree at the right side of the view pane shows the scenes the device belongs to and as a controller switch showing which devices it controls.<br />
<br />
Right mouse clicking on an INSTEON device node, presents a menu as depicted in Figure 36.<br />
<br />
<br />
[[image:Device Menu.PNG|frame|none|''Figure 36 – Device Menu'']]<br />
<br />
<br />
==Query==<br />
<br />
Choosing this option causes ISY to query the selected device. The ISY will retrieve the status of the device and present the status on the view pane. This operation usually takes between 5 to 10 seconds depending on the device.<br />
<br />
==Rename==<br />
<br />
Choose this option to rename the selected device.<br />
<br />
==Remove==<br />
<br />
Choosing this menu option completely removes the highlighted device from ISY, deletes all the associated timer, triggers, and dissociates it from all the scenes it may have belong to. <br />
In case of “Remove from Scene”, choosing the menu option removes the selected device from the Scene within the context of which it was selected.<br />
<br />
==Replace...with==<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new device. The ISY takes care of removing the defective device address from the device name and adding the new device address into the existing device name. It will swap all the linking information from the defective device to the new device. <br />
<br />
<br />
[[image:Compatible Device List.PNG|frame|none|''Figure 37. Compatible device replacement list.'']]<br />
<br />
<br />
To replace a defective device, you must first add the replacement device<br />
Then right mouse click the device node/name with the defective device. Select Replace menu and choose the replacement device from the menus of compatible or available devices.<br />
<br />
<br />
'''Known issue 1:''' As of version 2.6 firmware, there is no requester message directing the user to put into "Programming Mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no requester message is presented.<br />
<br />
The RemoteLinc is placed into Programming mode by simultaneously holding down the "Bright" and "Dim" buttons for 10 seconds or until the status light begins flashing.<br />
<br />
<br />
'''Known Issue 2:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
==Add to Scene==<br />
<br />
When there are many devices, using the drag and drop method sometimes becomes challenging. Choose this menu option to drop a device into a scene manually.<br />
<br />
<br />
==Restore Device==<br />
<br />
There might be cases where, for a variety of reasons (such as manual linking), a device does not perform as represented in ISY. In these cases, choose this option to restore all the links and reprogram the device to what’s logically represented in ISY.<br />
<br />
<br />
==Copy Attributes==<br />
<br />
This menu option allows you to copy attributes from one device and paste them into another. Attributes are such things as On Level, Ramp Rate, Set Point, etc.<br />
<br />
<br />
==Paste Attributes==<br />
<br />
This menu option allows you to paste the attributes which were copied into the selected device.<br />
<br />
<br />
==Properties==<br />
<br />
The purpose of this dialog box is to add additional information for each node (device) such as the location and the description.<br />
<br />
The isLoad check box can be used to show whether or not this device is actually controlling or physically connected to a load.<br />
The information gathered here is included in the HTML file created in Generate Topology Menu<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:Main Tab Layout|Main Tab : ]][[ISY-26 Insteon:Node|ISY Node : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3533User talk:Marksanctuary2008-01-18T05:58:31Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
Greetings Mark. I have a couple of questions for you:<br />
<br />
- I have recently added content to the "Replace" command under How To. Why is this section not under the general User Guide?<br />
<br />
- I would like to see us start gathering together all known hidden shell commands, and put them on the Wiki. Also how to do things like using the Debug feature, etc. These are all things that I see from time to time in the forums, and say to myself "I should try this sometime", but then I forget what it was and where I read it! So do you already have a list of these commands that we could post and explain how to use? Or should I start a thread on the forum asking for user input?\<br />
<br />
Best wishes,<br />
Frank<br />
<br />
==Mark==<br />
<br />
Frank,<br />
<br />
Thanks for working on the wiki while I am busy at work. Things will slow down in another week so I should have a bit more time again. <br />
<br />
The "Replacing a Device" How-To is there for a walkthrough of the process of replacing the device. It's not there for the command description, all the How-Tos are there for walkthrough style of documentation.<br />
<br />
As for a list of hidden commands or telnet commands I don’t have them. Michel has them and may have not shared them yet because they are working on debugging features.<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
I saw what you wrote in the "How To" section, that you had removed the "Replace...with" notes that I had put there. What you wrote made perfectly good sense, except that you said that it had been removed, when it really hadn't...it was still on the article page! So I just removed everything from both the article and discussion pages.<br />
<br />
I instead added it to the "User Guide" for the time being. I did this because the process is confusing due to the two "issues" that I have pointed out to Chris & Michel. The first issue is scheduled to get fixed. The second will be more complex. And I had already told Michel & Chris that I had posted this to the Wiki. So they expect it to be there somewhere.<br />
<br />
Since we don't have a "Bugzilla" page right now, and since some new users are complaining about how "sparse" the User Guide is, I figured that this should go someplace that it could be easily found as it is important information. So if "How-To" is not appropriate, then the Wiki User Guide is where it should go I guess.<br />
<br />
As Michel and Chris impliment the fixes, then the Wiki can be easily updated.<br />
<br />
Thanks</div>Yardman 49https://wiki.universal-devices.com/index.php?title=Talk:ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3529Talk:ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-18T05:50:00Z<p>Yardman 49: Removing all content from page</p>
<hr />
<div></div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3528ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-18T05:49:27Z<p>Yardman 49: Replacing page with '_________________________________________'</p>
<hr />
<div>_________________________________________</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:INSTEON_Device&diff=3527ISY-99i/ISY-26 INSTEON:INSTEON Device2008-01-18T05:47:57Z<p>Yardman 49: </p>
<hr />
<div>This device node is located as a branch under the ISY node. Expanding the ISY node (My Lighting), will show the devices within the network.<br />
<br />
<br />
[[Image:ISY Node Expanded.PNG|frame|none|''Figure 33. ISY Node branch expanded showing devices.'']]<br />
<br />
<br />
Selecting a device in the INSTEON Device branch will show the device properties in the view pane. <br />
The pane will also have controls by means of a slider or buttons. These controls allow the user to directly control and setup the device via the computer. Currently the ISY supports all SmartHome lights, switches and dimmers. Depending on the device that is linked to the system, you will be presented with the permissible control action the system can help you perform and automate. For example in Figure 32 the “Entry-1 Overhead” light was selected and its properties are shown in the view pane.<br />
On level and ramp rate adjustment are controlled with a slider control. On level sets the amount of light within 0 and 100%, where 100% is full brightness or ON. Ramp rate sets the amount of time it takes to reach the set ON level from OFF to ON and from ON to OFF. <br />
<br />
Setting the device properties via the ISY does not require you to press the set button on the device. Unlike manually setting the ramp rates and ON levels, you need not press the Set Button to store the set values. All you need to do is set the sliders to the desired level or ramp rates.<br />
<br />
<br />
[[image:Device Properties.PNG|frame|none|''Figure 34 – Device Properties'']]<br />
<br />
<br />
Buttons available are ON, Fast ON, OFF, Fast OFF, Brighten and Dim. <br />
ON or OFF Buttons, turns on/off the lights using the preset ON/OFF levels and ramp rate. This action is similar to pressing the switch once.<br />
<br />
Fast ON/OFF Buttons, turns on/off the lights to full ON/OFF at the fastest ramp rate. This action is the similar to quickly tapping the switch twice.<br />
<br />
Brighten and Dim Buttons, adjusts the light level by 5% for every click of the button. If you press and hold the button the level will change at 5% step for every second it is held.<br />
<br />
Mutually Exclusive Button allows you to group the buttons in Exclusive OR state. This button select is only available with the KeypadLinc Devices. The idea is you group a set of buttons so that only one button will be in ON state at any time. For example, you group buttons A and B, where A is assigned as All ON and B as All OFF. The state of the status LED in each button will be as follows:<br />
<br />
<br />
<Table border=1 cellspacing=0 cellpadding=0 style='margin-left:.2in'><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'> '''ACTION''' </td><br />
<td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'> '''REACTION''' </td></tr><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'>When All ON (button A) is pressed the status LED is Lit.</td> <br />
<td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'>Button B LED is not Lit.</td></tr><br />
<tr style='height:22pt'><br />
<td width=360 style='width:3.75in;padding:0in 6pt 0in 6pt;height:22pt'> When ALL OFF (button B) is pressed the status LED is Lit.</td> <td width=360 style='width:1.5in;padding:0in 6pt 0in 6pt;height:22pt'>Button A LED is not Lit.</td></tr><br />
</table><br />
<br />
<br />
Refer to the KeypadLinc User’s Manual Grouping Button section for more information.<br />
The ISY creates groups by creating a scene. This is accomplished by selecting Mutually Exclusive Button on the GUI and dragging the device buttons into the Mutually Exclusive Button 1 or 2. Refer to Figure 35.<br />
<br />
<br />
[[image:Mutually Exclusive.PNG|frame|none|''Figure 35. Mutually Exclusive Buttons.'']]<br />
<br />
Button Toggle Mode sets the button state to toggle from ON to OFF and vice versa, or stay always ON, or always OFF. Assigning a button for toggle OFF sets it to either always ON or always OFF mode setting. The ISY will ask you to physically set the button to ON or OFF (key status LED ON or OFF) in the process. Refer to the KeypadLinc User’s Manual Toggle Mode section for more information.<br />
<br />
<br />
<br />
Select and hold the slider control, move it to the level or ramp rate your desire. As you change these settings the device will proportionately change the lamp brightness or ramp up/down time of the lamp.<br />
<br />
The tree at the right side of the view pane shows the scenes the device belongs to and as a controller switch showing which devices it controls.<br />
<br />
Right mouse clicking on an INSTEON device node, presents a menu as depicted in Figure 36.<br />
<br />
<br />
[[image:Device Menu.PNG|frame|none|''Figure 36 – Device Menu'']]<br />
<br />
<br />
==Query==<br />
<br />
Choosing this option causes ISY to query the selected device. The ISY will retrieve the status of the device and present the status on the view pane. This operation usually takes between 5 to 10 seconds depending on the device.<br />
<br />
==Rename==<br />
<br />
Choose this option to rename the selected device.<br />
<br />
==Remove==<br />
<br />
Choosing this menu option completely removes the highlighted device from ISY, deletes all the associated timer, triggers, and dissociates it from all the scenes it may have belong to. <br />
In case of “Remove from Scene”, choosing the menu option removes the selected device from the Scene within the context of which it was selected.<br />
<br />
==Replace...with==<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new device. The ISY takes care of removing the defective device address from the device name and adding the new device address into the existing device name. It will swap all the linking information from the defective device to the new device. <br />
<br />
<br />
[[image:Compatible Device List.PNG|frame|none|''Figure 37. Compatible device replacement list.'']]<br />
<br />
<br />
To replace a defective device, you must first add the replacement device<br />
Then right mouse click the device node/name with the defective device. Select Replace menu and choose the replacement device from the menus of compatible or available devices.<br />
<br />
<br />
'''Known issue 1:''' As of version 2.6 firmaware, there is no requester message directing the user to put into "Programming Mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no requester message is presented.<br />
<br />
The RemoteLinc is placed into Programming mode by simultaneously holding down the "Bright" and "Dim" buttons for 10 seconds or until the status light begins flashing.<br />
<br />
<br />
'''Known Issue 2:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
==Add to Scene==<br />
<br />
When there are many devices, using the drag and drop method sometimes becomes challenging. Choose this menu option to drop a device into a scene manually.<br />
<br />
<br />
==Restore Device==<br />
<br />
There might be cases where, for a variety of reasons (such as manual linking), a device does not perform as represented in ISY. In these cases, choose this option to restore all the links and reprogram the device to what’s logically represented in ISY.<br />
<br />
<br />
==Copy Attributes==<br />
<br />
This menu option allows you to copy attributes from one device and paste them into another. Attributes are such things as On Level, Ramp Rate, Set Point, etc.<br />
<br />
<br />
==Paste Attributes==<br />
<br />
This menu option allows you to paste the attributes which were copied into the selected device.<br />
<br />
<br />
==Properties==<br />
<br />
The purpose of this dialog box is to add additional information for each node (device) such as the location and the description.<br />
<br />
The isLoad check box can be used to show whether or not this device is actually controlling or physically connected to a load.<br />
The information gathered here is included in the HTML file created in Generate Topology Menu<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:Main Tab Layout|Main Tab : ]][[ISY-26 Insteon:Node|ISY Node : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Summary_Tab&diff=3523ISY-99i/ISY-26 INSTEON:Program Summary Tab2008-01-17T03:15:23Z<p>Yardman 49: </p>
<hr />
<div>==Program Table==<br />
<br />
[[image:Program Summary.PNG|frame|none|''Figure 44. Program Summary screen.'']]<br />
<br />
<br />
* The Name column contains the program names created in the Program Detail tab. <br />
* The Enable column defines whether the program is ON or OFF. When set to OFF, the program is stopped from acting on any stimulus that starts the program. When set to ON, it allows the program to act on the stimulus to start it. <br />
* The Activity column represents the program process. The program states are; Idle, Running ‘Then’ and Running ‘Else’. Idle state, is when the program is running and is waiting for the stimulus to occur. It will also show Running ‘Then’ and Running ‘Else’ messages. These messages are momentarily shown as the program enters and exits the Then or Else statements within the program.<br />
* The Status column presents you with the program state. You will only be presented a True or False state in the column.<br />
* The Path column shows the program location in the program detail tab. Refer to 8.<br />
* Last Run Time and Last Finish Time columns are a time log or time stamp of when the program started and ended. <br />
<br />
<br />
==Pull Down Menu and Apply Button==<br />
<br />
The pull down menu has a selection of Enable, Disable, Run, Run Else, Stop, Run at Boot and Not Run at Boot. These are actionable commands that are entered in the applicable Enable or Run at Boot column.<br />
<br />
* '''Enable''' – enables the program to run -- '''Note:''' after a power failure, the ISY will evaluate which events have been missed, and will attempt to "catch up" with timed events that were missed<br />
* '''Disable''' – disables the program so that it will not ever run unless enabled<br />
* '''Run''' – immediately runs the "Then" block of a program as if the "If" conditions had been met<br />
* '''Run Else''' – immediately runs the "Else" block of the program<br />
* '''Stop''' – Stops the program if currently running<br />
* '''Run at Boot''' – whenever the system is rebooted, this program runs regardless of the condition<br />
<br />
<br />
[[image:Program Summary Menu.PNG|frame|none|''Figure 45. Program Summary tab pull down menu.'']]<br />
<br />
<br />
To enter the command in the enabled column:<br />
# Select the command in the pull down menu.<br />
# Select a program row in the table. Move the mouse pointer to the row and press the left mouse button.<br />
# Select the Apply button.<br />
<br />
<br />
==Edit==<br />
<br />
When a program row is on the table is highlighted and the Edit button is selected, the system will immediately jump to program detail screen showing you the code of the program selected. <br />
Refer to Figure 43 for a sample of the program detail screen.<br />
<br />
<br />
==Refresh Button==<br />
<br />
The refresh button updates the summary table if you feel the table is not up to date.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide :]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Summary_Tab&diff=3522ISY-99i/ISY-26 INSTEON:Program Summary Tab2008-01-17T03:13:48Z<p>Yardman 49: </p>
<hr />
<div>==Program Table==<br />
<br />
[[image:Program Summary.PNG|frame|none|''Figure 44. Program Summary screen.'']]<br />
<br />
<br />
* The Name column contains the program names created in the Program Detail tab. <br />
* The Enable column defines whether the program is ON or OFF. When set to OFF, the program is stopped from acting on any stimulus that starts the program. When set to ON, it allows the program to act on the stimulus to start it. <br />
* The Activity column represents the program process. The program states are; Idle, Running ‘Then’ and Running ‘Else’. Idle state, is when the program is running and is waiting for the stimulus to occur. It will also show Running ‘Then’ and Running ‘Else’ messages. These messages are momentarily shown as the program enters and exits the Then or Else statements within the program.<br />
* The Status column presents you with the program state. You will only be presented a True or False state in the column.<br />
* The Path column shows the program location in the program detail tab. Refer to 8.<br />
* Last Run Time and Last Finish Time columns are a time log or time stamp of when the program started and ended. <br />
<br />
<br />
==Pull Down Menu and Apply Button==<br />
<br />
The pull down menu has a selection of Enable, Disable, Run, Run Else, Stop, Run at Boot and Not Run at Boot. These are actionable commands that are entered in the applicable Enable or Run at Boot column.<br />
<br />
* '''Enable''' – enables the program to run '''Note:''' after a power failure, the ISY will evaluate which events have been missed, and will attempt to "catch up" with timed events that were missed<br />
* '''Disable''' – disables the program so that it will not ever run unless enabled<br />
* '''Run''' – immediately runs the "Then" block of a program as if the "If" conditions had been met<br />
* '''Run Else''' – immediately runs the "Else" block of the program<br />
* '''Stop''' – Stops the program if currently running<br />
* '''Run at Boot''' – whenever the system is rebooted, this program runs regardless of the condition<br />
<br />
<br />
[[image:Program Summary Menu.PNG|frame|none|''Figure 45. Program Summary tab pull down menu.'']]<br />
<br />
<br />
To enter the command in the enabled column:<br />
# Select the command in the pull down menu.<br />
# Select a program row in the table. Move the mouse pointer to the row and press the left mouse button.<br />
# Select the Apply button.<br />
<br />
<br />
==Edit==<br />
<br />
When a program row is on the table is highlighted and the Edit button is selected, the system will immediately jump to program detail screen showing you the code of the program selected. <br />
Refer to Figure 43 for a sample of the program detail screen.<br />
<br />
<br />
==Refresh Button==<br />
<br />
The refresh button updates the summary table if you feel the table is not up to date.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide :]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Summary_Tab&diff=3521ISY-99i/ISY-26 INSTEON:Program Summary Tab2008-01-17T03:12:18Z<p>Yardman 49: </p>
<hr />
<div>==Program Table==<br />
<br />
[[image:Program Summary.PNG|frame|none|''Figure 44. Program Summary screen.'']]<br />
<br />
<br />
* The Name column contains the program names created in the Program Detail tab. <br />
* The Enable column defines whether the program is ON or OFF. When set to OFF, the program is stopped from acting on any stimulus that starts the program. When set to ON, it allows the program to act on the stimulus to start it. <br />
* The Activity column represents the program process. The program states are; Idle, Running ‘Then’ and Running ‘Else’. Idle state, is when the program is running and is waiting for the stimulus to occur. It will also show Running ‘Then’ and Running ‘Else’ messages. These messages are momentarily shown as the program enters and exits the Then or Else statements within the program.<br />
* The Status column presents you with the program state. You will only be presented a True or False state in the column.<br />
* The Path column shows the program location in the program detail tab. Refer to 8.<br />
* Last Run Time and Last Finish Time columns are a time log or time stamp of when the program started and ended. <br />
<br />
<br />
==Pull Down Menu and Apply Button==<br />
<br />
The pull down menu has a selection of Enable, Disable, Run, Run Else, Stop, Run at Boot and Not Run at Boot. These are actionable commands that are entered in the applicable Enable or Run at Boot column.<br />
<br />
* '''Enable''' – enables the program to run '''Note:''' after a power failure, the ISY will evaluate which events have been missed, and will attempt to "catch up" with timed events that were missed<br />
* '''Disable''' – disables the program so that it will not ever run unless enabled<br />
* '''Run''' – immediately runs the "Then" block of a program as if the "If" conditions had been met<br />
* '''Run Else''' – immediately runs the "Else" block of the program<br />
* '''Stop''' – Stops the program if currently running<br />
* '''Run at Boot''' – whenever the system is rebooted, this program runs regardless of the condition<br />
<br />
<br />
[[image:Program Summary Menu.PNG|frame|none|''Figure 45. Program Summary tab pull down menu.'']]<br />
<br />
<br />
To enter the command in the enabled column:<br />
# Select the command in the pull down menu.<br />
# Select a program row in the table. Move the mouse pointer to the row and press the left mouse button.<br />
# Select the Apply button.<br />
<br />
<br />
==Edit==<br />
<br />
When a program row is on the table is highlighted and the Edit button is selected, the system will immediately jump to program detail screen showing you the code of the program selected. <br />
Refer to Figure 43 for a sample of the program detail screen.<br />
<br />
<br />
==Refresh Button==<br />
<br />
The refresh button updates the summary table if you feel the table is not up to date.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide :]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Summary_Tab&diff=3520ISY-99i/ISY-26 INSTEON:Program Summary Tab2008-01-17T03:11:32Z<p>Yardman 49: </p>
<hr />
<div>==Program Table==<br />
<br />
[[image:Program Summary.PNG|frame|none|''Figure 44. Program Summary screen.'']]<br />
<br />
<br />
* The Name column contains the program names created in the Program Detail tab. <br />
* The Enable column defines whether the program is ON or OFF. When set to OFF, the program is stopped from acting on any stimulus that starts the program. When set to ON, it allows the program to act on the stimulus to start it. <br />
* The Activity column represents the program process. The program states are; Idle, Running ‘Then’ and Running ‘Else’. Idle state, is when the program is running and is waiting for the stimulus to occur. It will also show Running ‘Then’ and Running ‘Else’ messages. These messages are momentarily shown as the program enters and exits the Then or Else statements within the program.<br />
* The Status column presents you with the program state. You will only be presented a True or False state in the column.<br />
* The Path column shows the program location in the program detail tab. Refer to 8.<br />
* Last Run Time and Last Finish Time columns are a time log or time stamp of when the program started and ended. <br />
<br />
<br />
==Pull Down Menu and Apply Button==<br />
<br />
The pull down menu has a selection of Enable, Disable, Run, Run Else, Stop, Run at Boot and Not Run at Boot. These are actionable commands that are entered in the applicable Enable or Run at Boot column.<br />
<br />
* '''Enable''' – enables the program to run; '''Note:''' after a power failure, the ISY will evaluate which events have been missed, and will attempt to "catch up" with timed events that were missed<br />
* '''Disable''' – disables the program so that it will not ever run unless enabled<br />
* '''Run''' – immediately runs the "Then" block of a program as if the "If" conditions had been met<br />
* '''Run Else''' – immediately runs the "Else" block of the program<br />
* '''Stop''' – Stops the program if currently running<br />
* '''Run at Boot''' – whenever the system is rebooted, this program runs regardless of the condition<br />
<br />
<br />
[[image:Program Summary Menu.PNG|frame|none|''Figure 45. Program Summary tab pull down menu.'']]<br />
<br />
<br />
To enter the command in the enabled column:<br />
# Select the command in the pull down menu.<br />
# Select a program row in the table. Move the mouse pointer to the row and press the left mouse button.<br />
# Select the Apply button.<br />
<br />
<br />
==Edit==<br />
<br />
When a program row is on the table is highlighted and the Edit button is selected, the system will immediately jump to program detail screen showing you the code of the program selected. <br />
Refer to Figure 43 for a sample of the program detail screen.<br />
<br />
<br />
==Refresh Button==<br />
<br />
The refresh button updates the summary table if you feel the table is not up to date.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide :]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Advanced_Configuration_Guide&diff=3519ISY-99i/ISY-26 INSTEON:Advanced Configuration Guide2008-01-17T02:55:59Z<p>Yardman 49: </p>
<hr />
<div>==The following notes pertain to using the ISY Shell==<br />
<br />
<br />
'''"DBG 1"'''<br />
<br />
To log key presses/X10 messages received to the java console, do the folliowing: <br />
<br />
1. Telnet to the ISY and login <br />
2. Type 'DBG 1'; this tells the box to send key presses to the GUI <br />
3. Login into the ISY Admin Console, and click the 'Program Summary' Tab <br />
4. Open the Java console <br />
5. Close Telnet session (optional) <br />
<br />
A line surrounded by square brackets is written to the Java console whenever a button is pressed, an X10 message is received, or a status change occurs. This is useful for determining whether or not the PLM has sent a button press or X10 message to the ISY. <br />
<br />
To turn it off, <br />
<br />
1. Telnet to the box and login <br />
2. Type 'DBG 0', this tells the box to stop sending key presses to the GUI <br />
3. Close the Java console (optional) <br />
4. Close Telnet session (optional)</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Advanced_Configuration_Guide&diff=3518ISY-99i/ISY-26 INSTEON:Advanced Configuration Guide2008-01-17T02:36:19Z<p>Yardman 49: New page: ==The following notes pertain to using the Admin shell== '''"DBG 1"''' To log key presses/X10 messages received to the java console, do the folliowing: 1. Telnet to the ISY and login ...</p>
<hr />
<div>==The following notes pertain to using the Admin shell==<br />
<br />
<br />
'''"DBG 1"'''<br />
<br />
To log key presses/X10 messages received to the java console, do the folliowing: <br />
<br />
1. Telnet to the ISY and login <br />
2. Type 'DBG 1'; this tells the box to send key presses to the GUI <br />
3. Login into the ISY Admin Console, and click the 'Program Summary' Tab <br />
4. Open the Java console <br />
5. Close Telnet session (optional) <br />
<br />
A line surrounded by square brackets is written to the Java console whenever a button is pressed, an X10 message is received, or a status change occurs. This is useful for determining whether or not the PLM has sent a button press or X10 message to the ISY. <br />
<br />
To turn it off, <br />
<br />
1. Telnet to the box and login <br />
2. Type 'DBG 0', this tells the box to stop sending key presses to the GUI <br />
3. Close the Java console (optional) <br />
4. Close Telnet session (optional)</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Add_to_Program&diff=3517ISY-99i/ISY-26 INSTEON:Add to Program2008-01-16T21:43:54Z<p>Yardman 49: </p>
<hr />
<div>This area facilitates the user in building the program. It simplifies the program building process by providing the user a preformatted edit space filled in using Schedule, Condition and Action buttons. It even provides you with a button to add comments in the program.<br />
<br />
* IF – has the condition that must be met to for the program to run. This condition is the trigger for the program to take action. <br />
* THEN – is the primary action when the condition is met. The program here stays running as long as the condition is met or True.<br />
* ELSE – is the secondary action when the condition is no longer met or False and only after the primary action was taken. <br />
<br />
Your program is not limited to one condition and action. You can have multiple condition and actions defined in the program. Multiple conditions are created using the And/Or pull down menu field. Buttons labeled Add And (...) or Add Or (...) will be available only after a second condition is added. The use of this button allows adding a parenthesis to your program condition. An example of a program with multiple condition and action is shown below. <br />
<br />
<br />
<br />
[[image:New Program.PNG|frame|none|''Figure 49. New Program Screen.'']]<br />
<br />
<br />
<br />
The enabled check box allows the system to run the program. Unchecking this box disables the program.<br />
<br />
<br />
==Schedule==<br />
<br />
The schedule button is used to enter time events into the IF section as a condition. When selected the lower portion of the Add to Programs area changes its selection fields. <br />
<br />
A check box for each day of the week and All (for all days) is available. This set the days of the week the timer event will occur. <br />
<br />
There are six pull down menu fields beneath the weekday checkbox. The first 5 fields define the occurrence and the sixth field defines if the occurrence is based on Time, Sunrise, Sunset or Last Run. Depending on the selection on the sixth field, the time set field (fields 2 to 5) setting will change. Refer to Figure 53 and Figure 54.<br />
<br />
A schedule can be set to occur at a specific or between the specified times. Selecting Time Is (refer to Figure 51) is for setting a specific time and From/To (refer to Figure 52) is setting for between specified times. <br />
<br />
The To field can be changed to For, defining the duration of the event based on time the start time. If you assigned a timer event to start at a time in a specific day of the week, and the For duration puts the end time to the next day, the ISY will complete the event timer on the next day. The timer event will always start at the set time of the selected weekday. For example, the start time (From) was set at 1:00PM on Monday and would last For 23Hrs. In this example the event will end on Tuesday at 12:00 noon. It will always start on Monday and end on Tuesday. This is a valid setting.<br />
<br />
<br />
<br />
[[image:Schedule Time Is.PNG|frame|none|''Figure 51. Schedule Time Is condition fields.'']]<br />
<br />
<br />
[[image:Schedule Time From_To.PNG|frame|none|''Figure 52. Schedule From/To condition fields.'']]<br />
<br />
<br />
Longer daylight and shorter night time in summer. Shorter daylight and longer night time in winter. The change in sunrise and sunset time through out the year from winter to summer meant that a fixed predetermined turn on or off time of lights meant you may either be turning on or off the lights too early or too late. Timer event based on Sunrise or Sunset instead of a specific time should solve this. You have the option to advance or delay the event to occur by setting the time and before/after fields.<br />
<br />
[[Image:Sunrise Sunset Field.PNG|frame|none|''Figure 53. Sunrise/Sunset field set.]]<br />
<br />
The Last Run option is an event timer based on the last runtime of the selected program. Refer to Figure 54. <br />
<br />
[[image:Last Run.PNG|frame|none|''Figure 54. Last Run field set.'']]<br />
<br />
To add a timer event to a program, select or create a new program. Set the time conditions for the timer event. Click on ‘Add to IF’ button to place the timer condition in the program. <br />
<br />
<br />
==Condition==<br />
<br />
Unlike the Schedule button that that uses the time as a trigger, the condition button uses the devices or a program to trigger the action. Conditions that are defined is added to the IF section. <br />
<br />
The INSTEON device status and controls are conditions for the trigger. Select ‘Status’ or ‘Control’ for in the menu.<br />
Another device is X10 devices. Selecting ‘X10’ from the menu will set the ISY to look for X10 command.<br />
The ‘Program’ option uses the status of another program for a trigger.<br />
<br />
<br />
[[image:Device and Program.PNG|frame|none|''Figure 55. Device and Program condition select.'']]<br />
<br />
The program state is set to True when the program enters the Then path and False when it enters the Else path. Folder conditions can be set based on the program state. This state is also reported in the Status column in the program summary table.<br />
<br />
Select ‘Add to IF’ button to add the triggers to the condition section.<br />
<br />
<br />
==Action==<br />
<br />
The "Action" button adds the action information in the ‘Then’ and ‘Else’ section of the program. It is defines the action taken after the condition is met or the trigger occurs.<br />
<br />
An Action can be setting a device to a defined state that is ON/OFF or set level. The type of Action is dependent on the device type. The two types of device Actions that are supported are '''INSTEON''' or '''Send X10''' .<br />
<br />
Besides setting a device, an Action can also be used to:<br />
<br />
*'''Run''' or '''Stop''' a Program.<br />
*'''Notify''' the addresses in the Recipients List.<br />
*'''Wait''' for a specified period or randomly within the specified period.<br />
*'''Repeat''' for a specified period or for a set number of times. Action statements following the Repeat action are indented. They will be repeated per the specified period or the set number of times.<br />
<br />
'''Note:''' To break a Repeat sequence, add a "Repeat 1 times". Actions after this Repeat will only run once (that is to say, they won't repeat at all). This is useful when you want some Actions repeated, but then want to continue on with more Actions that should not be repeated.<br />
<br />
'''Note:''' The Repeat and Wait actions have a "Random" option. This is set by selecting the Random check box. A Random value from 1 to the entered value will be randomly chosen each time the action is run. <br />
<br />
<br />
<br />
[[image:Action Command Set.PNG|frame|none|''Figure 56. Action command set.'']]<br />
<br />
<br />
==Comment==<br />
<br />
Select the comment button to show the comment entry field. This field is a free form field without character count limit.<br />
Select ‘Update’ button to add the comment in the program.<br />
<br />
<br />
[[image:Comment Entry.PNG|frame|none|''Figure 57. Comment entry field.'']]<br />
<br />
<br />
<br />
<br />
<br />
<br />
----<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]][[ISY-26 Insteon:Program Detail|Program Details : ]]<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:How-To Guide|How To Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3516User talk:Marksanctuary2008-01-15T14:28:17Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
Greetings Mark. I have a couple of questions for you:<br />
<br />
- I have recently added content to the "Replace" command under How To. Why is this section not under the general User Guide?<br />
<br />
- I would like to see us start gathering together all known hidden shell commands, and put them on the Wiki. Also how to do things like using the Debug feature, etc. These are all things that I see from time to time in the forums, and say to myself "I should try this sometime", but then I forget what it was and where I read it! So do you already have a list of these commands that we could post and explain how to use? Or should I start a thread on the forum asking for user input?\<br />
<br />
Best wishes,<br />
Frank</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3515ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-15T14:20:42Z<p>Yardman 49: </p>
<hr />
<div>_________________________________________<br />
<br />
This is from the current ISY-26 manual:<br />
<br />
'''"Replace....with" command:'''<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new<br />
device. The ISY takes care of removing the defective device address from the device name and<br />
adding the new device address into the existing device name. It will swap all the linking<br />
information from the defective device to the new device.<br />
<br />
__________________________________________<br />
<br />
<br />
'''Known problem:''' As of version 2.6 firmaware, there is no requester message directing the user to put into "Programming Mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no requester message is presented.<br />
<br />
The RemoteLinc is placed into Programming mode by simultaneously holding down the "Bright" and "Dim" buttons for 10 seconds or until the status light begins flashing.<br />
<br />
<br />
'''Known Problem:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:How-To Guide|How To Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3512ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-13T22:16:23Z<p>Yardman 49: </p>
<hr />
<div>_________________________________________<br />
<br />
This is from the current ISY-26 manual:<br />
<br />
'''"Replace....with" command:'''<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new<br />
device. The ISY takes care of removing the defective device address from the device name and<br />
adding the new device address into the existing device name. It will swap all the linking<br />
information from the defective devices to the new device.<br />
<br />
__________________________________________<br />
<br />
<br />
'''Known problem:''' As of version 2.6 firmaware, there is no requestor message directing the user to put into "linking mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no reminder is presented.<br />
<br />
<br />
'''Known Problem:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:How-To Guide|How To Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3511ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-13T21:53:52Z<p>Yardman 49: </p>
<hr />
<div>This is from the current ISY-26 manual:<br />
<br />
<br />
_________________________________________<br />
<br />
'''"Replace....with" command:'''<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new<br />
device. The ISY takes care of removing the defective device address from the device name and<br />
adding the new device address into the existing device name. It will swap all the linking<br />
information from the defective devices to the new device.<br />
<br />
__________________________________________<br />
<br />
<br />
'''Known problem:''' As of version 2.6 firmaware, there is no requestor message directing the user to put into "linking mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no reminder is presented.<br />
<br />
<br />
'''Known Problem:''' As of version 2.6 firmware, this command will leave programs that have used the Replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:How-To Guide|How To Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device&diff=3510ISY-99i/ISY-26 INSTEON:Replacing a Device2008-01-13T21:51:24Z<p>Yardman 49: </p>
<hr />
<div>This is from the current ISY-26 manual:<br />
<br />
<br />
_________________________________________<br />
<br />
'''"Replace....with" command:'''<br />
<br />
This menu option allows you to replace a defective device assigned to a device name with a new<br />
device. The ISY takes care of removing the defective device address from the device name and<br />
adding the new device address into the existing device name. It will swap all the linking<br />
information from the defective devices to the new device.<br />
<br />
__________________________________________<br />
<br />
<br />
'''Known problem:''' As of version 2.6 firmaware, there is no requestor message directing the user to put into "linking mode" any RemoteLincs included in scenes of which the Replaced device is a controller. Therefore, it will be necessary to do this at the beginning of the "Replace....with" process, even though no reminder is presented.<br />
<br />
<br />
'''Known Problem:''' As of version 2.6 firmware, this command will leave programs that have used the replaced device's name in an unspecified state for that device. To fix this, after performing the "Replace....with" command, review all programs that have used the "Replaced" device's name, re-select the proper device, and re-save the program.<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:How-To Guide|How To Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=Talk:ISY-99i_Series_INSTEON&diff=3352Talk:ISY-99i Series INSTEON2008-01-03T02:16:23Z<p>Yardman 49: New page: ==Frank== I updated the Migration section to reflect Michel's answer to my backwards migration question: [http://forum.universal-devices.com/viewtopic.php?p=5098#5098]</p>
<hr />
<div>==Frank==<br />
<br />
I updated the Migration section to reflect Michel's answer to my backwards migration question:<br />
[http://forum.universal-devices.com/viewtopic.php?p=5098#5098]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON&diff=3351ISY-99i Series INSTEON2008-01-03T02:13:37Z<p>Yardman 49: </p>
<hr />
<div>The ISY-99i Series have the same capabilities as 26 series but with the following additions:<br />
<br />
* Optional IR (input only) support - Any RC5/Philips/Universal Remote<br />
* Optional Support for 1024 device/scene combinations (PRO package)<br />
* Optional Support for a lot more Programs<br />
* Does not require an external Power Supply - it's powered through the PLM<br />
<br />
<br />
[[{{ns:6}}:Isy99new.jpg|600px]]<br />
<br />
<br />
==Documentation==<br />
<br />
Unless listed in this section, the documentation for 99i is the same as [[ISY-26 Insteon]].<br />
<br />
'''Migration from ISY-26'''<br />
# Locate a working ISY-26 backup file<br />
# Login to the 99i Administrative Console and choose File->Restore ISY<br />
# Choose the backup file identified in the first step<br />
'''NOTE:''' the reverse function '''cannot''' cannot be performed, i.e., a backup file from a 99i '''cannot''' be restored onto an ISY-26.<br />
<br />
<br />
'''Reboot'''<br />
# Use a sharp object to push in the Reset Button (on the front panel)<br />
<br />
<br />
'''Reset Userid/Password to admin/admin'''<br />
# Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second)<br />
# Hold for '''5 seconds''' till the RX, TX, Mem, Error lights turn on/off consecutively (RX -> Tx -> Mem -> Error)<br />
# Release <br />
<br />
<br />
'''Factory Reset'''<br />
# Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second)<br />
# Hold for about '''10 seconds''' until all of the the RX, TX, Mem, Error lights turn off and Mem light starts flashing really quickly<br />
# Release and wait for system reboot (reboot is complete when Mem light stops flashing)<br />
<br />
==Tutorials==<br />
<br />
* [http://www.universal-devices.com/mwiki/index.php?title=Quick_IR_Tutorial Quick IR Tutorial]<br />
<br />
<br />
==References==<br />
<br />
* [http://www.techav.com/ehx/ehxfall2007.htm EHX Fall 2007 Show Report] - by MikeB<br />
* [http://www.techav.com/udi/isy99i.htm Review of ISY-99i/IR PRO] - by MikeB<br />
* [http://forum.universal-devices.com/viewtopic.php?t=375 Codename ISY 99.9 (Forum)] - Information</div>Yardman 49https://wiki.universal-devices.com/index.php?title=Talk:INSTEON:_Troubleshooting_Communications_Errors&diff=3135Talk:INSTEON: Troubleshooting Communications Errors2007-12-28T20:28:24Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
Hello Mark:<br />
<br />
Here is your section that I removed:<br />
<br />
____________________________________________________________________________<br />
<br />
There is a desire to compare performance the PLC with the PLM and say, "the PLC worked fine why does the PLM not perform the same". The PLC was designed more with the mentality and behaved like it was communicating between themselves. It would not provide feedback to the user that it struggled to communicate, effectively hiding issues that may now be seen with the PLM and ISY setup. Also the PLM is a different design and has a reduced signal strength, it has been discussed that it is somewhere in the near 50% less than the PLC. <br />
<br />
_____________________________________________________________________________<br />
<br />
<br />
Many users that buy the ISY may never have used the Houselinc/PLC. So maybe we can rewrite this to be less specific, but still understandable to those that may have indeed made the comparison.<br />
<br />
Best wishes,</div>Yardman 49https://wiki.universal-devices.com/index.php?title=Talk:INSTEON:_Troubleshooting_Communications_Errors&diff=3134Talk:INSTEON: Troubleshooting Communications Errors2007-12-28T20:27:45Z<p>Yardman 49: New page: ==Frank== Hello Mark: Here is the section that I removed: ____________________________________________________________________________ There is a desire to compare performance the PLC ...</p>
<hr />
<div>==Frank==<br />
<br />
Hello Mark:<br />
<br />
Here is the section that I removed:<br />
<br />
____________________________________________________________________________<br />
<br />
There is a desire to compare performance the PLC with the PLM and say, "the PLC worked fine why does the PLM not perform the same". The PLC was designed more with the mentality and behaved like it was communicating between themselves. It would not provide feedback to the user that it struggled to communicate, effectively hiding issues that may now be seen with the PLM and ISY setup. Also the PLM is a different design and has a reduced signal strength, it has been discussed that it is somewhere in the near 50% less than the PLC. <br />
<br />
_____________________________________________________________________________<br />
<br />
<br />
Many users that buy the ISY may never have used the Houselinc/PLC. So maybe we can rewrite this to be less specific, but still understandable to those that may have indeed made the comparison.<br />
<br />
Best wishes,</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3133INSTEON: Troubleshooting Communications Errors2007-12-28T20:22:47Z<p>Yardman 49: </p>
<hr />
<div>== Communication Problems with INSTEON Devices ==<br />
<br />
The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that while their INSTEON devices seem to communicate reliably between themselves, the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The ISY-26 communicates to the INSTEON devices on a power line network via the SmartHome PLM (PowerLinc Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves. <br />
* The PLM and ISY-26 require reliable "acknowledgements" of their "requests" to the INSTEON devices. When these are not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY-26 function. <br />
<br />
<br />
Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free INSTEON device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility (as described in their enclosed instructions) to determine if they are on opposite legs of the power line mains. (The older SignaLincs can also be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give most signals the best chance of being propagated back throughout the entire power line network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or fluorescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of power line noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
Please see "[http://forum.universal-devices.com/viewtopic.php?t=507 Resolution to my PLM/ISY communication errors (Forum)]" for further help and discussion on this topic.<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3132User talk:Marksanctuary2007-12-28T20:21:36Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! <br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!<br />
<br />
<br />
==Mark==<br />
<br />
Yeah I am a huge consistent formatting guy too, the whole caps topic was hard to decide. <br />
<br />
The main things are... The large bold font that is used for the heading was hard to read in caps. The wiki grammar and formatting documents recommend caps only on acronyms, initials, and avoid it in titles. And proper writing guides also suggest against it, so finally I decided to go title case only instead. <br />
<br />
And now it's over 70 [[Special:Allpages|pages]] that would need to be moved and most likely over 200 links to fix now, and all the old orphan pages would have to be cleaned up by Michel. Which took me three days to move/rename them to the proper "Subject:Topic" title format.<br />
<br />
For now we can start with making sure INSTEON is caps in the writings and maybe the links but I don't think the moving of the pages is such a good idea, unless Michel will clean up all the orphan pages after its done.<br />
<br />
<br />
==Mark==<br />
<br />
Frank, I am exicted that you are joining me in working on the Wiki. It is fun an rewarding to work on it for me and which I hope will be for you too. I was kind of a solo job for a while there and I was hoping to have some other active editors join me. I want you to know I respect everyones writings here and will only fix boo-boos unless otherwise I see ideas for major change suggestions then I will pop a note your way.<br />
<br />
==Frank==<br />
<br />
Thanks very much for the welcome, Mark! I do a lot of writing in my current position as a a nationwide technical specialist for a major scientific products company. I had told Michel in the past that I would be willing to review the User's Guide for him. However, it was hard to get started on it, because of my job responsibilities and the problem with finding personal time to do a complete review of the Guide.<br />
<br />
I then saw that you had been working on the Wiki, and it seemed that this was a far better way to contribute to improving the UDI documentation: as soon as someone makes an edit or addition, it can be instantly reviewed by everyone. This really does seem to be a much more efficient method of creating and editing documentation. Sort of like a Lotus Notes database, but without the "local" replicas; instead, everyone has access to the master document. Very nice.<br />
<br />
Best wishes<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You just added to following to "Communication Troubleshooting":<br />
<br />
''There is a desire to compare performance the PLC with the PLM and say, "the PLC worked fine why does the PLM not perform the same". The PLC was designed more with the mentality and behaved like it was communicating between themselves. It would not provide feedback to the user that it struggled to communicate, effectively hiding issues that may now be seen with the PLM and ISY setup. Also the PLM is a different design and has a reduced signal strength, it has been discussed that it is somewhere in the near 50% less than the PLC''<br />
<br />
You may want to consider not leaving this comment in place. I had thought about going this route, but then decided against it. My reasoning is that I was trying to remain as objective as possible about this issue (which really is quite an aggravating one for a new user), and I wanted to stay away from any "inflammatory" remarks. Especially as this may make its way into the "official" documentation, Michel would probably not want any direct references to limitations of the PLM, or benefits of the PLC. He is always very diplomatic.<br />
<br />
Hence, I only included the following line, figuring that it would "cover everything without saying too much":<br />
<br />
''The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.'' <br />
<br />
This reveals that the PLM has weaknesses without stating more than we actually know. I agree that the Houselinc/PLC combination seemed more "robust", but I don't know if that was the PLC, or Houselinc hiding the problems.<br />
<br />
<br />
At any rate, if I were a new user, and saw your comment in the User Guide, it would feel strange to me, regardless of how true it may be. Such a user could then try to complain to SmartHome, who would then ask Michel why that comment was included, and it could jeopardize their working relationship.<br />
<br />
Please let me know what you think!<br />
<br />
Best wishes,<br />
<br />
Frank<br />
<br />
==Frank==<br />
<br />
Greetings Mark:<br />
<br />
As you havent' responded yet, I'm assuming that you are taking some time off. I hope that your Holidays are peaceful and filled with joy!<br />
<br />
I'm going to temporarily remove your paragraph from the Communications wiki page. I'll put it on the "discussion" section for that page. Maybe we can find a way to make it less specific, so as not to offend SH or anyone, and then we can put it back in. Hopefully you won't find this action to be offensive. I'm just trying to be as diplomatic as possible about the PLM's shortcomings.<br />
<br />
Best wishes</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3131User talk:Marksanctuary2007-12-27T16:54:53Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! <br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!<br />
<br />
<br />
==Mark==<br />
<br />
Yeah I am a huge consistent formatting guy too, the whole caps topic was hard to decide. <br />
<br />
The main things are... The large bold font that is used for the heading was hard to read in caps. The wiki grammar and formatting documents recommend caps only on acronyms, initials, and avoid it in titles. And proper writing guides also suggest against it, so finally I decided to go title case only instead. <br />
<br />
And now it's over 70 [[Special:Allpages|pages]] that would need to be moved and most likely over 200 links to fix now, and all the old orphan pages would have to be cleaned up by Michel. Which took me three days to move/rename them to the proper "Subject:Topic" title format.<br />
<br />
For now we can start with making sure INSTEON is caps in the writings and maybe the links but I don't think the moving of the pages is such a good idea, unless Michel will clean up all the orphan pages after its done.<br />
<br />
<br />
==Mark==<br />
<br />
Frank, I am exicted that you are joining me in working on the Wiki. It is fun an rewarding to work on it for me and which I hope will be for you too. I was kind of a solo job for a while there and I was hoping to have some other active editors join me. I want you to know I respect everyones writings here and will only fix boo-boos unless otherwise I see ideas for major change suggestions then I will pop a note your way.<br />
<br />
==Frank==<br />
<br />
Thanks very much for the welcome, Mark! I do a lot of writing in my current position as a a nationwide technical specialist for a major scientific products company. I had told Michel in the past that I would be willing to review the User's Guide for him. However, it was hard to get started on it, because of my job responsibilities and the problem with finding personal time to do a complete review of the Guide.<br />
<br />
I then saw that you had been working on the Wiki, and it seemed that this was a far better way to contribute to improving the UDI documentation: as soon as someone makes an edit or addition, it can be instantly reviewed by everyone. This really does seem to be a much more efficient method of creating and editing documentation. Sort of like a Lotus Notes database, but without the "local" replicas; instead, everyone has access to the master document. Very nice.<br />
<br />
Best wishes<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You just added to following to "Communication Troubleshooting":<br />
<br />
''There is a desire to compare performance the PLC with the PLM and say, "the PLC worked fine why does the PLM not perform the same". The PLC was designed more with the mentality and behaved like it was communicating between themselves. It would not provide feedback to the user that it struggled to communicate, effectively hiding issues that may now be seen with the PLM and ISY setup. Also the PLM is a different design and has a reduced signal strength, it has been discussed that it is somewhere in the near 50% less than the PLC''<br />
<br />
You may want to consider not leaving this comment in place. I had thought about going this route, but then decided against it. My reasoning is that I was trying to remain as objective as possible about this issue (which really is quite an aggravating one for a new user), and I wanted to stay away from any "inflammatory" remarks. Especially as this may make its way into the "official" documentation, Michel would probably not want any direct references to limitations of the PLM, or benefits of the PLC. He is always very diplomatic.<br />
<br />
Hence, I only included the following line, figuring that it would "cover everything without saying too much":<br />
<br />
''The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.'' <br />
<br />
This reveals that the PLM has weaknesses without stating more than we actually know. I agree that the Houselinc/PLC combination seemed more "robust", but I don't know if that was the PLC, or Houselinc hiding the problems.<br />
<br />
<br />
At any rate, if I were a new user, and saw your comment in the User Guide, it would feel strange to me, regardless of how true it may be. Such a user could then try to complain to SmartHome, who would then ask Michel why that comment was included, and it could jeopardize their working relationship.<br />
<br />
Please let me know what you think!<br />
<br />
Best wishes,<br />
<br />
Frank</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3130User talk:Marksanctuary2007-12-27T16:46:06Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! <br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!<br />
<br />
<br />
==Mark==<br />
<br />
Yeah I am a huge consistent formatting guy too, the whole caps topic was hard to decide. <br />
<br />
The main things are... The large bold font that is used for the heading was hard to read in caps. The wiki grammar and formatting documents recommend caps only on acronyms, initials, and avoid it in titles. And proper writing guides also suggest against it, so finally I decided to go title case only instead. <br />
<br />
And now it's over 70 [[Special:Allpages|pages]] that would need to be moved and most likely over 200 links to fix now, and all the old orphan pages would have to be cleaned up by Michel. Which took me three days to move/rename them to the proper "Subject:Topic" title format.<br />
<br />
For now we can start with making sure INSTEON is caps in the writings and maybe the links but I don't think the moving of the pages is such a good idea, unless Michel will clean up all the orphan pages after its done.<br />
<br />
<br />
==Mark==<br />
<br />
Frank, I am exicted that you are joining me in working on the Wiki. It is fun an rewarding to work on it for me and which I hope will be for you too. I was kind of a solo job for a while there and I was hoping to have some other active editors join me. I want you to know I respect everyones writings here and will only fix boo-boos unless otherwise I see ideas for major change suggestions then I will pop a note your way.<br />
<br />
==Frank==<br />
<br />
Thanks very much for the welcome, Mark! I do a lot of writing in my current position as a a nationwide technical specialist for a major scientific products company. I had told Michel in the past that I would be willing to review the User's Guide for him. However, it was hard to get started on it, because of my job responsibilities and the problem with finding personal time to do a complete review of the Guide.<br />
<br />
I then saw that you had been working on the Wiki, and it seemed that this was a far better way to contribute to improving the UDI documentation: as soon as someone makes an edit or addition, it can be instantly reviewed by everyone. This really does seem to be a much more efficient method of creating and editing documentation. Sort of like a Lotus Notes database, but without the "local" replicas; instead, everyone has access to the master document. Very nice.<br />
<br />
Best wishes<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You just added to following to "Communication Troubleshooting":<br />
<br />
''There is a desire to compare performance the PLC with the PLM and say, "the PLC worked fine why does the PLM not perform the same". The PLC was designed more with the mentality and behaved like it was communicating between themselves. It would not provide feedback to the user that it struggled to communicate, effectively hiding issues that may now be seen with the PLM and ISY setup. Also the PLM is a different design and has a reduced signal strength, it has been discussed that it is somewhere in the near 50% less than the PLC''<br />
<br />
You may want to consider not leaving this comment in place. I had thought about going this route, but then decided against it. My reasoning is that I was trying to remain as objective as possible about this issue (which really is quite an aggravating one for a new user), and I wanted to stay away from any "inflammatory" remarks. Especially as this may make its way into the "official" documentation, Michel would probably not want any direct references to limitations of the PLM, or benefits of the PLC. He is always very diplomatic.</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3129User talk:Marksanctuary2007-12-27T16:22:03Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! <br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!<br />
<br />
<br />
==Mark==<br />
<br />
Yeah I am a huge consistent formatting guy too, the whole caps topic was hard to decide. <br />
<br />
The main things are... The large bold font that is used for the heading was hard to read in caps. The wiki grammar and formatting documents recommend caps only on acronyms, initials, and avoid it in titles. And proper writing guides also suggest against it, so finally I decided to go title case only instead. <br />
<br />
And now it's over 70 [[Special:Allpages|pages]] that would need to be moved and most likely over 200 links to fix now, and all the old orphan pages would have to be cleaned up by Michel. Which took me three days to move/rename them to the proper "Subject:Topic" title format.<br />
<br />
For now we can start with making sure INSTEON is caps in the writings and maybe the links but I don't think the moving of the pages is such a good idea, unless Michel will clean up all the orphan pages after its done.<br />
<br />
<br />
==Mark==<br />
<br />
Frank, I am exicted that you are joining me in working on the Wiki. It is fun an rewarding to work on it for me and which I hope will be for you too. I was kind of a solo job for a while there and I was hoping to have some other active editors join me. I want you to know I respect everyones writings here and will only fix boo-boos unless otherwise I see ideas for major change suggestions then I will pop a note your way.<br />
<br />
==Frank==<br />
<br />
Thanks very much for the welcome, Mark! I do a lot of writing in my current position as a a nationwide technical specialist for a major scientific products company. I had told Michel in the past that I would be willing to review the User's Guide for him. However, it was hard to get started on it, because of my job responsibilities and the problem with finding personal time to do a complete review of the Guide.<br />
<br />
I then saw that you had been working on the Wiki, and it seemed that this was a far better way to contribute to improving the UDI documentation: as soon as someone makes an edit or addition, it can be instantly reviewed by everyone. This really does seem to be a much more efficient method of creating and editing documentation. Sort of like a Lotus Notes database, but without the "local" replicas; instead, everyone has access to the master document. Very nice.<br />
<br />
Best wishes</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3116INSTEON: Troubleshooting Communications Errors2007-12-27T04:08:41Z<p>Yardman 49: </p>
<hr />
<div>== Communication Problems with INSTEON Devices ==<br />
<br />
The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that while their INSTEON devices seem to communicate reliably between themselves, the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The ISY-26 communicates to the INSTEON devices on a powerline network via the SmartHome PLM (PowerLinc Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.<br />
* The PLM and ISY-26 require reliable "acknowledgements" of their "requests" to the INSTEON devices. When these are not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY-26 function.<br />
<br />
<br />
Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free INSTEON device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility (as described in their enclosed instructions) to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can also be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give most signals the best chance of being propagated back throughout the entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or flourescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Yardman_49&diff=3115User talk:Yardman 492007-12-27T02:51:28Z<p>Yardman 49: </p>
<hr />
<div>==Mark==<br />
<br />
Frank,<br />
I hope I did not bother you with doing the edit to add the bullets. The best thing about Wiki's is the ability to help each other. Let me know if you have any other questions. Mark<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
No problem at all with you adding the bullet points! After all, continual improvement via editing is what I guess the whole point of the Wiki is supposed to be!<br />
<br />
I'm just wondering how we should best communicate between ourselves. I'm not even certain if I am using this "talk" feature correctly!<br />
<br />
Thanks.</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3114User talk:Marksanctuary2007-12-27T02:49:33Z<p>Yardman 49: </p>
<hr />
<div>==Frank==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! <br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
<br />
<br />
==Frank==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
<br />
<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3113User talk:Marksanctuary2007-12-27T02:46:15Z<p>Yardman 49: </p>
<hr />
<div><br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
==Mark==<br />
<br />
<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
==Mark==<br />
<br />
<br />
<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
==Frank==<br />
<br />
Hello Mark:<br />
<br />
You may want to discuss the following with Michel: I'm thinking that any references to INSTEON in the ISY-26 documentation should show the word in all "caps". That is how SmartHome formats it on their documentation, and for the sake of consistency (I love consistent formatting) we probably should do likewise.<br />
<br />
I've made the changes to my "Troubleshooting" post, but nothing else yet. Probably the main page titles will need to be updated.<br />
<br />
Thanks!<br />
<br />
==Frank==</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3112INSTEON: Troubleshooting Communications Errors2007-12-27T02:41:15Z<p>Yardman 49: </p>
<hr />
<div>== Communication Problems with INSTEON Devices ==<br />
<br />
The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that their INSTEON devices seem to communicate reliably between themselves, but that the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The ISY-26 communicates to the INSTEON devices on a powerline network through the SmartHome PLM (PowerLinc Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.<br />
* The PLM and ISY-26 require reliable "acknowledgements" of their "requests" to the INSTEON devices. When not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY-26 function.<br />
<br />
<br />
Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free INSTEON device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility (as described in their enclosed instructions) to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can also be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give most signals the best chance of being propagated back throughout the entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or flourescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3111INSTEON: Troubleshooting Communications Errors2007-12-27T02:38:41Z<p>Yardman 49: </p>
<hr />
<div>== Communication Problems with INSTEON Devices ==<br />
<br />
The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that their INSTEON devices seem to communicate reliably between themselves, but that the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The ISY-26 communicates to the INSTEON devices on a powerline network through the SmartHome PLM (Power Line Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.<br />
* The PLM and ISY-26 require reliable "acknowledgements" of their "requests" to the INSTEON devices. When not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY-26 function.<br />
<br />
<br />
Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free INSTEON device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility (as described in their enclosed instructions) to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can also be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give most signals the best chance of being propagated back throughout the entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or flourescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3110User talk:Marksanctuary2007-12-27T02:21:17Z<p>Yardman 49: </p>
<hr />
<div><br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
==Mark==<br />
<br />
<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
==Mark==<br />
<br />
<br />
<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
==Frank==</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3109User talk:Marksanctuary2007-12-27T02:19:56Z<p>Yardman 49: </p>
<hr />
<div>==Mark==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
==Frank==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
==Mark==<br />
<br />
<br />
<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
==Frank==</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3108User talk:Marksanctuary2007-12-27T02:19:23Z<p>Yardman 49: </p>
<hr />
<div>==Mark==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
==Frank==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank<br />
<br />
==Frank==<br />
<br />
<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
==Mark==<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our names to appear on your discussion page??? Never mind, I just figured it out. Show off! :-)<br />
==Frank==</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3107User talk:Marksanctuary2007-12-27T02:16:35Z<p>Yardman 49: </p>
<hr />
<div>==Mark==<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
==Frank==<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
==Mark==<br />
<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank<br />
<br />
<br />
==Frank==<br />
<br />
Thought you might like your name in the headlines. :-P<br />
<br />
To change the editing window click on [[Special:Preferences|my preferences]] up in the top area. Go to the Editing tab, and change the Rows to say 30 and you should be good.<br />
<br />
Also so you are not in pre-Windows days turn on the "Show edit toolbar" so you can be in windows 3.1 days.<br />
<br />
Of course, what was I thinking! Yes, I do have the tool bar enabled, so of course I'm in Windows 3.1 !<br />
<br />
Hey, this is not fair.....how did you get our nicknames to appear on your discussion page???</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3105INSTEON: Troubleshooting Communications Errors2007-12-26T23:33:55Z<p>Yardman 49: /* Communication Problems with Some Devices */</p>
<hr />
<div>== Communication Problems with Some Devices ==<br />
<br />
The Insteon protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, Insteon users will sometimes find that their Insteon devices seem to communicate reliably between themselves, but that the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The SmartHome PLM that is utilized by the ISY-26 can be less tolerant of weak Insteon signals and power line "noise" (interference) than the Insteon switches themselves.<br />
* The ISY-26 and PLM require reliable "acknowledgements" of their "requests" to the Insteon devices. When not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY function.<br />
<br />
<br />
Due to these two characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free Insteon device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility (as described in their enclosed instructions) to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can also be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give most signals the best chance of being propagated back throughout the entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the Insteon signals. Likewise, certain models of GFCI outlets have also been reported to degrade Insteon signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your Insteon devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the Insteon signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other Insteon devices to miss Insteon control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or flourescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3104User talk:Marksanctuary2007-12-26T21:09:24Z<p>Yardman 49: </p>
<hr />
<div>Hello Mark:<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
Frank,<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
<br />
<br />
Hello Mark:<br />
Thanks for the tip! After I posted the question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3103User talk:Marksanctuary2007-12-26T21:08:30Z<p>Yardman 49: </p>
<hr />
<div>Hello Mark:<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!<br />
<br />
<br />
Frank,<br />
<br />
Bullets points come from doing a '*' in the first char of a line. I had to put the * in front of the <nowiki>'''</nowiki> bold markup to get it to work. Also the key for the number lines is to add an '#' in the first char of the line.<br />
<br />
For more tips check out the cheatsheet in the [[Help:Contents|Help]] section.<br />
<br />
Hello Mark:<br />
Thanks for the tip! After I posted teh question to you, I went in and looked at the code that you had used, and it made sense.<br />
<br />
On a related topic: how do you make the "edit" field "taller" on your computer screen? I can only see about 4 lines at a time. This makes edits in a large page very difficult. It makes me feel that I'm back in "pre-Windows" days!! Why does this Wiki interface have to be so archaic?? It's even more cumbersome than forums!<br />
<br />
Thanks! Frank</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Yardman_49&diff=3102User talk:Yardman 492007-12-26T21:01:57Z<p>Yardman 49: </p>
<hr />
<div>Frank,<br />
I hope I did not bother you with doing the edit to add the bullets. The best thing about Wiki's is the ability to help each other. Let me know if you have any other questions. Mark<br />
<br />
Hello Mark:<br />
No problem at all with you adding the bullet points! After all, continual improvement via editing is what I guess the whole point of the Wiki is supposed to be!<br />
<br />
I'm just wondering how we should best communicate between ourselves. I'm not even certain if I am using this "talk" feature correctly!<br />
<br />
Thanks.</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3091INSTEON: Troubleshooting Communications Errors2007-12-26T20:14:09Z<p>Yardman 49: </p>
<hr />
<div>== Communication Problems with Some Devices ==<br />
<br />
The Insteon protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, Insteon users will sometimes find that their Insteon devices seem to communicate reliably between themselves, but that the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The SmartHome PLM that is utilized by the ISY-26 can be less tolerant of weak Insteon signals and power line "noise" (interference) than the Insteon switches themselves.<br />
* The ISY-26 and PLM require reliable "acknowledgements" of their "requests" to the Insteon devices. When not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY function.<br />
<br />
<br />
Due to these two characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free Insteon device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give any received signals the best chance of being propagated back throughout entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the Insteon signals. Likewise, certain models of GFCI outlets have also been reported to degrade Insteon signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your Insteon devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the Insteon signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other Insteon devices to miss Insteon control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen or flourescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&diff=3087INSTEON: Troubleshooting Communications Errors2007-12-26T19:59:46Z<p>Yardman 49: /* Communication Problems with Some Devices */</p>
<hr />
<div>== Communication Problems with Some Devices ==<br />
<br />
The Insteon protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, Insteon users will sometimes find that their Insteon devices seem to communicate reliably between themselves, but that the ISY-26 will report "Communication Errors" on their power line network. There are multiple reasons for this:<br />
<br />
<br />
* The SmartHome PLM that is utilized by the ISY-26 can be less tolerant of weak Insteon signals and power line "noise" (interference) than the Insteon switches themselves.<br />
* The ISY-26 and PLM require reliable "acknowledgements" of their "requests" to the Insteon devices. When not properly received for any reason, the ISY-26 will display an error. Sometimes this will prevent the completion of an ISY function.<br />
<br />
<br />
Due to these two characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY-26 to provide error-free Insteon device monitoring and control.<br />
<br />
<br />
''The following tips may be helpful if communication problems are encountered:''<br />
<br />
<br />
* '''Use two SmartHome AccessPoints to improve network communications. Place these on opposite legs (sometimes called “phases”) of the power line mains.''' The AccessPoints provide their own internal utility to determine if they are on opposite legs of the powerline mains. (The older SignaLincs can be used for the same purpose.)<br />
* '''Place the two AccessPoints as close to the power line mains breaker or fuse box as possible.''' This will give any received signals the best chance of being propagated back throughout entire powerline network. This can provide a dramatic improvement in some cases. Again, be certain that the AccessPoints are placed on opposite legs of the power line mains.<br />
* '''Stack or “piggy-back” an additional AccessPoint on top of the PLM to improve network communications.''' The use of a stacked AccessPoint can improve Insteon signal strength to enable the PLM to better receive and send signals. Many users have reported that this is an effective solution. It may help to add this as an additional (third) AccessPoint in addition to the previously mentioned two AccessPoints.<br />
* '''Do not plug a PLM into a power strip that has any type of surge-suppression incorporated''', as this can weaken the Insteon signals. Likewise, certain models of GFCI outlets have also been reported to degrade Insteon signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your Insteon devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.<br />
<br />
<br />
''The next points are probably some of the most important:''<br />
<br />
* '''Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home.''' Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the Insteon signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other Insteon devices to miss Insteon control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.<br />
* '''For hard-wired halogen lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).''' <br />
* '''Some CFLs are prone to producing much higher levels of powerline noise than others.''' CFLs that are producing excessive line noise can be replaced with those that produce less interference.<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]][[ISY-26 Insteon:User Guide|User Guide : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=User_talk:Marksanctuary&diff=3086User talk:Marksanctuary2007-12-26T19:46:46Z<p>Yardman 49: New page: Hello Mark: How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how. Thanks!</p>
<hr />
<div>Hello Mark:<br />
<br />
How do you incorporate the bullet points into a Wiki post? I see that you've just done that on my post. I would have done that if I had known how.<br />
<br />
Thanks!</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-994i_INSTEON:User_Guide&diff=3080ISY-994i INSTEON:User Guide2007-12-26T19:00:52Z<p>Yardman 49: Undo revision 3079 by Yardman 49 (Talk)</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
The purpose of this document is to guide the system’s installer with the steps necessary to install and configure the Universal Devices’ ISY system and operate the GUI (Graphical User Interface) ISY comes configured for communications with the device(s) of your choice.<br />
<br />
<br />
==Installation==<br />
<br />
This section will cover the [[ISY-26 Insteon:Package Contents|Package Contents]], the basic [[ISY-26 Insteon:Installation|ISY Hardware Installation]], and enumerating the [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]] of the host computer and the network requirements. <br />
<br />
<br />
[[{{ns:6}}:Media Panel.jpg|right|Media Panel]]<br />
* [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]]<br />
* [[ISY-26 Insteon:Package Contents|Package Contents]]<br />
* [[ISY-26 Insteon:Installation|Hardware Installation]]<br />
<br />
<br />
==Inital Configuration==<br />
<br />
This section will cover the host computer [[ISY-26 Insteon:Configuration|Host Computer Configuration]], provide you some instructions on the host computer [[ISY-26 Insteon:Start up|Starting the ISY Window]] and an example of the [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]].<br />
<br />
<br />
* [[ISY-26 Insteon:Configuration|Host Computer Configuration]]<br />
* [[ISY-26 Insteon:Start up|Starting the ISY Window]]<br />
* [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]]<br />
<br />
<br />
==Main Window Interface==<br />
<br />
The graphical user interface (GUI) [[ISY-26 Insteon:Components and Navigation|Components and Navigation]] lend to the ease of using the ISY module. This section also details the functionalities and the operations of each [[ISY-26 Insteon:Tool bar|Tool Bar]] icon available in the Top Pane. Plus this section details the functionalities and the operations of each menu option listed in the Top Pane. The top menu options are [[ISY-26 Insteon:File Menu|File Menu]], [[ISY-26 Insteon:Link Management Menu|Link Management Menu]], [[ISY-26 Insteon:Tools Menu|Tools Menu]] and [[ISY-26 Insteon:Help Menu|Help Menu]]. <br />
<br />
<br />
* Root Window<br />
** [[ISY-26 Insteon:Components and Navigation|Components and Navigation]]<br />
** [[ISY-26 Insteon:Tool bar|Tool Bar]]<br />
* Pulldown Menus<br />
** [[ISY-26 Insteon:File Menu|File Menu]]<br />
** [[ISY-26 Insteon:Link Management Menu|Link Management Menu]]<br />
** [[ISY-26 Insteon:Tools Menu|Tools Menu]]<br />
** [[ISY-26 Insteon:Help Menu|Help Menu]]<br />
<br />
<br />
==Window Section Tabs==<br />
<br />
The [[ISY-26 Insteon:Main Tab Layout|Main Tab]] provides the user the ability to view the top level status of the network or the device details by selecting a tree node (tree branch). The nodes available in the tree are [[ISY-26 Insteon:Node|ISY Node]] and [[ISY-26 Insteon:Scene|Scene]]. The [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]] shows the program names in a table form showing if it is enabled, the status, the type of program, the last run time and the last finish time. The [[ISY-26 Insteon:Program Detail|Program Details Tab]] gives the user the ability to create timer or trigger programs. The [[ISY-26 Insteon:Configuration Tab|Configuration Tab]] allows the users to manage global settings such as [[ISY-26 Insteon:Configuring Physical Location|Location]]/[[ISY-26 Insteon:Date and Time Configuration|Date/Time]] and [[ISY-26 Insteon:Messaging Configuration|Messaging]] settings. <br />
<br />
<br />
* [[ISY-26 Insteon:Main Tab Layout|Main Tab]]<br />
** [[ISY-26 Insteon:Node|ISY Node]]<br />
***[[ISY-26 Insteon:Insteon Device|Insteon device]]<br />
** [[ISY-26 Insteon:Scene|Scene]]<br />
* [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]]<br />
* [[ISY-26 Insteon:Program Detail|Program Details Tab]]<br />
** [[ISY-26 Insteon:Tree View|Tree View]]<br />
** [[ISY-26 Insteon:Add to Program|Add to Program]]<br />
** [[ISY-26 Insteon:Manage Program|Manage Program]]<br />
** [[ISY-26 Insteon:Manage Program|Program Content]]<br />
** [[ISY-26 Insteon:Triggers and Schedules|Triggers/Schedules]] - this is info from the 2.4.x Beta which may need revising or removal<br />
* [[ISY-26 Insteon:Configuration Tab|Configuration Tab]]<br />
** [[ISY-26 Insteon:Configuring Physical Location|Location]]<br />
** [[ISY-26 Insteon:Date and Time Configuration|Date/Time]]<br />
** [[ISY-26 Insteon:Messaging Configuration|Messaging]]<br />
<br />
<br />
==Most Frequent How Tos==<br />
<br />
These How Tos are the low complexity frequent ones, for more challenging situations please see the [http://forum.universal-devices.com/viewforum.php?f=9 How Tos (Forum)] for help.<br />
<br />
<br />
* General Operation<br />
** [[ISY-26 Insteon:Your ISY IP Address|Get Your ISY IP Address]]<br />
** [[ISY-26 Insteon:Telnet To Your ISY|Telnet To Your ISY]] <br />
** [[ISY-26 Insteon:Spidering My Network|Spidering My Network]] <br />
** [[ISY-26 Insteon:Generate Typology|Getting a Network Typology Table]]<br />
** [[ISY-26 Insteon:Mutually Exclusive Buttons|Using Mutually Exclusive Buttons]]<br />
** [[ISY-26 Insteon:Adding Controlinc or Remotelincs|Adding Controlinc or Remotelincs]]<br />
** [[ISY-26 Insteon:Working With Keypadlincs|Working With Keypadlincs]]<br />
* ISY Scenes<br />
** [[ISY-26 Insteon:Create a Scene|Create a Scene]]<br />
** [[ISY-26 Insteon:Multi Way Circuit|Multi Way Circuit]]<br />
** [[ISY-26 Insteon:Controlling Keypadlinc LEDs|Controlling Keypadlinc LEDs]]<br />
<br />
<br />
==Troubleshooting==<br />
<br />
To report an error, please post the error/description to [http://forum.universal-devices.com/viewforum.php?f=6 our Forum]. Please provide the error and the situation in which the error presents itself. If possible please include a screen shot(s).<br />
<br />
<br />
* [[ISY-26 Insteon:Errors And Error Messages|Errors And Error Messages]]<br />
* [[ISY-26 Insteon:Red Exclamation Mark|Red Exclamation Mark]]<br />
* [[ISY-26 Insteon:X10 Troubleshooting|X10 Troubleshooting]]<br />
* [[ISY-26 Insteon:Troubleshooting|Communication Troubleshooting]]<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-994i_INSTEON:User_Guide&diff=3079ISY-994i INSTEON:User Guide2007-12-26T18:59:58Z<p>Yardman 49: /* Troubleshooting */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
The purpose of this document is to guide the system’s installer with the steps necessary to install and configure the Universal Devices’ ISY system and operate the GUI (Graphical User Interface) ISY comes configured for communications with the device(s) of your choice.<br />
<br />
<br />
==Installation==<br />
<br />
This section will cover the [[ISY-26 Insteon:Package Contents|Package Contents]], the basic [[ISY-26 Insteon:Installation|ISY Hardware Installation]], and enumerating the [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]] of the host computer and the network requirements. <br />
<br />
<br />
[[{{ns:6}}:Media Panel.jpg|right|Media Panel]]<br />
* [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]]<br />
* [[ISY-26 Insteon:Package Contents|Package Contents]]<br />
* [[ISY-26 Insteon:Installation|Hardware Installation]]<br />
<br />
<br />
==Inital Configuration==<br />
<br />
This section will cover the host computer [[ISY-26 Insteon:Configuration|Host Computer Configuration]], provide you some instructions on the host computer [[ISY-26 Insteon:Start up|Starting the ISY Window]] and an example of the [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]].<br />
<br />
<br />
* [[ISY-26 Insteon:Configuration|Host Computer Configuration]]<br />
* [[ISY-26 Insteon:Start up|Starting the ISY Window]]<br />
* [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]]<br />
<br />
<br />
==Main Window Interface==<br />
<br />
The graphical user interface (GUI) [[ISY-26 Insteon:Components and Navigation|Components and Navigation]] lend to the ease of using the ISY module. This section also details the functionalities and the operations of each [[ISY-26 Insteon:Tool bar|Tool Bar]] icon available in the Top Pane. Plus this section details the functionalities and the operations of each menu option listed in the Top Pane. The top menu options are [[ISY-26 Insteon:File Menu|File Menu]], [[ISY-26 Insteon:Link Management Menu|Link Management Menu]], [[ISY-26 Insteon:Tools Menu|Tools Menu]] and [[ISY-26 Insteon:Help Menu|Help Menu]]. <br />
<br />
<br />
* Root Window<br />
** [[ISY-26 Insteon:Components and Navigation|Components and Navigation]]<br />
** [[ISY-26 Insteon:Tool bar|Tool Bar]]<br />
* Pulldown Menus<br />
** [[ISY-26 Insteon:File Menu|File Menu]]<br />
** [[ISY-26 Insteon:Link Management Menu|Link Management Menu]]<br />
** [[ISY-26 Insteon:Tools Menu|Tools Menu]]<br />
** [[ISY-26 Insteon:Help Menu|Help Menu]]<br />
<br />
<br />
==Window Section Tabs==<br />
<br />
The [[ISY-26 Insteon:Main Tab Layout|Main Tab]] provides the user the ability to view the top level status of the network or the device details by selecting a tree node (tree branch). The nodes available in the tree are [[ISY-26 Insteon:Node|ISY Node]] and [[ISY-26 Insteon:Scene|Scene]]. The [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]] shows the program names in a table form showing if it is enabled, the status, the type of program, the last run time and the last finish time. The [[ISY-26 Insteon:Program Detail|Program Details Tab]] gives the user the ability to create timer or trigger programs. The [[ISY-26 Insteon:Configuration Tab|Configuration Tab]] allows the users to manage global settings such as [[ISY-26 Insteon:Configuring Physical Location|Location]]/[[ISY-26 Insteon:Date and Time Configuration|Date/Time]] and [[ISY-26 Insteon:Messaging Configuration|Messaging]] settings. <br />
<br />
<br />
* [[ISY-26 Insteon:Main Tab Layout|Main Tab]]<br />
** [[ISY-26 Insteon:Node|ISY Node]]<br />
***[[ISY-26 Insteon:Insteon Device|Insteon device]]<br />
** [[ISY-26 Insteon:Scene|Scene]]<br />
* [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]]<br />
* [[ISY-26 Insteon:Program Detail|Program Details Tab]]<br />
** [[ISY-26 Insteon:Tree View|Tree View]]<br />
** [[ISY-26 Insteon:Add to Program|Add to Program]]<br />
** [[ISY-26 Insteon:Manage Program|Manage Program]]<br />
** [[ISY-26 Insteon:Manage Program|Program Content]]<br />
** [[ISY-26 Insteon:Triggers and Schedules|Triggers/Schedules]] - this is info from the 2.4.x Beta which may need revising or removal<br />
* [[ISY-26 Insteon:Configuration Tab|Configuration Tab]]<br />
** [[ISY-26 Insteon:Configuring Physical Location|Location]]<br />
** [[ISY-26 Insteon:Date and Time Configuration|Date/Time]]<br />
** [[ISY-26 Insteon:Messaging Configuration|Messaging]]<br />
<br />
<br />
==Most Frequent How Tos==<br />
<br />
These How Tos are the low complexity frequent ones, for more challenging situations please see the [http://forum.universal-devices.com/viewforum.php?f=9 How Tos (Forum)] for help.<br />
<br />
<br />
* General Operation<br />
** [[ISY-26 Insteon:Your ISY IP Address|Get Your ISY IP Address]]<br />
** [[ISY-26 Insteon:Telnet To Your ISY|Telnet To Your ISY]] <br />
** [[ISY-26 Insteon:Spidering My Network|Spidering My Network]] <br />
** [[ISY-26 Insteon:Generate Typology|Getting a Network Typology Table]]<br />
** [[ISY-26 Insteon:Mutually Exclusive Buttons|Using Mutually Exclusive Buttons]]<br />
** [[ISY-26 Insteon:Adding Controlinc or Remotelincs|Adding Controlinc or Remotelincs]]<br />
** [[ISY-26 Insteon:Working With Keypadlincs|Working With Keypadlincs]]<br />
* ISY Scenes<br />
** [[ISY-26 Insteon:Create a Scene|Create a Scene]]<br />
** [[ISY-26 Insteon:Multi Way Circuit|Multi Way Circuit]]<br />
** [[ISY-26 Insteon:Controlling Keypadlinc LEDs|Controlling Keypadlinc LEDs]]<br />
<br />
<br />
==Troubleshooting==<br />
<br />
To report an error, please post the error/description to [http://forum.universal-devices.com/viewforum.php?f=6 our Forum]. Please provide the error and the situation in which the error presents itself. If possible please include a screen shot(s).<br />
<br />
<br />
* [[ISY-26 Insteon:Errors And Error Messages|Errors And Error Messages]]<br />
* [[ISY-26 Insteon:Red Exclamation Mark|Red Exclamation Mark]]<br />
* [[ISY-26 Insteon:X10 Troubleshooting|X10 Troubleshooting]]<br />
* [[ISY-26 Insteon:Communication Troubleshooting|Communication Troubleshooting]]<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-994i_INSTEON:User_Guide&diff=3078ISY-994i INSTEON:User Guide2007-12-26T18:55:00Z<p>Yardman 49: </p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
The purpose of this document is to guide the system’s installer with the steps necessary to install and configure the Universal Devices’ ISY system and operate the GUI (Graphical User Interface) ISY comes configured for communications with the device(s) of your choice.<br />
<br />
<br />
==Installation==<br />
<br />
This section will cover the [[ISY-26 Insteon:Package Contents|Package Contents]], the basic [[ISY-26 Insteon:Installation|ISY Hardware Installation]], and enumerating the [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]] of the host computer and the network requirements. <br />
<br />
<br />
[[{{ns:6}}:Media Panel.jpg|right|Media Panel]]<br />
* [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]]<br />
* [[ISY-26 Insteon:Package Contents|Package Contents]]<br />
* [[ISY-26 Insteon:Installation|Hardware Installation]]<br />
<br />
<br />
==Inital Configuration==<br />
<br />
This section will cover the host computer [[ISY-26 Insteon:Configuration|Host Computer Configuration]], provide you some instructions on the host computer [[ISY-26 Insteon:Start up|Starting the ISY Window]] and an example of the [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]].<br />
<br />
<br />
* [[ISY-26 Insteon:Configuration|Host Computer Configuration]]<br />
* [[ISY-26 Insteon:Start up|Starting the ISY Window]]<br />
* [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]]<br />
<br />
<br />
==Main Window Interface==<br />
<br />
The graphical user interface (GUI) [[ISY-26 Insteon:Components and Navigation|Components and Navigation]] lend to the ease of using the ISY module. This section also details the functionalities and the operations of each [[ISY-26 Insteon:Tool bar|Tool Bar]] icon available in the Top Pane. Plus this section details the functionalities and the operations of each menu option listed in the Top Pane. The top menu options are [[ISY-26 Insteon:File Menu|File Menu]], [[ISY-26 Insteon:Link Management Menu|Link Management Menu]], [[ISY-26 Insteon:Tools Menu|Tools Menu]] and [[ISY-26 Insteon:Help Menu|Help Menu]]. <br />
<br />
<br />
* Root Window<br />
** [[ISY-26 Insteon:Components and Navigation|Components and Navigation]]<br />
** [[ISY-26 Insteon:Tool bar|Tool Bar]]<br />
* Pulldown Menus<br />
** [[ISY-26 Insteon:File Menu|File Menu]]<br />
** [[ISY-26 Insteon:Link Management Menu|Link Management Menu]]<br />
** [[ISY-26 Insteon:Tools Menu|Tools Menu]]<br />
** [[ISY-26 Insteon:Help Menu|Help Menu]]<br />
<br />
<br />
==Window Section Tabs==<br />
<br />
The [[ISY-26 Insteon:Main Tab Layout|Main Tab]] provides the user the ability to view the top level status of the network or the device details by selecting a tree node (tree branch). The nodes available in the tree are [[ISY-26 Insteon:Node|ISY Node]] and [[ISY-26 Insteon:Scene|Scene]]. The [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]] shows the program names in a table form showing if it is enabled, the status, the type of program, the last run time and the last finish time. The [[ISY-26 Insteon:Program Detail|Program Details Tab]] gives the user the ability to create timer or trigger programs. The [[ISY-26 Insteon:Configuration Tab|Configuration Tab]] allows the users to manage global settings such as [[ISY-26 Insteon:Configuring Physical Location|Location]]/[[ISY-26 Insteon:Date and Time Configuration|Date/Time]] and [[ISY-26 Insteon:Messaging Configuration|Messaging]] settings. <br />
<br />
<br />
* [[ISY-26 Insteon:Main Tab Layout|Main Tab]]<br />
** [[ISY-26 Insteon:Node|ISY Node]]<br />
***[[ISY-26 Insteon:Insteon Device|Insteon device]]<br />
** [[ISY-26 Insteon:Scene|Scene]]<br />
* [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]]<br />
* [[ISY-26 Insteon:Program Detail|Program Details Tab]]<br />
** [[ISY-26 Insteon:Tree View|Tree View]]<br />
** [[ISY-26 Insteon:Add to Program|Add to Program]]<br />
** [[ISY-26 Insteon:Manage Program|Manage Program]]<br />
** [[ISY-26 Insteon:Manage Program|Program Content]]<br />
** [[ISY-26 Insteon:Triggers and Schedules|Triggers/Schedules]] - this is info from the 2.4.x Beta which may need revising or removal<br />
* [[ISY-26 Insteon:Configuration Tab|Configuration Tab]]<br />
** [[ISY-26 Insteon:Configuring Physical Location|Location]]<br />
** [[ISY-26 Insteon:Date and Time Configuration|Date/Time]]<br />
** [[ISY-26 Insteon:Messaging Configuration|Messaging]]<br />
<br />
<br />
==Most Frequent How Tos==<br />
<br />
These How Tos are the low complexity frequent ones, for more challenging situations please see the [http://forum.universal-devices.com/viewforum.php?f=9 How Tos (Forum)] for help.<br />
<br />
<br />
* General Operation<br />
** [[ISY-26 Insteon:Your ISY IP Address|Get Your ISY IP Address]]<br />
** [[ISY-26 Insteon:Telnet To Your ISY|Telnet To Your ISY]] <br />
** [[ISY-26 Insteon:Spidering My Network|Spidering My Network]] <br />
** [[ISY-26 Insteon:Generate Typology|Getting a Network Typology Table]]<br />
** [[ISY-26 Insteon:Mutually Exclusive Buttons|Using Mutually Exclusive Buttons]]<br />
** [[ISY-26 Insteon:Adding Controlinc or Remotelincs|Adding Controlinc or Remotelincs]]<br />
** [[ISY-26 Insteon:Working With Keypadlincs|Working With Keypadlincs]]<br />
* ISY Scenes<br />
** [[ISY-26 Insteon:Create a Scene|Create a Scene]]<br />
** [[ISY-26 Insteon:Multi Way Circuit|Multi Way Circuit]]<br />
** [[ISY-26 Insteon:Controlling Keypadlinc LEDs|Controlling Keypadlinc LEDs]]<br />
<br />
<br />
==Troubleshooting==<br />
<br />
To report an error, please post the error/description to [http://forum.universal-devices.com/viewforum.php?f=6 our Forum]. Please provide the error and the situation in which the error presents itself. If possible please include a screen shot(s).<br />
<br />
<br />
* [[ISY-26 Insteon:Errors And Error Messages|Errors And Error Messages]]<br />
* [[ISY-26 Insteon:Red Exclamation Mark|Red Exclamation Mark]]<br />
* [[ISY-26 Insteon:X10 Troubleshooting|X10 Troubleshooting]]<br />
* [[ISY-26 Insteon:Troubleshooting|Communication Troubleshooting]]<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-994i_INSTEON:User_Guide&diff=3077ISY-994i INSTEON:User Guide2007-12-26T18:53:12Z<p>Yardman 49: Undo revision 3076 by Yardman 49 (Talk)</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
The purpose of this document is to guide the system’s installer with the steps necessary to install and configure the Universal Devices’ ISY system and operate the GUI (Graphical User Interface) ISY comes configured for communications with the device(s) of your choice.<br />
<br />
<br />
==Installation==<br />
<br />
This section will cover the [[ISY-26 Insteon:Package Contents|Package Contents]], the basic [[ISY-26 Insteon:Installation|ISY Hardware Installation]], and enumerating the [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]] of the host computer and the network requirements. <br />
<br />
<br />
[[{{ns:6}}:Media Panel.jpg|right|Media Panel]]<br />
* [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]]<br />
* [[ISY-26 Insteon:Package Contents|Package Contents]]<br />
* [[ISY-26 Insteon:Installation|Hardware Installation]]<br />
<br />
<br />
==Inital Configuration==<br />
<br />
This section will cover the host computer [[ISY-26 Insteon:Configuration|Host Computer Configuration]], provide you some instructions on the host computer [[ISY-26 Insteon:Start up|Starting the ISY Window]] and an example of the [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]].<br />
<br />
<br />
* [[ISY-26 Insteon:Configuration|Host Computer Configuration]]<br />
* [[ISY-26 Insteon:Start up|Starting the ISY Window]]<br />
* [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]]<br />
<br />
<br />
==Main Window Interface==<br />
<br />
The graphical user interface (GUI) [[ISY-26 Insteon:Components and Navigation|Components and Navigation]] lend to the ease of using the ISY module. This section also details the functionalities and the operations of each [[ISY-26 Insteon:Tool bar|Tool Bar]] icon available in the Top Pane. Plus this section details the functionalities and the operations of each menu option listed in the Top Pane. The top menu options are [[ISY-26 Insteon:File Menu|File Menu]], [[ISY-26 Insteon:Link Management Menu|Link Management Menu]], [[ISY-26 Insteon:Tools Menu|Tools Menu]] and [[ISY-26 Insteon:Help Menu|Help Menu]]. <br />
<br />
<br />
* Root Window<br />
** [[ISY-26 Insteon:Components and Navigation|Components and Navigation]]<br />
** [[ISY-26 Insteon:Tool bar|Tool Bar]]<br />
* Pulldown Menus<br />
** [[ISY-26 Insteon:File Menu|File Menu]]<br />
** [[ISY-26 Insteon:Link Management Menu|Link Management Menu]]<br />
** [[ISY-26 Insteon:Tools Menu|Tools Menu]]<br />
** [[ISY-26 Insteon:Help Menu|Help Menu]]<br />
<br />
<br />
==Window Section Tabs==<br />
<br />
The [[ISY-26 Insteon:Main Tab Layout|Main Tab]] provides the user the ability to view the top level status of the network or the device details by selecting a tree node (tree branch). The nodes available in the tree are [[ISY-26 Insteon:Node|ISY Node]] and [[ISY-26 Insteon:Scene|Scene]]. The [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]] shows the program names in a table form showing if it is enabled, the status, the type of program, the last run time and the last finish time. The [[ISY-26 Insteon:Program Detail|Program Details Tab]] gives the user the ability to create timer or trigger programs. The [[ISY-26 Insteon:Configuration Tab|Configuration Tab]] allows the users to manage global settings such as [[ISY-26 Insteon:Configuring Physical Location|Location]]/[[ISY-26 Insteon:Date and Time Configuration|Date/Time]] and [[ISY-26 Insteon:Messaging Configuration|Messaging]] settings. <br />
<br />
<br />
* [[ISY-26 Insteon:Main Tab Layout|Main Tab]]<br />
** [[ISY-26 Insteon:Node|ISY Node]]<br />
***[[ISY-26 Insteon:Insteon Device|Insteon device]]<br />
** [[ISY-26 Insteon:Scene|Scene]]<br />
* [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]]<br />
* [[ISY-26 Insteon:Program Detail|Program Details Tab]]<br />
** [[ISY-26 Insteon:Tree View|Tree View]]<br />
** [[ISY-26 Insteon:Add to Program|Add to Program]]<br />
** [[ISY-26 Insteon:Manage Program|Manage Program]]<br />
** [[ISY-26 Insteon:Manage Program|Program Content]]<br />
** [[ISY-26 Insteon:Triggers and Schedules|Triggers/Schedules]] - this is info from the 2.4.x Beta which may need revising or removal<br />
* [[ISY-26 Insteon:Configuration Tab|Configuration Tab]]<br />
** [[ISY-26 Insteon:Configuring Physical Location|Location]]<br />
** [[ISY-26 Insteon:Date and Time Configuration|Date/Time]]<br />
** [[ISY-26 Insteon:Messaging Configuration|Messaging]]<br />
<br />
<br />
==Most Frequent How Tos==<br />
<br />
These How Tos are the low complexity frequent ones, for more challenging situations please see the [http://forum.universal-devices.com/viewforum.php?f=9 How Tos (Forum)] for help.<br />
<br />
<br />
* General Operation<br />
** [[ISY-26 Insteon:Your ISY IP Address|Get Your ISY IP Address]]<br />
** [[ISY-26 Insteon:Telnet To Your ISY|Telnet To Your ISY]] <br />
** [[ISY-26 Insteon:Spidering My Network|Spidering My Network]] <br />
** [[ISY-26 Insteon:Generate Typology|Getting a Network Typology Table]]<br />
** [[ISY-26 Insteon:Mutually Exclusive Buttons|Using Mutually Exclusive Buttons]]<br />
** [[ISY-26 Insteon:Adding Controlinc or Remotelincs|Adding Controlinc or Remotelincs]]<br />
** [[ISY-26 Insteon:Working With Keypadlincs|Working With Keypadlincs]]<br />
* ISY Scenes<br />
** [[ISY-26 Insteon:Create a Scene|Create a Scene]]<br />
** [[ISY-26 Insteon:Multi Way Circuit|Multi Way Circuit]]<br />
** [[ISY-26 Insteon:Controlling Keypadlinc LEDs|Controlling Keypadlinc LEDs]]<br />
<br />
<br />
==Troubleshooting==<br />
<br />
To report an error, please post the error/description to [http://forum.universal-devices.com/viewforum.php?f=6 our Forum]. Please provide the error and the situation in which the error presents itself. If possible please include a screen shot(s).<br />
<br />
<br />
* [[ISY-26 Insteon:Errors And Error Messages|Errors And Error Messages]]<br />
* [[ISY-26 Insteon:Red Exclamation Mark|Red Exclamation Mark]]<br />
* [[ISY-26 Insteon:X10 Troubleshooting|X10 Troubleshooting]]<br />
* [[ISY-26 Insteon:Troubleshooting|Communication Problems with Some Devices]]<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]]</div>Yardman 49https://wiki.universal-devices.com/index.php?title=ISY-994i_INSTEON:User_Guide&diff=3076ISY-994i INSTEON:User Guide2007-12-26T18:52:03Z<p>Yardman 49: </p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
The purpose of this document is to guide the system’s installer with the steps necessary to install and configure the Universal Devices’ ISY system and operate the GUI (Graphical User Interface) ISY comes configured for communications with the device(s) of your choice.<br />
<br />
<br />
==Installation==<br />
<br />
This section will cover the [[ISY-26 Insteon:Package Contents|Package Contents]], the basic [[ISY-26 Insteon:Installation|ISY Hardware Installation]], and enumerating the [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]] of the host computer and the network requirements. <br />
<br />
<br />
[[{{ns:6}}:Media Panel.jpg|right|Media Panel]]<br />
* [[ISY-26 Insteon:Pre-requisites|Host Computer Pre-requisites]]<br />
* [[ISY-26 Insteon:Package Contents|Package Contents]]<br />
* [[ISY-26 Insteon:Installation|Hardware Installation]]<br />
<br />
<br />
==Inital Configuration==<br />
<br />
This section will cover the host computer [[ISY-26 Insteon:Configuration|Host Computer Configuration]], provide you some instructions on the host computer [[ISY-26 Insteon:Start up|Starting the ISY Window]] and an example of the [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]].<br />
<br />
<br />
* [[ISY-26 Insteon:Configuration|Host Computer Configuration]]<br />
* [[ISY-26 Insteon:Start up|Starting the ISY Window]]<br />
* [[ISY-26 Insteon:Initial Browser Screen|Initial Browser Screen]]<br />
<br />
<br />
==Main Window Interface==<br />
<br />
The graphical user interface (GUI) [[ISY-26 Insteon:Components and Navigation|Components and Navigation]] lend to the ease of using the ISY module. This section also details the functionalities and the operations of each [[ISY-26 Insteon:Tool bar|Tool Bar]] icon available in the Top Pane. Plus this section details the functionalities and the operations of each menu option listed in the Top Pane. The top menu options are [[ISY-26 Insteon:File Menu|File Menu]], [[ISY-26 Insteon:Link Management Menu|Link Management Menu]], [[ISY-26 Insteon:Tools Menu|Tools Menu]] and [[ISY-26 Insteon:Help Menu|Help Menu]]. <br />
<br />
<br />
* Root Window<br />
** [[ISY-26 Insteon:Components and Navigation|Components and Navigation]]<br />
** [[ISY-26 Insteon:Tool bar|Tool Bar]]<br />
* Pulldown Menus<br />
** [[ISY-26 Insteon:File Menu|File Menu]]<br />
** [[ISY-26 Insteon:Link Management Menu|Link Management Menu]]<br />
** [[ISY-26 Insteon:Tools Menu|Tools Menu]]<br />
** [[ISY-26 Insteon:Help Menu|Help Menu]]<br />
<br />
<br />
==Window Section Tabs==<br />
<br />
The [[ISY-26 Insteon:Main Tab Layout|Main Tab]] provides the user the ability to view the top level status of the network or the device details by selecting a tree node (tree branch). The nodes available in the tree are [[ISY-26 Insteon:Node|ISY Node]] and [[ISY-26 Insteon:Scene|Scene]]. The [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]] shows the program names in a table form showing if it is enabled, the status, the type of program, the last run time and the last finish time. The [[ISY-26 Insteon:Program Detail|Program Details Tab]] gives the user the ability to create timer or trigger programs. The [[ISY-26 Insteon:Configuration Tab|Configuration Tab]] allows the users to manage global settings such as [[ISY-26 Insteon:Configuring Physical Location|Location]]/[[ISY-26 Insteon:Date and Time Configuration|Date/Time]] and [[ISY-26 Insteon:Messaging Configuration|Messaging]] settings. <br />
<br />
<br />
* [[ISY-26 Insteon:Main Tab Layout|Main Tab]]<br />
** [[ISY-26 Insteon:Node|ISY Node]]<br />
***[[ISY-26 Insteon:Insteon Device|Insteon device]]<br />
** [[ISY-26 Insteon:Scene|Scene]]<br />
* [[ISY-26 Insteon:Program Summary Tab|Program Summary Tab]]<br />
* [[ISY-26 Insteon:Program Detail|Program Details Tab]]<br />
** [[ISY-26 Insteon:Tree View|Tree View]]<br />
** [[ISY-26 Insteon:Add to Program|Add to Program]]<br />
** [[ISY-26 Insteon:Manage Program|Manage Program]]<br />
** [[ISY-26 Insteon:Manage Program|Program Content]]<br />
** [[ISY-26 Insteon:Triggers and Schedules|Triggers/Schedules]] - this is info from the 2.4.x Beta which may need revising or removal<br />
* [[ISY-26 Insteon:Configuration Tab|Configuration Tab]]<br />
** [[ISY-26 Insteon:Configuring Physical Location|Location]]<br />
** [[ISY-26 Insteon:Date and Time Configuration|Date/Time]]<br />
** [[ISY-26 Insteon:Messaging Configuration|Messaging]]<br />
<br />
<br />
==Most Frequent How Tos==<br />
<br />
These How Tos are the low complexity frequent ones, for more challenging situations please see the [http://forum.universal-devices.com/viewforum.php?f=9 How Tos (Forum)] for help.<br />
<br />
<br />
* General Operation<br />
** [[ISY-26 Insteon:Your ISY IP Address|Get Your ISY IP Address]]<br />
** [[ISY-26 Insteon:Telnet To Your ISY|Telnet To Your ISY]] <br />
** [[ISY-26 Insteon:Spidering My Network|Spidering My Network]] <br />
** [[ISY-26 Insteon:Generate Typology|Getting a Network Typology Table]]<br />
** [[ISY-26 Insteon:Mutually Exclusive Buttons|Using Mutually Exclusive Buttons]]<br />
** [[ISY-26 Insteon:Adding Controlinc or Remotelincs|Adding Controlinc or Remotelincs]]<br />
** [[ISY-26 Insteon:Working With Keypadlincs|Working With Keypadlincs]]<br />
* ISY Scenes<br />
** [[ISY-26 Insteon:Create a Scene|Create a Scene]]<br />
** [[ISY-26 Insteon:Multi Way Circuit|Multi Way Circuit]]<br />
** [[ISY-26 Insteon:Controlling Keypadlinc LEDs|Controlling Keypadlinc LEDs]]<br />
<br />
<br />
==Troubleshooting==<br />
<br />
To report an error, please post the error/description to [http://forum.universal-devices.com/viewforum.php?f=6 our Forum]. Please provide the error and the situation in which the error presents itself. If possible please include a screen shot(s).<br />
<br />
<br />
* [[ISY-26 Insteon:Errors And Error Messages|Errors And Error Messages]]<br />
* [[ISY-26 Insteon:Red Exclamation Mark|Red Exclamation Mark]]<br />
* [[ISY-26 Insteon:X10 Troubleshooting|X10 Troubleshooting]]<br />
* [[ISY-26 Insteon:Troubleshooting|Troubleshooting]]<br />
<br />
<br />
<br />
<br />
[[ISY-26 Insteon|ISY-26 Insteon : ]]</div>Yardman 49