Michel Kohanim

Hi Paul, My pleasure and I am so very sorry we couldn't get this to work. If you have a good backup and a new SD Card, we can try reinstalling the firmware. If so, please send me an email and I'll send you the instructions. My email is tech@universal-devices.com. With kind regards, Michel

Hi jim3342, Please click on the Save button to make sure the changes are saved. Then, please do ensure that you click on the row for the resource you wish to test. Once highlighted, the Test button should be enabled. With kind regards, Michel

Hi Gary, Long time no see! The last time I checked, this property is not query-able via the current protocol specs. I shall send an email to SH to verify. With kind regards, Michel

Hi mrp, Good question! From a logical perspective, a device's status is global and irrespective of the scene it belongs to. If you are suggesting conditions based on ISY scenes, well, we do have plans of supporting binary scene statuses (on/off) simply because we never managed to agree on what is the status of a scene. With kind regards, Michel

Hi mrp, Theoretically, yes, this operation wears out the flash in devices. Since this feature was added just about a year ago, we do not have conclusive evidence of how long it would take before the devices fail. My recommendation is not to use this feature excessively. Once or twice per day would probably cause very little harm. With kind regards, Michel

Hello mrp, First of all, thanks so very much for the detailed documentation of the problem. I do very much agree with the need for documentation. In the case of running a disabled program explicitly, when events occur, they are not applied to programs that are disabled. As such, the if conditions will never be re-evaluated while disabled. With kind regards, Michel

Hi Paul, I do apologize for the inconvenience. The problem is Fie System related. Would you be kind enough to take the SD Card out and try inserting it back in. Please do ensure that you hear a click while you put the SD Card back in. Also, if your firmware is 2.7.0, what you might want to do is to reboot ISY 4 times. If all else fails, please do contact our tech support and we'll help you get your system back up and running. With kind regards, Michel

Hi paulbram, This is possible but not without some challenges especially security: with the browser, you are using HTTPS in which case all traffic is encrypted. With mail messages, security is a little tricky and it may open up holes for hackers. With kind regards, Michel

Hi mitch236, Those errors happen when ISY can no longer send events to one (or more) of its subscribers. For instance, say you had the Admin Console up and running, left for a while, the computer went to sleep and therefore Admin Console did not Unsubscribe gracefully. ISY detects that the subscriber is not there and clears/expires the subscription. This could also happen with MobiLinc if you go out of service area. The same goes for any ISY client to which ISY can no longer communicate. With kind regards, Michel

Hello, My pleasure! First of all, I think the reason you could not save any of your settings was because you were probably using lowercase 'y' instead of Y. For static IP address, DCHP should be unchecked and an IP address out of the range of your router must be used. I think it would be much safer to schedule a session with our tech support team. With kind regards, Michel

Hi Brian, To be honest, so am I pleasantly surprised as well! This has never been possible before on any KPL versions (the latest one I tested was v36) before. Actually, we had to request our users to use a low on level to mimic off! So, since you are using KPL v36, I must ask: are you certain that you can turn off the load using its sub buttons? With kind regards, Michel

Hi Jim, I think I know the problem: you are probably using the same port for both HTTP and HTTPS and thus all the issues. Please try telnet into ISY: http://www.universal-devices.com/mwiki/ ... o_Your_ISY I think your IP address is 192.168.1.101. If that fails, then it would be OK to factory reset as long as you have a good backup. Otherwise, you will have to redo everything. If you do not have a backup, please contact our support and let us see if we can help further. With kind regards, Michel

Hi sanders2222, Please note that the My Lighting icon is the least reliable method of accessing your ISY if your ISY is on DHCP. This method uses UPnP which restricts the usage of some ports. The best methods are: http://isy (on windows machines only) http://www.universal-devices.com/99i/2.7.14 (applet) OR http://www.universal-devices.com/99i/2.7.14/admin.jnlp (application) Please do not factory reset before trying the above URLs. With kind regards, Michel

Hi again, Unfortunately this is the only fix available. With kind regards, Michel

Hi Dogan Bora, Unfortunately, we cannot take advantage of EZRain's internal programs. You must use ISY's programs. With kind regards, Michel

