larryllix

Yeah, I linked to my ISY program in a previous post, that was styled after that chart. The dewpoint curves from 100% down to about 55% follow the (100% - RH%) /5 very closely, but at lower humidities the curves don't behave that simply. I took any (100% - RH%) difference over 45%, and added an additional 0.7 of difference to it, before dividing that resultant by 5.That made the lower humidities follow the dewpoint curves closer. Exponential calculations would have definitely been better. Mountians? LOL. In my previous home I was 350m abobe sea level to my foundation top = 1148 feet, and I was in a slight valley from mostly flat land around us.. Currently, my home is on a small mountain at 340m above sea level to my foundation top = 1115 feet. (yup, lower) My humidity here, ranges from about 30-100%. Mostly in the higher ranges. We have huge bodies of water about 10km, on one side and 80km away, on the other side. That gives us snow, over our heads most winters and some days needing to blow snow out the driveway at least three times. The location was a mistake but the views are spectacular. LOL

I explained why that doesn't work in my previous post. Check the ends of the curves. They are way out for a workable range outside.

Just an information warning. If you use a RPi with NOOBs and install an OS the installation process partitions the microSD card and formatting it elsewhere will NOT get the full SD card space back. This takes partitioning software to correct the SD card back to one partition for full usage of the space. Other software can do this also.

If the status fields are blank then ISY has never received a Dry signal from the Leak Detectors. The reset buttons must be pressed to accomplish this. @Paul. He is using four LDs with AND logic. Using control / switched with AND logic can not work as four will never be processing True signals simultaneously inside ISY. It can't work with the intermittent nature of the signal logic. Status must be used for that program only and the "Run at Startup will never function either. The Wet program can use other but I would prefer not to use status at all.

Quite right about the number of controllers for scenes. My bad there. I don't use multiple device scenes with controllers at all. Leak Detectors only send out wet/dry signals when triggerred wet by water detection, and when manually reset by a tap of the button. ISY remembers the status until told otherwise. Scenes with muliple leak detectors cannot work to reset as the AND function is required to ensure all detectors are reset to dry status. He is using all statuses in his "If" section so "Run at Startup" works fine. If he was using Control / Switched conditions, this would not be the case ('Run at Startup" could not work). Control/ switched logic always tests False unless they, themselves are doing the triggerring at the time. More than one logic line can never be true simultaneously. With AND logic the If section could never be True.

You have both programs to "Run at startup", and are using status instead of "control / switched", and may not be resetting the leak detectors after detecting wet or possibly testing / installation. You could use "control /switched" in all cases but then an leak detector that has already triggered would be blind to more wet triggers. I see the purpose of the "Run at startup" for both programs and this is causing you the trouble. However, until you dry and reset the offending Leak Detector they are doing their jobs properly. Corrected as per Apostolakisl below You cannot create scenes with more than one Controlling Device and scenes do not support And / Or logic. You need ISY programs for this as you have been doing. Check the state of each LD to see whih one is locked on Wet.

After owning a bunch of them and my son having a house full of them I would avoid anything using a GU10 or MR16 bulbs. Very bad lighting. Bulbs are very restrictive for selection, poor efficiency, and you'll require about 4-5 times the number of fixtures to get even lighting. The fixture are very poor quality design. If you use incandescent halogen bulbs in them, the wiring will be charred to a crisp after ten years with the in-ceiling fixtures.

Yeah. I found several different calculations for dewpoint but none of the exponental stuff was happening in ISY math, so I used the simplest proposal put forward I could find and then worked it from there. A simple divide by 5 works for a good portion of the curve for some usages, but the curve got out of whack, so I experimented with a factor applying it to only one end ofthe curve until it got close enough. http://forum.universal-devices.com/topic/21727-bathroom-fan-control-solution/?do=findComment&comment=215296 Note this takes v5 and the Repeats are used as inline "If / then" constructs. When you see a line with $Variable = 0. That is to terminate the Repeat While construct. Multiple programs could have been used for v4 in order to get mutiple If / Then constructs.

