larryllix

One of the logistic problems with most of these ideas is that you still need a 120vac receptacle to mount and run an I/OLinc module. This means some kind of wiring box to hold an overcurrent device, a receptacle and connections to hack into your 240vac dryer plug cord anyway. I suppose a small signal cable could be run from the sensing device around the room to the I/OLinc plugged into the nearest 120vac receptacle.

That means opening your appliance and mounting and wiring a relay inside the dryer. most aren't going to do that, may not want to, or are not capable of doing that.. You would require a fused circuit to protect the I/OLinc reducing the overcurrent protection to 15A or less. It will be a bit technical in view of no Insteon product for this application though.

Yes. I am already using one but just brainstorming for people that use 240v dryers. There should be a fairly easy way for others.

May be a problem a gas dryer but... How about detecting the position of a damper totally inside the building inside the non-ferrous vent pipe with a vein switch of some design. Would have to lift the magnet or rotating one on the axle outside the pipe may take less torque.

hmmmm. many reed switches will take AC but if it is "sensitised" with a permanent magnet this may be a problem and the bridge would be needed. This precludes cutting into the conductors and then a small step up voltage or step down current transformer might be needed to get over the double diode voltage drops and then another coil for the reed switch.

I had a thought about this today. I wonder if a few turns of one leg or both legs, opposite wound around a garage door sensor into an I/OLinc would work If they can detect a magnet within 2" it may be sensitive enough for the current to closed the contacts.

One If section per program. Your program can call another program and do another "If". Disbale this program if triggers are not wanted to interfere with the logic. I never use Fade Up/Down or Fade Stop. Holding the paddle Up or Down for longer than a tap sends a Dim/Brighten command that I trap for setting scenes.

The groupings are tricky for these multiple Then and Else invocations conditions. Negative conditions require ANDs for the logic to be treated as a group negative of (positive ORs). DeMorgans theorem. ie. not(D or E or F) = (not D) and (not E) and (not F).... substitute 'and' for 'not(or)' Kitchen Cabinet Motion Override - [ID 0016][Parent 001A] If ( Control 'Kitchen / Kitchen Cabinets' is switched On Or Control 'Kitchen / Kitchen Cabinets' is switched Fast On Or Control 'Kitchen / Kitchen Cabinets' is switched Fade Up Or Control 'Kitchen / Kitchen Cabinets' is switched Fade Down Or Control 'Kitchen / Kitchen Cabinets' is switched Bright Or Control 'Kitchen / Kitchen Cabinets' is switched Dim ) AND Control 'Kitchen / Kitchen Cabinets' is not switched Off AND Control 'Kitchen / Kitchen Cabinets' is not switched Fast Off AND Control 'Kitchen / Kitchen Cabinets' is not switched Fade Stop Then Disable Program 'Kitchen Cabinet Motion' Else Wait 45 seconds Enable Program 'Kitchen Cabinet Motion'

I am not exactly sure how you want the two logics to combine. These lines of code may be able to be added in to your existing programs as they are later events than your code executes for. If From 9:15:01PM To Sunrise + 15 minutes (next day) And ( Control 'Sliding Door Open' is switched On And Control 'Sliding Door Open' is NOT switched Off ) Then Wait 10 minutes Enable program 'screen door only' Wait 10 minutes Disable program 'screen door only' Else - No Actions - (To add one, press 'Action') Program 'screen door only' (disabled) If Control 'Sliding Door Open' is switched Off Then Set Lights Off, dog is in, etc. Disable program 'screen door only'

Should be fine as it works going forward on firmware. Select | File | ISY Restore | browse for your file. Might be a good idea to do a backup first and save the mess, just I case anyway.

This has been raised many times and I believe this is on UDI's list of things to install.

Ask when you are ready. The response is fast, dimming levels are variable if set ahead of usage, and manual override works with a failsafe timer, for that "I thought it was auto" assumption that happens.

Thanks I assume a DON 1/2 would be a wet/dry signal. What would a DON 4 be? Perhaps a heartbeat? Maybe I got fooled. Did you try the short and long press. I found anything longer than about 1/2 second a long press. Edit: I saw your LeeG response above.

Just receiving two new Leak sensors and having two previous I have found they operate quite differently. On the two newer units (v.41) the pushbutton sends out Dry On, every time. On the two older units (v.43) the pushbutton sends out Wet On for a quick tap each time and Dry On for a longer push each time.

Here is a series of programs I use that do it all. I use a timer override for manual On/Off just in case you forget the automatic lights are locked on in manual. http://forum.universal-devices.com/topic/16694-50-latency-question/

With most of my auto lights I just let them turn on during the day. It may a dark area and I can't be bothered to inflict a third brightness level program switch. With LED bulbs running all day would not be a financial hardship and pointless for energy saving. I just want my 100w equiv. beside my bed dimmed in the middle of the night .

I link all my MSes to the lights for faster response. This requires different methods to control all the aspects of dimming and manual override..

Very Odd. Did you measure the output of the NPN transistor? Silicon transistor open collector can pull down to almost 0 volts. This was a hard concept for many to swallow when the base to emitter voltage is pegged at aprox 0.7v. Perhaps a darlington pair output.

I am glad this resulted in a solution for you. Agreed the I/OLinc is a bit screwy and if Insteon does change this setup I am sure nobody will find out until it doesn't work that way anymore. I am a little sore right now as I just received two new DampLincs = leak sensors and on the two new units the linking button sends Dry signals whereas my older two units send Wet signals sending my wife notifications about leaks while she was away. I was testing with the two new units and it seemed safe to continue on the old units. She is very sensitive to this right now, after two washing machine spills last week, and started shopping for a newer and improved mop.

This sounds like a call to UDI Tech support.

That usually indicates your Java cache needs to be cleared of duplicate files. Use the Control panel, Java and make sure you select all options before delete.

MS units work fine in scenes with lighting modules. As above, the Off has to be disabled from the MS then ISY can control that. Response is immediate. There is a way to control dimming also on a preset the scene basis.

No. However I have tried linking two I/OLincs into a scene successfully. I used my doorbell pushbutton detector as an controller and my BuzzLinc as a responder and tested just fine. The problem, as mentioned by LeeG is that the responder cannot be an extended time and the contact opens as soon as the PB is released. The scene is also not retriggerable to extend the time on as long as triggers keep happening. While scenes are fast with direct links between devices, control and logic is lost. No timing can be created and this is why most of us disable the Off signal from MS units, so that ISY can control the time off time.

Yes, but too late tonight to get one down for linking. The I/OLinc output dropped into the scene no problem but the sensor wouldn't. I assume this is because it has internal linking, same as any other module. Perhaps duplexing it was an afterthought?

Yeah but which one of you is correct? I attempted to create a scene with the input and output of the I/O Linc but something doesn't allow it. Funny ISY thinks it has all the statuses and responds as if it works with On/On for In/Out but it isn't happenning. Next I went to a standard light program with time off and yes, it is way too slow. It seemed the I/O Linc is slower than other controllers. Maybe only a visual effect as I can see exactly when I short the wires to cause an input. contact closure. I/O Linc is not going to work for both input and output with a decent speed. Input needs to be something different (MS or On/Of as was) with a direct linked scene and ISY time off, or output needs to be something different with a directlinked scene between devices.