Michel Kohanim

C Martin, Excellent post! The first thing you should do is to use http://www.universal-devices.com/beta instead of the Logon to MyISY URL simply because I know for a fact you are running the Beta 2.5. If you use the Logon to MyISY URL, you will have a client/firmware mismatch which explains why you don't see the tabs on either of your IMAC and Vista. Next, My Ligthing should appear in Network dialog in Vista. This has been thoroughly tested and currently used by many ISYers. If you don't see My Lighting in Network, then you might have setup your Vista Network for "Public" places which prevents all UPnP traffic. In order to access ISY directly (without going to our website), please do the following: 1. Go to our website using http://www.universal-devices.com/beta 2. Login to the Admin Console 3. Choose Help->About and write down the value for My URL 4. Create shortcuts and/or put that URL in your favorites in Safari The only problem with step 4 above is that ISY might be given a new DHCP assigned IP which causes your shortcuts/favorite links not to work in the future. To alleviate, you have three choices: A. Make ISY use static IP address B. Configure your router to make ISY's DHCP lease permanent C. If your link fails, simply redo steps 1,2,3,4 above With kind regards, Michel

Hello Ron, Apologies for the delay in my response. YES. Absolutely! You can trigger/schedule scenes. Simply look for the name of the scene in the "Then" block. And, as per Mark's comments, all you have to do is to keep that button in the scene. Are you trying to do something more elaborate? With kind regards, Michel

gatchel, The documentation you are referring to, alongside all the other new features in 2.5, do not exist yet and shall be available when 2.5 is released. At a high level, the procedure is VERY simple: 1. Configure your lights/scenes the way you like them within ISY 2. On the Configuration tab, choose ELK and enter the ELK's M1XEP's IP and Port. Click on Save ... now ELK will communicate with ISY over the network 3. On the same pane, click on Export ELK Configuration and save it to a file 4. Go to ELK RP, right mouse click on lighting, choose Import. In the ensuing dialog choose Universal Devices' ISY-26, and then choose the configuration file exported from ISY 5. After the import is done, choose "Future Use" column for all the scenes/devices for which you do NOT want X10 commands sent out (X10 slows the response time) 6. Save it to ELK (using the Send button) That's about it. With kind regards,

Mark, That's the whole point: whatever is linked to your CL is turned on/off when you click on the All On/off button. If you want all your lights to be controlled by All On/Off, then you have to have all your lights linked to at least one of the buttons on your CL. What you are witnessing has nothing to do with the 6th phantom button. With kind regards, Michel

Hello aLf, There's no hard limit. The only trouble you may run into is that your logs (default is 3MB) are going to get full, have to be truncated, and start back from the top which is a resource intensive process during which time, in all likelihood, ISY will not allow any other operations to complete. With kind regards, Michel

Mark, You don't have to set them up. By assigning different devices to different buttons, they automatically end up in the All On/Off for that CL. With kind regards, Michel

Mark, As I mentioned before, we already do support the All On/Off button on CL, RL, and ISY. At the moment I don't see why we would want to support a phantom button regardless of the level of difficulty since there are much more important features to implement. With kind regards, Michel

mdcastle, I am so glad that your upgrade was installed without incidence. Please do not hesitate to contact us if you have any other questions/comments/concerns/suggestions. With kind regards, Michel

Mark, Because we have to know the status of physical buttons ... dealing with phantom buttons is like dealing with ghosts: you might experience strange behavior and not know where it came from. With kind regards, Michel

Mark, That feature has been available for a very long time now. The only thing we do not support is the 6th button on the ControLinc. With kind regards, Michel

Hello upstatemike, No! ISY does not support phantom buttons. All on/off are already supported by the virtue of your INSTEON devices being linked to the PLM. As such, you can use My Lighting to send an All on/off to the whole system. With kind regards, Michel

Hello Brian, Yes, it is possible in our 2.5 release which we are now beta testing and which you can use to test your scenario. With kind regards, Michel

sloop, The PLM does not care about whether or not your KPL controls a load and, therefore, you still have 422 links! With kind regards, Michel

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