apostolakisl

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

First thing. If ElkRP is actively connected, NOTHING ELSE WILL WORK. This is a common mistake and will certainly prevent ISY from connecting. Whenever ElkRP is connected, all other IP connections are suspended. I do have the Elk module for ISY which changes the options around some. But I am pretty sure the settings I am about to tell you are the same even if you don't have the module. In ElkRP confirm the settings. From ElkRP connect to the Elk panel. Then click "m1xep setup" then click "receive" to load the current settings into ElkRP and ensure that the values shown are the actual values in the xep. Under the TCP/IP settings tab, you will want to confirm your Elk has a static ip address and that the "enable non-secure port" box is checked. If not, please give your Elk a static address and check the box to enable port 2101 and then click "send". It will reboot the m1xep. Reconnect and click "receive" again and confirm that your settings are correct. On ISY, go to the "configuration"/"Elk"/"Configuration" tab. Ensure that the IP address listed is the same as you set the xep to. Also confirm that the "enabled" box is checked and that the port is 2101. Also enter your user code. Lastly, in ElkRP, open up your user account for the user code you entered in ISY. In the "user authorizations" box, ensure that everything is checked EXCEPT "Access". "Access" should NOT be checked. Make sure to connect to the panel and load any changes you made into the the panel. And, of course, DON'T FORGET TO DISCONNECT WHEN DONE! The box that you highlighted earlier is a drop down to pick the area you want to deal with. Most homes only use a single area, but if you wanted you could divide your house into multiple areas. Having more than one area is almost like having multiple alarm systems. Like if you had a guest house you could put it on the same Elk panel but give it a separate area and it would work like a whole separate alarm system. As far as the functionality without the Elk module. It is somewhat limited. Pretty much you get to arm/disarm and see the status of the alarm. You also can export your entire lighting configuration into Elk from ISY for controlling/monitoring the lights using Elk. With the module, you get nearly 100% access to Elk stuff in your ISY programs. Like the status of a zone, an alarm, an output, a temp, a voltage on an analog input, etc. All of these various items can be used as "if" statements in ISY programs. On the "then" side of programs, you can pretty much do anything, like arm, disarm, bypass, send text to keypads, turn outputs on/off, etc. Essentially, the module "fuses" Elk and ISY together. It is well worth the $100. ISY is a much better platform to write programs than Elk. I would agree that Smarthome should indicate the various levels of connectivity and that for the full deal you need the module.

Any alarm that can be programmed to arm/disarm based on a zone status. Using an I/O link, connect the arm/disarm zone to the I/O link. If you don't already have an alarm, however, get an Elk. It is such an elegant solution when used with ISY. The extra cost for an EZ8 over other systems isn't that much.

I set the SSL settings for the Elk. The Elk still works with ISY. Not sure if there is any way to confirm that the communication is actually secure.

There is a check box on the configuration page if you want a system query on reboot. Otherwise device status stays blank until the device is involved in some activity or is queried. You can also write a program to run a query based on whatever "if" events you want.

Is this a problem with a previously working connection or is this a first time connection?

Is your computer that fails to connect on a different subnet? That will cause it to not find automatically. If that isn't it, try rebooting the router.

Hi apostolakisl, The URL you are using (I am not sure where you got it from) is not correct. There's a '-' between universal and devices. So, http://www.universal-devices.com/99i/3. ... board.jnlp With kind regards, Michel Hmmmm. I clicked on the link in the security guide tutorial. Despite the fact that the dash is there when you see it written on the page, when you click on it the web browser ignores the dash. http://www.universal-devices.com/docs/I ... 0Guide.pdf Perhaps because the dash is at the end of a line and it interprets that as a dash to indicate it wraps to the next line rather than being part of the URL. It even does it when you cut and paste (which is what I did). I'm using Chrome, not sure if IE would also do it. Perhaps you could reformat that the URL fits on one line of the page.

Trying to set up SSL for Elk but having no luck. Visiting http://www.universaldevices.com/99i/3.3 ... board.jnlp (or substituting other earlier versions) gives a page not found error. Otherwise no probs.

Real world experience I think would favor the Insteon devices as the most likely point of failure in this setup. Either do to failure of the device itself, or because of a failed comm. Which is fine, it's only a doorbell, and an auxiliary one at that. And the device isn't on the moon, it's in his basement, not a client across town costing you two hours of time on a service call. So if I were a pro installer who had to service it for free and could pass on the cost of a higher end device to start with, I would probably do it that way. But $10, it's chump change, and it is right there, a click on ebay and another on paypal and it's at your door, and it has the base with screw down terminals all right there ready to go so easy, and then you get a second one to stick in the drawer for that random future job.

