Michel Kohanim

Thanks so very much for the update and the vote of confidence! With kind regards, Michel

Hello Ryan0751, I am so very sorry to hear. I think it would be quite useful to review this article so that, at the least, we will be using the same vernacular: http://www.universal-devices.com/mwiki/ ... h_tutorial One you have studied this article, then please do let us know what you're trying to accomplish and we'll do our best to answer. With kind regards, Michel

Hello hart2hart, Thanks so very much for the details. Can you tell me what is: Scene:Great Room / Great Room:ThermostatORS Off 0 Thu 2012/08/02 06:46:26 PM Program Log Is your thermostat part of a scene? With kind regards, Michel

Hi hart2hart, Yes, polling intervals are saved. I think I understand what you mean ... having a shorter polling time is not necessarily a good thing since WB may block you from getting future updates if it considers you a hacker. Perhaps we should start by the program details and figure out what are the most important things that have to take place at reboot. With kind regards, Michel

Hello hbsh01, Sections 6.3 and 6.5 in the document are precisely what you need. For your reference: 1. Do http://your.isy.ip.address/rest/nodes (section 6.3) ... each device has an the content of which is what you need in ALL your futher communications with ISY for this device. In the document, should be replaced with the address of the device2. To send a command: /rest/nodes//cmd////.../ e.g. /rest/nodes/15 4E 0B 1/cmd/DON/128 ... turn the device on to 50% 3. For a list of commands, do /rest/config Hope this helps with initial questions. Again, the document has all you need in section 6. With kind regards, Michel

Mr. Miller, Please click on the Locate Me button ... it should give you an pretty accurate representation of your lat/long. If you are still having problems, please do send your zip code to support@universal-devices.com and we'll send you the correct lat/long. With kind regards, Michel

Hello hart2hart, The module subsystem is started after programs. The reason that I do not understand your question is because as soon as WB data is retrieved, then the corresponding programs are run. So the maximum delay is equal to the Polling interval you have chosen for your WB module. I think the problem is that you are thinking in sequential terms while ISY does things mostly in parallel and as events happen. With kind regards, Michel

Hello hbsh01, Please do be kind enough to peruse our WSDK documentation where everything is clearly explained/described: http://www.universal-devices.com/isy-developers With kind regards, Michel

Hello hart2hart, I am not sure what the first part of your question means. The answer to the second part is no, unfortunately not (yet). With kind regards, Michel

Hi JSP0511, You should choose either My ISY or My Lighting. It's quite odd that you didn't have the query program. With kind regards, Michel

Hello Robermax, Please do be kind enough to register for our newsletter at http://sales.universal-devices.com/my-account . 994i ZS series has already been certified and we should be ready for shipment by the end of this month (if not sooner). With kind regards, Michel

Hi Paul, that's great news and thanks so very much for the update! With kind regards, Michel

Hi all, Can we increase the timeout on the Network resource by 50% and see if that solves the problem. It might just be that the computer is way too busy? With kind regards, Michel

Hi Paul, yes, precisely. And, I do know of a few cases that this actually happens (set point goes to 0) and, in all those cases, the problem is that someone clicked on the All On/All Off button on ISY. So, we need to make sure that if this happens again, it's not related to an All On/All Off. With kind regards, Michel

Hi Paul, Thanks so very much for update. Very much looking forward to the result of your experimentation. With kind regards, Michel

Hi Paul, We need to figure out exactly what happens when you get those entries and why they happen. Perhaps couple of programs to send you a notification when these specific conditions happen. With kind regards, Michel

Hi NNilsen, You can get your SWL35s replaced for free. They have known defects which will cause major problems in INSTEON network. For KPL2A/2D, the problems are intermittent and you might have devices that turn on/off on their own just because they had been linked to KPL 2A/2D at some point. Here's a high level explanation of Event Viewer: http://www.universal-devices.com/mwiki/ ... ent_Viewer With kind regards, Michel

Hi hart2hart, The numbers are correct (half of the actual value). But, you are right! You are getting a set point of 0 returned back from your thermostat. This is NOT normal. How many thermostats do yo have and do they all have the same firmware version? And, do they all exhibit the same behavior? Also, do any of your thermostats are part of a scene? And, finally, do you ever use All On/All Off? With kind regards, Michel

Hello hart2hart, I am in agreement with io_guy. The first thing is to remove Norton security ... at the moment, firewall software is the ONLY external component of the PC that can impact both incoming and outgoing traffic. With kind regards, Michel

Hello NNilsen, You MUST replace SwitchLinc v35. Also, KeypadLinc 2A and 2D. And, finally, thermostat dongles lower than v2.2. With kind regards, Michel

Hi again, please see the post above first (if you have not already done so). What you might want to try is disable all those programs that are thermostat dependent and see if there are any improvements. Secondly, to figure out the slow response times, if this is repeatable, the first thing you might want to do is to disable the programs that are based on DSCLinc variables and see if there are any performance improvements. The fact that ISY cannot connect to DSCLinc tells me that there are some network connectivity issues. Is it possible that your PC is going to sleep mode? Does this happen immediately? Can you copy/paste your router's logs for the same period? With kind regards, Michel

Hello hart2hart, I really do not think these are the cause UNLESS you have programs that do things based on these values that require network activity such as: 1. Network resources 2. Emails/Notifications 3. Portal integrations (remote access) And, all the above is really not a problem UNLESS there's network connectivity issues such as DNS issues. The problem I see from your error log is that ISY is trying to "connect" to something on the network which is NOT responding. The timeout on your Network resources is the amount of time ISY waits to connect. With kind regards, Michel

Hi Michael, We were waiting for an updated version of 2441TH firmware. We shall be working on it as soon as it's available. With kind regards, Michel

Teken thank you. Brian H, thank you. You see, we cannot simply keep querying the thermostat since it will a) go into sleep mode and even if it doesn't, all the queries are going to drain the battery. We are still looking to see if there are minimal things we can do to support this sub-optimal device without causing all sorts of tech support issues. With kind regards, Michel

Hello hart2hart, If you don't mind me saying, I think INSTEON traffic from the thermostats (as long as it's normal) should be negligible. We have installations with more than 30 thermostats and the traffic has never been a problem. May I ask what problem you are trying to solve? With kind regards, Michel