apostolakisl

Remember, provided you don't make any changes to your devices after installing the 994i, you can always unplug it and plug the 99i back in and nothing will have changed. So, I wouldn't bother waiting to start running the 994i.

The simple way to do this is to use the weatherbug module. At my home weatherbug is almost always within 1 degree of what my thermometer reads outside my house. Other options are more complicated and go along with the discussion related to the freezer/fridge monitoring you posted on. Another option is to use a CAI board and one-wire temp sensors. It will need an internet connection so you either pull a wire to it or you need a wireless bridge. The new firmware can post values directly to variables in ISY without any outside intervention. This is relatively low cost. . . around $50 without a wifi bridge, add another $30 or $40 for that if you need it. Also, if you have an Elk security system and the Elk module you can use Elk sensors. You would also need to pull a wire. Elk temp sensors are seemingly overpriced to me at nearly $100 and they will need an open zone on your panel (I also believe it has to be one of the 16 main zones) Otherwise you would perhaps use a system that reports to a PC which then posts to ISY.

Vyrolan's approach is excellent. By including a "control not fast off" in the if clause he has created a second trigger (fast off). In the event that a "fast off" command is received, the program re-triggers. A program that re-triggers always terminates any current activity (the wait clause here) and starts over from scratch. Since the "fast off" is preceded by "not" this results in a "fast off" command received causing a false if condition which runs the else clause. So, in summary, if upon leaving the house, should you do a fast off on that switch, the wait currently running terminates, the program re-evaluates to false, the else clause runs, and the lights shut off.

This is a bit complex to try to describe the logic behind all this (what Lee said), but I'll try. Devices need to function independently because each device can be the member of a great number of scenes. So you could not have it that a device turning on turns all other linked devices on. If this were the case, anytime a switch turned on, every device linked to that device as part of any scene it had membership with would turn on. The result would be that there are no independent scenes and it would be the same as hardwiring all the switches together ala typical 3/4 way wiring. Insteon uses "controller" and "responder" designation to make this work. When you phyically act on a device (push the button), the device itself always responds, and, if the device is a controller of a scene, all the other devices in that scene respond as programmed to. A device can only be a controller for one scene. If you think about it, you will realize that if a device were a controller for 2 scenes, you will have effectively just merged those 2 scenes into one scene. So no point in that. When a device turns on as a responder, it is not the same thing as turning on by direct action on the device. If it did, you would realize that should that device be a responder to one scene, and a controller of another scene, the effect of a device responding to one scene by turning on, would then propagate through to any devices that the switch controlled, which could snow ball through your setup potentially turning every device in your system on. Also I will point out, when you turn a device on using ISY, you are turning the device on as a responder to a scene with two members: ISY and the device. ISY is the controller of that scene. All devices added to ISY are a member of at least one scene, the ISY scene (technically it is joined with the PLM). ISY is unique in the sense that it is a controller of multiple scenes. The reason for this is that ISY can uniquely control all those scenes independently. So in the end, there are two ways to turn a device on. Either directly act on it (push the button), or turn a scene on that it is a member of (either via ISY or using another switch linked to it as a controller).

I just wrote that same program for one of my switchlincs and it works perfectly. It's v38 2476D. So, I don't know whats up. What switchlinc are you using? If I have any of the same ones I'll test them.

I agree with what Lee is saying in principle, but am having a hard time thinking of what other program would interfere like that. Perhaps the variable is going up but another program runs off the same trigger and drops it back down. With two programs running nearly simultaneous, you would not see the up, down, it would appear to stay the same. Well, when all other programs are disabled, we will know soon enough. Also, you can look at the last run time on all of your programs and see if any other program runs at the same time this one runs. Also, that program should always run "true". It might be worth checking that indeed it is always stating "true". A program whose only "if" line is "control on" can never be anything but true (at least not without some other program doing a force run of the else clause).

Hmmm, Well, if the keypad linc executes with every "on" press, this would seem to indicate the ISY's execution of the program is not where the problem is. A switchlinc should also send an "on" command with each press without having to wait 5 seconds (also realize that 2 presses very quickly will send a "fast on" rather than an "on", but to do that you have to double click in a fraction of a second). If you open event viewer and set it to level 3, you should see an entry every time you push the button. If every press does not produce an "on" event in the viewer, it is either not being sent by the switch, or not being received by ISY.

Also, is this program in a folder? And if so, does the folder have any conditions?

Status only triggers with a change in status. So once it is on, it would have to be changed to some other status then back to on to run the program. Control on should work. I can't really think of any reason why it is only running every other time. Try changing the program to a different switch and see if it also only runs every other time.

Is the program running every time? Take a wifi laptop with the admin console running and watch the program summary page and see if every time you click "on" the program updates the run time.

