IndyMike

EDIT: I've just re-read your post and am not sure whether your outlets are on the same breaker (branch) or different breakers. If the outlets are on different breakers it's also possible that you are measuring different phases. Voltage differences across the phases are not uncommon when there is a load imbalance (one phase heavily loaded, the other lightly). If your comfortable with it, try measuring the voltage at the load panel for each phase. If you have no loads installed on your outlets, the voltage at the panel should be the same as the outlet voltage. If it is not, you either have a very bad connection or a device drawing significant current. The resonances that ELA and I were referring to apply at the Insteon frequencies of 130 KHz. They do not apply to the 60 Hz power distribution within your home. Original message below- Mark, I am very much hoping that you simply had a bad connection to your voltmeter when you measured the 114V. Assuming that there was no load on the outlet at the time, a 3 volt drop (117 to 114) would qualify as an extremely bad connection. Your meter should be high impedance and therefor be drawing an insignificant amount of current and no noticeable voltage drop. Please inspect/tighten the connections to this outlet and retest. If the drop is occurring at the wire attachment, it will generate heat (i.e. dangerous). It's possible that the receptacle "prongs" were simply oxidized and not allowing your meter to make a good connection. The acid test would be to apply a light load (60 watt incandescent) and monitor for a voltage drop. Again, a 60W load should be insignificant. If you measure a drop with the load installed, replace the outlet and re-test. IM

Hello Mark, Let me start by saying that I like your description of the PLM communicating into the load panel. Assuming that PLM is close coupled to the panel, it will attempt to drive the loading at that point to the full 3.2 Vp-p. The load at the panel is a complex composite of all of the loads in your home reflected back to the panel. I say attempt because it's possible that the signal loading at the panel is high enough that the PLM can't drive it to full level. The signal will then fan out across the branch connections on that phase. Signal degradation on a given branch can usually be viewed on a branch by branch basis. If you have a passive coupler that the panel, the PLM signal will be coupled in phase at a lower level and also fan out on that phase. If you are using a RF coupler, the PLM signal will be coupled on the next hop, but again at whatever level the RF coupler can drive into the load it "sees" (presumably 3.2Vp-p). ELA is exactly correct that the signal propagation through the branch circuits can be an extremely complex "transmission" with resonances and nodes as the R-L-C characteristics interact. That said, ELA and I share similar backgrounds and tend to think in these terms (EMI/EMC background - other engineers consider us to be "geeks"). Not speaking for ELA, but I sometimes drift off into complex theories of what might happen rather than gathering all the facts and focusing on what is happening. For most installations, you can consider the powerline as a simple resistive divider circuit. The longer the line, the more series resistance. The more loads installed, the lower the resistance to return (more signal degradation). This resonance condition was exactly what I was thinking of when you described the following: Since your SWL responded well to an off command, I was theorizing that you had a long transmission line and the added Inductive load of the transformer(s) was changing the powerline impedance and effectively killing a resonance at that point. I had hoped that you would install a incandescent lamp at the IOLinc location (not at the switchlinc) and thereby change the R-L-C loading for both the On and Off cases. Although you mis-interpreted the intent, you may have provided enough information to disprove this theory: 1) Your Switchlinc is close coupled to your media center and both are close coupled to the panel (18 inches - not a long line). 2) Your PLM is close coupled to the panel. 3) Is your PLM on the same phase as the SWL, or at least bridged at the panel? If your PLM is on the same phase (or coupled at the panel), your distances should be too short to set up a resonant condition (low line impedance). Adding an incandescent load would not have accomplished anything. A more likely scenario would be - 1) Your media center components are significant "signal suckers". Since these are close to the panel, they could be degrading signals from distant transmitters. 2) You have some noise on this circuit. The combination of noise and "signal suck" are degrading the inbound PLM signal to the point where it is marginal. When the SWL is turned on, you are adding the inductive load of the transformer and effectively filtering some of the noise at the SWL location. This allows the device to hear to the "off" command. Since your media center does appear to be a source of loading/noise (and it's close to the panel), I would agree with the others that filtering this circuit would be wise to prevent possible problems at the PLM. I am also curious whether you swapped to the opposite phase when you reconnected your SWL. In regard to your last comment: What ELA stated is absolutely true in a very strict controlled environment. Resonances will happen, particularly on long lines. In the home, this is normally a "transient" condition since the impedance of our home powerlines are constantly changing (every time we switch on or plug in a device we change the impedance). While I've been able to setup and measure resonances under controlled conditions, I have never observed one in the home. I have witnessed 2 instances of "global signal damagers": 1) The Boosterlinc - these devices actively interfere with insteon signals. The newer "Insteon blessed" devices are better than the old models, but still interfere with low level Insteon signals (unless there is a Rev 3.0 out there). 2) Oscillating power devices - These can be triac dimmer outputs that are "unhappy" with the load (CFL) or other power outputs that are on their last legs. While oscillating, these devices can draw significant power and radiate long distances (lower frequency than Insteon). Noise produced by these devices can activate the Automatic Gain Control (AGC) on Insteon devices and render them "deaf" to valid transmissions. Not sure whether this helps or simply confuses things further... IM

