Teken

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

Just some feed back across the pond. The light, light rate, do not operate here as well. I changed my stations to one of 15 options with no change what so ever. Regards Teken . . .

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 . . .

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 . . .

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 . . .

To clarify: You would like to be able to view the separate temperatures via the Energy Display? Teken . . .

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 . . .

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 . . .

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 . . .

Really? When did this happen and why?? Teken . . .

This is the log files upon making the timer changes and the end results. It appears nothing is being written to the device? Teken . . . Fri 01/27/2012 10:28:08 AM : CLI-WBug: Connecting to datafeed.weatherbug.com Fri 01/27/2012 10:28:08 AM : CLI-WBug: Successfully Processed WBug Response Fri 01/27/2012 10:28:08 AM : [MOD 2 2 1 11] 110000.000000 Weather - Wind Speed = 11 km/h Fri 01/27/2012 10:28:08 AM : [MOD 2 2 1 12] 110000.000000 Weather - Wind Average Speed = 11 km/h Fri 01/27/2012 10:28:08 AM : [MOD 2 2 1 22] 5822.000000 Weather - Evapotranspiration = 0.5822 mm/day Fri 01/27/2012 10:28:17 AM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Fri 01/27/2012 10:28:18 AM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) 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:18 AM : [All ] Writing 0 bytes to devices 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 Fri 01/27/2012 10:28:19 AM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 01/27/2012 10:28:19 AM : [All ] Writing 0 bytes to devices Fri 01/27/2012 10:28:28 AM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 06 0F 00 00 00 00 00 00 00 00 00 00 00 06 (00) Fri 01/27/2012 10:28:29 AM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Fri 01/27/2012 10:28:29 AM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/27/2012 10:28:29 AM : [All ] Writing 0 bytes to devices Fri 01/27/2012 10:29:07 AM : CLI-WBug: Connecting to datafeed.weatherbug.com Fri 01/27/2012 10:29:07 AM : CLI-WBug: Successfully Processed WBug Response Fri 01/27/2012 10:29:07 AM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Fri 01/27/2012 10:29:08 AM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Fri 01/27/2012 10:29:08 AM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/27/2012 10:29:08 AM : [All ] Writing 0 bytes to devices Fri 01/27/2012 10:29:08 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:29:08 AM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Fri 01/27/2012 10:29:08 AM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 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 Fri 01/27/2012 10:29:09 AM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 01/27/2012 10:29:09 AM : [All ] Writing 0 bytes to devices

This device will not allow me to keep the new values? Once you enter the new time *15 minutes* upon re-opening the options window. The value returns back to 255 minutes? Regards Teken . . .

Hello Michel, I am receiving this error with two SwitchLinc Timers. Both devices show the ability to make changes to the parameters. But, upon making any changes I am presented with this error message. Regards Teken . . .

andyf0, That was a most excellent write up as to how to solve this problem! You're going to be my next best friend when I receive my 8 AC transformers for the remote TSTATS! Teken . . .

Hello AlanF, I shall most definitely try this to see if it works. Much thanks for your reply and feed-back! Teken . . .

I would advise you to relocate the ISY in a interior controlled environment. Air born debris, salt, chemical fumes, in the future will be your next problem. Using a 35 foot CAT5e cable will not present any problems to you what so ever. Please relocate this device so you're assured long term reliability and use. Regards Teken . . .

andyf0, You're fantastic and I thank you for the follow up and testing. I would have done this test straight away but it is currently -36'C in my garage right now so fumbling around with little frozen wires 10 feet in the air wasn't going to be fun. If the results proved unproductive or helpful . . . Much thanks again Sir! Teken . . .

Rick, Please click on the help, then about . . . This will populate the firmware version along with the ISY UI version. You will need to go to the 2nd link in the forum and follow the steps to download the current ISY firmware release. Please ensure you follow all steps outlined by Michel . . . EDIT: Here is the link you need to read and follow: viewtopic.php?f=25&t=7878 Teken . . .

