andyf0 Posted May 25, 2012 Posted May 25, 2012 I've tried linking this using Wiki method and New Insteon Device. Both times I only get one node. What is the correct method to link it? Log below using Wiki method: Fri 05/25/2012 01:17:02 PM : [LNK-BGN ] 02 64 01 00 06 Fri 05/25/2012 01:17:24 PM : [LNK-STAT ] 02 53 M(01) gid=00 1D.6E.F6 050B 0A Fri 05/25/2012 01:17:24 PM : Linked: Linked 1D.6E.F6.00 type=05.0B.0A Fri 05/25/2012 01:17:24 PM : [iNST-TX-I1 ] 02 62 1D 6E F6 0F 0D 00 Fri 05/25/2012 01:17:24 PM : [iNST-ACK ] 02 62 1D.6E.F6 0F 0D 00 06 (00) Fri 05/25/2012 01:17:24 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 0D 02 (02) Fri 05/25/2012 01:17:24 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:24 PM : [1D 6E F6 0 ] Calibrating engine version Fri 05/25/2012 01:17:24 PM : [1D 6E F6 1 ] Start : Adding device to ISY Fri 05/25/2012 01:17:24 PM : [1D 6E F6 1 ] Finish : Adding device to ISY was Successful Fri 05/25/2012 01:17:24 PM : [All ] Writing 0 bytes to devices Fri 05/25/2012 01:17:24 PM : [LNK-BGN ] 02 64 01 00 06 Fri 05/25/2012 01:17:38 PM : ---- Initializing the linked devices ---- Fri 05/25/2012 01:17:38 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Fri 05/25/2012 01:17:38 PM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1D 6E F6 05 0B 0A 15 Fri 05/25/2012 01:17:38 PM : [1D 6E F6 1 ] Link 0 : 0FF8 [A20018CF62464E41] Saving [A20018CF62464E41] Fri 05/25/2012 01:17:38 PM : [1D 6E F6 1 ] Link 1 : 0FF0 [E20118CF62FF1F01] Saving [E20118CF62FF1F01] Fri 05/25/2012 01:17:39 PM : ---- All Linked Devices are now initialized ---- Fri 05/25/2012 01:17:39 PM : [iNST-TX-I1 ] 02 62 1D 6E F6 0F 6A 00 Fri 05/25/2012 01:17:39 PM : [iNST-ACK ] 02 62 1D.6E.F6 0F 6A 00 06 (00) Fri 05/25/2012 01:17:39 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 6A A3 (A3) Fri 05/25/2012 01:17:39 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:39 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 6B 02 00 00 00 00 00 00 00 00 00 00 00 00 00 93 Fri 05/25/2012 01:17:39 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 6B 02 00 00 00 00 00 00 00 00 00 00 00 00 00 93 06 (02) Fri 05/25/2012 01:17:40 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 6B 00 (00) Fri 05/25/2012 01:17:40 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:40 PM : [iNST-TX-I1 ] 02 62 1D 6E F6 0F 6A 20 Fri 05/25/2012 01:17:40 PM : [iNST-ACK ] 02 62 1D.6E.F6 0F 6A 20 06 (20) Fri 05/25/2012 01:17:40 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 6A 00 (00) Fri 05/25/2012 01:17:40 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:40 PM : [iNST-TX-I1 ] 02 62 1D 6E F6 0F 6A 60 Fri 05/25/2012 01:17:40 PM : [iNST-ACK ] 02 62 1D.6E.F6 0F 6A 60 06 (60) Fri 05/25/2012 01:17:41 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 6A 34 (34) Fri 05/25/2012 01:17:41 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:41 PM : ---- Initializing the linked devices ---- Fri 05/25/2012 01:17:41 PM : ---- All Linked Devices are now initialized ---- Fri 05/25/2012 01:17:41 PM : [ 1D 6E F6 1] ST 163 Fri 05/25/2012 01:17:41 PM : [ 1D 6E F6 1] CLIMD 0 Fri 05/25/2012 01:17:41 PM : [ 1D 6E F6 1] CLIHUM 52 Fri 05/25/2012 01:17:41 PM : [All ] Writing 16 bytes to devices Fri 05/25/2012 01:17:41 PM : [1D 6E F6 1 ] Link 0 : 0FF8 [A20018CF62464E41] Writing [A20018CF62464E41] Fri 05/25/2012 01:17:41 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 02 0F FF 08 A2 00 18 CF 62 46 4E 41 F9 Fri 05/25/2012 01:17:41 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 02 0F FF 08 A2 00 18 CF 62 46 4E 41 F9 06 (00) Fri 05/25/2012 01:17:42 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 2F 00 (00) Fri 05/25/2012 01:17:42 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:42 PM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1D 6E F6 05 0B 0A 15 Fri 05/25/2012 01:17:42 PM : [PLM ] Group 0 : Writing Controller Link matching [1D 6E F6 1 ] Link 0 : 0FF8 [A20018CF62464E41] Fri 05/25/2012 01:17:42 PM : [1D 6E F6 1 ] Link 1 : 0FF0 [E20118CF62FF1F01] Writing [E20118CF62FF1F01] Fri 05/25/2012 01:17:42 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 02 0F F7 08 E2 01 18 CF 62 FF 1F 01 76 Fri 05/25/2012 01:17:42 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 02 0F F7 08 E2 01 18 CF 62 FF 1F 01 76 06 (00) Fri 05/25/2012 01:17:43 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 A7 2F FD (FD) Fri 05/25/2012 01:17:43 PM : [standard-Direct Nack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:43 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 1D 6E F6 05 0B 0A 15 Fri 05/25/2012 01:17:43 PM : [PLM ] Group 1 : Writing Responder Link matching [1D 6E F6 1 ] Link 1 : 0FF0 [E20118CF62FF1F01] Fri 05/25/2012 01:17:43 PM : [1D 6E F6 1 ] Link 2 : 0FE8 [0000000000000000] Writing [00..............] Fri 05/25/2012 01:17:43 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Fri 05/25/2012 01:17:43 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Fri 05/25/2012 01:17:44 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 2F 00 (00) Fri 05/25/2012 01:17:44 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:44 PM : [1D 6E F6 1 ] Link 3 : 0FE0 : Writing High Water Byte Fri 05/25/2012 01:17:44 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Fri 05/25/2012 01:17:44 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Fri 05/25/2012 01:17:44 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 2F 00 (00) Fri 05/25/2012 01:17:44 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:45 PM : [iNST-ERX ] 02 51 1D 6E F6 18 CF 62 11 2F 00 00 01 0F E7 01 00 00 00 00 00 00 00 00 D9 Fri 05/25/2012 01:17:45 PM : [Extended-Direct][1D.6E.F6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 05/25/2012 01:17:45 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Fri 05/25/2012 01:17:45 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Fri 05/25/2012 01:17:45 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 2F 00 (00) Fri 05/25/2012 01:17:45 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:46 PM : [iNST-ERX ] 02 51 1D 6E F6 18 CF 62 11 2F 00 00 01 0F E7 01 00 00 00 00 00 00 00 00 D9 Fri 05/25/2012 01:17:46 PM : [Extended-Direct][1D.6E.F6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 05/25/2012 01:17:46 PM : [iNST-TX-I2CS] 02 62 1D 6E F6 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Fri 05/25/2012 01:17:46 PM : [iNST-ACK ] 02 62 1D.6E.F6 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Fri 05/25/2012 01:17:46 PM : [iNST-SRX ] 02 50 1D.6E.F6 18.CF.62 27 2F 00 (00) Fri 05/25/2012 01:17:46 PM : [standard-Direct Ack][1D.6E.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 05/25/2012 01:17:46 PM : [All ] Writing 0 bytes to devices The Main node seems to function correctly with scenes etc, but I do have some programs I like to execute on heat or cool control.
LeeG Posted May 25, 2012 Posted May 25, 2012 This is an I2CS device. Is the ISY at 3.2.6? Does Help | About show 3.2.6 for Firmware and UI? Was Device Type set to Auto Discover when using New INSTEON Device? Was the tstat Off?
andyf0 Posted May 25, 2012 Author Posted May 25, 2012 This is an I2CS device. Is the ISY at 3.2.6? Does Help | About show 3.2.6 for Firmware and UI? Was Device Type set to Auto Discover when using New INSTEON Device? Was the tstat Off? Yes, I'm at 3.2.6, both entries show 3.2.6. When using New Insteon Device I selected 2441TH (TempLinc) The Tstat was OFF. Also, either it's not a very chatty thermostat or it's not sending any temperature or humidity messages. When I do a Query I can see humidity change but it should have sent the new humidity automatically.
LeeG Posted May 25, 2012 Posted May 25, 2012 Try New INSTEON Device with Auto Discover. I think the lack of a v.xx number when selecting a Device Type may make it think this is a V1 adaptor (not sure about that). Something Michel posted a few days ago makes me think that but I could not find the post to be sure.
andyf0 Posted May 25, 2012 Author Posted May 25, 2012 I did that and no change. It correctly identified the device as 2441TH v.0A. But still only one node. I've submitted a ticket to UDI but if anyone has any other ideas ...
RichTJ99 Posted May 25, 2012 Posted May 25, 2012 I also have a 2441TH & i have yet to pull it out of hte box to play with it. I will follow this thread with interest!
andyf0 Posted May 25, 2012 Author Posted May 25, 2012 It's going to have to go back. It does only have a single node, but the ISY handles it differently than the Venstar. You can check status of Cool On and Heat On and all the different modes on the single node. But it's going back because it doesn't send temperature and humidity change messages automatically. It's like the V1 Venstar where you had to poll the thermostat at regular intervals for ISY to know the current temperature and humidity. It's a shame because the display is gorgeous, the backlight is a nice blue and is very sharp.
Michel Kohanim Posted May 26, 2012 Posted May 26, 2012 Hello Andy, Don't send it back yet. We just got a non-beta version that we are testing now. If you have 30 day money back guarantee, then it would be best to let us see what's going on. With kind regards, Michel
andyf0 Posted May 26, 2012 Author Posted May 26, 2012 Hello Andy, Don't send it back yet. We just got a non-beta version that we are testing now. If you have 30 day money back guarantee, then it would be best to let us see what's going on. With kind regards, Michel Thanks Michel, I'll hold on to it for a while while you check it out.
andyf0 Posted May 26, 2012 Author Posted May 26, 2012 I don't think there's much the ISY can do. Most of the issues seem to be with the thermostat. Here's what I've found: The 2441TH Insteon Thermostat ---------------------------- 1. No messages are sent from the thermostat without a Query: Temperature, Humidity, Locally changed setpoints, Heat On/Off, Cool On/Off, Fan On/Off when changed locally, Operating Mode. 2. The thermostat display doesn't match the data received by ISY. Doing a Query ISY shows 80, thermostat shows 79. Humidity shows 52%, ISY shows 53%. The ISY99 v3.2.6 --------------- 1. The Fan Mode in a scene is ignored. If set to Auto or On and sending a scene On, does not update the fan mode. The ISY UI for the thermostat always shows Fan Mode as On. The Fan Mode can be changed with a direct command. This is mostly cosmetic except you can't set the Fan Mode from a scene. The clock does seem to keep time though.
LeeG Posted May 26, 2012 Posted May 26, 2012 andyf0 If you have the capability to add link records outside of the ISY (not a good practice) add Controller link records for Group 1,2,3,4 (ISY may have added a Controller link for Group 1). According to the 2441TH User Guide these additional Groups are used for sending indications for heat/cool/humidify/dehumidify, etc. It will take additional nodes the other tstats have for these to be functional under the ISY but Insteon messages should flow once the tstat knows what device to send the messages to.
andyf0 Posted May 26, 2012 Author Posted May 26, 2012 andyf0 If you have the capability to add link records outside of the ISY (not a good practice) add Controller link records for Group 1,2,3,4 (ISY may have added a Controller link for Group 1). According to the 2441TH User Guide these additional Groups are used for sending indications for heat/cool/humidify/dehumidify, etc. It will take additional nodes the other tstats have for these to be functional under the ISY but Insteon messages should flow once the tstat knows what device to send the messages to. I don't have that capability. But even without those groups I should still get temperature & humidity updates right? The way I understand it the Groups are just to send ON & OFF to responders. Group 1 is for Cool Group 2 is for Heat Group 3 for Low Humid Group 4 for High Humid This is what the ISY reports as device links in the thermostat 0FF8 : A2 00 18.CF.62 46 4E 41 0FF0 : E2 01 18.CF.62 FF 1F 01 0FE8 : A2 32 18.CF.62 46 52 40 0FE0 : 00 00 00.00.00 00 00 00
LeeG Posted May 26, 2012 Posted May 26, 2012 Thanks for the link record display. The User Guide does indicate updates are part of the 2441TH tstat. "Reports changes in thermostat modes, temperature, humidity, setpoints and fan to compatible automation controllers or software" The User Guide (being that it is a User guide) has little about what it takes for the tstat to send those updates. How does it know the device address of the PLM to send the updates to. It does say Group EF is used for broadcasting all changes. Don't know if that is required to get async change messages. The 2441V says the last linked device gets the status updates. The 2441TH makes no such reference. Also think there is a command to Enable/Disable those broadcast updates, although that comes from a 5 year old command reference which may have nothing to do with the 2441TH. I think we have to wait for UDI to evaluate the non-beta 2441TH. My guess is the function is there on the production versions.
andyf0 Posted May 26, 2012 Author Posted May 26, 2012 Thanks Lee. At least I have hope that maybe the ISY can make this work. Now to try and figure out how to get into the Temp/Humid calibration mode. I've tried holding down PGM and tapping the Sensor_Time button but it just keeps going into program mode ......
RichTJ99 Posted May 26, 2012 Posted May 26, 2012 I am confused, I just bought it from smarthome, do I have a beta product?
LeeG Posted May 26, 2012 Posted May 26, 2012 RichTJ99 You have a production version. UDI had a beta device when they implemented support for the 2441TH. They now have a production version which they are evaluating. Not uncommon for a beta device to have some differences.
Nuttycomputer Posted May 27, 2012 Posted May 27, 2012 Glad someone posted this. I just changed out my Venstar for this and sent it back. The future wireless thermostats, 7 day programmable, cheaper pricetag, and the venstar's onboard module continually stopping on me made this one dream come true. I was about to post in the Mobilinc forums since that's how I primarily connect but now I'm assuming the problems I'm seeing on the mobilinc (inability to adjust fan, having to continually hit refresh) are probably the same issues you are having. In my ISY I also only have the single node and have to do queries to get temperatures to update.
andyf0 Posted May 27, 2012 Author Posted May 27, 2012 Another problem. I was playing with the thermostat by just hooking it up to power. Yesterday, given the hope that UDI could resolve these problems, I hooked it up to my HVAC. It's temperature control has a problem I think. In Houston it's around 93 degrees outside. The inside temperature (according to the Tstat) got stuck at 81.5 degrees and would not increase to trip the AC until I changed the set point down 1 degree. Then the Tstat reported 84 degrees and turned on the AC. The AC ran for a long time and the house got cool but the Tstat still reported 84 degrees until I changed the setpoint up 1 degree. Then it reported 84.5 degrees, obviously wrong. I disconnected it and put the Venstar back, much better temperature reporting. I'm sending it back, it's obviously a mistake to buy new products from SmartHome. I'll reconsider in a year when the firmware version is a little higher.
Tom Posted May 29, 2012 Posted May 29, 2012 I am also having some trouble with a recently purchased Venstar themostat. Mine is a 2491T7E. Purchased from Smarthome on 5/22/2012. After adding it to the ISY99 I see only 1 device. The current temperature etc. does not update without polling the thermostat. I am using it with HomeSeer with the ISY plugin. The firmware in my ISY99 is 3.2.6. Will UDI be able to release a newer firmware to support this Tstat better or will I need to setup polling from HomeSeer? Thanks Tom
Michel Kohanim Posted May 29, 2012 Posted May 29, 2012 Hi Tom, Venstar 2491T7E should be fully supported. TempLinc, on the other hand, we are having some problems with. Please do the following: 1. Remove the thermostat from your ISY 2. Do a factory reset on it 3. Turn it off 4. Use Link Management | Start Linking and then press and hold the set button on the thermostat If this does not work, then please provide the firmware version of the thermostat (from the Admin Console). With kind regards, Michel
Nuttycomputer Posted May 30, 2012 Posted May 30, 2012 Hey Michel I believe this may be related to the general controller group problems as I'm sure your working to get this device ironed out. One thing I noticed though is while the Thermostat Mode, States, Temperature, Set Points, Humidity can be resynced with the ISY via a Query it appears the Fan State never updates in the ISY regardless. This mimics the experience I'm seeing on the Mobilinc as well where it doesn't even give you option of controlling fan. Now interestingly enough this appears to only break when controlling the fan status locally. If I change the fan status in the ISY it is controllable again from the Mobilinc and all devices / programs respond correctly until the next time I change fan state directly with the local button. Trying to get a feel for this but is it because according to documentation the FAN doesn't have a controller group at all anyway and it's status should update via that Broadcast on Any Change group?
Michel Kohanim Posted May 31, 2012 Posted May 31, 2012 Hello NuttyComputer, Are you referring to 2441TH (which is problematic) or are you referring to 2491T7E which should work? In the latter, you should not have to query. For the former, we are still trying to get to the bottom of things. With kind regards, Michel
Nuttycomputer Posted May 31, 2012 Posted May 31, 2012 Referring to the 2441TH - Good to know you are still looking into it.. I'm available for any testing you might need
Michel Kohanim Posted June 1, 2012 Posted June 1, 2012 Hi Nuttycomputer, Thanks so very much for the offer and we should have a beta shortly. With kind regards, Michel
Recommended Posts