apostolakisl

Sorry oberck, my mind was focused on the kpl when I said "only the off button should initiate the program", I was trying to convey that exclusive of other kpl buttons. As I look at the log, it appears that these two lines. Master Bedroom / Master-Cans over Bed L On 63 Thu 2011/12/01 11:11:34 PM Program Log Master Bedroom / Master Bedroom Keypad On 63 Thu 2011/12/01 11:11:34 PM Program Log are indicating that a program has turned on the lights to 63 (to 25%), and then later you can see a status 25% reporting. The log at this detail level doesn't include actions taken on switches, so i can't tell if ISY received an off press or if it otherwise erroneously triggered the program. I am not sure if I feel better or worse that gviliunas also has the problem. I do appreciate the info and the fact that replacing the kpl did not fix the problem. This will save me that trial and error.

There are two switches. 'Master Bedroom / Master-Cans over Bed L' is a 2476D, it is the load 'Master Bedroom / Master Bedroom Keypad' is a 6 button KPL with this address being the main on/off The program works correctly almost all the time. Meaning that, if I phyically turn the master KPL off, or the 2476D off while the light is already off, it turns on to 25%. If the light is anything but off, it does nothing (evaluates false). But every once in a while, if I turn button b off while the 'Master Bedroom / Master-Cans over Bed L' is off, it runs the program. Last night for example, my wife had already gone to bed. The lights were off and she was asleep. Both switches correctly indicated that the cans were off by their LED's. Button B was lit as it should be since there were still lights on in the house. I pushed button b, the led shut off and the house lights shut off (as they should). HOWEVER, the overhead cans turned on to 25%, it woke my wife and she was annoyed. This is a BAD thing!!! I can only assume that button b's address is being mistaken for the master address by ISY. Either that or button b is sending the master address. Except, if that were the case, then the proper program for button b wouldn't have triggered (but it did trigger). You will notice in the log that button b turned on/off in their after the initial event. This is becuase I have button b track the status of a whole bunch of lights. All of those scenes take a few seconds to actually turn all the lights off so button b's back light will end up turning back on then off again depending on which lights were on and how long it takes for them to all get shut off by the program. Here is the log Master Bedroom / Master Bedroom Keypad / Mstr Bed Key B all off Status 0% Thu 2011/12/01 11:11:29 PM System Log Scene:Family Rm Ceil S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Kitchen Puck S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Kithchen Island S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Upstairs Hall S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Patio Lts S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Frt Foyer Chandalier S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Exterior Lights S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Dining Rm Chand S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Barrell Hall S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Scene:Back Hall S Off 0 Thu 2011/12/01 11:11:31 PM Program Log Kitchen / Butlers Pantry-Puck L Off 0 Thu 2011/12/01 11:11:31 PM Program Log Garage / Garage-Floures L Off 0 Thu 2011/12/01 11:11:31 PM Program Log Breakfast Room / Breakfast Rm-Chand L Off 0 Thu 2011/12/01 11:11:31 PM Program Log Kitchen / Kitchen Intercom-Puck L Status 0% Thu 2011/12/01 11:11:31 PM System Log Kitchen / Kitchen Micro-Puck Status 0% Thu 2011/12/01 11:11:31 PM System Log Kitchen / Kitchen Corner-Puck Status 0% Thu 2011/12/01 11:11:31 PM System Log Family Room / Family Rm-Over MantleLt L Off 0 Thu 2011/12/01 11:11:32 PM Program Log Kitchen / Kitchen-Over Sink L Off 0 Thu 2011/12/01 11:11:32 PM Program Log Scene:Night Routine S Off 0 Thu 2011/12/01 11:11:32 PM Program Log Living Room / Living Rm-Couch Lamps L Off 0 Thu 2011/12/01 11:11:32 PM Program Log Living Room / Living Rm-Wine Rm L Off 0 Thu 2011/12/01 11:11:33 PM Program Log Scene:Master Keypad B On 255 Thu 2011/12/01 11:11:33 PM Program Log Master Bedroom / Master-Cans over Bed L On 63 Thu 2011/12/01 11:11:34 PM Program Log Master Bedroom / Master Bedroom Keypad On 63 Thu 2011/12/01 11:11:34 PM Program Log Scene:Master keypad A Off 0 Thu 2011/12/01 11:11:34 PM Program Log Scene:Master Keypad B Off 0 Thu 2011/12/01 11:11:34 PM Program Log Scene:Master keypad A Off 0 Thu 2011/12/01 11:11:39 PM Program Log Scene:Master Keypad B Off 0 Thu 2011/12/01 11:11:39 PM Program Log Master Bedroom / Master Bedroom Keypad / Mstr Bed Key B all off Status 100% Thu 2011/12/01 11:11:40 PM System Log Scene:Master Keypad B Off 0 Thu 2011/12/01 11:11:40 PM Program Log Master Bedroom / Master-Cans over Bed L Status 25% Thu 2011/12/01 11:11:40 PM System Log Master Bedroom / Master Bedroom Keypad Status 25% Thu 2011/12/01 11:11:41 PM System Log Master Bedroom / Master Bedroom Keypad / Mstr Bed Key A Kitchen S Status 0% Thu 2011/12/01 11:11:41 PM System Log Master Bedroom / Master Bedroom Keypad / Mstr Bed Key B all off Status 0% Thu 2011/12/01 11:11:42 PM System Log Scene:Master Keypad B Off 0 Thu 2011/12/01 11:11:42 PM Program Log

