andrewm Posted January 7, 2009 Share Posted January 7, 2009 I've just installed a Venstar Thermostat with V.28 firmware being controlled by ISY 99 v2.6.8. I don't know if the issues I'm seeing are normal are not (we could do with a Wiki topic for this whacko device!) so I'd appreciate some feedback Note that I use the thermostat purely for heating. Auto changeover is disabled in the thermostat. Firstly I learnt the hard way that it doesn't appear that you can change the setpoint of the Thermostat in Program mode. I can live with that, but it means I have to completely program the operaton with the ISY. So I manually put the thermostat in heat mode and used a test program triggered by a RemoteLinc to change the setpoint either to 59° or 62°. Eg: If Control 'Bedroom 1 - Remote2: KeyD' is switched Off Then Set 'Living Room - Thermostat' Mode Heat Set 'Living Room - Thermostat' 59° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') When I pressed the remote key to trigger lowering the setpoint the Thermostat operated as expected - the setpoint changed after a few seconds. When I pressed the button to trigger increasing the setpoint, the thermostat's display changed as though the thermostat was in auto mode (ie both cooling and heating setpoints were displayed - 31° & 0° respectively - despite me not having that mode enabled). Then the display changes to just show a heat setpoint of 0°, then finally the display changes again to show a heat setpoint of 62°. So that's my first issue - why the intermediate steps with suspect values? The second issue is that occasionally when doing this latter operation, the fan blower turns on very briefly, even though the new setpoint is below the current temperature. This is obviously unnecessary and undesirable. The third issue is that if you notice above I send the command to put the Thermostat into heat mode, even though that should already be the case. If I didn't do that then the operation was unreliable - eg the thermostat display sticks on the 0° setpoint display! This is bizarre - is it normal, or could I have a faulty unit FWIW here's the ISY log during some of the above operations: (ENQUIRY) 2009/01/06 23:47:04 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:04 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 88 (88) 2009/01/06 23:47:04 : [ E 6A 46 1] ST 136 2009/01/06 23:47:04 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:05 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 7C (7C) 2009/01/06 23:47:05 : [ E 6A 46 1] CLISP 124 2009/01/06 23:47:05 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:05 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:05 : [ E 6A 46 1] CLIHUM 9 2009/01/06 23:47:05 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:06 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:47:06 : [ E 6A 46 1] CLIMD 1 (Press Remote key to trigger setting setpoint at 59°) 2009/01/06 23:47:31 : [iNST-SRX ] 02 50 0A.15.36 00.00.04 C7 13 00 LTOFFRR(00) 2009/01/06 23:47:31 : [ A 15 36 4] DOF 0 2009/01/06 23:47:32 : [iNST-SRX ] 02 50 0A.15.36 0C.A5.7A 41 13 04 LTOFFRR(04) 2009/01/06 23:47:32 : [ A 15 36 4] ST 0 2009/01/06 23:47:32 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 04 06 (04) 2009/01/06 23:47:33 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 04 (04) 2009/01/06 23:47:33 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:34 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 00 (00) 2009/01/06 23:47:34 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:34 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 7C (7C) 2009/01/06 23:47:34 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:35 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:35 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:35 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:47:35 : [iNST-ACK ] 02 62 0E.6A.46 0F 6D 76 06 (76) 2009/01/06 23:47:36 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6D 76 (76) 2009/01/06 23:47:36 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:47:36 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 00 (00) 2009/01/06 23:47:36 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:47:37 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 76 (76) 2009/01/06 23:47:37 : [ E 6A 46 1] CLISP 118 2009/01/06 23:47:37 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:47:37 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:47:37 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:47:38 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) (Press Remote key to trigger setting setpoint at 62°) 2009/01/06 23:48:18 : [iNST-SRX ] 02 50 0A.15.36 00.00.04 C3 11 00 LTONRR (00) 2009/01/06 23:48:18 : [ A 15 36 4] DON 0 2009/01/06 23:48:18 : [ A 15 36 4] ST 255 2009/01/06 23:48:18 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 04 06 (04) 2009/01/06 23:48:18 : [iNST-SRX ] 02 50 0A.15.36 0C.A5.7A 42 11 04 LTONRR (04) 2009/01/06 23:48:19 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:48:19 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 04 (04) 2009/01/06 23:48:20 : [uNKNOWN ] 15 15 2009/01/06 23:48:20 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6A 00 (00) 2009/01/06 23:48:24 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:48:24 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:48:24 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:48:25 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6B 01 (01) 2009/01/06 23:48:25 : [iNST-ACK ] 02 62 0E.6A.46 0F 6D 7C 06 (7C) 2009/01/06 23:48:25 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6D 7C (7C) 2009/01/06 23:48:25 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 00 06 (00) 2009/01/06 23:48:26 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 88 (88) 2009/01/06 23:48:26 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 20 06 (20) 2009/01/06 23:48:26 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6A 7C (7C) 2009/01/06 23:48:26 : [ E 6A 46 1] CLISP 124 2009/01/06 23:48:26 : [iNST-ACK ] 02 62 0E.6A.46 0F 6A 60 06 (60) 2009/01/06 23:48:27 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 23 6A 09 (09) 2009/01/06 23:48:27 : [iNST-ACK ] 02 62 0E.6A.46 0F 6B 02 06 (02) 2009/01/06 23:48:27 : [iNST-SRX ] 02 50 0E.6A.46 0C.A5.7A 27 6B 01 (01) Link to comment
andrewm Posted January 7, 2009 Author Share Posted January 7, 2009 I just repeated the above test and got slightly different results. The lower setpoint was triggered OK, as before. Then triggering the higher setpoint resulted in the blower coming on and the thermostat getting stuck on the Cool 31 / Heat 0 display. Previously I'd only seen this when I didn't send the command to put the thermostat in Heat Mode command (as described in issue #3). Suggestions welcome! Link to comment
CompKing Posted January 7, 2009 Share Posted January 7, 2009 Known issue. Upgrade to the latest ISY beta. There was thermostat issues in the early betas. Link to comment
andrewm Posted January 8, 2009 Author Share Posted January 8, 2009 Known issue. Upgrade to the latest ISY beta. There was thermostat issues in the early betas. Thanks for the reply. Do you have a link to where this issue (or the fix) is described, as I couldn't see anything when I searched before? Link to comment
CompKing Posted January 8, 2009 Share Posted January 8, 2009 Known issue. Upgrade to the latest ISY beta. There was thermostat issues in the early betas. Thanks for the reply. Do you have a link to where this issue (or the fix) is described, as I couldn't see anything when I searched before? http://forum.universal-devices.com/view ... ostat#8119 for example Link to comment
andrewm Posted January 8, 2009 Author Share Posted January 8, 2009 That issue was from March 2008, and it looks like the fix was released in rev 2.6.4. I'm on 2.6.8. The only change to thermostat operation I see since 2.6.4 is 2.6.13 (the latest) which has the following fix: "thermostat query puts a 0 in the log before the actual value". Link to comment
CompKing Posted January 9, 2009 Share Posted January 9, 2009 That issue was from March 2008, and it looks like the fix was released in rev 2.6.4. I'm on 2.6.8. The only change to thermostat operation I see since 2.6.4 is 2.6.13 (the latest) which has the following fix: "thermostat query puts a 0 in the log before the actual value". I recall it wasn't that many versions ago where "heat" mode was being interpreted by the thermostat as "auto" mode. It was a bug which was around for a couple revisions. Before jumping to the conclusion that the thermostat is faulty, I'd try the upgrade and see if it resolves your issues. You aren't doing anything complex, and I have very similar routines set-up which work very well on my thermostat. I don't use Program or Auto modes, though I haven't disabled them either. As soon as Insteon communicates with the thermostat, they are ignored anyways by using the "Heat" mode in your command. Do you have "Programmable" turned on for the thermostat (option #1). I do, even though I don't use it... I suspect since you say your thermostat won't take keypad temperature changes (which mine does) that you have some kind of option enabled which I don't which is locking out the user. Perhaps setting the thermostat to Factory Defaults (see 19.2 of the manual) would be a fresh start too. Before changing settings, get the basics working first. If you are still having problems after a factory reset of the thermostat and firmware upgrade, send me a PM and we can work it in more detail. Cheers Link to comment
andrewm Posted January 9, 2009 Author Share Posted January 9, 2009 I did as you suggested and went to 2.6.13 last night - it seems to have improved the operation considerably. I no longer see any changes to auto-mode on the Thermostat display Thanks for all your responses. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.