Hi Mark, I've been watching from a distance and have not had anything to add because Lee's diagnosis has (as usual) been excellent. You're last post indicated that the "off command" may be working properly, while the "on command" shows the delay. This is rather odd unless the powerline is interacting with the installed devices on this circuit. [*:14x3knq3]Is this a GFCI or AFCI circuit? [*:14x3knq3]If turning on the LED transformer does improve communications, it could be performing the function of a line terminator. Could you try plugging in a Incandescent lamp in the IOlinc location?

Hello Michel, The Icon is fully functional when used in the "Automatic" messaging mode which the ISY defaults to. Issues only arise when the user manually switches to the "Device reported mode". I completely agree with your assessment of the priority. I noted the addition of I2 support for the Icon in the release notes and wanted to give feedback. Sincerely, IM

Hi Michel, Great idea - I had forgotten about the manual scan. The manual scan works like a charm using a start address of 0x00F8. Sun 08/14/2011 08:43:02 PM : [14 78 3B 1 ] Using engine version i2 for 'BSMT Bed' Sun 08/14/2011 08:43:02 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 00 FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/14/2011 08:43:02 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00) Sun 08/14/2011 08:43:02 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 08/14/2011 08:43:02 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00 Sun 08/14/2011 08:43:02 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sun 08/14/2011 08:43:03 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 00 F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/14/2011 08:43:03 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00) Sun 08/14/2011 08:43:03 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 08/14/2011 08:43:04 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 F7 01 A2 10 13 22 F9 FF 1F 00 00 Sun 08/14/2011 08:43:04 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sun 08/14/2011 08:43:04 PM : [All ] Writing 0 bytes to devices

Hello Michel, I1 (peak/poke) operations work fine with the Icon. It's the I2 read/write operations that present a problem. As expected, I2 restore operations fail for the same reason as the link read operation. Honestly, not that big a deal with the Icon since it doesn't have that many links. Just need to make sure that "Automatic messaging" is checked in the ISY options to enable the I1 mode. If this were a KPL, I'd be whining a bit more. Thanks for the prompt reply, IM

