hart2hart

Gentlemen: I'm not concerned about a timeout during the routine hourly update. FWIW, DSC it-100 doc indicates that not all updates are broadcast by panel and recommends a periodic update to confirm in sync ... Not clear the potential missing updates are worth effort but I was just following DSC recommendation. My real concern is that an alarm REST variable update timed out within a couple tests. I'm good with any solution that minimizes this possibility or retries ASAP. My personal efforts have been to see if the timeouts were created by my environment. The DSCLlink PC and ISY are on same network switch and the PC is only running DSCLink. This ties in with reason I was concerned with thermostat activity since I'm not sure how their activity could impact REST updates. Sent from my ADR6300 using Tapatalk 2

1. 7/30/2012 8:00am - Put ISY in trusted zone of DSCLink PC NIS Results 7/30/2012 9:39pm No ISY error log entries since but still getting timeouts on DSCLink REST updates 7/31/2012 7:30 No ISY error log entries and 7 DSCLink Rest timeouts ... about one per each full DSC hourly update and different variable each time 2. Disable programs that run based on DSCLink variables -- Very few program runs immediatly as a result of variable updates. The value of DSC variables are used at other times as part of an and condition to determine if programs run as needed. The alarm variable = 1 is notable exception. 3. Remove NIS

Michel: Will create programs for thermostat set point values greater than 80 or less than 60 for each tstat. While, I have not noticied it, I'm guessing you're thinking (or we're trying to determine if) the thermostat actually has these wierd numbers as set points? What else should program include to aid diagnosis? Thanks, Paul

Gentlemen: Thanks. Based on your input, I will perform following actions one at a time and note results every few days. 1. 7/30/2012 8:00am - Put ISY in trusted zone of DSCLink PC NIS Results 7/20/2012 9:39pm No ISY error log entries since but still getting timeouts on DSCLink REST updates 2. Disable programs that run based on DSCLink variables -- Very few program runs immediatly as a result of variable updates. The value of DSC variables are used at other times as part of an and condition to determine if programs run as needed. The alarm variable = 1 is notable exception. 3. Remove NIS To provide additional details, I perform a DSC panel update request from ISY to DSCLink every hour since DSC documentation states you cannot depend on all actions to be broadcast and many (but not all) timeouts during this update (I have 30 zones variables and all other standard like away stay alarm ready etc). The reason I'm evaluating my environment is a time out occured during alarm system test and the alarm variable REST update timed out. Paul

Thanks for feedback. There are not programs that trigger based on thermostat updates/values so for now I'll consider this not part of DSCLink Issue.

Michel: I have three thermostat adapters that are all version 2.2R and they are not members of scenes. I set their heat and cool set points via programs. Only one log entry out of several thousand during a month was for 0. There are a few where the System value is 16 and that occurs on all three thermostats. One of the three thermostats had only one entry with 0. Paul

Michel: No problems on reply. As always you and team do an excellent job and I'm just trying to get handle on where configuration stands. The ISY is only talking to the one PC with DSCLink installed and that PC does have Norton Internet Security. Would ISY sometimes get responses and other times be refused? I looked at PC NIS network map and marked ISY as fully trusted so can see if that makes a difference. More to what I was looking to determine was the issue with DSCLink timeouts and the speed of REST updates compared to what io_guy gets. Can you offer suggestions on what I should review? BTW, all three of recent posts are part of a tune up review to make sure all is well -- have not done this in quite some time. Thanks.

I felt the "System" entry was the reply/update but was more interested in why the strange values from second half of inquiry. Thanks

Hi Michel: Given the retries and tiemouts with DSCLink from post below, this was one of several avenues I saw that flet may be contributing. In one month there were 90,000 entries in log and 60,000 were thermostat update related.

According to instruction manual v2.2R thermostat adapters are supposed to stablize to a value for 2 miutes before an update occurs. If I went back to manual method and queried every 30 to 60 minutes my insteon traffic would be much reduced since I have 3 adapters. Located how to do this in adapter user manual listed below. In final step (4) how would I modify for ISY? Does this cause adapter to stop broadcasting reports or does it still send but is ignored since not linked? In genral ... do you recommend doing this? what are others doing? may be able to show some values update more frequently than 2 minutes -- contact Smarthome? Disabling Change Reports 1) Set the thermostat to Off mode 2) Press & hold the Set button Thermostat Adapter for 3 seconds The Thermostat Adapter Status LED will begin blinking The thermostat display will flash all the LCD characters once 3) Press & hold the Set button on Thermostat Adapter for 3 seconds again The Thermostat Adapter Status LED will continue blinking The thermostat display will flash all the LCD characters once 4) Press & hold the Responder’s Set button for 3 seconds The Thermostat Adapter Status LED will stop blinking The thermostat display will flash all the LCD characters once

