Michel Kohanim

Hello DStampfer, 2.7.13 is a beta release before our current official release (2.7.15). We are going to have another official release very soon. In the meantime, please upgrade your system to 2.8.10 which is quite robust: http://forum.universal-devices.com/viewtopic.php?t=5613 With kind regards, Michel

mbrett, You can expect: 4 nodes (one for main, one for cool, one for heat, one for fan) and then status changes sent to ISY automatically. If you do not see 4 nodes, then please remove your thermostat from ISY, do a factory reset on it and then add it back. Make sure you have the latest firmware (2.8.10). With kind regards, Michel

Hi zanderl, Thanks so very much. This must be a bug and shall be fixed. With kind regards, Michel

Hi Jay, Is it possible that you gave ISY an IP or subnet that is not inside your own subnet? The best thing to do is this (hopefully you have a good backup): 1. Factory reset your ISY 2. Restore your ISY 3. Be very careful when you change network settings: if you are assigning static IP addresses, you have to make sure that they are within the same subnet as your router and that it does not have a conflict with any other device With kind regards, Michel

Hi SoCalRob, I do apologize if I was not clear in my previous post: the immediate level setting is not affected by batch mode. The Programming part is. So, you can ignore all those errors and when you are done, turn everything off and then turn on the batch mode. This will program all your scenes to the what you had them programmed to and since all your devices are now off, they should be programmed without a problem. With kind regards, Michel

Hi Teken, This is how ISY works: you send a request, ISY sends out the INSTEON equivalent, waits for a response back, and then publishes the state to the clients. If you click to quickly on some button, then ISY puts them in a queue and each one is done in sequence. So, on on off on off is actually going to be in the same sequence. What you need to do is to open the Event Viewer on the last level and see if there are any INST-ACKs without any accompanying INST-SRXs. Polexian, the Beep duration is the duration in time and not in number. So, for instance, 10 would be less than 0.5 seconds and so on and so forth. With kind regards, Michel

Hi Teken, If you use TouchSwitch, then http://isy.ip.address/scenes If not, then http://isy.ip.address . With kind regards, Michel

Hi Teken, I do not think this is Java related. This seems to be much more serious. Can you do me a favor? Try the same with the HTML interface: try turning on/off a scene and see the behavior of your devices. With kind regards, Michel

Hi Joe, 1. HTTPS (not HTTP) enforces encryption on all traffic between the browser and ISY. So, no one without a KEY would be able to decrypt the traffic 2. Certificate is like a decryption key for the browser. By having your own unique certificate it means that you have your own unique decryption key With kind regards, Michel

Hi Teken, Ah, it's Alzheimer or senility or age or all ... sorry for the confusion! With kind regards, Michel

Hi Teken, Are we talking about devices physically not turning on/off or their status not updated properly OR both? With kind regards, Michel

Hi Joe: http://www.universal-devices.com/mwiki/ ... ertificate With kind regards, Michel

Hi Teken, thanks so very much. Do you actually see the status of the RL button change in ISY? With kind regards, Michel

Hello Orest, At a first glance, everything looks good and I did a test here and it worked fine. Can you do me a favor? Please create a folder, put the time constraint as the condition for the folder. Move this program in that folder and then remove the time condition. Please retry and let me know if you are still having issue. Please also note that On means 100%. Although this does not make any difference for KPL buttons, but for future reference, if you want to refer to 1% to 99% then you must use Not Off. With kind regards, Michel

Hi Guys, Getting a version number does not mean that it has been linked properly to ISY (i.e PLM = Slave, Remote Linc = Master). In the scenario that you use Auto Discover, do you get status feedback from RemoteLinc buttons in ISY? With kind regards, Michel

Hello Teken, Yes it does make sense but I think the problem is somewhere else: do you have any devices with green 1010 icons? It seems that ISY is trying to do other things simultaneously. If not, then do yo have any programs that might start executing when that scene is activated? With kind regards, Michel

Hi Rob, First of all you are not doing anything wrong! There's a batch function which in PRO series which lets you do all the changes (batch them up) and then submit them for writing. I am not sure if the cost of upgrading to PRO ($30.00) justifies what you want to do: modify your scenes without ISY controlling the loads. In short, once you are done with modifications, you do not plan on changing them continuously and thus PRO would be an overkill. Above and beyond that, I am not sure what else to suggest .. is it possible to unplug the transformers while programming? With kind regards, Michel

Hi Joe, You cannot install a certificate remotely. You have to do it when you are local to ISY. It's up to you to decide whether or not you want to install a new certificate. All ISYs come with default certificates out of factory which is not going to be very secure. It's best to install your own certificate and make sure to use only port 443. With kind regards, Michel

Hello Teken, If you click on the on/off on a controller within a scene, nothing should work! The problem is that ISY cannot act as a proxy for the controller. Did I get it right? With kind regards, Michel

Hi BrianH, RemoteLincs are controllers only and, as such, Linking would not work (it will add them as responders and thus you would not get any status updates). The problem, though, is that RLs do not respond properly to IDReq and that's why you do not see the version. With kind regards, Michel

Hi Harold, Point well taken. I agree that the Advanced Configuration guide should be an appendix to the User Guide. In any case, if you have any difficulties with setting up your system, please do not hesitate to contact us. With kind regards, Michel

Hello Paul, If you can access your ISY using https://your.external.ip.address:555 but you cannot do it remotely, then I suspect that port is blocked by your ISP. You might want to change the port forwarding rules to say 8443->555. Also, you do NOT want to use UPnP. So, please go to Help | About and make sure that Internet Access says Disabled. If not, please go to File | Disable Internet Access. With kind regards, Michel

Hello bocaray, Please make sure you do not have any devices that have pending device operations (green 0101 icon). If you do, you might want to disable them before doing anything with your motion sensor. Once you are done with your motion sensor, then we have to figure out why those devices are out of synch with ISY. In most cases, ISY attempted to program them but failed in the middle and now is trying to complete the process. With kind regards, Michel

Hi Harold, All information is on our website under Support | Wiki. You can also get to Wiki from the Admin Console. You do not need the serial emulator to find the IP address for your ISY. That's why we have the Admin Console which finds ISY (searches the network). My question to you is: what are you trying to accomplish and why do you need the serial port? If I know the answer to this then we'll figure out the best way to provide that information in one of the documents/links on our website. And, the answer is: it's not hard; we just never envisioned that Advanced Configuration should be included in the User Guide. With kind regards, Michel

Hello kurelgyer, I am so very sorry for the troubles you are having. If Tools | Diagnostics | PLM Status/Info shows "Connected", then the problem is usually related to Java Cache (Certificates) or firewall software. Please do the following: 1. Close all your browsers and clear your Java cache ( http://www.universal-devices.com/mwiki/ ... Java_Cache ) 2. Go to Java Console | Security and remove all Universal Devices Certificates 3. Go to http://www.universal-devices.com/99i/2.8.10/admin.jnlp If you are still having problems, then please checkout this forum for solutions to firewall issues: http://forum.universal-devices.com/viewforum.php?f=3 Please keep us posted. With kind regards, Michel