Nest Thermostat Link

[mytaglist.com support]

The capability to link Nest Thermostats as tags has been added. To link, from https://mytaglist.com/eth/ simply click "+ Add a New Tag" then "Link Nest Thermostats". 

Now you can

• Set heat/cool targets, home/away, fan on/off from the web/app interface like shown in kumostat.com
• Use temperature events @another sensor tag to control Nest. The lower/upper target temperature at Nest will automatically move so as to regulate the temperature at specified sensor tag within the "comfort zone" (this will automatically control the too-hot/too-low temperature at the chosen tag). Simply choose the tag at "Set at" drop-down. 
  Once you set the "target" back to Nest itself, the target temperature at Nest will be automatically restored to the value on "comfort zone" slider. 
• Once Nest is linked, a whole new range of KumoApp becomes available for installation, such as "Turn off heat/AC ( equivalent to setting to "away" in Nest when "auto-away" is not used, and to "off" with "auto-away" on ) when window is open", "turn on heat/AC (same as setting to "home" or "heat-cool" depending on if auto-away is used) when my iPhone gets close to home". With soon-be-available PIR and Reed sensors, you will be able to install/write your own KumoApps like "when PIR detected motion, set to home, or use temperature events at the PIR sensor to control thermostat.  "When sliding door/window is open, set to "away" etc. 
• "Upper/lower target temperatures" at Nest are just like the upper/lower temperature thresholds in regular tags with temperature monitoring enabled. When these thresholds are crossed, you can specify email/tweets/push notifications to be sent or custom URL to be called. You can even use these events to control another Nest thermostat.

The current iOS app does not have the link button added, but once linked from the Web interface, the thermostats are accessible also from the iOS app. Complete Nest link support will appear in the next iOS app release (in approx. 1 week). 

No amount of internal testing can substitute feedback from actual users. Please submit bug reports at the forum or email to sup...@mytaglist.com. We appreciate your feedback.

[Aidan Bree]

Hi,

Really happy to see the Nest integration. I have tried to use the app

'When any of the window or door is opened, turn off AC/heat'

however, it won't start for me.

Any suggestions?

[mytaglist.com support]

I just checked your account. Usually if you encounter any problem it is because of expired/unsynchronized  Nest authorization token. You just need to click "Add New Tag" and then "Link Nest Thermostats" button again. This will force the system to re-authorize with Nest again and update the authorization token. I just did this for you and looks like your Nest system cannot "cool" so unfortunately it cannot be set to "heat-cool" which is the only mode we support currently.

[Aidan Bree]

Hi,

Any idea when you will support only 'heat'?

Can you clarify whether you are working on IFTTT integration? I see that as a brilliant way to integrate the tags with other systems. Particularly interested in using these with Philips Hue and obviously the Nest. It would also be really nice to have the google docs integration and all the other bits from IFTTT.

Thanks again

Aidan

[mytaglist.com support]

Hi Adrian,

We have made some updates in the Nest Link server back-end, so if your thermostat can only do "heat" or "cool" that mode will be chosen instead of "heat-cool". There is no user interface change (which takes longer because of app review times) so you will still see the two knobs in the range slider, but only the lower knob (for heat only system, and upper knob for cool only system) will be functional. You can still drag the non functional knob but it should soon return to the edge -1C / 44C by itself. If you set temperature target to another tag you will be able to drag both knobs, but the system will only turn off heat by setting the target temperature lower if the temperature target tag is "too hot". 

Please give it a try. 

Thanks,

support

[Zhiheng Cao]

Right now, it seems that we are too "small" to be taken seriously by folks at IFTTT. We have marketing plans being implemented over the next few weeks to boost our sales and presence. 

Due to the unique architecture of our product we have very healthy profit margin even at the current low pricing point. 

We believe that with the right plan we can use that to boost our scale and growth while remain profitable. 

--
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.
For more options, visit https://groups.google.com/d/optout.