I have been thinking about this. I have a couple of the wireless modules that post the temperature to their servers and can be pulled down. Can the ISY be programmed to poll a website with some of the extension modules? Refresh this page to get the latest values for your TX-60 devices. Name Probe Device Hum Last Seen Batt Link Greenhouse 31.2 °F 30.2 °F 86% 12/18 10:19 PM OK 100 % Shop 64.5 °F 45.6 °F 64% 12/18 9:25 PM OK 100 % ISY can receive data via GET commands. I don't believe any module is necessary to do that, but it might require the network module. If you want ISY to initiate the conversation it would need to be generated by an ISY network module posting to your server which then runs a script that separately runs a GET posting of a value to an ISY variable. In other words, you can't query a table of values and then have ISY parse it out.

Large scenes should not pose a problem and in fact should alleviate problems. A mix of device types should also not be a problem. When a single activity (like a going to bed activity) puts all devices into a single scene, there is only a single Insteon command to run that activity. One command means less traffic which tends to reduce problems.

A webcontrol board would do the trick, but you would need to have it on a UPS (as well as your ISY and your router/modem/gateway). You also would need to find a wired pathway into the fridge. The Lacrosse technology wireless thermometer/humidity sensors work quite well, even when closed up in a fridge. The battery lasts many many months (perhaps more than a year). However, I have yet to figure out a good way to get the data out of the receiver and into something else (like ISY) automatically.

rain data is piss poor at every station that I have ever tried anywhere near my current house or my old house.

Great to see you got that working. A couple things that might help you. Elk outputs are 12v and 50ma max (didn't look up the 50ma but I take your word for it). The actually amps is determined by the resistance of the load, it doesn't just always flow 50ma. So a 12v 30ma device will only draw 30ma, no need for resistors. The 50ma rating is only a warning to not use a device that draws more than 50ma since you may damage the Elk. The equation V=IR dictates the situation. V is set by Elk, and R is a property the attached load, I is the result of the other 2. The resistors you added have dropped the voltage presented to the relay. Apparently the relay still works despite the lower voltage. At present, your voltage is getting split up between the resistors and the relay. It will be split up proportionately based on the relative resistances of the relay as compared to the resistance of the resistors (for example if they were equal, then each would be getting half the volts). Since you know that v=ir for each device, and that i must be equal for the two devices (they are in series), and that total voltage is 12v, the following equations apply. Vrelay/Rrelay = Vresistor/Rresistor where Vrelay + Vresistor = 12. The same holds true at home where your typical wall output is rated 120v 15amps. That doesn't mean that everything you plug in gets 15 amps forced through it. Bypassing zones on an armed Elk system is allowed and can be done from Elk rules. I haven't looked into ISY's ability to do so and take your word for it that it can't. If you need to bypass a zone on an armed system, it can always be done from Elk rules. If you want ISY to do something on Elk that only can be done from an Elk rule (like bypass an armed zone), then you need to trip an elk rule from ISY. To do this, use an unused Elk output. Have ISY turn the output on for one second (pick something high that you will never actually have a real voltage connected to, like output 100), and then have an Elk rule tripped by "whenever output 100 turns on, then blah blah blah"

Yes, I do know what that is.

I'd be interested in seeing a wiring diagram on how swapping 2 single pole 120v breakers in the same box with the same neutral bar affects neutral load. But that aside. Might I make another suggestion. You appear to have very few devices in this setup. At a glance it appears that they are all dual band. Consider filtering all of your Insteon devices. Take the power line component completely out of the equation and let the RF do all the work. Of course if your devices are at a distance this won't work. But it is a thought. Another thought would be to abandon Insteon and use IP. A global cache device can be controlled by the ISY network module but communicates over IP. Unfortunately, I don't believe they have a wifi version that would accommodate your needs. But you could use a wifi bridge if wired IP isn't available. You could also consider a webcontrol board. Same holds true regarding wifi. Perhaps there are other brands of devices I am unaware of that control relays over wifi IP natively that can run on the ISY network module.

Assumptions: 1) 120v x 3 incoming power from the utility 2) Insteon devices are all plugged into standard 120v outlets going back to single pole breakers at the panel. 3) None of the 120v breakers that go to outlets that the Insteon devices are plugged into have significant loads (which they definitely would not if they are going to standard wall outlets.) Swapping which of the 3 phases any of those single pole breakers take power off the grid from will have no impact on anything inside the building, including neutrals. Neutral trouble can come to bear if you change around your hots away from the breaker box (in a j-box for example). But if you are unsure of what you are doing, consult an electrician. Not that this is a cure all. The 3 phase motors will of course be attached to all 3 phases so if one of them is noisy or attenuates signal, then you will have solved nothing since there is a good chance it will affect all 3 phases. Although, this is not for sure. Many times some components of a 3 phase device will only take power off of one of the three phases. For example, a 3 phase motor may have a control panel that is powered off of 120v, so if the control panel were noisy, the other 2 phases may survive unaffected. An algorithm: 1) Identify which breakers power your Insteon devices. 2) Shut off all breakers except the one going to ISY 3) Turn on the breaker going to your first Insteon device. Test for comm reliability. 4) Repeat step 3 until all the Insteon devices are on. 5) If communciation between all the devices is reliable, start turning on additional breakers one at a time without powering on the loads connected to the breaker. 6) Repeat step 5 until all breakers are on 7) Once all breakers are on and if you still have not run into reliability troubles, start turning the loads on one at a time. If at any time you lose reliability, turn that breaker or load off, tag it as a trouble maker, and move on. If you are able to determine that you have one or more trouble makers, then consider how to solve that based on what is causing the trouble. Sadly, if it is a high amp device, you may be out of luck. Filters for high amps are very pricey and may just not be available depending on how many amps you are talking. If your lucky enough to find a single phase circuit that is the root of your trouble, moving your Insteon devices off of that phase may be all you need. Or you may be able to filter that entire breaker (assuming no Insteon devices on the breaker and that it is 20 amp or less).

