larryllix

I/O Linc modules have options that can be accessed from the device's status page in Admin Console. There you can set whether the sensor is hard connected to the output contact or not, as well, there are options to set the contact to momentary and/or continuous. as well as to initiate it on various logic triggers. Without looking closer at my own you may be able to set the momentary timeout to do what you want on a self trigger on only have ISY monitor the action. No scene required. Another possibility for more control would be to remove any scene you have created inside it and just use a program with the sensor as the trigger and the output as the light control. Expect a slight communication and ISY delay for the light though. Program examples can be supplied if needed. It seems fairly straightforward using that technique.

I have about 40 Insteon devices, no boosters, access points or repeaters. I don't seem to need any. I do have an old passive X10 phase coupler close to my distribution panel. I do get some slow Insteon communication occasionally on the next floor just above my PLM and my four solar inverters beside it.

How is the open/close module mounted and what does it detect?

2443 only results in a micromodule and not an Access Point. Is that some older number that has since disappeared? BoosterLincs appear to be X10 signal repeaters and may hurt your Insteon signals.

Maybe I am not reading the correctly but I see the OP wanting. On button = SceneX lights on A button = SceneA lights on Off button = SceneX (includes A lights too) off, **Button A LED off**= the request Could the A led not be included in SceneX as the kitchen lights are included in Scene X and the LED would also indicate as if A have been pushed on. Or....maybe the penny just dropped. Would button A not change it's toggled position thinking it is still on? I don't use the toggle mode on mine so I am not familiar with the fine details and I know you have lots of KPL polish (but in English:)). Mine just flash uncontrollably after I am done .

Only having limited experience with KPLs I am learning this one. I only use my KPL as a combination keypad for a notification system, restarting my well pump and washing machine after a leak.. Can the A LED not be included in the SceneX to turn it off along with other SceneX devices and vice versa?

That is exactly what my last program example does. IRule sets a variable, ISY uses it and sets it back to 0 after changing the fan speed.

No RPi needed. Just the Network Module for ISY is needed and use of lots of network resources or with the addition of non-cached variable substitution in Network Resources with ISY v5.x only one, or maybe a few, Network Resources. If you can tolerate a Wait 1 second between controlling each Hue bulb then this can be done with v4.3.18 and up with only a few network resources used.

I am not familiar with iRule. Can the programs not just control the variable? That way all the trigger and supervising programs work based on the variable value. That is the beauty of the event based ISY engine. Multiple programs can just stuff a value into the variable and the fan just shifts gears, seemingly by itself. Perhaps just duplicate the master control program with the iRule as a trigger? If iRule sets a variable then set it back to 0 after the $sFanspeed variable is changed. This could also be incorporated into the existing master control program with an "OR" condition. If ( Control KPL is switched on OR $s.iRule.variable > 0 ) AND $sFanSpeed <= 3 Then $sFanSpeed +=1 $sFanLinc init to $sFanSpeed $s.iRule.variable = 0 Else $sFanSpeed = 0 $sFanLinc init to $sFanSpeed $iRule.variable = 0 EDIT: Added s prefixes for state variable designation.

I was using cascading programs for everything but now I find the state variable triggering works very well. It's a little cryptic with unrelated programs running but that is classic for event based programming. The nice part is viewing the program tree in Admin Console shows the currently selected program automatically as green/true and the rest as red/false in a self managed case style switching arrangement. Now we need to add control from iRule (assuming some apple sauce here) to synchronise the variable from the other influence..

You're welcome. Scenes can work also, but only with one component device in each so there is no point.

I haven't done this yet as I have no fanlink and thinking about one doing the same with a simple SwitchLinc running the light and Fan. Define a state variable called something like $sFanSpeed Create a 4 programs. One for each fan speed with a condition like this. Don't forget to write one for Off=0 If $sFanSpeed is 1 <--- this changes for each speed 0,1,2,3 Then Set fanlinc to low speed <-----I don't know how the syntax for how this looks. Now set up a master control program that increments the variable $FanSpeed with a safety to reset it back to Off=0 If Control KPL is switched on AND $sFanSpeed <= 3 <-----top speed Then $sFanSpeed +=1 <---- go faster $sFanLinc init to $sFanSpeed Else $sFanSpeed = 0 <----turn Off $sFanLinc init to $sFanSpeed Hope this helps some. Let us know how this works out for you!

Sure. If you don't hardwire a load to a SwitchLinc it can't control it. The signal is still sent and Insteon listening devices like ISY994i can do whatever they want with it, even turn lights off from the On signal sent. I use one SwitchLinc dimmer a huge amount in my Great Room. I have some lights hardwired to it that turn off but a double down/off tap turns on another 11 coloured lights. I use Hue coloured lights as well as MiLight bulbs and RGBW strips and they are all controllable with the optional plug-in "Network Resources" module in the ISY. This is available right from a URL link inside your ISY and is just a click and payment away. And like Minute Rice (no association) Ready in five minutes. People here have also controlled their Sonos music system. Not sure how it is done but do some searches in the UDI forum.

