Can someone tell me how to achieve the following with NEST 2nd Gen ?

[Zuhdi AK]

So basically I have the following settings : 

Now I expect that when the Kumo sensor reaches 23 or 23.5 Celsius it will deactivate and activate my AC respectively. However, this does not happen. I don't have a heating wire attached and removed the Fan mode; The nest only has a Cooling function.

Maybe I have something wrong in the settings? Am I missing something? Would it be more efficient to use KumoApps for such thing?

Thanks

[Zuhdi AK]

Just wanted to add that both have the temperature range set between 23 and 23.5

[Zhiheng Cao]

Simply set the upper threshold (the box on the right edge) to something like 40C since you are not using it. Don't set the left and the right box number different by less than 1.5C like I explained already.

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.
To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/5877fcb4-af9e-4b79-a853-7f8704775940%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Sent from MetroMail

[Zuhdi AK]

Wouldnt that force the thermostat to go beyond 23.5C which is just around my comfort zone?

On Wednesday, March 30, 2016 at 11:30:56 PM UTC+4, mytaglist.com support wrote:

Simply set the upper threshold (the box on the right edge) to something like 40C since you are not using it. Don't set the left and the right box number different by less than 1.5C like I explained already.

On Wednesday, March 30, 2016, Zuhdi AK <zuhd...@gmail.com> wrote:

So basically I have the following settings : 

Now I expect that when the Kumo sensor reaches 23 or 23.5 Celsius it will deactivate and activate my AC respectively. However, this does not happen. I don't have a heating wire attached and removed the Fan mode; The nest only has a Cooling function.

Maybe I have something wrong in the settings? Am I missing something? Would it be more efficient to use KumoApps for such thing?

Thanks

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-tags+unsub...@googlegroups.com.
To post to this group, send email to wireless-sensor-tags@googlegroups.com.

Visit this group at https://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/5877fcb4-af9e-4b79-a853-7f8704775940%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Sent from MetroMail

[Zuhdi AK]

That doesn't make sense tbh. If I set my upper threshold to 50, then my sensor would state that it's too hot by the time my living room starts boiling!

I want the temperature to be between 23 and 23.5. Shouldn't this be easy to accomplish?

[Tom Wright]

I don't have exactly the same set up but I use it for heating. I like to keep the temperature between 20 and 20.5 degrees. What I've done is set the lower limit to 20, and the upper one to 25. I've used the temperature threshold setting to limit it to 0.5 of a degree difference. The behaviour now is that my heating comes on at 20, heats the room to 20.5 and then goes off.

In your case you could do the reverse for your AC - set the upper limit to 23.5 and your lower limit to maybe 20, then set a half a degree threshold. It should then cycle the temperature between 23-23.5.

[Zuhdi AK]

Thanks for the reply. It seems like I missed the whole threshold increment you spoke of. Can you post a pic of your settings? I'm not sure how to define the threshold by 0.5, and also how does that work?

[Tom Wright]

Screenshot is attached.

The threshold window is what determines the heating to come on and off as required, the upper boundary doesn't really do anything other than alert me, since I don't have AC.

When the room reaches the lower boundary, 20C, the heating will come on until it reaches 20.5C (as the threshold window is 0.5C), then it will go off.

In your case I would guess you can do the reverse of this, by ignoring your lower boundary (just set it to something really low) and set the upper boundary to the temperature you require the AC to come on at, so 23.5C. With your threshold set at 0.5C, it should cool to half a degree below that, so 23C, and then go off.

Again I'm no expert but I'm guessing that you may have been running into problems because the difference between your upper and lower boundaries was less than your threshold window, so nothing happened.

[Zuhdi AK]

Thank you for explaining this. I did what you told me and it seems to go down to 22 or 22.5 before switching off. At least that's better but I still need to test it more for the next few hours to make sure it's stable and not just being lucky.

Regarding what you mentioned, why does it work that way? I thought the upper boundary is used for the maximum temperature that is considered comfortable, which means anything higher than that is too hot. And the same goes for the lower boundary and related coldness. Why would the threshold window switch the Nest on and off? Logically, it should turn on at the higher boundary and turn off at the lower one, right?

