oskrypuch

When I added a 1900 in ISY (MAS), I got a Main, Heat, Cool and Fan control line. Adding a 1700 (STY) I only get a Main. I can still control the 1700, temps and mode show correctly but the Heat/Cool State is blank on its Main page. Is that normal? I could just remove it and try relinking it to check this, but I have it added now to a lot of programs, so would prefer not to do that unnecessarily. * Orest

.11 updated to .14 All is well. * Orest

Thanks, and even better, so far so good. * Orest

I rigged up a pair of triggerlincs on the garage doors. These were programatically tied in to some keylincs and an X10 Ding Donger. Tested it out after the install, seemed to be working fine. Over the next couple of weeks I would periodically get phantom indications that the garage door was open, and curiously I saw the AUX input as showing a value occasionally even though the jumper is set to disable that input. I looked for possible AC noise, moved an access point into the garage, rebooted the triggerlincs, fiddled with the jumper, removed and readded them in the ISY, replaced them (I had two extras), installed NO microswitches to drive the triggerlincs thinking there might be something odd about the magnets and metal door -- this also allowed me to prove the trigger circuit continuity. Finally in desperation I even jiggled the cords, however I studiously avoided factory rebooting the ISY. Nothing seemed to cure this errant behavior. I was about to give up on the 2421s and get some hardwired EZIOs when I hit on the solution ... One night there was a wicked windstorm outside, and the garage door "open" indication went crazy, activating many times an hour. I had to get up and disable the program. In the morning it kind of dawned on me what was going on. The garage doors had been knocked about by the wind. The triggerlincs are screw mounted to the doors themselves. I took another look inside and it seemed that the batteries might have been a trifle loose inside. I stretched out the spring a bit, sprayed it with contact cleaner and then also put two strips of electrician's tape where the battery fits to snug it up. The case seemed to snap together more securely. The problem disappeared! It seems that the vibration from garage door opening/closing, or the wind, or poltergeists would work loose the battery just enough that the switch would reboot or something just short of that, and this had caused all the trouble I had had. If I had set it up with the triggerlincs/switches mounted on the wall, this would not have occurred. However, the physical layout of the door demanded the switch be on the door. * Orest

Well, somehow, that is very satisfying! * Orest

I want to create two non-overlapping time periods, but with no "uncovered" time inbetween. With inequalities that is easy ... range one if A .GT/E. 8 and A .LT. 9 range two if A .GT/E 9 and A .LT. 11 All values, including 8 and all values between 8 and 11, but NOT 11 are covered in the two ranges, and there are no values between range one & two. So, now the time interval programming ... program early If On Mon From 5:30:00AM To 8:00:00AM (same day) etc. program later If On Mon From 8:00:00AM To 9:00:00AM (same day) etc. Would that work, or would both programs execute at precisely 8AM? The scenario is a manual force of the IF clause in both programs. I may be answering my own question, but I understand that the execution of a time interval IF clause will trigger at the From time and it will run the THEN clause, and then again at the TO time, and run the ELSE clause. If that is the case with the the manual trigger of the two programs, then all should be OK. What I do not want to happen is to ever have the THEN clause from Program Early and Program Later to be executed at the same time, but I do want all times in the range covered with no uncovered time inbetween. * Orest

Right, so to trigger a re-evaluation, the result TRUE or FALSE of the IF clause does not need to change, just one of the input values in the inequality. A range of inputs (as you note) might keep the result as TRUE, or FALSE, whatever it was. * Orest

Wrote a short test program, and it looks like to trigger a re-evaluation, you need BOTH a parameter refresh PLUS that parameter must have changed value. So, even when the parameters refresh, if that particular value did not change, then no trigger. If that proves out for sure, it will be just what I need. If anyone feels that is contrary to their experience, please post. I am just exploring all this at the moment. * Orest

Well, the story so far, I have five program variables defined ... summer hot summer spring/fall winter winter cold The intent is to have toggled TRUE only one of those, at all times. It would be triggered by the high temp, perhaps the current temp, as well as high average wind velocity would affect the winter assessment. That is a work in progress. Those variables in turn control a number of things, including VenStar setpoints and mode, early curtain closing in the summer, that sort of thing. If the temp changing triggers an assessment, then that will make it easy. I currently have these parameters reassessed at 3pm and 3am. * Orest

