larryllix

Well If I knew exactly what I was doing and had worked it out to always work, maybe I could instruct you to be able to do it yourself. Having said all that, I can't. It would still be in the experimental stage for a boy that's been doing this kind of thing for many decades. At this point, usually somebody with different angle of experience pops in and says....why don't you just use this gadget? ...and that is what the forum is all about.

My guess it that these sensors just trigger a 12 vdc signal at the GDO that could take a sensitive realy to isolate and interface to a I/OLinc input. Some electronics knowledge would be necessary to do the measurements and trial and error necessary to make this work. A solid state opto-isolator type or even a diode, capacitor and a few voltage dropping resistors could make it work but polarities and more expertise would be necessary. An open collector buffer transistor may work better yet. I am looking to do the same thing on my furnace fan with 6-7 input speed controls at 24vac each going into an I/OLinc sensing.

Remove the LED from all other scenes and create a new scene for each LED. Drop the KPL LED into the scene and adjust to 'ON. (Scene On = LED On) This program is about as simple as ISY gets. This gives a 1 second delay to avoid Insteon traffic collisions but on an LED indication response it shouldn't matter. This does not change any other ISY logic that controls the door, just the LED indication Note: My contact is closed when the door is closed. Either contact can work with the 'reverse' option. Garage Door Open.LED - [iD 0097][Parent 0109] If 'Garage / Garage Door.closed' Status is Off <----I changed from 'On' to get status Off = door open = LED On Then Wait 1 second Set Scene 'Mudroom / MudRm kpl.LED.a' On Else Wait 1 second Set Scene 'Mudroom / MudRm kpl.LED.a' Off

I would just switch the scene command in the program lines to reverse the LED indication. Contacts do NOT need to be changed or switched from NO/NC. A better contact is not going to change the look of your LED. This is what having a PLC HA = ISY is all about... not having to change hardware. Coincidentally I just did this for my garage door last night. It took about 15 seconds after seeing the LED results and I decided the same thing. I want the LED to look like an unusual/alarm situation when it is On. Paul has a point about scenes vs. programs and that takes a certain type of contact but if your LED doesn't work while you are away will you notice? Don't use the "reverse" option in the ISY option box. It will cause you troubles, as mentioned above by others. To do this you need to remove the LEDs from the I/OLink scenes and create a new and separate scene for each LED. Then you need to write a program for each LED to operate that scene. If Garage door is open Then set LED scene On Else set LED scene Off

"...only pennies per day", has added up, through my lifetime, to be almost $100K per year. Most of us want ..finite and absolute... and "cloud' is becoming a dirty word, a way to disguise taking money from our wallets, a little at a time by dazzling our eyes with technology we haven't seen before.. Doesn't "cloud" suggest "confusion", "haze", "can't see", "unresolved", "unknown"? Probably a really bad nickname for something we are not what to call it in a "one-size-fits-all" naming attempt. Clouds blow away and the sky may eventually become blue and clear..

Your Elk zone is probably timing out, sending an Off to ISY. Your pogram sees the Off and runs the Else section, stopping the Then section from finishing Either make a disabled program and call it from the first one, shorten your Wait 10 minutes, or lengthen your MS time off delay so it survives the Wait 10 minutes timer. If From 9:00:00PM To Sunrise (next day) <----these two lines can cause Else to run and Then to stop And Elk Zone 'Upstairs MS' is Violated <---- Then Run Program2 Else ---- Program 2 (disabled) If -- Then In Scene 'Stairs Light' Set 'Stairs Light - Top of Stairs' 35% (On Level) Wait 10 minutes Set Scene 'Stairs Light' Off Else - No Actions - (To add one, press 'Action')

If you are referring to the Amin Console and you have your full colour option on for the icons, you will see a solid green icon when the program runs, and a partial green icon once the program is done running. Your program would run so fast that you would not likely ever see the solid colour. The green colour is a remnant that will stay to indicate your program last ran True = Then section. This is normal behaviour. You could add a wait 5 seconds fr testing so you can see the different states.

Ditto what Techman reported. Also there are many temperatures sensors CAO Tags are very accurate but cloud dependant to report. Autelis with 1 wire sensors for totally LAN CAI WC8 with 1-wire sensors for totally LAN. Several Venstar, Honeywell, ecobee3 with NodeLink running on an RPi but the Venstar is the only one not cloud dependant and they all take AC power. I use 2441ZTH stats for probes and one for anti-freeze heater in my utility room.

Is this the box you are talking about? also... If so, do you have an IP address installed in the list as shown in the screen shot?

What does ISY Finder say?

When the ISY Finder comes up, click "Add" and put in your ISY URL like http:///192.168.x.xxx. If you only make one entry it will boot up the admin console automatically. If you have more than one you may have to double click on the desired URL each time.

The linking button is to manually create links between devices as per SH instructions. Only battery devices need to be put into linking mode with ISY.

