
oskrypuch
Members-
Posts
756 -
Joined
-
Last visited
Everything posted by oskrypuch
-
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
-
I have fiddled with my bathroom motion setup, and have implemented all of these facets ... 1) Control two (or more) separate lights or scenes from motion, with a timed OFF 2) Timer restarts/extends while motion detected 3) Allow for an manual override on the brightness when occupied 4) Allow for a manual forced OFF of some lights when occupied 5) Allow for a manual forced OFF of all lights when leaving 6) Minimize the Insteon com traffic I also have three different modes, depending on time of day, whether dark or light, and whether in 'sleep mode', I've only included the 'day' modes for brevity. Motions are fully controlled by the ISY, and set to ON operation only, 30 second timer. The following variables (programs) are used to flag whether the respective doWait programs are running: var BTH mirror wait var BTH tub wait The following are two of a number of variables (programs) that I use to control execution logic: var dark var sleeptime This logic is easily extensible for any number of lights. BTH motion (day) If Control 'master bath / BTH - PIR-Sensor' is switched On And Program 'var sleeptime' is False And Program 'var dark' is False Then Run Program 'BTH motion mirror 70' (If) Run Program 'BTH motion (day) mirror doWait' (Then Path) Run Program 'BTH motion tub 80' (If) Run Program 'BTH motion (day) tub doWait' (Then Path) Else - No Actions - (To add one, press 'Action') BTH motion mirror 70 [disabled] If Status 'master bath / BTH - mirror lights' is Off And ( Program 'var BTH mirror wait' is False And Program 'var BTH tub wait' is False ) Then Set 'master bath / BTH - mirror lights' 70% Else - No Actions - (To add one, press 'Action') BTH motion (day) mirror doWait [disabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 second Run Program 'var BTH mirror wait' (Then Path) Wait 35 minutes Wait 5 minutes (Random) Set 'master bath / BTH - mirror lights' Off Run Program 'var BTH mirror wait' (Else Path) Else - No Actions - (To add one, press 'Action') BTH motion tub 80 [disabled] If Status 'master bath / BTH - Tub Pots' is Off And ( Program 'var BTH tub wait' is False And Program 'var BTH mirror wait' is False ) Then Set 'master bath / BTH - Tub Pots' 80% Else - No Actions - (To add one, press 'Action') BTH motion (day) tub doWait [disabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 second Run Program 'var BTH tub wait' (Then Path) Wait 35 minutes Wait 5 minutes (Random) Set 'master bath / BTH - Tub Pots' Off Run Program 'var BTH tub wait' (Else Path) Else - No Actions - (To add one, press 'Action') BTH motion mirror OFF If Control 'master bath / BTH - mirror lights' is switched Off Then Wait 7 seconds Run Program 'var BTH mirror wait' (Else Path) Stop program 'BTH motion (day) mirror doWait' Stop program 'BTH motion (sleep) doWait' Else - No Actions - (To add one, press 'Action') BTH motion tub OFF If Control 'master bath / BTH - Tub Pots' is switched Off Then Wait 7 seconds Run Program 'var BTH tub wait' (Else Path) Stop program 'BTH motion (day) tub doWait' Else - No Actions - (To add one, press 'Action') Happy to entertain questions, and delighted for any comments. * Orest
-
+1 on control vice status. Believe this is the wiki reference, yes? ... Using Motion Sensors in Bathrooms * Orest
-
Well, that is more or less using a program as a variable, but yes it is a little more elegant. Like so ... Program DoSomething If Then do stuff do stuff Run Program 'DoSomething' (else) Else Thanks! * Orest
-
From the Program Summary page, programs can be listed as Enabled (on/off), Activity (idle/running 'xxx') and Status (true/false) In an IF statement you can test for the Status like so: If Program 'DoSomething' is True ... I don't see any way to directly test for the Activity of a program, IOW whether it is currently idle or running Then or Else, etc. You could handle it with a separate Program "variable", but that is a bit clumsy. That was what I was asking. * Orest