mdyod Posted August 31, 2012 Posted August 31, 2012 I cant get my new Venstar Thermostat - INSTEON Integrated Remote Control Thermostat 7-Day Programmable Item# 2491T7E to add to my isy99 devices. I'm not sure if I'm doing things right since the only instructions for linking is on the quick start guide and it only talks about linking to a scene controller button... Anyway, Here's what I'm doing.... I press the set button on the thermostat until it's LED blinks then I go to the admin console and try to link by adding new Insteon device ( I enter the device address, choose {05.0E } (2491T) "All-In-One Thermostat" from the drop down menu and click "remove existing links" ) Then i get the "unable to get high watermark error " and indication that linking failed. I have an access point about 5 feet from the thermostat and it is about 2 feet away from My ISy99 Thanks in advance for you help help....
LeeG Posted August 31, 2012 Posted August 31, 2012 Two ways to add a device. Do not press the device Set button as that put it into linking mode which prevented the ISY from communicating with it. Select New INSTEON Device, enter the Insteon address, Name of your choice, leaving Device Type set to Auto Discover. Click Ok. Or click Start Linking which puts the ISY PLM into linking mode. Press the Set button on the device for 3-5 seconds for the device to identify itself to the ISY PLM. Click Finish. The ISY and the Admin Console need to be at 3.2.6.
mdyod Posted September 5, 2012 Author Posted September 5, 2012 ok I got ISY and admin console both to 3.2.6 BUT I still cant get thermostat to link using either method that you described previously... Still not showing up in device tree... What is the deal?
LeeG Posted September 5, 2012 Posted September 5, 2012 Run Tools | Diagnostics | Event Viewer with Level 3 selected. Use the New INSTEON Device option with Auto Discover. Add the thermostat and post the trace. Be sure there is a Dual Band device close to the thermostat for RF communication and the thermostat is Off.
mdyod Posted September 5, 2012 Author Posted September 5, 2012 Run Tools | Diagnostics | Event Viewer with Level 3 selected. Use the New INSTEON Device option with Auto Discover. Add the thermostat and post the trace. Be sure there is a Dual Band device close to the thermostat for RF communication and the thermostat is Off. Tue 09/04/2012 09:53:47 PM : ---- Initializing the linked devices ---- Tue 09/04/2012 09:53:47 PM : ---- All Linked Devices are now initialized ---- Tue 09/04/2012 09:53:47 PM : ---- Add remaining devices ---- Tue 09/04/2012 09:53:47 PM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Tue 09/04/2012 09:53:47 PM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Tue 09/04/2012 09:53:56 PM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Tue 09/04/2012 09:53:56 PM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Tue 09/04/2012 09:54:05 PM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Tue 09/04/2012 09:54:05 PM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Tue 09/04/2012 09:54:09 PM : ---- All Remaining Device Added ---- Tue 09/04/2012 09:54:09 PM : [All ] Writing 0 bytes to devices
LeeG Posted September 5, 2012 Posted September 5, 2012 None of the commands sent to the thermostat get a response. Could be out of range of a Dual Band device. Try a factory reset of the thermostat and move an Access Point closer to the thermostat. Take care not to lose phase coupling in the process. Also double check the Insteon address. Some times a B and 8 can look the same.
Michel Kohanim Posted September 5, 2012 Posted September 5, 2012 And one more suggestion: if you have baby monitors, unplug them! With kind regards, Michel
mdyod Posted November 24, 2012 Author Posted November 24, 2012 .....Try a factory reset of the thermostat and move an Access Point closer to the thermostat. Take care not to lose phase coupling in the process. Also double check the Insteon address. Some times a B and 8 can look the same. Hello all - sorry to be so long getting back to this but I need to get this figured out... I did a factory reset of the thermostat and that didn't help... the address I'm using is correct everything is within five feet of each other and there are no baby monitors in the house... *When I attempt to link using the "Add device" Method - the status window appears for a split second and nothing happens - no new device shows up in my device tree... *When I attempt to link using the "Start Linking" Method - the PLM "buzzes" after i press the set button on the thermostat 3-5 seconds then goes quite and the green LED stops blinking (i think it goes out of linking mode) When I choose "Remove Existing Links " and click "Finish" from the console the status window appears for a split second and nothing happens - no new device shows up in my device tree... Thanks Again for you help D
LeeG Posted November 24, 2012 Posted November 24, 2012 When New INSTEON Device appears, then disappears immediately after clicking Ok the Insteon address is already known to the ISY. Click on My Lighting Click the Address column heading which will sort the display by Insteon Address. Check that thermostat address is not already in the list. If not in the list run Tools | Diagnostics | Event Viewer at Level 3. Use New INSTEON Address to add the thermostat. Be sure thermostat is Off before attempting device add. Post the event trace.
mdyod Posted November 24, 2012 Author Posted November 24, 2012 Hey LeeG thanks for your response, Its not in my list by address here's the trace.... Sat 11/24/2012 09:44:42 AM : ---- Initializing the linked devices ---- Sat 11/24/2012 09:44:42 AM : ---- All Linked Devices are now initialized ---- Sat 11/24/2012 09:44:42 AM : ---- Add remaining devices ---- Sat 11/24/2012 09:44:42 AM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Sat 11/24/2012 09:44:42 AM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Sat 11/24/2012 09:44:51 AM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Sat 11/24/2012 09:44:51 AM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [iNST-TX-I1 ] 02 62 00 00 16 CF 13 00 Sat 11/24/2012 09:45:00 AM : [iNST-TX-I1 ] 02 62 00 00 17 CF 13 00 Sat 11/24/2012 09:45:00 AM : [iNST-ACK ] 02 62 00.00.16 CF 13 00 06 LTOFFRR(00) Sat 11/24/2012 09:45:00 AM : [standard Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:00 9(0) Sat 11/24/2012 09:45:00 AM : [ Time] 09:45:01 9(0) Sat 11/24/2012 09:45:00 AM : [iNST-ACK ] 02 62 00.00.17 CF 13 00 06 LTOFFRR(00) Sat 11/24/2012 09:45:00 AM : [standard Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sat 11/24/2012 09:45:00 AM : [iNST-TX-I1 ] 02 62 14 B9 7F 0F 0D 00 Sat 11/24/2012 09:45:01 AM : [iNST-ACK ] 02 62 14.B9.7F 0F 0D 00 06 (00) Sat 11/24/2012 09:45:05 AM : ---- All Remaining Device Added ---- Sat 11/24/2012 09:45:05 AM : [All ] Writing 0 bytes to devices
LeeG Posted November 24, 2012 Posted November 24, 2012 Thanks for the additional event trace. The thermostat continues not to respond to commands. All commands sent to the thermostat fail to get any response. Do you have any RF devices such as a RemoteLinc or RemoteLinc2 that can be used near the thermostat location to see if RF communication from that location is seen by the ISY and PLM. There is nothing the ISY can do with a device that will not respond to any command. Is the thermostat controlling the heating system correctly? I'm wondering if the thermostat is functional.
mdyod Posted November 24, 2012 Author Posted November 24, 2012 yes the thermostat is controlling the hvac just fine - and following schedules just as programed
mdyod Posted November 24, 2012 Author Posted November 24, 2012 I will post results from FR testing as soon as i get a RL up and running
mdyod Posted November 27, 2012 Author Posted November 27, 2012 Interesting, I just attempted to link a remotelinc -and it shows up in my tree but i cant communicate with it... there are "!" marks beside each button... I have the RL within a foot of an AP
LeeG Posted November 27, 2012 Posted November 27, 2012 If the RemoteLinc was in linking mode by pressing the Dim/Bright buttons (RemoteLinc LED blinking) there is some RF or coupling issue. Perhaps the Access Point is not working. Try the 4 tap Set button test with that Access Point and verify it is in RF range and on opposite 120v leg to the other Access Point.
biredale Posted November 27, 2012 Posted November 27, 2012 I had a problem with a Venstar thermostat not linking even though the thermostat was functioning normally other than that. It would never enter the linking mode. I figured it was defective and got it replaced with a new one. The new one was able to link and worked. Thanks! Brian
mdyod Posted November 28, 2012 Author Posted November 28, 2012 ok I "4 tapped" the button on one RL and it began to chirp - the other AP's LED blinked red in conjunction with the first....
mdyod Posted November 28, 2012 Author Posted November 28, 2012 ok - i moved th APs around and they are on different phases and the Remotelinc seems to be working fine now- BUT the Thermostat STILL wont show up in the device tree - THANKS D
LeeG Posted November 28, 2012 Posted November 28, 2012 Does the RemoteLlinc now work at the thermostat location?
Xathros Posted November 28, 2012 Posted November 28, 2012 To confuse matters a bit more, as I recall, mdyod has a 3 phase installation. -Xathros
LeeG Posted November 28, 2012 Posted November 28, 2012 Sorry, I missed the part about the RemoteLinc working from the thermostat location now that the Access Points are on opposite phases. If the RemoteLinc works from the thermostat location and the thermostat does not that would suggest the thermostat is not working. Was another attempt to add the thermostat done after the Access Points were moved and if so was the add traced by the Event Viewer? If this is 3 phase it does raise additional questions. Last time I looked Smarthome would not provide support for a 3 phase installation because of all the variables associated with the different relationships of the Sine Wave on each phase. However, with the RemoteLinc working when used alongside the thermostat and the thermostat not working it does suggest an issue with the thermostat. It does go back to what commands are not working now with the thermostat. The RemoteLinc is probably still using the older link method. The new thermostats are using I2CS which means there could be a difference in that Standard commands work with the RemoteLinc and Extended commands do not work with the thermostat. In the previous traces no command worked so there was no question about Standard versus Extended. That is why it is important to know how it is not working now with the Access Points moved.
mdyod Posted November 28, 2012 Author Posted November 28, 2012 Does the RemoteLlinc now work at the thermostat location? I will check for sure when i get home for tonight
mdyod Posted November 28, 2012 Author Posted November 28, 2012 To confuse matters a bit more, as I recall, mydod has a 3 phase installation. -Xathros Thanks for remembering - But my 3 phase istall is at my office The thermostat problem is at my home (2phase) YOU GUYS ARE AWESOME!!!
mdyod Posted November 28, 2012 Author Posted November 28, 2012 ....Was another attempt to add the thermostat done after the Access Points were moved and if so was the add traced by the Event Viewer? .... Yes - I will Post the trace tonight THANKS!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.