Ah this makes a bit more sense now.
1. It's set as the wireless tag and not the thermostat.
2. Yeah it keeps flipping back to On.
3. I'm not using the heat functionality with my Nest though.
Now the whole 28 Celsius temperature output from the tag makes sense. It senses that the room became too cold after cooling and sets it to 28 to heat it down to the comfort zone. However I am not using the heating function at all, only the cooling and fan wires are connected to my nest. I'm essentially trying to trigger the nest to activate by setting it to 22 when its hot and 24 when its too cold (so that it turns off or on respectively).
On Tuesday, March 29, 2016 at 12:08:49 AM UTC+4,
mytaglist.com support wrote:
> 1. If the "Set At" sensor is not the thermostat itself, what the thermostat puts is not the comfort zone but computed from the state of the sensor tag in order to force the AC or heat on/off. What is your "Set At:"?
> 2. Have you tried the Fan on/auto switch in the app? The integration should not change the whatever fan state is set at the thermostat.
> 3. Please set your thermostat to "Heat-Cool" due to a bug on the Nest's side, if your thermostat is set to "Heat" only the lower threshold is saved and if it is "Cool" only the upper threshold is saved.
>
>
> On Monday, March 28, 2016, Zuhdi AK <
zuhd...@gmail.com> wrote:
>
> I have a few problems with Nest integration with PIR KumoSensor :
>
>
> I'm not sure why, but my set comfort zone (22.5-23.5 Celsius) isn't really monitored. I suddenly see the thermostat put at 28 celsius!!After the A/C runs, the fan is automatically turned on and I can't seem to prevent that. The fan doesn't usually run prior to the wireless tag, but now it keeps running every single time.The application shows one thing (comfort zone 22.5-25) and the web shows another, they don't seem to communicate well