Michel Kohanim

Hello OmegaQuest, Do you have any type of firewall software on your computer? I think ISY's IP address changed and your FW is no longer cognizant of ISY. With kind regards, Michel

Hello scotcarter, Please do not hesitate to contact our tech support team (links below) in case you are still having problems. With kind regards, Michel

Hi Nuttycomputer, Thanks so very much for the offer and we should have a beta shortly. With kind regards, Michel

Hello NuttyComputer, Are you referring to 2441TH (which is problematic) or are you referring to 2491T7E which should work? In the latter, you should not have to query. For the former, we are still trying to get to the bottom of things. With kind regards, Michel

Hello dss, The log only captures changes in state. So, if the temp/humidity remain the same at each query, then there won't be a log entry for any that has not changed. With kind regards, Michel

Hello uffy, CLISPC = CLImate-SetPoint-Cool .... so this is your cool set point. Does the thermostat actually call for heat/cool? You might want to try changing the set point right at the thermostat and not from ISY. With kind regards, Michel

Hello dss, It should but it seems that we have problems with the production releases of 2441TH. We are currently working on it. With kind regards, Michel

Hi uffy, The problem is that your thermostat is not reporting that status to ISY (for some reason). What you want to do is to look at the Event Viewer (level 3) and then try and make your thermostat call for Heat/Cool. You should see CLIHCS events. If you don't, then that's where the problem is and, in all likelihood, it has to do with how your thermostat is linked to ISY. If this is the case, the first thing I recommend is to remove the thermostat and then add it back in/retry. With kind regards, Michel

Hi M.A., Thank you. I just got it and it seems that ISY has to maintain a persistent socket connection ... this is not something that ISY can currently do (unfortunately). Have you checked out DSCLinc? With kind regards, Michel

Hi uffy, The problem is that IRLinc Beep function does not work (or, at least, not that I have seen). What's the condition for your If statement? If status of a device (as you had listed), then please open the Event Viewer on level 3, turn on/off one of your devices, and check the traffic in the Event Viewer. Do you see any traffic? With kind regards, Michel

Hello dss, Apart from graphs, aren't all these already captured in the log? In short, what's missing in the logs? With kind regards, Michel

Hello mrp! Thanks so very much. Yes, indeed I have: rain today: 0.26 inches rain rate: 0.12 inches/hour We are not getting any max rain rates for some reason. It's blank coming from WB ... sorry. With kind regards, Michel

Hello uffy, I have never seen that command work on IRLinc ... we have just left it there because it should be supported! With kind regards, Michel

Hi Tom, Venstar 2491T7E should be fully supported. TempLinc, on the other hand, we are having some problems with. Please do the following: 1. Remove the thermostat from your ISY 2. Do a factory reset on it 3. Turn it off 4. Use Link Management | Start Linking and then press and hold the set button on the thermostat If this does not work, then please provide the firmware version of the thermostat (from the Admin Console). With kind regards, Michel

Hello M.A., We would do our best to help you with Network Resources. When you get a chance, please post the link (or send to support@universal-devices.com) to the API docs. With kind regards, Michel

Hello Andy, Don't send it back yet. We just got a non-beta version that we are testing now. If you have 30 day money back guarantee, then it would be best to let us see what's going on. With kind regards, Michel

Hello dbong, I am not certain what MobiLinc does when it refreshes or synchs up. Will follow up with them. With kind regards, Michel

Hello brausse, Would you please be a little more specific as far as what you mean when you say "it quit" ... is it only communications from ISY that quit? If communications only, please check the firmware version on this switch (though it has to be added to ISY for you to get the version). Do you remember whether or not it reported as v35? If so, that's the root cause. If not, there are two cases: 1. Signal quality ... 2. Signal strength .. You might want to change the location of your PLM just to make sure you are on the same phase as the switch. If not, you may want to use dual band devices and/or access points to bridge the phases and extend the range and improve signal strength. Signal quality is a little more difficult to figure out but, in short, we will need to figure out whether or not one or more of your devices are noisy. With kind regards, Michel

Hello ertyu, Control links are controller only devices and thus they will always fail during scene test. As far as other devices, if scene test fails, then it points to signal quality or signal strength. Usually, the first thing I would do is to change the location of the PLM and see if the problem changes to other devices. If that's the case, then in all likelihood getting access points (or dual band devices) and making sure that they bridge the phases should help. In short: 1. Make sure your phases are bridged using Access Points or Dual band devices 2. Make sure your PLM is not plugged into an outlet where you have a lot of transformers, monitors, chargers, and computers connected With kind regards, Michel

Hello Damon, I am so very sorry to hear. Would you please check and make sure that the Micro SD Card is seated properly? If you are still having problems, it's most expedient to contact our support (links below) and we'll make sure you are up and running in no time. Again, sincere apologies. With kind regards, Michel

Hello ubuntulinuxuser, Are you trying to upgrade from Linux? It's best to try http://www.universal-devices.com/99i/admin.jnlp and then, in ISY Finder, try the HTTPS URL for ISY. If you are still having problems, please do contact our support and we'll do our best to get it resolved. With kind regards, Michel

Hello robandcathy, Please do be kind enough to submit a ticket ... it's much more expedient and we'll have a chance to login to your device and see what's going on. With kind regards, Michel

Hello scontor, Thanks for the detailed description. The best way to debug this is to have notifications sent before and after the wait. In the notification, use custom content to list out the status of the variables and program statuses. This way, we will know what contributes to this behavior. With kind regards, Michel

Hi Scott, Are there any other conditions in your program above and beyond rain data? Wait is interruptible so if the condition turns false, then the wait is stopped prematurely regardless of the configured duration. With kind regards, Michel

Hi again, How about the ports? And, did you use File | Enable Internet Access or did you manually create port forwarding rules in your router? With kind regards, Michel