Revision 3.1.6 downloaded and installed without issue. Attempted a link table read from my 2876SB Icon V.39 using I2 protocol - no go. There is some upside. Previous revisions of the ISY firmware really wouldn't communicate much at all with this device in I2 mode. With rev 3.1.6 things are a bit more clear. The ISY appears to be reading from start address 0FFF while the device is responding with start address 00FF. The ISY rejects the response and then "errors out" after 3 attempts (log below). The data reported by the Icon is correct for the first link record. I believe this is due to the smaller link table in the more recent versions of the Icon switch (verified by LeeG some time ago). Not sure that I can call this a bug. Just another difference in the module configuration (exception) that needs to be accounted for in the ISY. Sorry guys, I've lost track of the number of "exceptions" and "workarounds" that you've already implemented. This may be another one for the list. IM Sat 08/13/2011 12:29:33 PM : [14 78 3B 1 ] Querying engine version Sat 08/13/2011 12:29:33 PM : [iNST-ACK ] 02 62 14.78.3B 0F 0D 00 06 (00) Sat 08/13/2011 12:29:33 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 0D 01 (01) Sat 08/13/2011 12:29:33 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 08/13/2011 12:29:33 PM : [14 78 3B 1 ] Retrieved engine version is i2 Sat 08/13/2011 12:29:34 PM : [14 78 3B 1 ] Using engine version i2 for 'BSMT Bed' Sat 08/13/2011 12:29:34 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {isy requesting data from address 0F FF} Sat 08/13/2011 12:29:34 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00) Sat 08/13/2011 12:29:34 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 08/13/2011 12:29:34 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00 {icon responding with data from address 00 FF} Sat 08/13/2011 12:29:34 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 08/13/2011 12:29:34 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored {response rejected due to invalid address range} Sat 08/13/2011 12:29:43 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {read attempt #2} Sat 08/13/2011 12:29:44 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00) Sat 08/13/2011 12:29:44 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 08/13/2011 12:29:44 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00 Sat 08/13/2011 12:29:44 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 08/13/2011 12:29:44 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 08/13/2011 12:29:53 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {read attempt #3} Sat 08/13/2011 12:29:54 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00) Sat 08/13/2011 12:29:54 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 08/13/2011 12:29:54 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00 Sat 08/13/2011 12:29:54 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 08/13/2011 12:29:54 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 08/13/2011 12:29:58 PM : [All ] Writing 0 bytes to devices

Michel, Fix verified with V3.1.5.

Hello ryarber, I've had problems communicating with my 2876sb Icon (V.39) when using I2 mode. Check to make sure that the ISY is set to use the "Automatic" communication mode (menu item: "Link Management/Advanced Options/Automatic"). I can communicate with my 2876DB with V3.1.5 when using I1 mode. I2 mode is a no-response (same with previous revisions of the ISY firmware).

30 minute turnaround on a bug fix? I'd be willing to wager that's a new benchmark. I've become accustomed to excellent service from the UDI team, but will try not to hold you to this standard for future releases. Confirmed proper triggering with V3.1.5. Using a .6281 Irrigation requirement, the ISY correctly evaluated a true (> .62) and a false (>.63) condition. Thanks again for excellent support of an already outstanding product, IM

Hello Michel, In a word - Yes. I do see the correct status after termination of the Progress Bar. After the initial query (first 30 - 40 seconds), I can actually change linked devices and watch them update in the Admin console (progress bar continues for an additional ~ 5 minutes).

Hi Michel, I had the same thought - no Joy. I checked the "Irrigation Complete" Email and the Irrigation Requirement value had not changed. Unfortunately, this Email was generated immediately after I had issued the "cycle complete" command. The ISY had apparently not had time to update the value. I was also logging data at 1 hour intervals. The interval prior to irrigation shows the "requirement" at .2644 inches. The interval after irrigation shows 0 inches (reset by the cycle complete command). 3 AM Log (Prior to Irrigation) Date,Time,ET,Current_Temp,High_Temp,Low_Temp,Humidity,Wind_Speed_AVG,Wind_Speed,Pressure,Light,Rain_today,Dew Point, Irrigation Requirement, Water deficit 2011/07/14,03:00:25,0.1229 inches/day,62.2 °F,64 °F,62 °F,78 %,2 mph,3 mph,30.08 inches,0 %,0 inches, 55 °F, 0.2644 inches, 0.2644 inches 8 AM Log (After Irrigation - Irrigation requirement set to 0) Date,Time,ET,Current_Temp,High_Temp,Low_Temp,Humidity,Wind_Speed_AVG,Wind_Speed,Pressure,Light,Rain_today,Dew Point, Irrigation Requirement, Water deficit 2011/07/14,08:00:25,0.1691 inches/day,62.7 °F,64 °F,61 °F,59 %,5 mph,4 mph,30.09 inches,7.4 %,0 inches, 48 °F, 0 inches, 0.2644 inches I've been playing with test programs varying the "irrigation requirement" trigger. I had thought there might be a factor of 10 error somewhere. Again no joy. The following program still triggers with the irrigation requirement of .2612 as shown below. The irrigation requirement qualifier is limited to 20 inches - I can't test a factor of 100 (26.12 inches). If I'm doing something wrong, I sure can't see it. Update: I rearranged the condition to test for Irrigation Requirement < 20.00 Inches - the program does not run. Do we have a factor of 100 error here? Thanks, IM If Time is 3:36:00PM And Module 'Climate' Irrigation Requirement > 20.00 Then Send Notification to 'Yahoo' content 'Irrigation Start' Wait 30 seconds Send Notification to 'Yahoo' content 'Irrigation End' Else - No Actions - (To add one, press 'Action')

