Michel Kohanim

Hello f_richey, This specific situation that you are describing should be fixed in 2.7.3. But, what's not fixed (and is an SH issue) are: 1. Changing the status of the relay changes the status of the sensor (from Admin Console) 2. When the IOLinc relay times out, the status is not reported back to ISY With kind regards, Michel

Hello Davonavo, First of all, thanks so very much for considering ISY. As much as I would want you to own an ISY, but I do think that currently ISY and the devices it supports do not match the same capabilities as JDS TC. As you noted, you could use ISY with I/O devices (such as IOLinc/TriggerLinc and - if you are lucky - with EZIOxxx) and then use their inputs to effectuate program execution. But, beyond those devices, ISY does not have the capability of natively supporting I/O devices. You will find many programming examples and tutorials here: http://www.universal-devices.com/mwiki/ ... e#Programs With kind regards, Michel

Hello NewTech, Normally you wouldn't have to know anything about i1/i2 since ISY should take care of them under the covers. At a high level, i1 and i2 are two modes of communications with INSTEON devices with i2 supporting longer messages. The reason you see references to i1/i2 is because a while back we had difficulties figuring out which devices supported which. Now, that should be history for the most part. With kind regards, Michel

Hello ergodic, We will surely investigate this feasibility. The problem is not necessarily horse power but priorities: the client update task has a higher priority than the programs. The main question is: do you wish for your clients (such as Admin Console, InterfaceGo, IES touchscreen, HS) to be updated first or the programs? With kind regards, Michel

Hi Moshe, Can you check your logs to see if you have any -6000x errors? It seems as if ISY is not synching with your NTP properly. With kind regards, Michel

Hi Al, You are very much justified to feel nervous. I have already sent an email to SmartHome Engineering and they are testing it. Unfortunately, I cannot provide you with more detailed information since I do not have any. Just to clarify, this is the issue where changing the status of the relay causes the sensor to have the same status as that of the relay. Correct? The other issue is that the sensor does not send an Off command when timing out. With kind regards, Michel Re-reading this I am nervous that the "Status of IOLinc incorrect" is not actually a fix in 2.7.3 but text stating that there is a firmware issue that you cannot work around. If there is no known workaround for the firmware issue can anyone point me to a discussion about this firmware issue, hopefully one that involves smarthome. Thanks, Al

Hi Ken, We continuously improve on performance. As Mike suggested, it's very rate that programs take longer than 1 to 2 seconds. I just tested my ISY with many programs and the response time was almost immediate. Bob, we could possibly make this user configurable but, without detailed analysis of how much more performance is gained (see above), the side effects (deadlock), it would not be a good idea. With kind regards, Michel

Hi Josh, The main issue is that you are trying to control something that is already being controlled by the switch itself. So, at best, you will have a flicker and at worst it won't work. Also, you only need "And Control Master Bath is switched on" ... get rid of the Or. With kind regards, Michel

Hi Moshe, That is very odd unless ISY is not actually synchronizing with NTP every 24 hours. So, is ISY 1 minute fast every day or every month or every time you check it? With kind regards, Michel

Hello Ken, First of all, thanks so very much for the detailed explanation and benchmarking. With that said, the reasons that your HomeSeer responds more quickly are: The program task has a lower priority than a. The HTTP task - accepts HTTP requests from your plugin b. The Updater task - updates the plugin with status c. The number of programs that have to be evaluated Now, with a task oriented OS such as ours, the program task will not get to run till the Updater (send event to HS) and the HTTP (respond to HS) tasks are completed. These priorities were chosen based on many factors including start up times, client responsiveness, and the feelings that programs are programs (events) which do not have to be instantaneous (we have scenes for those) and 1 to 5 second response times are permissible depending on the context. With kind regards, Michel Withk

Hi NewTech, I do apologize for the inconvenience. Please do make sure you have the latest firmware (beta 2.7.2) and it should take care of it for you (http://forum.universal-devices.com/viewtopic.php?t=2508). Please do keep us posted. With kind regards, Michel

Hi, Please make sure to minimize your ISY while using other programs. This was fixed in 2.7.0 so, please do make sure you clear your Java cache. If it happens again, then I suspect regression. With kind regards, Michel

Hello f_richey, Would you be kind enough to try an IP address instead of pool.ntp.org (on the DOS cmd prompt, type: nslookup pool.ntp.org). If this works, then it means that ISY cannot resolve names to IPs. This usually happens if your router ignores DNS requests OR if you have setup a static IP address with the wrong DNS. With kind regards, Michel

Hi Josh, What you need to do is to make a program with and use From To in the condition. You will find this link very useful: https://www.universal-devices.com/mwiki ... _a_Program With kind regards, Michel

Hello ryarber, You are 100% correct and this is on our list of todos. But, there's a low tech work around: In your program OR each date with the previous year for the next 10 years, so you would have: If Time is 4/1/2009 1:00 AM OR Time is 4/1/2010 1:00 AM OR Time is 4/1/2011 1:00 AM Then Your actions Else With kind regards, Michel

Hi DevonSprings, Do you want to evaluate the condition every 15 minutes or set Kitchen Scene Off every 15 minutes? For the second, use the Repeat statement under Actions. With kind regards, Michel

Hi petesc2, I totally agree with you. I wished I could be of more assistance. We are still waiting for a response back from SH. With kind regards, Michel

Hello ryarber, Variables are - as you might imagine - a little more difficult than other development efforts especially when constrained by memory and resources (unlike Indigo). Rest assured we are working on it and it will be close to what you have in mind. With kind regards, Michel

Hello Joe, Not at the moment and, unless there's a lot of demand, we do not have any plans thus far. With kind regards, Michel

Hello mikestreb, Unfortunately, we are still trying to get EZxxx to work properly and haven't succeeded yet. We need another 2 weeks to use the last possible algorithm to communicate with EZxx devices. If you have only two inputs, you may want to consider using 2 x IOLincs and thus use one for relay and one for sensor. SH has not yet confirmed this issue. With kind regards, Michel

Hello all, http://forum.universal-devices.com/view ... 9345#19345 With kind regards, Michel

Hi All, http://forum.universal-devices.com/view ... 9345#19345 . Thank you Burak! With kind regards, Michel

Hello All, Thanks to Burak, ISY now has its first iPhone app interface ready to be tested: http://forum.universal-devices.com/view ... 9345#19345 With kind regards, Michel

Burakk, This is wonderful news. Thanks so very much for your hard work. With kind regards, Michel