apostolakisl

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.

Yes, those relays will work. I actually have one of those exact boards. The only downside to that model is that it is backwards. In other words, it is ground switched, so when 5v is applied, it turns off, and vice-versa. That board (and some others like it) use regular coil relays which are not physically powered by the CAI. These are dry contact relays and have decently high voltage/current switching so you can switch motors and other full out stuff. CAI has an option to use "state reversed" to help not get confused when using backwards relays. In other words, turning an output on actually turns the 5v off when using this mode. You can also use a true solid state relay board. These cost a little more (like $25 for 8 board). I have not used the board I see for sale on amazon and ebay, but others I have used do not require any power supply (it all comes from the CAI). These are more limited in what you can power off of them. Also, I found the relay board you listed on Amazon for cheaper with free shipping. It probably will come a lot faster too and Amazon in general is a bit more reliable. Searches that bring up the ttl level relays include "arduino relay", "pic relay", "ssr relay", and "ttl relay". As far as power supplies. I have the same issue. I have taken to using old ATX power supplies and wiring up to terminal strips. They are cheap (free) and typically provide high current, stable, clean power. Trouble is, no 9v. Soldering can be quick, or not. I soldered up my garage door opener and it was probably a 5 minute job. It had plenty of room around the 3 micro switches and there were only 6 wires total to solder. But another project required 8 micro switches that each required 4 solders and the board was packed super tight. That one was very tedious and when I was done it looked like the board had grown a mohawk.

Do you mean you are trying to change the name of the variable? Is so, you can have no spaces in the names of variables. If you put a space in, it won't give you an error, it just won't change the name. Commonly people use a period instead of a space. Also, it is common to start the name of any integer variable with an "i" and any state variable with an "s" since there is otherwise no distinction when you pull the variables up in programs.

It looks like 3.2.14 which came out in September. They also have one more after that which is 3.2.15. According to the manual, it will handle up to 2mhz on ttl input 1. It also appears that it can be set to read out frequency or do a raw count. I am figuring this out reading the online manual and have no experience with it yet. It also appears that using this function will preclude using it as an x10 device.

Curious comments for sure. CAI as a relay controller is quite simple. You need 1) CAI 2) TTL relay board ($15 on ebay) 3) some wire 4) A couple wall warts Connect the 8 outputs on cai to the corresponding 8 relay inputs on the board with your wire. Connect your wall warts and plug it in Plug cat5 into switch/router Log into your CAI and set the IP, port, username, and password you desire. Go to Network resource settings on your ISY Http Get IP on your LAN of CAI Port number of CAI (often left at 80) Path /api/setttloutput.cgi?output=1&state=1 (this turns output 1 on, sub out the 1 to 0 after state to turn it off) Click "ADD", then "authorization" and put your CAI user/password Click "Update" Click "Save" Click "Save" on the main screen. Create 2 of these for each output, one to turn it on, and one off. Just use the "copy" function and change just those values and give it a name that corresponds. Now, in ISY, just write your program If Event of your choice Then Resource 'CAI Webcontrol Output 1 On' Wait 1 second Resource 'CAI Webcontrol Output 1 Off' Wait 1 second Resource 'CAI Webcontrol Output 2 On' Wait 1 second Resource 'CAI Webcontrol Output 2 Off' Wait 1 second Resource 'CAI Webcontrol Output 3 On' Wait 1 second Resource 'CAI Webcontrol Output 3 Off' Else - No Actions - (To add one, press 'Action') Once you get the soldering done, I am guessing 15 minutes for the setup. This would "push" the three buttons for one second each with one second delay in between. Mind you, this is only an output solution. If you want input, you need to use WClink and a computer (or pogo thing a ma jigger). But the car started only needed 3 outputs. Total Cost for this is $60 assuming you have wire and wall warts. This also can be accessed not just on your LAN but anywhere in the world. For example: you could control a CAI board at your office from the ISY at home. You could also write this program in CAI if you so choose and simply have one resource command on ISY that serves to trigger the "macro" on CAI. Your choice. But if you don't want to mess with CAI's PLC code, then don't do it that way.

