mdyod Posted November 29, 2012 Author Posted November 29, 2012 RemotLinc does work in thermostat location Here's the trace.... Wed 11/28/2012 06:34:59 PM : [ Time] 18:35:00 13(0) Wed 11/28/2012 06:35:54 PM : ---- Initializing the linked devices ---- Wed 11/28/2012 06:35:54 PM : ---- All Linked Devices are now initialized ---- Wed 11/28/2012 06:35:54 PM : ---- Add remaining devices ---- Wed 11/28/2012 06:35:54 PM : [iNST-TX-I1 ] 02 62 14 B9 F7 0F 0D 00 Wed 11/28/2012 06:35:54 PM : [iNST-ACK ] 02 62 14.B9.F7 0F 0D 00 06 (00) Wed 11/28/2012 06:36:03 PM : [iNST-TX-I1 ] 02 62 14 B9 F7 0F 0D 00 Wed 11/28/2012 06:36:03 PM : [iNST-ACK ] 02 62 14.B9.F7 0F 0D 00 06 (00) Wed 11/28/2012 06:36:12 PM : [iNST-TX-I1 ] 02 62 14 B9 F7 0F 0D 00 Wed 11/28/2012 06:36:12 PM : [iNST-ACK ] 02 62 14.B9.F7 0F 0D 00 06 (00) Wed 11/28/2012 06:36:16 PM : ---- All Remaining Device Added ---- Wed 11/28/2012 06:36:16 PM : [All ] Writing 0 bytes to devices
LeeG Posted November 29, 2012 Posted November 29, 2012 No change. There are no 02 5x inbound messages from the thermostat. With the RemoteLinc working either the thermostat is defective or a very remote possibility the Insteon Address label on the thermostat is wrong. It happens once every two or three years. Try using Start Linking. Once the PLM LED starts to blink press the Set button on the thermostat for 3-5 seconds. I would have the Event Viewer running at Level 3 so that any inbound message (02 5x) from the thermostat will be visible. The inbound message (if it happens) will have the actual Insteon address that is burned into the thermostat internal PLM. If an inbound message is not received immediately after pressing the thermostat Set button, click Finish to bring down Start Linking, If no message is received with the Set button after getting the Access Points on opposite legs and the RemoteLinc working from the thermostat location I would replace the thermostat.
mdyod Posted November 29, 2012 Author Posted November 29, 2012 I ran it twice... Thu 11/29/2012 07:40:06 AM : [LNK-BGN ] 02 64 01 00 06 Thu 11/29/2012 07:40:36 AM : ---- Initializing the linked devices ---- Thu 11/29/2012 07:40:36 AM : ---- All Linked Devices are now initialized ---- Thu 11/29/2012 07:40:36 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Thu 11/29/2012 07:40:36 AM : ---- Initializing the linked devices ---- Thu 11/29/2012 07:40:36 AM : ---- All Linked Devices are now initialized ---- Thu 11/29/2012 07:40:36 AM : [All ] Writing 0 bytes to devices Thu 11/29/2012 07:40:36 AM : [All ] Writing 0 bytes to devices Thu 11/29/2012 07:40:51 AM : [LNK-BGN ] 02 64 01 00 06 Thu 11/29/2012 07:41:23 AM : ---- Initializing the linked devices ---- Thu 11/29/2012 07:41:23 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Thu 11/29/2012 07:41:23 AM : ---- All Linked Devices are now initialized ---- Thu 11/29/2012 07:41:23 AM : ---- Initializing the linked devices ---- Thu 11/29/2012 07:41:23 AM : ---- All Linked Devices are now initialized ---- Thu 11/29/2012 07:41:23 AM : [All ] Writing 0 bytes to devices Thu 11/29/2012 07:41:23 AM : [All ] Writing 0 bytes to devices
LeeG Posted November 29, 2012 Posted November 29, 2012 Nothing from the thermostat in response to the Set button press. I am always reluctant to conclude a device is not working. Most of the time there is some explanation for the problem other than it is not working. In this case I don't have another test to run. Everything indicates a thermostat problem.
mdyod Posted January 26, 2013 Author Posted January 26, 2013 OK - Sorry to be so long getting back to this issue, but the Holidays and family obligations took priority for a while... I am now using a brand new Thermostat - and the same thing is happening - I STILL can not get it to link. Interestingly, when using the "start linking/press set button" the PLM responds to the "3-5 second set button press" by producing a long chirp... but the thermostat is still not showing up in the device list. below are the traces for both methods of adding the device... Thanks in advance for your help... Sat 01/26/2013 09:41:06 AM : ---- Initializing the linked devices ---- Sat 01/26/2013 09:41:06 AM : ---- All Linked Devices are now initialized ---- Sat 01/26/2013 09:41:06 AM : ---- Add remaining devices ---- Sat 01/26/2013 09:41:06 AM : [iNST-TX-I1 ] 02 62 21 DA 69 0F 0D 00 Sat 01/26/2013 09:41:06 AM : [iNST-ACK ] 02 62 21.DA.69 0F 0D 00 06 (00) Sat 01/26/2013 09:41:15 AM : [iNST-TX-I1 ] 02 62 21 DA 69 0F 0D 00 Sat 01/26/2013 09:41:15 AM : [iNST-ACK ] 02 62 21.DA.69 0F 0D 00 06 (00) Sat 01/26/2013 09:41:24 AM : [iNST-TX-I1 ] 02 62 21 DA 69 0F 0D 00 Sat 01/26/2013 09:41:24 AM : [iNST-ACK ] 02 62 21.DA.69 0F 0D 00 06 (00) Sat 01/26/2013 09:41:28 AM : ---- All Remaining Device Added ---- Sat 01/26/2013 09:41:28 AM : [All ] Writing 0 bytes to devices Sat 01/26/2013 09:43:30 AM : [LNK-BGN ] 02 64 01 00 06 Sat 01/26/2013 09:43:50 AM : ---- Initializing the linked devices ---- Sat 01/26/2013 09:43:50 AM : ---- All Linked Devices are now initialized ---- Sat 01/26/2013 09:43:50 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Sat 01/26/2013 09:43:50 AM : ---- Initializing the linked devices ---- Sat 01/26/2013 09:43:50 AM : ---- All Linked Devices are now initialized ---- Sat 01/26/2013 09:43:50 AM : [All ] Writing 0 bytes to devices Sat 01/26/2013 09:43:50 AM : [All ] Writing 0 bytes to devices
LeeG Posted January 26, 2013 Posted January 26, 2013 The symptom remains consistent, no response from thermostat. The event trace shows 02 62 messages which are outbound Insteon messages. There continue to be no 02 50 or 02 51 inbound Insteon messages. With two thermostats producing the same results there is an issue with RF coverage at the thermostat site. I Deleted a T2491T1E and added it back to show what the beginning of a New INSTEON Device event trace will look like. Note the 02 50 inbound messages that are missing from the trace of your thermostat. Sat 01/26/2013 10:59:29 AM : [14 B7 2A ] Added to list of devices to link to ISY Sat 01/26/2013 10:59:29 AM : [iNST-TX-I1 ] 02 62 14 B7 2A 0F 0D 00 Sat 01/26/2013 10:59:29 AM : [iNST-ACK ] 02 62 14.B7.2A 0F 0D 00 06 (00) Sat 01/26/2013 10:59:29 AM : [iNST-SRX ] 02 50 14.B7.2A 19.70.06 2B 0D 02 (02) Sat 01/26/2013 10:59:29 AM : [std-Direct Ack] 14.B7.2A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 01/26/2013 10:59:29 AM : [iNST-TX-I1 ] 02 62 14 B7 2A 0F 10 00 Sat 01/26/2013 10:59:29 AM : [iNST-ACK ] 02 62 14.B7.2A 0F 10 00 06 ID-REQ (00) Sat 01/26/2013 10:59:30 AM : [iNST-SRX ] 02 50 14.B7.2A 19.70.06 2B 10 00 ID-REQ (00) Sat 01/26/2013 10:59:30 AM : [std-Direct Ack] 14.B7.2A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 01/26/2013 10:59:30 AM : [iNST-SRX ] 02 50 14.B7.2A 05.0E.95 8B 01 00 (00) Sat 01/26/2013 10:59:30 AM : [std-Broadcast] 14.B7.2A-->05.0E.95, Max Hops=3, Hops Left=2
mdyod Posted February 1, 2013 Author Posted February 1, 2013 I see that but I have an AP within 5 feet or the thermostat and my PLM is within 3 feet.. WHat else can i try? Thanks D
LeeG Posted February 1, 2013 Posted February 1, 2013 Process of elimination. Operate another RF only device at the thermostat location. Pushing a button on a RemoteLinc2 held next to the thermostat for example. Does the button activity show up in the event trace. If not the issue is with the Access Point or PLM (assuming 2413), or perhaps there is something in the area such as a baby monitor, wireless phone in the 900 MHz range, etc. If the RemoteLinc2 button activity is traced but the thermostat is not, that would indicate a thermostat issue. Maybe a factory reset.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.