apostolakisl

Yes, your PLM somehow does not have the switch linked. The PLM is kind of the ISY "device". Every switch that is installed via ISY gets the PLM included in the "scene" (not actually a scene, but same concept). Once the PLM is in the "scene", ISY then becomes aware of everything that happens to that switch because the PLM gets updated. Is this the only switch that is doing this? Did the switch ever report in the ISY gui? You may need to uninstall the switch and then reinstall it so that ISY writes the links to the PLM. If all of your switches are having trouble then you may need to restore the PLM or maybe you need a new one.

Lee is on the mark. I have a variable I call "Light.outside". It sets to 1 when the sun rises and 0 when the sun sets. So anything that you want to happen while the sun is up includes "if $light.outside is equal to 1" as one of the conditions. so If $iLight.Outside is equal to 0 and From 6:20am To sunrise plus 30 Then Set couch light on Else else set couch light off One note, the light will get turned off at 6:20 if the variable is equal to 1 (or in other words, if 6:20 is after sunrise). You might not want that and if so you need to split the "off" part into another program. Also please note, you need to use an integer variable. A state variable would trigger the program every time it changes and potentially run the program at unintended times or force an "else" to execute that you didn't want.

This is why the program isn't working. As Michel stated, you don't have links. If restoring the device doen't work, you might try removing the device entirely from ISY and the re-installing it from scratch. When I select "Tools / Diagnostics / Show PLM Links Table" and then click on "Start", I only see one line... 0000 : E2 00 00.00.00 00 00 00 When I press "Count" the result is "1". Should the PLM Links Table show ALL of the links in the PLM? Yeah, that's not good. You might have a dead plm? Or maybe somehow it just got scrambled and you can factory reset it and then restore the PLM.

This is why the program isn't working. As Michel stated, you don't have links. If restoring the device doen't work, you might try removing the device entirely from ISY and the re-installing it from scratch.

That program should work. Check to see if ISY recognizes the button turning on when you push the button. Go to the "main" screen and highlight that button on the tree. It should show "on" or "off" as you push the button on/off on the right side panel. I suspect you either have some labeling issues with the button (you have buttons confused) or you are having a communication issue between the device and ISY. Also, make sure the program is "enabled" and saved.

Take the cover plate off of the switches so you can read the address off the switches. Enter the addresses of each switch into ISY manually giving it an appropriate name. Create folders if appropriate to help you stay organized as you get more switches. When it asks you if you want to clear all links say yes. Then use ISY to create new scenes. Right click on the switches you want in each of the scenes and add them (or drag and drop). For a virtual three way you want all the switches set as controllers. You can then set your on level and ramp rates for the switches when acted on directly (by clicking on the lone switch in the tree) and when responding to the scene (by clicking on the scene in the tree).

I know what he is talking about. Sometimes the java console just looses it's connection. It only happens when the java console has been running for a long time, like a day or two. As far as I know, no, when it looses it's comm, you just have to shut it down and re-open. If you are loosing comm often, then you should look into the cause of that, not how to refresh out of it. I have also noticed that sometimes the java consolue starts eating up processor. Again, only if it is up for a long time. Perhaps it has some endless loop running away. If I notice that my fan has kicked into high gear, I will check the task manager and see that java is running the processor at 50% or more. I shut it down and re-open fixing the issue.

There is a "random" box that you can check on the "wait" and "repeat" commands. So, write your program to execute at some time, say 8pm, then the first "then" line is a wait command for say 20 minutes. Then put a line to do something like turn a light on. The result will be that the light will turn on at some random time between 8 and 8:20. If Time is 8:00:00PM Then Wait 20 minutes (Random) Set 'Light' On Else - No Actions - (To add one, press 'Action')

Another way to say this would be that this: If From 7:00:00AM For 1 hour Then Set 'light' On Else - No Actions - (To add one, press 'Action') Would be the same as these two programs: If Time is 7:00:00AM Then Set 'Light' On Else - No Actions - (To add one, press 'Action') If Time is 8:00:00AM Then Set 'Light' Off Else - No Actions - (To add one, press 'Action')

You need a 3.x.x firmware. Don't forget to clear your java cache. You may consider 3.1.10 rather than the most recent if you would prefer to stay clear of all the brand new Elk stuff which still has a few bugs.

