larryllix

This really begs the question. If you cannot communicate properly with a device, how can we factory reset it when the reason for doing it in the first place is we can't control it? I understand the need for this but logic prevents it from being possible usually.

These constant definitions work for low batteries and a few other functions by keeping lists. A notification with a list like 19212029 tells me the motion went from the downstairs landing into the great room, MBR, and then out the mudroom door. See the list above.

The number as ISY can't handle text, yet. I am hoping they will implement a swap text for numbers function in v5. But I define integer variable as constants for programmes like. $cMudRm is set permanently to 21 so in my programs I can use this. If MudRm.MS is switched on Then Set $sZone.violated = $cMudRm Else .... When the monitoring program sees motion by the state variable changing. If $sZone.violated > 0 Then Notify Larry.via text zone.violated Else .... The notification sends. ------------------------ Motion is detected in ${var.x.x.} room Zones 20:GathRm, 21:MBR, 29:MudRm 10:RecRm, 12:EveBr, 13:AftBR 30:Shop --------------------

I use ten motion detectors. I have assigned each room a numeric identifier. When motion is detected I simply assign a variable called $smotion.room with the room number. Anothet program watches that state variable and if it is not zero sends a text and email notification to me with that variable. This is acompanied by a small chartcof the room numbers to identify what room had motion. I also keep a two variable list of the last rooms activated so movement tracking is possible by reading the eight number list that the two variables can hold. No you do not need a separate program for each room. This also comes in handy for othet logic. If my away detector last sees motion in my mudroom 20 minutes are allowed. If any othrt room is triggered then 4 hours are allowed before marking the house empty.

I had a similar problem with Restore PLM and v5.0.2 beta. I had a hard time getting any one device to restore. ISY was so tied up with the loop, the individual device restore would not activate. I had to keep resetting the linking mode in the device each time the linking mode would timeout and hope that ISY would try to link to that device. This ranged from five to twenty minutes of hoping to hit the restore loop sequence right for each of dozens of battery devices. The loop does get faster as the number of devices goes down. If I had more devices I believe my ISY would have needed to be factory reset and started from scratch . Try allowing one device to link in at a time by repeatedly putting it in linking mode until ISYs timing coincides with the device and it suceeds.

Thanks. I only see one line with Tapatalk??? Edit: I see the whole program(s) now with IE, now.

You mean I posted and editted two compleyr programs, verified the posting and now the mahor part of the code is missing,? Anybody else see more than one line of code in my post?

Program "True" and "False' indicates the last state of the "If" conditional logic evaluation and is used for debugging purposes. If you pull down menu item at the top (can't remember which one) there is an option to turn on folder and program colours so this is more visible to watch program actions and status. This is not a problem but rather a feature. Devices have On, Off, analogue levels etc.

As per oberkc above. If 1.5 hr from sunset to sunrise next day. <---this will always trigger else and control motion sensor is on. then set outside fan on set outside lights on wait 5 min set outside fan off set outside lights off Else set outside fan on wait 5 min set outside fan off Time frames are a gotcha' in ISY. They need to be disabled to NOT trigger the else at the end of the filter condition. If control motion sensor is switched on. <----requires triggering enabled Then run (if) Program2 Else -- Program 2 (disabled) --------- If 1.5 hr from sunset to sunrise next day. <--requires triggering disabled=filter only then set outside fan on set outside lights on wait 5 min set outside fan off set outside lights off Else set outside fan on wait 5 min set outside fan off

That is what I set mine up to do but you have to add in the existing time passed to that point first. Most of the rest is just init to be able to survive a power failure.

Nice. My biggest problem was handling the midnight run over and cutting it off properly. If you don't handle the next day reset of the ISY seconds counter and the pump runs over midnight Example of midnight pump run time: You will get a (negative) -80,150 seconds reading if the pump started at 80,300 seconds and stopped at 150 seconds the next day.

LOL. I guess I misread the program with so many 'ump's. if you have a continuous run over midnight things will be off somewhat depending on how long the run lasts. 24x7 continuous run will register as zero seconds per day as only Offs count.. I also changed mine to minutes to look more of a mentally manageable time unit.

Yes I share the same type of experience with other products. You can't beat aartech.ca's prices in Canada either. Amazon and SH doesn't even come close after money differential and shipping. Order today and receive it tomorrow usually. Well, maybe not if you didn't vote for Dustbin.

From friends that have A/C in the attic they love it and claim they would never change that. Mind you if you put the compressor up there it will be a head shaker too. so just the evaporator coils. They claim the cool air drops down on the rooms from ceiling vents and has a better distribution. makes sense for economy of air pumping but the heat in an attic may be a detriment for keeping the air cold during transit. Turbulence is not your friend! I have a pipe run to my MBR that howls after a certain fan speed. I changed the run from 4" to 5" and changed the furnace boot size up too but it didn't work. Unfortunately, the only way to supply this run was right out of the plenum. grrrr... Right now I have a short piece of flex to accommodate an offset in the run which hasn't done jack skeet for the problem. Some day I am making a double walled pipe muffler that is supposed to work fairly well for stopping noise transmission. Some day I will be deaf anyway.

So you are not using the program you posted then?