Yeah! Exactly what Stu posted above from the mechanical to the logic comments. I only have one KPL and it function as a combination lock. I don't like the looks or the function of them. In my Gathering room I have 6 x RGBWW LED strips, 5 x Hue bulbs, 5 MiLight RGBWW bulbs, 5 sets or lights controlled by 5 Insteon SwitchLinc dimmers and I operate all of them in 7 different scene setup from one SwitchLinc switch. ISY is your friend.... ...... Your imagination is the limitation.

Once you go to V5 you can receive all those values in a realistic decimal formats. Kumoapps drops them right into ISY all in perfect decimal format.

I find faults in my ISY programs from years ago that seemed so simple. Another method I like to use is to bring all the raw CAO data into ISY state variables but only use a common variable for all other programs. This way I can back up parameters with multiple sources. My outside temperature variable comes from three different sources averaged with any value outside more than 2C from the average thrown out of the average calculation. This selectively excludes temperatures from each sensor where the sun affects the reading improperly. Living on a small "mountain" the sun shines on all four walls at some point in the day. V5.x is invaluable in this, having a while repeat construct that can act as an inline IF condition, making program logic stretch much further in one program. Another method I mostly use is with two or more sensors. One is a primary source and when it is updating and looks reasonable the secondary source program is disabled. If the secondary program runs and it doesn't look reasonable or i't heartbeat also fails then a notification is sent out. I found this invaluable when a new stat is installed...no programs use it directly and it's easy to change out. ISY...the best logic puzzle toy yet!

I can see you have been working very hard for some time on this one! I would worry about delta temperatures using too many factors to contribute to a delta humidity. If one element fails it would be easy to receive an erroneous value among other problems. To get around most of these obscure problems, I would typically use a simple all-else-fails timer to shut of the fan on a long term basis. Although it should theoretically never come into play, it could save you from some weird sequence of operations that you never thought of, leaving the fan on while you away on a winter vacation for two weeks. Too much outside air can cost you heating money, when you live in a cold winter climate. I do a similar thing for my cold cellar, but compare dewpoints (inside to outside), so I don't draw in lower % RH air, that results in raising my cold cellar humidity, instead of lowering it, once it is cooled to the indoor temperature.

Screen shot. Then use the Full/Advanced editor button bottom right

Seconds would maje a lot nore traffic and i.o jams on the ISY. ISY has lots of spare cpu power but i/o is the biggest bottleneck usually. Sent from my SGH-I257M using Tapatalk

The CAI boards don't need anything else. The ISY Rest variable stuffer code is built right in to it. Sent from my SGH-I257M using Tapatalk

