Michel Kohanim

Hello stevehoyt, Do you get any errors while trying to clear the logs? Or is it just returning without actually clearing the log? With kind regards, Michel

Hello again, There is something that bothers me: Even though your door is open, the status of the sensor does not reflect the correct status unless queried. May I recommend the following: 1. Make sure you have 2.7.7 alpha installed (Help | About) 2. Please remove IOLinc from ISY 3. Do a factory reset on it 4. Add it back to ISY 5. Simulate door open/close and make sure that the status of the Sensor is reflected correctly and that the query returns the correct status If we figure this out, then I would hope that other problems are also solved. With kind regards, Michel

Hi mpf541, Would you be kind enough to do the following test: 1. Change the status of the sensor to be the reverse of the relay 2. Do a query on the sensor If the query returns the correct status for your sensor, then you should be OK. But, I am still unsure why you would have that issue after power failure. With kind regards, Michel

Hi Paul, 1. Using X10 messages as flags would have delays associated with X10. You can easily do the same with a program. i.e. run the Then part to set the program to true or else part to set the program to false. Then you can use the status of that program 2. ISY does not keep previous state ... but, this requirement is part of the new triggers release With kind regards, Michel

Hi evarsanyi, Would you be kind enough to try the following: When you have the issue, do a query on the device, then Right mouse click on the node and choose rename. In the rename dialog, just click OK (you do not have to actually rename it). Please let me know if after reboot you still get the same error. If you do, it most probably has to do with communications error. If not, then we have a bug in ISY. With kind regards, Michel

Hi kcrossley, Please go to Tools | Diagnostics | Event Viewer level 3 and try removing a device. Does it time out (i.e. you get a series of INST-ACK without INST-SRX)? With kind regards, Michel

Hi evarsanyi, Does it only happen after each reboot? With kind regards, Michel

Hi Paul, As much as I would love you to buy an ISY, at the same time I do not want to disappoint you. At the moment, you can use the status of programs as flags (true/false). We are working on variable support but I cannot really give you an ETA. With kind regards, Michel

Hi Mike, At this point, it would make a lot more sense to actually request for the latest version of IOLinc which would solve most of the issues you are grappling with. With kind regards, Michel

Hello, Apologies for any confusion I may have caused by pointing some of you to use http://www.universal-devices.com/99i/2.7.7/admin.jnlp ... ISY has two pieces: firmware which runs on ISY and client which is a Java applet/application. One could be using 2.7.7 UI features without having 2.7.7 firmware installed. As such, if you go to Help | About and it shows 2.7.6, then you do NOT have 2.7.7 installed. smileyw, yes, I am certain I was told v39 ... With kind regards, Michel

Hi all, The firmware that supports thermostat updates is 2.7.7/2 which is not out yet. Those who are on our 2.7.7 list, shall be notified of the release of this firmware. With kind regards, Michel

Hi Heiko, I got it ... this seems to be a bug. I have opened a bug to investigate. Thanks SO very much and with kind regards, Michel

Hi Heiko, Repeating random (in your case) means that it would either repeat the block or not execute at all. I think what you need is to use the Random function on Wait instead of repeat. This way, the amount of time waited for the next statement will be random. With kind regards, Michel

Hi Heiko, Thanks so very much. We will get right on it. With kind regards, Michel Unfortunately this doesn't work either. If I select 'Raw Text', then there's no 'Replace with' available. There was no 'not specified' available when I chose the type 'Insteon'. In addition to that, simply selecting the correct device didn't help either. As soon as I change it (manually) from 'not specified' to the correct device, the action (i.e. setting heat setpoint to 72) is lost (in this case it defaulted back to 'query') and I had to set everything again. My ISY is already configured correctly again, but you may get a flood of complains once folks start replacing their thermostat adapter with the v2.0. Heiko

Hi X, Yes, it's fixed ... sorry for not letting you know. The problem was that we added enhanced images for folders with conditions. Unfortunately, Linux does not yet support image overlay. As such, it's conditionally compiled out in case the operating system is Linux. Please clear your Java cache and try: http://www.universal-devices.com/99i/2.7.7/admin.jnlp With kind regards, Michel Any update on this ? Thanks. -X

Hello Heiko, Unfortunately that's the limitation of the firmware at this point ... it's on the list to be enhanced. What you can do is to use the Find/Replace function in the programs to look for Not Specified and then replace them with your new device. With kind regards, Michel

Hi doubleshot, The major issue is that your condition is being impacted by the action. In this case: Set '1st.Bath1.Light.Overhead' 50% Set '1st.Bath1.Light.Shower' 50% Makes your condition true. And, Set '1st.Bath1.Light.Shower' Off Set '1st.Bath1.Light.Overhead' Off Makes your condition false in which case the whole program stops since the condition has turned false. With kind regards, Michel

Hi Glenn, Long time no see! Hope all is well. Please upgrade to 2.7.7 (need to send an email to support@universal-devices.com). Once upgraded, use: http://www.universal-devices.com/99i/2.7.7/admin.jnlp Most MAC issues are resolved in this release. With kind regards, Michel

Hi Walter, Thanks so very much: First of all, please clear your Java cache and ensure that you are using the latest 2.7.7/admin.jnlp for we have made many changes. Secondly, please do make sure your IOLinc version is above .39. 1. Known issue with the hold time ... we changed the 2 seconds to 2 10th of a second as per instructions from SH. Apparently those are not valid instructions. For now, you could use the number x 10 (to convert to seconds) till we figure out what the actual range is 2. It works here ... so, please ensure you have v.39 and above With kind regards, Michel

Hi Tim, Thanks so very much for the update which I am sure is quite helpful to others. My main question is: if you have the Trigger Off (reverse) checked, does the Relay status equal to the Sensor status OR are they independent? This is the main issue which we are currently waiting for an answer on. Thanks again and with kind regards, Michel

Hi Kevin, No need to apologize: that's why we are here! It's not good to completely shut off your firewall. Please review the recommendations here and let me know if they also solve your issues with Kaspersky: http://forum.universal-devices.com/viewtopic.php?t=1162 With kind regards, Michel

Hi Kevin, If you can turn on the lights the we do not have network related issues. This is a very good sign. Now, I am almost certain the problem is with the firewall on your systems. Have you tried putting ISY in the trusted zone? What firewall software do you have and have you tried the remedies here: http://forum.universal-devices.com/viewforum.php?f=3 With kind regards, Michel

Hi Kevin, Yes! Try turning on/off a device from the Admin Console. If the device actually turns on/off, then the problem is that your firewall is STOPPING traffic from ISY. You might want to try the following URL which is an application instead of an applet. In some cases, firewalls might be more lenient with applications: http://www.universal-devices.com/99i/2.7.7/admin.jnlp ... if this works, then I recommend upgrading to 2.7.7. With kind regards, Michel

Hello mvprj84, Thanks so very much for the update. Although things work, I would like to know the exact behavior of this device. As such, I am going to forward this post to our SH contact. Thanks again and with kind regards, Michel

Hello mvprj84, I just tested the status issue with both Trigger On/Off (reverse) and in both cases the status of the sensor was independent of the status of the relay. I am using Latch (continuous mode). This does not make sense at all and I would like to get to the bottom of it. Would you be kind enough to retest with Trigger option in reverse? And, THANK YOU SO VERY MUCH for your warm words. I do appreciate it very much and I must tell you that you just made my day! When your review is ready, would you be kind enough to send a link to our support (support@universal-devices.com) so that we can include it in our Wiki. Thanks and with kind regards, Michel