apostolakisl

I had the same problem when I was adding a new 2477D last week. I power cycled ISY and then it worked. But it sounds like my experience was not unique, so perhaps there is an underlying bug?

It sounds like ievery.other.day.counter is working correctly since it sounds like it is only irrigating every other day. You might just check to be certain that indeed the variable is alternating 0/1 at midnight every day. Check your program summary page for any programs that run or are running at 3:00 and 3:15. This should narrow done the potential culprit.

Here is a solution. This is all predicated on whether you can fit an inline linc into the fixture's box. The one that has no neutral at the switch has a "switch loop" of wire going to the wall's switch box. Hot/Neutral and Load (obviously) must all be at the fixture's box. At the fixture: 1) Install an inline linc picking up the hot/neutral/load 2) Splice hot to one of the 2 wires going to the switch 3) Splice neutral to the other wire At the switch 1) Use white or black tape as needed to indicate the hot/neutral status of the two wires as per how you hooked them up at the fixture 2) Install a switch linc using only the hot and neutral, cap the load wire 3) Linc the switchlinc to the in-line linc with the switchlinc as a controller In ISY 1) Create a scene which includes all of the devices in the basement as responders only 2) Write a program that turns that scene off whenever the "exit" switch is control switched off

So it sounds like you have 3 switches that each independently control their own set of light fixtures and each is the only switch controlling their respective fixtures. I was hoping that the one without a neutral was part of a 3-way circuit where you could re-purpose one of the conductors. It also sounds like you want to turn the 3 separate switches controlling 3 separate sets of light fixtures into a 4-way situation where you have 3 switches which simultaneously are controlling all of the light fixtures. If indeed this is the case, you may have a simple task of rewiring, if you have attic above the lights. It may be a simple matter of jumping your load wire from one fixture to the fixture whose switch has no neutral (you should also jumper the neutral since they aren't on the same circuit). If both of these fixtures are in a ceiling with attic over the top, then running that wire is going to be a quick and easy job. After picking the load and the loads neutral up from one of the other switches, the 2 wires going to the switch without the neutral can be re-purposed to hot/neutral. You won't need a load wire to the switch anymore since that will be coming from the other fixture.

If you could be more specific on what wires you do have at each location, it may be possible to do this. It sounds like all 3 locations are not wired up to control the fixture as a 4 way in the conventional sense. Are 2 or them together as a 3 way? What is the the last location controlling at present if not this fixture? Which ones have the neutral? What does the location that does not have a neutral actually have?

I have several harmony remotes all of which are controllers for ISY. First off, you need the ISY with IR. If you don't have that one, I would look into seeing if you can trade up. Other options exist, but this is the best. Logitech already has ISY in its Harmony database. Add the ISY to your Harmony along with the 40 pre-configured IR codes that Logitech knows for ISY. You will need to have your Harmony in line of sight with the ISY, or if you have the Harmony with the extenders, then you can use the extender to control ISY. Then it is a simple matter of adding ISY IR commands to your activities on the Harmony, and programming the ISY to respond to those IR commands by setting your scenes. The other option is to get the Insteon IR receivers. I tried one of those a while ago and it didn't work for a damn, so I returned it. I have my Harmony setup to control my alarm Elk alarm system as well as lots of lights that I might want. Like I can shut off the kitchen lights when the kids leave them on, or turn the front door lights on when someone rings the bell.

The key point is basically that the on/off switchlinc is a dry contact relay. Many types of loads can be damaged by triac dimmers, like florescent, motors, and other electronics. What Xathros says is true, except for the part about cheaper. The on/off relay costs the same as the dimmer ($49.99). I'm not sure what he is referring to, maybe the non-dual band, but I'm not sure they make those anymore.

Agreed. I have mine set to 120 which results in about a 90% hot to cold mix. Also is less risky for the kids. I have seen some of the tankless units allow recirc pumps and still warranty the device, but only if you added a holding tank. Kind of defeats the purpose though.

I have to wonder about your tankless heaters if they will shut off during a shower. Ours turns on for even small amounts of water, washing your hands for example even with the flow rate on low. I might suggest taking a drill and opening up the flow restrictor on your shower heads. It probably would be cheaper than running the recirc pump and make for much nicer shower experience. Also, recirc pumps void the warranty on many if not most tankless hot water heaters. Once the hot water makes the full loop a couple tmes the returning water barely needs to be heated which results in lots of cycling of the burners.

First off, you need to add the "run program line" to keep this program looping until the clock runs out IF $pump_run_time > 0 THEN turn pump outlet on decrement $pump_run_time wait 1 min Run Program (this one) if clause ELSE turn pump outlet off But I am confused as to why you want the pump to run for 30 minutes or 60 minutes after it is triggered by someone pushing the button. Isn't the point of an on demand pump to run just long enough to get water to the faucet and then shut off? I would think it should take only a few seconds depending on pump size and distance. Either that or you run the pump continuously during the times when it might be used. Like at your typical wake up time and your go to bed time. That way there is no need to do anything to trigger the pump, the hot water will be there during those times regardless of use. Or maybe some combo of both.

If the washer has an indicator light that is on during the wash, or that turns on at the completion of the wash, you can put a photocell over the light to indicate when the wash is done. Someone described that on cocoontech as well.

As Lee said, yes. Enable/Disable only changes the programs ability to self trigger an evaluation of the 'if' clause. And I see where the right click/status is, it is just bringing up that summary screen I was referring to, but it does also highlight the program you were on.

I'm not sure what you mean by "I monitor the program with the 'status' option". In ISY, on the program summary page, you can see the "activity" of a program as running or idle, status tells you if it last ran true or false. There is no reason that your program would be in a loop, at least not from what you've shown here. Unless you have some other program that you are not showing that keeps causing the one shown to keep running. And a violation of a zone is a trigger for a program containing that zone's status in the "if" section. I don't know that ISY checks Elk or if Elk pushes updates to ISY. My guess is it is the latter since there is no appreciable delay between something on Elk happening and ISY responding, at least in my house. Is the second program disabled? I see you calling it from the first program, which would not make a lot of sense since the first program would run while you are still in the driveway pushing the homelink button. I am also pretty sure you don't want the Elk to say "welcome home" every single time you open that door. If I am guessing what you want, when you arrive home and hit your homelink button, you want the alarm to say welcome when you open the door for the first time after disarming the system. Then after that you don't want the message. So what you need to do is. Elk: Kitchen Entry - Welcome If Elk Zone 'Kitchen Entry' is Violated Then Set Elk Speak Word 'Welcome' Set Elk Speak Word 'Home' *****Disable Program 'Elk: Kithcbe Entry - Welcome'***** Else ***** What is this else clause for? ***** Wait 5 minutes Run Program 'Elk: Kitchen Entry - Welcome' (If) If Status 'X10 Bridge - 0 / 1E.7B.6B.1' is 100% Then Set Scene 'Garage Door Operations (R)' On Set Scene 'Arrive Home' 100% Set 'X10 Bridge - 0 / 1E.7B.6B.1' Off Set Elk Area 'Area1' Disarm *****Enable Program 'Elk: Kitchen Entry - Welcome' ****** Else - No Actions - (To add one, press 'Action')

I agree. I started to do it once a while back and couldn't get it figured out.

You definitely misunderstood its fully supported and not a linux thing. I'm doing it with my Raspberry Pi now for my Hue integration. You can see status changes, variable changes, etc. With the 4.x alpha you can get control events as well. What I meant by Linux, is that it is an OS thing. For example, the Elk can't subscribe, you must have the Elk module. Webcontrol can't enroll, and there is no module.

Well, we'll see what Michel says. I may be wrong. Perhaps you can run something like a java console that gets updates as things change. Working with Michel and Wayne on getting the webcontrol unit linked, this was not possible, but with linux, you might have more options.

You can't do that. Only UD can do that by writing it into the firmware. What you can do is write programs that use the network module to send one of the various types of IP commands (like GET,POST,etc). But they have fixed content, so you would need an individual program for each value of each variable you wanted to send. The best way to do this might be to get your raspberry pi to query the ISY using the REST interface to get the values. Of course this relies on the rasberry pi knowing when it needs to ask. It might be that you do some combination of the above two. ISY could send a single command to rasberry pi informing it that it needs to ask for the variable values. One big program with all the variables listed in the "if" section where they are state variables, so anytime one changes, it sends a message to rasberry pi which then queries ISY?

I have it tell me to service the septic tank every 6 weeks, it turns the light alarms for the kids bedrooms off on holidays, it triggers my sprinklers, it reminds me of my every other week recycling, it does special stuff on birthdays, it starts my holiday programs the day after thanksgiving and ends them 12 days after Christmas, and so the list goes on.

Thank you, I spent an hour or so this morning setting up the variables and changing the programs to use the proper variables because I have a few in use already and that messed up the number system. I noted on your screen capture that it thinks that iEvery.third.week and iEvery.fourth.week are true currently. At midnight will get a notification email of what I thinks the date is if it's off or not. Alan The number next to the "Every x whatevers" is not a 1/0 as in true/false. They count through the weeks, 0,1,2,3,0,1, etc. For example, every 4th week cycle and every third are below 0,1,2,3,0,1,2,3,0,1,2,3,0,1,2 0,1,2,0,1,2,0,1,2,0,1,2,0,1,2 So, you can see, every so often, the numbers line up. The way to use the variable is to first look at what today is in the schedule. So today both every 3rd week and every 4th are both zero. Say, you want to send an alert every 4 weeks, and you want it to start in 2 weeks. So 2 weeks from now, the variable will be "2". Then after another 4 weeks it will be "2" again. You write your program as such If $i.every.fourth.week is 2 Then do whatever. If you look at the equation it will make sense. For example, the every 4 weeks program, is dividing the total number of weeks since the counter started (I set mine to start Jan 1, 1900) by 4, then it sets the variable as the remainder of that division. All of this is based off of the number of days since Jan 1, 1900 (at least as I set the variable). If you look at my screen shot, you'll see it has bee 41,335 days since then. That keeps an uniterupted running tally of days, which when divided by 7 gives you the same thing for weeks. What you set that number at is not relevant to anything except that this is how MS Excel does it. And I used excel to test my programs.

Here is a screen shot from my computer this morning. You can just copy all the values as they are on m screen skipping the ones that have nothing to do with this program (13-33, 42, 43)

You have to set the variables to start with. It's like a clock, you need to tell it the date to start with, after that it keeps going on its own. Go to the integer variables page and manually enter the 1) month (3) 2) day (2) 3) year (2013) 4) leap year (1) 5) day of week (6) 6) day of year (61) that is 31+28+2 Also, I would try to test such things with a time that is further in the future than two minutes. Java is running the clock you see on your computer screen. When you start the admin console, it loads the time from ISY, then Java runs the clock on your local machine and in my experience, it can get way off fast. Lastly, you need to set up the email addresses in ISY. Have you confirmed that your ISY is properly sending emails using the address you used in that program? When trying to figure out what is going on, go to the program summary page. For each program, it will show you the last time the program ran, whether it ran true or false, and the next scheduled time. The program you wrote should list tonight at 10:35 as the next run time, and last night at 10:35 as the last run time. It should have ran 'true' last night, and it will run 'false' tonight (and every night until 4/1). If it lists that it ran last night at 10:35 but ran false, then that means you didn't "set the clock" (fill out the starting variables I listed above). If it says it did run last night and ran "true", then that means your email settings aren't working. You can always right click on a program and hit "run then" or "run else" to test that the "then" or "else" clause are doing what you expect.

If $iDay.of.Month is 9 And Time is (whatever you want) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') This will execute whatever you put in the "then" section whenever it is the 9th day of any month at whatever time you specified. Incidentally, I am not sure what happens if you import a program that refers to a non-existent variable. I have never tried it. You might need to re-import the programs if you did that first. Maybe not. Let me know.

OHHHH SHOOOT I just saw a mistake in my directions. Leap year variable is supposed to be set to 1 this year. 0 is a leap year, not 3 as I wrote. Please be sure to set leap year to 1.

Unzip the file, Right click on the "my programs" folder at the top of the folder tree on the "programs" page, the click import, and point it to the file you just unzipped. Just follow the directions I put on the wiki. There are like 4 steps total.

You are correct. You would need to use an OR statement to connect 12 dates per year for as many years into the future as you want. If you haven't already started using variables, implementing the programs is not hard at all. Just download them from the wiki and install them. Then label the variables using the screen shots. Then all that is left is setting all the variables to today's date (month 3, day 1, year 2013, and day of year (31 plus 28 plus 1). The other variables will self populate at midnight. It only gets tricky if you already are using the same variables. But I get the feeling you haven't used any of them yet.