Illusion

Here is a really simplified version of one that would function all the time, not just for pre-heat Aux Heat Temp Monitor: If Module 'Climate' Temperature > 38 °F Then Set 'Garage / Aux Heat Enable-Relay' Off Else Set 'Garage / Aux Heat Enable-Relay' On And here is a really simplified pre-heat type program. I just made this up real quick to give you some ideas, mine are much more complicated: Pre-Heat Cabin: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Aux Heat Temp Monitor' Set 'Garage / Aux Heat Enable-Relay' Off Set 'T-Stat' 75° (Heat Setpoint) Wait 6 hours Run Program 'Pre-Heat Cabin' (Else Path) Else Enable Program 'Aux Heat Temp Monitor' Now the problem with the really simplified Aux Heat Temp Monitor is that every time the ISY polls the weatherbug info, it is going to run the then or the else, so we will be sending tons of commands to that IOLinc. No good, so I actually do this with 4 programs as follows. These are actually copies of some of my programs so there are references to the parent folder which gets enabled or not based on other stuff. Aux Heat Disable: If Folder 'Auto Aux Heat Inhibit' is True And Module 'Climate' Temperature >= 32 °F Then Run Program 'Aux Heat Disable Action' (If) Else - No Actions - (To add one, press 'Action') Aux Heat Disable Action: If Status 'Garage / Aux Heat Enable-Relay' is not Off Then Set 'Garage / Aux Heat Enable-Relay' Off Else - No Actions - (To add one, press 'Action') Aux Heat Enable: If Folder 'Auto Aux Heat Inhibit' is True And Module 'Climate' Temperature <= 29 °F Then Run Program 'Aux Heat Enable Action' (If) Else - No Actions - (To add one, press 'Action') Aux Heat Enable Action: If Status 'Garage / Aux Heat Enable-Relay' is not On Then Set 'Garage / Aux Heat Enable-Relay' On Else - No Actions - (To add one, press 'Action') The parent folder I have all these in gets disabled by my pre-heat program so none of them run while in pre-heat regardless of how cold it is outside. No aux heat in pre-heat ever in my system. I hope this helps you.

It is cheap cable. Buy it. First, it will be rated to be installed in walls. (jacketed) Second, it will be solid core, making the connection to the equipment and IOLinc easy. Third, if this is also an AC unit: Get 4 conductor wire instead of 2 (18ga). Run the other two wires to the input of the same IOLinc. At the unit, connected those wires to a readily availble, inexpensive, and easy to install HVAC pan float switch. Should the pan ever back up with water, you get an email after setting up said program in the ISY. Yes, between common and NC. I would love to post my pre-heat program, but I am not the right guy to ask that of. Climate control is one of the most advanced and complicated things my ISY controls. I have over 250 interrelated programs for my indoor climate control. I did go to my programs to see what I could easily translate here for you, but alas, all my programs like pre-heat are just a series of calls to other programs at the proper moment when the if is met. Most of those programs called also call other programs. I have no easy way to put it here without posting dozens of programs, maybe even a hundred. Sorry.

Exactly. And do not get hung up on just breaking the line. I put my IOLinc in a convenient spot, then ran two conductor wire to the air handler. Then inside the air handler I just pull the aux heat wire off the terminal, connecting it to one of the two conductors. The other conductor is then attached to the terminal on the unit. It makes a nice long switch loop so you can put the IOLinc wherever it is easy to run the wire and have an outlet.

The ultimate solution, which is what I have done. In a conventional 24V Heat Pump, the aux/emergency heat is called by the t-stat. I just put an IOLinc in that line, breaking the t-stat's direct connection to the HVAC System. The IOLinc is normally closed, allowing the t-stat to call heat strips when it wants to. Then when I run the 'Pre-Heat' program from within the ISY, the ISY opens this IOLinc and sets the t-stats to my target temp. The T-Stat of course calls for both mechanical and resistance heat, but the resistance heat call never makes is to the equipment. This method has the added advantage of instituting an outdoor temperature limit for the resistance heat. Through an ISY program, this IOLinc is opened any time the outdoor temp is above X (per weatherbug data). This way, even when I manually raise the temperature, I only use mechanical heat if there is enough energy in the air outside that it makes sense to just wait a bit longer for the room to warm up and save all that electricity.

