larryllix

I have come to this conclusion several times in my ISY career. Later I always find something that I messed up. You sound very frustrated and it becomes hard to keep focused on a fix at times when this happens. One of the most common problems that happens is programs creating oscillating loops that can tie ISY up in a program loop as fast as it can go. People here will help you to resolve this as I can assure this is not typical of ISY. If this was happening to everybody with an ISY I would be here and would still own a Hub and HomeSeer 2/3. Can you view your programs on the program tree and watch icons for changing colours quickly? Do you know how to view your logs, and error logs, and/or post them here? Do you know how to record an event log using level 3 so that people can analyse it to start you on the road to recovery?

Low temperature detector in the house to detect ALL heating failures?

Let us know when it works! Then I can sleep again wondering if I missed something.

This should agree with LeeG's description in post #9. There really are no 3 wire switches or wiring in Insteon. Just parallel operation OR logic. One switch does all the work and another, unrelated one, has remote control.

OK. In the 4 gang box - SwitchLinc black to the black bundle - SwitchLinc white to the white bundle - 3w/black wire to the black bundle - 3w/white wire to the white bundle - 3w/red capped off = n/c - SwitchLinc red to the 2w/black wire - 2w/white already in white bundle In the remote switch box - SwitchLinc Black to the 3w/black - SwitchLinc/white to the 3w/white - SwitchLinc/red capped = n/c - 3w/red capped = n/c The rest is done in ISY. Don't forget the Factory Reset both SwitchLincs before ISY involvement.

This is what I think I am hearing. Branch offs from the white bundle and black bundle are not mentioned in the wiring chart. 4 Gang Fixture Remote Sw. ---------------- ------------ -------------- feed/Bk - Sw/B feed/W - 2w/W 2w/W - lamp/W Sw/S - 3w/Bk 3w/Bk - Sw/S Sw/S - 3w/W 3w/W - Sw/S 3w/R - 2w/Bk 2w/Bk - lamp/Bk 3w/R - Sw/Bk

What type of thermostat do you have?

The positioning of the MS is more important. I use MSes in all bedrooms mounted over the head of the beds about face height if you stand on the bed mattress. You can kick your feet into the air to get a light on, or stand up but rolling very seldom activates it. I also use scenes and dim the response of the bulb in the sleep hours to about 15% (100W equiv LED) so it doesn't blind anybody. I also use ramp speeds about 2.0-4.5 seconds for night responses. I use manual override programs from miniRemotes and wall SwitchLincs to lock the light on 100% when needed. An all-else-fails-I-forgot timer in the program restores automatic operation as well as a manual override Off click. I don't need to use any variables for these programs. Times frames are used by other dedicated programs that just change scene levels. These can be combined but I find each bedroom has it's own schedule requirements. Time delays are not noticeable using this technique.

Elk is non-Insteon, hardwired control system, that communicates with ISY. It is felt that ISY does not issue an Insteon All-On signal but rather two signals get bit-confused and devices only interpret it that way. This would be an Insteon thing only.

Android MobiLinc needs to have a new image captured from ISY in Setup|Light Controller when a new device is added.

Hope that's it!

Second that! Best prices found anywhere, after shipping to Canada, too.

Thanks. What I wanted to know was why ISY has this in it's setup options if it is just a scene setup and sounds like it doesn't connect ISY into the loop.

Thanks stu. If I read that correctly, this is a scene setup from ISY without ISY involvement in the links.

I saw this grouping with my KPL also. What was the intention of this feature?

Good point! Don't give them any ammunition to blame a problem on something in your side of the court. It gives them an opportunity to walk away until you do something and then you are on the hook. Keep the ball on their side of the court.

Not likely Insteon RF signals would affect the millivolt wiring in a furnace otherwise every cell phone, radio station, and WiFi router signal would disrupt it also. The powerline communications are done .across the live to neutral on the household grid and should be received everywhere in the house. The power supply inside the furnace is usually and mostly 24vac to run coil based relays. Any sensitive electronic circuits have filtered power supplies that should remove any minute signals from the smoothed dc power. Having said that nothing is concrete but signals bothering another piece of equipment indicates a poorly designed, or defective piece of equipment. If the minute Insteon signals bother other equipment they have no business being in a household environment out in the real world.

Read my edit. I missed your latest.

Put your time frame condition and Then in an isolated program that is disabled. Call it from the power level condition enabled. Now the timer will always finish. It's that inverted mountain air

When the power changes by a Watt the condition should be re-evaluated and if it is over your setting AND between your times True gets run again and the timer gets restarted. Now if this happens and the wait is anxiously waiting to turn off the fan and the time frame runs out, or the power drops below your condition, guess what? No turn off.

Any analogue conditions I have used will retriever the logic evaluation again even though the result doesn't change. I'm afraid LeeG is correct.

I think it was mentioned once-upon-a-time that the CPU was 0.6-0.8 GHz . In a previous life, I ran an X10 system that had as many devices and even had triggers based on an every second clock. It never experienced any slow downs from a CPU bound system that I could detect.. This system ran on a super-duper 40 MHz (yes. 0.04 GHz !) AMD CPU. I don't think being CPU bound is a problem for the ISY system. Insteon comm congestion can tie the system up, slightly. X10 coming and going out of the same PLM as Insteon, much more. I tried to measure the speed at which ISY processed lines of code once, but failed, as routines run simultaneously on it's multitasking system and it's hard to nail down. Anybody else manage to create a speed test program for ISY994i? Want to?

I wouldn't be sure SmartyPants can lower their prices much and stay in business with the new big-name competitors coming on the scene (pun intended) from everywhere in droves. They are priced about the same as everybody else. What surprises me in light f the same fact (above) that SmartyPants hasn't had a big sale or price drop, at least temporarily drop prices to hook a future captive audience to their product line. In other forums I constantly hear the single supplier argument and I believe it takes it's toll on their share of the market just as it drove Apple into the ground for so many decade of floundering. If the Insteon product line had a huge advantage above other protocols it may rise to the top but it doesn't. The watching future market doesn't see any advantage to Insteon at all and until you have some experience with it you aren't going to know any difference except for the big-name behind other products. Who is SmartyPants anyway?

I believe you should be able to drag all those devices into a scene with the settings you want and include the KPL LED as another item and now when you turn the scene on and off the LED just follows, as if by magic. For bed time scenes, the long ramp off is nice to not jar the senses but not really wanted for other times when fast on lights may suit better. These techniques make your program code much simpler to use and easy to read. Another advantage of using non-toggle modes and only having the On command sent is you can easily set up a second scene for the second tap of the same button. GathRm Mode.Reading/TV.select - [iD 00B1][Parent 0004] If Control (Old) 'Gathering Room / PotLights over Chairs' is switched On Then Run Program 'GathRm Mode.Reading/TV.toggle' (If) GathRm Mode.Reading/TV.toggle - [iD 0030][Parent 0004][Not Enabled] If $sGathRm.Mode is $cMODE.TV Then $sGathRm.Mode = -1 $sGathRm.Mode = $cMODE.READING Else $sGathRm.Mode = -1 $sGathRm.Mode = $cMODE.TV Must be disabled due to trigger variable being State type.

I would never listen to my father, either.