Michel Kohanim

Hi mpf541, Would you be kind to do one more test: 1. Please remove both the sensor and the relay from all the scenes to which they belong 2. Redo the query and let me know if you still have the same issue In the meantime, I am going to contact SH for further clarification. I do have a v36 here which does not exhibit the same issues you are experiencing. With kind regards, Michel

Hi ryarber, You can safely ignore these errors if: 1. You are using a mobile client (such as iLinc or eKeypad) 2. Some connections are lost These errors basically mean that the subscriber could no longer be reached and thus the subscription is expired. With kind regards, Michel

Hi jason|99, Every time a program's state changes the conditions to which it's part of are re-evaluated. If I use the concept of Control vs. Status, programs only support Status. With kind regards, Michel

Hello Al, Would you be kind enough to let me know whether or not ISY considers this device as "unsupported". If yes, can you give me the numbers after the "v" on the top center of the screen for this device? Thanks and with kind regards, Michel

someguy! What URL as you using? There are two files: 1. One is the macro file which is part of the applet code 2. The other is the actual log which is downloaded from ISY 1 requires 2. With kind regards, Michel

Hi Paul, [ignore] means two things: 1. The device itself shall ignore this record 2. You should consider this record as a logical delete and ignore it With kind regards, Michel

Hi greg, Please do be kind enough to try our 2.7.7 firmware. Once you have this installed, then use http:/www.universal-devices.com/99i/2.7.7, make sure the options are correct (Momentary C), and then let us know how it works out. If you are interested in installing our 2.7.7 alpha release (which is very stable), please send an email to support@universal-devices.com. With kind regards, Michel

Hello mpf541, please check the version of your IOLinc. If you have anything below 32, please have them contact us so that we can resolve the issue. It's a known fact that IOLinc versions 31 and below report the status of the relay as the status of the sensor. This should have been addressed in higher versions. With kind regards, Michel

Hi fasttimes, Apologies for a tardy reply. Yes. Please use Event Viewer/Level 3 to figure out which device is causing this issues. In most cases the problem is signal. In 10% of the cases the problem is the device itself refusing to write to a specific memory location. Factory reset fixes this issue. With kind regards, Michel

Hello UDNewUser, I did send you couple of emails one of which was almost immediately after I received your email. Since I didn't hear anything back, I sent you another email after about 15 minutes and still didn't get anything back. I also called you this morning but got the voicemail. Please do be kind enough to call us so that we can get to the bottom of this issue as soon as possible. With kind regards, Michel

Hi Paul, Unfortunately that feature is not available currently but is high on our list. With kind regards, Michel

Hi UDNewUser, Can you send an email to support@universal-devices.com now? I would like to login to your computer and see what's going on. Thanks and with kind regards, Michel

fasttimes!!! You are indeed quite fast! This is a hotly requested feature and we will indeed include it in one of our releases in the near future. With kind regards, Michel

Hi fasttimes, I do apologize for a tardy reply ... Using Event Viewer/Level 3 you would know exactly what is causing request failed. What seems to be happening is that due to the failures, some links have not been removed. Currently, the easiest way to remove them is to: 1. Create a dummy scene 2. Put both your RL and the device that responds to RL 3. Make sure that the RL is actually controlling that device 4. Event Viewer/Level 3 5. Remove the scene altogether ... please make sure to save the Event Viewer log and send it to us in case this procedure fails We are currently working on a more direct way of removing unwanted links ... we just haven't figured out the best way of doing so without jeopardizing the synchronization between ISY and the devices. With kind regards, Michel

Hello UDNewUser, I am so very sorry to hear about all the problems you are having. Please note that 2.7.0+ had a bug with SSL and, for sure, iLinc could cause it to crash. The main question is whether or not reboot solves the problem. If the reboot solves the problem then I strongly recommend upgrade to 2.7.7 (please send an email to support@universal-devices.com). If the reboot does not solve the problem, then I must say that this is the first ever case that two units would just die irrecoverably. When you reboot, what's sequence of LEDs do you see? With kind regards, Michel

Hi tome, Grouping is only organizational and has no impact on anything else. Originally, we didn't show the status for sub buttons but due to very popular demand we had to add that feature. With kind regards, Michel

Hi fasttimes, We have considered so many different possibilities including a semi/protected virtual machine ... at the end of the day, though, we just need more resources to help with development. With kind regards, Michel

Hi fasttimes, Are you certain that the size of the second zip file was zero? Please note that Windows has a problem unzipping a zip within a zip (you need WinZip or AllZip). Not all files are in XML. There many low level files that are in binary. On the other hand, you can get device configuration, nodes, and other system settings by using either our Web Services or REST interface. As such, you can still get access to the information you want but NOT by reading the contents of the zip file. With kind regards, Michel

Hi sanders2222, Thanks for the update. If ISY still has a hard time writing the links, I am bound to assume we have signal issues. Is it possible at all to move this device (even temporarily) close to the PLM and see if it exhibits the same behavior. During Restore, ISY drops all the links from the PLM, defrags the device database (getting rid of 22s), and recreates everything from scratch. So, if the process is interrupted in the middle, some of the links may not be recreated (as such you may assume they have been dropped). With kind regards, Michel I did the factory reset at the device. But the restore device on the console shows the same error message. That would mean the device is OK. When I list the PLM Links, the only lines I see for the device are: 002A : E2 00 12.60.E0 01 01 37 002B : E2 00 12.60.E0 01 01 37 This indicates my PLM lost the ‘A2’ link. The device worked properly earlier today. What is the reason a link is suddenly dropped in the PLM?

Hello jsmith6, We should have 2.7.7/2 out by the weekend, a week of testing, and then Beta. With kind regards, Michel

Hi Brian, Yes, this is correct. You can supply ISY with up to 30 volts and it should work fine. The minimum is 5Volts, 300 mA, and 2 mm barrel connector. With kind regards, Michel

Hi fasttimes, Good question! The answer is basically limited resources ... ISY firmware is quite complex internally with quite a number of modifications in the OS/kernel to achieve network performance and concurrency. Although everything can be ported to Linux or Windows CE, the major hurdles are integration and reliability testing for which we currently do not have any resources. With kind regards, Michel

Hello backinthelab, Actually, firmware version 2.7.7 is much more stable than 2.7.6 and as such I certainly recommend upgrading. With kind regards, Michel

Hello capsterx, Would you be kind enough to let me know the firmware version of your SWLs. You can find this on the top center of the Admin Console screen when you click on that device. In some rare cases, SWL 35s exhibited some signal sensitivity issues. With kind regards, Michel

Paul, Rest assured that we are working on it ... the main issue right now is time/resources and the level of complexity attached to supporting variables. It's our practice to either do something 90%+ or not do it at all. Thanks so very much for your patience. With kind regards, Michel