Michel Kohanim

Cliff, Excellent. v85 was a production PLM. Now, this is what I want you to do please: 1. Make sure you have a good backup with this PLM 2. Identify one of the switches that we can use as test 3. Do a factory reset on ISY (you can use telnet, and then issue FR) 4. Once ISY reboots, try to link the switch we identified in 1 5. If this also fails, then we have to figure out why the signals are not getting to the device 6. If it succeeds, then restore your backup (File | Restore ISY) followed by File | Restore Devices 7. Once 6 is done, make sure you do not have any 0101 green icons on any of the devices on the left With kind regards, Michel

Hi Cliff, What was the version of the original PLM? 7A was a beta PLM and I do not trust it. Please do the following: 1. Configuration | System | uncheck Query at startup 2. Reboot your ISY with the original PLM 3. Let me know what ISY reports for the PLM version With kind regards, Michel

Hello apostolakisl, Control events are issued when something is done to the device physically. So, is NOT will be doing nothing if nothing has been done to the switch. If something is done to the switch, then is NOT basically checks to see if the event is equal to what you had in your condition and then evaluates to false if it's not equal. Again, control events are not issues by themselves. They have to be triggered by a physical activity on a device. With kind regards, Michel

Hello Cliff, Apologies for the inconvenience. Can you tell me what you see when you go to Tools | Diagnostics | PLM Status/Info? Please do not restore or factory reset since they are not going to help the issue. With kind regards, Michel

Hi boatfevor, If you have assigned a static IP address for ISY, that could explain why you cannot get to pool.ntp.org. Please make sure the DNS settings for your ISY are correct. Furthermore, if the interval for checking NTP is too low, pool.ntp.org will reject it. With kind regards, Michel

Hello boatfevor, MEM/ERR blinking means: network problems the top 4 of which are: 1. ISY's cable is disconnected from the network 2. ISY cannot communicate with the router 3. ISY cannot renew its DHCP lease 4. There's another devices with the same IP address on the network If you have 2.8.10, you can go to Tools | Error Log and review the errors which are pretty descriptive and can tell you what's going on. With kind regards, Michel

jcanter, It basically means that while ISY was waiting to receive an ACK from the device you controlled via ISY, someone or something changed something physically on a device. This caused an ACK to be sent to the PLM while ISY was waiting for an ACK from the original device. Completely benign with the side effect that whatever happened in between, is ignored and thus the status of the device might not be reflected properly. In most cases, this happens when you have difficulty communicating with a device and ISY keeps retrying. With kind regards, Michel

Hi Brian, yes: the problem is so intermittent that we have not been able to find a fix for it. Hello DStampfer, This sounds a LOT like firewall issues. Would you be kind enough to let me know which firewall software you have, and whether or not ISY's IP address has changed, and whether or not you have put ISY in the trusted zone/white list in your firewall software? With kind regards, Michel

Hi Tim, Thanks so very much for the update. I still would be very interested to know what in EZIO is causing the hang. If you are not sending your EZIO for repair, may I ask to have it for a couple of days? With kind regards, Michel

Hi Zandrel, Originally I thought this is a simple UI fix. But, unfortunately, this is how it was designed to accommodate older KPLs where you had to press the button to choose the mode: everything is done in real time. I will see what we can do but since we are very close to our offiical release and since this code is tied into other pieces inside ISY, I do not want to have to go through antoher regression testing right before our official release. Rest assured it has been logged and that it will be fixed after our official release. With kind regards, Michel

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