Two things: 1) The "fins" are the extensions of alluminum at the top and bottom that extend out further than the width of the plastic housing. They can be snapped off if you are putting multiple switches next to each other, but that reduces the heat sink. 2) The chandalliers you have are different than I thought. I was thinking the small bare-bulb ones with the small base. I think your bulbs may have the full size base (a19). Plus, they look like they are hidden by a decorative glass piece. My point being, if indeed this is the case, you should definitely think about going with LED. You can get 60 watt eq in those bulbs that only use about 10. Insteon works just great with every led bulb I have ever tried and LED's usually dim pretty well. Make sure you get 2700k bulbs, however.

It could be the type of load. Resistance vs Inductance. Usually wattage is listed for resistance loads and amps or volt-amps for inductance. They may also be hedging a little on the wattage since they assume an in-line linc is going to be in a sealed up space.

Questions: 1) I am using 4.6.8 firmware on the Elk. Elk has the 4 series and the 5 series depending on which wireless system you use. I use neither, so 4 or 5 are both fine for me. It seems that most people are running the 5 series. Should I switch? Was the ISY firmware/module designed more for one or the other? 2) Also, my bootware is one revision old. According to the release notes, very little changed. In addition, there isn't anywhere on Elk's website to download the latest bootware. Could the bootware be having any impact? (3.3.2)

I agree. I think you need to go up the ladder. If you have incandescent bulbs, you will need to head up there anyway every 2000 hours of use. I don't think you can switch to led. I have never seen a chandallier bulb that is more than 25 watt equivalent (3 watts). Maybe I'm not looking in the right place. Putting an in-line linc at one or more of the chandalliers is the only option I can see. Or using 45 watt incandescents instead of 60.

Same here I submitted a ticket with access details. Did you try power cycling the ISY?

Did you clear your java cache?

I think I am going to skip the export/import and just re-write the rules as programs in ISY and delte them from Elk. It looks like the module does not include any provision for "tasks". I am trying to figure out how it would work to get ISY programs to respond to a task executed from an Elk keypad.

Is it possible that installing the Elk module has changed the indexing of lights on elk side? Since installing the module, Elk executed rules are now controlling the wrong lights.

So far this all seems very simple and self explanatory. You guys included a ton of stuff, even individual keystrokes on the keypads. The main question I have at this point is what things will act as triggers. So far, everything I have tested behaves as a trigger.

Installed 3.1.12. It needed a power cycle after the install as it locked up. After the power cycle all seems to be fine. Installed Elk module. No problems there. So far so good on playing with the Elk zones/outputs/status'/etc. Just doing some stupid stuff right now. ISY makes the security system say "seven" when I open the back door. Good news is, that is what I programed it to do!

Your program is written properly. I have multiple programs with an identical if section that work. There is something else wrong.

I have several programs like that using icon dimmers, so it isn't the icon dimmer. Just to be sure, check that the program is saved and is enabled. The ISY might not be getting good com with the switch so it may think the light status is not "off" when you are hitting the "off" side of the switch. Check the status of the light on the ISY console before hitting the "off" button. Then check to be sure the program ran by looking at the "last run time" in the program summary page and make sure the program ran.

Please copy and paste the actual program from ISY. In the program details screen, right click on the program in the three on the left and hit "copy to clipboard". Then paste it to the forum. The program should be true any time it is triggered between those time slots by turning on either of those two lights. The other possibility is that you are not turning those things "on" but rather have them at some percentage of on. You could try changing the language to "not off" instead of "on". If From Sunset + 1 hour and 20 minutes To Sunset + 2 hours and 22 minutes (same day) And ( Status 'Kitchen Ceiling Keypad - A' is not off Or Status 'Fam Rm Table' is not off )

Yes, for all intents and purposes, unlimited. It recovers just fine from power outages with accurate time and date. It also will checks an NTP server per your instruction. It also gives you options on how to handle recovering from a power outage regarding execution of programs that may have been missed. In addition, it only draws a few watts (7 seems to ring a bell) so you can put it on a UPS and it could run for days without killing the battery.

You may be having some conflicts. Your program 1 and program 2 share many of the same triggers and could be in conflict with one another. As an experiment, try disabling program 1 at some point during that time period after sunset and then turn on that keypad or lamp listed in the program. I suspect the program will work (must have those parenthesis properly placed). Assuming it does, this points to program 1 as being in conflict.