LeeG

Sure. The 4.3.10 image supports TLS1.2 and high grade cipher suites. From the 4.3.10 announcement .... IMPORTANT SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites

Sorry, I do not know what can be done with the 99i. I would move to a supported 994i. Perhaps UDI knows a work around.

The Admin Console no longer supports SSL because of the security issues with SSL. What ISY level and UI level is being used (Help | About). From 4.3.10 announcement, but I believe even 3.2.30 indicated SSL3 no longer supported. IMPORTANT SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites

In addition to what oberkc has mentioned, you have to change the Responder for the Controller. In an ISY Scene "Garage Motion" there are multiple Controllers where the Responder of each Controller must be changed Scene Garage Motion - PLM is Controller of this Insteon Scene Motion Sensor-Sensor - Controller - Motion Sensor-Sensor is Controller of this Insteon Scene KPL button D - Controller - KPL button D is Controller of this Insteon Scene Garage Back Lite - Responder Multiple Adjust Scene statements are required. In Scene 'Garage Motion' Set 'Garage Back Lite' 31% (On Level) - for when the ISY Scene is used in a Program In Scene 'Motion Sensor-Sensor' Set 'Garage Back Lite' 31% (On Level) - for when Motion Sensor-Sensor is Controller In Scene 'KPL button D' Set 'Garage Back Lite' 31% (On Level) - for when KPL button D is Controller

That is great news! Better than I thought it would be. Thanks for posting back the results.

I don't think Exporting the Programs will help. I have seen folks report that deleting and readding device without restarting the Admin Console in between leaves the Programs with the correct device name but I cannot confirm that based on what I have seen. The worst case is the reference to the device will still be there but with an undefined name. Change one device and see what the Program(s) have. Be sure the Program(s) actually work if the device name is correct.

A ToggleLinc can be Replaced with a SwitchLinc assuming both are Dimmer or both are Relay. Add the SwitchLinc under a dummy device name. Right click on ToggleLinc and select Replace ToggleLinc Dimmer/Relay with .... A popup is displayed listing new devices that can replace ToggleLinc. When complete the Admin Console will terminate as SwitchLinc device name will no longer exist.

The SwitchLinc Relay and Icon Relay do not have the required Controller link records (start with E2 01 ........) to report Status change. This is the result of the Delete Modem (PLM). Unless you have an ISY Backup taken before the Delete Modem (PLM) that can be restored (anything that old would likely be very out of date regarding overall Insteon installs) the only solution is to delete and readd those devices that are missing the Controller link records.

Pick a SwitchLinc if possible as it will have less link records. Do a Show Device Links Table. Post the Show display along with the the new PLM Insteon address.

That is the passive coupler (2406H). The down side to that form of coupling is the Insteon signal is transferred to the opposite 120v leg at the same signal level as received. It is normal to have signal reduction so a lose of 50% would mean the Insteon signal starts out at that reduced signal level. With so much Dual Band devices in use today it may not make much difference because the RF signal is transmitted at full strength. That is why I prefer Range Extenders rather than the passive coupler. The up side to the passive coupler is there is no Hop needed to couple the two 120v legs.

Need to know what starts the process. If always, set Program to Run at Startup. If by some device action, such as pressing a KPL button or similar, just need to know what that is. The meat of the Program If depends on additional information Then Repeat every 10 minutes Set 'fan' On Wait 30 seconds Set 'fan Off Else Set 'fan' Off

hutchyx I would try a fresh battery. Is this city/treated water? They remove much of what a Leak Sensor uses to detect water. Does the LEVEL 3 Event Trace show any indication of the Wet/Dry nodes cycling since the v.41 does not lock in a Wet condition.

The V.43 Leak Sensor stays Wet=On once it detects a wet condition. The V.41 Leak Sensor cycles back to Dry when no longer Wet.

What ISY firmware is being used? 4.3.8 may have that ability built in. If not UDI can supply you with a version that does not require a PLM.

Baja Take a look at this link to the Wiki section that discusses Irrigation. It covers the various areas involved. http://wiki.universal-devices.com/index.php?title=Using_the_HAM_Weather_Irrigation_Module

Is the Irrigation command Irrigation - Cycle Complete being used to indicate amount of water applied when EZFlora Program complete?

Whether another Program is needed would be dependent on the logic of the Programs. An If Control .......... Or Control 'Kitchen / Kitchen Cabinets' is not switched Off will drive the Else clause when the device is physically switched Off Of course a separate Program with If Control 'Kitchen / Kitchen Cabinets' is switched Off Then Wait 20 seconds Enable Program 'Kitchen Cabinet Motion' Or Status can be used If Status 'Kitchen / Kitchen Cabinets' is Off Then Wait 20 seconds Enable Program 'Kitchen Cabinet Motion' Just depends on whether looking for the device that is physically turned Off where If Control is used, or If Status when checking for device being Off whether turned Off at the device or something else turned the device Off.

