
pjjameso
Members-
Posts
329 -
Joined
-
Last visited
Everything posted by pjjameso
-
ERV Air Testing Routine - Improvement Suggestions
pjjameso replied to pjjameso's topic in IoX Program Support
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 -
ERV Air Testing Routine - Improvement Suggestions
pjjameso replied to pjjameso's topic in IoX Program Support
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 -
ERV Air Testing Routine - Improvement Suggestions
pjjameso replied to pjjameso's topic in IoX Program Support
Thanks, tried that and even recreated original program and couldn’t get it to work. -
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
-
Any suggestions on how to improve process would be appreciated. Not an expert at programing by any means, more like try, fail, try again, rinse and repeat!
-
Okay, no idea why it worked on Polisy perfectly as one program, but to get it working on Eisy had to break into 3 programs. Issue solved so far... 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
-
-
@Jimbo.Automates Would it be possible to add the PM 1.0 and 2.5 measurements to the nodeserver? 2025-02-14 12:25:25.689 Thread-32 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm1=2.0 2025-02-14 12:25:25.689 Thread-32 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm1=2.0 2025-02-14 12:25:25.689 Thread-32 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm25=2.0 2025-02-14 12:25:25.689 Thread-32 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm25=2.0
-
Thank you much! Timer - [ID 003E][Parent 0030] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 1 hour Run Program 'Airthings AQ Normal' (If) Else - No Actions - (To add one, press 'Action') Airthings AQ Normal - [ID 006D][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
-
So migrated to Eisy after bricking my Polisy with the upgrade. All seems to be working except for one program which I cant figure out why. The program shows green which means the If statement is true but the ERV doesnt turn off after the 15 min wait period. Any thoughts? Airthings AQ Normal - [ID 006D][Parent 0001] If 'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM And 'Airthings Controller / Main Level' VOC <= 225.0 Then Repeat Every 1 hour Set 'ERV' On Wait 15 minutes Set 'ERV' Off Else Set 'ERV' On
-
Quick question, does my zwave internal board mount internally in eisy or do I need the external enclosure?
-
Wired…. 300$ upgrade to eisy for me unfortunately.
-
Router shows online, and I can ping. Ioxfinder shows it but version is blank.
-
Well count me in as to a possibly bricked Polisy. Watched the upgrade on mobile app complete to 100%. Unable to reboot via 5 button presses so pulled the plug but not no beeps only far left light is on. Any thoughts on what to try at this point? Probably the quickest fix is to buy an Eisy!
-
The interesting point is the buttkicker has never changed to another device in the then statement. It’s just the device in the join action. Wonder how the set device is locked but the join is not, could it be due to the apostrophe? Maybe I should loan you a couple of Sonos units!
-
Thanks Bob for your thoughtful reply. One curious point is with the then statement Set 'ST-Sonos / Buttkicker' Join Basement Is that the buttkicker never changes in the program just the join Sonos device. Wonder why if it is reindexed as you suggest. Appreciated your help, understand that there doesn’t look like a solution.
-
Thanks Bob for the explanation. Of course I have a follow up question, is there a way to delete or disable all the other nodes in the ST-Sonos which would then force a default to the basement node. Or would it try and join to itself, assuming only two nodes?
-
I have a simple program that senses when to execute a join function as seen below. My problem is that it works fine but then after a while it loses the saved sonos unit in the program and changes to a random sonos unit. Is this a problem in the program function of IOX or is it a st-sonos issue? Any thoughts on how to correct the issue? Buttkicker - [ID 0032][Parent 0001] If 'Emporia / Bmt UPS' Killowatts >= 0.4000 kW Then Set 'ST-Sonos / Buttkicker' Join Basement Else Set 'ST-Sonos / Buttkicker' Leave
-
Thanks for the effort, appreciate previous updates......
-
@Jimbo.Automates Thank you for the update. Of course I can’t figure out how to turn off polling, could you point me in the right direction?
-
@Michael Ticket created.
-
@Jimbo.Automates Thank you Jimbo. Question when I try and upgrade it says I dont have a valid license. Is this a bug or do I need to purchase again?
-
File too big to attach, send email address?
-
Will do, will revert tomorrow with file.
-
I was more trying to not overload the short polling process by deleting the node. Solution at this point is to increase the polling time.