Michel Kohanim

Hello jwagner010, Would you be kind enough to try the Test button in the Network Resource panel and let me know if you have the same response time? In short, I want to figure out if the problem is network resources activating a resource or if the problem is that the evaluation of the trigger by the programs take longer. With kind regards, Michel

Hi Moshe, Are any of the SwitchLincs version 35 (as reported by the Admin Console)? If so, there lies the problem. Otherwise, the problem is that the signals are not getting to your switches OR that one or more of your switches have loads that cause noise. You might want to remove the load from your devices (if possible) and see if scene test succeeds. With kind regards, Michel

Hello Zellarman, Apologies for tardy reply. The problem is that basically ISY cannot get the remote IP from your router. Personally, I do not recommend using UPnP if you want to have reliable remote access to your ISY. Instead, I suggest disabling Internet Access (File | Disable Internet Access) on ISY and then configuring your router for manual port forwarding: http://www.universal-devices.com/mwiki/ ... o_Your_ISY Please review the section under Configuring Non UPnP Routers. Furthermore, you might want to get a Dynamic DNS account so that you would not have to remember your IP address and IP address changes are not going to make ISY inaccessible. With kind regards, Michel

Hi Lou, First of all, I wanted to apologize for this bug. Secondly, thanks so very much for finding it, and finally: it's already fixed and should be available in the next release. Thanks again and with kind regards, Michel

Thanks Lou. As far as Restore failing, I think it has to do with firewall ... I am tempted to ask you to try and restore again but let me do some more testing before we do anything else. With kind regards, Michel

Hi Tom, Please contact our tech support and we'll help you configure it. With kind regards, Michel

Hello Lou, Thank you. So, this is what happened: 1. Removed some resources 2. Backed up 3. Restored 4. IDs changed Is this correct? With kind regards, Michel

Hello jlloyd_UD, I have to conclude as BrianH especially since PLM Status shows "not connected". The first thing I would do is to make sure the cable between ISY and the PLM are secure and if that fails, then I would ask for a replacement PLM. With kind regards, Michel

Hello bcall, Apologies for tardy reply. Please try DFON (instead of DON) and see if that works. If it does, then the problem is that your ISY does not have the latest states for On Level (DON goes to the on level at the predefined ramp rate). Moshe, have you tried Scene Test on those scenes with problems? Do they all succeed? With kind regards, Michel

Hello apostolakisl, Thanks so very much for the update. I do have your zipped file and I am going to try it and see what happens. With kind regards, Michel

Hi Mark, By load you mean the actual load is flashing? i.e the lamps? If so, the problem is surely electrical wiring related. I have seen this in two cases: 1. Older/defective SwitchLincs 2. The load is higher than the maximum supported wattage of the device I have never seen just the load LED (button A or ON) blinking. With kind regards, Michel

Hello apostolakisl, Thanks so very much. I just tested this a few times and it works fine. Basically, this is what it should do: 1. Delete everything from network resources 2. Recreate them in the order they were in the table before the export Did the Admin Console first remove all the other entries before doing a restore? With kind regards, Michel

Hello Zellarman, Would you be kind enough to send your uuid (Help | About) to sales@universal-devices.com and we'll figure out what's going on. With kind regards, Michel

Hello rubin, Thanks so very much!!! This is excellent. May I humbly request that you also post this article in the Developer Forum under WSDK: http://forum.universal-devices.com/viewforum.php?f=62 If you are planning to upgrade to 99i, please note that you get a developer discount. Thanks again and with kind regards, Michel

apostolakisl, Restore MUST use the same IDs. Import does not. So, this must be a bug. Are you on 2.8.10? With kind regards, Michel

Michaelv, Please contact our tech support and we'll help you upgrade. Eakin, I am so very sorry. You are 100% correct and the problem has already been fixed. If you need early access to 2.8.11, please send an email to support@universal-devices.com . heatvent, Please send an email to sales@universal-devices.com and we'll do our best to keep your cost as low as possible! Polexian, Please contact our tech support team for I have not been able to reproduce this specific problem. With kind regards, Michel

dnl, Thanks so very much! With kind regards, Michel

Hello junkycosmos, Excellent idea! I do not think we'll have time to implement in the current release but I think this is a very important feature! With kind regards, Michel

Hi guys, First of all, thanks so very much for the lively discussion without the types of which we wouldn't have been able to improve on ISY's functionality. The main problem is that for ISY everything is an event. All events are queued up and sent for evaluation. Based on what kingwr is saying, we should now have a separate event class called trigger. In this scenario, it's the trigger that DECIDES whether other events should be evaluated. At a high level this makes sense to those of us with programming experiences and it's kind of like: If (x) then switch (other evaluations) else switch (some other evaluations) From an implementation perspective, though, this has some major regression testing ramifications and might not be as easily backward compatible with previous programs. Of course, we would have to do more investigation on it. Since we are doing variables. we might look more closely into this request and see what we can do to make things more consistent. Again, thanks so very much and with kind regards, Michel

Hi Tim, This is only a warning and you should not worry about it IF they go away by themselves. In short, something opened a socket but did not close it when ISY did the accounting. In all cases, the thing that opens the socket is waiting for something and will eventually close the socket. Sluggishness could be related to devices that have pending updates OR too many things are trying to control INSTEON devices one of which may have communications problems. As far as notifications, if you do not see any -5000x errors (SMTP errors), then the problem is with the programs. With kind regards, Michel

Michaelv, The problem is that the UI files have not been installed in your ISY. Please try http://www.universal-devices.com/99i/2.8.10/admin.jnlp and see if you can log in. If so, then try the upgrade again. kd7iyt, If you are still having issues, please contact our tech support and we'll try to fix it remotely. With kind regards, Michel

Hi Jeff, You are correct. This must be a bug. With kind regards, Michel

Hi Jeff, We did go back and forth with SH on this specific topic many times. For some reason, no matter what we put in the memory location, a sub button cannot turn off the load. Unfortunately, there's no way around this. I am so very sorry. With kind regards, Michel

Hi Greg, thank you. This should already be fixed. With kind regards, Michel

jch, Unfortunately you can not set it to 0. You have to set it to 2% and that's the limitation of the KPL mapping. With kind regards, Michel