If Module 'Climate' Temperature High .LT/E. 60 °F And Module 'Climate' Temperature High .GT. 40 °F Then Run Program 'var season spring/fall' (Then Path) Else Run Program 'var season spring/fall' (Else Path) (had to replace the inequality symbols, the board doesn't like them) Will the above ever execute, that is will the Module 'Climate' parameters changing trigger a program? If so, will it execute continually and repeatedly and hog ISY execution time (the Else clause), or only on the Climate parameters update, which I have set to every 30min? What might be a better way to do this? I was first going to reset all the var season variables at 3:00:00pm, and then test for each season condition at 3:00:05pm to set the correct one. That avoids the Else issue, but seems very sloppy. * Orest

Well, decided to plunge into the TStat, too cool not to do, I am aware of the potential issues of the hanging communication that folks seem to get. To that end, I wrote a set of programs to query the FAN status of the tstat, then flick it to ON, and check if it responded. If it didn't, then likely there is a problem, and it sends an email. program check tstat.wait If Time is 5:00:00AM Then Run Program 'check tstat.set' (If) Else - No Actions - (To add one, press 'Action') program check tstat.set (disabled) If Status 'master bdrm / MAS - tstat - Main' is Fan Auto Then Set 'master bdrm / MAS - tstat - Main' Fan On Wait 5 seconds Run Program 'check tstat.check' (If) Else Send Notification to 'oskrypuch - GMail' content 'TStat MAS error1' program check tstat.check (disabled) If Status 'master bdrm / MAS - tstat - Main' is Fan On Then Set 'master bdrm / MAS - tstat - Main' Fan Auto Send Notification to 'oskrypuch - GMail' content 'TStat MAS responding' Else Send Notification to 'oskrypuch - GMail' content 'TStat MAS error2' I get an email if all is OK, or one of two error emails alerting me to a potential problem. * Orest

A lot has been posted on the EZIO's, it seems that from 2.8.8 on, most of the issues have been settled. Application Independently sense status of two garage doors, both will have a contact switch mounted. Proposed Method The units would be linked in to the ISY for status. I am debating whether to get two 2450 IOLincs, or perhaps just one EZIO2X4. I don't need the other inputs/outputs of the EZIO, but cost is similar and having one box is tidier. Questions I am a little concerned that you might need to poll the EZIO unit to get status, whereas the 2450 like any other insteon device should just send the status immediately on a change. Also about any other issues that still remain with the EZIO family. Appreciate any guidance on this. * Orest

Nothing drastic done. I closed down the ISY Java program, and that took a bit of effort, restarted and all the 1010's and WRITING were gone. I can't be sure what the lights were during the episode, but currently the single green light is ON, flashing when the Java app contacts it. As far as I can tell, the units appear to be operating normal, but that is hardly much of a test. I think it was #2, ISY was way to busy. It was a very large scene I was updating. If that is the case, then perhaps I don't have a problem? * Orest

Well, I guess I join the chorus. * Orest

Yes you can, but that is clumsy. Seems that allowing for a wildcard year shouldn't be too difficult. Hope it gets "on the list". * Orest

Hmm, still a little short of the mark. You would have to reset it each year, you can't set it to a certain month for example, only day/month/year. * Orest

Bingo! Thanks. Now I have seasons. * Orest

I somehow missed that, where exactly is that? It doesn't appear in the schedule dialog that I can see. * Orest

There seems to be no way to query the date (just the time). The ISY doesn't know if it is winter or summer. Am I missing something? * Orest

OK the WRITING and 1010 disappeared, and a message popped up: Socket Open Failed java.io.IOException: An existing connection was forcibly closed by the remote host. Does that mean that some device's tables are corrupted/incomplete? What do I do next? * Orest

Added an item to a scene, got the usual dialog, and maybe halfway through, the task activity bar disappeared, and I'm left with the ISY MAIN window with multiple devices showing WRITING and 1010. No activity for some time now. Now what? * Orest

OK, figured out a way to do it ... program var entry sense.wait (a variable) program entry sense If Program 'var garage open' is True And Program 'var dark' is True And Program 'var sleeptime' is False Then Run Program 'var entry sense.wait' (Then Path) Wait 20 seconds Run Program 'var entry sense.wait' (Else Path) Else - No Actions - (To add one, press 'Action') program entry sense.do If Control 'laundry rm / LND - PIR-Sensor' is switched On And Program 'var entry sense.wait' is True Then Set 'front hallway / FH - Pots' 80% Set 'kitchen / KIT - Pot' On Run Program 'var entry sense.wait' (Else Path) Else - No Actions - (To add one, press 'Action')

OK, I have event1, event2 and actionA. If event1 occurs, then if within 20 seconds event2 occurs, then do actionA. How do I code that in ISY? * Orest

I have the above noted active (amplified) signal bridge installed, here is a link for more info ... http://www.smarthome.com/4823/Leviton-H ... ter/p.aspx It cured a multitude of X10 problems I had. Now that I've moved just about fully to Insteon, I'm wondering if having this guy installed is good, bad or indifferent. My only concern is the potential for the X10 focused circuitry causing interference with the Insteon signal. So far, things seem to be running fine, and I have a couple of dozen units installed so far. Any one with experience? * Orest

Exactly my goal!! * Orest