My irrigation program triggered today and logged the values to Email. Obviously, there's something I don't "get". The logged values indicate that my irrigation requirement was at 0.2644 inches while my trigger was set at >= 0.35 inches. The program ran and completed (logged the irrigation end Email) despite the trigger value. What am I missing? Do I need to copy the Irrigation requirement in order to use it as a condition? Thank you, IM Program If Time is 4:00:00AM And Module 'Climate' Irrigation Requirement >= 0.35 Then Set 'Sprinkler-Relay' On Send Notification to 'Yahoo' content 'Irrigation Start' Wait 3 hours Set 'Sprinkler-Relay' Off Irrigation - Cycle Complete Send Notification to 'Yahoo' content 'Irrigation End' Else - No Actions - (To add one, press 'Action') Values logged at program start: Date, Time, Deficit, ET0, Requirement 2011/07/14, 04:00:01, 0.2644 inches, 0.119 inches/day, 0.2644 inches

Hello Michel, Answers below - Correct - with the programs disabled, the progress bar terminates is roughly 40 seconds. Not in this test - the above program was the only one enabled. ...BTW - I wouldn't call this a "tardy reply". We users may be demanding, but we do recognize that you need to sleep at times. Thanks again, IM

Hello Michel, Absolutely - The program is extremely simple - it monitors my second floor devices and updates KPL buttons to indicate the ON/OFF status of the second floor. There are 3 KPL's in the "2nd Floor Status" scene spread throughout the house. I have a number of "status" programs that will produce the same effect, this was the simplest. Enabling this program by itself will cause a "several minute" progress bar if I query My Lighting. Curiously, if I query the Scene that contains all of my Insteon wired devices ( No 2420's or remotelincs) the progress bar responds properly and terminates after roughly 30 seconds. The scene contains all of the devices listed in the program (program is run during the query). As always, thank you for the support IM If ( Status '2nd Floor / David Switch' is Off And Status '2nd Floor / Kath Icon' is Off And Status '2nd Floor / Master Fan' is Off And Status '2nd Floor / Master KPL 1 - Master Overhea' is Off And Status '2nd Floor / Matt Inline' is Off ) Then Set Scene 'SC 2nd Floor Status' Off Else - No Actions - (To add one, press 'Action')