Any contact will work just fine with the right program logic but the "Reverse" option will cause you troubles when the 3:00 AM query reports the status "unreversed". The I/O linc needs to be enabled, to work, and your programs need to be straightened out.

If you are electronically oriented there are many things you could try to alleviate the sensitivity problems. These are typically components that a more responsible company would have installed after trial and error. MOVs, inductors / toroids and a few other small components are the usual components used. Sometimes PCBs will be found with empty solder pads for these components where the newbie engineer showed the old dogs how much cheaper the product can be made, with a pair of side cutters. "When it stops working, put that part back in, whatever it does, and then try another one."

I thought you may be a little new and this whole Insteon thing is a bit confusing at first. I never use Fade Up/Down. If you want your lights to go on to a certain level, specify it in your program. If you want your lights to ramp up or down slowly , find them in the device webpage in the Admin Console and set the speed with the Ramp setting. Ramp speeds are 0.1? seconds to 8 minutes. Nine is now not available. Experiment with some settings and operate them manually from the device page. You can't hurt anything.

Set absolute values. If you want a ramp speed you can set that in a scene containing those lamps, or set it with the admin console device page for the local and ISY control levels. Modify your program and then save. Right click on it and select "run Then" to try it anytime. BTW: I have never used a Fade Up. IIRC it only sends a very small increase in level. May not work if lights are not already on. Too finnicky. Scenes are like prestes on your car radio. You set them up with a level, ramp speed and other variables and ISY assigns everybody involved a "secret scene number". When you turn that scene on from ISY, ISY sends out that "secret scene number" and everybody deoes what you prearranged.

We were always prohibited from even owning any single touch testers. All voltage indicators, testers, and meters, had to have two leads to connect across the "potential difference ...and they had to be tested on a live source before trusting, each occasion.

The main issue is not to use the reversal" option in the IOLinc setup in ISY. Mine shows On, when the garage door is closed, works just fine, labelled as GarageDoor.closed so that it is true logic, and never gives false indication from the 4:00 AM Query. Whether you have On or Off with the garage door closed makes no difference, just write your software to work with no reversal option turned on, and label your device point to the proper logic.

Excellent. From your drawings, you were almost there anyway.

Typically it is not ISY program execution or logic processing that slows things down. Years back I ran a similar system for X10 HA on a 40 MHz 80486 CPU and never saw any problems with loops or CPU bogging down. It was busy as it had an every second trigger that many programs used to do counting timers etc. Now ISY comes along with a somewhere between a 600- 900 MHz (15 - 25 times) CPU and I am sure it doesn't sport an 8 bit bus either. The slow down is the Insteon protocol. While it is much faster than X10 and many others the time lags do add up. When ISY sends out a command the targeted device has to acknowledge the command or ISY will send it again (Retry) Before the targeted device can acknowledge it must wait for all devices to finish repeating the command with up to four hops and original send times. Now the Acknowledge goes through the same process with up to four hops before anybody is allowed to talk again without signal collisions. This all adds up to not too many commands, echoes, and acknowledges, with their hops/echoes per second. The trick is to use scenes where only one command gets sent out and everybody involved does their thing at the same time. One other trick is to space out your device commands with wait lines in your programs. I use an ALL OFF scene and also an All OFF program with waits between 40-50 devices. They both have their uses.

OK...think I have the picture. Both SwitchLincs need power. Box 1 - connect the black wire to the others in the connector, leave the black/3wire connected there, as is Box 2 - connect black wire to black/3wire Both SwitchLincs need neutral Box 1 - connect white to white/connector bundle with white/2wire to load and white/3wire to box 2 Box 2 - connect white to white/3wire One SwitchLinc has a load Box 1 - connect red to black/2wire to lamp Box 2 - red gets capped. Spare wires Box 1 - red/3wire gets capped Box 2 - red/3wire gets capped As a check, in the end all blacks/SwitchLincs connect to black, whites/SwitcLinc to white, Red/SwitchLinc 1 to black/2wire going to load and both red/3wire capped both ends.

You need two SwitchLinc switches to make this work. and in box 1 the second cable from the left is not clear where the black, in the 3wire going to box 2, is going. The photo is focused on the twist connectors, in the air, and it is hard to be sure where things are going, since we need that black conductor from that cable. Also the third and fourth cables may be involved and need to be clearer.

It appears they are designed to do just what you are doing with them. This is a different situation than most power supplies.

Not the program. Switching power supplies do not like their inputs to have a chopped up waveform, as a SwitchLinc dimmer puts out. The inputs capacitors and circuitry would not be expected to last long. It may injure the SwitchLinc also. A regulated power supply for the LEDS major job is to regulate the output voltage even if the input varies. Varying the input voltage to it should not vary the LED strip brightness right up until the power output fails. If you leave the SwitchLinc dimmer on 100% all the time and vary the LED controller it may work OK but the SwitchLinc is a waste. Perhaps your power supply is not a regulated type?

I hope you are not running a switched power supply, with it's only job to maintain a constant voltage, off a SwitchLinc Dimmer. If so you may have burnt out one of the two parts.