LeeG

No. Do not go to a backup before the PLM was changed. That backup has the old PLM address. Are the Scenes working from an ISY perspective? That is, if the Scene is turned On or Off through the Admin Console does it work correctly? Was not sure if the Scene problem is through the ISY Admin Console or HS only.

Jeff The text in the popup is correct at 2.8.16. Lee

I was holding my breath as well. The backup would have you got you back in case bad things happened. The PLM should not have been defined as a device so what the ISY would do when deleting it was a question. As Brian has inquired, did you Restore PLM after booting up with the new PLM. Either the Wiki or the User Guide has the steps to follow in replacing a PLM. It is not the same as replacing a device. If a Restore PLM was not done then the Admin Console will not reflect the correct device status because the devices still have the old PLM address. Also Programs will not trigger for the same reason.

The PLM is automatically identified when the ISY boots up with the PLM connected to the Serial port. Delete the PLM definition in the My Lighting tree. Be sure to have a current Backup before deleting the PLM device entry.

The PLM used by the ISY as the powerline interface is not a defined device and should not be in the My Lighting tree.

You need to Delete the device from the ISY, change the button mode from 6 to 8, then add it back to the ISY. The Delete will automatically remove the KeypadLinc from Programs and Scenes. The KeypadLinc will have to be added back to Programs and Scenes after adding in back to the ISY.

Have you thought about changing where the projector is plugged in rather than where the PLM is receiving power? If the ISY/PLM is working for all things at its present plug location it may be more appropriate to move the projector plug point. Also plugging the projector into the FilterLinc bottom filtered outlet might resolve the problem. Plugging the ISY into a FilterLinc is probably not going to resolve anything. It is the electrical interference an appliance puts on the powerline interfering with PLM powerline communication that a FilterLinc addresses and that is accomplished by plugging the offending application into the FilterLinc. Very unlikely the ISY itself is affected by powerline noise.

Under Configuration | Emails/Notifications | Customizations custom responses can be defined.

If running on a windows system enter the ipconfig command in a dos command window. Most subnet masks are 255.255.255.0. The default gateway address is displayed by the ipconfig command.

Yes. I just deleted and added a TriggerLinc under 2.8.16. Be sure Link Management | Advanced Options | Automatic is selected. The Device Type should be specified as [10.02] TriggerLinc. Be sure the TriggerLinc is in linking mode using Set button before using New INSTEON Device. If this does not work invoke Tools | Diagnostics | Event Viewer with Device Communications Events selected and post the trace produced during the add.

Jeff Sorry, I do not work for UDI Lee

Jeff Should be no reason to go to a backup. PLMs should not be losing links when power drops. If the PLM consistently loses link records during a power failure I would suspect a defective PLM. I initially assumed the PLM had been reset during an image update process. There is no reason to reset the ISY or the PLM when upgrading to a later image. I would try a few more Restore Device requests. I'm afraid you have a problem waiting to happen with the Smartlinc. Not that the device itself is a problem but doing Set button links to establish the SmartLinc Scenes with the ISY managing device links it seems that things will get out of sync eventually. The Set button process will not overlay link records written by the ISY but the ISY is not aware of links created by the Set button process. Lee

Jeff When the ISY controls the devices and Scenes Ok but manual control at the device(s) is not reflected back to the ISY it means there is a problem with the link records between the device(s) and the ISY PLM. If a single device (or only a few devices) is having an issue then Restore Device (right click on device node in My Lighting tree) will cause the ISY to rewrite the device link database. Best to try this as first solution as it is the fasted of the recovery options. If all the devices have the same issue then likely the PLM was reset along the way and File | Restore Modem (PLM) is needed. This process can be lengthy if a large number of devices are defined. Lee

If they are Off and you Query them and they report On then that is an issue to discuss with Smarthome. If they were On and the Admin Console shows them On, then power drops and they come up Off as the new devices now do, the ISY and Admin Console will not know they are Off because they do not report status changes at the device. It is necessary to Query the devices to determine if they are On or Off. A Program can be defined that runs at startup to Query those devices if you want the Admin Console and ISY to be aware of status after a power cycle.

