LeeG

Normally the PLM will come up faster than the ISY when power is applied at the same time. I don't think having the ISY on a UPS is normally an issue. It does keep the ISY up over short power outages. My guess is the PLM was upset by a power line issue from the outage. Power does not always come up cleanly when restored from an outage. There is often a very large draw on the power when an entire circuit is powered at once. Consider how many houses were restored at the same time when power was restored. Unless this is an issue that surfaces on all outages I would not change the current arrangement. edit: I had my ISY on the UPS years ago. This is a very rural area and power would drop out for 1-2 seconds frequently, some times multiple times a day. Eventually the power co-op redid the entire system. Added more substations, cleaned up the trees along the power lines to prevent wind from blowing limbs into wires. Now the power here is more reliable than my other house in a large town. Eventually took the ISY off the UPS as it was not needed any more but it worked well for the years it was on the UPS.

I think so. It does not say it is wide gap so placement has to be correct. I use one similar to that and it works well.

Unfortunately Trigger Reverse applies only to the commands the I/O Linc Sensor node sends,. That is, the Sensor sends an On when the Sensor turns Off and Off when the Sensor turns On. Trigger Reverse does NOT change the Query response. Query reports the actual state of the Sensor. At 3AM when the ISY does a Query the Sensor node changes state because the Query response is the true state of the Sensor. The best solution is to change the magnetic switch to a NO so Trigger Reverse is not needed.

Looking at the 3.3.10 announcement from Jan 2013 it looks like it should be ISY. rather than www. http://isy.universal-devices.com/99i/admin.jnlp

Do not use Relay follow Input. This option has the relay being controlled by the I/O Linc Sensor.

The initial 0/0 is the default value of the KPL. Set a value to something else; then back to 0/0 which should turn the KPL LEDs Off. Setting to 1/0 should be very dim. edit: there is always a difference of 8 between Off/On LED level so that an On button looks different than Off button. Makes some of the settings appear to make no change.

The ability of the KPL button A to stay in sync with the ToggleLinc depends first on the Scene definition being correct, the KPL button A and the ToggleLinc being Controllers of the ISY Scene. The next thing that must be working is the Insteon network itself. If the ToggleLinc can be turned On/Off and the KPL button A does not always follow the same On/Off pattern the Insteon network is having problems. There is a difference between a Program and the Admin Console turning the ISY Scene On/Off and communication between the two devices. When a Program or Admin Console turns the ISY Scene On/Off the PLM is the Controller and there is no retry associated with the activity. When KPL button A is pressed the KPL is the Controller and the ToggleLinc is the Responder. When the ToggleLinc toggle is pressed On/Off the ToggleLinc is the Controller and the KPL is the Responder. There is retry when the KPL button or the toggleLinc is the Controller. The Insteon network communication is very different depending on which device is the Controller and whether there is retry associated with the activity.

The KPL Secondary button A is a Controller in a Scene ToggleLinc that turns On/Off a load is also a Controller of same Scene I do not understand the remainder of the configuration. The KPL ON/OFF buttons also turn On/Off a load? What are you expecting KPL button A to do?

Does not matter what the device type is. SwitchLinc, ToggleLinc, even another KPL button that is physically controlling the load, it has to be a Controller in the Scene that also has the KPL button as a Controller. Being a Controller is what makes the ToggleLinc turn the KPL button On and Off.

Both the KPL button and the SwitchLinc should be Controllers of the Scene. Remove the SwitchLinc as a Responder and add it back to the Scene as a Controller.

Right click on Scene name, select "Remove from Folder"

There are comm problems between the motion sensor and the PLM, assuming the motion sensor Red LED was blinking indicating it was in linking mode.

The new SwitchLinc can physically replace the defective SwitchLinc. The Replace xxxx.... does NOT send any commands to the old SwitchLinc. 1 Add the new SwitchLinc to the ISY using a dummy name. 2 Right click on old SwitchLinc node, select Replace xxxxx with .... which will display a list of potential replacement SwitchLincs. They must be the same type of device, Relay for Relay, Dimmer for Dimmer. 3 Select the new replacement SwitchLinc and click Ok. When the Replace is done the old node name will remain but with the Insteon address of the new SwitchLinc. The new SwitchLinc added under the dummy name will be deleted. The Admin Console is closed and must be restarted.

Post the actual Program. Put the motion sensor into linking mode, right click on Sensor node, select Diagnostics | Show Device Links Table, post the displayed link table.

The Wiki pulldown sample also does not show options .... Write Updates to Device Diagnostics Advanced

Suggest opening a Ticket with UDI support. Only folks I know that can discuss what an ISY image did more than 18 months ago. I do not think Remove did anything different than what Delete does now. A Factory Reset cannot be activated programmatically and I have never seen command activity that would reset each device function to its default. Edit: what ISY image were you using that had Remove rather than Delete?

I went back to 3.3.10 where the Delete option exists. Not sure what older image had a Remove choice. Yes, factory reset does clear the device link database and resets device configuration options to default.

Deleting a device from the ISY removes references to that device from other devices the ISY is aware of. The "Remove existing links" option insures the device has no active links when adding the device back to the ISY.

4.2.5 uses HAM. WeatherBug is no longer used. Being on 4.2.5 has the Climate Module using HAM.

Yes.

Two problems, first the Repeat precedes the statements to be Repeated. However, as soon as the Status of "Cupula and Pavers" goes to On and the Repeat is executed the Program will be triggered with a False status driving the Else and preventing the Repeat. Not sure why the "Cupula and Pavers" needs to be turned on multiple times.

When adding it back use "Remove existing links" to insure there are no links in the device other than what the normal device add requires.

"Delete" removes the device from the ISY if that is the action desired.

There may be pending updates to the motion sensor and the SwitchLinc. Put the motion sensor into linking mode, right click on Sensor node and select Write Updates to Device. When that is complete do the same to the SwitchLinc. When devices are added to the ISY 'Remove existing links' (the default) should be chosen. This insures there are no links carried forward.

The Program that is being triggered can be gated to not react at 3AM. UDI opened a problem ID for this. What ISY image are you running?