Was going through log and thought I had a program triggering twice to set heat and cool setpoint but notice one had user "Program" and other system "System". I assume this is normal per below: Master Suite / Master Bedroom:Thermostat Heat Setpoint 70 Sun 2012/06/17 09:00:00 AM Program Log Master Suite / Master Bedroom:Thermostat Heat Setpoint 70 Sun 2012/06/17 09:00:00 AM System Log Master Suite / Master Bedroom:Thermostat Cool Setpoint 75 Sun 2012/06/17 09:00:00 AM Program Log Master Suite / Master Bedroom:Thermostat Cool Setpoint 75 Sun 2012/06/17 09:00:01 AM System Log Also, see "System" entries that have an unusal number and at odd times. They have been 0,1,119,12,16,255,37, and 38. The most common is 16 and couple follow. Master Suite / Master Bedroom:Thermostat Cool Setpoint 0 Fri 2012/07/27 05:22:24 AM System Log Master Suite / Master Bedroom:Thermostat Cool Setpoint 16 Sat 2012/07/28 07:52:15 AM System Log

From DSCLink forum conversations with io_guy and reviewing my log files, I'm getting slow response and many retries to REST commands. io_guy indicates getting 6 REST updates in a couple seconds and retries only during 3:00 am resync of ISY. From reviewing my log, I get retries all during the day (will have between 80-100 today) and REST updates take 5-15 seconds on a regular basis. The ISY and DSCLink PC are on same network switch and I've looked and don't see anything talking to ISY other than DSCLink. What should I look at to diagnose? I would like REST response faster with retries reduced for optimal inferface with security system and in turn web cam recording software. Also, I've posted couple other questions about thermostat activity. They may have some bearing on this question but seperated them if just coincidental issues. Thanks Last few days of error log: Time User Code Message Sun 2012/07/22 12:16:48 PM System -5012 164 Sun 2012/07/22 12:17:01 PM System -5012 165 Sun 2012/07/22 12:17:31 PM System -170001 [uDSockets] RSub:40 error:6 Sun 2012/07/22 12:22:57 PM System -170001 [uDSockets] HTTP:32 error:6 Sun 2012/07/22 12:23:02 PM System -170001 [uDSockets] HTTP:32 error:6 Mon 2012/07/23 09:17:30 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 5 Mon 2012/07/23 09:19:53 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2012/07/23 09:22:30 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 6 Mon 2012/07/23 10:19:53 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2012/07/23 11:19:53 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2012/07/23 12:19:53 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2012/07/23 01:19:53 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2012/07/23 08:20:13 PM System -5012 174 Mon 2012/07/23 08:21:40 PM System -5012 175 Mon 2012/07/23 09:21:01 PM System -140005 Net Module Rule: 5 Tue 2012/07/24 11:24:34 AM System -5012 177 Tue 2012/07/24 11:24:46 AM System -5012 178 Tue 2012/07/24 11:25:29 AM System -5012 179 Tue 2012/07/24 11:25:29 AM System -5006 uuid:179 Tue 2012/07/24 11:25:31 AM System -5006 uuid:179 Tue 2012/07/24 11:26:59 AM System -170001 [uDSockets] RSub:40 error:6 Tue 2012/07/24 03:52:41 PM System -140000 datafeed.weatherbug.com Tue 2012/07/24 10:03:41 PM System -5012 181 Tue 2012/07/24 10:03:42 PM System -5006 uuid:181 Tue 2012/07/24 10:03:44 PM System -5006 uuid:181 Tue 2012/07/24 10:06:38 PM System -5012 182 Tue 2012/07/24 10:06:43 PM System -5006 uuid:181 Tue 2012/07/24 10:06:45 PM System -5006 uuid:181 Tue 2012/07/24 11:52:33 PM System -140000 datafeed.weatherbug.com Wed 2012/07/25 07:19:45 AM System -5012 184 Wed 2012/07/25 07:19:47 AM System -5006 uuid:184 Wed 2012/07/25 07:19:49 AM System -5006 uuid:184 Wed 2012/07/25 07:31:32 PM System -10108 Check log Thu 2012/07/26 07:16:33 AM System -10011 n/a Thu 2012/07/26 08:32:44 AM System -5012 188 Thu 2012/07/26 08:34:18 AM System -5012 190 Thu 2012/07/26 08:34:19 AM System -5006 uuid:190 Thu 2012/07/26 08:34:21 AM System -5006 uuid:190 Thu 2012/07/26 09:22:27 PM System -170001 [uDSockets] HTTP:26 error:6 Thu 2012/07/26 09:22:32 PM System -170001 [uDSockets] HTTP:26 error:6 Thu 2012/07/26 10:40:06 PM System -5012 192 Thu 2012/07/26 10:40:07 PM System -5006 uuid:192 Thu 2012/07/26 10:40:09 PM System -5006 uuid:192 Fri 2012/07/27 01:22:26 AM System -170001 [uDSockets] HTTP:26 error:6 Fri 2012/07/27 01:22:31 AM System -170001 [uDSockets] HTTP:26 error:6 Fri 2012/07/27 01:22:36 AM System -170001 [uDSockets] HTTP:26 error:6 Fri 2012/07/27 04:22:22 AM System -170001 [uDSockets] HTTP:27 error:6 Fri 2012/07/27 07:22:23 AM System -170001 [uDSockets] HTTP:30 error:6 Sat 2012/07/28 08:22:20 AM System -170001 [uDSockets] HTTP:30 error:6 Sat 2012/07/28 08:22:25 AM System -170001 [uDSockets] HTTP:30 error:6 Sat 2012/07/28 09:22:25 AM System -170001 [uDSockets] HTTP:26 error:6 Sat 2012/07/28 09:22:30 AM System -170001 [uDSockets] HTTP:26 error:6

