LeeG

To programmatically perform the same function as pressing the A button issue In the Then clause Set Scene 'scene with button A as controller' On. This will turn On button A and the Responders defined in the Scene. Perhaps what is missing from the question is how do you want to trigger the Program. Under what conditions would the Program run and perform the same function as pressing button A.

Did you power off the ISY and the old PLM, plug in the new PLM, power up the ISY, then do a Restore Modem (PLM).

Most likely issue is poor comm with the I/O Linc location. Move the I/O Linc to the PLM plug point and test the Sensor there by using a jumper between GND and Sensor to turn the Sensor On/Off. If the status changes look into comm in the garage. If the status does not change at the PLM plug point either the link records in the I/O Linc or the PLM have been lost. A Show Device Links Table and Compare will verify if the I/O Linc link records are intact. The easiest approach with the PLM is to do a Restore Modem (PLM) to rebuild the PLM link database. Do other devices show state change? If no device shows a state change then look at the AV such as Kaspersky, Avast, and AVG.

andrew67 I agree with much of what you wrote. However, it is not possible to do as you suggest. Commands which were available for device link management since day one of Insteon have been physically removed from the new devices. SmartLabs told everyone these commands were depreciated back in 2007. However, it was not until the new I2CS protocol surfaced beginning in March 2012 were these depreciated commands actually removed from the new devices. Defining a device as an old KeypadLinc where the ISY used commands that have been around literally forever no longer work with the new devices. It is absolutely necessary for the ISY to dynamically obtain the information from the device itself to know what the device is and what commands must be used. If the ISY accepted a device override all the link management commands would fail as they literally no longer exist in the new devices. For years one could buy an 8 button KeypadLinc where link management commands that worked in 2006 continued to work even into 2012. Certainly new features such as Beep and better Backlight control were introduced but the underlying device link management remained intact. It took months for SmartLabs to roll out devices with firmware containing I2CS protocol and SmartLabs did not publish a schedule when each device type would be converted to I2CS. In a perfect world one could install Insteon and walk away. Unfortunately that is not possible with Insteon. With the changes to the basic protocol and its additional requirements combined with the removal of commands that have been with use literally from day one of Insteon it cannot be installed and forgotten. It is a guarantee that a user will be burned if he/she does not stay actively aware of what SmartLabs/Smarthome is doing and what the ISY is forced to adapt to.

The KeypadLinc Dual Band device was released after 3.3.10 was released. Only one of several devices that have come out since 3.3.10 was released. The problem is the 99i memory it not large enough to accept the support for all the devices that have come out since and will continue to come out later. There was an update path announced back in Feb to get from a 99i to a 994i. This has long since expired being some 7 months ago. The OP should contact UDI directly. andrew67 All things have a life span. The Dual Band KeypadLinc is not compatible with an ISY-26, nor an ISY-99i. It is compatible with an ISY 994i. There is no doubt in my mind that somewhere in the future the 994i will be replaced with something bigger and better. That is the nature of technology.

First, is the OutletLinc a Relay or Dimmer? If an OutletLinc Relay it does not have a Controller function which means turning it on Locally will not notify the ISY of that activity. That is why it cannot be added to a Scene as a Controller because the ISY knows an OutletLinc Relay has no Controller function. Second, Secondary KeypadLinc buttons cannot be turned On/Off with Direct commands. Insteon Direct commands have no mechanism for identifying which Secondary button to control. A Secondary KeypadLinc button has to be assigned as a Responder in a Scene and the Scene turned On/Off to control a Secondary KeypadLinc button LED. Really want to go back to using a Scene to operate so many devices. A Scene will have the devices reacting essentially simultaneously. Doing the devices one at a time will take seconds before the last device reacts.

Blinking Red is the correct behavior. It means the device sending the test RF message and the device receiving the test RF message are on the same 120v leg.

The two program structure looks fine. Wait and Repeat statements allow the If to be reevaluated if something the If is checking changes. I have not used the On/Off Outdoor module. Have no experience with its range. Keep it vertical for antenna orientation and water out of the outlet. A Stucco exterior is applied over a metal mesh (I think). That could degrade the ability to get the RF through a Stucco wall. I would be worried about depending on RF through the exterior wall at a distance.

How is Motion Sensor 2 configured? If the Motion Sensor times out before the Wait time expires the change in Sensor node status will retrigger the Program. The If will now be False driving the Else clause so the statements after the Wait to turn Off the devices will never execute. One solution is to split the Program into two. The current If is in Program 1 that invokes Program 2 in the Then clause. Program 2 contains the current Then statements. That way when the Motion Sensor times out it does not affect Program 2. The current device firmware does not honor the duration. Perhaps someday the devices will be updated to react to duration. For now Beep duration has no affect.

Having the Program Disabled prevents the If section from triggering the Program which is part of your requirement. The Disabled Program can be invoked with a Run Program 'xxxxx' If section which will have the If section evaluated to determine if the Then section (If True) or the Else section (If False) will be execute. If this did not work then determine why not as it should have. The Programs | Summary tab will show if/when the program was last executed (Last Run Time) and whether the If evaluated True or False by what the Status column shows.

There is nothing linked to button G based on the Show Device Links Table of the Mini Remote except the PLM. The InLineLinc could have a Responder link (broken link) which would allow it to respond but the only thing linked to button G is the PLM itself. The InLineLinc will have to be access to get its Insteon address.

