Michel Kohanim

Hello stillen_i30, Please do contact our support team (links below) and we'll schedule a call to help you out. With kind regards, Michel

Hi Todd, Thank you. Can you tell me how slow the delay is? Are you simply looking for Control for the Motion Sensor and then activate a scene (or is it a device and/or multiple devices)? With kind regards, Michel

Hello morgan4x4, As we have noted in the instructions, the way in which we handle network resources has changed and thus, now, they run in a separate thread. The only thing that the program does is to queue the activation requests. So: This basically means only two things (though it's rather unlikely that the delay would actually be 30 seconds): 1. The previous network resource activation had a timeout of more than 30 seconds and it actually took 30 seconds to complete 2. The program itself turned to false and then back to true (while waiting) and everything restarted from scratch 3. ISY is busy doing things with much higher priorities (unlikely) So, my recommendations are: If you really have to use a wait command, ensure that the condition does NOT turn to false while waiting. You can do this by putting those that require a wait in a separate program. i.e. Program 2, has NO conditions: Resource 'Basement LED Yellow' Resource 'Home Theater Receiver Power On' Set Scene 'IR TV Power On' Wait 1 Second Resource 'Directv Home Theater On' wait 6 seconds Resource 'Home Theater Receiver Volume -26DB' Resource 'Home Theater Receiver HDMI 2' Wait 30 Seconds Set Scene 'AV rack LED Off' Wait 1 Second Set Scene 'Home Theater Nook LED Off' Resource 'All LED Ambience' This will ensure that this program will always run to its completion. This said, the first thing we have to do is to make sure that your condition does NOT turn false. Also, if you long timeouts in Network resources, you need to make them shorter. With kind regards, Michel

Hi Bruce, Thank you. Does this crash the unit all the time and is reproducible? With kind regards, Michel Hi Michel, That is correct. I am sending one command from the ISY-99i to the IPTOIR to have it repeat the the IR signal 6 times. Regards, Bruce

Hi Todd, Thanks so very much for the feedback. First of all - and as you noted - the fact that the motion sensor has to be in programming mode (or listen mode) before we make any changes is quite daunting. As a matter of fact, we did try this a few times and the success rate was not that high. Furthermore, it seems that HouseLinc has the same type of issues with this approach. The best case is that we can program the motion sensor. The worst case is that we cannot and now your system is left in a zombie state till we retry again. And, then, we have to define number of retries before failing and finally the interval between retries. All and all, if the solution was as easy (or supportable) as changing the scene level (which you already do), then it would have already been implemented. I am so very sorry to disappoint but I am afraid that this solution will cause more damage than good especially since: 1. It has to run a few times a day 2. It's RF 3. The RF device has to be in listen mode With kind regards, Michel

Hello OmegaQuest, I tested this with multiple SMTP servers and, unfortunately, even with , From field is replaced with the account email address unless the SMTP server is configured with the From. We can do further testing to see if there's anything we can do to change this. With kind regards, Michel

Hello Bruce, That's not good. So, in short, you are sending ONLY one command which repeats the IR signal 6 times on its own, correct? With kind regards, Michel

Hello OmegaQuest, If you use the default SMTP settings, then no. Otherwise, it all depends on your SMTP server. Most SMTP servers out there use the Account information and either ignore the From field OR if you put something other than the Account (email), they will reject the message. With kind regards, Michel

Hi jtara92101, I am not sure which documents you were looking at so please do let us know so that we can update. Our latest WSDK does have everything you need to know about REST with optional parameters to show folders recursively or not. That's how ISY AJAX works and thus it must have been documented somewhere. Just need to figure out what you were looking at. Thanks and with kind regards, Michel

Hi Tim, I do think the length has something to do with it. If you have another switch/router, you might want to put the switch/router in the garage and the hookup ISY to it. I suspect you are getting a lot of collisions because of the length. With kind regards, Michel

Hello LeeG, Agreed! Thanks so very much for all your help/feedback and support. With kind regards, Michel

Hi apostolakisl, Sounds good. With kind regards, Michel

Hello gfridland, Thanks so very much for the update! With kind regards, Michel

Hello all, We shall surely consider this requirement when we have moved to our next official release. Furthermore, we do not want to make it annoying with pop ups, so we have to look for some creative ways of doing it. With kind regards, Michel

Hi Robert, Thank you. Is there anything more specific you can tell us ... we really need to get to the bottom of these issues and we'd appreciate your help. For instance, is always the same programs? What do they have in common? The schedules that miss, can you check the last run time to see if they actually ran or missed? With kind regards, Michel

Hello Elvis, Do you have any baby monitors around? Also, what's your thermostat's firmware version? And, finally, what's your PLM's firmware version? With kind regards, Michel

Hello mrxmas, In most cases, it's best to run the Admin Console version equaling to the firmware version. This can be done in two ways: 1. Use the network shortcut which downloads the Admin Console directly from ISY --> it will have the same version as ISY version; OR 2. Go to Help | About, find your version (Insteon_UD99 v.nn.uu.mm where nn.uu.mm is the firmware version) and then go to http://www.universal-devices.com/99i/nn.uu.mm Please clear your Java cache before you doing either. With kind regards, Michel

Hi matapan, Unfortunately not yet. With kind regards, Michel

Hi Tom, I totally understand and YES, you can use a different ISY for production, restore your backup from the development as long as the PLM remains the same. This said, I do not feel right that you would have to purchase another ISY just to test our current release. Please do send me an email (tech@universal-devices.com) and let's see what we can do ... perhaps a short time loaner of some sorts? With kind regards, Michel

Hello GreyFox, I do apologize for the inconvenience. Please do be kind enough to submit a ticket (link below) and we'll schedule a remote session to see what's going on. With kind regards, Michel

Hello rodtoll, Is your questions whether or not ISY can trigger a program in case of change in status of "any" switch or one switch. If one switch then the following should work: If Status device_a is not off Then .... If you want to add more devices, then you can Or them together If Status device_a is not off Or Status device_b is not off Or ... Then .... If you want to sense actual button presses, then what you need to do is to use Control instead of status. With kind regards, Michel

Hello GreyFox, My pleasure. So, the remaining question is whether or not M1XEP does actually have the IP address that you have set in the Admin Console. Please go to https://elk.m1xep.address and see if you can communicate with it. With kind regards, Michel

LeeG, thanks so very much! You are 100% correct. johnnyt, there's a bug in 3.1.x where the time in the Admin Console does not get updated properly. The issue is in the Admin Console and not ISY. With kind regards, Michel

Hello AutomationNut, Please upgrade to 3.1.16 and then follow the instructions below to link it to ISY: http://www.universal-devices.com/mwiki/ ... rmostat_V2 with kind regards, Michel

Hi Tom C., My pleasure. We are hoping to have 3.1.x official release by the end of this month. So far things look good. Since you are using a lot of network resources - and if you don't mind and if you can ensure you have a good backup - I would appreciate it if you could upgrade to 3.1.16 and make sure your system still behaves the same. The reason is that we decoupled Network Resource activation from program execution so, now, program only requests for the resource to be activated and then continues. The resource activation requests are queued and run in a separate thread. This has boosted program execution performance dramatically with the caveat that you cannot be certain that the resource is activated prior to the end of the program. Your input will be quite appreciated. With kind regards, Michel