apostolakisl

No, I think you pretty much have figured out the only way to randomize running of a program. You could let the program run every day, but just randomize the start time and the duration time. Not exactly the same, but this is how most people would do it and it gives the impression someone is actually living there all the same.

Yes, you have a router that doesn't support the ISY auto config. You will need to manually set your router to port forward to ISY. I suggest using the secure port (443). I assume your isp has not given you a static ip, so you will need to setup a dynamic dns server. dyndns.com can guide you through that. Probably your router has a page dedicated to that function, but if not, you can run an application in the background on your pc. You need to give your ISY a static IP address if you haven't already done so. Go to your router page and find the port forwarding section. Set port 443 to point to whatever IP address you gave the ISY (like 192.168.1.xx). Now, from any internet connection, type in https://www.thenameyousetupwithdyndns.com and it will take you to the ISY.

It's every switch I have set to beep. 2476d's 2476s's 2476db's All of my switches are about 2 years old or less as I replaced essentially all of them for the paddle issue. If I sort the log by "beep" it is 100% of them that do the error.

OK, but then why does it happen? I have about 5 programs written like this to beep the switch a minute or so before it is going to be flipped off. All of them appear to be giving the nack every single time they receive the beep command. The beep does beep. Also, how does the duration number work? As I mentioned it seems like the beep sounds the same no matter what the number.

Well, I bet you can do it. Setting up a CAI to just monitor temp is a lot lot easier than setting up an ISY. Just connect the temp probe, connect the power cable, connect the cat5, log into the unit, enroll the temp sensor and give it a static ip address. Create a temp variable in isy. Run io_guys program and enter the cai and isy's ip address. It will find the units and populate the variables. Then set the temp in cai to update the isy temp variable. Done

If you have an Elk security system and the module then you can do it that way. Another option is to get a CAI Webcontrol ($35) and a temp probe for it ($5). Then load io_guy's syncing program which will keep one of the variables in ISY set to the current temp. This will require that a computer is left on with io_guys program running in the background.

I noticed in my log that every time one of my switches beeps as a result of a program telling it to, I get this error log. This is true for multiple programs working on different switches. All programs have the same structure. The switch does beep as expected. Also, if someone could tell me what the number next to beep duration means. I have set it to different numbers and don't notice anything different. Kitchen / Pantry-Light L Beep 100 Thu 2011/12/08 02:50:45 PM Program Log Kitchen / Pantry-Light L Beep 100 Thu 2011/12/08 02:50:45 PM Program -1 If Status 'Kitchen / Pantry-Light L' is not Off Then Set 'Kitchen / Pantry-Light L' 100 (Beep Duration) Wait 30 seconds Set 'Kitchen / Pantry-Light L' Off Else - No Actions - (To add one, press 'Action')

I would not have pushing the keypad link button turn the lights off and lower the furnace. Instead, I would have the "armed away" status of the alarm do that. Then no matter how you arm the system the lights will turn off and the furnace shut down. This is how I have my home system. And I agree with the above method of linking the two keypad link buttons into one scene. Then using the scene status to set the alarm. In addition to that, I would right a program that turns the scene on when the system is armed away. In this way, if you arm the system using a different method, the button will still light up.

I have a chicken coup with a home made automatic door opener. I am using my Elk to control it but that I could be using the ISY just the same. I use an RF relay to control it. I soldered the remote controls button terminals to relays on the Elk which causes the remote to send the signal to the RF relay unit in the coup which closes or opens the door. It works great. This is the RF relay I bought: http://www.ebay.com/itm/130545242235?ss ... 1439.l2649 I used this set of double pole relays since each button closes 2 contacts. http://www.ebay.com/itm/130589816898?ss ... 1439.l2649 The double pole relays are connected to 8 outputs on the Elk. When you turn an output on the elk on, it powers up one of the relays on the dpdt board. This closes a contact on the rf transmitter which sends the signal to the rf receiver which closes a relay which powers the motor that closes or opens the door. Now that I have the ISY/Elk module I could use ISY to control it. If I hadn't already set it up in ISY, I would do that, but why bother now, it works as it should. It takes a little patience to solder up the 32 wires necessay to control all 8 buttons (th

I was thinking, it might be possible to take an old strand of lights that don't work, cut off the wire from the pass through plug they come with, solder the resistor to the little stub of wire and shrink wrap it with that insulation srink wrap stuff. In this fashion, you will have a very small solution that also has a pass through plug. It will be 99.99% invisible.

I don't really think it is a good idea to take your lamplinc appart and void the warranty and possibly screw it up. It really is so easy to just put a tiny little load on with the led lights. If you really wanted something tiny, you could experiment with resistors and find the highest rated resistor that drains off enough juice to stop the led's from glowing. Just stick the two leads into the female part of one of your strings of light and see which ones get the lights to shut down. Of course only do this with the lamplinc off (only the sensor current flowing) so as to avoid getting shocked. Once you determine the best resistor, wire it up to a plug, insulate it, and plug it in to the string of lights.

Yes, I learned of this last year. The devices are not malfunctioning. They normally "leak" a micro amount so that they can tell if you manually turn the attached device (light) on/off. The thing with LED's is that they require only milliamps to start to light up. If you want to block this from happening add another load. A wall wart does the job.

They are mostly around $40 or $50. ISY takes care of all the linking. It stores all the info in its database, which you can backup. You can restore devices and replace devices and with a single click it re-writes all the links.

2 things I think of. 1) Sunset is after 9:40 (unlikely in Dec) 2) The load on the plug is a signal sucker or noise producer. What do you have plugged into it? CFL or incandescent? CFL's can cause troubles.

Yes. At sunset plus 20, the then clause will run At 10pm the else clause will run. So what isn't happening. The sunset part or the 10pm part or both? In your program summary page, does it indicate that the program ran and at what time? Did you double check that you saved the program and that it is "enabled"?

I have tried to reproduce the problem and I can't. It just happens every once in a while. Perhaps if I stood there and tried 100 times I might get it to do it. Or maybe not. This tells me that there is not a problem in any of my programming logic but rather some intermittant error in either sending of the correct insteon address when I hit button b, or the interpretation of the address at the level of ISY. I kind of doubt it has anything to do with power line issues. I would expect noise or poor signal throughput to just fail, not get mis-interpreted.

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.