KumoApps are not reliably being triggered on tag Events.

[David Eck]

As each tag logs an event it is imediately stored here: https://www.mytaglist.com/eth/events.html These stay up to date and are correct, but only some of my apps respond to them while others that are also waiting on the same event do nothing. There is nothing wrong with the code as some apps work one day but not the next. For example, I have 3 separate apps looking at the same sensor for door open and closed events. When the door opens it shows in the Event History, but not all three are triggered by it when it happens. It may be only one or two of them that take action one day, and the next it could be a defferent one or two.
I have stopped and restarted the apps, uninstalled and reinstalled, many times and on one or two occations it might have temporarily helped.

I don't know if it is related or not but sometimes I will get the following error in the KumoApp log, sometimes it runs (without error) exactly like it is supposed to, or does nothing (without error) as described above.

Jurassic.JavaScriptException: ReferenceError: KumoApp 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

[Zhiheng Cao]

Thank you for reporting this problem,  can you copy&paste the app code here?  When you find the app respond or not respond to events, do you do this through logged message?

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

[mytaglist.com support]

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

Yesterday change to KumoApp engine was made which should significantly improve this problem.  Please report back in couple days if this situation improved or not. 

On Friday, September 7, 2018 at 2:58:44 PM UTC-7, mytaglist.com support wrote:

Thank you for reporting this problem,  can you copy&paste the app code here?  When you find the app respond or not respond to events, do you do this through logged message?

On Fri, Sep 7, 2018 at 2:52 PM David Eck <dave...@gmail.com> wrote:

As each tag logs an event it is imediately stored here: https://www.mytaglist.com/eth/events.html These stay up to date and are correct, but only some of my apps respond to them while others that are also waiting on the same event do nothing. There is nothing wrong with the code as some apps work one day but not the next. For example, I have 3 separate apps looking at the same sensor for door open and closed events. When the door opens it shows in the Event History, but not all three are triggered by it when it happens. It may be only one or two of them that take action one day, and the next it could be a defferent one or two.
I have stopped and restarted the apps, uninstalled and reinstalled, many times and on one or two occations it might have temporarily helped.

I don't know if it is related or not but sometimes I will get the following error in the KumoApp log, sometimes it runs (without error) exactly like it is supposed to, or does nothing (without error) as described above.

Jurassic.JavaScriptException: ReferenceError: KumoApp 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

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

[Claire Britton]

I think this change has led to my new problems. The Kumo apps that I have been running for years, have now stopped working. I can start the app and everything looks fine, but it simply does nothing. Almost every Kumo app in my setup simply no longer works, with no error.

Can the please be fixed, as this also effects my WeMo setup and D-Link camera setup. These Tags are at the core of my setup and most importantly the Kumo app system.

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

To post to this group, send email to wireless-s...@googlegroups.com.

[Darrin J. Calcutt]

I too am with Kumo apps now!

Darrin J. Calcutt

Sent from my iPhone

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

[Russel Met]

My Kumo Apps I've been using for well over a year are now not working any longer.  They start fine and return one change in value and then nothing.  Here's my code. Can someone tell me what I need to change to get these to work again?

var tags = <#tags_[12|13|32|52|62|72|21]_N#>;

var isy_ip=<%ISY IP Address%>;

var isy_user = <%ISY username%>;

var isy_password=<%ISY password%>;

var isy_variable = <%ISY Variable%>;

tags.forEach(

function (tag) {

    tag.updated = function () {

        var cur_temp = tag.temperature;

        var cur_temp_f = cur_temp * 9 / 5 + 32;

        var new_cur_temp = Math.round(cur_temp_f * 10);

        KumoApp.Log("Temp updated to "+new_cur_temp+", actual tag temp is "+cur_temp);

        KumoApp.httpCall("http://"+isy_user+":"+isy_password+"@"+isy_ip+"/rest/vars/set/1/"+isy_variable+"/"+new_cur_temp, "GET");

    };

}

);

[Zhiheng Cao]

What is your app login email?  Looking at the log, we see KumoApp triggers for many users keeps firing normally. I just want to match your user id to the log to see any of your triggers are firing at all. 

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[David Abigt]

Add me to the list.  _wst at m42.biz Been working (except for batteryVolt for some reason) for quite awhile till a couple weeks ago.

Simple app sending changed values of 8 tags to Homeseer  like so

var tags = <#tags_[12|13|26|32|52|62|72|21]_N#>;

