CompKing

Thank you for the prompt response. So it sounds to me even though there is a bug in the log, the "fix" will also impact the erroneous impact on my programs which rely on the returned value of the thermostat? Thanks

I have captured the event using Event Viewer. I hope this helps. The time of "status" being reported as "0" in the event log shows as 03:06:01 PM The relevant areas of the log are: 2009/01/03 15:04:11 : [iNST-SRX ] 02 50 0A.3C.92 0C.A5.CB 41 13 01 LTOFFRR(01) 2009/01/03 15:04:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:04:20 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:04:21 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32) 2009/01/03 15:04:21 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:04:30 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:04:39 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:04:40 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32) 2009/01/03 15:04:41 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:04:49 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:04:50 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 23 6A 18 (18) 2009/01/03 15:04:50 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:04:59 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:04:59 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01) 2009/01/03 15:04:59 : [ Time] 15:05:29 1(0) 2009/01/03 15:05:16 : [ Time] 15:05:46 1(0) 2009/01/03 15:05:18 : [iNST-ACK ] 02 62 00.00.21 CF 11 FF 06 LTONRR (FF) 2009/01/03 15:05:19 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 07 06 (07) 2009/01/03 15:05:28 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 07 06 (07) 2009/01/03 15:05:30 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 07 (07) 2009/01/03 15:05:30 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:05:30 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 00 (00) 2009/01/03 15:05:31 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:05:39 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:05:40 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32) 2009/01/03 15:05:40 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:05:49 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:05:50 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 18 (18) 2009/01/03 15:05:50 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:05:59 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:06:08 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:06:09 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01) 2009/01/03 15:06:09 : [ A AD 16 4] ST 255 2009/01/03 15:06:09 : [ 9 91 5D 5] ST 255 2009/01/03 15:06:09 : [ B E3 76 1] ST 255 2009/01/03 15:06:09 : [ E 63 53 1] ST 0 2009/01/03 15:06:09 : [iNST-ACK ] 02 62 00.00.24 CF 11 FF 06 LTONRR (FF) 2009/01/03 15:06:10 : [iNST-ACK ] 02 62 0E.63.53 0F 6D 24 06 (24) 2009/01/03 15:06:12 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6D 24 (24) 2009/01/03 15:06:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:06:12 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 00 (00) 2009/01/03 15:06:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:06:13 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 24 (24) 2009/01/03 15:06:13 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:06:22 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:06:23 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 19 (19) 2009/01/03 15:06:24 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:06:25 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01) 2009/01/03 15:06:26 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 04 06 (04) 2009/01/03 15:06:35 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 04 06 (04) 2009/01/03 15:06:35 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 04 (04) 2009/01/03 15:06:35 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:06:44 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00) 2009/01/03 15:06:46 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 23 6A 32 (32) 2009/01/03 15:06:46 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:06:55 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20) 2009/01/03 15:06:56 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 24 (24) 2009/01/03 15:06:56 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:07:05 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60) 2009/01/03 15:07:05 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 19 (19) 2009/01/03 15:07:05 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:07:14 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02) 2009/01/03 15:07:15 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01) 2009/01/03 15:07:15 : [ A AA F5 8] ST 255 2009/01/03 15:07:15 : [ A AE 44 5] ST 255 2009/01/03 15:07:15 : [ 9 91 5D 4] ST 255 2009/01/03 15:07:15 : [ E 63 53 1] CLISP 36 2009/01/03 15:07:16 : [ E 63 53 1] CLIHUM 25 2009/01/03 15:07:16 : [iNST-ACK ] 02 62 00.00.24 CF 11 FF 06 LTONRR (FF) 2009/01/03 15:07:16 : [ E 63 53 1] ST 50

