larryllix

OK this is what I would try. It may not work for you. Disconnect the pushbutton from all else. Wire it to the I/OLink from Gnd to Sense. No other wires in these terminals. You may want to test this to ISY or to the LEDs on the side first before proceeding. The low voltage from the I/OLinc may make a flakey PB operation. Wire transformer to I/OLinc COM. Other end of transformer to Chime. Other side of Chime to I/OLinc NO. Set options on I/OLinc to Latching Continuous. Relay Follows Input = NO Use Amin Console to test the output manually testing if the doorbell rings from device controls on ISY, Be careful not to leave the Chime on too long and heat up doorbell. Test pushbutton to see if status changes on ISY device input page. Write a program like this If control I/OLinc.input is 'On' AND variable BabySleeping is Not 1 <----add this if basic program and connections work. Then Set I/OLinc.output 'On' Wait 1 second Set I/OLinc.output 'Off; Now your ISY knows about the doorbell button pushed and can decide whether to echo the command to the chime. If I am in ISY vacation mode I send myself and wife notifications that somebody rang our doorbell. Being rural this isn't too often. Note the options allow the I/OLinc to be combined or split into two distinct parts, input and output but I cannot see any way to control this from ISY. Talk to Michel about adding this option to the language later as an improvement. Maybe I am just missing the method. This would speed up your chime response time.

Can the ISY inject the doorbell status into the Elk instead? I believe the I/OLinc can be programmed to control and link the output contacts directly from the input or separate them. If this can be done on-the-fly from ISY programs the I/OLink would be all you need except for the 5 volt sensing input and the 24vac doorbell transformer. If you don't have a pushbutton light you could possibly eliminate the transformer and just tie the pushbutton across the input I/OLinc sensing. Barring that you would require a 24vac relay to isolate the circuit voltages. That's the way I did it. I left the circuit the way it existed and tied the relay across the doorbell and the I/OLink sensing the relay contacts. My I/OLink output rings the back doorbell sound and we use it to indicate the dryer is finished since we have no backdoor button.

At 20k only one resistor should be plenty. Power = E2 / R = 242 / 20k = 0.03 Watts. Not even going to warm but wil not be enough current to trigger the Elk series detection. Current = E /R = 24 / 20k = 1.2mAmps. Not gonna' trigger the Elk sensing. Brian stated this current from the spec as 900mA minimum and this would take R = E / I = 24vac / 900mA = 26.67 ohms or less at 24vac transformer. At 16vac, less resistance. I find it hard to believe any electronic doorbell would draw this kind of power. A mechanical doorbell might draw that heavy but I have never measured mine and they do put out a few watts of sound power. Strange input sensing.

Some analysis really needs to be done to determine where the disturbance came into the house and where it went out. Surge protectors cannot typically protect against surges. All sounds like terminology but most are just spike clippers and mislabelled. It is not likely you could protect your self from surge on the grid without tens of thousands of dollars worth of isolation transformers and UPS equipment. However you can stop some of the high voltage glitches that typically don't come in on the grid supply. They come in as differences of potential across different sources eg. Phone cable to grid, cable TV to phone cable, TV antenna to ground. Your PLM is hooked between one circuit on your electrical distribution panel to your ISY to possibly another distribution panel circuit and to your LAN to your router on another. This suggests it may have come in on your ISP signal source and out the electrical grid or vice versa. Good grounding techniques in the house can alleviate these problems somewhat if it isn't a major disturbance. If you are not electrically based with experience you probably should get somebody that works in the field to looks at what happened and suggest remedies. You may have a badly bonded neutral, poor house ground , a TV antenna that is not protected and brings in the lightning shocks, etc. and may be easy to solve. The trouble with all this is it is still "best shot". An educated expert takes their best shot and you will never know if it worked until it never happens again. You can wait forever unfortunately. If breakers are tripping during storms then you have a larger problem that needs to be solved first with possibly your grid input to your house. call your utility and tell them what happened and try to get them out to check your street transformer grounding. You may need an electrician to check/prove your grounding for your service. You must also have some bad wiring before or after the breaker trips where the lightning spikes were/are leaking/breaking through your wiring insulation now. These circuit need to be scrutinised visually and/or with equipment to test for leakage. (Meggar is the brand name term classically used) You may have hidden damage to wiring. All the best. It can be a tough one.