Jellis, Only the newest firmware of the CAI board has the ability to count high frequency pulses from a flow meter. I have sent several of my boards back to CAI to get upgraded, but they are not back yet. Setting up a counter using the PLC code is not complicated. It would only be a few lines of code. A few more lines of code would divide the counts into ounces or into 12 ounce blocks, or both, or whatever you want. With WClink you can sync those to variables in your ISY to notify you. You could have fun with that. Flashing lights, or voice announcement (if you have Elk) or any number of crazy ideas. Regarding Keg beer: I have a designed and patented a new coupler (tap) that measures the pressure differential between the gas and liquid at the coupler and from that can tell how much beer is in the keg, if beer is flowing, and the split second when the keg runs dry. It is accurate to about +/- 10 ounces at any given level in the keg. Simplistically, you can think of it as measuring the weight of the column of beer in the dip tube above the resting level in the keg. I was using the CAI boards as the controllers for the coupler during my initial testing. The coupler itself is finished and in limited production. I have hired out the design and production of the dedicated controller as I am not one to design circuit boards. Currently we are finishing the firmware on that. It is a wifi system that posts via internet to my businesses server which then creates graphs and reports. It also uncouples the keg the split second it goes dry so you don't "blow" the keg and fill your beer line with gas (mostly a problem with bars/restaurants with long lines). This is a commercial product designed for inventory control and order fullfillment. I plan a home version as well. A timeline on this is hard to tell. So maybe you stick with your flow meter for now. Early on when I was first playing around with this I picked up a flow meter for about $40 from someone in England. It was a fine device but after working with bar owners discovered it wouldn't work for various reasons. I can't recall where I bought it, but I found it just googling.

Yea but Amazon doesn't even have the things and there was only 1 for sell on Amazon Marketplace. That's a lot more work than just plugging something in... Admittedly it's more inputs and outputs, but for not much more money you could just buy a SHN device, plug it in, and be done. That's also added complexity since you have to program different things in different places. A SH product would likely be completely programmable and managed by the ISY once U-D added support. It would just be one ISY program as the "single command to initiate the action". I have 10 of these. You can buy them direct if Amazon isn't working out for you. In fact, I believe the marketplace seller is the actual company. If you want easy, fine, but nothing about soldering a remote control together to run your car is easy. If you know how to use the ISY network module you will find that this is a process where the vast majority of your time is spent soldering the little tiny contacts in the remote and the rest is "easy". So I think the easy folks left the room a while ago. The car remote is a simple control which can all be done in ISY using only the network module to post commands directly to the board. You will need ioguy program if you want comm going from the webcontrol to isy, but that isn't necessary for this application. It is a lot less money than SHN Device. You are at $200 for the device plus the PLM. The $100 price I listed is for all the bells and whistles. $60 buys all the parts you need including shipping if you just get the board and the relays and mount it to a board or in a can that you already have. Also, the webcontrol does not rely on insteon power line commands. It is all done over IP. In most settings, IP is going to beat out PLC reliability by a factor of 10 or maybe even way higher depending on your PLC failure rate.

You should edit the screen shot and black out your IP/port number. I was able to access your ISY. Of course I don't have your password, but still, I wouldn't publicly broadcast this stuff.

Webcontrol board (amazon) plus a compatible relay board (ebay) will give you 8 digital inputs, 3 analog inputs, 8 digital outputs, 8 temp inputs (using 1-wire sensors), and optional humidity sensor. All this connects to ISY using io_guy's program listed on this forum. Total cost would be about $100 if you also picked up a housing and other accessories. Something like the sequence that does the car start could all be programmed into webcontrol (using PLC code) and ISY would send a single command to initiate the action.

Most folks would have at least 3 keypads in a house that size. Master Bedroom Front door Back door Other possible locations Upstairs Hall Family Room

The UD Elk module is a license upgrade to your ISY and is just a matter of paying the money and activating it. It's not a physical thing. But I suspect you will want it as it gives ISY essentially full access to everything on the Elk. You will need an XEP. ISY and Elk can't talk without it. Elk can't talk to anything internet without it and you will have to plug a computer directly into the Elk board to program it. Hard to know what else you might want since I know nothing about your house and what you want it to do. But my guess is that one keypad is going to be a bit deficient. But you may hold off and play around with using tablets as keypads as some of them are less than $100 now and with proper mounting hardware can make really slick keypads.

I ended up buying these things as well and pretty much did the same thing. I bought 2 of the units I listed above that receive the rolling code and programming 2 buttons in my car. I used my Elk panel to receive the input. Since I was down to my last unused zone on Elk, I put the 2 devices in parrallel connected to the zone, but I also put a resistor on one of the units. So, when neither button is being pushed, the zone is open (14v) When the one button is pushed, it is closed (0v) When the other button (with resistor) is pushed, it is closed, eol resistor (7v). Since ISY and Elk are linked, I set the ISY to look for open, short, and eol.

You can use a webcontrol board to count the pulses. Then using io_guy's program that links the webcontrol board to ISY, you program the 2 devices to accomplish your goal. The program io_guy has will synchronize the variables, inputs, and outputs, on webcontrol with variables on ISY. Webcontrol can be programmed to count pulses. The new firmware is necessary to count rapid pulses, so make sure you get the most up to date version. You would need to write code in the webcontrol to some extent to get values that could be transferred to ISY. http://www.amazon.com/Webcontrol-Univer ... webcontrol viewforum.php?f=81