tags.forEach(

function (tag) {

tag.updated = function () {

//KumoApp.Log("Updating:"+tag.name);

if(tag.name === "Comp Rack 0"){

 KumoApp.httpCall("http://10.10.1.45/JSON?user=hs3user&pass=hs3pass&request=controldevicebyvalue&ref=3121&value="+(tag.batteryVolt / 3.2),"GET"); 

 KumoApp.httpCall("http://10.10.1.45/JSON?user=hs3user&pass=hs3pass&request=controldevicebyvalue&ref=3122&value="+(tag.moisture),"GET"); 

 KumoApp.httpCall("http://10.10.1.45/JSON?user=hs3user&pass=hs3pass&request=controldevicebyvalue&ref=3123&value="+(tag.eventState),"GET"); 

 KumoApp.httpCall("http://10.10.1.45/JSON?user=hs3user&pass=hs3pass&request=controldevicebyvalue&ref=3126&value="+(tag.rssi),"GET"); 

 KumoApp.httpCall("http://10.10.1.45/JSON?user=hs3user&pass=hs3pass&request=controldevicebyvalue&ref=3124&value="+(tag.temperature * 9 / 5 + 32),"GET"); 

}  for each tag

Happened last week no errors and repowering seemed to sort it.

This week it stopped sending after getting this

9/8/2018 5:06 PM Unhandled exception occurred in one of your app: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1. Parameter name: dueTime at System.Threading.Timer.Change(Int32 dueTime, Int32 period) at System.Runtime.Remoting.Lifetime.LeaseManager.LeaseTimeAnalyzer(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

Tried rebooting and repowering but is only updating temperature value of tag 1

All data shows in charts and values are changing.

 

[Russel Metlitzky]

My app login e-mail is ta...@zerop.net

[Russel Met]

I also got this error yesterday and it hasn't worked since:

Unhandled exception occurred in one of your app: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1. Parameter name: dueTime at System.Threading.Timer.Change(Int32 dueTime, Int32 period) at System.Runtime.Remoting.Lifetime.LeaseManager.LeaseTimeAnalyzer(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[Zhiheng Cao]

>"Unhandled exception occurred in one of your app: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue "

This was probably due to a newly added configuration having a timeout value that is too large. This has just been fixed.  

Russel , your kumoapp were triggering today at these times (timezone in UTC).  Could you please check the time to see if something happening, because our record is showing your event handlers was started at 16:44:20:339  and finished at 16:44:21:324, for example.   The Tag handler(d8bebe3a-4556-4bf3-af55-607393b86554) means your KumoApp ID d8bebe3a.... was running. Your can find your KumoApp ID by right click on the kumoApp in Web Interface and choose "Inspect element" then look for a DIV tag with ID like "appid_d8bebe3a...." 

KumoAppEngine_131810712866678921.log(243): 09/10-16:44:20:339:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(d8bebe3a-4556-4bf3-af55-607393b86554) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(244): 09/10-16:44:21:324:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(d8bebe3a-4556-4bf3-af55-607393b86554) Successful

KumoAppEngine_131810712866678921.log(247): 09/10-16:44:35:152:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(24b56716-f960-418c-946f-d81ed3ed7181) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(248): 09/10-16:44:35:183:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(24b56716-f960-418c-946f-d81ed3ed7181) Successful

KumoAppEngine_131810712866678921.log(253): 09/10-16:44:48:621:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(a98c1a33-f183-4ec3-b894-432c19815f4e) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(254): 09/10-16:44:48:667:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(a98c1a33-f183-4ec3-b894-432c19815f4e) Successful

KumoAppEngine_131810712866678921.log(257): 09/10-16:45:00:386:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(5888a258-cbde-4f47-8e1f-fe174719f004) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(258): 09/10-16:45:00:418:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(5888a258-cbde-4f47-8e1f-fe174719f004) Successful

KumoAppEngine_131810712866678921.log(293): 09/10-16:50:42:090:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(7798db3a-9738-48dc-b406-dfedadef5f33) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(294): 09/10-16:50:42:121:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(7798db3a-9738-48dc-b406-dfedadef5f33) Successful

KumoAppEngine_131810712866678921.log(297): 09/10-16:51:10:636:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(9fbf113b-7fc2-4fa9-adbb-ac054ce14f08) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(298): 09/10-16:51:10:683:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(9fbf113b-7fc2-4fa9-adbb-ac054ce14f08) Successful

KumoAppEngine_131810712866678921.log(311): 09/10-16:56:15:621:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(e7e12235-f52b-4c0d-831f-3b14f8fd5f63) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(312): 09/10-16:56:15:668:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(e7e12235-f52b-4c0d-831f-3b14f8fd5f63) Successful

KumoAppEngine_131810712866678921.log(313): 09/10-16:56:32:558:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(2c438be8-fb0d-4315-a141-f562e07eef90) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(314): 09/10-16:56:32:590:<90c1be48-7ec8-47d7-991d-891be24bb1d5>Tag handler(2c438be8-fb0d-4315-a141-f562e07eef90) Successful

KumoAppEngine_131810712866678921.log(1781): 09/11-0:57:16:792: Stopping script for user 90c1be48-7ec8-47d7-991d-891be24bb1d5

KumoAppEngine_131810712866678921.log(1782): 09/11-0:57:16:901: Unloaded AppDomain for user 90c1be48-7ec8-47d7-991d-891be24bb1d5 REASON:'KumoAppEngine has been restarted by administrator for maintenance. Your app should restart automatically when the engine is restarted.

-----------

David, your KumoApp was triggering at below times:

KumoAppEngine_131810712866678921.log(217): 09/10-16:43:58:996:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) triggering 1 handlers...

KumoAppEngine_131810712866678921.log(218): 09/10-16:43:59:027:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) Successful

KumoAppEngine_131810712866678921.log(225): 09/10-16:44:00:339:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) triggering 0 handlers...

KumoAppEngine_131810712866678921.log(226): 09/10-16:44:00:339:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) Successful

KumoAppEngine_131810712866678921.log(835): 09/10-20:09:16:799:No more app running for userid 8734f7f3-3355-4bf6-ac46-61083beda08d unloading AppDomain...

KumoAppEngine_131810712866678921.log(839): 09/10-20:09:39:033:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) triggering 0 handlers...