A Program without anything in the IF section can never self trigger. Enabling a Program does not cause the Program to be triggered. Enabling a Program allows the IF section to trigger the Program. Instead of Enabling the Program send a command to Run the Program.

The PLM 24.1A.B5 is NOT added to the ISY. The PLM is automatically detected when the ISY boots up. The Restore Modem (PLM) was suggested because the PLM was described as the "old PLM" which was taken to mean the PLM had been replaced. Since the PLM was never replaced the Restore Modem (PLM) was not required. Did not hurt anything to do the function. The Kitchen SwitchLinc is on the opposite 120v leg from the PLM since it was blinking Green. The other SwitchLinc must be out of RF range of the PLM since it did not blink at all. I think you indicated the InLineLinc was manually linked to the Mini Remote. What button was the InLineLinc linked to?

24.1A.B5 UNK Device is an old PLM, do Restore Modem and try again I do not know what 24.1A.B5 or 24.22.D7 is. In a previous post 24.1A.B5 was described as an old PLM. Is that the PLM Insteon address? Was the SwitchLinc LED that was blinking Red or Green?

The PLM is NOT added to the ISY as a device. If the PLM is a 2413 Dual Band PLM tap the PLM Set button 4 times which puts it into RF test mode. Look at the SwitchLinc LEDs to see if they are responding to the PLM RF test. If so what are the LEDs on both SwitchLincs doing in response to the PLM test? There are two Insteon addresses that cannot be reached. Presumably one of the addresses is the InLineLinc. Do you know what device the other address is associated with?

From the link database the Mini Remote has not been added to the ISY OR the PLM the ISY is using was changed and the procedure for using a new PLM was not followed. What devices are being used to couple the 2 120v legs?

Two Access Points are positioned outside of all structures running on extension cords. How are you maintaining vertical orientation which is critical to RF range? Power panels alternate the 120v legs vertically; A,B,A,B, and so on. Not A on the left side and B on the right side. With one device blinking Green and one blinking Red in the garage they are on opposite 120v legs. Now that Trigger Reverse has been activated again all the issues with Query results being different from Sensor command based states are in play. The ISY 3AM Query of all devices means the Sensor state displayed in the Admin Console will be different when viewed in the morning even though the door has not moved. The Event Trace at LEVEL 3 showing several door open/close activities will show the general health of the comm from the garage to the ISY PLM location. Control of other Insteon devices in the garage may help clarify comm. reliability since from the blinking Red versus blinking Green devices are on opposite 120v legs in the garage.

Put the Mini Remote into manual linking mode using the Set button. Right click the Mini Remote Primary node, select Diagnostics | Show Device Links Table. Assuming you know the Insteon address of the other devices the Insteon address that does not look familiar should be the InLineLinc. For future reference, the Set button links that have been done between the Mini Remote and the other devices are not known to the ISY. Eventually the link records created that way will be deleted and/or overlaid. All device linking should be done with ISY Scenes.

I used the event viewer in the Admin Console. The Admin Console is a subscriber like any other application. It was easier than trying to catch screen captures of the temp changes displayed for the node.

I see temp (status) changes from my 2441TH. I increased the ambient temp several degrees with these temp change messages being the result as the ambient temp returned to normal. Tue 09/10/2013 11:33:28 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 6E AC (AC) Tue 09/10/2013 11:33:28 AM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Tue 09/10/2013 11:33:29 AM : [ 1D 6C D6 1] ST 172 Tue 09/10/2013 11:33:36 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 6E A5 (A5) Tue 09/10/2013 11:33:36 AM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Tue 09/10/2013 11:33:36 AM : [ 1D 6C D6 1] ST 165 Tue 09/10/2013 11:33:42 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 6E A2 (A2) Tue 09/10/2013 11:33:42 AM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Tue 09/10/2013 11:33:42 AM : [ 1D 6C D6 1] ST 162

As Brian has already covered the new Dual Band device is supported by ISY firmware later then 3.3.10. It is best to move to a 994i as this is not the only case of a new device being released by Smarthome after 3.3.10 was released. Try using New INSTEON Device and select the specific Device Type for 2486D. Not sure but that may override the normal ISY use of the cat/subcat (device type) retrieved from the device.

Either press and hold the On paddle until it ramps to full On, then cycle Off to On OR double tap the On paddle to generate a Fast On which will bring the load to full On, then cycle Off to On. It sounds like the SwitchLinc is operating in Resume Bright mode which has the On paddle return to the last Bright level. Check the SwitchLinc User Guide under Local On Level "resume bight" for a description of the function and how to turn Off "resume bright". That option is not under control of the ISY.

Repeat statement is positioned at the beginning of the statements to be repeated. The statements that are part of the Repeat are indented. Link to UDI Wiki that discusses Repeat http://wiki.universal-devices.com/index ... EON:Action Use the blinking lights with care. The process can be a significant load on Insteon. Since this only happening if the alarm trips it will be infrequent but could interfere with other Insteon traffic while the lights are being "blinked".

This REST command turns the device On to approx 60% (255 * .60 = 153). http://192.168.2.2/rest/nodes/15 B2 6A 1/cmd/DON/153

Tap the Leak Sensor Set button. The Leak Sensor will alternate between Wet message, Dry message, Wet message, etc for each Set button tap.