larryllix

This is the method I use for almost all my MSes. It works like a charm and no delay can even be detected by us. I also use logic controlled dimming for the lamps involved by manipulating the scenes. Can you post your program involved here to look at?

I guess we would need specifics to evaluate the value of using the stat to protect from further damage. How did the A/C unit malfunction? If The A/C unit was running continuously the temperature should have dropped. Maybe a window is in order.

This sounds a little nonsensical. Aren't you basing a protection mechanism on the thermostats system that is failing? It also sounds like the A/C is stuck on and yet you are sensing a high temperature to turn it off. Wouldn't an independant thermostat be in order to protect this from overheating and over cooling? Maybe just a mechanical thermostat in series with the cooling wire for reliable protection against runaway. I would be sure it may be more complicated than first glances.

That sounds more like bad communications. My two leak detectors have never missed a beat in about a year now.

Most of my main devices turn on by scene link from the MS to the lamps/light. They will all turn on manually and still automatically but will not turn off automatically if my ISY fails. I love HA! I started with X10 back in the 1980s and when I moved couldn't wait to get a better (Insteon) system.

Strange I do not have a 2441TH and only two 2441ZTH units talking to ISY. When I changed my units from F to C the scale of the transmission of data does not change. The 2441ZTH only transmits C with two counts for every degree. When you change your ISY994i over to C from F no adjustments are made on the 2441ZTH thermostats to accommodate the scale change. It would appear that F scales are all done at the readout ends.

That is the time (new) they need them. The factory fresh devices do weird thing that you or I could never make them do if we tried to.

After not heeding this advice from other many times I always do this now. Always factory reset every Insteon device before using in your HA system.

In the first scenario the links connecting the two switches did not get installed. - Are you sure you used the correct switch as the controller and the other with the load as the responder? - The Insteon commands from the switches can cause ISY to "think" the devices are on without actually operating them. Do a device query after operating to update to real statuses from the actual devices.

Yes the same CU30x controller. My well is 155 feet deep (lift probably only about 50-60 feet)and using the 1/2 hp as the biggest I could get for 120vac. The pressure is limited to 60PSI and at 70 PSI it takes a long time to shut off. If my well water level drops significantly it may never shut off and consume massive quantities of energy before noticing. I only have one floor and basement. A second story would made the story different.

Yeah! what he said! I was getting around to that in about another five-six hours but I had to warm him up first! Edit: replaced minutes with hours

Another possibility (and second thought)would be to define a variable called $Winter that would be evaluated set every day. The time could be tweaked with experience. Program Set_Season If ..at sunrise every day Then ..run Program Set_Season.2 Else -- Program Set_Season.2 (disabled so times don't trigger) If ..From 12:00:01 AM ..To 7:00 AM (adjust by experience) Then ..set $Winter to $cFalse Else ..set $Winter to $cTrue Now the rest should be fairly straightforward. Program Event If ..From 6:30 AM M-F ..To 7:30 AM Then ..run program Event.season Else ..set scene winter Off ..set scene summer Off Program Event.season (disabled but $Winter is not a state var. and won't auto-trigger anyway) If ..$Winter is $cTrue Then ..set scene winter On ..(Wait 1 hour ..set scene winter Off = alternative to time range usage above) Else ..set scene summer On Note that time frames filters are usually best in separate DISABLED programs because the end time triggers the else section if you are using code there.

"Between" or from-to exactly? From-to time conditions initiate Then - Else at only those two exact times. There will be time where a partial run may happen or they neither will run. If you want one program to always run depending on season I would use a variable called say.. $Nightime. Program Night.detection If ..From sunset+10 minutes ..To sunrise-10 minutes Then ..set $Nightime to $cTrue (I define variable names as constants =1) Else ..set $Nightime to $cFalse Program Event.trigger If ..From 6:30 AM ..To 7:30 AM Then ..Run program Event.season Else ..Run program Events.stopAll (common off program/scene) Program Event.season (disabled to stop self triggering) If ..$Nightime is $cTrue Then ..Run program winter scene Else ..Run program summer scene The sunrise times will not have your offset in them so some inaccuracies may be incurred but if the most important time is 6:30 and one always must be run this may do your job or be another route to contemplate.

Do the programs have to exactly at 6:30 and stop at 7:30? If so the determination of season using sunrise will cause problems in the same program. It appears to only ever start the "Then" sections based on your sunrise times. At 6:30 and 7:30 the "If" logic in both programs can never be true and the "Else" sections will always run. The time range will not work that way.

Since the syntax will be critical on this perhaps you can paste your programs here for the exact wording. Right click on the program's icon (in ISY's Admin Console) and select "copy to clipboard". Then paste it here. One point of possible misunderstanding is the time conditions using sunrise do not have a before or after. They will trigger at an exact time specified only. Any event listed in your "If" section will cause the whole logic to be evaluated and run then or else depending on the outcome. At 7:30 on weekdays both "elses" will run.