It has been mentioned that three phase power plus poor comm/noise is at the root of your problem. I might suggest you consider re-configuring the phases so you can get everything Insteon on the same phase. Hopefully you can find one of the three phases that is not cluttered with noisy devices. 3 phase panels generally are such that every 3rd contact on the panel is of the same phase. If you swap the wires/breakers up/down one there is a good chance you can get all of your insteon devices to be on the same phase. It seems as though you only have few devices so probably very few modifications would be necessary to accomplish this.

Yup! The as of yet unreleased webcontrol32 board is user upgradable. But that doesn't really help out for now does it. Probably it was Wayne. CAI webcontrol is a small time operation. I have had quite a few email interactions with them and all of them ended up in Wayne's inbox. My gut feeling is that Wayne is the US face of the company and that otherwise it is a foreign (Chinese) operation.

Agreed. When you first added variables to ISY and I went to give out a few names (using spaces of course) and nothing happened, I was at first thinking, Hmmmm, what the heck. After a few more tries my language got more colorful until I surmised the no spaces allowed restriction.

So I looked up the 1100. It does allow an RF extender. What you need to do is buy one of those and put it's "blaster" in line of sight of the ISY and designate the ISY commands to go to the RF extender. This device receives the RF from the remote and translates to IR. This is a proprietary signal that isn't receivable by anything except the Harmony RF extender (as far as I know of at least). If you already have an RF receiver, you probably can have 2 of them on the same 1100. You definitely can on the 890 (I have 2 on that one), but you should confirm this before buying. Also keep in mind that you can make an extension cord for the RF "blaster". So if you already have one and there is a way to get a wire from it to your ISY, no need for another one. I have one extension cord running like 50 feet without issue. You need a mono 1/8 inch female and another 1/8 male (please check to be certain your uses 1/8 size) and wire up however many feet between them you need. Or, you could just cut the wire it already has and splice in an extension. Keep in mind that polarity does matter when wiring these up.

I think we could have fun. Tried welding inside once too. Don't recommend it. Smoke detectors are very sensitive to whatever the microscopic invisible smoke that comes off when welding. On the CAI units, I would check to see what firmware is shipping. I just sent several of mine back for upgrading to 3.2.16 which might not be shipping yet unless you ask for it. They added GET function for CAI to CAI comm. as well as more email capacity. I am hoping the GET function is flexible enough to use ISY's REST function so that we no longer need to run wclink (not that I don't very much appreciate wclink, I just would rather skip that extra step). Sometime in the next few months cai will have a new bigger board with double everything and other extra features. So if you have any thoughts of controlling anything with lots of ins/outs you might keep that in mind. That board also firmware updates over the internet, so no needing to mail it back.

I don't have the 1100 model, but I do have a couple 890's and a 900 model harmony, so will give you my thoughts based on that experience. First off, I assume you are confident that you have line of sight from the remote to the ISY receiver. I can confirm that Harmony imported ISY codes do work on all of my remotes and I would doubt that the code library isn't exactly the same for all Harmony downloads. Does the 1100 model have the option to use an RF receiver? If so, check to be certain that you don't accidentally have the ISY codes going out as RF.

I just emailed Wayne at CAI and he tells me that the 3.2.14 firmware has a bug. That's why the .15 version only a few weeks later. He is sending me out the .16 version which also includes GET function to post values/states between two (or more?) CAI's. I'm looking forward to seeing it. Maybe it will let me post to ISY, but I doubt it. Wayne tells me the current hardware is pretty much out of space for adding any more features and aside from cleaning up any bugs, this is the end of the line for new features. EDIT: I found the flow meter I got a while back. I'll hook it up to the CAI board when I get them back and let you know how it works.