I dim all my keypads each night, and brighten them the next day. Max Bright: For a KPL V.39: On 15 / Off 7 (Backlight Level) For a Dual Band KPL v.40: 100% (Backlight Level) For a Switchlinc Dimmer v.38: 0% (Backlight Level) For a Switchlinc Dimmer v.40: 0% (Backlight Level) For a Switchlinc Relay v.3A: 0% (Backlight Level) For a Dual Bank Switchlinc v.40: 100% (Backlight Level) And to make them as dim as possible: For a KPL V.39: On 0 / Off 0 (Backlight Level) For a Dual Band KPL v.40: 0% (Backlight Level) For a Switchlinc Dimmer v.38: 1% (Backlight Level) For a Switchlinc Dimmer v.40: 1% (Backlight Level) For a Switchlinc Relay v.3A: 1% (Backlight Level) For a Dual Bank Switchlinc v.40: 0% (Backlight Level) Programs: Switch Backlights Day (Enabled): If From Sunrise - 29 minutes To Sunset + 29 minutes (same day) And Program 'Away Flag' is False And Program 'Keypads are Dim' is True Then Run Program 'Backlight level Bright' (Then Path) Else - No Actions - (To add one, press 'Action') Switch Backlights Night Bright (Enabled): If From Sunset + 30 minutes To Sunrise - 30 minutes (next day) And Program 'Away Flag' is False And Program 'Keypads are Dim' is True And ( Status 'Bathroom / Bathroom Shower Light' is not Off Or Status 'Bathroom / Bathroom Track Lights' is not Off Or Status 'Bathroom / Bathroom Vanity' is not Off Or Status 'Livingroom / Livingroom Lamp' is not Off Or Status 'Office / Office Desk Lamp' is not Off Or Status 'Office / Office Hutch Lights' is not Off Or Status 'Office / Office Light' is not Off Or Status 'Livingroom / Livingroom Mantle' is not Off Or Status 'Livingroom / Livingroom Overheads' is not Off Or Status 'Livingroom / Fireplace' is not Off Or Status 'Livingroom / Ent Center Lights' is not Off Or Status 'Kitchen / Kitchen LEDs' is not Off Or Status 'Kitchen / Back Porch KPL' is 30% Or Status 'Kitchen / Kitchen Fan-Light' is not Off ) Then $SWITCH_BACKLIGHTS_BRIGHT = 1 Else $SWITCH_BACKLIGHTS_BRIGHT = 0 Swithc Backlights Night Dim (Enabled): If From Sunset + 30 minutes To Sunrise - 30 minutes (next day) And Program 'Away Flag' is False And Program 'Keypads are Dim' is False And Status 'Bathroom / Bathroom Shower Light' is Off And Status 'Bathroom / Bathroom Track Lights' is Off And Status 'Bathroom / Bathroom Vanity' is Off And Status 'Livingroom / Livingroom Lamp' is Off And Status 'Office / Office Desk Lamp' is Off And Status 'Office / Office Hutch Lights' is Off And Status 'Office / Office Light' is Off And Status 'Livingroom / Ent Center Lights' is Off And Status 'Livingroom / Fireplace' is Off And Status 'Livingroom / Livingroom Mantle' is Off And Status 'Livingroom / Livingroom Overheads' is Off And Status 'Kitchen / Kitchen LEDs' is Off And Status 'Kitchen / Back Porch KPL' is not 30% And Status 'Kitchen / Kitchen Fan-Light' is Off Then $SWITCH_BACKLIGHTS_DIM = 1 Else $SWITCH_BACKLIGHTS_DIM = 0 Wait Night Bright (Enabled): If $SWITCH_BACKLIGHTS_BRIGHT is 1 Then Wait 10 minutes Run Program 'Backlight level Bright' (Then Path) Else - No Actions - (To add one, press 'Action') Wait Night Dim (Enabled): If $SWITCH_BACKLIGHTS_DIM is 1 Then Wait 10 minutes Run Program 'Backlight level Dim' (Then Path) Else - No Actions - (To add one, press 'Action') Keypads are Dim (not enabled): If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Backlight Level Bright (not enabled): If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Bedroom / Wake 3AM' On 15 / Off 7 (Backlight Level) Set 'Entry / Front Porch' 100% (Backlight Level) Set 'Livingroom / HVAC KPL' On 15 / Off 7 (Backlight Level) Set 'Livingroom / Livingroom KPL - On' On 15 / Off 7 (Backlight Level) Set 'Livingroom / Livingroom Mantle' 0% (Backlight Level) Set 'Livingroom / Livingroom Overheads' 0% (Backlight Level) Set 'Bathroom / Bathroom Shower Fan' 0% (Backlight Level) Set 'Kitchen / Back Porch KPL' On 15 / Off 7 (Backlight Level) Set 'Bathroom / Bathroom Vanity' 90% (Backlight Level) Set 'Bathroom / Bathroom Track Lights' 0% (Backlight Level) Set 'Bathroom / Bathroom KPL' On 15 / Off 7 (Backlight Level) Set 'Bathroom / Bathroom Shower Light' 90% (Backlight Level) Set 'Bathroom / Bathroom Fan' 0% (Backlight Level) Set 'Livingroom / Livingroom Fan KPL' On 15 / Off 7 (Backlight Level) Set 'Kitchen / Kitchen Fan KPL - Light' On 15 / Off 7 (Backlight Level) Run Program 'Keypads are Dim' (Else Path) Else - No Actions - (To add one, press 'Action') Backlight level Dim (not enabled): If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Bedroom / Wake 3AM' On 0 / Off 0 (Backlight Level) Set 'Entry / Front Porch' 0% (Backlight Level) Set 'Kitchen / Back Porch KPL' On 0 / Off 0 (Backlight Level) Set 'Livingroom / HVAC KPL' On 0 / Off 0 (Backlight Level) Set 'Livingroom / Livingroom KPL - On' On 0 / Off 0 (Backlight Level) Set 'Livingroom / Livingroom Mantle' 1% (Backlight Level) Set 'Livingroom / Livingroom Overheads' 1% (Backlight Level) Set 'Bathroom / Bathroom Shower Fan' 1% (Backlight Level) Set 'Bathroom / Bathroom Track Lights' 1% (Backlight Level) Set 'Bathroom / Bathroom Vanity' 0% (Backlight Level) Set 'Bathroom / Bathroom KPL' On 0 / Off 0 (Backlight Level) Set 'Bathroom / Bathroom Fan' 1% (Backlight Level) Set 'Bathroom / Bathroom Shower Light' 0% (Backlight Level) Set 'Livingroom / Livingroom Fan KPL' On 0 / Off 0 (Backlight Level) Set 'Kitchen / Kitchen Fan KPL - Light' On 0 / Off 0 (Backlight Level) Set Scene 'Scenes / Whole House / Keypad Dim Cleanup' Off Run Program 'Keypads are Dim' (Then Path) Wait 2 seconds Set Scene 'Scenes / Whole House / Keypad Dim Cleanup' Off Wait 30 seconds Set Scene 'Scenes / Whole House / Keypad Dim Cleanup' Off Else - No Actions - (To add one, press 'Action') What this series of programs does essentially is 10m after I have all the lights off like I would if I were going to sleep, it dims all the backlights if I am home. The scene 'Keypad Dim Cleanup' is a scene with all the KPL buttons in it so any that were left on get turned off so the keypads go completely dark. Well, almost all the KPL buttons, I left my nightlight button in the bathroom out of the scene so it stays illuminated so I can find it in the dark.

