apostolakisl

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.

Yes, you are correct. But there must be multiple switches controlling that light, or there would be no need for a scene at all. All the switches aside from the load switch would get stuck with that super long ramp rate even if locally controlled. The point still stands. I really think it is a better solution to create a scene that is solely for the purpose of running the 8 minute ramp rate for the wakeup alarm rather than reprogramming the switch 2x per day and rendering the other scene controllers stuck with the 8 minute ramp during that time.

Rather than changing the scene ramp rate 2x per day, I would have suggested simply making 2 scenes. Both scenes have the exact same switches in them. 1) Scene 1 would be your normal use scene. This is the one that will have the switches as controllers and the regular ramp rate. 2) Scene 2 will have no controllers (only responders). This scene has an 8 minute ramp rate and will be activated only by your wake up program. By changing the ramp rate, you will not only be affecting the lights turning on by the program, but also if someone manually turns the light on during that time period. So lets say Olivia wakes up when the light is just starting to ramp up and wants full light, the only way to get the light on full brightness right away will be to go to the load switch and "fast on" it. NOTE: If your daughters light only has a single switch, then you need only make one scene. This is the 8 minute ramp rate scene. For manual use, the switch just works according to the "applied locally" settings and no scene is needed. This is how I have it for my daughters bedrooms since the overhead room light has only one switch.

That program would never have worked. When you close the door, the zone becomes normal, which re-triggers the program, ending the "wait", the "if" evaluates to false, running the "else", which is empty. You need to put the "wait 5 minutes, set light off" in the else clause.

The 994i accepts a zigbee radio attachment allowing both zigbee and insteon control. I don't know the details of zigbee support and whether only limited devices are supported or all devices are supported. I have to say, however, what is up with only Apple stores selling these? And what is up with the silly colors? For half the price you can get the Insteon bulb and be limited to that good old standby soft white. Maybe they are good for Christmas or Halloween decorations.

I just bought a new building for my office, gutted it, and used the CREE ceiling troffers instead of fluorescent in the new build-out. http://crseries.creeledlighting.com/ I primarily used the CR22 model. They are very good. The light they make is in no way a compromise. It has great color rendering, it is bright, and it is soft. They cost about double a conventional ceiling troffer but use about 1/2 the electricity and last 50,000 hours to 80% original lumen (of course I'm going on their word with that). So they should be maintenance free for the life of my office. My electric bills are half what the previous occupants paid (I also replaced the HVAC units and put in spray foam insulation). I did get back about 20% of what I spent on them in rebates from my local electric provider so the ended up costing about 1.5x what I would have paid for normal ones. Of course normal ones also cost you about $40/ea every 5 years or so for re-lamping in addition to double the electric use (and double the heat production which is important where I live).

In order to have a random shut off time you must have a wait. You are terminating a wait. As I mentioned, "stop program" only affects a program that is currently executing a "then" or "else" clause. The only way to have an "else" or "then" clause that lasts more than a split second (and thus has opportunity for a stop to be interjected) is during a "wait" or "repeat". . . mostly just "wait" since "repeats" without "waits" don't take very long either.

Stop program does not disable disable the program. It merely stops the current execution of a "then" or "else". It has no impact on past actions of the program or futures executions of the program either from its own "if" or by some other program initiating it. It is only useful to stop a program that is in a "wait" or "repeat" where a "stop" could be interjected. In the program shown in the jpeg earlier in this thread, the "stop" command will do nothing. That program is not running except for a split second at the "from" and "to" times. So you will be stopping a program that is not running. Look at the program summary page, if the program does not saying "running then" or "running else", then telling it to "stop" does nothing. Stopping an "idle" program is a non-action. Programs are not "running" between the "from" and "to" times, they only ran AT the "from" and "to" times (assuming there is nothing else causing it to run).

I think you don't exactly understand how they work. There is nothing to maintain at all. Once it is installed it is maintenance free. The only caveat is if the ISY is offline at midnight and continues to be offline past the "catch up" time you set into ISY on reboot, it will fall 1 day behind. But there is a simple fix to that, you run the "advance one day" program. Since I finished the program, I have not had to touch it once. The only "tedious" thing is that you have manually add the variable labels when first installed. The programs themselves can be downloaded and installed as is, no tinkering at all. And the best time to install this set of programs is BEFORE you start using up a bunch of variables for other things. It would be tedious to change the variable addresses, but you would only need to do that if you had a conflict because you already used those addresses for other variables.

ISY has no wild cards when it comes to dates. In other words, you can't do something like every Dec 5 and leave the year blank. I wrote a series of programs that use the variable function in ISY to fix the problem. Or, you can just do what you are already doing and spell out the exact dates for each year all connected with a bunch of "or" statements. The programs I wrote allow for pretty much any kind of recurring date function you might ever think of. http://www.universal-devices.com/mwiki/ ... _Variables EDIT: I just read your program more closely and what you are doing won't work at all. To write a single program and be able to not touch it again (for at least several years), it would need to go like this. (from 2012/12/15 to 2013/1/3 or from 2013/12/15 to 2014/1/3 or from 2014/12/15 to 2015/1/3 etc) and (time is from 4:30 pm to 10pm or time is from 7am to 8:35am)

What is powering your IO lincs during a power outage? If it is the generator, and the generator fails to start with a power outage, you won't get your email. The only solution I can think of is to put them on a UPS along with a dual band device to jump the signal over to a dual band PLM or other dual band device on the same power lines as a non-dual band PLM.

No. You do it in an Elk rule. And if you need ISY to do something use an Elk output as a flag.

Solutions: 1) Tell her how you want it done and expect it to be done that way. She is an employee, not your wife. 2) Disable "single keypress quick-arm" under the "area" menu. (also stops everyone else) 3) Why does it matter who is arming the system? If the system is armed by any mechanism to away mode, set the thermostat to unoccupied. If you want to limit it to certain hours, then add that in.