EDIT: I got beat to it. This is the same stuff. If you used the "else" clause on your third program to send the door closed message, you could delete the other 2. The third program triggers when one of two things happen, the door opens, and the door closes. These are the only 2 possible changes that can occur to the door so that should encompass all possible triggers. When the door opens, it will run true, it will send the message from the "then" clause, then it will keep sending tgat message every 5 minutes until it is interrupted. When someone closes the door, the program will trigger (which interrupts the repeating then), but it will trigger as false. This will run the "else" clause which can contain your door closed message. Since this clause doesn't have a repeat, this program will end. If you wanted one message when the door first opened, a different message after the door was left open, then place the first message before the repeat, then wait 5 minutes, then the repeat every 5 minutes with your other message after the repeat.

My ADT contract ran out a few months ago and I went through the decision of switching to Elk or sticking with DSC. In the end, I stuck with DSC. Price wasn't the factor but it is quite a bit cheaper. For me, DSC is the largest alarm player in the market and have a very stable system. I like the Elk system but fundamentally I have an issue with having that much power in my alarm controller. This is a UL certified alarm instrument - in my opinion it's not the place to control lighting, garage doors, tempertures, write programs, etc. With all those features and constant firmware updates it's just a recipe to introduce bugs. I like the fact that my alarm system is hard coded and geared to just do one thing - alarm. That's why we have an ISY - to control automation. And last, the new DSC touchsreen is a thing of beauty, Elk's screens are ugly duckings. I agree, Elk's old keypads aren't the greatest looking, but the new screen that came out a few months ago is pretty sharp. But as these things are going, you can put any tablet up and run the touchpad software on the tablet and get any look you want. From a security point, Elk is UL listed and rock solid. The HA stuff in no way compromises the security. A few glitches with the play stuff like email exist, but not security. And from the point of mission critical controls, I only use Elk to control that because of the ~ zero failure rate. I would never control something that has anything to do with water or a motor using Insteon. But the thing is, security and HA go hand in hand. Things like occupancy and door/window status are very much a part of both worlds. Also light control as part of the security system is a valuable tool in the event of fire or burglar alarm. For example, fire alarms light exit routes.

I know your installer doesn't do Elk, but I think you should reconsider. As someone who wants security and automation (presumably Insteon) to work together, and as someone who currently does not have a pre-installed security system. There is no better way to link an ISY to a security panel than to use an Elk with the Elk module for ISY. Bar none, it is a superior method and not just by a little. io guy created a fabulous program in the dsclink, but it can't compare to the built-in Elk control that ISY has. Virtually any aspect of the security system is accessible from ISY and it is all there in its native form (ie, zones are listed by name as the zones they are, outputs are the same, zone voltages, armed status, armed up status, alarm status, temps, zone bypasses, etc, etc. . . it is all there in easy to use format. No need to code a bunch of variables as go betweens. If you already had a DSC installed, no doubt, ioguys program is a great tool. As far as installing, Elk hardwires in the same as any other system. The pure security side programming is something any experienced alarm installer should be able to pick up in a few minutes. All the fancy automation stuff has a learning curve, but that really should fall to you to do anyway. Just saying, I think you will kick yourself later for not getting an Elk. .. if indeed you use ISY/Insteon for your home automation.

1) The LED Christmas lights shouldn't be a problem. I have a lamplinc doing the same thing for 3 years running now. 2) Assuming it isn't a member of all kinds of programs/scenes, a simple thing to do is simply delete the device completely and then re-add to ISY. You might do the same with that other devices listed in the log functioning at the same time.

Check you logs to see if you can't find exactly when it is shutting off and if there are any other activities running at the same time. Certainly if you witness it turning off, pull up your log right then and see what the listed activity is. Possibilities. 1) You have a program that is turning it off. Sometimes these things happen where you left a scene or device in a program by mistake (maybe you were using the device for something else at some other time or you accidentally clicked on the device/scene by mistake instead of the one above/below it). Right click on your programs tree and click "find/replace" and look for the device. Also, do the same for any scenes that it is a member of. 2) You have a legitimate link that shouldn't be there. Check the device "controller" and "responder" list to make sure only the right stuff is there. 3) You have a phantom link. It is possible that ISY thinks the device should have a link that it should not have. Delete the device from ISY entirely and re-add it, then join it back to any scenes/programs it is a part of may fix this. Just because it only lists the proper stuff in the controller/responder list doesn't mean that there isn't a false link in the ISY table. I had this happen once and it was frustrating to work it out. Unfortunately, there could be a phantom link in a different device that is turning it off. Only deleting that device and re-adding will fix this issue. The key to working this problem out is looking at your logs at the time the device shuts off to see what is on the power lines.

Moved post to Elk