KumoAppEngine_131810712866678921.log(840): 09/10-20:09:39:033:<8734f7f3-3355-4bf6-ac46-61083beda08d>Tag handler(498fc75b-7473-4a39-a823-802421c0ab03) Successful

KumoAppEngine_131810712866678921.log(1845): 09/11-0:57:18:995: Stopping script for user 8734f7f3-3355-4bf6-ac46-61083beda08d

KumoAppEngine_131810712866678921.log(1846): 09/11-0:57:19:089: Unloaded AppDomain for user 8734f7f3-3355-4bf6-ac46-61083beda08d REASON:'KumoAppEngine has been restarted by administrator for maintenance. Your app should restart automatically when the engine is restarted.

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[Russel Met]

My apps were triggered at the following approximate times,15:05 UTC, 16:30 UTC and then again at 01:00 UTC; however, they should be trigger many mores time than this.  It should be triggered every time there is a temperature change and it has changed many times in this 10 hour period, not just three times.

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[Zhiheng Cao]

I think you have misunderstood the Event handler "updated", it is triggered when something like the name or comment of the tag changes. What you are looking for is may be the temperatureChange Event handler,  please refer to http://mytaglist.com/kumoapp/60/temperaturechange

For all available events, please refer to http://mytaglist.com/kumoapp/17/tags-kumosensors-kumostats

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[Russel Met]

I have been using this app for well over a year and every time the temperature changed it updated. It didn't only update when a tag name or comment was updated. Even today it has updated a few times and nothing has been changed with the tag. It's really annoying when something that has been working perfectly for years now needs fixing because you decided to make some kind of "improvement".

If I'm using the wrong code could you provide specifics as to what I should change in my code as I'm not a programmer?

https://groups.google.com/d/msg/wireless-sensor-tags/cyGI5sauSmg/0dyWT_B6BQAJ

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

[Raymond Linschoten]

I'am also having difficuties with my KumoApps. I had to stop two off them because they are no longer 

reliable in what they supposed to do. Just like Russel they have been running for years now and I have been finetunning them during

this time but now they are no longer functioning.

A few days ago I have read the message from mytaglist.com support that there was a change in the KumoApp Engine and that it was no longer 

possible to have an event handler registered within a event handler and that they should be registered at the start of the app. For all I know I do not use an eventhandler in a eventhandler, but I am not quite sure. 

An example of code would help. I feel that I'am stuck now, I am willing to recode my KumoApps but haven't got a clue how.

I did make a support ticket by the way which I haven't received a response yet.

I would like to know if the KumoApp problems that users describe here since the change in the KumoApp engine are related to this event handler thing. If that is the case then please can you clarify perhaps with a example 

what a event handler registered in an event handler looks like and an example of how to recode this.

Op dinsdag 11 september 2018 08:14:19 UTC+2 schreef Russel Met:

[john simano]

@mytaglist.com support:

According to your own API documentation, the event "updated" is much more than just the name or comment changing:

http://wirelesstag.net/kumoapp/40/updated