I thought the threshold window only assists in notifying you that the temperature range is comfortable, and the value is used for how long it should wait before pushing the notification after crossing the boundary (e.g. a threshold of 0.5 means it will alert that it's comfortable at 23 when 23.5 is max)... Guess I understood it wrongly?

Thanks

[Tom Wright]

What are your threshold and boundaries set at?

I'm not 100% sure, but I think it works like this because the rule works by state change, the TempState variable in the KumoApp. Therefore, your AC comes on when the state is "too hot" (above the maximum boundary) and goes off when it is back to normal (the maximum boundary minus the threshold window). This is when it decides that the state is no longer "too hot".

To achieve behaviour as you describe, where it cools to the lower boundary, you would have to write a rule which turns the Nest off when the state changes to "too cold" rather than "normal" .

[Zuhdi AK]

Ahh this makes much more sense now !!! I thought my understanding was correct, didn't know it  registers the "normal" variable into consideration.

I turned off KumoApps and it seems to still directly control the thermostat, which the conditions you described helping in the process. I attached my settings : 

To achieve behaviour as you describe, where it cools to the lower boundary, you would have to write a rule which turns the Nest off when the state changes to "too cold" rather than "normal" 

I might just do that later, and ignore the normal state completely. 

[Tom Wright]

Glad you sort of got it sorted!

If you didn't want to use KumoApps you could also get a similar effect by making the threshold window a bit bigger, say 1 degree rather than 0.5, so it brings the temperature down a bit lower. Just don't make it larger than the difference between the upper and lower boundaries.

[Zuhdi AK]

Got it. Thanks a lot for explaining this more elaborately. Appreciated.

[Zuhdi AK]

Everything was working fine except for this last moment, temperature dropped and kumo signalled that temperature is back to normal, so nest stopped. However it's 24.5 now and it didn't signal nest to turn on!!! I didn't change a thing :/

Maybe I should use kumo app to avoid such strange behaviours?

[Zuhdi AK]

I realised that the KumoApp code "thermostat.forceBits(-1, true);" is useless and not very efficient. Not sure why but the whole KumoApp suite is not working reliably, although feedback from the ".log" is observed.

Can I force a specific temperature value on the thermostat, rather than just turn it off and on?

[Tom Wright]

Does it say that it's too hot or does it still say normal?

I find sometimes my heating doesn't react when one of the devices is unreachable. I think it tries 3 or 5 times and then times out.

I don't know what logic the built in app which triggers Nest to react to the temperature changes is using, but I found using a Kumoapp which triggers when the temperature changes rather than crosses the boundary to be more reliable (using temperatureChange rather than temperatureCross), because if it crosses and doesn't trigger for whatever reason, it's not going to trigger again.

[Zuhdi AK]

It says hot/normal/cold with no issues, it just doesn't trigger the nest. I modified the code to this and now it worked (first trial) : 

var sensors = <#Temperature sensor_[12|13|21|32|52|62|72]_N#>;

var thermostat = <#Thermostat_[62]_1#>;

sensors.forEach(function(sensor){

        sensor.temperatureCross= function () {

                try{

                    KumoApp.Log(sensor.name + " state is now " + sensor.tempState);

                    if(sensors.some(function(tag){ return tag.tempState==2 })){  // any tag is too hot

                         thermostat.forceBits(-2, true);

                         KumoApp.Log(thermostat.name + " AC turned ON");}

                    else if(sensors.some(function(tag){ return tag.tempState==3 })){  // any tag is too cold

                        thermostat.forceBits(0, true);

                        KumoApp.Log(thermostat.name + " AC turned OFF");}

                    else  

                        KumoApp.Log(thermostat.name + "Normal");

                }catch(e){

                    KumoApp.Log(JSON.stringify(e));

                }

        };

});

With the log : 

3/31/2016 9:15 PM	Living Room ThermostatNormal
3/31/2016 9:15 PM	Temp KumoSensor state is now 1
3/31/2016 9:12 PM	App has been started successfully.
3/31/2016 9:12 PM	App has been stopped successfully.
3/31/2016 9:11 PM	Living Room Thermostat AC turned ON
3/31/2016 9:11 PM	Temp KumoSensor state is now 2
3/31/2016 8:58 PM	App has been started successfully.

But it might stop working soon, so I'd rather use the temperatureChange. I noticed in docs its

  <#tag_[13]_1#>.temperatureChange=function(tag){ KumoApp.Log(tag.name + " is now " + tag.temperature + " degC" ); };  

Any idea how this can be used in my code? Or rather maybe your code is more efficient and you don't mind sharing it?

[Zuhdi AK]

Trying this out to see if it works : 

var sensors = <#Temperature sensor_[12|13|21|32|52|62|72]_N#>;

var thermostat = <#Thermostat_[62]_1#>;

sensors.forEach(function(sensor){

        sensor.temperatureChange= function () {

                try{

                    KumoApp.Log(sensor.name + " state is now " + sensor.temperature);

                    if(sensors.some(function(tag){ return tag.temperature>23.5 })){  // any tag is too hot

                         thermostat.forceBits(-2, true);

                         KumoApp.Log(thermostat.name + " AC turned ON");}

                    else if(sensors.some(function(tag){ return tag.temptemperature<22.6 })){  // any tag is too cold

[Zuhdi AK]

Well the code works and returns "AC turned ON" but nothing happens, reverting back to older code to see if that still works :/

[Tom Wright]

If it was working earlier but not now it sounds like your Nest is just unreachable. Can you confirm that your Nest is still online and in the correct mode?

[Zuhdi AK]

Well it worked for one trigger, didn't test a whole cycle .. It's more of a hit-or-miss kind of ordeal with this whole thing. The Nest thermostat is online and active.

Can you share your code? Maybe it's more efficient

[Tom Wright]

My set up is actually for Wemo, not Nest, so the code for triggering them is quite different as the Wemos are just on or off. The temperature state and threshold mentioned previously though is the same.

[Zuhdi AK]

Ah I see...Not sure what's going on. Do the Kumosensor support team look over these forums?