Hi Simon, Those numbers are quite strange especially the 16. The 140 I can understand since communicating with the thermostat requires using the actual setpoint x 2. Sometimes, the thermostat might act erratically since the group commands it sends use the actual temp. I do not think this has to do with your SWL35. If you don't mind, please send me the program that was running at that time. With kind regards, Michel

Hi, Would you please go to the IR tab, press the IR_003 button and ensure that ISY is hearing it (it gets highlighted). With kind regards, Michel

Hi Dogan Bora, I think you are set ... that should do be sufficient. With kind regards, Michel

Hi Brian, Thanks so very much for the update. I am so very pleased to hear that everything is working properly (except the brightness). The answer to your question is: in most cases yes. Unless, you had your ISY crawl your KPL and there were too many orphaned links (not very likely). With kind regards, Michel

Hello pemoller, SmartHome does have a 220 SWL but it's a little strange looking: it's basically two 120v SWLs. Apart from that, I am not aware of any other 220v relays. With kind regards, Michel

Hi Brian, SWL versions below 4.5 do not allow for the backlight to be adjusted using programing. What version of SWL do you have? As far as the KPLs, I really do not know where to go from here. I do have versions 2D and 36 for both of which I can adjust the backlight levels. The difference between the UI from our website and ISY is practically nothing except that in some rare cases, if we have UI changes, then we just upload it on the website so that you do not have to upgrade the firmware. Now, back to your IOLinc. I was not aware of this feature mostly because I have to experiment with things just to make sure they do what they should. Now, the main questions for me: 1. Does ISY show the correct status for the sensor node for each and every one of your IOLincs? If so, what happens if you query the IOLinc? Is the status still correct? (i.e. does it show whether or not the door is opened/closed?) 2. I assume you have a scene with the IOLinc relays as responders and a KPL as a controller, correct? 3. Can you please (one more time) explain what happens now. I understand what should happen but I need to better understand what does actually happen With kind regards, Michel

Hi Illusion, Thanks for the tip ... indeed that works properly. I wonder what's the cause. Jeff, Fan should also update when you go from Auto to On. The only time it may not work is if you change the mode quickly which does not give enough time for the dongle to sense the change. With kind regards, Michel

Hi all, Thanks so very much for the verification. Appreciate it. Illusion, I have the same problem with my MAC. The problem is that I have yet to find a JVM 1.6 that supports 32 bit systems. Unfortunately, mine is 32 bits and that's why everything reverts to 1.5. Does anyone else have a problem with the fan state not reporting? With kind regards, Michel

Hi Brian, Apologies for a tardy reply. As far as the KPL On/Off button, are you certain that you are not describing the non-toggle mode? As far as I remember, that's the only mode that lets you have the On button not toggle (with off). There's also one more option which is called mutual exclusivity: when buttons {...} are on buttons {.,.} are off and vice versa. If you see the on/off level for your SWL as well, then please update your firmware to 2.7.14 (you have 2.7.13) and make sure you clear your Java cache. Alternatively, you might want to try the following URL to see if you have the same behavior before upgrading to 2.7.14: http://www.universal-devices.com/99i/2.7.14/admin.jnlp As far as your IOLinc, from what I understand, Momentary C means that the relay's status is equal to the sensor status (unless reversed). In short, whenever the sensor is shorted, the relay is shorted and whenever the sensor is opened the relay is opened. From my experience with Garage doors, I am not certain how you could use this mode. Depending on the SWITCH mode for your garage door opener, the best modes are latching or Momentary A or B. In Momentary A or B, your choice of NC or NO lets you decide which signal should turn on the relay. If you could explain in more depth the use case, I would be better equipped in answering your question. Furthermore, if you have an multi meter, it would be great if you could check how your current garage door switch works (toggle or non-toggle on or non-toggle-off). With kind regards, Michel

Hi Bruce, Thanks so very much. At this point, I have to think that this is a bug and I would sincerely appreciate your help. Would it be possible for you to take the SD Card out, zip all contents therein and send it to tech@universal-devices.com? Thanks and with kind regards, Michel