The power supply is rock solid. I had not considered excess voltage bleed off as heat by the ISY. I had assumed it would just use less amperage to function. If excess voltage is converted to heat to provide 5V internally in the ISY 5V would be the smart choice here.

If I have an external power supply, and I can choose my voltage, is their any compelling reason to choose one voltage over another? I have an adapter that can do 5, 6, 7.5, 9, and 12V. In my world, higher voltage is generally better due to reduced amperage need. Is that the case here. 12V seems like a nice mid-ground from the 5-30V rating of the ISY; whereas, the 5V selection is right at the minimum of the range, so it would seem to me that if there were any issues with the adapter... being a little further away from the minimum would be good. Thoughts?

Actually LeeG, I think I am still a little lost. If the IOLinc did not have an exception, and acted like all other devices, when turning the scene on, shouldn't it be correct. If I turn the scene on, the relay turns off, but again the ISY shows status of the node as on, when in fact it is off. This is with the fader for the relay node as off. Any other module that has its fader as off shows as off if I turn the scene on.

No. Latching. I guess this is becoming a feature request then. I will repost in feature requests unless I see a response from one of the UD guys here in the next day or so. As always, thanks for the speedy reply, LeeG. Sent from my iPhone using Tapatalk

I have an IOLinc relay's node in a few scenes. In one of these scenes I have the fader for for the relay at zero, so the operation of the relay is opposite that of the scene action. I am happy with the function but not the ISY's awareness of the IOLinc relay node. If I turn the scene off, the relay turns on, but the ISY lists the Relay as off unless I query the node. As the ISY knows that the fader is at zero in the scene, shouldn't it update status correctly? If I turn the scene on, the relay turns off, but again the ISY shows status of the node as on, when in fact it is off. If I have a lamp module at zero in a scene, and I turn the scene on, the ISY shows status of that module as off. Why should the operation of an IOLinc be any different? Am I missing something?

