Nest Link question forceBits

53 views
Skip to first unread message

Joe McMenimen

unread,
Sep 9, 2015, 8:14:04 AM9/9/15
to Wireless Sensor Tags
I am trying to turn off and on my Nest when a door is open or closed. Below is the code I am trying to use
thermostat.forceBits(0, false);KumoApp.Log("turn off");

The Log statement shows, but the Nest does not turn off.

Does the Nest integration support this method?

thanks

Zhiheng Cao

unread,
Sep 9, 2015, 6:49:39 PM9/9/15
to Joe McMenimen, Wireless Sensor Tags
Yes the Nest integration DOES support this method. However since a few days ago a server update to fix a bug related to Honeywell thermostat integration introduced a new bug that were blocking all temperature setting command sent to Nest. This bug has just been fixed, so please try again. 


--
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 http://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/3a3e635c-ac20-4c15-9f77-39a1dde1c9c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Joe McMenimen

unread,
Sep 13, 2015, 9:33:28 AM9/13/15
to Wireless Sensor Tags, joseph.m...@gmail.com
I tried again and am getting unexpected behavior.

My expectation is if I call forceBits(0, true) my Nest will turn off. Is this correct?

Also, I would think that forceBits(1, true) would turn on Heat and forceBits(-1, true) would turn on Cool. Is this a correct assumption?

Finally is hvacOn still supported? It seems to have disappeared from the Online Documentation and returns undefined when I try to log it.

thanks 

On Wednesday, September 9, 2015 at 6:49:39 PM UTC-4, mytaglist.com support wrote:
Yes the Nest integration DOES support this method. However since a few days ago a server update to fix a bug related to Honeywell thermostat integration introduced a new bug that were blocking all temperature setting command sent to Nest. This bug has just been fixed, so please try again. 

On Wed, Sep 9, 2015 at 5:14 AM, Joe McMenimen <joseph.m...@gmail.com> wrote:
I am trying to turn off and on my Nest when a door is open or closed. Below is the code I am trying to use
thermostat.forceBits(0, false);KumoApp.Log("turn off");

The Log statement shows, but the Nest does not turn off.

Does the Nest integration support this method?

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.

Zhiheng Cao

unread,
Sep 13, 2015, 11:45:12 PM9/13/15
to Joe McMenimen, Wireless Sensor Tags
If there is some error calling forceBits it will be logged in the KumoApp log. Please send me the log if there is "unexpected behavior". 

>My expectation is if I call forceBits(0, true) my Nest will turn off. Is this correct?Also, I would think that forceBits(1, true) would turn on Heat and forceBits(-1, true) would turn on Cool. Is this a correct assumption?
Yes

hvacOn property is not available. hvacOn=true would be identical to resume() and hvacOn=false would be identical to turnOff() so please use those methods


On Sun, Sep 13, 2015 at 6:33 AM, Joe McMenimen <joseph.m...@gmail.com> wrote:
I tried again and am getting unexpected behavior.

My expectation is if I call forceBits(0, true) my Nest will turn off. Is this correct?

Also, I would think that forceBits(1, true) would turn on Heat and forceBits(-1, true) would turn on Cool. Is this a correct assumption?

Finally is hvacOn still supported? It seems to have disappeared from the Online Documentation and returns undefined when I try to log it.

thanks 

On Wednesday, September 9, 2015 at 6:49:39 PM UTC-4, mytaglist.com support wrote:
Yes the Nest integration DOES support this method. However since a few days ago a server update to fix a bug related to Honeywell thermostat integration introduced a new bug that were blocking all temperature setting command sent to Nest. This bug has just been fixed, so please try again. 

On Wed, Sep 9, 2015 at 5:14 AM, Joe McMenimen <joseph.m...@gmail.com> wrote:
I am trying to turn off and on my Nest when a door is open or closed. Below is the code I am trying to use
thermostat.forceBits(0, false);KumoApp.Log("turn off");

The Log statement shows, but the Nest does not turn off.

Does the Nest integration support this method?

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-...@googlegroups.com.

