Network integration seems unreliable

56 views
Skip to first unread message

mej...@gmail.com

unread,
Sep 1, 2015, 12:10:40 AM9/1/15
to Wireless Sensor Tags
I have kumo apps reporting wemo gateway timeouts and at the same time ifttt triggers do not happen so two external services not being reliably triggered by my tags.  One is being triggered directly by a kumo app the other is using a default tag return to normal trigger.

Bradley Britton

unread,
Sep 1, 2015, 2:16:44 AM9/1/15
to Wireless Sensor Tags
My kumo apps also keep timing out and are unreliable. I wonder if it's just a problem with the kumo app service.

Zhiheng Cao

unread,
Sep 1, 2015, 2:31:45 AM9/1/15
to Bradley Britton, Wireless Sensor Tags
If even IFTTT cannot trigger your WeMo, it is not fault of KumoApp. It is the fault of Belkin WeMo server (which is what the "gateway" means in the "gateway timeout" error message).  

On Mon, Aug 31, 2015 at 11:16 PM, Bradley Britton <bradbr...@gmail.com> wrote:
My kumo apps also keep timing out and are unreliable.  I wonder if it's just a problem with the kumo app service.

--
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/c5d6543b-b8f8-40d6-8cb3-31c09948caed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mej...@gmail.com

unread,
Sep 1, 2015, 2:58:14 AM9/1/15
to Wireless Sensor Tags


On Tuesday, September 1, 2015 at 2:16:44 PM UTC+8, Bradley Britton wrote:
My kumo apps also keep timing out and are unreliable.  I wonder if it's just a problem with the kumo app service.

This is not just Kumo apps.  My IFTTT recipes  are not being triggered by my tags either and this is not linked with the Kumo apps at all this is supposed to be through IFTTT channel integration.  I think there is a bigger network issue or resource issue with the tag service to external apps.  I am next going to checl the inbuilt url calling to see how reliable the local lan url calling is and if it triggered 100% of the time it should be.

mej...@gmail.com

unread,
Sep 1, 2015, 3:08:25 AM9/1/15
to Wireless Sensor Tags, bradbr...@gmail.com
No it is not that ifttt cannot trigger the wemo it is the ifttt recipe itself is not being triggered when looking at the ifttt logs when a tag was supposed to trigger there is no trigger record so no attempt by ifttt to then turn my wemo on/off.  The wemo network had a 30 minute maintenance over the last day and I can see errors in ifttt not being able to trigger wemo with actual wemo errors.  But again this is a case of ifttt never being triggered.


On Tuesday, September 1, 2015 at 2:31:45 PM UTC+8, mytaglist.com support wrote:
If even IFTTT cannot trigger your WeMo, it is not fault of KumoApp. It is the fault of Belkin WeMo server (which is what the "gateway" means in the "gateway timeout" error message).  
On Mon, Aug 31, 2015 at 11:16 PM, Bradley Britton <bradbr...@gmail.com> wrote:
My kumo apps also keep timing out and are unreliable.  I wonder if it's just a problem with the kumo app service.

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

Bradley Britton

unread,
Sep 1, 2015, 5:41:58 AM9/1/15
to Wireless Sensor Tags
I was just wondering as my kumo app are tag specific only and I still many times get a message "the opporation has timed out" and the kumo app fails to complete. There is no external services in this case, only the tag system.
Reply all
Reply to author
Forward
0 new messages