This is NOT a bug, but request for advice.
I have a Whyntair portable AC. Because of it's internal temp sensor showing much colder than room temp and no way to set an offset, I have created a Thermostat Controller with Cool only to control the cooling, and a virtual thermostat with heat only to control my primary thermostat (and smart vents). So, instead of directly controlling the AC, I get to use the TC and an external temp sensor in the room. Everything worked great. However, more recently, my daughter has started complaining of the beeping during the night. I've spoken with Whyntair and there is no way to turn off the beeping which is feedback for button presses or remote commands. I thought to open the AC to cover or disable the speaker inside, but I can't manage to open the outer cover(s). For the meanwhile, the AC gets turned off every night when a virtual "daughter is sleeping" switch gets thrown through a sleep routine.
I think what is happening is that when the temperature changes in the room as sensed by the external temp sensor, the TC (Idle Mode set to Offset) will send another temperature setpoint (as far as I can tell from the Events log). As the room is cooling, let's say by 5 degrees (plus 1/2 hysteresis), when the sensor reports a change of 0.5, the TC will send a readjusted temp setpoint. And the AC beeps. Repeat 11 more times until 1/2 the hystersis is reached and then the TC sends a setpoint higher than or the same as the current room temperature which lets the AC manage itself.
If I set the Idle Mode to Off, then the TC is unable to turn the AC on again and set the AC to cool or auto mode (long story, not the fault of TC).
This TC behavior, if it's even true, is fine for my primary thermostat and others that don't beep. Is there some way I can configure my TC to send a very low temperature setpoint ONCE when cooling is needed and then nothing else UNTIL the required setpoint is reached, thus eliminating, let's say 11 intermediate beeps?
