Okay, my Zen thermostat has been behaving well for months. Now, with firmware 2.3.9.201, this has changed. I don't know how, but my cool and heat settings for the Zen will unexpectedly switch. It is in the 20s (F) outside. The thermostat heat setpoint was stepping down so that the setpoint ended up being as low as 40 degrees (F). It took several attempts to run my check rule for the thermostat to finally accept the proper temperature setpoints.
I have tried backing down to 2.3.9.200 as I have never had this type of switching temperature checkpoints. I have had times when the setpoint changes did not happen at the proper time, but never anything like this.
I have backed off to 2.3.9.200. I don't know what changed for this to happen. I hope that reverting to 2.3.9.200 will fix this.
There haven't been any changes to the Zen Thermostat driver since platform version 2.3.4, so whatever is happening for you must just be coincidence. But what that is, I can't say...
There may have been no changes to the Zen Thermostat driver, but something has changed. I switched back to 2.3.9.200 and it is behaving. I tried upgrading to 2.3.9.201, and the same problem with really weird temperature setpoints for heating and cooling started up again. I backed of to 2.3.9.200, and things are working again.
It could be related to my HF amplifier but I have used that many times previously with nothing like this happening. I am at a loss to explain what might be happening. However, I will stick with 2.3.9.200 since it is working.
@mike.maxwell This is really strange., My Zen Zigbee edition has been working well until I did the upgrade to the 2.3.9.201 firmware. I don't know what may have changed that could be causing issues. I have, during the cold weather, had the thermostat going to setpoints that make no sense, such as shifting from my heating setpoint of 72F to temperatures in the 40s and my cooling setpoint of 76F to temperatures in the 50s, turning the AC on. This is with outside temperatures in the 30s and 40s.
I did not capture the logs and it appears that those entries have aged out so I can't view them or they were cleared when I reverted back to the 2.3.9.200 firmware. Since reverting, the thermostat is behaving normally and I have not seen anything more than the usual occasional time when the setpoint change did not happen. In that case, my rules to check catch that and on the next check, the setpoints will be corrected.
There may have been no changes in the Zen driver, but something changed that is affecting the thermostat. I have no idea what that might be.
Edit: Just to confirm, I did the 2.3.9.201 update again and started experiencing the same anomalies. I reverted to 2.3.9.200 again, and have not had the problem occur. The only change in operation is the firmware. I've used the Ameritron ALS-1300 amplifier many times and not had it affect my thermostat settings so I do not think the amplifier is the issue.
Edit: Unfortunately, I just had it happen again with the 2.3.9.200 firmware, so it likely is related to the amplifier.
I decided that the Zen has likely reached the end of its serviceable life for me. I had previously ordered a Lux KONOz, so I installed it today. I hope it will behave better.
I had to modify my rules. The KONOz lacks an auto mode, so I created two rules that should act like the auto mode. If the temperature exceeds 74F and stays that way for 30 minutes, the rule should switch it to Cool mode. Conversely, if the temperature drops to 68F and stays that way for 30 minutes, the rule should switch the KONOz to heat mode. It will take time to see if this actually works as this time of year, I don't expect the weather to be warm enough to switch from heat to cool and vice-versa.
So, just for housekeeping, I will mark this as solved.