I am just testing my washing machine here for water problems. After two spills this week that drained down a floor and triggered my leak detector I am real nervous about running the washing machine unwatched, nervously. Me thinks a large pan under the washer and laundry sink with a drain tube, leak sensor, On/Off module for the washer may be in order. I don't know where these large metal catch pans come from but the leak sensor is temporarily on the edge of the sink and the plug-in module is installed for the washer, so far. This to alleviate the immediate laundry sink overflow problem for now. A more permanent and coverall solution is being engineered. Are these large catch basins custom made? How large of a lip is recommended? Is a drain tube or some way to empty it needed? I assume the leak detector would have to mounted on a slight raised thickness or material to keep it off the metal. Anybody familiar with these things?

Awesome. It doesn't spec how much current for the PS. It may run right off the I/O Linc aux output at 5vdc. I would imagine the venturi action would need to be handled somehow. Possibly a small air scoop that could be rotated to calibrate??? @Xathros: Need to fill it plain water but a large sign over it about "Corrosive acid solution". Intruders have to wonder nervously as it follows them around pointing and the sign flashes.

No. Convenience and safety of my home mostly. When one switch turns on 30 different lights that I have no control over otherwise that is convenience. Really helps copensate for forgetfullness too. What was I saying now....?

Cool! You could also wrap the other conductor around the core in the reverse direction to get more turns, and eliminate the slack in the "spare' conductor. We used 3 wire CT's for metering that did exactly this. The two phases passing through were wound in opposite directions on one core with one secondary. The resultant is the sum/average of currents in the two legs. I would think without some iron, an air core CT would have enough uumph to operate a relay directly though. Probably the sensor input on an I/O Linc, for sure. As you mentioned with the right amount of turns. The other thing that tickles me a bit would be to bond a reed relay to the iron and hope that a small current would close the contacts and feed into an I/OLinc without out the secondary winding or the interfacing fuss.

Nice Are you effectively making an air-core current transformer? Is the I/O Linc sensitive enough to detect this? Will the AC signal not injure the sensor input? Are more components needed?

My dryer is a 120v gas dryer so it was a no-brainer. The clamp-on solution could work well if it is still available??? However, it cannot be clamped over the whole cable as there is no **net "differential current" in the cable unless there is a short inside that travels somewhere that isn't the cable. Not likely, with a ground conductor in the cable connected to the dryer shell, even with faulted wiring. ** The current going in must be equal to the current coming out, Kirchhoff's Law = zero. Only one conductor can be involved in the measurement for the clamp to work. https://en.wikipedia.org/wiki/Kirchhoff%27s_circuit_laws

Set jumper No.5 On (two pins) and the rest off (One pin). Now the MS can be totally set by ISY The option to time out is to save batteries. Turn it Off or your MS will be blind for a few minutes each time motion is detected. Put the MS into Linking mode ! Create a scene, give it a name, and drag your MS and SwitchLinc or LampLinc onto the scene making the MS the only controller to the scene. Take the MS out of Linking mode! Now the MS and the light controller are linked as if they were wired together with a cable. No ISY required. Use a program like this. MudRm Lights.auto - [iD 0067][Parent 0066] If 'Mudroom / Motion.MudRm' is switched On Then Wait 10 minutes Run Program 'MudRm Lights.auto' (Else Path) Else Set Scene 'Mudroom / Passthrough' Off Every time an On signal is received from the MS the timer is rest and starts over.

Years back we had continual problems with a tapchanger control relay always getting hit by lightning surges and burning out the input sensing transistors. I replace the darn things in the middle of the night too many times over 15 years and finally the utility I worked for contacted the defunct manufacturer of the equipment. He explained some things I didn't know before. He sent us a few home-made looking boards with a large MOV and a few paralleled disc capacitors in series with the MOVS. The explanation was that lightning disturbances consist of many short bursts of high frequency spikes that ring and fade away. Frequency ranges and very technical details were supplied which I confirmed with other sources available back in the 80s. If a MOV was connected in parallel across the sensing input, to protect it, in a transformer station environment, the MOVs usually take the lightning effect out and save the equipment, but the grid supplied power surges that follow the disturbance would cause the MOVs to explode, as they do sometimes. Adding disc capacitors in series with a MOV provides the same path to high frequency disturbances and yet presents a high impedance to the grid power frequency that was stated to cause the damage. In short, I installed these boards on the 14kV PT secondaries 1983ish? and the problem has never occurred until I retired in 2008. There was some interesting lessons I learned in that one.

Ferrorus hole = choke. Lots of inductance to MHz ringing found in lightning discharges. Edit:I guess counterEMF would be the effect that is the result of the inductance to a high-freq current attempting pass through. CounterEMF would be counter to the voltage and cause no current to pass.

My comments were exactly that, about how to use grounding effectively for Direct lightning strikes since you raised it. Even a #12 AWG is good enough for a lightning rod. It only has to carry milliamperes or maybe even microamperes. #6 AWG as ammonium spec in electrical safety codes is mostly about physical prowess of the conductor. We frequently had to stop the HV electricians from running ground wires down metal towers and passing through the iron structure holes in order to avoid drilling and using one hole clamps on the conductors. Lightning results in pulsating high frequency bursts that will not pass to ground through a ferrous hole no matter how big the copper conductor is. Hard concept to explain to a HV electrician and we took a lot of flack for it.

It should be noted that although a nice slow ramp rate for off is great but a slow on can be a PITA. The slow on can be beaten in a program by issuing a Fast On for MS usage

The protection againt direct lightning strike is attempt to distract it from your sensitive parts...(Ouch! ) and try to eliminate it from becoming so large (not your sensitive parts!) by bleeding the charge with a pointed and grounded lightning rod.