Yes, but for $10 total (shipping included) you are getting 2 relays with multi throws each (meaning you have lots of contacts to choose from). And it is just a doorbell. If it should stop working, it's not like your fire alarm is going to stop working. I really really really doubt those fail (assuming the coils are good as stated by seller). Feel free to really really really doubt it. I am only speaking from 35+ years of experience. Many of which were troubleshooting and redesigning miss applied relay applications. Re-specified a low current contact for a number of applications using that very IDEC relay in a low current application that intermittently failed for the reasons stated. As was stated earlier: you may get a way with it. Or as you said if you are willing to rewire or replace from time to time. Take this for example. http://www.elkproducts.com/product-cata ... elay-board These are commonly used 10amp contact rated that are almost always used for milliamp applications. It is a 5 minute install, so R and R not a big deal. But I promise, no R and R will be needed, those will work.

Yes, but for $10 total (shipping included) you are getting 2 relays with multi throws each (meaning you have lots of contacts to choose from). And it is just a doorbell. If it should stop working, it's not like your fire alarm is going to stop working. I really really really doubt those fail (assuming the coils are good as stated by seller).

Here are 2 of them with the bases. http://www.ebay.com/itm/LOT-OF-2-IDEC-R ... 43b5e6c4fb

You could add one of those little check boxes in the corner that says "don't show this message in the future".

How about a simple compromise. When you exit the admin console, a pop-up that asks you if you want to do a backup. The OP complains that he "often forgets" to do backups, and this should fix that problem. I would also admit to be a bit lax about backups after making changes. But, as mentioned, backups serve no purpose unless something was changed. And nothing can change via any mechanism aside from a person logging in and changing something, so a system that reminds that person upon exit should cover you. Conceptually, this is how Elk works. When you try to close the admin console, it asks you if you want to save it. Saving an Elk config is the same thing as an Elk backup since a "save" is a backup file of the Elk configuration, not the actual, uploaded to Elk, file.

I would try a reboot.

No. ISY only runs programs, it is not needed for you to manually control the lights. ISY is a tool to program the switches, but once programmed, the switches don't need it. Professional installers who do Insteon will use ISY to program a house and then they unhook it and take it to the next job. The ISY (or something like it) is necessary to run programs (like scheduled lights) or to integrate your Insteon with other technologies (like Elk). But you will not lose any programming rebooting them. The xep does not contain the programming, it is only the ethernet adapter, the programs are in the main Elk board. But still, no worries, these things are quite robust. But it is certainly not a bad idea to run a backup of your ISY if you haven't already. The Elk programming also is saved to the Elkrp software so if somehow the Elk loses it's programming you just upload it back in from ElkRP. Remember, your ISY is going down every time you have a power outage anyway. And probably the xep unless you have it on a UPS.

It sounds like you don't have the Elk module. ISY still has communication ability with Elk without the module, though it is very minimal, but it would include the ability to have an Elk motion detector turn a light on. If you don't have the Elk module, then this means your Elk is calling all the shots. In other words, you must have a "rule" on your Elk that says something like "whenever zone x becomes not secure then turn y light on for z minutes" rather than a program on ISY. The Elk is linked to the ISY which receives the lighting commands via IP and then passes that through to the PLM which broadcasts it over your home power lines. Why your screen is doing this bounce around thing when you try to input info I am not sure. But here is where I would start. 1) Remove power from both the XEP and the ISY. 2) Power up your XEP. 3) Run your ElkRP software. 4) Click on XEP setup then "find" button and confirm xep responds with the IP and port number you expected. (xep is slow to boot, this may not respond for a minute or two after power up) 5) Do not login to your alarm panel with Elk RP. Logging into the panel with Elk RP software will close all other connections including ISY. (only ElkRP does this, the m1togo, the Elk java panel, and any smartphone apps that login will not do this) 6) Power up your ISY 7) Enter your Elk settings under the configuration tab. See if it connects. You should get a status bar just below the top menu telling you if the system is armed/disarmed and it should have a box allowing you to input the code to arm/disarm. Let me know what happens.

I don't understand what you mean by "the isy program begins to jump on the screen" What makes you suspect that ISY/Elk are not communicating aside from this one light not turning on? Do you have the Elk module for ISY? (look under help/about and it will say "Elk Security System" in the "product" section. Does the ISY admin console show the correct status of your alarm at the top of the screen? Did you change some of your Elk settings to think that ISY would have wrong settings?

Lee, I grant you I made a mistake answering a little too quick on one point. But the point about there being more switches still holds. There would be no point in him changing the ramp rate if there were not more than one switch. If there were only one switch, he would just leave the scene at 8 minutes all the time since presumably nothing else would be activating that scene. I suppose there could be multiple responders and thus a need for scene, but that is generally not how a bedroom is setup.

My point was directed at the OP in that I think he would be better served to take a different approach. Having a scene dedicated to the purpose of morning wakeup is simple and clean, it avoids un-intended consequences, and it avoids errors in re-writing the switch that can occur, especially if someone tries to use the switch while it is re-programming or if other Insteon/ISY activity coincides with the re-write.