It is a linksys wrt610n.

Thanks for consideration. I use DHCP reservations.

Michel: First, I'm on latest firmmware 3.2.6 and don't have regular network issues? I've seen the issue(s) surrounded by DNS errors and I just reboot ISY. On most ocassions, weatherbug or time have stopped reporting and all other network connections are working .... I run test email/txt program and I can connect wity Mobilinc, ISYajax and PC. In future release, could some of the system errors be exposed to programs (with me including controls to keep from getting a 1000 txt messages when there is general network failure -- oh wait that won't happen )? Maybe we could work with io_guy to have a heartbeat variable monitor program in reverse like DSCLink from a supervising PC and it could send txt message? io_guy are you tunned in? Just moved to DSCLink and that allowed me to retire current HomeSeer so I'm now using ISY for total HA. As usual working fantastic. Thanks, Paul

On occassion, I get errors where ntp service or weather bug has stopped responding. The error log will be full of errors when I notice and look. Is there a method to catch these errors in a program so I could for example send myself a text to investigate service issue?

I knew there was a reason I installed the XP virtual machine

Michel: I upgraded to 3.2.4. However, I don't have old laptop (win XP) to access ISY which had telnet. I'll have to find another telnet program for Win 7? Been so long ... do I need to telenet in via rs232 or can I go in via IP address? Paul

My ISY with latest official release (3.1.17) was getting many errors attempting to sync with NTP service so I reboooted it. ISY restarted with normal query all sequence but then it displayed an additional very slow moving work in progress bar (about 10 minutes to get to 100%). I have a program that sends me a text message at startup so I can review a couple program states and the text message did not arrive until after the progress bar finished so I took a quick look at error log to see if something was wrong and found the following: (BTW I get error messages about opening elk files even though I do not have the module ... no big deal unless it suaggests something larger) Time User Code Message Wed 2012/04/18 08:52:46 AM System -170001 [HTTP] Socket not active#2 30 Wed 2012/04/18 08:52:48 AM System -170001 [HTTP] Socket not active#2 33 Wed 2012/04/18 08:53:04 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:53:25 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:53:51 AM System -170001 [HTTP] Socket not active#2 33 Wed 2012/04/18 08:54:16 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:54:40 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:05 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:30 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:54 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:56:19 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:56:39 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF Wed 2012/04/18 08:56:39 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF Wed 2012/04/18 08:57:33 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:57:58 AM System -170001 [HTTP] Invalid socket 30

...just assumed program had to have a condition. Thanks for information about 3.1.?, UD always has solid software and the best support of any product I've ever purchased. I've had HS for years starting in X10 days -- only use it today for interface to DSC panel so I'm look forward to upgrading to variables, implementing DSCLink and retiring HS 2.x. We'll see if 3.x adds any value but I doubt it since all I read is Zwave as in waving goodbye

I want to run a program at reboot (power failure) so I can manually reset the value of a couble program variables that need to be persisted. I'll upgrade to 3.1.? when I have time but system is rock solid and I don't need another project now Easy enough to say run at startup but what "if" condition should I use? Device status, schedule etc?

Okay Thanks. I also want the button to run the then or else branch of the program to set its state. How do I do this without infinite loop? My first thought was make KPL button a controller instead of responder but I think this would create loop issue.

I just added 8 button keypadlinc. I want three buttons to follow the state of 3 programs corresponding. My thought was to turn the button on in the then branch and turn it off in the else branch. Please clue me in as to the nomenclature of Insteon command action for keypadlinc buttons with format of: On 99 / Off 99 (Backlight Level)

I've added 12 IRLinc TX devices to ISY following ISY console onscreen instructions. It appears that the resulting IRLinc TX devices must be added to a scene and then that scene must be turned On for the IR command to be issued. Is this correct or can the IR command be issued for on and/or off command ... or am I missing details on how this works. Thanks.

Upgraded from 2.7.15 to 2.8.15 went well .. yesterday.