pjjameso Posted February 15 Posted February 15 (edited) I just moved from Polisy to Eisy and one of my programs stopped working. Had to break it into 3 programs to get it back up and running which seems very inefficient. Looking for some help on improving the routine. Basic idea is when air quality is good just run the ERV for 15 min each hour. If the quality if above the thresholds run the ERV continuously until they return to normal and then resume the 15 min routine each hour. Here is what I currently am using. Airthings Timer - [ID 003E][Parent 0030][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 1 hour Run Program 'Airthings AQ Test' (If) Else - No Actions - (To add one, press 'Action') Airthings AQ Test - [ID 003F][Parent 0030] If 'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM And 'Airthings Controller / Main Level' VOC <= 225.0 Then $sAirThings = 1 Else $sAirThings = 0 Airthings AQ Normal - [ID 006D][Parent 0030] If $sAirThings is 1 Then Set 'ERV' On Wait 15 minutes Set 'ERV' Off Else Set 'ERV' On Edited February 15 by pjjameso Typo Quote
paulbates Posted February 15 Posted February 15 (edited) When switching to eisy it's common to have to open some programs and press save to get them working. Sometimes these programs have a yellow icon next to them Edited February 15 by paulbates Quote
pjjameso Posted February 15 Author Posted February 15 5 minutes ago, paulbates said: When switching to eisy it's common to have to open some programs and press save to get them working. Sometimes these programs have a yellow icon next to them Thanks, tried that and even recreated original program and couldn’t get it to work. Quote
Guy Lavoie Posted February 15 Posted February 15 There is nothing wrong with using multiple programs, and it's not a question of efficiency. Complex, nested logic requires multiple programs like that. Quote
IndyMike Posted February 15 Posted February 15 @pjjameso, your timer program is marked "Run at startup". Can you see it running in the "program summary tab" (you've probably already looked). If not, try a manual start (Run Then) to see if things run and continue. If everything looks good with the timer program, try re-writing and saving the "Airthings AQ Normal" program. I have seen instances where the "text" of a program is correct, but the saved XML is not. A simple Edit/Save will not correct this. Quote
pjjameso Posted February 15 Author Posted February 15 I cant get these programs to work at all. It seems like the timer program will not execute the aq test if statement as the variable show last updated friday night. Weird as i have changed the timer to every 2 minutes for the test. Thinking there might be a bug in the 4.91 where commands following a repeat are not executed. Of course it could be Im just missing something obvious. Thanks for the help Quote
pjjameso Posted February 15 Author Posted February 15 Think it may be working now for god only knows why. Just using two programs, a timer and a test. Copied below for info. Thanks for the help Airthings Timer - [ID 003E][Parent 0030][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 1 hour Run Program 'Airthings AQ Test' (If) Else - No Actions - (To add one, press 'Action') Airthings AQ Test - [ID 003F][Parent 0030] If 'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM And 'Airthings Controller / Main Level' VOC <= 225.0 Then Set 'ERV' On Wait 15 minutes Set 'ERV' Off Else Set 'ERV' On Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.