[Aidan Bree]

Thanks for the update....I am trying it out now.

Hopefully you are just on the list of integrators and they will get to you soon....I see that there were 4 additional channels on IFTTT added today, one of which looks similarly 'small' but interesting!

http://littlebits.cc/cloud

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

[Aidan Bree]

Hi,

I am still getting failures.

I have removed the Nest thermostat and re-added it but no difference

Also, I am unable to set the Nest to away from the Wirelesstag web ui. I was getting an error message but it is no longer generating it.

[mytaglist.com support]

If the error message was "invalid thermostat Id" or something similar, it is caused by a known bug in the Nest API (see https://github.com/nestlabs/control-jquery/blob/master/app/javascript/nest.js line 255 which admits this bug and shows the workaround). This workaround has just been added to our code. 

// TAH-361, device_id does not match the device's path ID
  thermostat.device_id = structure.thermostats[0];

If the error message was something else, can you post it here.

[Aidan Bree]

Hi,

I removed the thermostat yesterday and re-added it. When I did that I could set it to away/home via the interface.

Today I went in to see the logs and noticed that the apps have stopped - I then tried to toggle home/away manually again but get a message

'Invalid structure ID'

And the toggle no longer works.

[mytaglist.com support]

Yes we got that error in our log also. 

I don't know what other people think of the Nest official API based on Firebase, but it seems there is quite a bit of quirks. 

The structure ID changes and not consistent in three different places where it appears...  It is like the API telling you your thermostat is moving from one building (structure) to another.

Anyway, we have increased the robustness on our side in case the Nest API returns inconsistent results (i.e. if it complains about "invalid structure Id" try a different structure Id appearing in the data returned by them... even though there supposed to be only one structure Id).  

Please try again. 

[Aidan Bree]

Now getting a new message

'The given key was not present in the dictionary'

I have tried removing and re-adding without success

[mda]

@mytaglist.com support 

Is it possible to enable/disable the nest following the temperature from a particular tag (or in general) using http commands (so my home automation system can turn that feature on and off based on its knowledge of when we go to sleep and if certain rooms are occupied?

Thanks.

[mda]

i can not link more than one of my Nest thermostats to my account. The UI lets me select both of my Nests but only one shows up in my list of tags. 

My nest account is setup with each Nest in its own home, perhaps that is a case that you did not code to handle?

What info can i provide to help debug? Thanks!

[Zhiheng Cao]

Yes you would use the JSON web method http://mytaglist.com/media/mytaglist.com/ethClient.asmx@op=ThermostatOnOff.html   supply it with Cookie you received from http://mytaglist.com/media/mytaglist.com/ethAccount.asmx@op=SignIn.html  

--

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.

[mytaglist.com support]

Nest service official API is based on Firebase, a semi-open (because their client library source code is encrypted, protocol undocumented, so for example people cannot write a full feature ASP.NET/C# client or dig deeper when something goes wrong) platform. 

We have upgraded the Firebase client library version from 1.0.17 to 1.0.21 (https://www.firebase.com/docs/web/changelog.html) (we use node.js for this). 

Hopefully this will fix some of the issues you are having with Nest Link. 

[Aidan Bree]

Hi,

I have not seen any improvement since the update. I can see from the temperature graphs on my Nest in the panel that there is connectivity for a few hours every few days...

[mytaglist.com support]

Hi Aidan

We have discovered a serious problem with the Nest Link and have recently fixed it. Please try again to see if Nest Link is now working for you.

http://wirelesstags.myshopify.com/blogs/news/15577140-nest-link-is-now-working

[Aidan Bree]

Hi,

I can confirm that everything is now working correctly! Many thanks for sorting this issue. It now works really well

Cheers

Aidan

[Wynne Walker]

Sorry if this is a stupid question but ss it possible to receive feedback from Nest not just send commands to it? For example can we see if Nest is currently calling for Heat, Cool or Fan? If so, can we use that state to trigger other events? 

Wynne

[Blair Phifer]

I may be repeating a question, but...

I have a two story house that is only one zone, with the thermostat on the main floor. I understand that I can't have a multi-zone system with the way my furnace and AC are set up, but what I'd like to have is the ability to base the temperature on a different location in my house, (the second floor). In the winter, the top floor is too warm, and in the summer, the AC makes it too cold. I do have a way to change the direction of the airflow, buy it doesn't work enough. I also have a fireplace on the main floor that I can't use due to it's proximity to the thermostat.

If I get a Nest, can I use your sensors to be the temperature that the Nest is working to?

Thanks!

[mytaglist.com support]

Yes. 

[mytaglist.com support]

Yes. Your nest thermostat when linked as a tag will be able to generate the temperature too hot/too cold/back to normal events, which you can use from a KumoApp by assigning function to the event http://mytaglist.com/kumoapp/61/temperaturecross 

[Steve Clark]

I see from other posts that it's not possible to link multiple thermostats to wireless tags, but is the reverse possible?  Is it possible to have multiple tags control one thermostat?  I have been using one tag to control my Nest and it's been working great, but as the seasons change we're finding different parts of our new home are now colder relative to the rest of the house when other rooms were the problem earlier (I think it has to do with sunlight, etc). 

This is a long way of asking if it's possible to have two rooms set minimum temperatures and if EITHER falls too low to have the thermostat kick in?  I'd rather not keep juggling tags and moving them around, seems like we'll lose or confuse them that way.  If it's possible it would be an excellent feature, especially in old one zone heating systems like ours.

On Thursday, July 17, 2014 at 3:42:37 PM UTC-4, mytaglist.com support wrote:

[mytaglist.com support]

Hi Steve,

Yes this is possible with a simple KumoApp code like follows:

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

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

sensors.forEach(function(sensor){

        sensor.temperatureCross= function () {

                try{

                    

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

                         thermostat.forceBits(-1, true);

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

                        thermostat.forceBits(1, true);

                    else

                        thermostat.forceBits(0, true);

                    

                }catch(e){

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

                }

        };

});

Link to the app:

http://mytaglist.com/eth/appcoder.html?619984d4-9686-49bc-b417-3f27ca5fc764

[Senyo]

Hi support, I've just tried that kumoapp code with my 2nd generation nest and it doesn't work. Have you got any other suggestion please.

[Zhiheng Cao]

What's your app login email?

On Thursday, January 21, 2016, Senyo <seclke...@gmail.com> wrote:

Hi support, I've just tried that kumoapp code with my 2nd generation nest and it doesn't work. Have you got any other suggestion please.

--
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/affc9a0d-cb8b-4a64-b356-5d9d2aa2ceaa%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Sent from MetroMail

[Stelios Makrinos]

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

[Zhiheng Cao]

Yes, use the KumoApp "Set thermostat temperature sensor to different tag at different time of the day" and choose nest itself as the temperature sensor in some of the 4 available scheduling time points. 

On Wed, Mar 2, 2016 at 11:29 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

--

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/8ce1d833-7966-4fe6-974c-2bfdaf1d8f18%40googlegroups.com.

[Stelios Makrinos]

I have been using that one, however I am unsure of a couple of things.  

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   
2. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

On Wednesday, March 2, 2016 at 6:40:54 PM UTC-5, mytaglist.com support wrote:

Yes, use the KumoApp "Set thermostat temperature sensor to different tag at different time of the day" and choose nest itself as the temperature sensor in some of the 4 available scheduling time points. 

On Wed, Mar 2, 2016 at 11:29 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

--
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]

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   

I am not sure I understand your question. There is only 1 comfort zone setting (high/low temperature) for each nest no matter what the "Set At" is. If the "Set At" is changed from nest itself to a tag, the tag's temperature monitoring is automatically updated to the comfort zone, and nest's setting will change to make it turn on/off heat or AC. If the "Set At" is changed from a tag to nest itself, the comfort zone setting will be applied back to nest's setting. The "comfort zone setting" itself should never change unless you drag the slider in the app or if "Set At" is nest itself and you change the nest's setting. If "Set At" is nest itself the comfort zone setting is synchronized with nest, meaning if you change it from wireless tag app home.nest.com side will change automatically and if you change from home.nest.com side wirelesstag app comfort zone will change automatically. 

1. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

So this is possible if "Set At" is nest itself. 

On Thu, Mar 3, 2016 at 5:56 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have been using that one, however I am unsure of a couple of things.  

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   
2. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

On Wednesday, March 2, 2016 at 6:40:54 PM UTC-5, mytaglist.com support wrote:

Yes, use the KumoApp "Set thermostat temperature sensor to different tag at different time of the day" and choose nest itself as the temperature sensor in some of the 4 available scheduling time points. 

On Wed, Mar 2, 2016 at 11:29 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

--
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/8ce1d833-7966-4fe6-974c-2bfdaf1d8f18%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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/faa3ab16-b09b-43fd-9ea0-90818a02afc4%40googlegroups.com.

[Stelios Makrinos]

So I understand the bit about the synchronization between the actual Nest and the "associated" Nest in the wireless tag app.  That is fine.

My bigger issue is that when the Nest is being controlled by another tag (e.g. the tag in my bedroom) which has a different setting than the Nest, occasionally something is triggering a change in the comfort zone settings to match the Nest itself.  This is incorrect.  The comfort zone settings of the Wireless Tags should not get updated by the Nest.

On Thursday, March 3, 2016 at 1:06:01 PM UTC-5, mytaglist.com support wrote:

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   

I am not sure I understand your question. There is only 1 comfort zone setting (high/low temperature) for each nest no matter what the "Set At" is. If the "Set At" is changed from nest itself to a tag, the tag's temperature monitoring is automatically updated to the comfort zone, and nest's setting will change to make it turn on/off heat or AC. If the "Set At" is changed from a tag to nest itself, the comfort zone setting will be applied back to nest's setting. The "comfort zone setting" itself should never change unless you drag the slider in the app or if "Set At" is nest itself and you change the nest's setting. If "Set At" is nest itself the comfort zone setting is synchronized with nest, meaning if you change it from wireless tag app home.nest.com side will change automatically and if you change from home.nest.com side wirelesstag app comfort zone will change automatically. 

1. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

So this is possible if "Set At" is nest itself. 

On Thu, Mar 3, 2016 at 5:56 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have been using that one, however I am unsure of a couple of things.  

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   
2. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

On Wednesday, March 2, 2016 at 6:40:54 PM UTC-5, mytaglist.com support wrote:

Yes, use the KumoApp "Set thermostat temperature sensor to different tag at different time of the day" and choose nest itself as the temperature sensor in some of the 4 available scheduling time points. 

On Wed, Mar 2, 2016 at 11:29 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

--
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 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/8ce1d833-7966-4fe6-974c-2bfdaf1d8f18%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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 https://groups.google.com/group/wireless-sensor-tags.

[Ben G.]

Support --

Sorry, I'm still a little confused on how best to set up my Nest and tag(s). Have a two-story house, single zone HVAC, and the Nest is downstairs. I would like to use a wireless tag in one of the upstairs bedrooms at night, but only as the temperature sensor for the Nest. I would like to keep the Nest as primary for scheduling what the temperature should be. I do not want to control the Nest via comfort zones in the WirelessTag app. I just want the Nest to look to the wireless tag for the temperature during certain periods. Is that possible? Sorry if this has already been answered.

Thanks,
Ben

On Thursday, March 3, 2016 at 10:06:01 AM UTC-8, mytaglist.com support wrote:

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   

I am not sure I understand your question. There is only 1 comfort zone setting (high/low temperature) for each nest no matter what the "Set At" is. If the "Set At" is changed from nest itself to a tag, the tag's temperature monitoring is automatically updated to the comfort zone, and nest's setting will change to make it turn on/off heat or AC. If the "Set At" is changed from a tag to nest itself, the comfort zone setting will be applied back to nest's setting. The "comfort zone setting" itself should never change unless you drag the slider in the app or if "Set At" is nest itself and you change the nest's setting. If "Set At" is nest itself the comfort zone setting is synchronized with nest, meaning if you change it from wireless tag app home.nest.com side will change automatically and if you change from home.nest.com side wirelesstag app comfort zone will change automatically. 

1. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

So this is possible if "Set At" is nest itself. 

On Thu, Mar 3, 2016 at 5:56 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have been using that one, however I am unsure of a couple of things.  

1. When looking at the associated Nest where does it get its Comfort Zone settings from and what happens if you modify them.  I would expect that the come from the Nest and the UI should not allow them to be modified.
   
2. Occasionally the comfort zones that I set up on the wireless sensors seem to get overwritten by the one on the associated Nest.  Has anyone else experienced this?

On Wednesday, March 2, 2016 at 6:40:54 PM UTC-5, mytaglist.com support wrote:

Yes, use the KumoApp "Set thermostat temperature sensor to different tag at different time of the day" and choose nest itself as the temperature sensor in some of the 4 available scheduling time points. 

On Wed, Mar 2, 2016 at 11:29 AM, Stelios Makrinos <stelios....@icloud.com> wrote:

I have a 2 story house with a single zone.  I have linked my Nest and wish to control it through a tag upstairs, but only during certain parts of the day.  I have been able to do that by installing and modifying a KumoApp however when it isn't controlled by the tag I want the Nest to control the temperature.  What I mean is that I want the actual settings on the Nest to be used rather than the temperature range that appears on the linked Nest in the app.  Is there anyway to do this?

--
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 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/8ce1d833-7966-4fe6-974c-2bfdaf1d8f18%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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 https://groups.google.com/group/wireless-sensor-tags.

[Neal Patrick]

Hi, I have tried using the KumoApp "When Any of the window or door is opened for too long, turn off AC/heat" with my Nest. I am using a Reed sensor, and can configure it to notify me when the door is opened or closed.

However, when I run the app, and I open the door, I get the following error: Jurassic.JavaScriptException: ReferenceError: sensor is not defined at anonymous(ScriptEngine , Scope , Object , FunctionInstance , Object[] ) at Jurassic.Library.UserDefinedFunction.CallLateBound(Object thisObject, Object[] argumentValues) in C:\z560_backup\jurassic_0336599937d3\Jurassic\Library\Function\UserDefinedFunction.cs:line 245 at MyTagList.KumoAppEngine.Tag.b__18_0(String json) in C:\z560_backup\MyTagList\KumoApp\KumoAppEngine\Tag.cs:line 158

Not sure what to do from here - thanks!

[Ken Link]

I'm seeing the same javascript error. Have you figured out a solution/workaround?

[Neal Patrick]

I have not received a response. My workaround has been to use IFTTT, which is sub-optimal since it doesn't allow for a delay (the Nest adjusts the temperature as soon as the door is opened).

[Steve Clark]

I have noticed a similar odd error message with the "For multiple sensor tags: If any is too hot or too cold, turn on AC or heat" app.  I tried uninstalling/re-installing the app, and also tried re-linking the Nest thermostat, and it will work for a bit, but then I start receiving the error message again.  Is there any chance I have something incorrectly configured on the Nest or Wireless Tag side?  Has anyone else experienced this?  The app worked great last year, but now have more kids' rooms to cover and want to be sure it's working.

Error message: {"message":"Heat/AC is currently off","stack":"Error: Heat/AC is currently off\r\n at forceBits (native)\r\n at anonymous (unknown:11)"}
      - The "unknown:11" changes to different numbers each time (13, 15, etc)

Thanks
     - Steve