Michel Kohanim

siegeld, You can do this using the same onTriggerStatus callback. Simply look for the event associated with your program! With kind regards, Michel

siegeld, Thanks so very much. I think I am beginning to understand what you are looking for. Have you ever tried using the onTriggerStatus() callback? This function is called when any of the triggers change state (i.e. are run/stopped/idle, etc.). Adding a JSDK event is an excellent idea and one which we'll review and in all likelihood implement. In the short term, you can create a program with an empty Then block. Every time that program is run, onTriggerStatus() is called within which you can trap your specific event and do as you wish. As far as a scene being turned on, we do not maintain the state of the "scene" that's why you don't get any notifications of the status. What does it mean that a scene is turned on? With kind regards, Michel

mdcastle, Apologies for the inconvenience. As MikeB suggested, going to our Web URL (http;//www.universal-devices.com/MyInsteonISY) will fix the issue. The problem has to do with a bug in 2.4 where the state of the Admin Window is captured even though minimized. In all likelihood, you closed the Admin Console while minimized. May I humbly suggest upgrading to 2.4.12? With kind regards, Michel

mdcastle, For what you want to accomplish, 2.5 Beta is much more flexible. I have already send you the instructions on the upgrade. Please do let me know how it goes. With kind regards, Michel

Mark, You are being picky! Nonetheless, I don't see any harm moving it to the end. Consider it done. Thanks so very much. With kind regards, Michel

Mark, I do not consider this a bug and thus I cannot consider the change a fix. Furthermore, there are some ramifications with need more investigation: a. If you want a trigger based on the "level" of a KPL/CL/RL button. i.e. you are dimming a scene to 40% using any of those buttons and you want the trigger to run only when you are below/above 40%. In short, the "logical" level of any one of those buttons closely (but not 100%) reflects the collective/average level of all the members of that scene b. In most cases, the status of the KPL sub-buttons actually reflects whether or not the back-light for that button is on/off There are other ramifications which are a little less important. With kind regards, Michel

Rand, Precisely. Thank you so very much. Mark, Yes, this is the compromise between color coding everything vs. those that are only controllers in a scene. With kind regards, Michel

upstatemike, Good plan. I still have to get back to you with respect to HomeSeer integration. I haven't forgotten and it's on the list of my things to do in the coming days. I shall keep you posted. With kind regards, Michel I Have the original SmartHome X-10 translator which is a PLC PowerHome uses a PLC Homeseer is currently a PLC but will be switched to a PLM EZX10RF is PLM based? EZIO8 has a PLM My Plan: Install a W800RF32A on my ELK panel and connect the ELK to an ISY 99.9 This will let me eliminate both of the EZ units and the X-10 translator. Convert Homeseer from the PLC to a PLM (Homeseer will not support the PLC in future releases. Not sure how ISY and Homeseer will work together yet. PowerHome only supports the PLC at this point but I will likely take it off line when I bring up the ISY. So the short answer is that I don't plan to keep any PLCs and just have to figure out how to work with Homeseer's PLM. Would be nice if Homeseer communicated to the ISY over the network like the Elk so I could have only 1 Insteon interface to manage.

Rand, As usual, I couldn't have said it better: ControLincs/RemoteLincs/Keypad Sub-buttons do not have status because they do not control a load. This said, however, ISY maintains the "previous" state of these buttons as if they had a load. Maybe we should get rid of these states but, especially in the case of keypadlink sub-buttons, these states indicate the status of the backlight. mdcastle, First of all, I am so glad you got everything working. As Rand suggested, you should use If Control ... Please do let us know if you are still experiencing difficulties, With kind regards, Michel Again, I don't know how a ControLinc button can have a status, it has no load and cannot be switched in any manner other than manually pressing a button. To look for a Status you must query a device that has direct control of a load (SwitchLinc, InlineLinc, LampLinc, etc.). Hope this helps, Rand

GPG, No problem at all. For EZIO: Each Input takes 2 links Each Output takes 1 link With kind regards, Michel

Hi Mark, I think you should post this question at techmall! With kind regards, Michel

upstatemike, ISY can support 512 device/scene combinations. Right now, you have a maximum of 400 distinct INSTEON buttons (nodes in our vernacular). That leaves you with 112 scenes. The current PLM (v. 52), though, will not support your number of links. You would either have to use their Beta (which supports 1600 links) or wait for its official release. X-10 Translator does not take any links if you use ISY for triggers/actions. How many PLCs do you have? I still have to get back to you with respect to HomeSeer integration. With kind regards, Michel

Mark, Thank you so very much. GPG, I am going to work with Mark to get the numbers in there for EZRain. As far as EZIO, ISY has stopped working with any of the new firmware versions of EZIOxx especially those attached to/using PLM v.52. Unfortunately, it's quite impractical for us to support devices for which we are not notified of the changes in behavior, APIs, and ramifications between different revisions/versions. Therefore, our support for EZIOxx devices is currently as-is and unofficial. In this respect, then, I feel a little hesitant adding EZIOxx in the list. With kind regards, Michel

Mark, Precisely. The new PLM works at 75% and thus you should expect a lot of communication problems. With kind regards, Michel

RLIKWARTZ, My pleasure. With kind regards, Michel

RLIKWARTZ, Apologies for the delay in my reply. We were trying to test this scenario and unfortunately could not reproduce it. This said, however, I do have a few more questions (if you don't mind): 1. Did you follow up your File->Restore ISY with File->Restore Devices ? 2. The numbers you are referring to, say 50% etc, are they the numbers in the Status column on the table on the top part of the view (to your right) or the values of the sliders at the bottom half of the view? With kind regards, Michel

mdcastle, Thanks so very much for the status update. There's one more request which I'd appreciate your help with: would you be kind enough to do File->Restore Modem (PLM). This will let us know whether or not we are dealing with a known PLM bug for which we already have a work-around. Also, would you be interested in our 2.4.11 (Beta 2.5)? With kind regards, Michel

RLIKWARTZ, Why would you backup and restore after deleting and recreating all your scenes? What did you actually restore? Also, what do you mean by? With kind regards, Michel

upstatemike, Yes, all information will be available at EHX Yes, IR will be an optional addition No, there are no trade-offs except for $$ Yes, ELK integration remains intact With kind regards, Michel

mdcastle, Thank you. You have identified the problem: ISY is not updated with the status of the button presses on your ControLinc. In normal cases, all buttons should report back their status to ISY. There are three cases when a ControLinc does not report back its status to ISY: 1. When linking the ControLinc, you chose the third option to "import existing links" and in the existing links there are conflicting information 2. The ControLinc button is assigned as an X10 button (some ControLincs only) 3. The PLM, for some reason, does not have the correct links to "listen" to ControLinc initiated messages May I humbly suggest the following: 1. Factory Reset one of your ControLincs (this also removes X10 associations) 2. On Admin Console, please right mouse click on any one of the ControLinc buttons, and choose Restore Device 3. Please wait for the restore to complete and then check to see if the status of the buttons are updated Furthermore, would you be kind enough to do Help->About and let us know ISY's firmware version. Thanks and with kind regards, Michel

mdcastle, The reason that the ControLincs have status is precisely for triggering purposes. If you click on your ControLinc buttons, do you see their status updated on ISY? Are you saying that only two of the buttons on ISY have their status updated? Would you be kind enough to send us the program you are trying to run? With kind regards, Michel

Hi Rowland, Are you trying to reverse engineer our product Button associations are not stored in the link database. They are memory locations in the KPL itself that you have to play with. How did we do it? Pretty much some very interesting code inside ISY! Thanks and with kind regards, Michel

Hello black_fx_35, 99.9 comes in two flavors: with IR and without IR support. The IR version will not be generally available till early December (only sent to our distributors/partners before then). With kind regards, Michel

aLf, It was a pleasure! With kind regards, Michel

Hi Frank, Yes! So, the program runs until it receives the Off in which case it stops running till it gets the next On. With kind regards, Michel