I have solved this issue. I built another scene, moved all the nodes to the new scene, and deleted the old scene. I suppose I should have left the problem scene in the ISY with no responders so the issue does not come up again when I create a new scene and the ISY re-uses that group ID #. Ah well, next time it comes up I will do that. Much easier to have abandoned scene in a holding pen than to reprogram the IR TX module!

No, not scene. In my experience, the only time a person has not had the Replace with option available in the contextual menu is when the device is in a sub folder. After right clicking on the device it should be right there under restore if the device is in the root folder of 'My Lighting' and there is a device in the ISY with which to replace it.

First remove the device from any folder it may be in.

Ouch. Not good news, but thank you for the explanation. Sent from my iPhone using Tapatalk

Could you elaborate on that a little. Was this supposed to happen? Is this fixable? How do I stop the device from responding to scenes it is not a member of? Sent from my iPhone using Tapatalk

Device added under 3.1.5. Modified nodes and scene memberships a bit under 3.1.10 No -11000X errors to report.

If I delete the 'Livingroom Fan High' scene, should it also delete the offending link, since the ISY know it is there, even though it does not show in the UI. There should be only one group 91 right. So deleting that scene should delete all the 5b link records that the ISY knows aobut? This has gotten largely academic for me. I am not going to delete the device and re-add it back. As this should never have happened in the first place, as I never had that module as a responder to said scene, what is to say it would not happen again. It would be easier for me to modifiy my behavior than redo that module. This does get me thinking. Group 91 seems kinda like a low number for how new the scene is and how many scenes I have. Is is possible that this was a scene of mine long ago, before I streamlined the IR TX scenes, that did include the IR TX. Hypothetically, I have a scene. It gets assigned group #91. It has only the IR TX iPod Play/Pause node in it as a responder. I delete the scene during clean-up cause I find it is a duplicate or whatever. If the link record does not get deleted, at some point in the future group #91 would get reused by the PLM/ISY and the IR TX would respond, right? But in my case, the ISY knows about the links that should not exist...

Here are the link records that have a 5b but not all have the PLM address. 0F28 : A2 5B 13.24.AA 00 00 0D 0E90 : A2 5B 13.24.AA 00 00 22 0E88 : A2 5B 13.24.AA 00 00 01 0E70 : A2 5B 13.24.AA 00 00 0A 0E58 : A2 5B 13.24.AA 00 00 0F 0E40 : A2 5B 13.00.AA 00 00 05 0E28 : A2 5B 13.24.AA 00 00 13 0E10 : A2 5B 13.24.AA 00 00 0E 0DF8 : A2 5B 13.24.AA 00 00 03 0DE0 : A2 5B 13.24.AA 00 00 24 0DC8 : A2 5B 13.24.AA 00 00 08 0DB0 : A2 5B 13.24.AA 00 00 07 0D98 : A2 5B 13.24.AA 00 00 21 0D80 : A2 5B 13.24.AA 00 00 1F 0D68 : A2 5B 13.24.AA 00 00 1D 0D50 : A2 5B 13.24.AA 00 00 14 0D38 : A2 5B 13.24.AA 00 00 15 0D20 : A2 5B 13.24.AA 00 00 16 0D08 : A2 5B 13.24.AA 00 00 17 0CF0 : A2 5B 13.24.AA 00 00 18 0CD8 : A2 5B 13.24.AA 00 00 1A 0CC0 : A2 5B 13.24.AA 00 00 1B 0CA8 : A2 5B 13.24.AA 00 00 1C 0C90 : A2 5B 13.24.AA 00 00 12 0C78 : A2 5B 13.24.AA 00 00 23 I did the compare and came up with two record mismatches: [Record mismatch]0E40 : A2 5B 13.00.AA 00 00 05 Device link table 0E40 : A2 5B 13.24.AA 00 00 05 ISY link table [Record mismatch]0CF8 : A2 11 00.F5.69 00 00 17 Device Link Table 0CF8 : A2 11 12.F5.69 00 00 17 ISY link table