Hello backinthelab, My Hunter controller is actually the Grandfather of the Pro-C (it's a 10 year old SRC controller). The connections on the Pro-C are a bit different, but should still work. Have a look at page 8 of this link: http://www.hunterindustries.com/Resources/PDFs/Owners_Manuals/Domestic/lit329w.pdf. The IOlink will wire in the location for the rain sensor. I connected the NO (normally open) and common terminals of the IOLink to the sense terminals of the Hunter. Polarity doesn't matter - you're using the IOlink as a switch input to the Hunter. When connected to the NO/COM terminals, the Hunter will be enabled when the IOLink is ON (relay closed).

Hello Michel, I actually encountered this several months ago. Rebooting the ISY (or querying My Lighting) would produce activity in the event monitor for roughly 30 seconds. The progress bar, however, would continue updating for several minutes. I noted several "strange" X10 response entries for devices that could not respond in my system (1 way X10). I theorized that this was causing the large time lag in the query. To troubleshoot, I created a "query" scene of all my Insteon devices. A query on this scene would complete in 30 seconds (progress bar closes). I believed that the above proved that the X10 devices were causing the large delay in querying My Lighting - I was wrong. I've been playing with things today and have found an interaction between my status programs the the My Lighting query. If I disable the status programs, the query completes normally after ~ 30 seconds. With the programs enabled, I can see them execute during the query. This apparently confuses the ISY and the progress bar again takes several minutes to terminate. I do not remember this being the case on older revisions of the ISY firmware. My confusion at this point is why the same doesn't occur when I query my scene that includes all of my Insteon devices. The programs still execute, but the ISY seems to handle it gracefully. Sorry for the previous mis-information, IM

Hello kingwr, Somewhat unrelated topic - I also get the "System Busy" dialog for a long period of time after a re-boot or query of "my lighting". I have the X10 module installed and after looking at the "event Viewer", I've determined that most of this time is spent querying X10 devices that can't respond (one way devices). This causes a huge delay as the ISY/PLM must time out on each X10 query before proceeding to the next. The querying of my Insteon devices is actually quite quick. I'm curious whether you have the X10 module installed as well? It might be possible to eliminate this lag if the ISY team were to incorporate a flag to specify whether the X10 devices were 1 way (receive only) or 2-way (receive/transmit). In the world of X10, there are actually very few of the 2-way devices available. I'm simply not sure how many ISY users have the X10 module installed. If only a few, this would be down quite a way on the priority list.

Hello jgreco, I'm very late to the discussion, but nonetheless interested. I have implemented programs exactly as you've described below to allow KPL buttons to monitor the status of various "groups" of devices in my home (1st floor, second floor, basement, whole house). You're correct that adding/deleting devices can be a little arduous. As you can probably tell, there has been a plethora of discussion on how to implement a conditional statement for a scene. The discussions to date have (in general) become very complex trying to cover all of the possible scene combinations and events. The result is a stalemate with no outcome. Your post above lead me to think about how I actually use "status tracking" in my applications. For most of my applications, I simply don't care whether a device is at it's preprogrammed scene level of xx%. I simply want to know whether the device is on or off. So what if we were able to treat scenes as a simple collection of devices that we would apply a condition to? I'm not sure what this would entail from the ISY side. It would essentially be a macro (collection) that the ISY would track as the system changed. As an example, I use the following to monitor the lights on my first floor. The KPL status buttons (3 locations) are in a scene "1st floor status", while the monitored devices are in the scene "1st floor On". If ( Status '2nd Floor / Master KPL 5 - 1st Floor' is not On Or Status '1st Floor / Mud KPL 3 - 1st Floor' is not On Or Status '1st Floor / Fam Room / Fam KPL 5 - 1st Floor' is not On ) And ( Status '1st Floor / Bar Cans' is On Or Control '1st Floor / Bar Lamp' is switched On Or Control '1st Floor / Dinnette SWL' is switched On Or Control '1st Floor / Fam Room / Fam Fan' is switched On Or Control '1st Floor / Fam Room / Fireplace Spots' is switched On Or Control '1st Floor / Foyer' is switched On Or Control '1st Floor / Foyer KPL 1 - Bar Lamp' is switched On Or Control '1st Floor / Foyer KPL 3 - Foyer' is switched On Or Control '1st Floor / Foyer KPL 4 - Bar Cans' is switched On Or Control '1st Floor / Foyer KPL 5 - Kitchen Cans' is switched On Or Control '1st Floor / Foyer KPL 6 - Dinnette' is switched On Or Control '1st Floor / Fam Room / Fam KPL 1 - Wall' is switched On Or Control '1st Floor / Fam Room / Fam KPL 2 - Fireplace Spots' is switched On Or Status '1st Floor / Fam Room / Fam KPL 3 - Lamps' > Off Or Control '1st Floor / Fam Room / Fam KPL 4 - Fan' is switched On Or Control 'Motion/RF / RL2 Fam Wall' is switched On Or Control 'Motion/RF / RL3 Fam Fan' is switched On Or Control 'Motion/RF / RL4 Kitchen' is switched On Or Control 'Motion/RF / RL5 Dinnette' is switched On ) Then Set Scene 'SC 1st Floor Status On' On Else - No Actions - (To add one, press 'Action') Using the "group" or "collection" approach, this would simplify to: If ( Any device '1st floor status' is not on ) And ( Any device '1st floor on' is switched on ) Then Set Scene 'SC 1st Floor Status On' On Else - No Actions - (To add one, press 'Action') In the above, the "any device" would equate to an "or". The statement "all devices" could be used for an "and" (doesn't make sense with my example above). For my given example, I would need to rework things a bit since I've used both "status" and "switched" within the same program. This is doable. The advantage would be that the ISY would track and update the scene membership as the system evolved. No additional program changes would be required. Thoughts? I'm not sure what this would entail within the ISY. Nor am I sure whether users would value the function. IM

Hello Michel, I've been trying to be patient... My eyes popped open when you first posted the support for ET calculations in 3.1.3. Could you provide a little more detail? I am extremely interested and am fighting the urge to purchase an EZFlora prior to understanding the implementation. Please?, IM

Your Accesspoint should not require any "presses". It may, however, have locked up, or your RF signal path may have changed due to things in your home being "re-arranged". 1) In it's existing location - reset the AP by unplugging for ~10 seconds and then re-install (powerline spikes may have upset the AP). Re-try adding your 2420's. 2) If #1 doesn't work, try moving your AP closer to the 2420 (RF transmission my be obstructed).