--
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 http://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/c52c272e-a847-4be3-be5c-31213c036bf9%40googlegroups.com.

Joe McMenimen

unread,
Sep 14, 2015, 8:26:26 AM9/14/15
to Wireless Sensor Tags
I am not getting the expected behavior. It Never turns off, and the -1 and 1 change the target temp, but does not turn on heat or cool.

Here is the app and the log if you want to take a look.

When any of the window or door is opened for too long, turn off AC/heat. Off (App has been stopped successfully.)
Run

9/13/2015 9:36 AMApp has been stopped successfully.
9/13/2015 9:36 AMundefined
9/13/2015 9:34 AMApp has been started successfully.
9/13/2015 9:34 AMApp has been stopped successfully.
9/13/2015 9:26 AMundefined
9/13/2015 9:26 AMundefined
9/13/2015 9:25 AMApp has been started successfully.
9/13/2015 9:23 AMApp has been stopped successfully.
9/13/2015 9:23 AMundefined
9/13/2015 9:22 AMApp has been started successfully.
9/13/2015 9:22 AMApp has been stopped successfully.
9/13/2015 9:21 AMundefined
9/13/2015 9:19 AMApp has been started successfully.
9/13/2015 9:18 AMApp has been stopped successfully.
9/13/2015 9:17 AMundefined
9/13/2015 9:17 AMApp has been started successfully.
9/13/2015 9:16 AMApp has been stopped successfully.
9/13/2015 9:15 AMundefined
9/13/2015 9:14 AMApp has been started successfully.
9/13/2015 9:10 AMApp has been stopped successfully.

thank you for you support.



On Sunday, September 13, 2015 at 11:45:12 PM UTC-4, mytaglist.com support wrote:
If there is some error calling forceBits it will be logged in the KumoApp log. Please send me the log if there is "unexpected behavior". 

>My expectation is if I call forceBits(0, true) my Nest will turn off. Is this correct?Also, I would think that forceBits(1, true) would turn on Heat and forceBits(-1, true) would turn on Cool. Is this a correct assumption?
Yes

hvacOn property is not available. hvacOn=true would be identical to resume() and hvacOn=false would be identical to turnOff() so please use those methods

On Sun, Sep 13, 2015 at 6:33 AM, Joe McMenimen <joseph.m...@gmail.com> wrote:
I tried again and am getting unexpected behavior.

My expectation is if I call forceBits(0, true) my Nest will turn off. Is this correct?

Also, I would think that forceBits(1, true) would turn on Heat and forceBits(-1, true) would turn on Cool. Is this a correct assumption?

Finally is hvacOn still supported? It seems to have disappeared from the Online Documentation and returns undefined when I try to log it.

thanks 

On Wednesday, September 9, 2015 at 6:49:39 PM UTC-4, mytaglist.com support wrote:
Yes the Nest integration DOES support this method. However since a few days ago a server update to fix a bug related to Honeywell thermostat integration introduced a new bug that were blocking all temperature setting command sent to Nest. This bug has just been fixed, so please try again. 

On Wed, Sep 9, 2015 at 5:14 AM, Joe McMenimen <joseph.m...@gmail.com> wrote:
I am trying to turn off and on my Nest when a door is open or closed. Below is the code I am trying to use
thermostat.forceBits(0, false);KumoApp.Log("turn off");

The Log statement shows, but the Nest does not turn off.

Does the Nest integration support this method?

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.

--
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-s...@googlegroups.com.
Visit this group at http://groups.google.com/group/wireless-sensor-tags.

mytaglist.com support

unread,
Sep 17, 2015, 5:51:51 PM9/17/15
to Wireless Sensor Tags
Does -1 and 1 change the target temp to be lower or higher than the current temp at the Nest?  It is supposed to change the set temp at nest to be higher or lower than current temp at Nest. If you are saying heat or cool does not turn on even when set temp is higher/lower than current temp, it is because something inside nest is trying to save energy. Try -2 or 2, even -3 or 3, these will set the target temp at nest to more extreme one. 
Reply all
Reply to author
Forward
0 new messages