I have two remote temperature sensors (ADC-S2000-T-RA) connected to a thermostat. They show up in the Alarm.com dashboard, but I am having trouble using them with the set point. It seems to be not working correctly, but I could be misunderstanding something.
ISSUE #1: set point behavior
When I try to use the app to change the temperature reading to the remote sensors, it seems to work at first, but the system always automatically “resets” back to the using the main sensor. Is it supposed to do this?
EXPLANATION
Say for example, the main thermostat reads 75 and the remote reads 72. If the set point is 73, by default, the system is cooling since it only looks at the main sensor. Expected behavior.
If I use the app and instead select the remote thermostat, the UI shows the temperature is now “72” (since it’s reading the remote). The cooling turns off. Again, expected behavior.
After some delay, the UI resets and again shows the temperature from the main thermostat “75”. The cooling turns back on. NOT EXPECTED BEHAVIOR.
I’e tried this repeatedly, and the system always eventually “forgets” that I’ve selected the remote sensors. Sometimes it takes a few minutes, sometimes it takes a few hours. I wonder if this could be a bug, maybe with the Android app. Has anyone experienced this?
ISSUE #2: schedule
How are remote sensors supposed to work with the schedule?
For example, I set my cooling schedule so at 8pm it changes to “72”. This works fine, more or less. AT 8pm, the set point changes to 72.
However, if I select the remote sensor on the cooling schedule, it doesn’t seem to make a difference. It changes the set point to 72, but it doesn’t change the sensors that it’s using to read the temperature. Meaning it runs until the main thermostat reads 72, when my expectation is that it would run until the remote reads 72. Of course, this could be just another symptom related to ISSUE #1.
Really hoping someone has insight into how this is supposed to work.