apostolakisl

The only way ISY will be able to control speed is by getting a fanlinc. The only possible caveat to that is that you could train an irlinc or global cache unit to shine the ir commands to the fan from a nearby location. This assumes that the remote that came with the fan is ir based.

That program doesn't do exactly what you asked, but it might be what you meant. "(changed from Off to On) I want to wait 10 minutes and check that sensor again. If it is still on I want to send an sms notification." Taken literally, this could mean you want it to ignore any off/on cycles that happen during those 10 minutes. This won't be the case. That program will only send you an SMS if the i/o linc were continuously on for 10 minutes.

This is because outlook doesn't get emails pushed to it. Outlook runs a send/receive at whatever interval you set it to in the options. So outlook doesn't know there is an email waiting for it to receive until it runs its next check.

Afraid I am at a loss here. I have never seen a switchlinc behave as you say with the led's flashing and the load flashing. When you push the on button on a switchlinc, the led's should travel up to the "on level applied locally" setting. The load directly connected to that switch will always do the same. It won't matter what scene it is a member of or if it is in any scenes at all. In this respect, an Insteon switch behaves just the same as a non-insteon dimmer. The only possible way to alter that behavior is with a program in ISY, but still, what you describe still makes no sense. Of course none of the switches local or scene behavior requires ISY. So if you wanted to rule out any ISY affect on the switch/scene, you could just unplug it. ISY is only a tool to setup the switches or to run programmed events.

I guess ISY firmware needs an update to support the higher temps. Not sure why it doesn't already, perhaps there is a reason that isn't so simple. I am sure Michel will chime in with an answer to that. A solution would be to use a CAI webcontrol board with a waterproof 1-wire temp sensor. The CAI can be programmed to post directly to ISY variables on any schedule or condition you like. Or, you could skip the ISY and program the cai board to cycle the recirc pump on its own.

Your saying some weird stuff. Why are you pushing buttons with the tip of a screwdriver? Which buttons are you pushing with the tip of a screwdriver? What happens when you push them with your finger like normal? Aside from physically breaking a switch using an instrument instead of your finger, it shouldn't matter what you use to push a button.

120v smokes have a third wire for comm. The hot and neutral don't carry any comm. But it still is not code to use the hot/neutral for anything besides the smokes and (unlike some codes) this code is actually a really good idea.

The main 2 kpl buttons on a 6 button device are the same as pushing the on or off side of a switchlinc paddle. They are not listed as two separate buttons. Looking at your screen shot, it appears that it is already done correctly. Your "All On" scene has all three devices as responders and the two KPL's load switches as controllers. It should work. But I wouldn't name it "all on" since it doesn't only turn them all on, it also will turn them all off if you push the off side of the kpl. So, in short, it appears you had everything correct from the start. Perhaps you had some comm failures because something in the house turned on that was making noise. Edit, and by the way, the blinking kpl buttons happens when there is a comm failure.

What do you mean "I switched the paddles on the switchlincs"

I have a lot of experience with Harmony remotes and ISY, however, not the "smart control" model. Though I suspect it works the same as the other harmony remotes of which I have 2 890's and a 900. I presume the harmony base station emits IR commands on command from your phone or the included remote. The base station IR output needs to point in the general direction of the ISY input. Harmony has the 40 ISY base commands built in and it sounds like you already added those. You also need to install the 40 base commands to ISY. If you use all those up, you can add more using the learning mode for both ISY and Harmony. Then you need to write programs in ISY that respond to triggering the 40 base commands. If IR 'IR_013' is Pressed And Status 'Theater / Theater Sconces L' is not Off Then Set Scene 'Theater On' Off Else - No Actions - (To add one, press 'Action')

First off, use the search function in the programs editing section and search the name of the switch (edit: also any scenes that is a member of) to make sure it only exists in the programs you specified. Obviously if it exists in an unintended location, delete it. If all looks good, then you will have to wait until the problem occurs again. If/when it does, go back and look at your log. Also use the programs summary page to see what programs ran, when they ran, and whether they ran true or false.