andyf0, Would you mind performing a test for me and see if the *ALL OFF* does indeed operate as you indicate above. I would greatly appreciate it . . . Teken . . . I hit ALL OFF. Everything turned off and the garage door closed. I hit it again and the garage door stayed closed. As I anticipated. I also have two Venstar thermostats and their settings were maintained, they were not reset. I know you tested as indicated above. But, could you please confirm 4 more times for me while the door is down and closed. Pressing the *ALL OFF* button and confirming the door does NOT attempt to open. If so, I will rewire the I/O link accordingly. I thank you so much for doing these tests for me and the UDI membership. Teken . . .

andyf0, Would you mind performing a test for me and see if the *ALL OFF* does indeed operate as you indicate above. I would greatly appreciate it . . . Teken . . .

May I humbly suggest that you provide a check box for the I/O device, and RF TSTATS. To allow the user to determine IF this command is required. I do not want to take away something from the masses, just because (I) do not see a benefit. There may be others who do like this strange behavior and use this to their benefit. I believe having a option check box for these two devices would allow the best balance for all parties concerned. As always your continued support, guidance, and feed-back is greatly appreciated. Regards Teken . . .

LeeG / Bcall, Thank you both for the clarification on this matter. I just find this part very hard to understand and accept to be honest. I understand based on how it is described by LeeG now. But, it truly boggles my mind knowing a *ALL OFF* command would turn something *ON*?? What I am trying to grasps is this so please bare with me. Right now everything (keeping the I/O Linc out of the picture) is off. If I select the *ALL OFF* from the ISY Admin Center, everything that is OFF, will remain OFF. If I turn everything on, or random devices to a on state. Selecting *ALL OFF* will in fact send a off command and those things will turn off. There will be no device which was off, will turn on. Now, we have this I/O device . . . It is off, for both relay and sensor. I am trying to grasp why a OFF command would even have any play into this situation?? OFF is OFF . . . It is not ON !! I apologize for the rant - But, realize that my home is extremely secure and I have two things I value the most. My family, and then the possessions which I have worked very hard for, for more than three decades for. Having the whole family dead asleep one moment, then having the entire house in an alarming state, all zones being locked down, sirens, strobes, alarm company, police coming in the dead of night. Is NOT something I take lightly . . . The only saving grace is that I am aware of this strange behavior and will NOT use it any further. As aside I checked all the configurations and the only scenes created is for the I/O link to the KPL to control the OH Door. The only other links / scenes are those attached to the SmartLinc device. This device is also linked to a Appliance Linc, to provide a status feed back with respect to the doors open / close status. There is nothing else linked, or attached to the Insteon Network. I know this because this time last week the entire ISY melted down and I literally had to erase all links manually in all 70 plus devices in my home. Then, do a hard reset of the PLM, and the ISY. Just to bring that device back to a usable state . . . For reference: When this ISY meltdown occurred the device indicated some cryptic message about the ELK module (I don't have one, nor did I purchase it) then everything took a shit and died! Regardless, I just wanted everyone who has a Garage I/O kit know if they use the *ALL OFF* they may be inadvertently opening the biggest door in your home to strangers and potential thieves! If other members could please confirm / validate this does happen I would appreciate it. If it does NOT happen. Please do be kind enough to let me know how your environment is different to allow this to operate as expected. Lastly, besides this none sense. The latest firmware release is working as expected, and much thanks goes to the UDI team for their continued support and endless commitment to their customers! Regards Teken . . .

Michel, Could you please explain this to me in layman's terms? When I look at my ISY tree all of the devices are off. If I review the status of garage door sensor / relay, it too is in a off condition. If I look at the SmartLinc (Which is the only thing linked) it too is in a off state. I do not understand how a global off command can make something which is already off, turn on?? The Garage I/O kit is set up with momentary C, the KPL is set for toggle. As far as I am aware there are no other related links / scenes attached to this device. Regards Teken . . .

Michel, Tonight I observed a serious issue upon sending a *ALL OFF* command via the ISY Admin Center. When I pressed the *All Off* command the garage door opened up! I can't begin to tell you, when the central alarm system went off showing a breach in the perimeter of my home, I almost jumped out of my skin! Please let me know why this happened and how to resolve this issue . . . Regards Teken . . .

This is indeed what I have observed this evening . . . Teken . . .