If Status 'Master Bedroom / Master-Cans over Bed L' is Off And ( Control 'Master Bedroom / Master-Cans over Bed L' is switched Off Or Control 'Master Bedroom / Master Bedroom Keypad' is switched Off ) Then Set 'Master Bedroom / Master-Cans over Bed L' 25% Set 'Master Bedroom / Master Bedroom Keypad' 25% Else - No Actions - (To add one, press 'Action') The above program on several occasions has run when I turn button B off. The keypad listed in the program above sits next to the bed and is a 6 button kpl. I have set button "b" to initiate a program that shuts most of the lights in the house off. What has happened on several occasions is that the above program runs, despite the fact that I did not push the main "off" on the kpl. Only the main "off" on the kpl should initiate this program. Why is it running (only rarely) when I shut "b" off?

If only it were that easy. Unless you have a $1000 oscilliscope and the knowledge to use it, it is all a guessing game. Some stuff is obvious, like you turn a cfl on and all hell breaks loose. Other stuff is just random and hard to pinpoint. Just about any wall wart can make noise as well as computers and other electronics. For me, I had a low voltage transformer for low voltage lights that reaked havoc. But that was obvious. I wish I could tell you more.

Hi Michel et al I'm resurrecting an old thread because I just received a new PLM in the mail. I unplugged the old PLM, plugged in the new, connected the Cat 5 to the ISY and powered the ISY with a new power supply (since the new PLMs don't do that apparently). I then logged onto the web interface and was given a warning that it could not communicate with the PLM and that was usually the result of a defective PLM. Figuring that this was probably the result of adding the new PLM, I went to File|Restore Modem (PLM). It failed around 30% or so twice with the message Failed Resetting the PLM [-200000/-30] Am I doing something wrong? I just replaced a PLM as well and can report a possible reason. When I booted my ISY, I did not have the data cable connected. I connected it just a bit later. I did then get the same error you are getting. I then tried leaving the data cable between the PLM and the ISY connected. I unplugged both the PLM and the ISY. I did a factory reset on the PLM as I plugged it back in (held the button for 3 seconds). Then I powered the ISY. Then I restored the PLM from ISY and it worked.

What we have here is a failure to communicate. Sorry, couldn't resist. But, just like you can initiate a scene by pushing a button and one or more of the devices may fail to get the message, the plm may fail to get the message. The better your mesh and the less noise you have in the system the less likely this is to happen. But I would not recommend a system wide query every hour. You will find that the traffic at that time will create troubles with executing scenes and programs. I have a system wide query run at 3am so as to avoid issues with my usage during the query.

ISY does not assume the status. Every switch is linked to the PLM, similar to how switches are linked together in a scene. The PLM thus is informed of every action taken on every device and relays that info to ISY. ISY could get out of sync if there was a failure of communication between the device and the PLM. If your ISY is not reporting the correct status of a switch, it may not have been properly linked to the PLM. You should be able to walk around your house with a laptop and watch the status of every switch change as you turn it on and off, instantly. If you replaced your PLM at some point and didn't do a "restore" on the new one, then none of your switches will be linked.

You should not need to do that. If you have switches getting out of sync then you should try to figure out how to make the communication failure go away. Querries do put traffic out on the network. If you are just doing one switch, that is minimal. If you are doing all switches in a large installation, that will definitely clog your system up for as long as the querry takes. If you have 50 or 60 switches that could be 30 seconds or so.

Regarding number 2. I have a global cache Itach unit. It allows ISY to send IR. ISY has IR receving built in (if you buy that model). Currently I use a Harmony 890 and have it intigrated with the ISY. My intention is to use a tablet and have Itach execute all of my remote commands. There is a good ipad app for that. I have android and there is an app for it too, but I haven't had time to figure it out. Anyway, it all can be integrated with ISY because it can receive IR and can send IR using the network module/itach. Also, with Itach, you can have lots of them and ISY can send commands to each one individually. The itach work on wifi so you can put them all over the house.

OK, I have removed some defective devices since installing that old PLM.

So, I got a new dual band PLM and 4 dual band switches to strategically locate so that I can hopefully get my hop count down to 1. I powered down the system and plugged in the new dual band plm and powered up the ISY, but I neglected to plug in the serial cable between the two until after all was powered up. I think this caused the problem. I went ahead and did the restore PLM. It looked like it did the restore and then wrote new links to all the devices. Then I checked the PLM links table. . . . 0! The PLM wouldn't track any devices as expected. I tried repeating the restore it took about 2 seconds and wrote nothing. Now, I had no backup. Stupid right? I had a 6 day old backup but I had changed a bunch of stuff. Almost entirely programs. I can't remember, but I might have added a device to a scene. I did not add any new devices. I saw no way out but to backup my programs and then resotre the ISY to 6 days ago putting the old plm back on. Then I started the restore process all over again and this time it worked as expected. I then deleted the programs and restored the backup programs so I got all that back. Here is the question. I had a plm link count of 273 on the old plm I have a plm link count of 266 on the new one. What gives? Do I need to worry about this? All seems to be working. Should I just assume there were some orphan links?

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.