You didn't mention a fanlinc, but I assume you have one. This post tells you how to set up a kpl with a fanlinc. You will see that some of the setting have kpl buttons as controllers. A KPL button that is not a controller of any scene will do nothing but light up when you push it. For a button to control anything besides its own load natively (as a pure insteon device), it must be a controller of a scene. viewtopic.php?f=26&t=10312&hilit=fanlinc+setup The concept is as follows. You have 4 scenes, one each for high, med, low, off. You dedicate 4 kpl buttons to those 4 states. Each kpl button is in each scene, one of them is a controller, the other 3 are responders. For example, the "high speed" scene might use button A. So button A is a controller of the scene and sets the fanlinc to 100%. The other 3 buttons are responders and set to 0%. the "medium speed" scene might use button B. Button B is a controller and sets the fan to whatever it needs to be for medium (like 60% I think), and the other 3 buttons are set as responders of 0%. etc. So in the above example, button A is the only controller of a scene with the fan and the other 3 buttons as repsonders. When you push A, the fan responds by going to 100%, and whichever of the other 3 buttons will shut off. Technically, you don't need the other 3 buttons to shut off, but it is a nice feature. This way it will only have the one button lit that corresponds to the current speed.

It may be the installing a new OS fixes your problem, but in that case it would indicate a corrupted xp on that computer, not that xp itself is problematic. I have 8 computers running xp and all of them run the admin console just fine.

I'm not for sure what you are describing. But if you are trying to change the local on level, not the scene responder on level, you need to pick the individual device in the "in scene" section, not a scene that the light is in. But you might abandon that approach and use this approach. If status bathroom light is off and control bathroom light is switched off Then set bathroom light to 15% This is how I do my night lights. You just hit the off paddle on a light that is already off and it goes to 15%.

I'm running XP pro on almost all of my machines and don't have any issues. So I suspect that something else is your issue.

Yes. Entering a set of parenthesis is done as a single click that enters both the start and finish. ISY always adds new content to the end, so you use "move line up" or "move line down" to get the start/finish around the right stuff. Or alternatively, you can move the conditions up or down to get them inside of the parenthesis. I agree it does seem clunky, but it works fine and since it is not something you are likely going to do that often, a little clunkyness isn't the end of the world.

By example If ( - this is a start parnethesis $iDay.of.Year < 365 And $iLeap.Year > 0 - this and statment menas both statements must be true for the entire parenthesis group to be true ) - this is the end, so everything between these gets evaluated together as true/false Or ( - this or statement means the true/false result of above group is "or'd" against the next item or group $iDay.of.Year < 366 And $iLeap.Year is 0 - this and statement means both statements must be true for the entire parenthesis section to be true ) Then $iDay.of.Year += 1 $iDay.of.Year Init To $iDay.of.Year $sDay.of.Year Init To $iDay.of.Year $sDay.of.Year = $iDay.of.Year Run Program 'Every x Day Counter' (Then Path) Run Program 'Year' (If) Else $iDay.of.Year = 1 $iDay.of.Year Init To 1 $sDay.of.Year = $iDay.of.Year $sDay.of.Year Init To $iDay.of.Year Run Program 'Every x Day Counter' (Then Path) Run Program 'Year' (If) Another much more complex example. Here we have nested parenthesis sections. You need to keep track of how far indented the parenthesis are as this controls what is nested inside of what. If ( $iDay.of.Month < 31 And ( $iMonth is 1 Or $iMonth is 3 Or $iMonth is 5 Or $iMonth is 7 Or $iMonth is 8 Or $iMonth is 10 Or $iMonth is 12 ) ) Or ( $iDay.of.Month < 30 And ( $iMonth is 4 Or $iMonth is 6 Or $iMonth is 9 Or $iMonth is 11 ) ) Or ( $iDay.of.Month < 29 And $iMonth is 2 And $iLeap.Year is 0 ) Or ( $iDay.of.Month < 28 And $iMonth is 2 And $iLeap.Year > 0 ) Then $iDay.of.Month += 1 $iDay.of.Month Init To $iDay.of.Month $sDay.of.Month Init To $iDay.of.Month $sDay.of.Month = $iDay.of.Month Run Program 'Day of Week' (If) Run Program 'Month Advance' (If) Run Program 'Month Reset' (If) Run Program 'Week of Month' (Then Path) Run Program 'Ever X Weeks' (Then Path) Run Program 'Odd Even Day' (Then Path) Run Program 'Holiday reset' (Then Path) Else $iDay.of.Month = 1 $iDay.of.Month Init To 1 $sDay.of.Month Init To $iDay.of.Month $sDay.of.Month = $iDay.of.Month Run Program 'Day of Week' (If) Run Program 'Month Advance' (If) Run Program 'Month Reset' (If) Run Program 'Week of Month' (Then Path) Run Program 'Ever X Weeks' (Then Path) Run Program 'Odd Even Day' (Then Path) Run Program 'Holiday reset' (Then Path)