Wolf I post this only because the weekend is starting. ISY access to the Internet is established either through the Enable Internet option which requires the router support UPnP or by manually establishing Port forward as you have successfully done. It sounds like the router does not support UPnP so the Enable Internet option does not work and is not necessary when you have manually configured Port forwarding. Lee

From and Insteon perspective a Group is a Scene is a Group. The Insteon command document and PLM developer guide do not have the word Scene in either document. All Controller to Responder relationships are Groups from a hardware perspective. Scene is used in end user documents to describe an Insteon Group. I don't use MobiLinc so I have no reference to what is considered a Group from that products perspective. When an Insteon Direct command is sent from the Admin Console to control an individual device there is no placeholder for a Group number. Link records are not required and not used with an Insteon Direct command.

You turn the Scene On and Off from the Admin Console for both switches to follow. In Insteon, even though switches are cross-linked, turning either switch On/Off "individually" from another controller (PLM in this case) does not cause the other switch to react. That would be cascading Controller function (controller 1 turning on responder 1 which then becomes controller 2 and turns On/Off its responders) which is not the way Insteon works.

lazarow Try bringing up the Admin Console again. I do not always see device status displayed when I start the Admin Console. Restarting the Admin Console resolves the issue here. In my case it is not a PLM problem. I can control devices through the Admin Console and simply starting the Admin Console again usually works. It appears the Java thread that receives the notifications does not receive the device status information. Here it is always all or nothing. When the Admin Console shows device status when it starts everything works fine. Lee

At 2.8.16 the Sensor option is labeled Trigger Reverse. When unchecked, default, the Sensor is Off when the Sensor is NOT connected to GND, On when connected to GND. With Trigger Reverse checked, the Sensor reflects the opposite state. The Sensor is On when NOT connected to GND and Off when connected to GND. My I/O Linc does NOT lose the Trigger Reverse option when power is removed. Perhaps the original author of the Wiki article had an earlier I/O Linc. Note that when the Trigger Reverse option is changed, the Sensor must be cycle On/Off for it to get in sync with the new Trigger Reverse setting. As you say, you can always use the opposite type of magnetic switch. You can see what the opposite type switch will produce by changing the Trigger Reverse option temporarily until the new switch is installed.

The I/O Linc has a Trigger Reverse option that can be set using the ISY. This reverses the On/Off state the Sensor normally indicates so if the magnetic switch you have is giving the opposite effect to what you want/need simply set the Trigger Reverse option.

wharris Thanks for posting the information on your success. The second Set button tap to cause the "double flash" is not necessary. The Auto Discover does not work with a Motion Sensor. The technique you discovered that works is the procedure described in the ISY User Guide for adding a Motion Sensor. The ISY User Guide and Wiki are very good sources for how to information. Lee

My 3A ToggleLinc Dimmer does Beep. Don't have a Relay to test.

The beep is heard at the switch. The chirp is short duration and multiple beeps are suggested as an indication. Not all devices support beep.

johnmsch This is what an Event Viewer trace looks like when the ToggleLinc sends a Fast On. Mon 02/21/2011 09:43:46 PM : [iNST-SRX ] 02 50 15.2A.1C 00.00.01 CB 12 00 LTON-F (00) The 12 is a Fast On command and the ISY interpretation is LTON-F for Fast On. Lee

johnmsch Slower never works. When the toggle is pressed the ToggleLincs normal response is to send an On command or Off command as the case may be. This happens rather quickly, otherwise there would be a delay in the devices turning On or Off. You have to tap the toggle the second time very quickly, before the ToggleLinc can send the On command. When done quickly, the On command is changed to a Fast On command. I have heard other folks have the same problem with a toggle. It is easier to double tap a paddle or KPL button than to move the toggle Up or Down twice quickly. It can be done but it must be done quickly. Once the ToggleLinc sends the On command the opportunity to convert to a Fast On is lost. Keep the Event Viewer active and practice double tapping the toggle until you see a consistent Fast On command in the trace. Lee