I have a program which regularly (every 5 mins) queries the thermostat for its reported temperature. I have a program which monitors the value and if below a threshold it adjusts the set temperature. I have had this program running for approx 4 months in all the prior betas. A symptom I have is occasionally the program is executed when the temperature reported is erroneously reported as "zero", which may be a default on bad comm's. As a "wireless device", perfect communication is likely not possible. So far, I only have a capture of my log with the Temperature entries. I have turned on event viewer to see if I can capture level 2 comms when this happens. The funny part is this only happened weekly previously. Now, it seems to happen multiple times in a single day. Here is a log of the applicable portion. THERMOSTAT Status Query░ Sat 01/03/2009 11:51:51 AM Program Log THERMOSTAT Status Query░ Sat 01/03/2009 11:51:51 AM Program Log THERMOSTAT Humidity 0.24 Sat 01/03/2009 11:52:04 AM System Log THERMOSTAT Fan State On Sat 01/03/2009 11:55:59 AM Program Log THERMOSTAT Status 26░ Sat 01/03/2009 11:56:10 AM System Log THERMOSTAT Humidity 0.23 Sat 01/03/2009 11:56:22 AM System Log THERMOSTAT Fan State Auto Sat 01/03/2009 11:56:25 AM Program Log THERMOSTAT Humidity 0.24 Sat 01/03/2009 11:57:01 AM System Log THERMOSTAT Status Query░ Sat 01/03/2009 11:57:09 AM Program Log THERMOSTAT Status Query░ Sat 01/03/2009 11:57:09 AM Program Log THERMOSTAT Status Query░ Sat 01/03/2009 12:03:31 PM Program Log THERMOSTAT Status Query░ Sat 01/03/2009 12:03:31 PM Program Log THERMOSTAT Status 27░ Sat 01/03/2009 12:03:33 PM System Log THERMOSTAT Fan State On Sat 01/03/2009 12:04:10 PM Program Log THERMOSTAT Status 0░ Sat 01/03/2009 12:04:44 PM System Log THERMOSTAT Heat Setpoint 18░ Sat 01/03/2009 12:05:16 PM Program Log THERMOSTAT Status 27░ Sat 01/03/2009 12:05:20 PM System Log THERMOSTAT Setpoint 18░ Sat 01/03/2009 12:05:53 PM System Log THERMOSTAT Thermostat Mode Heat Sat 01/03/2009 12:06:37 PM Program Log THERMOSTAT Humidity 0.23 Sat 01/03/2009 12:07:20 PM System Log Note the "Status 0". Also note the number of entries in each "5 minute" time period varies. Some have 2 lines with values, some have 3 lines. Some show 'Query' and no results, and some are quite comprehensive. Regardless of how good/poor my wireless traffic, I would argue that a zero value should not be assumed unless on poor data packets. Regards Geoff

It's been a while since I have seen discussion on this topic. With the current protocols, it appears to only be possible to query the humidity of the thermostat (with appropriate thermostat/module). Is it viable in the future that the ISY will also be able to control the themostat's set level for Humidity? If so, would it be only a software (protocol) upgrade for the ISY or would new hardware be needed for the Venstar thermostat/insteon module? (i.e. is it impossible for the Insteon venstar module to set this value to the Venstar themostat, even though it can query the value) It is likely this functionality has been considered, and is tabled on a "to-do" list. If that is the case, has there been any current development? Regards Geoff

It appears searching about WB's history that this application started in the U.S. There was an announcement that a company was going to implement WB infrastructure in Canada over the next 3 years. I am located in Calgary, AB, Canada. The native desktop application doesn't allow me to select Canadian cities, so I cannot tell whether there are WB stations located nearby. I have seen forum posts that some people close to the border are able to locate WB stations located in Canada by using a zip code located in the norther part of the U.S. With the ISY module, is it possible to pick/locate stations in Canada? Regards Geoff

My https: also works fine, but http: doesn't. I would like to have port 80 open as I am trying to access my lighting from within my LAN and not externally. I am using the WiFi built into my iPhone. Regards Geoff