"If an function is assigned to this event, any update (motion, periodic temperature update, temperature too low/too high/back to normal/out of range/in range/tag name edits, ...) to the tag will cause the handler to be called. "

I too am seeing that Kumo apps are not properly triggered for temperature changes. (even if i use the "temperatureChange" event)

[Zhiheng Cao]

The problem has just been identified and resolved. 

--

[David Abigt]

Mine started updating again about an hour back

[Zhiheng Cao]

The problem was entirely different from what was expected...  but now fixed. 

Now with the update, with the minor limitation you cannot dynamically add or remove event handlers inside another event handler, (99% of existing KumoApp does not do such thing so will not be affected) the memory footprint of the KumoApp engine is much smaller, events will trigger more reliably (problems reported by David E. should go away) , your KumoApps are starting and stopping much more quickly, and there will be more memory available for other parts of the system for overall server performance improvement. 

[David Abigt]

Thanks for the update. 

[David Eck]

Thank you very much! This issue has definitly been resolved.

[Yacov Malen]

Hi,

If I'm to understand correctly. I cannot schedule adding a tag.updated call back?

I.e. <@at time x@>.Task= function(){
tag.updated=function(){};
}

Thanks.

[Zhiheng Cao]

Correct. Just add the updated handler in the beginning and use Javascript time function to decide if to perform the action you want to perform. For example, if you intend to start logging at 16:00 then stop at 17:00 with schedule, instead of 

<@at time 4pm start@>.Task= function(){

tag.updated=function(){KumoApp.Log(this.temperature);};
}

<@at time 5pm stop@>.Task= function(){
tag.updated=null;
}

do this

tag.updated = function(){

if((new Date()).getHours()==16)KumoApp.Log(this.temperature);

}

[john simano]

@mytaglist.com support:

Your example uses hard-coded time. Could you give an example with a <@description@> placeholder, so the time window can be configurable?

Thanks!

[Zhiheng Cao]

Please refer to http://mytaglist.com/kumoapp/18/days-of-the-week-time-of-the-day

You can use the property TimeOfDay+ TimeZoneOffset to find the minute past midnight in UTC which is the timezone the Javascript engine will run. For example

var start_time = <@time start@>;

var stop_time = <@time stop@>;

tag.updated = function(){

var now = new Date();

var tod = now.getHours()*60+now.getMinutes();

if(tod > start_time.TimeOfDay + start_time.TimeZoneOffset && tod < stop_time.TimeOfDay + stop_time.TimeZoneOffset)KumoApp.Log(this.temperature);

}

[mytaglist.com support]

Here is a smarter way to do this

var $enabled=true;

 <@time start@>.Task=function(){ $enabled=true; }

 <@time stop@>.Task=function(){ $enabled=false; }

tag.updated = function(){

if($enabled)KumoApp.Log(this.temperature);

}

The "$" sign in the variable $enable makes the KumoApp engine save the variable in non-volatile storage that will survive app restart and KumoApp engine restart (a periodic maintenance that can happen as often as once per week).  Without it, the variable will be reset to true every time the app is stopped&started. 

On Wednesday, September 19, 2018 at 10:11:26 AM UTC-7, mytaglist.com support wrote:

Please refer to http://mytaglist.com/kumoapp/18/days-of-the-week-time-of-the-day

You can use the property TimeOfDay+ TimeZoneOffset to find the minute past midnight in UTC which is the timezone the Javascript engine will run. For example

var start_time = <@time start@>;

var stop_time = <@time stop@>;

tag.updated = function(){

var now = new Date();

var tod = now.getHours()*60+now.getMinutes();

if(tod > start_time.TimeOfDay + start_time.TimeZoneOffset && tod < stop_time.TimeOfDay + stop_time.TimeZoneOffset)KumoApp.Log(this.temperature);

}

On Wed, Sep 19, 2018 at 6:20 AM john simano <jason.p...@gmail.com> wrote:

@mytaglist.com support:

Your example uses hard-coded time. Could you give an example with a <@description@> placeholder, so the time window can be configurable?

Thanks!

On Tuesday, September 18, 2018 at 7:22:52 PM UTC-4, mytaglist.com support wrote:

Correct. Just add the updated handler in the beginning and use Javascript time function to decide if to perform the action you want to perform. For example, if you intend to start logging at 16:00 then stop at 17:00 with schedule, instead of 

<@at time 4pm start@>.Task= function(){

tag.updated=function(){KumoApp.Log(this.temperature);};
}

<@at time 5pm stop@>.Task= function(){
tag.updated=null;
}

do this

tag.updated = function(){

if((new Date()).getHours()==16)KumoApp.Log(this.temperature);

}

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