BigfootC Posted July 3, 2017 Posted July 3, 2017 I want to monitor the time between cycles on my water pump. In my ISY (version 4.5.4), I have a state variable which monitors the power it draws when running. So I know when it is pumping and when it is off. When the time period between cycles exceeds 60 minutes it is telling me that the water filter needs changing and I want to get a text or email message. Any help with some guidance on how to program this would be appreciated.
smokegrub Posted July 3, 2017 Posted July 3, 2017 I don't know if this will help, but I use it to tell me if a pump runs more than 5 minutes. Pump Not Off - [iD 0017][Parent 0021][Not Enabled] If Status 'Pump / Pump SynchroLinc' is 100% Then Wait 5 minutes Send Notification to 'Donnie Wheeler' content 'Wolf Creek Pump Did Not Turn Off' Else - No Actions - (To add one, press 'Action') Sends a notification if the pump turns on and runs for 5 minutes or more. This allows me to assess if a major problem exists and make a decision to turn the pump off using the Pump Controller (Outdoor Module). 1
larryllix Posted July 3, 2017 Posted July 3, 2017 (edited) As per smokegrub's program..just set a timer to notify you and let the control/switched event of the pump detection keep resetting the timer. If ....control pump is switched off (status doesn't work well here) AND ....control pump is NOT switched on (cancel Then running = off is coming) Then ....Wait 120 minutes = offtime x 2 (maybe missed one signal and eiminate nuisance notifications) ....send notification to you Else ....--- You also may want another reboot program to initiate this in case of a power failure. Enabled to run at power up. If ...-- Then ....Run (then) program above Else ...--- Edited July 3, 2017 by larryllix
BigfootC Posted July 3, 2017 Author Posted July 3, 2017 Smokegrub: thanks for the suggestion. I already do this but looking at my state variable $PumpPower > 0 to detect if the pump is running. Larryllix: I assume in your example "control pump" would be my state variable $PumpPower which tells me the power draw. So the code the first part of the If would be If $PumpPower = 0 (pump is switched off) However, I am confused about how to code after the AND because isn't "NOT switched on" the same as pump is switched off? Is it AND $PumpPower Not > 0 I'm still a bit of a newby to this ISY condition evaluation stuff so I appreciate your patience. Thanks
larryllix Posted July 3, 2017 Posted July 3, 2017 Smokegrub: thanks for the suggestion. I already do this but looking at my state variable $PumpPower > 0 to detect if the pump is running. Larryllix: I assume in your example "control pump" would be my state variable $PumpPower which tells me the power draw. So the code the first part of the If would be If $PumpPower = 0 (pump is switched off) However, I am confused about how to code after the AND because isn't "NOT switched on" the same as pump is switched off? Is it AND $PumpPower Not > 0 I'm still a bit of a newby to this ISY condition evaluation stuff so I appreciate your patience. Thanks This is one of the confusing logic puzzles ISY has. Took me awhile to absorb this one. The best example I have is to use a SwitchLinc Switch Status has two states = On/ Off. This is the status of the electronic switch controlling the light. Along comes the switch handle with four states. Tapped up, Not tapped Up, tapped down, and Not tapped down = think two devices for just the paddle. So now the tap up detection = ISY "Control switch Switched On" signal has two states. Happenning now or not happenning. Also the tap down detection = ISY "Control switch Switched Off" signal has two states. Happenning now or not happenning. When an event like a SwitchLinc paddle is tapped down , the ISY engine scans all the programs to see who cares. If ....Control device is switched Off would get evaluated by the ISY engine finding it true and running Then but ....Control device is NOT switched Off, would get evaluated by the ISY engine finding it False and running the Else section. Let's see if I can confuse you further another way. The line can never be true. If the paddle is not tapped down, the program logic line, if it is ever tested, will always be False When the paddle is tapped down, the program logic line will be tested and the Not will make it False.
BigfootC Posted July 4, 2017 Author Posted July 4, 2017 Thanks for the clear explanation. I think I understand the concept. 1
Recommended Posts