I agree. Seems to be a typo. Status should work as a simple logic filter (no triggers) and control / switched works as well but control / switched will always be False and always run Else (depending if any other OR logic doesn't override)

The status On line will cause you troubles if you ever add another line to the then or in the else section. When you change the status the program will trigger again and run Else immediately. No further lines after the set Kitchen Light to 100% (if you added one) would execute. The line isn't needed for your case anyway. You can try it this way to see if you like it. Set the local level to 10% on the SwitchlInc to start with, by holding the paddle down to the lowest level you can get it to. Tap it off. Tap it on. Come back after 10 PM and try it again or change your time frame to test during the day. Don't forget to set the time frame back Have fun with it. You can't break it If Control 'Kitchen lights' is switched on And from 7:00 AM to 10:00 PM then Set 'Kitchen Lights' Fast On Else No Actions

You program should never be true with two Switched On triggers. Take one out and only use one. One of tricks I have used is to set a long ramp of the light with the 100%. Say about 3-4 seconds. Now when the switchlinc Control On is detected and the time frame is met, turn the light on to 10% with a fast ramp on. Actually thinking back...the opposite works better. Set the level so that the local (paddle) light level comes on at 10%. Now with one program using the SwitchLinc control On beat the 10% with a fast On which is 100%. You won't even notice the delay and the local level will not be reset to 100% with a Fast On. You can test this technique at the SwitchLinc. Hold the paddle to get the 10% and then turn the switchlinc off. Now double tap the paddle up. Turn off, then back on with single taps. It remembers.

The login via the ISY portal is the same as the ISY Portal login, not the ISY login. If you have forgotten, then use an automatic password fill-in from your browser and change your login to something you can remember. Creat a short email with the info and mail it to yourself, saving it in an obscure and not obvious folder. Keep a note book in your desk drawer?

When you call another program you specify which section (If, Then, or Else) you want to run, whether disabled or not. "Disable" only disables the triggers in the program, in the If section. Everything else works per normal.

Just a reminder that this ISY Portal button will display the last option you selected in the pulldown. IOW:"Portal Login" or "Go to My ISY" may not be on the button shwoing, unless that was your last selected option.

Easiest and cheapest yet. Put a push rod arrangement with a float at the bottom end and an Insteon door/window sensor at the top end of it. A few brackets with holes and some threaded rod could do it. For the float a toliet float may screw right onto the end. Battery monitoring signal security should be easy and already done by others. To work with Apostolakisl's idea above, a float switch used for sump pumps (and readily available) could do the job. Most just work by tilt position and the wires could be directly connected by cutting off the dual plug/receptacle adapter that comes with item. https://www.homedepot.ca/en/home/p.mechanical-float-switch-10-sump.1000668933.html

Being involved with overcurrent protection matching curves for 34 years, I would disagree with the assumption a higher quality fuse would likely damage the SynchroLinc. I don't think anybody can assume the Synchrolinc would be damaged, and the SynchroLinc design makes it very unlikely. Opening up my SynchroLinc I see a fuse, a calibrated current shunt, and some #14 AWG wire between the supply plug and the receptacle, all rated to carry anything that can be plugged into it, except for, maybe the fuse. The nameplate on my SynchroLinc states 120 vac at 15 amperes. No mention of incandescent only or motor loads either. This is likely due to no electronic components or contacts involved in the circuit. Nothing in this circuit is incapable of handling short term surges of 5-10 times that any typical motor would draw. In addition the SynchroLink is plugged into a house circuit with a breaker circuit than will allow 10,000 amperes for a very short period. The SynchoLinc did not require a fuse in it's power circuit design, if plugged into an already protected for 15 ampere circuit. The fuse should have been for the sensitive electronics. Pass the CSA / ETL/ UL approval faster? Who knows? The conductors in the synchroLinc were approved to carry the rated load, and therefore a surge of 20-30 times that for a few seconds, is not likely to damage the conductors for that same reasons given previously.... good conductor metals have a longer damage time curve than any slow blow fuse. Otherwise, slow blow fuses wouldn't exist and this is what they are designed for....to limit the amount of time a particular current that can flow without damaging equipment. It's all about understanding overcurrent protection curves. No suggestion was made to increase the rating of the fuse, only the time curve that the fuse will allow. This is standard procedure and acceptable code practice with any fused distribution panel to replace standard fuses with slow-blow, or dual element fuse types, where a motor load is connected. Many dual element fuses blow at lower currents than their fast-blow counterparts given the same current ratings. They are consider better protection. However, supporting your point. (and a good warning) People should not change electrical designs, on an assumption that it should work, especially putting in electrical protection when they do not understand the potential consequences. There are other solutions for most people.

Mechanical electrical conductors are very long slow blow curves. Contacts and electronic parts aren't making them hard to match destruction curves for protection designers. Aluminum wiring is worse due to it's exponential resistance to temperarure curve. Copper can glow red hot and not vapourise due to the opposite curve style. A slow blow should never be a problem for a piece of copper conductor wire with a CT core around it as the thermal curve of a slow blow fuse is shorter than a simple conductor. YMMV Sent from my SGH-I257M using Tapatalk

Maybe it was you then. A slow blow style of fuse should have been installed for the manufacturer. This tells us how cheap The Smarties are in manufacturing products. Sent from my SGH-I257M using Tapatalk