andyf0

I agree something is wrong with backup. I am using an iMac with Mountain Lion and was unable to browse to my backup folder after I selected Backup ISY. When I selected the backup folder I just got a busy animated icon. This didn't happen in 3.3.1. The other change I made is to access Admin Console using method (d) since my original method was to access the ISY directly from my home page but this caused the new version of Safari to crash. FYI, Java 7. Clearing the cache is now done through System Preferences

Teken, thanks. I suppose you could de-solder the sensor and wire it outside the thermostat but it would make such a good looking thermostat kinda ugly. How does Venstar not run into this problem? Is it just separation distance from the triacs?

I see the 2441TH in the New Device pull down menu but not the 2441ZTH. Do you just use the 2441TH device when adding the 2441ZTH? I'm still interested in these even though I sent my original one back. Does anyone know if they've resolved the triacs heating up the temperature sensors yet? Also, the remote wireless version wouldn't have that problem since it's not actually controlling an HVAC unit.

Screenshot sent. I'm using a MAC so am limited to the latest available JVM (1.6.0_33-bo3-424 both 32 and 64 bit. I am configured for SSL 3.0 both client and server. Thanks. -Xathros I received a 1.7 update on my iMac. Check software updates. If not, go to java.com and click on the version check. It will recommend the 1.7 update. I'm running Mountain Lion.

I loved the look of it, however it didn't work very well. I didn't believe the temperature it reported, the AC was either on for hours or would never come on. Also, there's still no ISY support for the different groups. I sent it back. I did just read the review about the triac placement, interesting .. When the bugs are fixed I will buy one again, also the matching wireless thermostat.

Indeed. Up until about 2 weeks ago the temperature was fairly stable in the house anyway so it went unnoticed. I have mixed feelings. I think the Venstar looks okay but my wife seems to notice the difference and enjoys the look of the 2441TH more. My biggest concern is the functionality I was looking forward to. Our basement area can be +/- up to 10 degrees from where are thermostat is depending on whether the door was left closed, open, how long the fan has been running etc. I was particularly looking forward to putting a wireless slave thermostat down there so we could get better control while the area is in use. Same with our Master Bedroom for night time sleeping. I'm uncertain how else I can achieve that sort of functionality without actually spending the money to put in a full 2 zone system. I've achieved a little of what you want to do. I bought a second Venstar thermostat to use as a slave in the bedroom. It's powered with a 24v Xformer. When I go to sleep I press a button on a RL2 which turns off the thermostat upstairs and sets the slave thermostat to auto with the setpoints I want. When the slave calls for cool I turn on the main thermostat, when it calls off I turn the main off. This way, with the bedroom door closed I control the HVAC based on the temperature in the bedroom only. It's a lot more complicated with checks for control failures etc but basics are not that difficult.

I too have noticed the same with the humidity sensor but since I don't use it I've not considered it an issue. The circular disk is installed in my setup. I understand this is required for fire safety reasons. The thermostat itself though has what I assume are vents all the way around to allow the surrounding air to reach the sensor. Right now though I've replaced it once and will probably go ahead and go back to the Non-Integrated Venstar version. For reference both the one I returned and the replacement are v1.0 I'm so glad someone else is noticing the poor temperature readings. I guess it just got hotter, quicker in Houston that I was able to observe it sooner. My Venstars are working perfectly but they look nowhere as good as the Smarthome thermostat. I'm hoping all this will get fixed one day, looking forward to trying again.

If the MS keeps turning on then that is likely the cause of the dusk/dawn problem. The MS doesn't send a dusk/dawn change while the sensor is on.

When you say "new Smarthome one.." are you referring to the 2441TH? I've got to make a decision within the next few days as to what I'm going to do. I spoke to the Universal folks today. The Venstar 2391T7E is an I2CS device, From what I understand, Michel is working on a firmware revision. If I am going to return anything, I have to do it by the 14th. I'm debating whether to return just the tstat or the tstat and the ISY. A functional ISY with no compatible tstat doesnt do me any good. My preference would be to keep the ISY and get a tstat that is fully compatible, but I am runnning out of time. Did you have any issues with the Smarthome replacement? What controller are you using? I had the "Smarthome" one (2441TH) and sent it back. Michel seems to be having problems getting it working properly with the ISY and suggests that a thermostat firmware update may be required. I also think the firmware has some other problems reporting and acting on temperature changes, although I haven't seen any other posts regarding this. I will wait until this thermostat is much more mature before purchasing it again. It does look "really" nice though.

Do you have any experience with the other Thermostat offerings like the Ventrstar? I am currently using 2 Venstar thermostats. One as a master and another as a slave controlled using ISY programs. They do work better at temperature monitoring and control but don't look as nice as the Smarthome thermostat. They've been available for a while and consequently their firmware is a lot more robust. If you peruse the ISY logs you do see some bogus messages but they are corrected within 2 secs and do not affect operation. From an operational standpoint they are very good, just not that cosmetically appealing. I'm hoping someone develops some network resources to control a NEST thermostat. That would be awesome.

I'm sending mine back. Even without linking it to ISY and using it as a normal thermostat it doesn't work very well. It won't update it's temperature and turn on cooling unless I adjust the set point locally, then the temperature jumps 2 degrees. When the A/C is on it won't turn it off or show the lowering temperatures until I hit a set point button.

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.

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

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

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.

Thanks Michel, I'll hold on to it for a while while you check it out.

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.

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

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.

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.

I have to ask. Do you have SEP 1.1 certification yet? Can I read my Smart Meter?

You actually have to hold the buttons and air gap longer than you think you would. Hold them in until the MAIN and load turns on.

I have been thinking of getting the 994 also and the exact same questions have come to mind. I want to use the Zigbee module to monitor my Smart Meter using SEP. One more question to add: How would one go about swapping out the old PLM to the new PLM.

The Motion Sensors have to change state before they send a message to the ISY. Until then the ISY doesn't know what state they're in. If they were off they need to detect motion to send an ON. If they were on then they need to timeout before they send an OFF, assuming you're using them in ON/OFF mode. The same same goes for Dusk/Dawn with the exception they won't send Dusk/Dawn messages while they are ON.

It should also be noted that the Dusk/Dawn message is not sent while the motion sensor is ON. So if you had a timeout set for 1 hour, sticking it in a draw for 20 mins would not cause Dusk/Dawn to be set.