There was typically a shutter on the fan output to close down the volume. The installer had to do calculations and close down the damper to suit the CFM required. On squirrel cage fans the less air you move the less power is drawn and the fan speed increases slightly due to less load. If the adjusted damper restriction was removed you could overheat your fan motor with volume overload.

Thanks LeeG!

My ECM fan has multiple logic inputs to control speeds. When the heating mode is selected it starts on a very slow speed and then ramps up to medium speed after about 45 seconds. Then (if selected) ramps up to a high speed about 5 minutes later. This is using two 24vac logic inputs. One of them is phase sensitive to get more logical inputs. originally I had the input from another 24 vac supply that was fed off the other phase of my panel and the fan would not ramp up properly. A call to their tech support identified I was feeding it the wrong phasing and a feature that wasn't fully supported on the ECM motor was being enabled. I moved the breaker over to the other phase of my panel and it functioned properly ramping through the speeds again. That just amazed me that a motor 24vac input could be phase sensitive. All selected in the ECM programming. The same fan motor also has two A/C 24vac logical inputs that control three different speed selections. Then there is a humidity lowering input (jumper to live) that just slows all speeds down a bit. easily takes a humidistat dry contact. Work with A/C only. IIRC there is two fan on logical inputs that do not use a logic table and only provide two discreet speeds. On top of all these speeds the ECM motor continuously varies speeds to compensate for filter clogging and other air restrictions. Timing and speed logic is all programmed by the furnace supplier using this generic GE ECM fan motor. When it goes defective I have to go back to the furnace manufacturer to get the same secret programming setup.

Since you were into this and I have been meaning to create one for my HRV I set these up. They have been tested somewhat but not thoroughly yet. Four Integer variables need to be defined for start, stop, runtime, and scratchpad Here is the start and stop with accumulation timer = runtime HRV.tracking - [ID 0094][Parent 00BD] If 'Cold Cellar / CCel Ventilation Fan' Status is Off Then $HRV_Fan.offTime = [Seconds since start of day] $HRV_Fan.offTime Init To $HRV_Fan.offTime $HRV_Fan.scratchpad = $HRV_Fan.offTime $HRV_Fan.scratchpad -= $HRV_Fan.onTime $HRV_Fan.runtime += $HRV_Fan.scratchpad $HRV_Fan.runtime Init To $HRV_Fan.runtime Else $HRV_Fan.onTime = [Seconds since start of day] $HRV_Fan.onTime Init To $HRV_Fan.onTime The reporting take two programs as I don't want the condition of the fan running over midnight to trigger that program. Note there is code included to account for a running fan over midnight while the report is being generated. This should keep the times exact except for the time short of midnight when ISY is probably very busy. Also, power failures should be handled to stay accurate by initialising key variables. HRV.tracking.report - [ID 0095][Parent 00BD] If Time is 11:59:50PM Then Run Program 'HRV.tracking.report.2' (If) Else - No Actions - (To add one, press 'Action') HRV.tracking.report.2 - [ID 009A][Parent 00BD][Not Enabled] If 'Cold Cellar / CCel Ventilation Fan' Status is Off Then $HRV_Fan.scratchpad = [Seconds since start of day] $HRV_Fan.scratchpad -= $HRV_Fan.onTime $HRV_Fan.runtime += $HRV_Fan.scratchpad Run Program 'HRV.tracking.report.2' (Else Path) Else Send Notification to 'Text Larry' content 'HRV RunTime Report' Wait 8 seconds $HRV_Fan.onTime Init To 0 $HRV_Fan.onTime = 0 $HRV_Fan.runtime Init To 0 $HRV_Fan.runtime = 0 Add in last time to midnight (if any) Send report Set On time = 0. .If running, use midnight=0, else use next On time. Reset accumuated runtime Finally here is a screenshot of my notification message. .

V5.0.2 has some cosmetic problems but is mostly functional for all of my stuff.

Just for my own brain as I hardly ever use 'status' and very few folder conditions. I find them very "hidden". Control ---------- The folder(s) will not be enabled as the control signal(s) 'On' or 'Off' have never been received soon after the power up stage. ISY doesn't know yet. Status --------- How does the 'status' condition for the folder logic get resolved if the controls signal(s) 'On' or 'Off' have never been received soon after a power up? ISY doesn't know yet. A query? What initiates the query?

With the multispeed ECM motor there is usually an extra speed connection to use for HA without getting into complex "is it already running" logic. Usually the highest speed selected rules and the lower speeds do not matter as you are only selecting logic inputs. The PSC motors may not like this idea though as two windings being energised can produce some unexpected results. My past home had a multispeed PSC motor with a few relays that switched to the fastest speed called. When I spec'ed my current furnace, about 7 years ago, the ECM motors were just coming on the scene and hard to find.

Here is a description of the three types used and some history. http://www.achrnews.com/articles/112674-comparing-motor-technologies

You need to be running IIRC v4.2.18 and up. V5++ has it for sure.

Well said. This is a hard concept, at first. I like to think of 'control' detecting the edge of the change or active signal and each device has two (or more) signals. 'On' and 'quiet'. The other signal is 'Off' and 'quiet'. ISY has combined and remembers the results into one status page with just 'On' and 'Off' showing.