I have been running an SQE variable speed Grundfos pump for the last seven-eight years in my home. Since about Sept 2013 I have installed Insteon units and currently have about 40-50 units now. I have never experienced a problem between the two that I have ever noted. The Grundfos signals are superimposed on the lines to the pump and by the looks of the coils in the control box the incoming supply is well isolated from interference and interfering with external gadgets. My pump control is 120vac 1/2 hp and runs off my PV inverter. I chose 120vac due to only having a single phase 120vac inverter at that time. Plugged in, within ten feet, and probably not more than 15 feet of wire, is my PLM and ISY running off my grid panel. I do have Insteon plug-in units running off the inverter backed-up circuits with no problems. My X10 units have communication problems on those circuits with over 70-80 feet of 14/2 cables but not Insteon. AFCI breakers did give my Insteon units some problems before adding more dual band units in those zones but I seldom see inverter interference in bedrooms because the inverters aren't running during non-sunny times when I would be in the bedrooms with lights on. I have no Access Points, no Insteon repeaters or phase bridges, and no noise filters but I live in the rural with only three customers on one underground grid transformer. I do have an old X10 phase bridge on the same 5 foot long circuit that my ISY/PLM is plugged into. This Grundfos signal concern was raised with me years back on another group when I first purchased it with concerns for working with an inverter. Has never been a problem for pump, inverter or Insteon.

You can backup, decompress the file and load it into your browser or editor. You can read everything there easily.

One other thing while you are at it is to factory reset each and every MS when they are new before installing them. I found some of mine doing things that didn't even seem possible until I factory reset them.

I use a setting of about 50-75 for mine. A few report dark in shaded rooms quite early and the count of them is useful on very un-sunny days to activate programs based on number that reported darkness as an analogue value.

For the four-way switching circuit, only the switch/dimmer wired to the flood lights will electrically control the lights and the other two units will not have loads on them, only sending Insteon commands to the one with the light load on it. The wiring will have to be sorted out and some capped off. All switches/dimmers will require a neutral connection and act as if they were in parallel controlling the light after the logic is set up. Take several pictures inside each box from different angles showing the entrance of each cable (under the clamp), wire colours and what connections each one goes to BEFORE starting disconnections. Label them definitively on your computer.

Some basics with these MS units. - Battery operated devices do not generally respond to queries from ISY unless the placed in "Linking" mode by usage of the button inside. - a query will update the battery low input. Only the LowBatt will respond to a query when not in "linking mode". Right click on the Low Battery node and select "query". - it is popular practice to disable the MS from sending the Off command and let ISY do the Off timing - darkness/lightness responses takes about 5 minutes to test after changing the light density - Night only mode means do not send out motion detected during light times. This will disable sensing motion during the day and not allow other programming ideas to recognise occupancy of the house. - Switch 5 on means the hardware controls are now inactive and settings are all in the ISY software options (after linking mode is established by the button long pressed). Not entering "linking mode" first will give you a multitude of errors. - In your ISY program (if using it for time control) you should have a time off timer in the "Then" section and a 'Control" in your "If" section. The "Control" usage insures that every time the MS sends an "On" the then section will start again retriggering the "Then" Wait timer to start over. - If you created a scene, the MS must be in linking mode to receive the update. More complex programming will then be needed to intervene with the direct link you have established between the MS and the light switch to control brightness and time of day response. Some of my LEDs are just left to come on during the day as the energy used is so insignificant. There is a way but more complex than if you didn't create a scene (and a direct link = ISY independent) between your MS and light control and just let ISY handle the "On" decisions. - If the "As motion is sensed" is not checked the MS will go to sleep for several minutes each time motion is sensed an will confuse your setup process thinking. Make sure it is checked, especially if you want a 30 second time off otherwise motion will not retrigger the Wait timer and the light will be off most of time while you are moving in front of it. I recommend a longer Off time off so motion is detected more easily within your time selection. The blinking on and off becomes annoying quickly. 1-2 minutes works well for me in all rooms.

Nice! It would seem I will need to get a serious RPi unit to be a slave to my ISY to get these values accessible to programs at lest until v5 arrives in 2018.

My DDNS service was totally free also, (with the purchase of their router.)

The variable needed (thus this request) is not available and is not likely to become available from the flavour here. http://forum.universal-devices.com/topic/13900-use-of-sysextip-variable-in-notifications/page-2

Odd Days - [ID 00A3][Parent 0001] If Time is 12:01:00AM on 2015/06/01 Or Time is 12:01:00AM on 2015/08/01 Or Time is 12:01:00AM on 2015/09/01 Or Time is 12:01:00AM on 2015/11/01 Then - reset the date timer code to 1 Else - No Actions - (To add one, press 'Action') Something like this could get you to next year using a daily incremented counter. The months after the ones with 31 days can be identified using the above filters.