That is the changes I suggested except I would draw source to load left to right Your resistors don't show any resistance value. Depending on value they may be a problem burning out your transformer, I/O Linc or themselves (not likely). 5w20kj is not a resistance value but rather power ratings.

I think of the Wait and Repeat this way....an analogy. Once the "Then" or "Else" program section is given the microphone it gets to talk, exclusively, without interruption (finish it's program section) from the audience (programs). A Wait or Repeat instruction is like voluntarily giving the microphone (CPU) back to the emCee (ISY) until the Wait time period is over. The emcee (ISY) checks the rest of the audience (programs) to see if somebody else wants to take the microphone (other program triggers). The emCee (ISY) respects the Wait time specified and attempts to give the microphone back to the original speaker (program) when the specified Wait time is over. All speakers are fast talkers (code is quick) and do not run-off at the mouth, interfering with other's rights to talk (run their programs) much. Speakers are picked (ISY real-time engine) in no particular order and not by age, name, or gender. Sometimes speakers send the Paige (PLM) out on an errand (Insteon comms) and other speakers (programs) have to, not only wait their turn (time slice), but also for the Paige (PLM) to get back before they can use his service (Insteon comms).

OK I'll have a try at this. I don't know what your Elk connections are and I can't read the terminals but... I assume the Elk is a series connected current sensing input? In addition the Brian's correction above, 1. reconnect resistor green wire to the doorbell white/white wire going to Elk (parallel) 2. reconnect doorbell button red/black wire to I/OLink com terminal(swap with #3) 3. reconnect Chime red/black wire to I/OLink NC terminal (swap with #2) Note: The resistors should be connected across the Chime at both ends except for the contact which will switch the one connection end of each between Chime and resistor bank. I don't see any resistance indicted on the pic or in text to know what kind of current will be drawn.

There are two ways scenes are done and this terminology is always confusing. You can create a scene inside ISY, writing it into the devices with no controller so that only ISY can trigger it. In this case where ISY is the only controlling entity you can adjust the levels within the scene with this method. Note the scene name is MBR Passthrough and I am adjusting the device included in the scene that only ISY controls. MBR Lamp Level adjust2 - [iD 009A][Parent 000A] If From 10:30:00PM To 9:30:00AM (next day) Then In Scene 'Master Bedroom / MBR Passtrough' Set 'Master Bedroom / MBR Wall Lamp' 15% (On Level) Else In Scene 'Master Bedroom / MBR Passtrough' Set 'Master Bedroom / MBR Wall Lamp' 70% (On Level) -------------------------------------------- or You can create a scene inside ISY downloading it into the devices (or manually link the devices without ISY ) with a controlling unit so that ISY can trigger it or the controlling device can trigger it directly not even requiring ISY to be active. In this style of scene adjusting it inside ISY will not affect the directly linked scene between the controlling device and the responding devices. It is a different scene. This method is very desirable as the respond time is almost immediate and delays are almost not discernable. Note: Motion.MBR is NOT a scene but it is still found in the scene pulldown list. Motion.MBR is a device that is controlling the scene. Real time logic cannot affect this type of scene but ISY can change some parameters, previous to the scene being triggered, using this technique. MBR Lamp Level adjust - [iD 0084][Parent 000A] If From 10:30:00PM To 9:30:00AM (next day) Then In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 15% (On Level) <---no scene name used. Else In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 70% (On Level) <--no scene name used

Most likely only the Pro version of ISY

My HD had the 25watt and 40watt equiv in the old style but all the 60W were the new vented units, thus the odd style for one bulb in a group of six. Tried three stores for the older 60W style but no find. In Canada, here, we have no CRI >90 bulbs in Cree yet. The old stock has to move first and they are pushing the Philips flat weird junk first. I checked in Florida and Buffalo in January and they had no >90 CRI either.

I attempted the new receipt trick at The Borg (HD) but the Cree bulbs have all changed styles as they constantly find ways to improve and make them cheaper. I couldn't find the last style Cree manufactured. I took the bulb back into the customer desk in a different city, just incase they said "No" and I was marked for future. The Borg is the only store that handles Cree here anyway. I was ready for the fight. I had no receipt and the woman admitted that they had no defective bulb policy or process set up, did the shifty eye thing, and told me to just take the replacement unit and go. The new 60W equiv. has vents in the bulb and much larger size and also doesn't dim with the same curve as the other five in the chandelier. Great! Now we have LED bulbs that will fill up with dust on internal parts with no access to wipe clean.

The LED strips I was referring to were these ones. There are no puck lights. http://stores.ebay.com/dealdelight-store/3528-SMD-LED-Strip-/_i.html?_fsub=4530091016 The bulbs in two brands were also mentioned for comparison. I understood you wanted colour capability also. I now understand you only want single colour 5000K white. My mistake. I have only heard of LED strips that can produce warm while and cool white at 3000K and 6500-8000K. The 5000K sounds like a nice colour for a work surface if you can find one.. Here is a 6000-6500K strip. These things are plenty bright with the 120 LEDs per metre making 24w per the 5m strip. http://www.ebay.com/itm/Hot-Sale-5M-3528-SMD-600-Leds-White-Color-Flexible-Strip-Light-IP65-Waterproof-/281173373025?hash=item41773d3061

A phototransistor should work better. Lights acts as an input to the base of the transistor and they switch cleaner with the amplification of the transistor.

Forget the sticky backing. You need the silicone clamps. Once the LEDs are on for 30 minutes they fall off when the sticky backing get warm. RGB LED strips do not produce white light period and not bright enough to do counter work. The LED strips I have are RGNW and the white is almost useless as it is so purple you can't call it white. The latest LED strips I got are RGBWW and they produce a beautiful white and very bright. The MiLight controller with RGBW or RGBWW strips and bulbs produce identical colours for the same codes except the white as noted above. MiLight / LimitlessLED controllers cannot produce white and RGB colours at the same time. The LED strips can produce all colours with beautiful depth and richness but Hue bulbs are lacking green and blue capability. However Hue bulbs fade slowly and can produce pastels colours whereas MiLight controllers can't. They all take a bridge/hub to convert Ethernet to proprietary2.4GHz RF. MiLight hub is WiFi input and Hue is Hardwired Ethernet. LED strips take a controller wired to a 5 pin socket to connect to pre-terminated RGBW strips. A connector is provided at each end of the 5m strips so you can cut them at 122 cut spots and use them as two prewired pieces. 12v 3-5amp power supplies are required with the 2. x 5.5mm plug on the end or two wires for the terminals, your choice for each section. The ISY Network Module can control the Hubs for either Hue or MiLight hubs easily. MiLight Hubs can only handle four groups with as many controllers as desired in each group. Al bulbs and/or strips within a group will all respond to the same color and brightness. I use two MiLight Hubs for 8 groups with 9 sections. One shares two lamps. I ran out of hubs and don't want more.. Hope that helps some of the purchase confusion.

...and the ramp rate of every dimmable device for each scene so that different breeds of lights can look like all dimming or brightening together. Nice to have slow offs and fast ons for MS applications etc.. etc..

If you referring to my calculations the pullup resistor was calculated to be 3200 ohms and used to calculate that as parallel resistor isn't going to work. A parallel resistor can pull the input down to 0.7 volts but the sensor becomes so insignificant in the circuit that the voltage can never return high enough to switch to he logic high state again with sensor at infinity ohms.

If you used 800 ohms to pull it down to 1v and the supply is 5v then the pullup current is E/R = 1v / 800 = 1.25mA Assuming the pullup source is not a constant current and is just a resistor E/I = 4v / 1.25mA = 3.2k ohms. Now with your sensor in series with the calculated pullup resistor with we have 2.25v therefore the current in the circuit is E / R = (5-2.25)v / 3200 ohms = 0.859mA and your sensor is running at 2.25v / 0.859mA = 2618 ohms To make this sensor pull the voltage down to 0.7 volts we require a circuit with a resistance ratio of 0.7 / 5.0v To get this the current in the pullup (3200 ohm) would be E/R = (5-0.7)v / 3200 = 1.344mA and the resistance of the sensor in parallel with a resistor would be E/I = 0.7v / 1.344mA = 521 ohms Since we have a sensor with (calc) 2618 ohms we need a parallel resistor of 1/Rp = 1/Rt - 1/Rs = 1/521 - 1/2618 = 1/650 Our parallel resistor would have to be 650 ohms. Checking our sensor 'Off' voltage and assuming infinity resistance when dark we have a voltage divider using the 3200 ohm pullup and only the 650 ohm parallel resistance we would have a voltage of 5v x 650 / (3200 + 650) ohm = 0.844 volts. = not enough to switch the I/O Link . A parallel resistance isn't going to work! Need a transistor or a phototransistor with a better curve. E and O.E

Again. To put the MS in linking mode press and hold the button until the red LED starts flashing slowly. Do not press it again until done. I see no off timer or sequence to turn the light off and you have a few redundant lines. Big Bathroom Sensor On - [iD 0016][Parent 0017] If Control 'Bathroom Big-Sensor' is switched On And Control 'Bathroom Big-Sensor' is not switched Off <-------this line runs else. else is empty Then Enable Program 'Big Bathroom Sensor 2 Off' Set Scene 'Live - Key H' Off Wait 15 minutes Set 'Bathroom Big Micro Dim' Off <------------if all else fails turn it off anyway Else - No Actions - (To add one, press 'Action') Big Bathroom Sensor 2 Off - [iD 0019][Parent 0017][Not Enabled] If Control 'Master Bed Motion-Sensor' is switched On And Control 'Master Bed Motion-Sensor' is not switched Off <-------this line runs else....else is empty Then Set 'Bathroom Big Micro Dim' Off Wait 3 seconds Set Scene 'Live - Key H' On Disable Program 'Big Bathroom Sensor 2 Off' Else - No Actions - (To add one, press 'Action')

Read the manual very carefully. I know it's is there and still have trouble finding it when looking to reverify but... The button on the back when held puts the MS into linking mode. Two more taps gets it back to normal. Each tap on the button ends a toggling status to the ISY. So ISY will register motion On/Off/On/Off. This is independent of any other settings. Seven rapid taps on the button will force the Dark sensor to send it's status IF the status has changed. My last one only takes five taps. Make sure the dark level setting is reasonable and point it at alternate lighting levels ie. dark/light/dark/light.... It takes a few seconds for the sensing circuit to readjust each time before doing this.

As a slight variant and addition to that, above, have a very long time off on the bathroom light and if motion is detected in the hallway make an assumption the person left and shorten the time off for the bathroom. If bathroom motion is detected again, reset the sequence and start a very long timer again. This gives a compromise that can work for people not moving too much. I wouldn't put a short auto-Off in a bathroom. You may be caught in the shower in the dark. Energy saving with the new LEDs will never pay for the MS anymore. It's about convenience now. I can walk in most common areas in my home now with my hands full of boxes and never have to touch a lightswitch. I have MSes in all my bedrooms and occasionally I get asked by guests making sure they are not webcams.

The learning curve for event based software can be tough for some people. It will come. I spent a few years working on an event based system that controlled electrical grid systems that controlled a good portion of our economic area of the province. You make mistakes on that one you pay and pay so dummy training systems and emulators were written to prove everything before installation into the real deal. Even still, ISY gave me a run for my money. Now when I look back at programs I wrote a year ago I think, "That's dumb. I could have done it this way, so much better". Don't be discouraged. Use canned programs from people and you will still find yourself improving on them for your needs, and then improving them again, later. It's a cool hobby controlling the world.

I avoid scenes in most cases for clarity and lack of comm handshake. However they do afford an increase in speed for response when ISY is not involved eg. MS/LampLinc and the reduction in lines of code for multiple devices is nice.

But Windows still cannot print out a directory listing. It was so easy on a Unix work-alike system back in the 80s.

Thanks giesen! I've been looking for a service like that for many years. Perfect location too, although I am now 4 hours away but once or twice a year.... I really should give aartech.ca a kick again. They usually have prices in Can that can't be beat.