Michel Kohanim

Hello someguy, No, it should not show those buttons because they are not applicable to the folder. This is a bug. With kind regards, Michel

Hi pleo, I would have to echo LeeG's observation. It's also possible that you have other programs that turn that light on to 100%. It would be best to disable all other programs while testing. With kind regards, Michel

xd40, Just to be sure, I created a test program which calls 3 different programs each one of which send an email to a different recipient: If Status 'adf / blah blah' is On Then Run Program 'email 1' (Then Path) Run Program 'email 2' (Then Path) Run Program 'email 3' (Then Path) Else - No Actions - (To add one, press 'Action') This works as expected. As I mentioned, unless the condition causes the program to stop, all programs should be called in sequence. i.e if the status of the lamp adf/blah blah becomes off during the execution then everything stops. With kind regards, Michel

Hello me23, I must emphasize that 2.7.15 has absolutely nothing to do with intermittent communications problems. You are welcome to go to a previous release to test. What I would do is to move the PLM/ISY to some other location to see if there are any changes in the pattern. If yes, then the problem is that there's something in the original location causing all these issues. If not, then I would have to suspect the PLM. With kind regards, Michel

Hello pleo, What happens if you try to dim/brighten using the main screen? With kind regards, Michel

Hello xd40, Please note that Mutex buttons are only active locally (i.e. when you press the buttons on the switch). If you do anything with them in scenes where other controller control them, then the KPL responds as if there are no mutex buttons. With kind regards, Michel

Hello xd40, Perhaps we are not talking about the same thing? You can call as many programs (run if/then/else) from the main program. The only time the execution stops is IF the condition of the calling program has been invalidated. With kind regards, Michel

Hello someguy, All On/Off are precisely All [devices] on and off. The bug is that these buttons should NOT be visible when clicking on a folder. With kind regards, Michel

Hello xd40, Yes. In the meantime, you can actually call other programs from within your current program. You can even call the If, Then, or Else segments of all other programs. With kind regards, Michel

My pleasure Illusion. We are still trying to figure out if we can put ELK in our next release and thus the hold up on the next release. In short, support for this device should be in our next release. With kind regards, Michel

Hello me23, porboy911 has an excellent point! It's quite possible that the filterlincs are stopping all traffic. With kind regards, Michel

Hi Chad, Those are file system errors. I do not think your backup is valid. If you don't mind, please send your backup to support@universal-devices.com and we'll figure out the cause. We are all off till Sunday ... With kind regards, Michel

Hello Illusion, This device is not yet officially supported since we just got our hands on a couple quite recently. With kind regards, Michel

Hi all, Not yet. I will add it to the list of our requirements but, honestly, with all the things we have on our plate, this feature will not have a high priority. With kind regards, Michel

Hello me23, The best thing to do when you want to start fresh is to factory reset your ISY: http://www.universal-devices.com/mwiki/ ... ur_ISY-99i What you want to do next just to make sure you have good communications between ISY/PLM is to plug in a lamp module right on top of the PLM and try adding it using the Start Linking method. If that fails, then the problem is the PLM. If that succeeds, then you would have to figure out what's blocking the communications between the PLM and other devices. With kind regards, Michel

Hi robandcathy! Boy, this does not sound good. But, on the upside, the problem is isolated only to those devices that have 0101 icons. How many of those do you have and where are they? With kind regards, Michel

Hello sanders2222, Thanks so very much for the update. Your program seems fine ... good thing emails are financially free (though emotionally quite taxing!). With kind regards, Michel

Hello apostolakisl, This is quite interesting ... if you find the cheap boards we can buy and communicate with using I2C, please let me know and we'll surely look into it. With kind regards, Michel

Hello bocaray, I am so glad it finally worked! Yes, it should be. Rand is the genius in charge so I am sure he'll have it documented in our Wiki soon. With kind regards, Michel

Hi Tim, Orchestrator is only available through our utilities distributor. The retail price is about $399.00. We are also working with Check-it.ca which is an energy monitoring portal. It can get Brultech messages from ISY and provide nice charts/analysis on what's going on. This does not require Orchestrator but 99i with a Brultech energy meter and the latest firmware (still in Alpha). I was told by Check-it that they might have a promotion coming for ISY/Brultech users. With kind regards, Michel

Hello sanders2222, First of all, apologies for the inconvenience. We have not been able to figure out how to work with hotmail yet. I assume they require a client certificate. You can use our temporary mail server: http://forum.universal-devices.com/viewtopic.php?t=4818 As far as the consoles being open, that should not matter. ISY automatically expires subscriptions if the computer/Admin console does not respond (usually when the computer goes to sleep). With kind regards, Michel

Hello Rick, Unfortunately the only way to communicate with Current Cost right now is through a second serial port which is only available on Orchestrator. Current Cost module has not yet been thoroughly tested but from initial testing, it seems to be quite good for "information" and not that good for "accuracy" unless you figure out exactly how to position the CTs! With kind regards, Michel

Hello apostolakisl, Which universal guys? We have to communicate with the unit using one of the interrupt pins on the CPU otherwise the response time would be worse than going to Ethernet back to Global Caché ! With kind regards, Michel

Hello kingwr, Let me clarify: All on/off sends a group command to group 255. The outcome of which is that all responders to "sender" go to the on level/ramp rate of the FIRST ever link for that controller/responder relationship. So, in this vein, an All On/Off from ISY will have the PLM as the source. And, the status of devices are based on the first ever link for PLM (as controller) and device (as responder). All On/Off from ControLinc/RemoteLinc have the source as the CL/RL and the on levels are based on the first ever link between the CL/RL and the responders. The scene for ISY all on/off is the PLM id. With kind regards, Michel

Hi kingwr, Any specific reason for the wait? It's possible that while waiting, the program becomes false and therefore the KPL button stays lit. With kind regards, Michel