For a fool proof way to push something off for 24 hours, use the ISY day of week function. Set a variable on boot or at midnight to set a variable to the current day of week (1 for Mon, 2 for Tues, etc). If On Mon Time is 12:00:01AM Then $iDay.of.Week = 1 Else - No Actions - (To add one, press 'Action') etc for each day of week Then your program that pushes something off to the next day has a new variable that says add 1 to the current value (and roll over an 8 to a 1). If whatever you want to trigger the 24 hour delay Then $sTomorrow = $iDay.of.Week $sTomorrow += 1 (or 2, 3 ,4, 5, 6 if you want to push something off more than 1 day into the future) $sTomorrow Init to $sTomorrow Else - No Actions - (To add one, press 'Action') If $sTomorrow > 7 Then $sTomorrow -= 7 $sTomorrow init to $sTomorrow Else - No Actions - (To add one, press 'Action') Then you use that variable as being equal to the current day of week variable in your "if" clause of whatever it is that is going to happen the next day. If $iDay.of.Week is $sTomorrow and Time is ? Then do whatever Else - No Actions - (To add one, press 'Action') You could use the same program to push something off 2 days or more up to a max of 6 days.

This program '15 minute timer' get the ball rolling. At 8pm it will start trying to arm after 15 minute wait If Time is 8:00:00PM Then Enable program 'motion detector' Wait 15 minutes Set Elk Area 'Main House' Arm Night Else - No Actions - (To add one, press 'Action') This program 'motion detector' will look for the motion detector to activate. If it does, it will start the 15 minutes over again. If Control 'motion detector' is switched On Then Run Program '15 minute timer' (Then Path) Else - No Actions - (To add one, press 'Action') This program will cause the auto arm program to stop, in my example by disarming your system. You could have something else do it. If Elk Area 'Main House' 'Armed State' is Disarmed Then Stop program '15 minute timer' Disable program 'motion detector' Else - No Actions - (To add one, press 'Action')

This is what I use to warn my kids that their bedroom light is about to turn off. Their bedroom lights shut off after 30 minutes if left alone. During the last minute, the switch beeps to warn them once per second. If they take any action on the light switch it aborts and starts over again. If Control 'Lauren Bedroom / Lauren BR-Overhead L' is switched On Or Control 'Lauren Bedroom / Lauren BR-Overhead L' is switched Fast On Or Control 'Lauren Bedroom / Lauren BR-Overhead L' is switched Fade Up Or Status 'Lauren Bedroom / Lauren BR-Overhead L' is not Off Then Wait 29 minutes Repeat 60 times Set 'Lauren Bedroom / Lauren BR-Overhead L' 130 (Beep Duration) Wait 1 second Repeat 1 times Set 'Lauren Bedroom / Lauren BR-Overhead L' Off Else - No Actions - (To add one, press 'Action')

Back to your original post. I never have any troubles with SH when it comes to returning stuff that is broken and inside of warranty. They really have never given me a hard time. Except, if I didn't buy it directly from them. So I only buy direct from them. Plus when they do the 20% sales with free shipping they are cheapest available anyway. In the past few years there stuff doesn't seem to be breaking though.

What do you mean unfortunately not? Does not the zwave radio give ISY control and integration of zwave devices? EDIT: Wait, I think you meant only UBE.

With zwave and possibly ube on the horizon for ISY users, I think things should be just fine. If you want to move away from Insteon, because of the capabilities of ISY, transitioning to one of these other 2 technologies should not be painful and will be something that can be done gradually.

You need something to turn it on and off. Unless you want to just go to the UD console and click "run then" to start it and "stop" to stop it. But I assume you would rather have a switch, or a kpl, or something in the room to start and end the program. You don't put the appliance line in the "if" section. The appliance linc has no on/off switch. That is how they work, you use other things to control them.

If control switched on (Whatever switch you want to control this) and control not switched off Then repeat every 15 minutes Set appliance linc on wait 15 minutes set appliance linc off Else - - -