Honeywell TH8320ZW Tstat

[JayD.]

My Tstats randomly change its programming to "Permanent hold". I have several Honeywell TH8320ZW connected to a M1 using eKeypad on iPhone/iPad for control. Does anyone have experience with this Tstat and know the cause of the program change?
 

 

[wkearney99]

I had a Honeywell (not that model) also get confused about being on a permanent hold.  Turned out it was a low battery situation on a wireless remote configured to work with it.  The touchscreen was getting wonky due to low power and was causing the hold change.  Go figure.  Mine are the VisionPro 8000 series, using the Redlink gateway.  Which I may replace as Honeywell seems to have abandoned actually doing anything with Redlink.  Such is the price for being caught at the cutting edge, when tech zigs and you zagged.

 

[JayD.]

Thanks for the info.  I am not getting any support from Honeywell.  The tech desk said the problem is created when the Tstats are enrolled in the zwave network.  So much for wanting a zwave Tstat.  I will replace the batteries any way.

 

[SterlingDonnelly]

Have you tried excluding and then re-including the thermostat?

 

[wkearney99]

Thanks for the info.  I am not getting any support from Honeywell.  The tech desk said the problem is created when the Tstats are enrolled in the zwave network.  So much for wanting a zwave Tstat.  I will replace the batteries any way.

 
The issue with the batteries was not in the thermostat itself, but in the remote that was associated with the Redlink network.  The remote was sending an errant command that the thermostat was causing the thermostat to go into permanent hold mode.  I gather this was some sort of failsafe.  I can't readily repeat it, so who knows.  But I'd wonder if there's anything in your configuration that might be leading the thermostat to decide on the hold mode?  Don't know how you'd determine this, though.  One thought might be to minimize what can interact with it, start by peeling back to no devices and then adding them back.  The tricky part will be watching to see what/when the hold gets triggered.
 
My VisionPro has a microSD card slot and I believe it's capable of some sort of logging.  Is there any kind of logging option for your model?  Might be a good way to pin down when it's happening, if not also what instigated it.

 

[JayD.]

Update:
Been traveling a lot recently and managing the house remotely with eKeypad and M1ToGO. I configured the TSTATs to Non-programmable mode and programmed temp setpoints with the ELK. The TSTATs would still frequently go into Energy Saving mode and ignored the Elk temp setpoint programming. I discovered that sending a Set TSTAT Off command would change the Energy Saving mode. I also had problems with some commands not executing and had to set some TSTATs manually remotely.

Back home now, I added the code below to control the four TSTATs. The code appeared to be working corrected at each setpoint time. Any suggestions and/or experience using similar code? Also, how could the AC mode setpoints be activated?

Away TStat Mode
WHENEVER TSTAT Away (Task 14) IS ACTIVATED
THEN SET MAIN (Tstat 1) OFF
THEN SET MAIN (Tstat 1) TO HEAT
THEN SET MAIN (Tstat 1) HEATING DESIRED TEMP TO 64 DEG. F. (18 DEG. C.)
THEN TURN Output 105 ON FOR 1 MIN
WHENEVER Output 105 STATE IS TURNED OFF
THEN SET MASTER (Tstat 2) OFF
THEN SET MASTER (Tstat 2) TO HEAT
THEN SET MASTER (Tstat 2) HEATING DESIRED TEMP TO 64 DEG. F. (18 DEG. C.)
THEN TURN Output 106 ON FOR 1 MIN
WHENEVER Output 106 STATE IS TURNED OFF
THEN SET LOWER (Tstat 3) OFF
THEN SET LOWER (Tstat 3) TO HEAT
THEN SET LOWER (Tstat 3) HEATING DESIRED TEMP TO 64 DEG. F. (18 DEG. C.)
THEN TURN Output 107 ON FOR 1 MIN
WHENEVER Output 107 STATE IS TURNED OFF
THEN SET UPPER (Tstat 4) OFF
THEN SET UPPER (Tstat 4) TO HEAT
THEN SET UPPER (Tstat 4) HEATING DESIRED TEMP TO 64 DEG. F. (18 DEG. C.)