Hello mmknox, Sorry to hear about the communication problems. I've been using dimmable CFL's in my outdoor lamps for some time. These are rather nasty noise makers, but I put up with them. I run two programs to control the lights in the daytime: Outside Daytime If From Sunrise + 1 minute To Sunset - 10 minutes (same day) And ( Status 'Outdoor / Entry Deck' > Off Or Status '1st Floor / Mud KPL 1 - Entry Garage' > Off Or Status 'Outdoor / Entry Patio' > Off Or Status 'Outdoor / Entry Porch' > Off ) Then Wait 2 minutes Set Scene 'SC Ouside Night' Off Else - No Actions - (To add one, press 'Action') Outside Daytime Poll If From Sunrise + 1 minute To Sunset - 10 minutes (same day) And Time is Last Run Time for 'Outside Daytime Poll' + 30 minutes Then Set Scene 'SC Outside Sunset' Query Else - No Actions - (To add one, press 'Action') During daylight hours the "poll" program will trigger every 30 minutes and run the query. If an outside light status "on" is detected, the main program will trigger to turn it off. This could likely been done more eloquently with a folder. As it is, I've been running it for years and it hasn't given me a problem.

Hello Cliff, I'm afraid we'll need help from the UDI team on this one. I'm not aware of any backup problems with the ISY 2.7.15 version. What version were you using previously? It's possible that your "old" version was not properly saving programs, or there is an incompatibility between versions. Either way, we need the UDI team to confirm.

Hello Cliff, You are correct that the programs should be saved with the back-up. There were some problems with earlier versions of the ISY firmware, but this was some time ago. I recently performed an upgrade and "appeared" to have lost my programs as well. Please use the following (standard) procedure: 1) Exit all browser windows 2) Clear your Java Cache 3) Re-start your browser/admin console. I understand that you've been using the ISY for some time and am not trying to be insulting here. Nonetheless, it's sometimes the little things that trip us up. If this doesn't work, we'll need Michel's/UDI help.

This statement may make more sense if we look at the actual programming screen: 1) In the highlighted condition above, the trigger is "ON". 2) The choice "IS" will cause the "Then" statement to execute. 3) The choice "IS not" will cause the "else" statement to execute. The "IS" and "IS not" are essentially vectors to the "Then" and Else" branches. I'll agree that it's difficult to separate these when looking at the program. However, when looking at the "condition selections" it appears clear.