satwar

I think you got it right, about the inhibit state. After pounding away on the keyboard for a few hours, I finally remembered how to connect to the PLM and then to EZFlora. I turned Inhibit Off and all is fine (i think it's too late now) I'll check it more rigorously tommorow. Thank you so much, this problem was driving me nuts.

Well I ran an electrical extension cord from the same receptacle that the EZFlora is plugged into and ran the extension cord to the PLM. With both PLM and EZFlora on the same cicuit, the on/off commands still are not working reliably Diagnostics Level 3: First attempt didn't work Wed 09/23/2015 03:28:15 PM : [iNST-TX-I1 ] 02 62 1E 7A 55 0F 40 00 Wed 09/23/2015 03:28:15 PM : [iNST-ACK ] 02 62 1E.7A.55 0F 40 00 06 (00) Wed 09/23/2015 03:28:15 PM : [iNST-SRX ] 02 50 1E.7A.55 13.20.08 2B 40 00 (00) Wed 09/23/2015 03:28:15 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Second attempt worked Wed 09/23/2015 03:28:18 PM : [iNST-TX-I1 ] 02 62 1E 7A 55 0F 40 00 Wed 09/23/2015 03:28:18 PM : [iNST-ACK ] 02 62 1E.7A.55 0F 40 00 06 (00) Wed 09/23/2015 03:28:18 PM : [iNST-SRX ] 02 50 1E.7A.55 13.20.08 2B 40 80 (80) Wed 09/23/2015 03:28:18 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 09/23/2015 03:28:18 PM : [ 1E 7A 55 1] ST 255 My Isy99i has firmware 3.3.10 and UI 4.2.30

I'm currently running isy99i @ firmware 3.3.10 I have a small house and both modules are in the basement, perhaps within 20 ft.

I have a Isy99i (recently ordered a isy994i) running firmware 3.3.10, and EzFlora v28. I'm really struggling with this device. I used "add an Insteon device" and I got 8 different Irrigation zones (which was good). The first sign of trouble is when I select a zone and send the "ON" command it will not turn on. It takes multiple tries of "ON" then "OFF" commands on a zone before it finally changes state It goes without saying that my Irrigation Program (which turns on each zone on in sequence) does not work either.

Yes, I agree. I have a simple surge protector on this circuit with no problem. The fancier power bar was the culprit. Stopped the Insteon signals from traveling any further down the circuit.

Goddamn power bar. Something you said about communication problems rang a bell with me because I indeed was getting ISY warnings about "loose connections". This has been a periodic problem in this house circuit for many years, so I decided to chase it down. I tore apart the light switch boxes in this circuit where the Insteon modules "loose connection" message was showing, several times with no avail. For a time the "loose connections" went away, but then came back. After spending a frustrating day on this I slept on it, and woke up this morning thinking about "what about the power bar" I have plugged into this circuit. All modules downstream of where this powerbar was plugged in where reporting communication problems. Eureka !!!! Problem solved. What a pain this was !!!!! Lesson learned, very painfully.

I've run Isy firmware 3.2.6 and 3.3.10. Isy says it can't identify Insteon engine

I'm having all sorts of trouble adding a new 2466SW to my isy99i network. I noticed both troublesome switches have version 5.8 whereas all previous switches were version 5.3. Do I need to upgrade to version isy994 to enable 2466sw version 5.8

I've managed to hookup I1 & I2 to a dry contact device as per attached drawings, and the EZIO2X4 responds correctly. I think I understand that to hookup I3 & I4 to dry contact devices I need to install a 10k pull-up resistor between +5V terminal and I3 (I4) terminal. Then I connect the wire pair coming from dry contact device, between I3 (I4) terminal and Gnd terminal ? Does EZIO2X4 need to be reconfigured using SHH utility to enable this to work ? Thanks in advance for your help.

Folder Conditions for 'House Deicer Control' Add conditions to limit when programs in this folder are allowed to run. If $Automatic.Gutter.Deicing is 1 Then Allow the programs in this folder to run. Program Content for "Driveway Gutter Heater Logic" If Status 'Driveway / Outdoor Temp Alarm - 9' is On And $Snow.On.Roof is 1 Then Set 'Driveway / Gutter Driveway' On Else Set 'Driveway / Gutter Driveway' Off Program Content for "Porch Gutter Heater Logic" If Status 'Driveway / Outdoor Temp Alarm - A' is On And $Snow.On.Roof is 1 Then Set 'Driveway / Gutter Porch' On Else Set 'Driveway / Gutter Porch' Off

I set the values of these variables by running simple macros in mControl, which write to ISY with REST commands. I simply push a button in mControl labelled "Automatic Gutter Deicing" and $Automatic.Gutter.Deicing is set to 1 in ISY. I push a button in mControl labelled "Manual Gutter Deicing" and $Automatic.Gutter.Deicing is set to 0 in ISY. Similarly I have buttons in mControl labelled "Snow On Roof" and "No Snow on Roof" which change the value of $Snow.On.Roof in ISY to 0 and 1

I don't know how to copy code from ISY. The folder condition is: If $Automatic.Gutter.Deicing is 1 where $Automatic.Gutter.Deicing is a state variable

Yes I have been slow to learn this. I guess the wording of the folder condition "allows the programs in this folder to run" was not fully understood. I think that's where I got the notion that the program was running once the folder flag was set.

Okay Guys, thanks for the help. It seems that I'm barking up the wrong tree. Since temperature alarm state status only updates in the gutter heating program while the program is running, I'll just have to leave it running. The only time the program is stopped (folder flag set to 0), is when a pure manual operation of gutter heaters is desired. The user then only has to specify whether or not Snow is On Roof. Eventually I'd like to replace the manually set Snow On Roof status, direct detection of free-water in gutter. Thanks for getting me to think outside the box.

I monitor trmperature with a Winland Enviroalert 400, whiich provides a contact output, which is read by EZIO2x4

Yes the input state display for 'Outdoor Temp Alarm' on the EZIO shows correctly on ISY Admin Console, but the ISY program doesn't see the current state. The state is only picked up correctly after a change in alarm state occurs. I do this now, by manually changing alarm limits on the temperature monitoring device, which toggles the alarm state off and then on again. My problem occurs when the temperature alarm is on before the ISY program is started. I start the ISY program by setting it's folder flag =1. For some reason ISY program doesn't see alarm state correctly until I toggle the alarm state.

Yes $Snow.On.Roof is a state variable which I toggle between 0 and 1. The problem is ISY does not recognize the true status of 'Outdoor Temp Alarm' until it changes. Could it be that I'm running 3.6.2 firmwae on ISY ?

Yes, that is exactly what my problem is. I seem to need a trick to toggle the 'Outdoor Temp Alarm' status, which is a contact input picked up from a EZIO module. If Status 'Outdoor Temp Alarm' is On And $Snow.On.Roof is 1 Then Set 'Gutter Heater' On Else Set 'gutter Heater' Off

I really don't understand how ISY programs run, and I have a problem with the execution of a gutter heating program. The program executes when the folder flag is set to "1". The program simply checks whether a temperature alarm is "on", and if so, turns the heating cable on. My problem is that my ISY program doesn't see that the temperature alarm is "on" if the temperature alarm occurs before the program starts running (i.e. before the folder flag is set to "1"). All subsequent alarm status changes are read successfully What kind of statement should I use to force the ISY program to read the temperature alarm status when program first starts running ? Hope this makes some sense.

That sounds like what I want to achieve ! Thank you very much, once again.

Well that's a no-no for me, but I have had success in pushing the button on 2450 casing. I can get relay to follow sensor, although the relay status doesn't change on isy screen (possibly another 3.3.3 issue). But when I activate "latching, continuous", I get no sign of latching, just the relay following sensor. Are all these issues 3.3.3 issues ?

I don't seem to be able to change the Options settings on my 2450. Is there a trick ?

I was planning to monitor an alarm condition, which will be only be triggered momentarily. I would like to latch the alarm condition in the isy. The alarm condition in the isy would then be reset manually. Can this functionality be achieved in the isy ?

Well I'll be a monkey's uncle. I was out of RF range. I was ready to throw this USB PLM out, because it wouldn't work, and all along I was out of range. Unbelievable !

Yes I agree, but I couldn't connect to EZIO2x4. First step of connecting to PLM seemed to work but got no response from EZIO2x4 when I typed in Insteon ID address