Hops is too complex a subject to explain in a forum post. Go to insteon.com, Technology, White papers, and read the insteondetails.pdf document starting on page 23. It covers Hops and Time slots in detail. Insteon devices are not enrolled. They can be added to the ISY and moved at will if desired. Physical distance is not so important. I have several Insteon devices in a two story detached garage which is more than 300' wire feet away from the main house, all of which operate okay. Devices can simulcast the same message so Hops count has not been an issue. Do you actually have comm issues or something that may be an issue?

No. "If Status" triggers a Program whether the specified Status being checked matches, which can result in a False evaluation that drives the Else clause. "If Control 'xxxx' is switched yyy" triggers the Program ONLY when the condition matches. There is no False evaluation so Else does not run. The "If Control 'xxxx' is not switched yyy" triggers the Program when "not switched yyy" and drives the Else clause because of the "not". Control - [iD 0094][Parent 0001] If Control 'SwitchLinc Dimmer 1' is switched On And Control 'SwitchLinc Dimmer 1' is not switched Off Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Sat 07/04/2015 11:22:59 AM : [iNST-SRX ] 02 50 16.3F.93 00.00.01 CB 11 00 LTONRR (00) Sat 07/04/2015 11:22:59 AM : [std-Group ] 16.3F.93-->Group=1, Max Hops=3, Hops Left=2 Sat 07/04/2015 11:22:59 AM : [D2D EVENT ] Event [16 3F 93 1] [DON] [0] uom=0 prec=-1 Sat 07/04/2015 11:22:59 AM : [ 16 3F 93 1] DON 0 Sat 07/04/2015 11:22:59 AM : [D2D-CMP 0094] CTL [16 3F 93 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Sat 07/04/2015 11:22:59 AM : [D2D EVENT ] Event [16 3F 93 1] [sT] [255] uom=0 prec=-1 Sat 07/04/2015 11:22:59 AM : [ 16 3F 93 1] ST 255 Sat 07/04/2015 11:22:59 AM : [X10-RSP ] 02 63 66 00 06 Sat 07/04/2015 11:22:59 AM : [D2D-CMP 0080] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:22:59 AM : [D2D-CMP 0067] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:22:59 AM : [D2D-CMP 0019] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Sat 07/04/2015 11:22:59 AM : [ X10] A1 Sat 07/04/2015 11:22:59 AM : [ X10] A1/On (3) Sat 07/04/2015 11:22:59 AM : [iNST-SRX ] 02 50 16.3F.93 22.80.0B 41 11 01 LTONRR (01) Sat 07/04/2015 11:22:59 AM : [std-Cleanup ] 16.3F.93-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Sat 07/04/2015 11:22:59 AM : [iNST-DUP ] Previous message ignored. Sat 07/04/2015 11:23:00 AM : [X10-RSP ] 02 63 62 80 06 Sat 07/04/2015 11:23:01 AM : [X10-RX ] 02 52 66 00 Sat 07/04/2015 11:23:01 AM : [ X10] A1 Sat 07/04/2015 11:23:10 AM : [iNST-SRX ] 02 50 16.3F.93 00.00.01 CB 13 00 LTOFFRR(00) Sat 07/04/2015 11:23:10 AM : [std-Group ] 16.3F.93-->Group=1, Max Hops=3, Hops Left=2 Sat 07/04/2015 11:23:10 AM : [D2D EVENT ] Event [16 3F 93 1] [DOF] [0] uom=0 prec=-1 Sat 07/04/2015 11:23:10 AM : [ 16 3F 93 1] DOF 0 Sat 07/04/2015 11:23:10 AM : [D2D-CMP 0094] CTL [16 3F 93 1] DOF op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:23:10 AM : [D2D EVENT ] Event [16 3F 93 1] [sT] [0] uom=0 prec=-1 Sat 07/04/2015 11:23:10 AM : [ 16 3F 93 1] ST 0 Sat 07/04/2015 11:23:10 AM : [X10-RSP ] 02 63 66 00 06 Sat 07/04/2015 11:23:10 AM : [D2D-CMP 0080] STS [16 3F 93 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Sat 07/04/2015 11:23:10 AM : [D2D-CMP 0067] STS [16 3F 93 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Sat 07/04/2015 11:23:10 AM : [D2D-CMP 0019] STS [16 3F 93 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Sat 07/04/2015 11:23:10 AM : [ X10] A1 Sat 07/04/2015 11:23:10 AM : [ X10] A1/Off (11) Sat 07/04/2015 11:23:11 AM : [iNST-SRX ] 02 50 16.3F.93 22.80.0B 4B 13 01 LTOFFRR(01) Sat 07/04/2015 11:23:11 AM : [std-Cleanup ] 16.3F.93-->ISY/PLM Group=1, Max Hops=3, Hops Left=2 Sat 07/04/2015 11:23:11 AM : [iNST-DUP ] Previous message ignored. Sat 07/04/2015 11:23:11 AM : [X10-RSP ] 02 63 63 80 06 Sat 07/04/2015 11:23:12 AM : [X10-RX ] 02 52 66 00 Sat 07/04/2015 11:23:12 AM : [ X10] A1 Should have included a command that "If Control" is not checking. Fast On does not trigger Program (no X10 traffic). Sat 07/04/2015 11:46:21 AM : [iNST-SRX ] 02 50 16.3F.93 00.00.01 CB 12 00 LTON-F (00) Sat 07/04/2015 11:46:21 AM : [std-Group ] 16.3F.93-->Group=1, Max Hops=3, Hops Left=2 Sat 07/04/2015 11:46:21 AM : [D2D EVENT ] Event [16 3F 93 1] [DFON] [0] uom=0 prec=-1 Sat 07/04/2015 11:46:21 AM : [ 16 3F 93 1] DFON 0 Sat 07/04/2015 11:46:21 AM : [D2D-CMP 001A] CTL [16 3F 93 1] DFON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Sat 07/04/2015 11:46:21 AM : [D2D-CMP 0019] CTL [16 3F 93 1] DFON op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:46:21 AM : [D2D EVENT ] Event [16 3F 93 1] [sT] [255] uom=0 prec=-1 Sat 07/04/2015 11:46:21 AM : [ 16 3F 93 1] ST 255 Sat 07/04/2015 11:46:21 AM : [D2D-CMP 0080] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:46:21 AM : [D2D-CMP 0067] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sat 07/04/2015 11:46:21 AM : [D2D-CMP 0019] STS [16 3F 93 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Sat 07/04/2015 11:46:21 AM : [D2D EVENT ] Event [2E ED 5D 2] [sT] [255] uom=0 prec=-1 Sat 07/04/2015 11:46:21 AM : [ 2E ED 5D 2] ST 255 Sat 07/04/2015 11:46:21 AM : [iNST-SRX ] 02 50 16.3F.93 22.80.0B 41 12 01 LTON-F (01) Sat 07/04/2015 11:46:21 AM : [std-Cleanup ] 16.3F.93-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Sat 07/04/2015 11:46:21 AM : [iNST-DUP ] Previous message ignored.

It would be useful to know the load Amperage, starting and running.

With one exception, the If evaluation may be different. If Program A does a Run Else for Program B, the Program B Icon will be solid Red while running Else statements even though the If could evaluate as True. The Run Else forces the Else clause to run regardless of whether the If would evaluate as True

dtt255 My door openers are Wayne Dalton which use multi button RF only door controls. Had to do the same attachment you are considering. Has worked for years with Insteon control of detached garage doors. I have experience with small low wattage soldering iron so did the work myself. If you have a usual assortment of neighbors very likely at least one will have the needed soldering iron and experience using it. Using caution the wires can be attached with no damage to door controller.

* Would the ISY have better data if you called out devices in programs, when possible, rather than scenes? Yes. But Scenes should/do work unless you have Insteon network issues. Doing individual devices brings the devices to the new state one at a time. Much better to use Scenes and fix the Insteon network. * When devices report back there status, how is that used by the ISY? The new Status is associated with the device reporting. * How many device status tables are there in an ISY & PLM network? PLM has no Status information stored for device. All Status information storage handled by ISY (in one place as far as I know).

The Green bar indicates the last time the Program was triggered it was True The Red bar indicates the last time the Program was triggered it was False

"To have one switch control the other, and visa versa, don't they each need to be a controller of the other? " Yes, that is correct. See my post #2 above. That is what Scene "entry light" does. it causes the two switches to be cross-linked so both switches operate the other. This is the arrangement you should have now. "If I make them both a responder, the 3 way option will not work, right? " Wrong. The "entry light" Scene has linked the two switches as Controller/Responder to each other. Creating another Scene that I called "downstairs lights" which has the two switches as Responders (and other devices also as Responders) does not affect the "entry light" Scene. The "entry light" Scene creates the three way switch configuration. The additional Scene "downstairs lights" with those same switches (and others) as Responders allows all the downstairs lights to be turned Off. Again, the "downstairs lights" Scene does not alter the cross link 3 way arrangement created by the "entry light" Scene.