Teken Posted January 27, 2012 Posted January 27, 2012 For the benefit of others who may be following this topic, Smarthome has discontinued the 2476ST device. Really? When did this happen and why?? Teken . . .
LeeG Posted January 27, 2012 Posted January 27, 2012 Don't know. Went to the SH web site to pull down data on the 2476ST. Search no longer finds that type. The very first post on page 1 of this topic has the link to the sales page. That page now says the device has been discontinued. Poor sales or maybe issues with the device. They rarely every indicate a why.
Teken Posted January 27, 2012 Posted January 27, 2012 Don't know. Went to the SH web site to pull down data on the 2476ST. Search no longer finds that type. The very first post on page 1 of this topic has the link to the sales page. That page now says the device has been discontinued. Poor sales or maybe issues with the device. They rarely every indicate a why. Ughhhhhhhhhhhhhh . . . Well, if I need a replacement I guess they better have some back up inventory!! And . . . How on Gods green Earth do you kill the power on these stupid things??? All of these devices have the clear plastic set button. Yet pulling on any of them does NOT kill the power to the device?? WTF?? Teken . . .
LeeG Posted January 27, 2012 Posted January 27, 2012 Turns out I had archived a copy of the 2476ST User Guide. From the User Guide ... "Pulling the Set button at the bottom of the paddle out as far as it will go (about 1/8 inch) opens mechanical contacts that remove all power from SwitchLinc and its load." Perhaps that is why the product was discontinued.
Teken Posted January 27, 2012 Posted January 27, 2012 Turns out I had archived a copy of the 2476ST User Guide. From the User Guide ... "Pulling the Set button at the bottom of the paddle out as far as it will go (about 1/8 inch) opens mechanical contacts that remove all power from SwitchLinc and its load." Perhaps that is why the product was discontinued. LeeG, I'm sorry but your quote doesn't make any sense to me?? Pulling out the plastic set button does absolutely nothing to any of these devices?? The LED remains lit and you do not hear the standard click at all. Teken . . .
LeeG Posted January 27, 2012 Posted January 27, 2012 I understood your previous post. The User Guide indicates the Air Gap switch should remove power from the SwitchLinc and the load. Since it does not on multiple devices I was guessing that might be the reason for the device being discontinued.
Brian H Posted January 27, 2012 Posted January 27, 2012 Maybe it was made with the older 2476S design and didn't have any Air Gap Switch. All of my old hardware revision 2476S SwitchLinc Relay modules don't have an Air Gap Switch and use a 100% different method to do a Factory Reset. The on line 2476ST page also does not say anything about the Air gap Switch when doing a factory reset. http://wiki.smarthome.com/index.php?tit ... t_Settings
Brian H Posted January 27, 2012 Posted January 27, 2012 Teken, Are the two 2476ST modules different revisions? As I see the ISY reports one has a v.63 firmware and the other one a v.38. The unofficial list of users inputed data indicated the v.63 is an i1 device and the v.38 is the newer i2 device.
Teken Posted January 27, 2012 Posted January 27, 2012 Teken, Are the two 2476ST modules different revisions?As I see the ISY reports one has a v.63 firmware and the other one a v.38. The unofficial list of users inputed data indicated the v.63 is an i1 device and the v.38 is the newer i2 device. Yes, there are indeed two different versions in the home. The odd thing is that the device with the ISY v.63 was made a lot earlier than the v.38?? How does one go from v.63 to v.38?? I have to gather this was during the i1 support only and this was the version being released at the time. I can't understand how the vendor sold me two different versions during the original sale? Regardless, none of these SwitchLinc Timers operate as expected anymore. They control the local load just fine, react to linked commands, and also operate fine via the ISY Admin Center. Yet, all of the sudden none of them work internally as a timer now?? Teken . . .
Brian H Posted January 28, 2012 Posted January 28, 2012 I have also seen this firmware and hardware version numbers change with models. I have some 2876SB Icon On/Off switches. The older ones with green LED are hardware 1.1 and firmware v.60. The later one with Amber LED is a hardware 1.0 firmware v.28. I hope someone from UDI can find out whet happed to your units. I believe there are some parameters that can be charged in them to do things like disable the timer functions.
Teken Posted January 28, 2012 Posted January 28, 2012 Maybe it was made with the older 2476S design and didn't have any Air Gap Switch.All of my old hardware revision 2476S SwitchLinc Relay modules don't have an Air Gap Switch and use a 100% different method to do a Factory Reset. The on line 2476ST page also does not say anything about the Air gap Switch when doing a factory reset. http://wiki.smarthome.com/index.php?tit ... t_Settings Brian, Thank you so much for linking me to the factory reset procedures. I attempted to reset all three timers, but quite honestly I don't know if it worked?? The reason I say this is that the switch does not behave as one would expect during a reset. I will have to perform the reset one more time so I can document what LED flashes, and the order in which they occur so others may supply some feed back. Going off memory: Pressing the paddle up and holding for what seems like eternity. The top LED pulses, the bottom one appears to blink as well?? Pressing the set button for another 10 seconds, doesn't seem to do anything. No beep, no click, no nothing. Pressing the set button for another 10 seconds, again doesn't seem to do anything either. No beep, no click, no flash of the LED?? The only way I can tell something has occurred is the simple fact previous linked devices no longer turn this device on / off. This same switch also does not react to other linked devices via the ISY etc. I gather this device is reset at this point?? Removing and re-adding the device back into the ISY tree also did not resolve the odd timer values present in device. Help . . . Teken . . .
Brian H Posted January 28, 2012 Posted January 28, 2012 If your memory is correct you may have missed a step. Hold the top paddle until the top LED flashes and release. I don't remember if the bottom one may also. Then push the set button in momentarily and release. Then hold the set button in again for ten seconds and release.
Teken Posted January 28, 2012 Posted January 28, 2012 If your memory is correct you may have missed a step.Hold the top paddle until the top LED flashes and release. I don't remember if the bottom one may also. Then push the set button in momentarily and release. Then hold the set button in again for ten seconds and release. I did not perform the 2nd set button press as described above. I will do so now but swear the e-doc said to press the set button and hold for 10 seconds. Two separate times . . . Teken . . .
Teken Posted January 28, 2012 Posted January 28, 2012 OK after some trial and error these are my observations. The timer value window does absolutely nothing for these four SwitchLinc Timers. It appears to request what the default timer value's are from the switch. I have one v.38 at the stairs and this device has a timer value of 15 minutes. Next, is a ceiling fixture v.38 which has this insane default of 255 minutes! Keep in mind this light fixture worked perfectly fine before with a default of 15 minutes etc. It has since changed and I can not restore this 15 minute value any longer! The next one is in my daughters room v.63 (This device used to work just fine, then out of no where the timer just stopped working!) The ISY shows a default timer value of 0? Last but not least is the hall way corridor light v.63. The ISY shows a default timer value of 0 as well. In all cases none of the timers can be changed via the ISY Admin Center. While the other settings do seem to perform some interactions, such as the blink when LED TX is enabled. I have no clue whether or not the other check box operate or not since I can't make them change the default timers. Insight . . . Teken . . .
LeeG Posted January 28, 2012 Posted January 28, 2012 Only to the two older SwitchLincs. The ISY is using I2 Extended Set/Get commands to read/write the configuration data. Very likely the older SwitchLincs do not support I2, thus the 0 timeout value. This can be confirmed with an Event Viewer trace with 3-Device communications events selected. Read the current options for one of the old SwitchLincs. This is from one of your previous posts. The 02 51 Extended response will likely not be traced with the older SwitchLinc. Fri 01/27/2012 10:28:18 AM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Fri 01/27/2012 10:28:18 AM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Fri 01/27/2012 10:28:18 AM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/27/2012 10:28:19 AM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 00 F2 00 00 00 26 B3 00
Teken Posted January 29, 2012 Posted January 29, 2012 This is the level 3 diagnostic traces from my daughters room. Each event is due to me de-selecting one of the check box's, then checking them. The first entry is my attempt to change the 0 value to something else. This is presented with a pop up error message from the ISY. So my questions remain: Are these devices broken / defective. Or is the new ISY firmware not playing nicely with these devices now? As I indicated previously everything was operating just fine before?? Teken . . . Sat 01/28/2012 07:30:42 PM : [5 F5 5D 1 ] Querying engine version Sat 01/28/2012 07:30:42 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 0D 00 06 (00) Sat 01/28/2012 07:30:42 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 0D 00 (00) Sat 01/28/2012 07:30:42 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:30:42 PM : [5 F5 5D 1 ] Retrieved engine version is i1 Sat 01/28/2012 07:30:42 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 1F 00 06 GOF (FLAGS) Sat 01/28/2012 07:30:43 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 1F 00 GOF (FLAGS) Sat 01/28/2012 07:30:43 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:30:43 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:30:43 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:30:51 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:30:58 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 02 06 (02) Sat 01/28/2012 07:30:58 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 02 (02) Sat 01/28/2012 07:30:58 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:30:58 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:08 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 03 06 (03) Sat 01/28/2012 07:31:08 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 03 (03) Sat 01/28/2012 07:31:08 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:08 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:13 PM : CLI-WBug: Connecting to datafeed.weatherbug.com Sat 01/28/2012 07:31:13 PM : CLI-WBug: Successfully Processed WBug Response Sat 01/28/2012 07:31:14 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 04 06 (04) Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 1] -130000.000000 Weather - Temperature = -13 °C Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 4] -180000.000000 Weather - Feels Like = -18 °C Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 5] -9000.000000 Weather - Temperature Rate = -0.9 °C/h Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 11] 80000.000000 Weather - Wind Speed = 8 km/h Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 12] 140000.000000 Weather - Wind Average Speed = 14 km/h Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 13] 10000.000000 Weather - Wind Direction = N Sat 01/28/2012 07:31:14 PM : [MOD 2 2 1 22] 9122.000000 Weather - Evapotranspiration = 0.9122 mm/day Sat 01/28/2012 07:31:14 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 04 (04) Sat 01/28/2012 07:31:14 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:14 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:19 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 05 06 (05) Sat 01/28/2012 07:31:19 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 05 (05) Sat 01/28/2012 07:31:19 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:19 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:23 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 06 06 (06) Sat 01/28/2012 07:31:23 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 06 (06) Sat 01/28/2012 07:31:23 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:23 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:25 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 07 06 (07) Sat 01/28/2012 07:31:26 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 07 (07) Sat 01/28/2012 07:31:26 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:26 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:28 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 08 06 (08) Sat 01/28/2012 07:31:28 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 08 (08) Sat 01/28/2012 07:31:28 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:28 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:30 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 09 06 (09) Sat 01/28/2012 07:31:30 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 09 (09) Sat 01/28/2012 07:31:30 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:30 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:32 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 0A 06 (0A) Sat 01/28/2012 07:31:32 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 0A (0A) Sat 01/28/2012 07:31:32 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:32 PM : [All ] Writing 0 bytes to devices Sat 01/28/2012 07:31:34 PM : [iNST-ACK ] 02 62 05.F5.5D 0F 20 0B 06 (0B) Sat 01/28/2012 07:31:34 PM : [iNST-SRX ] 02 50 05.F5.5D 13.24.E1 2B 20 0B (0B) Sat 01/28/2012 07:31:34 PM : [standard-Direct Ack][05.F5.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 07:31:34 PM : [All ] Writing 0 bytes to devices
LeeG Posted January 29, 2012 Posted January 29, 2012 It is an I1 device. “Retrieved engine version is i1" There is a series of changes issued. LED On during Tx LED Off during Tx Countdown Timer Disabled Countdown Timer Enabled Trigger ALL-Link Disabled Trigger ALL-Link Enabled LED Off LED Enabled 1 minute warning Disabled 1 minute warning Enabled There were no commands issued to set the Timeout Interval. Does not appear to be an I1 command to set the Timeout interval. No I1 command is listed in the command reference for that purpose. If the error popup occurred when attempting to change the Timeout interval it is a logical failure message. In other words, no command actually failed as there is no I1 command to issue. Except for the lack of an I1 command to change the Timeout interval the other commands track the options listed in the posted screen capture.
Teken Posted January 29, 2012 Posted January 29, 2012 It is an I1 device. “Retrieved engine version is i1" There is a series of changes issued. LED On during Tx LED Off during Tx Countdown Timer Disabled Countdown Timer Enabled Trigger ALL-Link Disabled Trigger ALL-Link Enabled LED Off LED Enabled 1 minute warning Disabled 1 minute warning Enabled There were no commands issued to set the Timeout Interval. Does not appear to be an I1 command to set the Timeout interval. No I1 command is listed in the command reference for that purpose. If the error popup occurred when attempting to change the Timeout interval it is a logical failure message. In other words, no command actually failed as there is no I1 command to issue. Except for the lack of an I1 command to change the Timeout interval the other commands track the options listed in the posted screen capture. So, where does this leave me then?? Teken . . .
LeeG Posted January 29, 2012 Posted January 29, 2012 From the I1 test results I would conclude the older SwitchLincs do not support changing the countdown interval programmatically. I went through the command reference again, searching for "countdown", "timeout, "interval". Found no reference for setting the countdown interval with I1 commands. All the other options displayed in the popup are described and match the commands issued in the trace. Not unlike the motion sensors. There are things that can be done programmatically with the later motion sensors that cannot be done programmatically with the early ones. Another example is some older devices must be power cycled for certain configuration changes to take effect. The I1 method for setting some values does not provide a method for activating the changes. On newer versions of the same device that support I2 configuration, changes are automatically picked up without a power cycle.
Teken Posted January 29, 2012 Posted January 29, 2012 From the I1 test results I would conclude the older SwitchLincs do not support changing the countdown interval programmatically. I went through the command reference again, searching for "countdown", "timeout, "interval". Found no reference for setting the countdown interval with I1 commands. All the other options displayed in the popup are described and match the commands issued in the trace. Not unlike the motion sensors. There are things that can be done programmatically with the later motion sensors that cannot be done programmatically with the early ones. Another example is some older devices must be power cycled for certain configuration changes to take effect. The I1 method for setting some values does not provide a method for activating the changes. On newer versions of the same device that support I2 configuration, changes are automatically picked up without a power cycle. I could understand this point *IF* all things are were equal. But, in this case I can accept that the older i1 devices don't / won't be able to take advantage of the new software etc. But, one of them had always worked fine prior to any of these firmware upgrades. Now it doesn't work at all, and has a 0 value for the timer?? Then, there are the newer style v.38 devices . . . Only one of them seems to work in terms of the default timer of 15 minutes. Yet it can not be changed?? This device controls the stair lighting. The other v.38 device controls the ceiling lights which has the same v.38 and has the 255 minute default. Which previously had a 15 minute timer, now it can not be reset, or changed?? I am at a loss here and am looking for some assistance here . . . Teken . . .
LeeG Posted January 29, 2012 Posted January 29, 2012 There is no means of retrieving the countdown value from an I1 device, thus the 0 value. The ISY cannot change the countdown interval on I1 devices so I have to conclude this is a device failure (not the 0, the fact that it does not countdown). If that is in question do a Factory Reset of the I1 device. If the device is not defective that will restore the countdown operation. I have not seen a trace of an I2 device having the countdown time changes. I'll be happy to take a look if you want to generate a test trace. With the Event Viewer running with 3-Device communications events selected, set the countdown interval to some value, say 100, click Save and then Close. Bring up the configuration popup again and change the countdown value to 50, click Save and then Close. Bring up configuration again and Close. Post the trace. The reason for closing and restarting the configuration process each time is the ISY retrieves the current settings with an I2 command at the beginning. Starting the configuration process new each time will show what effect the previous change actually had.
Brian H Posted January 29, 2012 Posted January 29, 2012 Since they don't have a Air Gap Switch. After the Factory Reset. Maybe a power cycle may also be needed. Though this is just a see what happens thing.
LeeG Posted January 29, 2012 Posted January 29, 2012 I looked over an I2 trace from a earlier post. The Red FF (255) is the default countdown value. The Blue F2 is the time remaining. Note that in the second 02 51 response the time remaining to Off has gone down by 1 minute (F2 to F1) which generally matches the difference in time stamps between the two trace entries. Fri 01/27/2012 10:28:19 AM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 00 F2 00 00 00 26 B3 00 Fri 01/27/2012 10:29:09 AM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 00 F1 00 00 00 2F FC 00 It would be very interesting to see what command sequence is issued when the Save button is clicked and what the read of the current values are the next time the configuration popup is displayed.
Teken Posted February 2, 2012 Posted February 2, 2012 There is no means of retrieving the countdown value from an I1 device, thus the 0 value. The ISY cannot change the countdown interval on I1 devices so I have to conclude this is a device failure (not the 0, the fact that it does not countdown). If that is in question do a Factory Reset of the I1 device. If the device is not defective that will restore the countdown operation. I have not seen a trace of an I2 device having the countdown time changes. I'll be happy to take a look if you want to generate a test trace. With the Event Viewer running with 3-Device communications events selected, set the countdown interval to some value, say 100, click Save and then Close. Bring up the configuration popup again and change the countdown value to 50, click Save and then Close. Bring up configuration again and Close. Post the trace. The reason for closing and restarting the configuration process each time is the ISY retrieves the current settings with an I2 command at the beginning. Starting the configuration process new each time will show what effect the previous change actually had. Here is the trace from the Ceiling Light. This device is V.38 and did work before several firmware changes came along. Below is the diagnostic trace records as per your request. Teken . . . Thu 02/02/2012 03:01:05 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:06 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:06 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:06 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:06 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:07 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:07 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:08 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 08 00 00 00 2C 03 00 Thu 02/02/2012 03:01:08 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:08 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:17 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 06 64 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:17 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:17 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:17 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:23 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:24 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:24 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:24 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:24 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:25 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:25 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:26 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 07 00 00 00 2D 05 00 Thu 02/02/2012 03:01:26 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:26 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:30 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 06 32 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:31 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:31 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:31 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:35 PM : CLI-WBug: Connecting to datafeed.weatherbug.com Thu 02/02/2012 03:01:35 PM : CLI-WBug: Successfully Processed WBug Response Thu 02/02/2012 03:01:35 PM : [MOD 2 2 1 11] 20000.000000 Weather - Wind Speed = 2 km/h Thu 02/02/2012 03:01:38 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:38 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:38 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:38 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:39 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:39 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:39 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:39 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 07 00 00 00 2D 05 00 Thu 02/02/2012 03:01:39 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:39 PM : [All ] Writing 0 bytes to devices
Teken Posted February 5, 2012 Posted February 5, 2012 I will be pulling these guys out of service and have them replaced under warranty. There is no head way on this matter no amount of resetting and killing the power has any affect on these things. I don't know why my gut keeps telling me there is a conflict with the newest ISY firmware that is causing this issue to appear. Unfortunately I can't roll back the firmware to find out in this case . . . Teken . . .
Recommended Posts