jmed999 Posted June 7, 2013 Share Posted June 7, 2013 I ordered 2 new wireless thermostats (2441ZTH) V1.3 and they both linked to the ISY with ease. They have been sitting beside my computer for a couple weeks now and neither the temp nor humidity values are showing up on the admin console. They are surrounded by dual band devices (~20) within a 40' radius. The dual band PLM is about 30 ft away. I had a V1.0 for a long time and it worked great but failed due to having it out on a deck. I ordered a new one and it was a V1.3 and never could get it to link. I discussed this in another thread but that thread when off on a tangent so I abandoned it. I tried everything to get the stat to work but it never would so I returned it and bought 2 more. Those now also don't show up in the admin console. Please help me diagnose the issue. Any suggestions? Thanks in advance! Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 Run Tools | Diagnostics | Event Viewer at LEVEL 3. Do either thermostat report temp changes? If temp change messages are not being received the Admin Console would not show them. If temp change messages are being received the message structure can be analyzed to see why the ISY does not use the information. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 BTW, I just pressed the set button on one to put it in linking mode and changed the cooling setpoint temp. When I did and got the following on level 3 event viewer. Fri 06/07/2013 11:21:24 AM : [iNST-TX-I2CS] 02 62 22 0D 93 1F 6C 06 00 00 00 00 00 00 00 00 00 00 00 00 00 8E Fri 06/07/2013 11:21:24 AM : [iNST-ACK ] 02 62 22.0D.93 1F 6C 06 00 00 00 00 00 00 00 00 00 00 00 00 00 8E 06 (06) Fri 06/07/2013 11:21:24 AM : [iNST-SRX ] 02 50 22.0D.93 1C.FC.92 2B 6C 06 (06) Fri 06/07/2013 11:21:24 AM : [std-Direct Ack] 22.0D.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 11:21:24 AM : [ 22 D 93 1] CLISPC 6 Lee, if this is not what you meant please let me know. Thanks! Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 The above event viewer was changing the set point temp in the admin console and the stat in linking mode. When I change the setpoint temp on the stat (not in linking mode) it does not give anything in the event viewer level 3. Also these are both running on battery. Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 The event trace shows the set point change was successful. With Hops Left=2 comm with this tstat is good. Fri 06/07/2013 11:21:24 AM : [std-Direct Ack] 22.0D.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 11:21:24 AM : [ 22 D 93 1] CLISPC 6 The following messages are examples of humidity (6F) and temp (6E) information being sent from tstat to PLM. I was discussing these messages. Do the tstats report humidity and temp? Fri 06/07/2013 11:23:38 AM : [iNST-SRX ] 02 50 1F.0F.B4 22.80.0B 01 6F 28 (28) Fri 06/07/2013 11:23:38 AM : [std-Direct ] 1F.0F.B4-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 11:23:38 AM : [ 1F F B4 1] CLIHUM 40 Fri 06/07/2013 11:23:39 AM : [iNST-SRX ] 02 50 1F.0F.B4 22.80.0B 01 6E 37 (37) Fri 06/07/2013 11:23:39 AM : [std-Direct ] 1F.0F.B4-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 11:23:39 AM : [ 1F F B4 1] ST 55 Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 Yeah so when I put the stat in linking mode and changed the temp setpoint in the admin console it showed good comm (hops = 2) but the setpoint on the stat didn't change to the value I changed it to in the admin console. Also, when I change the setpoint temp on the stat, the event viewer doesn't show any activity so I can't give you the humidity or temp info as it doesn't appear as if the setpoint change made it to the PLM. What next? Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 The Admin Console has been eliminated as it can report only information it receives. With the tstat not reporting the information the UI cannot display it. The Cool set point was changed. Is the tstat is Cool mode? I would try and get objective information as to the number of link records in the PLM. Show PLM Links Table followed by Count. The Show / Count has to be done 3-4 times to insure the Count number is consistent as any Insteon activity reaching the PLM during the Show will produce a false link record count. It can be difficult to get a good Show PLM Links Table count in some installations. The alternative would be a Restore Modem (PLM) to compress out duplicates and rebuild the PLM link database. The PLM may be full such that the Responder link record needed in the PLM to receive messages from the tstats could not be written because the link table is full. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 The Admin Console has been eliminated as it can report only information it receives. With the tstat not reporting the information the UI cannot display it. The Cool set point was changed. Is the tstat is Cool mode? Yes it was. I don't see a show PLM links table anywhere. I'll keep looking. Where is this at? Thanks again! Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 The PLM has lost it link database. A Restore Modem (PLM) should bring it back. When I did this post I see the 0 count part of the last post has been deleted? Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 I was doing something wring....its still counting up to 400 so far. I'll post the final number shortly. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 Ok I did this 4 times and got 486, 543, 543, and 543 in that order. What next? Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 If 543 is accurate the PLM is not full. The link records for the new tstats will be at the end of the Show PLM Links Table display. Visually verify there are Responder (starts with A2 and have tstat Insteon address) link records present. Do a Show Device Links Table for the tstat you have been testing with. Click Compare when the display is complete. Are the required link records in the tstat. I have no reason to think the link records are not in the tstat and not in the PLM with a count of 543 but running out of things that would explain the lack of messages from the tstat. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 Also, while these have been sitting here the last two weeks linked but not reporting, I have installed several other insteon devices that have worked perfectly. I think and have thought this for a while now, that there is a problem with V1.3 sending info to the ISY. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 Hmmm. Not sure what else to do. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 If 543 is accurate the PLM is not full. The link records for the new tstats will be at the end of the Show PLM Links Table display. Visually verify there are Responder (starts with A2 and have tstat Insteon address) link records present. Do a Show Device Links Table for the tstat you have been testing with. Click Compare when the display is complete. Are the required link records in the tstat. I have no reason to think the link records are not in the tstat and not in the PLM with a count of 543 but running out of things that would explain the lack of messages from the tstat. -The link records for the new stats were near the end of the Show PLM Links Table. They did start with A2. -I tried to then do a Show Device Links Table but got a "Failed Reading Device ink" error. Is this due to them being on battery power? Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 If the link records check out in both the tstat and the PLM I cannot think of anything more to check. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 If the link records check out in both the tstat and the PLM I cannot think of anything more to check. As I said above, the links show up in the PLM table but when trying to do a Show Device Links Table but got a "Failed Reading Device ink" error. SO I can't confirm the links are in the stat links table. Should I delete them and try to relink them? Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 I decided to delete the stats. What is the correct way to add them? I'm pretty sure I added them correctly before but just in case how would you add them? Link to comment
Brian H Posted June 7, 2013 Share Posted June 7, 2013 You may have been able to read the link database if you woke it up with its set button. Like other battery devices are. Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 Run Tools | Diagnostics | Event Viewer at LEVEL 3 so a full trace of commands issued with results are available. I added my 2441ZTH the same way I add every device (with minor exceptions for special devices). Select New INSTEON Device. Enter Insteon Address and Name of choice, leave Device Type set for Auto Discover. Put the tstat into linking mode with tstat Set button. Click Ok on New INSTEON Device. When the device add is complete Save the event trace for analysis. It is an I2CS device so link record creation is a single command rather than a long series of 1 byte commands. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 When I added it I got the following in the event viewer... Fri 06/07/2013 03:48:33 PM : [22 d 7c ] Added to list of devices to link to ISY Fri 06/07/2013 03:48:33 PM : [iNST-TX-I1 ] 02 62 22 0D 7C 0F 0D 00 Fri 06/07/2013 03:48:33 PM : [iNST-ACK ] 02 62 22.0D.7C 0F 0D 00 06 (00) Fri 06/07/2013 03:48:33 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 0D 02 (02) Fri 06/07/2013 03:48:33 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:33 PM : [iNST-TX-I1 ] 02 62 22 0D 7C 0F 10 00 Fri 06/07/2013 03:48:33 PM : [iNST-ACK ] 02 62 22.0D.7C 0F 10 00 06 ID-REQ (00) Fri 06/07/2013 03:48:33 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 10 00 ID-REQ (00) Fri 06/07/2013 03:48:33 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:33 PM : [iNST-SRX ] 02 50 22.0D.7C 05.0A.0D 8B 01 35 (35) Fri 06/07/2013 03:48:33 PM : [std-Broadcast] 22.0D.7C-->05.0A.0D, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:33 PM : [22 D 7C 0 ] Calibrating engine version Fri 06/07/2013 03:48:33 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 06/07/2013 03:48:33 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 06/07/2013 03:48:34 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:48:34 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:34 PM : [iNST-ERX ] 02 51 22 0D 7C 1C FC 92 11 2F 00 00 01 1F FF 01 E2 EF 1C FC 92 FF 00 EF 48 Fri 06/07/2013 03:48:34 PM : [Ext-Direct ] 22.0D.7C-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 03:48:34 PM : [22 D 7C 0 ] Using Database Link Table offset 0x1FF8 (reported 0x1FF8) Fri 06/07/2013 03:48:34 PM : [22 D 7C 1 ] Start : Adding device to ISY Fri 06/07/2013 03:48:34 PM : [22 D 7C 1 ] Finish : Adding device to ISY was Successful Fri 06/07/2013 03:48:34 PM : [22 D 7C 1 ] Link 0 : 1FF8 [E2EF1CFC92FF00EF] Saving [E2EF1CFC92FF00EF] Fri 06/07/2013 03:48:34 PM : [22 D 7C 2 ] Start : Adding device to ISY Fri 06/07/2013 03:48:34 PM : [22 D 7C 2 ] Finish : Adding device to ISY was Successful Fri 06/07/2013 03:48:34 PM : [22 D 7C 2 ] Link 1 : 1FF0 [E2011CFC92FF0001] Saving [E2011CFC92FF0001] Fri 06/07/2013 03:48:34 PM : [22 D 7C 3 ] Start : Adding device to ISY Fri 06/07/2013 03:48:34 PM : [22 D 7C 3 ] Finish : Adding device to ISY was Successful Fri 06/07/2013 03:48:35 PM : [22 D 7C 3 ] Link 2 : 1FE8 [E2021CFC92FF0002] Saving [E2021CFC92FF0002] Fri 06/07/2013 03:48:35 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 Fri 06/07/2013 03:48:35 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02) Fri 06/07/2013 03:48:36 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2E 02 (02) Fri 06/07/2013 03:48:36 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:43 PM : CLI-WBug: Connecting to datafeed.weatherbug.com Fri 06/07/2013 03:48:43 PM : CLI-WBug: Successfully Processed WBug Response Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 1] 849000.000000 Weather - Temperature = 84.9 °F Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 2] 850000.000000 Weather - Temperature High = 85 °F Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 4] 920000.000000 Weather - Feels Like = 92 °F Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 6] 680000.000000 Weather - Humidity = 68 % Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 11] 10000.000000 Weather - Wind Speed = 1 mph Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 12] 10000.000000 Weather - Wind Average Speed = 1 mph Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 13] 10000.000000 Weather - Wind Direction = N Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 14] 10000.000000 Weather - Wind Average Directi = N Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 15] 110000.000000 Weather - Gust Speed = 11 mph Fri 06/07/2013 03:48:44 PM : [MOD 2 2 1 16] 10000.000000 Weather - Gust Direction = N Fri 06/07/2013 03:48:45 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 Fri 06/07/2013 03:48:45 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02) Fri 06/07/2013 03:48:45 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2E 02 (02) Fri 06/07/2013 03:48:45 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:54 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 Fri 06/07/2013 03:48:54 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02) Fri 06/07/2013 03:48:55 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2E 02 (02) Fri 06/07/2013 03:48:55 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:48:59 PM : [22 D 7C 0 ] Successfully added device Fri 06/07/2013 03:48:59 PM : [All ] Writing 25 bytes to devices Fri 06/07/2013 03:48:59 PM : [22 D 7C 1 ] Link 0 : 1FF8 [E2EF1CFC92FF00EF] Writing [E2EF1CFC92FF00EF] Fri 06/07/2013 03:48:59 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 02 1F FF 08 E2 EF 1C FC 92 FF 00 EF 40 Fri 06/07/2013 03:48:59 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 02 1F FF 08 E2 EF 1C FC 92 FF 00 EF 40 06 (00) Fri 06/07/2013 03:49:00 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:00 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:00 PM : [MNG-LNK-RSP ] 02 6F 41 A2 EF 22 0D 7C 05 0A 0D 15 Fri 06/07/2013 03:49:00 PM : [PLM ] Group 239 : Writing Responder Link matching [22 D 7C 1 ] Link 0 : 1FF8 [E2EF1CFC92FF00EF] Fri 06/07/2013 03:49:00 PM : [22 D 7C 1 ] Link 1 : 1FF0 [E2011CFC92FF0001] Writing [E2011CFC92FF0001] Fri 06/07/2013 03:49:00 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 02 1F F7 08 E2 01 1C FC 92 FF 00 01 24 Fri 06/07/2013 03:49:00 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 02 1F F7 08 E2 01 1C FC 92 FF 00 01 24 06 (00) Fri 06/07/2013 03:49:02 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:02 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:02 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 22 0D 7C 05 0A 0D 15 Fri 06/07/2013 03:49:02 PM : [PLM ] Group 1 : Writing Responder Link matching [22 D 7C 1 ] Link 1 : 1FF0 [E2011CFC92FF0001] Fri 06/07/2013 03:49:02 PM : [22 D 7C 1 ] Link 2 : 1FE8 [E2021CFC92FF0002] Writing [E2021CFC92FF0002] Fri 06/07/2013 03:49:02 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 02 1F EF 08 E2 02 1C FC 92 FF 00 02 2A Fri 06/07/2013 03:49:02 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 02 1F EF 08 E2 02 1C FC 92 FF 00 02 2A 06 (00) Fri 06/07/2013 03:49:03 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:03 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:03 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 22 0D 7C 05 0A 0D 15 Fri 06/07/2013 03:49:03 PM : [PLM ] Group 2 : Writing Responder Link matching [22 D 7C 1 ] Link 2 : 1FE8 [E2021CFC92FF0002] Fri 06/07/2013 03:49:03 PM : [22 D 7C 1 ] Link 3 : 1FE0 [0000000000000000] Writing [00..............] Fri 06/07/2013 03:49:03 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 02 1F E7 08 00 00 00 00 00 00 00 00 C1 Fri 06/07/2013 03:49:03 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 02 1F E7 08 00 00 00 00 00 00 00 00 C1 06 (00) Fri 06/07/2013 03:49:04 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:04 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:04 PM : [22 D 7C 1 ] Link 4 : 1FD8 : Writing High Water Byte Fri 06/07/2013 03:49:04 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 00 1F DF 01 00 00 00 00 00 00 00 00 D2 Fri 06/07/2013 03:49:04 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 00 1F DF 01 00 00 00 00 00 00 00 00 D2 06 (00) Fri 06/07/2013 03:49:04 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:04 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:05 PM : [iNST-ERX ] 02 51 22 0D 7C 1C FC 92 11 2F 00 00 01 1F DF 01 00 00 00 00 00 00 00 00 D1 Fri 06/07/2013 03:49:05 PM : [Ext-Direct ] 22.0D.7C-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 03:49:05 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 00 1F DF 01 00 00 00 00 00 00 00 00 D2 Fri 06/07/2013 03:49:05 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 00 1F DF 01 00 00 00 00 00 00 00 00 D2 06 (00) Fri 06/07/2013 03:49:05 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:05 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:06 PM : [iNST-ERX ] 02 51 22 0D 7C 1C FC 92 11 2F 00 00 01 1F DF 01 00 00 00 00 00 00 00 00 D1 Fri 06/07/2013 03:49:06 PM : [Ext-Direct ] 22.0D.7C-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 03:49:06 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2F 00 00 02 1F DF 08 00 00 00 00 00 00 00 00 C9 Fri 06/07/2013 03:49:06 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2F 00 00 02 1F DF 08 00 00 00 00 00 00 00 00 C9 06 (00) Fri 06/07/2013 03:49:06 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2F 00 (00) Fri 06/07/2013 03:49:06 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 03:49:06 PM : [22 D 7C 1 ] Memory : Write dbAddr=0x5001 [00] cmd1=0x2E cmd2=0x00 Fri 06/07/2013 03:49:06 PM : [iNST-TX-I2CS] 02 62 22 0D 7C 1F 2E 00 00 08 00 00 00 00 00 00 00 00 00 00 00 CA Fri 06/07/2013 03:49:06 PM : [iNST-ACK ] 02 62 22.0D.7C 1F 2E 00 00 08 00 00 00 00 00 00 00 00 00 00 00 CA 06 (00) Fri 06/07/2013 03:49:07 PM : [iNST-SRX ] 02 50 22.0D.7C 1C.FC.92 2B 2E 00 (00) Fri 06/07/2013 03:49:07 PM : [std-Direct Ack] 22.0D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 The address of the Stat is 22.0D.7C. Did that tell you guys anything? Thanks! Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 I do not see anything wrong in the trace. The link records created in the tstat match my 2441ZTH. The only difference I see is I have v.0B and this tstat has v.0D firmware. Link to comment
jmed999 Posted June 7, 2013 Author Share Posted June 7, 2013 Yeah something is up here. Everything seems right except for the info inst showing up on the admin console. I think something isn't jiving with between these newer version wireless stats and the ISY. Any other ideas here besides returning them an assuming they just wont work with the ISY? Link to comment
LeeG Posted June 7, 2013 Share Posted June 7, 2013 The tstat should have been Off when adding to the ISY. My error in not including that in the instructions. What mode is the tstat operating in, Heat, Cool? I've had mine on batteries only for all my tests and the trace messages I’ve posted. Currently the tstat is set for Heat mode. Although not instantaneously when I press the Up/Down buttons to move the set point I do eventually get a message from the tstat that the set point has been changed. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.