Okay did the rest thing. Came up with this: 33176 Livingroom Fan High 49280 91 16 7C 18 6 12 F5 69 11 14 9D 29 2 F C1 DE 3 So I am looking for the number 91 (5b?) in the second byte of a link record. In this example what value is the second byte? 06? 0CD0 : A2 06 16.7C.18 00 00 1A

I have a 2411T IRLinc Trasmitter. It has 24 nodes. One of those nodes is the IR code for play/pause on my iPod. I put some fanlincs in, and created some scenes for these. One of these scenes is called Livingroom Fan High. This scene has 4 members IR RX-Liv Fan H (a 2411R IRLinc Reciever) as a controller a secondary KPL button as a responder another secondary KPL button as a controller from a different KPL Living room Fan-motor (of course) This scene works fine when controlled from either of the member controllers; however, when I trigger it from the ISY it causes my IR Tranmitter 2411T to send the code to play/pause my iPod. It should have nothing whatsoever to do with this scene. So I figured errant half link or something. So I tried adding the iPod Play/Pause node of the IR TX to the scene, then delete it, but it persists. But only when triggered from the ISY. So I tried adding every node of the IR TX to the scene, then deleting it. Same thing the ISY initiation of the scene cause the Play/Pause node of the IR TX to fire. Thoughts?

A cool idea, using disable. But my requirements are that should the conditions become false during the wait, the action does not execute.

So, just out of curiosity, as the state variable idea is working great, how would we have done this before variables?

Thanks for the quick reply!! Works great. An interesting distinction between variables and using programs as flags. It had not occurred to me that setting up a variable as a 1 or 0 would be any different that the true-false condition of a program, but here we are. And indeed you solution works perfectly.

I think I am having a brain failure. I should know this but I am stumped. I have a really complex program that is re-entering execution during a wait and I want to fix this today, but I cannot figure out what to do. So I made a small program that is simple and explanatory of my issue: If Status 'Kitchen / Kitchen Fan-Light' is On Or Status 'Kitchen / Kitchen LEDs' is On Or Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is On Then Wait 10 seconds Set 'Office / Office Desk Lamp' On Else - No Actions - (To add one, press 'Action') For this example I want the desk lamp to come on 10s after any of the other units in the if come on. The problem here is that as long as I am changing some of the units in the condition I can keep the desk lamp from coming on. Even though the program is always true as I leave one of the conditions units on, the new status of another device in the if causes a re-entry into the wait and the desk lamp does not come on. So I logically split this into two programs: If Status 'Kitchen / Kitchen Fan-Light' is On Or Status 'Kitchen / Kitchen LEDs' is On Or Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') If Program 'Test Program' is True Then Wait 10 seconds Set 'Office / Office Desk Lamp' On Else - No Actions - (To add one, press 'Action') But this suffers the same issue. Even though the test program is true, and an event causes an evaluation of the status that results in 'true' so the program status does not change, the second program re-evaluates and I can keep the desk lamp from coming on as long as I change conditions in the test program before it gets through its wait, but always being true. How do I set this up so the desk lamp comes on 10s after any of the other units come on, but not if all of the units are off before the wait expires? In the real program, the issue is that I have lots of conditions. I want something to happen, but only after 10m of 'True'. I do not care how the conditions change, as long as it has been 'True' for 10m. If at anytime in the 10m wait there is a condition of 'False' I do not want execution.

As always, thanks LeeG. A very thorough and informative answer.